[Touch-packages] [Bug 2061299] Re: Thinkpad T510 24.04 beta hangs on live CD

[Rob Peters]

Yes, safe boot boots correctly and that is where I did the dmesg.
Is there anything I can try to help eliminate possibilities?

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

Title:
  Thinkpad T510 24.04 beta hangs on live CD

Status in mesa package in Ubuntu:
  New

Bug description:
  Booting with UB 24.04 CD on Thinkpad T510.  Budgie graphics are missing on 
boot, just test "Ubuntu Budgie 24.04".
  Once desktop is loaded a hard freeze.  If one selects the boot option "Safe 
graphics" then the boot completes and liveCD is functional without lockup

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: mesa-vulkan-drivers 24.0.3-1ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr 14 15:21:51 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  MachineType: LENOVO 4384AJ9
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset --- quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.release: 1.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4384AJ9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4384AJ9
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061299/+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 2061327] Re: 24.04 beta hangs at desktop

[Rob Peters]

Not sure but no kernal drm module

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

Title:
  24.04 beta hangs at desktop

Status in mesa package in Ubuntu:
  New

Bug description:
  I have a Thinkpad T510 dual boot windows and Ubuntu Budgie 22.04

  Booting the 24.04 Ubuntu Budgie livecd, I notice that instead of the nice 
desktop graphics for Budgie I get a text line saying Ubuntu Budgie 24.04. Then 
when the desktop finally loads the liveCD locks up tight. Only a hard reset 
works.
  I have tried the Ubuntu 24.04 beta with same results.
  If I take the boot option "safe graphics" the live cd session loads correctly 
and does not hang.
  /$ inxi -FZRa
  System:
  Host: rob-ThinkPad-T510 Kernel: 6.8.0-11-generic arch: x86_64 bits: 64
  compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm
  parameters: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic
  root=UUID=35c54a5b-4746-419b-a598-d3d408c9066a ro quiet splash
  vt.handoff=7
  Desktop: Budgie v: 10.9.1 tk: GTK v: 3.24.41 wm: budgie-wm
  with: budgie-panel,plank tools: gnome-screensaver,gsd-screensaver-proxy
  dm: LightDM v: 1.30.0 Distro: Budgie 24.04 LTS (Noble Numbat) base: Ubuntu
  Machine:
  Type: Laptop System: LENOVO product: 4384AJ9 v: ThinkPad T510
  serial: Chassis: type: 10 serial:
  Mobo: LENOVO model: 4384AJ9 serial:
  uuid: BIOS: LENOVO v: 6MET92WW (1.52 ) date: 09/26/2012
  Battery:
  ID-1: BAT0 charge: 47.8 Wh (97.8%) condition: 48.9/47.5 Wh (103.0%)
  volts: 11.7 min: 10.8 model: LGC 42T4848 type: Li-ion serial: 39414
  status: discharging
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
  serial: 22-c2-4c-cc charge: 55% (should be ignored) rechargeable: yes
  status: discharging
  CPU:
  Info: model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere
  gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6
  model-id: 0x25 (37) stepping: 2 microcode: 0x11
  Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
  L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
  L3: 4 MiB desc: 1x4 MiB
  Speed (MHz): avg: 1720 high: 2667 min/max: 1199/2667 boost: enabled
  scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1199 2: 2667
  3: 1553 4: 1463 bogomips: 21280
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
  vulnerable
  Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
  SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
  prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
  sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
  STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
  Graphics:
  Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo
  driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports:
  active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3,
  VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.11 compositor: budgie-wm driver: X:
  loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
  display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
  s-diag: 414mm (16.31")
  Monitor-1: LVDS-1 model: Lenovo 0x40b0 built: 2010 res: 1366x768 hz: 60
  dpi: 101 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6")
  ratio: 16:9 modes: 1366x768
  API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
  device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus
  inactive: gbm,wayland
  API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.0.3-1ubuntu3
  glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (ILK)
  device-ID: 8086:0046 memory: 1.46 GiB unified: yes
  Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 5
  driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
  class-ID: 0403
  API: ALSA v: k6.8.0-11-generic status: kernel-api
  tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
  status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
  tools: pw-cat,pw-cli,wpctl
  Network:
  Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e
  v: kernel port: 1820 bus-ID: 00:19.0 chip-ID: 8086:10ea class-ID: 0200
  I

[Touch-packages] [Bug 2061326] [NEW] 24.04 beta hangs at desktop

[Rob Peters]

Public bug reported:

I have a Thinkpad T510 dual boot windows and Ubuntu Budgie 22.04

Booting the 24.04 Ubuntu Budgie livecd, I notice that instead of the nice 
desktop graphics for Budgie I get a text line saying Ubuntu Budgie 24.04. Then 
when the desktop finally loads the liveCD locks up tight. Only a hard reset 
works.
I have tried the Ubuntu 24.04 beta with same results.
If I take the boot option "safe graphics" the live cd session loads correctly 
and does not hang.
/$ inxi -FZRa
System:
Host: rob-ThinkPad-T510 Kernel: 6.8.0-11-generic arch: x86_64 bits: 64
compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic
root=UUID=35c54a5b-4746-419b-a598-d3d408c9066a ro quiet splash
vt.handoff=7
Desktop: Budgie v: 10.9.1 tk: GTK v: 3.24.41 wm: budgie-wm
with: budgie-panel,plank tools: gnome-screensaver,gsd-screensaver-proxy
dm: LightDM v: 1.30.0 Distro: Budgie 24.04 LTS (Noble Numbat) base: Ubuntu
Machine:
Type: Laptop System: LENOVO product: 4384AJ9 v: ThinkPad T510
serial: Chassis: type: 10 serial:
Mobo: LENOVO model: 4384AJ9 serial:
uuid: BIOS: LENOVO v: 6MET92WW (1.52 ) date: 09/26/2012
Battery:
ID-1: BAT0 charge: 47.8 Wh (97.8%) condition: 48.9/47.5 Wh (103.0%)
volts: 11.7 min: 10.8 model: LGC 42T4848 type: Li-ion serial: 39414
status: discharging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
serial: 22-c2-4c-cc charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere
gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6
model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1720 high: 2667 min/max: 1199/2667 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1199 2: 2667
3: 1553 4: 1463 bogomips: 21280
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo
driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports:
active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3,
VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
Display: x11 server: X.Org v: 21.1.11 compositor: budgie-wm driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: LVDS-1 model: Lenovo 0x40b0 built: 2010 res: 1366x768 hz: 60
dpi: 101 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6")
ratio: 16:9 modes: 1366x768
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus
inactive: gbm,wayland
API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.0.3-1ubuntu3
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (ILK)
device-ID: 8086:0046 memory: 1.46 GiB unified: yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
class-ID: 0403
API: ALSA v: k6.8.0-11-generic status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pw-cat,pw-cli,wpctl
Network:
Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e
v: kernel port: 1820 bus-ID: 00:19.0 chip-ID: 8086:10ea class-ID: 0200
IF: enp0s25 state: down mac: f0:de:f1:4c:d3:b9
Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:4239
class-ID: 0280
IF: wlp3s0 state: up mac: 58:94:6b:79:73:d4
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 238.47 GiB used: 11.89 GiB (5.0%)
SMART Message: Unable to run smartctl. Root privi

[Touch-packages] [Bug 2061327] [NEW] 24.04 beta hangs at desktop

[Rob Peters]

Public bug reported:

I have a Thinkpad T510 dual boot windows and Ubuntu Budgie 22.04

Booting the 24.04 Ubuntu Budgie livecd, I notice that instead of the nice 
desktop graphics for Budgie I get a text line saying Ubuntu Budgie 24.04. Then 
when the desktop finally loads the liveCD locks up tight. Only a hard reset 
works.
I have tried the Ubuntu 24.04 beta with same results.
If I take the boot option "safe graphics" the live cd session loads correctly 
and does not hang.
/$ inxi -FZRa
System:
Host: rob-ThinkPad-T510 Kernel: 6.8.0-11-generic arch: x86_64 bits: 64
compiler: gcc v: 13.2.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic
root=UUID=35c54a5b-4746-419b-a598-d3d408c9066a ro quiet splash
vt.handoff=7
Desktop: Budgie v: 10.9.1 tk: GTK v: 3.24.41 wm: budgie-wm
with: budgie-panel,plank tools: gnome-screensaver,gsd-screensaver-proxy
dm: LightDM v: 1.30.0 Distro: Budgie 24.04 LTS (Noble Numbat) base: Ubuntu
Machine:
Type: Laptop System: LENOVO product: 4384AJ9 v: ThinkPad T510
serial: Chassis: type: 10 serial:
Mobo: LENOVO model: 4384AJ9 serial:
uuid: BIOS: LENOVO v: 6MET92WW (1.52 ) date: 09/26/2012
Battery:
ID-1: BAT0 charge: 47.8 Wh (97.8%) condition: 48.9/47.5 Wh (103.0%)
volts: 11.7 min: 10.8 model: LGC 42T4848 type: Li-ion serial: 39414
status: discharging
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325
serial: 22-c2-4c-cc charge: 55% (should be ignored) rechargeable: yes
status: discharging
CPU:
Info: model: Intel Core i7 M 620 bits: 64 type: MT MCP arch: Westmere
gen: core 1 level: v2 built: 2010-11 process: Intel 32nm family: 6
model-id: 0x25 (37) stepping: 2 microcode: 0x11
Topology: cpus: 1x cores: 2 tpc: 2 threads: 4 smt: enabled cache:
L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1720 high: 2667 min/max: 1199/2667 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1199 2: 2667
3: 1553 4: 1463 bogomips: 21280
Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode;
SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW,
STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Core Processor Integrated Graphics vendor: Lenovo
driver: i915 v: kernel arch: Gen-5.75 process: Intel 45nm built: 2010 ports:
active: LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3,
VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0046 class-ID: 0300
Display: x11 server: X.Org v: 21.1.11 compositor: budgie-wm driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99")
s-diag: 414mm (16.31")
Monitor-1: LVDS-1 model: Lenovo 0x40b0 built: 2010 res: 1366x768 hz: 60
dpi: 101 gamma: 1.2 size: 345x194mm (13.58x7.64") diag: 396mm (15.6")
ratio: 16:9 modes: 1366x768
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast surfaceless: drv: crocus x11: drv: crocus
inactive: gbm,wayland
API: OpenGL v: 4.5 compat-v: 2.1 vendor: intel mesa v: 24.0.3-1ubuntu3
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics (ILK)
device-ID: 8086:0046 memory: 1.46 GiB unified: yes
Audio:
Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Lenovo 5
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
class-ID: 0403
API: ALSA v: k6.8.0-11-generic status: kernel-api
tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
tools: pw-cat,pw-cli,wpctl
Network:
Device-1: Intel 82577LM Gigabit Network vendor: Lenovo driver: e1000e
v: kernel port: 1820 bus-ID: 00:19.0 chip-ID: 8086:10ea class-ID: 0200
IF: enp0s25 state: down mac: f0:de:f1:4c:d3:b9
Device-2: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:4239
class-ID: 0280
IF: wlp3s0 state: up mac: 58:94:6b:79:73:d4
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 238.47 GiB used: 11.89 GiB (5.0%)
SMART Message: Unable to run smartctl. Root privi

[Touch-packages] [Bug 2061299] Re: Thinkpad T510 24.04 beta hangs on live CD

[Rob Peters]

The kernal module drm seems to be missing.

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

Title:
  Thinkpad T510 24.04 beta hangs on live CD

Status in mesa package in Ubuntu:
  New

Bug description:
  Booting with UB 24.04 CD on Thinkpad T510.  Budgie graphics are missing on 
boot, just test "Ubuntu Budgie 24.04".
  Once desktop is loaded a hard freeze.  If one selects the boot option "Safe 
graphics" then the boot completes and liveCD is functional without lockup

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: mesa-vulkan-drivers 24.0.3-1ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr 14 15:21:51 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  MachineType: LENOVO 4384AJ9
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset --- quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.release: 1.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4384AJ9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4384AJ9
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061299/+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 2061299] Re: Thinkpad T510 24.04 beta hangs on live CD

[Rob Peters]

The drum kernal module seems to be missing.

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

Title:
  Thinkpad T510 24.04 beta hangs on live CD

Status in mesa package in Ubuntu:
  New

Bug description:
  Booting with UB 24.04 CD on Thinkpad T510.  Budgie graphics are missing on 
boot, just test "Ubuntu Budgie 24.04".
  Once desktop is loaded a hard freeze.  If one selects the boot option "Safe 
graphics" then the boot completes and liveCD is functional without lockup

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: mesa-vulkan-drivers 24.0.3-1ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr 14 15:21:51 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  MachineType: LENOVO 4384AJ9
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset --- quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.release: 1.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4384AJ9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.33
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4384AJ9
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2061299/+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 2061299] [NEW] Thinkpad T510 24.04 beta hangs on live CD

[Rob Peters]

Public bug reported:

Booting with UB 24.04 CD on Thinkpad T510.  Budgie graphics are missing on 
boot, just test "Ubuntu Budgie 24.04".
Once desktop is loaded a hard freeze.  If one selects the boot option "Safe 
graphics" then the boot completes and liveCD is functional without lockup

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: mesa-vulkan-drivers 24.0.3-1ubuntu4
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.496
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Sun Apr 14 15:21:51 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
LiveMediaBuild: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
MachineType: LENOVO 4384AJ9
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset --- quiet splash
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2012
dmi.bios.release: 1.82
dmi.bios.vendor: LENOVO
dmi.bios.version: 6MET92WW (1.52 )
dmi.board.name: 4384AJ9
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.33
dmi.modalias: 
dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:br1.82:efr1.33:svnLENOVO:pn4384AJ9:pvrThinkPadT510:rvnLENOVO:rn4384AJ9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
dmi.product.family: ThinkPad T510
dmi.product.name: 4384AJ9
dmi.product.version: ThinkPad T510
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug noble ubuntu

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

Title:
  Thinkpad T510 24.04 beta hangs on live CD

Status in mesa package in Ubuntu:
  New

Bug description:
  Booting with UB 24.04 CD on Thinkpad T510.  Budgie graphics are missing on 
boot, just test "Ubuntu Budgie 24.04".
  Once desktop is loaded a hard freeze.  If one selects the boot option "Safe 
graphics" then the boot completes and liveCD is functional without lockup

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: mesa-vulkan-drivers 24.0.3-1ubuntu4
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr 14 15:21:51 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  LiveMediaBuild: Ubuntu-Budgie 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  MachineType: LENOVO 4384AJ9
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset --- quiet splash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.release: 1.82
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4384AJ9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No 

[Touch-packages] [Bug 2061169] [NEW] Notify send displays HTML tags

[Rob Somerville]

Public bug reported:

When Guake terminal is installed, the message alerting the user to press
F12 is displayed with HTML markup tags wrapping the F12 text rather than
displaying the F12 in bold.

This also applies to all other HTML tags as specified at:

https://www.galago-project.org/specs/notification/0.9/x161.html

[To recreate]

On a terminal, run:

notify-send "This is a bold message"


[Expected behavior]

Notify-send should either interpret the tag or not display it

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libnotify-bin 0.8.3-1build2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 12 17:35:23 2024
InstallationDate: Installed on 2024-04-10 (2 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: libnotify
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug noble wayland-session

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

Title:
  Notify send displays HTML tags

Status in libnotify package in Ubuntu:
  New

Bug description:
  When Guake terminal is installed, the message alerting the user to
  press F12 is displayed with HTML markup tags wrapping the F12 text
  rather than displaying the F12 in bold.

  This also applies to all other HTML tags as specified at:

  https://www.galago-project.org/specs/notification/0.9/x161.html

  [To recreate]

  On a terminal, run:

  notify-send "This is a bold message"

  
  [Expected behavior]

  Notify-send should either interpret the tag or not display it

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libnotify-bin 0.8.3-1build2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 17:35:23 2024
  InstallationDate: Installed on 2024-04-10 (2 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
  ProcEnviron:
   LANG=en_GB.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: libnotify
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/2061169/+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 2061022] [NEW] Intermittent keyboard lag with Tecknet EKB01002BK01 keyboard

[Rob Somerville]

Public bug reported:

This bug manifests itself slightly differently across different
scenarios. To summarise, scrolling through a long file/directory listing
in Midnight Commander (e.g. > 40 items) causes the cursor to lag,
stutter and pause.

In 23.10 if the up/down key is depressed there is a delay of about 0.25
seconds before moving onto the previous/next item. In 24.04, the cursor
will stick on the previous/last item until it is released.

This behavior is not exhibited in a console session [e.g. via
Ctrl+Alt+F5], with Ubuntu 22.04 LTS or under Wayland. It also does not
seem to affect the Tecknet EMK01707 keyboard under Ubuntu 23.10.

This behavior has been observed using both Guake terminal [Version 3.10]
and Gnome terminal [Version 3.52.0 for GNOME 46].

[Affected Ubuntu versions]

Ubuntu 23.10
Ubuntu 24.04

[To recreate]

Open mc in terminal and browse through a long directory/file listing (>
40 items). This behavior will manifest immediately or after a few
cycles.

[Expected behavior]

The cursor should scroll linearly throughout a list without pauses,
juddering, lag or requiring the user to release the key.

[Workarounds]

1. Switch to Wayland
2. Use a different keyboard. The problem was not apparent using a Tecknet 
EMK01707 keyboard under 23.10, however this has not been tested under Noble 
Numbat.

[Further information]

MC version:

GNU Midnight Commander 4.8.30
Built with GLib 2.80.0
Built with S-Lang 2.3.3 with terminfo database
Built with libssh2 1.11.0
With builtin Editor and Aspell support
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
With internationalization support
With multiple codepages support
With ext2fs attributes support
Virtual File Systems:
 cpiofs, tarfs, sfs, extfs, ext2undelfs, ftpfs, sftpfs, fish
Data types:
 char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64;

[Related bugs]

This seems related to https://bugs.launchpad.net/debian/+source/xserver-
xorg-input-evdev/+bug/1002951

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.fabric-imex-mgmt:
 DeviceFileMinor: 4323
 DeviceFileMode: 256
 DeviceFileModify: 1
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  550.67  Tue Mar 12 23:54:15 
UTC 2024
 GCC version:  gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3)
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 11 19:11:20 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus: nvidia/550.67, 6.8.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:2375]
InstallationDate: Installed on 2024-04-10 (1 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-22-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.00
dmi.board.name: A320M-DVS R4.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.00:bd07/16/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-DVSR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.3-1ubuntu4
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: 

[Touch-packages] [Bug 2043215] [NEW] Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.

[Rob Frohne]

Public bug reported:

There is more information on this issue: 
https://github.com/xournalpp/xournalpp/issues/5303
and the other bug report that is linked there.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 10 07:17:22 2023
DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
 virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
InstallationDate: Installed on 2021-05-25 (899 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux 
quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
dmi.bios.date: 12/21/2015
dmi.bios.release: 1.15
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.15
dmi.board.name: FJNB288
dmi.board.vendor: FUJITSU
dmi.board.version: D2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
dmi.product.name: LIFEBOOK T935
dmi.sys.vendor: FUJITSU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic ubuntu

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

Title:
  Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
  Xorg.

Status in xorg package in Ubuntu:
  New

Bug description:
  There is more information on this issue: 
https://github.com/xournalpp/xournalpp/issues/5303
  and the other bug report that is linked there.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 07:17:22 2023
  DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
  InstallationDate: Installed on 2021-05-25 (899 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic 
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
  dmi.bios.date: 12/21/2015
  dmi.bios.release: 1.15
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.15
  dmi.board.name: FJNB288
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 

[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04

[Rob Brown-Bayliss]

I have an issue. I can connect to the hotspot just fine, but the
connected devices get disconnected almost immediately

I tried all the wifi security options one by one, and there is the same
behavior with each of them.

from journalctrl output
Nov 11 08:36:29 tortuga wpa_supplicant[19131]: wlo2: AP-STA-CONNECTED 
a6:81:e8:e3:73:66
Nov 11 08:36:29 tortuga wpa_supplicant[19131]: wlo2: EAPOL-4WAY-HS-COMPLETED 
a6:81:e8:e3:73:66
Nov 11 08:36:47 tortuga wpa_supplicant[19131]: wlo2: AP-STA-DISCONNECTED 
a6:81:e8:e3:73:66

How do I get this to work?  The Ubuntu 22.04 machine gets internet from
a wired connection to the home router, the router provided DHCP and DNS
services

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

Title:
  My machine has Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1970284] Re: Touch to click cannot be turned off....

[Rob Frohne]

A bunch of other controls in gnome-settings were not working either.
You could not turn off the touchpad or two finger scrolling or turn on
natural scrolling, etc.

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

Title:
  Touch to click cannot be turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970284/+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 1970284] Re: Touch to click cannot be turned off....

[Rob Frohne]

This can be resolved by removing the xserver-xorg-input-synaptics
package.  I don't know if it was installed previous to installing Ubuntu
22.04, but both it and libinput were installed afterwards.  Here is the
page that gave me the tip.

https://gitlab.gnome.org/GNOME/gnome-flashback/-/issues/54

** Bug watch added: gitlab.gnome.org/GNOME/gnome-flashback/-/issues #54
   https://gitlab.gnome.org/GNOME/gnome-flashback/-/issues/54

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

Title:
  Touch to click cannot be turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970284/+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 1970284] Re: Touch to click cannot be turned off....

[Rob Frohne]

Natural scrolling works when selected in Wayland.  Furthermore, edge scrolling 
cannot be turned off
in xorg, but can be in Wayland. Two-finger scrolling cannot be turned off 
either in xorg. Neither can the touchpad.

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

Title:
  Touch to click cannot be turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970284/+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 1970284] Re: Touch to click cannot be turned off....

[Rob Frohne]

Natural scrolling doesn't work either.

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

Title:
  Touch to click cannot be turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970284/+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 1970284] [NEW] Touch to click cannot be turned off....

[Rob Frohne]

Public bug reported:

Hi,
Using xorg, I cannot turn touch to click off.  It can be turned off in wayland.
Rob

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 25 15:52:04 2022
DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
InstallationDate: Installed on 2019-04-19 (1102 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
MachineType: LENOVO 20FES0EX00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: xorg
UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
dmi.bios.date: 06/26/2018
dmi.bios.release: 1.70
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET91W (1.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FES0EX00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.27
dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
dmi.product.family: ThinkPad Yoga 260
dmi.product.name: 20FES0EX00
dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
dmi.product.version: ThinkPad Yoga 260
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu

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

Title:
  Touch to click cannot be turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX0

[Touch-packages] [Bug 1970284] Re: Touch to click cannot be turned off....

[Rob Frohne]

This occurred on updating to Ubuntu 22.04.
Rob

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

Title:
  Touch to click cannot be turned off

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970284/+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 1923384] [NEW] [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at all

[rob from ottawa]

Public bug reported:

When I run Alsamixer, there seem to be two cards, the first of which is
HDA Intel HDMI, so my initial thought was that the wrong sound port must
be selected by default, but wgen I use F6, to select "HDA Intel PCH",
Card Realtek ALC3661, I still cannot get the internal speakers to
produce sound. Note that the headphone jack does work.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 11 19:31:46 2021
InstallationDate: Installed on 2021-04-10 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2015
dmi.bios.release: 0.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: Dell Precision M3800
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.ec.firmware.release: 0.9
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/08/2015:br0.9:efr0.9:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Dell Precision M3800
dmi.product.sku: Dell Precision M3800
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

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

Title:
  [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I run Alsamixer, there seem to be two cards, the first of which
  is HDA Intel HDMI, so my initial thought was that the wrong sound port
  must be selected by default, but wgen I use F6, to select "HDA Intel
  PCH", Card Realtek ALC3661, I still cannot get the internal speakers
  to produce sound. Note that the headphone jack does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 11 19:31:46 2021
  InstallationDate: Installed on 2021-04-10 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Dell Precision M3800, Realtek ALC3661, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.release: 0.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 0.9
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/08/2015:br0.9:efr0.9:svnDellInc.:pnDellPrecisionM3800:pvrA09:rvnDellInc.:rnDellPrecisionM3800:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1923384/+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 1922926] [NEW] Battery applet not updated after sleep

[Rob Peters]

Public bug reported:

Ubuntu Budgie 21.04.
On battery, for example, battery says 40%.  Close lid of laptop and then plug 
the laptop into AC.
Open laptop on AC and applet still says 40% and gives no indication of being on 
AC.  Disconnect AC and reconnect AC no change.  The applet uses Upower to 
respond to battery events. So whatever is feeding Upower isnt being updated 
after a resume.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: upower 0.99.11-2
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Budgie:GNOME
Date: Wed Apr  7 07:17:27 2021
InstallationDate: Installed on 2020-04-18 (353 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: upower
UpgradeStatus: Upgraded to hirsute on 2021-03-28 (9 days ago)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  Battery applet not updated after sleep

Status in upower package in Ubuntu:
  New

Bug description:
  Ubuntu Budgie 21.04.
  On battery, for example, battery says 40%.  Close lid of laptop and then plug 
the laptop into AC.
  Open laptop on AC and applet still says 40% and gives no indication of being 
on AC.  Disconnect AC and reconnect AC no change.  The applet uses Upower to 
respond to battery events. So whatever is feeding Upower isnt being updated 
after a resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: upower 0.99.11-2
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Budgie:GNOME
  Date: Wed Apr  7 07:17:27 2021
  InstallationDate: Installed on 2020-04-18 (353 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200417)
  SourcePackage: upower
  UpgradeStatus: Upgraded to hirsute on 2021-03-28 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1922926/+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 1901430] [NEW] After suspend stylus position confused about rotated screen in multi-monitor setup

[Rob Frohne]

Public bug reported:

I have a tablet computer that has the monitor rotated to upside down
landscape position.  There is also an external monitor connected to this
computer.  When I suspend and awake this computer, the stylus position
is as if the tablet computer's screen was not rotated.  The mouse cursor
is fine, but not the stylus, and the confusion of the stylus goes into
the external monitor.

Thanks for all you do to fix annoying bugs for all of us users!

A work around is to rotate the screen, as the stylus regains its
bearings when you do that.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 25 10:57:29 2020
DistUpgraded: 2020-10-23 20:36:53,845 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-52-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.8.0-25-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:162a]
InstallationDate: Installed on 2020-05-17 (161 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Hewlett-Packard HP EliteBook 2760p
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=694dacef-c80d-436a-8434-767b308d9087 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to groovy on 2020-10-24 (1 days ago)
dmi.bios.date: 07/15/2013
dmi.bios.release: 15.66
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SOU Ver. F.42
dmi.board.name: 162A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 05.40
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 5.64
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SOUVer.F.42:bd07/15/2013:br15.66:efr5.64:svnHewlett-Packard:pnHPEliteBook2760p:pvrA0005F02:rvnHewlett-Packard:rn162A:rvrKBCVersion05.40:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 2760p
dmi.product.sku: XX047AV#ABA
dmi.product.version: A0005F02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy ubuntu

** Summary changed:

- After suspend  stylus position confused about rotated screen is multi-monitor 
setup
+ After suspend  stylus position confused about rotated screen in multi-monitor 
setup

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

Title:
  After suspend  stylus position confused about rotated screen in multi-
  monitor setup

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a tablet computer that has the monitor rotated to upside down
  landscape position.  There is also an external monitor connected to
  this computer.  When I suspend and awake this computer, the stylus
  position is as if the tablet computer's screen was not rotated.  The
  mouse cursor is fine, but not the stylus, and the confusion of the
  stylus goes into the external monitor.

  Thanks for all you do to fix annoying bugs for all of us users!

  A work around is to rotate the screen, as the stylus regains its
  bearings when you do that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: 

[Touch-packages] [Bug 1806407] Re: Mobile broadband SIM doesn't work but does on same machine booted into Windows

[Rob Davis]

Thrilled to confirm that this now works in Ubuntu 20.04.1 LTS 64bit I
have checked today.

Thank you so, so much.

Will update with more details on:
https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-
work-with-ubuntu-18-04-but-does-work-in-same-device

SIM hardware is detected following and it's then just a case of going
through the wizard setup dialog Windows that is displayed after you
click on your mobile networking symbol on top right or from the top
right drop down.

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

Title:
  Mobile broadband SIM doesn't work but does on same machine booted into
  Windows

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I am trying to use a mobile broadband sim with my TabletPC running
  Ubuntu 18.04, but it doesn't work, I get: "Connection Failed:
  Activation of network connection failed" when trying to connect with
  it. HOWEVER, if I boot this same TabletPC into Windows 10, the sim
  works fine. So it is not a problem with the SIM nor a problem the
  TabletPC hardware. It is a problem with Ubuntu.

  Can I ask what testing/Quality Assurance (QA) you did on Ubuntu for
  mobile broadband and where your testing records are kept?

  
  Further details here:
  
https://askubuntu.com/questions/1079689/mobile-broadband-sim-doesnt-work-with-ubuntu-18-04-but-does-work-in-same-device

  "I have a Panasonic FZ-G1 MkIII Toughpad touchscreen tablet PC which
  is based on an x86-64bit Intel® Core™ i5-5300U CPU @ 2.30GHz, with 4Gb
  RAM.

  This is dual-booted with Windows 10 Pro 64bit (build 1803) and Ubuntu
  18.04.1 LTS 64bit.

  The mobile sim is a standard giffgaff sim which works fine in Windows
  on this machine - it is recognised and internet access via it works,
  detected as LTE (4G). So this proves that the sim is working correctly
  with the WLAN modem hardware in this tablet.

  However, when the same tablet is booted into Ubuntu 18.04.1 LTS 64bit,
  the same sim that worked in the Windows partition, does not work in
  Ubuntu. Error message: "Connection Failed: Activation of network
  connection failed" pops up when attempting connection via Settings. "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1806407/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Rob Robertson]

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

This is not a duplicate of bug 1576559.   It is a duplicate of #1878194

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rob Robertson]

** Also affects: bluez (Ubuntu)
   Importance: Undecided
   Status: 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/1878194

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rob Robertson]

There is another confirmation of this happening with QC35s on the Bose
forums.

https://community.bose.com/t5/Around-On-Ear-Headphones/qc35-microphone-
not-working-on-ubuntu-20-04/td-p/300415

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878194/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rob Robertson]

I'm experiencing this issue after upgrading to 20.04 from 19.10.   My
headphones are Bose QC35s.  Pretty much exactly the same symptoms.
Sound works well from A2DP profile.  Sound stops working when HSP/HFP is
selected. Works when A2DP is,again, selected.

Tried deleting the user .config profile.

[system info]
ubuntu: 20.04 - 5.4.0-31-generic 
hardware: dell xps 13 7390 
pulseaudio 13.99.1
headset:  bose qc35

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1878194/+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 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

[Rob Frohne]

As another work around (for those of us doing online lectures to avoid spread 
of Covid-19) you can use this gnome extension.
https://extensions.gnome.org/extension/906/sound-output-device-chooser/

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

Title:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1864638] [NEW] e-cal-recur: Incorrect timezone used for DTEND from DURATION

[Rob N]

Public bug reported:

Recurring events from CalDAV with DTSTART and DURATION but no DTEND get
incorrect timezone for the end time.

Reported upstream:

https://gitlab.gnome.org/GNOME/evolution-data-server/issues/194

And fixed:

https://gitlab.gnome.org/GNOME/evolution-data-
server/-/commit/80072aea88235e1cfe2223d8d5c7d9605700a71f

I'd love to see this backported to 18.04. The equivalent patch against
3.28.5 should just be:

--- evolution-data-server-3.28.5.orig/src/calendar/libecal/e-cal-recur.c
+++ evolution-data-server-3.28.5/src/calendar/libecal/e-cal-recur.c
@@ -206,6 +206,8 @@ ensure_timezone (icalcomponent *comp,
 
if (!prop)
prop = icalcomponent_get_first_property (comp, prop_kind);
+   if (!prop && prop_kind == ICAL_DTEND_PROPERTY)
+   prop = icalcomponent_get_first_property (comp, 
ICAL_DTSTART_PROPERTY);
if (!prop)
return TRUE;
 

(I've been running this patch for a week and it seems to be working
great).

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  e-cal-recur: Incorrect timezone used for DTEND from DURATION

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Recurring events from CalDAV with DTSTART and DURATION but no DTEND
  get incorrect timezone for the end time.

  Reported upstream:

  https://gitlab.gnome.org/GNOME/evolution-data-server/issues/194

  And fixed:

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/commit/80072aea88235e1cfe2223d8d5c7d9605700a71f

  I'd love to see this backported to 18.04. The equivalent patch against
  3.28.5 should just be:

  --- evolution-data-server-3.28.5.orig/src/calendar/libecal/e-cal-recur.c
  +++ evolution-data-server-3.28.5/src/calendar/libecal/e-cal-recur.c
  @@ -206,6 +206,8 @@ ensure_timezone (icalcomponent *comp,
   
if (!prop)
prop = icalcomponent_get_first_property (comp, prop_kind);
  + if (!prop && prop_kind == ICAL_DTEND_PROPERTY)
  + prop = icalcomponent_get_first_property (comp, 
ICAL_DTSTART_PROPERTY);
if (!prop)
return TRUE;
   

  (I've been running this patch for a week and it seems to be working
  great).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1864638/+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 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

[Rob Bruce]

It seems a shame that my affected hardware didn't live to see this day
:( If it had held on another year and a half, I would've been able to
test this out. Glad Martin's was still working to check it out over
_eleven years_ (!) after he first commented on this issue!

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

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez-utils-old/+bug/123920/+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 1860915] [NEW] slow shutdown Whonix as guest on Ubuntu host running KVM

[rob]

Public bug reported:

Recently I have come to use Whonix 15.0.0.7.1 as guest OS running in a VM under 
KVM, while the host OS I am running is Ubuntu 18.04.3. Problem is the slow 
shutdown of Whonix which most of times takes about 2 minutes. There is a 
problem report regarding this issue on Whonix which testifies I am not the only 
user affected by this problem. 
https://forums.whonix.org/t/slow-shutdown-of-version-15-workstation-and-gateway/8828
Still other people seem not affected (a regular shutdown should take about 3 
seconds). 

One of Whonix maintainers Patrick asked for log files. Part of the
systemd log:

Jan 24 11:13:38 host systemd[1]: session-1.scope: Stopping timed out. Killing.
Jan 24 11:13:38 host systemd[1]: session-1.scope: Killing process 1956 
(lightdm) with signal SIGKILL.
Jan 24 11:13:38 host systemd[1]: session-1.scope: Failed with result ‘timeout’.
Jan 24 11:13:38 host systemd[1]: Stopped Session 1 of user user.

This provoked Patrick to ask for the lightdm logs. I sent those as well,
which did not reveal anything out of the ordinary. Still Patrick thought
I should contact the upstream maintainer of the lightdm package. Version
lightdm: 1.26.0-4.

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

** Attachment added: "systemd-log-previous-workstation"
   
https://bugs.launchpad.net/bugs/1860915/+attachment/5323046/+files/systemd-log-previous-workstation

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

Title:
  slow shutdown Whonix as guest on Ubuntu host running KVM

Status in lightdm package in Ubuntu:
  New

Bug description:
  Recently I have come to use Whonix 15.0.0.7.1 as guest OS running in a VM 
under KVM, while the host OS I am running is Ubuntu 18.04.3. Problem is the 
slow shutdown of Whonix which most of times takes about 2 minutes. There is a 
problem report regarding this issue on Whonix which testifies I am not the only 
user affected by this problem. 
  
https://forums.whonix.org/t/slow-shutdown-of-version-15-workstation-and-gateway/8828
  Still other people seem not affected (a regular shutdown should take about 3 
seconds). 

  One of Whonix maintainers Patrick asked for log files. Part of the
  systemd log:

  Jan 24 11:13:38 host systemd[1]: session-1.scope: Stopping timed out. Killing.
  Jan 24 11:13:38 host systemd[1]: session-1.scope: Killing process 1956 
(lightdm) with signal SIGKILL.
  Jan 24 11:13:38 host systemd[1]: session-1.scope: Failed with result 
‘timeout’.
  Jan 24 11:13:38 host systemd[1]: Stopped Session 1 of user user.

  This provoked Patrick to ask for the lightdm logs. I sent those as
  well, which did not reveal anything out of the ordinary. Still Patrick
  thought I should contact the upstream maintainer of the lightdm
  package. Version lightdm: 1.26.0-4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860915/+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 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[Rob Grune]

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

affects me too.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850887/+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 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected

[Rob Frohne]

I spent 45 minutes playing with this problem this morning.  I restarted
my computer this morning, but nothing helped.  Now, after work, where
the computer was in suspended, but not restarted, and used periodically,
and it works just fine.  I did connect another headset to see if it was
a Sony problem, and now both headsets work as expected.  I do know that
A2DP is deactivated if you select the microphone on the headset, but
this morning I switched that back and forth several times with no
effect.  Fortunately, or unfortunately as it may be, I cannot now
duplicate the results I had this morning, and I can't figure out why.
It may have happened when I connected the headset to bluetooth again to
test this evening.  I cannot remember if I disconnected the headset and
reconnected it this morning.

Rob

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

Title:
  Bluetooth headphones/speaker default to low quality headset mode and
  fails to switch to A2DP when selected

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Whenever I turn on my headphones theyll connect to my computer but im
  able to hear the input audio from my microphone and low quality output
  audio. I have to disconnect the headphones in the bluetooth devices
  and reconnect for it to fix the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  litleck1398 F pulseaudio
   /dev/snd/controlC0:  litleck1398 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 23 17:07:59 2019
  InstallationDate: Installed on 2019-09-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: WH-1000XM3
  Symptom_Type: High background noise, or volume is too low
  Title: [WH-1000XM3, playback] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2019
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.19
  dmi.board.name: 01NYPT
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified:
  dmi.product.family: Alienware
  dmi.product.name: Alienware Aurora R5
  dmi.product.sku: 0729
  dmi.product.version: 1.0.19
  dmi.sys.vendor: Alienware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845046/+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 1850444] [NEW] Cannot connect headset to A2DP anymore....

[Rob Frohne]

Public bug reported:

As of October 29, I can no longer connect to my Sony MDR-1000x headphones using 
A2DP.  The gnome sound manager has the setting, but when I select it and use 
the test button, it is only mono.  I tried the gnome extension 
https://extensions.gnome.org/extension/906/sound-output-device-chooser/ and the 
option is always grayed out there. I tried to make A2DP the default using the 
method described here: 
https://medium.com/@overcode/fixing-bluetooth-in-ubuntu-pop-os-18-04-d4b8dbf7ddd6
I tried to install some tools to try and get a better idea what might be going 
on.  In case it was a recent update, here are the last few days of my update 
log:
Start-Date: 2019-10-21  08:19:53
Commandline: aptdaemon role='role-commit-packages' sender=':1.375055'
Install: linux-image-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-extra-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-modules-5.3.0-19-generic:amd64 (5.3.0-19.20, automatic), 
linux-headers-5.3.0-19:amd64 (5.3.0-19.20, automatic)
Upgrade: linux-headers-generic:amd64 (5.3.0.18.21, 5.3.0.19.22), 
linux-libc-dev:amd64 (5.3.0-18.19, 5.3.0-19.20), linux-image-generic:amd64 
(5.3.0.18.21, 5.3.0.19.22), linux-signed-generic:amd64 (5.3.0.18.21, 
5.3.0.19.22), linux-generic:amd64 (5.3.0.18.21, 5.3.0.19.22)
End-Date: 2019-10-21  08:21:37

Start-Date: 2019-10-21  11:42:11
Commandline: aptdaemon role='role-commit-packages' sender=':1.1749'
Upgrade: libaspell15:amd64 (0.60.7-3, 0.60.7-3ubuntu0.1), aspell:amd64 
(0.60.7-3, 0.60.7-3ubuntu0.1), libexiv2-14:amd64 (0.25-4ubuntu2, 
0.25-4ubuntu2.1)
Remove: linux-modules-extra-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-modules-5.0.0-32-generic:amd64 (5.0.0-32.34), 
linux-image-5.0.0-32-generic:amd64 (5.0.0-32.34)
End-Date: 2019-10-21  11:42:26

Start-Date: 2019-10-22  06:19:40
Commandline: /usr/bin/unattended-upgrade
Upgrade: libopenjp2-7:amd64 (2.3.0-2, 2.3.0-2build0.19.10.1)
End-Date: 2019-10-22  06:19:41

Start-Date: 2019-10-22  19:12:43
Commandline: aptdaemon role='role-commit-packages' sender=':1.375112'
Upgrade: google-chrome-stable:amd64 (77.0.3865.120-1, 78.0.3904.70-1), 
xsltproc:amd64 (1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:amd64 
(1.1.33-0ubuntu1, 1.1.33-0ubuntu1.1), libxslt1.1:i386 (1.1.33-0ubuntu1, 
1.1.33-0ubuntu1.1)
End-Date: 2019-10-22  19:12:59

Start-Date: 2019-10-24  07:00:54
Commandline: aptdaemon role='role-commit-packages' sender=':1.660642'
Upgrade: firefox-locale-en:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), firefox:amd64 (69.0.3+build1-0ubuntu1, 
70.0+build2-0ubuntu0.19.10.1), linux-firmware:amd64 (1.183, 1.183.1)
End-Date: 2019-10-24  07:01:58

Start-Date: 2019-10-29  06:33:22
Commandline: /usr/bin/unattended-upgrade
Upgrade: libwbclient0:amd64 (2:4.10.7+dfsg-0ubuntu2, 2:4.10.7+dfsg-0ubuntu2.2), 
samba-libs:amd64 (2:4.10.7+dfsg-0ubuntu2, 2:4.10.7+dfsg-0ubuntu2.2), 
libsmbclient:amd64 (2:4.10.7+dfsg-0ubuntu2, 2:4.10.7+dfsg-0ubuntu2.2)
End-Date: 2019-10-29  06:33:25

Start-Date: 2019-10-29  07:22:22
Commandline: /usr/sbin/synaptic
Requested-By: frohro (1000)
Install: bluez-tests:amd64 (5.50-0ubuntu4), bluez-tools:amd64 
(2.0~20170911.0.7cb788c-2build1), bluetooth:amd64 (5.50-0ubuntu4)
End-Date: 2019-10-29  07:22:28

Start-Date: 2019-10-29  07:44:42
Commandline: apt install pulseaudio pulseaudio-utils pavucontrol 
pulseaudio-module-bluetooth
Requested-By: frohro (1000)
Install: pavucontrol:amd64 (3.0-4)
End-Date: 2019-10-29  07:44:48

Nothing I tried solves the issue.  It was working a few days ago.

Thanks,

Rob

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: bluez 5.50-0ubuntu4
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 29 07:52:45 2019
InstallationDate: Installed on 2019-04-19 (193 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 20FES0EX00
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro
SourcePackage: bluez
UpgradeStatus: Upgraded to eoan on 2019-10-18 (11 days ago)
dmi.bios.date: 06/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1GET91W (1.70 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FES0EX00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad Yoga 260
dmi.product.name: 20FES0EX00
dmi.p

[Touch-packages] [Bug 1641417] Re: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.

[Rob Cannell]

This is still an issue for me on Ubuntu 18.04. Can mount iPhone 5 via
Nautilus but it doesn't show on Rhythmbox or Banshee.

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

Title:
  Ubuntu 16.04 unable to detect/connect  to and work properly with
  iPhone 4.

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  
  Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. 
  Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via 
gphoto2, where access is limited to viewing and copying photos and videos. The 
2nd connection that is mounted via afc fail to work, hence other folders in 
iPhone are not accessible.

  Action 2: Unplugged and re-plugged iPhone 4 to the workstation.
  Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount 
point appear.

  Checks and Remedy used: 
  1. "ideviceinfo" and lsusb command show iPhone 4 is connected.
  2. "idevicepair validate" command shows "SUCCESS: Validated pairing with 
device [UDID]"
  3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in 
Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 
appears and are accessible.

  I believe the 1st mounting of iPhone 4 on Nautilus is due to the
  "gvfs-backends" package. W/o it, auto detection/connection of iPhone 4
  would not occur and appear in Nautilus. However, the afc mount failed
  to work

  The 2nd mounting is caused by ifuse. This works perfectly but requires
  manual mounting and unmounting.

  
  Questions: 
  1. How to overcome issues/failures mentioned in Result 1 & 2? 
  2. Ideally, i would like the automatic detection-connection between Ubuntu 
and iPhone to work. If not, is there a way to automate connection via ifuse? 

  
  System and package info:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial

  $ uname -or
  4.4.0-47-generic GNU/Linux

  $ dpkg -l | grep iPhone
  ii  ifuse1.1.2-0.1build3 amd64  FUSE module for 
iPhone and iPod Touch devices
  ii  libimobiledevice-utils   1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with iPhone and iPod Touch devices
  ii  libimobiledevice6:amd64  1.2.0+dfsg-3~ubuntu0.2  amd64  Library for 
communicating with the iPhone and iPod Touch
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  usbmuxd  1.1.0-2 amd64  USB multiplexor 
daemon for iPhone and iPod Touch devices

  $ dpkg -l | grep libusb
  ii  libgusb2:amd64   0.2.9-0ubuntu1  amd64   GLib wrapper around 
libusb1
  ii  libusb-0.1-4:amd64   2:0.1.12-28 amd64   userspace USB 
programming library
  ii  libusb-1.0-0:amd64   2:1.0.20-1  amd64   userspace USB 
programming library
  ii  libusb-1.0-0:i3862:1.0.20-1  i386userspace USB 
programming library
  ii  libusbmuxd-tools 1.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - tools
  ii  libusbmuxd4:amd641.0.10-2ubuntu0.1   amd64   USB multiplexor 
daemon for iPhone and iPod Touch devices - library
  ii  libusbredirhost1:amd64   0.7.1-1 amd64   Implementing the 
usb-host (*) side of a usbredir connection (runtime)
  ii  libusbredirparser1:amd64 0.7.1-1 amd64   Parser for the 
usbredir protocol (runtime)

  $ dpkg -l | grep gvfs
  ii  gvfs:amd64  1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - GIO module
  ii  gvfs-backends   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - backends
  ii  gvfs-bin1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - binaries
  ii  gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual 
filesystem - common data files
  ii  gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - servers
  ii  gvfs-fuse   1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - fuse server
  ii  gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64  userspace virtual 
filesystem - private libraries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1641417/+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 1812095] Re: console login loop after entering username followed by RETURN

[Rob Mosher]

I'm experiencing the same issue. Here is the output from
/var/log/auth.log after attempting to login:

Jan 30 17:52:39 computername login[3483]: pam_unix(login:auth): conversation 
failed
Jan 30 17:52:39 computername login[3483]: pam_unix(login:auth): auth could not 
identify password for [username]
Jan 30 17:52:42 computername login[3483]: FAILED LOGIN (1) on '/dev/tty2' FOR 
'UNKNOWN', Authentication failure
Jan 30 17:52:42 computername login[3483]: pam_securetty(login:auth): cannot 
determine username
Jan 30 17:52:46 computername login[3483]: FAILED LOGIN (2) on '/dev/tty2' FOR 
'UNKNOWN', Error in service module
Jan 30 17:52:46 computername login[3483]: pam_securetty(login:auth): cannot 
determine username
Jan 30 17:52:49 computername login[3483]: FAILED LOGIN (3) on '/dev/tty2' FOR 
'UNKNOWN', Error in service module

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1796707] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

[Rob Bushell]

Public bug reported:

upgrade from 16.04 to 18.04 identified this bug during the installation
process. Reported an unstable installation.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic i686
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: i386
Date: Mon Oct  8 10:16:43 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2013-07-19 (1907 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package bionic i386 third-party-packages

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

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  upgrade from 16.04 to 18.04 identified this bug during the
  installation process. Reported an unstable installation.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  Date: Mon Oct  8 10:16:43 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-07-19 (1907 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796707/+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 1796512] [NEW] systemd starting CIFS before wireless network avaiblale

[Rob Peters]

Public bug reported:

Trying to get a wireless laptop to mount a CIFS drive at boot time.
However, keep getting error below. It appears that the attempt at
mounting the CIFS drive is taking place before the wireless network
comes online. However, I have the _netdev specified on the mount which
should delay the mount. Yes, I can create a shell script to mount the
drive but… Not sure if this is a core Ubuntu thing or you guys.

fstab entry
//192.168.1.205/janice /samba cifs 
credentials=/var/credentials,uid=1000,gid=1000,_netdev,vers=1.0 0 0

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: systemd 239-7ubuntu9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Sat Oct  6 12:25:03 2018
InstallationDate: Installed on 2018-09-13 (22 days ago)
InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180912)
MachineType: LENOVO 20BXCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=a633cba7-e6d5-4a7d-929e-211ddd2d5eee ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET71WW (1.35 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET71WW(1.35):bd09/14/2018:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450s
dmi.product.name: 20BXCTO1WW
dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
modified.conffile..etc.systemd.logind.conf: [modified]
mtime.conffile..etc.systemd.logind.conf: 2018-09-19T09:15:50.969847

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


** Tags: amd64 apport-bug cosmic

** Attachment added: "9dfeb8778f88ad7e3c6014cbee10889a966e535d.png"
   
https://bugs.launchpad.net/bugs/1796512/+attachment/5198139/+files/9dfeb8778f88ad7e3c6014cbee10889a966e535d.png

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

Title:
  systemd starting CIFS before wireless network avaiblale

Status in systemd package in Ubuntu:
  New

Bug description:
  Trying to get a wireless laptop to mount a CIFS drive at boot time.
  However, keep getting error below. It appears that the attempt at
  mounting the CIFS drive is taking place before the wireless network
  comes online. However, I have the _netdev specified on the mount which
  should delay the mount. Yes, I can create a shell script to mount the
  drive but… Not sure if this is a core Ubuntu thing or you guys.

  fstab entry
  //192.168.1.205/janice /samba cifs 
credentials=/var/credentials,uid=1000,gid=1000,_netdev,vers=1.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sat Oct  6 12:25:03 2018
  InstallationDate: Installed on 2018-09-13 (22 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180912)
  MachineType: LENOVO 20BXCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=a633cba7-e6d5-4a7d-929e-211ddd2d5eee ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET71WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET71WW(1.35):bd09/14/2018:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.systemd.logind.conf: [modified]
  mtime.conffile..etc.systemd.logind.conf: 2018-09-19T09:15:50.969847

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

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

[Touch-packages] [Bug 1791529] [NEW] package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Rob Bowkett]

Public bug reported:

I was upgrading Lubuntu...

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gconf2 3.2.6-4ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
Uname: Linux 4.4.0-135-generic i686
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: i386
Date: Sun Sep  9 12:44:00 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2018-08-22 (18 days ago)
InstallationMedia: Linux Lite 3.8 - Release i386
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: gconf
Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2018-09-09 (0 days ago)

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


** Tags: apport-package i386 xenial

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

Title:
  package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  I was upgrading Lubuntu...

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gconf2 3.2.6-4ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic i686
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: i386
  Date: Sun Sep  9 12:44:00 2018
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-08-22 (18 days ago)
  InstallationMedia: Linux Lite 3.8 - Release i386
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-4ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to xenial on 2018-09-09 (0 days ago)

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

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

Re: [Touch-packages] [Bug 1063853] Re: CAN'T PRINT OVER NETWORK SINCE LAST UPDATE

[Rob]

Thank you: it is lo longer a problem.

On 10/08/18 08:45, gf wrote:
> Hello Rob,
> Thank you for submitting this bug and reporting a problem with cups.  You 
> made this bug report some time ago and Ubuntu and cups have been updated 
> since then.
>
> Could you confirm that this is no longer a problem and that we can close the 
> ticket?
> If it is still a problem, are you still interested in finding a solution to 
> this bug?
> If you are, could you let us know and, in the current version, could you run 
> the following (only once):
> apport-collect 1063853
> and upload the updated logs and and any other logs that are relevant for this 
> particular issue.
>
> Thank you again for helping make Ubuntu and cups better.
> G
>
> ** Changed in: cups (Ubuntu)
> Status: New => Incomplete
>

--

Robert John Morton <http://robmorton.20m.com/index.htm>

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

Title:
  CAN'T PRINT OVER NETWORK SINCE LAST UPDATE

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  UBUNTU 12.4
  PRINTING PROBLEM (SINCE LAST CUPS UPDATE, I THINK)

  I have 2 computers in a network. I call them neddy and nelly.
  Samba installed and configured on both.
  Neddy has a printer attached. Nelly has not.
  Nelly has always, until recently, been able to print to neddy's printer.
  All configurations are the same as they were whenit all worked.

  Since a recent update, I can only print from nelly to neddy's printer
  as follows:

  Finish work, eg in nelly's word processor then hit the word
  processor's print button.

  [at this point nothing prints. The print job appears in nelly's print queue 
with a message
  saying "processing - printer not connected?" Neddy's printer is connected, 
ready and 
  configured as shared on both neddy and nelly.]

  On rebooting nelly, the job prints on neddy's printer.

  From then on, after the first job has actually been printed, I can print 
normally from 
  applications running in nelly to neddy's printer for as long as both neddy 
and nelly
  remain up (running) - days, weeks. I can even switch the printer on and off 
in between 
  times without and adverse effect. 

  Without rebooting there is no way that I have found to make the print job 
actually print. 
  Restarting CUPS doesn't work. 

  Temporary solution: I ask nelly's user to put a copy of what needs printing 
in her Public folder.
  I then pick it up from there through Samba and print it on neddy.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Mon Oct  8 12:06:30 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Lpstat: device for HP-Deskjet-3538-Color-Inkjet-Printer: 
dnssd://hp%20deskjet%203500%20%40%20neddy._ipp._tcp.local/cups
  MachineType: System manufacturer System Product Name
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic-pae 
root=UUID=180a60a2-7b5c-493c-9f06-fb493bdff0e4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0404
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7H55-M LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0404:bd04/11/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-MLX:rvrX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1063853/+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 1779936] [NEW] mkinitramfs fails on Raspian 9 "Stretch"

[Rob Roschewsk]

Public bug reported:

Atempting to install kdump-tools fails due to error in mkinitramfs:

/usr/sbin/mkinitramfs -v -d /var/lib/kdump/initramfs-tools -o
/var/lib/kdump/initrd.img-4.14.30-v7+.new -4.14.30-v7+

mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools/

Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'

>From traces  it seems it's getting tripped up because the root
device specified in /proc/cmdline is in the form:
root=PARTUUID=6ddc62b3-02

I changed the boot command line to read: root=/dev/mmcblk0p2

and kdump-tools installed correctly.

Attaching output of /proc/mounts and mount for good measure.


root@raspberrypi:/usr/share/initramfs-tools# mount
/dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)
devtmpfs on /dev type devtmpfs 
(rw,relatime,size=470128k,nr_inodes=117532,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup 
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup 
(rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/net_cls type cgroup 
(rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup 
(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/devices type cgroup 
(rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup 
(rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs 
(rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
/dev/mmcblk0p1 on /boot type vfat 
(rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
tmpfs on /run/user/1001 type tmpfs 
(rw,nosuid,nodev,relatime,size=94944k,mode=700,uid=1001,gid=100)

root@raspberrypi:~# cat /proc/mounts
/dev/root / ext4 rw,noatime,data=ordered 0 0
devtmpfs /dev devtmpfs rw,relatime,size=470128k,nr_inodes=117532,mode=755 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup 
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/net_cls cgroup rw,nosuid,nodev,noexec,relatime,net_cls 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs 
rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0
mqueue /dev/mqueue mqueue rw,relatime 0 0
sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
/dev/mmcblk0p1 /boot vfat 
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro
 0 0
tmpfs /run/user/1001 tmpfs 
rw,nosuid,nodev,relatime,size=94944k,mode=700,uid=1001,gid=100 0 0

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  mkinitramfs fails on Raspian 9 "Stretch"

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Atempting to install kdump-tools fails due to error in mkinitramfs:

  /usr/sbin/mkinitramfs -v -d /var/lib/kdump/initramfs-tools -o
  /var/lib/kdump/initrd.img-4.14.30-v7+.new -4.14.30-v7+

  mkinitramfs: failed to determine device for /
  mkinitramfs: workaround is 

[Touch-packages] [Bug 1771733] Re: bluetooth device disappears after several minutes of use

[Rob]

Welp. My mouse has been working for a couple days now and has survived
multiple reboots, but the problem is that I don't know what I did to get
it working again. I just sat down, wiggled the mouse to wake it up out
of habit, and it worked. Could be a hardware issue on my end. Close this
bug I guess. Sorry for the mix up, I really have no idea what happened.

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Re: bluetooth device disappears after several minutes of use

[Rob]

I have executed the command suggested by vanvugt for one week, but to
complicate matters further, I have been able to use my mouse for about
an hour now... I don't know how to troubleshoot this issue, but I will
update if I have any complications from this point forward... I just
replaced the batteries in my mouse, but that doesn't explain the loss of
*ALL* bluetooth hardware functionality until several reboots
later...right? Even with dead mouse batteries, surely my computer should
not report that there is no bluetooth hardware available. Please note
that bluetooth became available again *without* rebooting, I just hadn't
touched anything for several hours.

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  New

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Lspci.txt

[Rob]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1771733/+attachment/5141143/+files/Lspci.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] getfacl.txt

[Rob]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141150/+files/getfacl.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcModules.txt

[Rob]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141148/+files/ProcModules.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] UdevDb.txt

[Rob]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1771733/+attachment/5141149/+files/UdevDb.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcCpuinfo.txt

[Rob]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141144/+files/ProcCpuinfo.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcEnviron.txt

[Rob]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141146/+files/ProcEnviron.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcInterrupts.txt

[Rob]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141147/+files/ProcInterrupts.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] ProcCpuinfoMinimal.txt

[Rob]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141145/+files/ProcCpuinfoMinimal.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Dependencies.txt

[Rob]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141142/+files/Dependencies.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntubudgie/+bug/1771733/+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 1771733] Re: bluetooth device disappears after several minutes of use

[Rob]

apport information

** Tags added: apport-collected bionic

** Description changed:

  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-date.
  
  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after several
  minutes of use, I find that my mouse has disconnected, and I no longer
  have a bluetooth icon in the top right status indicator. Then, when I
  open bluetooth settings, the window reads "No bluetooth found: Plug in a
  dongle to use bluetooth." My laptop has bluetooth built in. It's an Asus
  UX305CA.
  
- This is my first bug report so please let me know if I've left out any
- important details and I will provide them as soon as possible. Thanks
- for all your hard work with Ubuntu Budgie!
+ This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: Budgie:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-05-15 (3 days ago)
+ InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX305CA
+ Package: bluez 5.48-0ubuntu3
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/08/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX305CA.300
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX305CA
+ 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.:bvrUX305CA.300:bd06/08/2016:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: UX
+ dmi.product.name: UX305CA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: 4C:34:88:A3:4C:6E  ACL MTU: 1021:5  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN 
+   RX bytes:1186983 acl:12228 sco:0 events:120531 errors:0
+   TX bytes:99607321 acl:116734 sco:0 commands:1078 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1771733/+attachment/5141141/+files/CurrentDmesg.txt

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

Title:
  bluetooth device disappears after several minutes of use

Status in Ubuntu Budgie:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I am using budgie-desktop 10.4 on ubuntu budgie 18.04, fully up-to-
  date.

  When I open bluetooth settings, I am able to see many different
  bluetooth devices detected by my computer, and I can connect to my
  bluetooth mouse (Microsoft sculpt comfort mouse). However, after
  several minutes of use, I find that my mouse has disconnected, and I
  no longer have a bluetooth icon in the top right status indicator.
  Then, when I open bluetooth settings, the window reads "No bluetooth
  found: Plug in a dongle to use bluetooth." My laptop has bluetooth
  built in. It's an Asus UX305CA.

  This is my first bug report so please let me know if I've left out any 
important details and I will provide them as soon as possible. Thanks for all 
your hard work with Ubuntu Budgie!
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-15 (3 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  

[Touch-packages] [Bug 1756511] [NEW] Xorg freezes on bionic kernel 4.15.0-12

[Rob Ludwick]

Public bug reported:

Similar thing that happens here:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839

The difference is that I can't log in.  So it dies before it asks me to
login.

The workaround is to boot into an old kernel.

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

** Description changed:

- Same thing that happens here:
+ I have a Dell XPS 15 9650, and it freezes with the latest kernel for
+ bionic.
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
  
- And freezes in exactly the same way.
+ The solution is to run a very old kernel.

** Description changed:

- I have a Dell XPS 15 9650, and it freezes with the latest kernel for
- bionic.
+ Similar thing that happens here:
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
- 
- The solution is to run a very old kernel.

** Description changed:

  Similar thing that happens here:
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
+ 
+ The difference is that I can't log in.  So it dies before it asks me to
+ login.

** Description changed:

  Similar thing that happens here:
  
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839
  
  The difference is that I can't log in.  So it dies before it asks me to
  login.
+ 
+ The workaround is to boot into an old kernel.

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

Title:
  Xorg freezes on bionic kernel 4.15.0-12

Status in xorg package in Ubuntu:
  New

Bug description:
  Similar thing that happens here:

  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839

  The difference is that I can't log in.  So it dies before it asks me
  to login.

  The workaround is to boot into an old kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1756511/+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 1746015] Re: Apt and apt-get do not ship a us_EN language catalog

[Rob A]

C is not a language

** Attachment added: "c-not-a-language.png"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+attachment/5045192/+files/c-not-a-language.png

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

Title:
  Apt and apt-get do not ship a us_EN language catalog

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 17.10
  Release:17.10

  If you install anthy with additional languages, with "US English" as
  your primary language, you end up with a "locale" output similar to
  the following:

  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US:de:ja
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_GB.UTF-8
  LC_TIME=en_GB.UTF-8
  LC_COLLATE=C
  LC_MONETARY=en_US.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT=en_US.UTF-8
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=

  The LANGUAGE variable in this case is using the rules from
  https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-
  variable.html

  When running "aptitude" or "apt-get" or "apt install", the messages
  that come back are in German.  If you strace those commands, you'll
  see apt trying to search for an en_US or en catalog, finding none, and
  falling down to the 2nd language in the list: "de" or German.

  If you run:
  $ LANGUAGE="" apt-get update

  Then the messages come back in English, because the system's fallen
  back to the "C" locale.

  apt should also properly ship an en_US language catalog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Jan 29 08:31:38 2018
  InstallationDate: Installed on 2017-04-27 (276 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1746015] Re: Apt and apt-get do not ship a us_EN language catalog

[Rob A]

While that may be a precise and accurate statement, I believe it is the
wrong answer.

$ LANGUAGE=en_US:de:ja apt install vim
E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: 
Permission denied)
E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, 
sind Sie root?
$ LANGUAGE=invalid:de:ja apt install vim
E: Sperrdatei /var/lib/dpkg/lock konnte nicht geöffnet werden. - open (13: 
Permission denied)
E: Sperren des Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, 
sind Sie root?
$ LANGUAGE="" apt install vim
E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied)
E: Unable to lock the administration directory (/var/lib/dpkg/), are you root?

C is the *fallback* language, not the primary.  Therefore, even though
the user has requested English, and English is available in "C", the
user is not receiving English.

Besides: "C" isn't even a valid language (see screenshot).

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

Title:
  Apt and apt-get do not ship a us_EN language catalog

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Description:Ubuntu 17.10
  Release:17.10

  If you install anthy with additional languages, with "US English" as
  your primary language, you end up with a "locale" output similar to
  the following:

  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US:de:ja
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_GB.UTF-8
  LC_TIME=en_GB.UTF-8
  LC_COLLATE=C
  LC_MONETARY=en_US.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT=en_US.UTF-8
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=

  The LANGUAGE variable in this case is using the rules from
  https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-
  variable.html

  When running "aptitude" or "apt-get" or "apt install", the messages
  that come back are in German.  If you strace those commands, you'll
  see apt trying to search for an en_US or en catalog, finding none, and
  falling down to the 2nd language in the list: "de" or German.

  If you run:
  $ LANGUAGE="" apt-get update

  Then the messages come back in English, because the system's fallen
  back to the "C" locale.

  apt should also properly ship an en_US language catalog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Jan 29 08:31:38 2018
  InstallationDate: Installed on 2017-04-27 (276 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1746015] [NEW] Apt and apt-get do not ship a us_EN language catalog

[Rob A]

Public bug reported:

Description:Ubuntu 17.10
Release:17.10

If you install anthy with additional languages, with "US English" as
your primary language, you end up with a "locale" output similar to the
following:

$ locale
LANG=en_US.UTF-8
LANGUAGE=en_US:de:ja
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
LC_COLLATE=C
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

The LANGUAGE variable in this case is using the rules from
https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-
variable.html

When running "aptitude" or "apt-get" or "apt install", the messages that
come back are in German.  If you strace those commands, you'll see apt
trying to search for an en_US or en catalog, finding none, and falling
down to the 2nd language in the list: "de" or German.

If you run:
$ LANGUAGE="" apt-get update

Then the messages come back in English, because the system's fallen back
to the "C" locale.

apt should also properly ship an en_US language catalog.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apt 1.5.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Jan 29 08:31:38 2018
InstallationDate: Installed on 2017-04-27 (276 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: apt
UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Apt and apt-get do not ship a us_EN language catalog

Status in apt package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 17.10
  Release:17.10

  If you install anthy with additional languages, with "US English" as
  your primary language, you end up with a "locale" output similar to
  the following:

  $ locale
  LANG=en_US.UTF-8
  LANGUAGE=en_US:de:ja
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=en_GB.UTF-8
  LC_TIME=en_GB.UTF-8
  LC_COLLATE=C
  LC_MONETARY=en_US.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER="en_US.UTF-8"
  LC_NAME="en_US.UTF-8"
  LC_ADDRESS="en_US.UTF-8"
  LC_TELEPHONE="en_US.UTF-8"
  LC_MEASUREMENT=en_US.UTF-8
  LC_IDENTIFICATION="en_US.UTF-8"
  LC_ALL=

  The LANGUAGE variable in this case is using the rules from
  https://www.gnu.org/software/gettext/manual/html_node/The-LANGUAGE-
  variable.html

  When running "aptitude" or "apt-get" or "apt install", the messages
  that come back are in German.  If you strace those commands, you'll
  see apt trying to search for an en_US or en catalog, finding none, and
  falling down to the 2nd language in the list: "de" or German.

  If you run:
  $ LANGUAGE="" apt-get update

  Then the messages come back in English, because the system's fallen
  back to the "C" locale.

  apt should also properly ship an en_US language catalog.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apt 1.5.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Jan 29 08:31:38 2018
  InstallationDate: Installed on 2017-04-27 (276 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: apt
  UpgradeStatus: Upgraded to artful on 2018-01-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1746015/+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 1714839] Re: Xorg freezes on zesty default 4.10 kernel

[Rob Ludwick]

Still happening with the latest 4.10 kernel.  Dell XPS 15 9560

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+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 1727237] Re: systemd-resolved is not finding a domain

[Rob Schultz]

The issue is with systemd-resolvd not adding the captive portal DNS
after the logon. This worked fine with dnsmasq in 16.04 (and I assume
17.04).

For my laptop I have currently changed to 'unbound' for DNS resolution.
Note: If you are running Qemu/KVM you will want to keep dnsmasq-base
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/1727237

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

[Rob Schultz]

Interesting. I installed 17.10 and Bluetooth worked so much better than it had 
with 16.04 (I had basically given up using it).
Then I re-installed to eliminate any of my changes as a contributor to a 
different issue and now Bluetooth stutters again.

I've commented on bug 88827, but not sure where this goes from here.
Bluetooth may seem like an nice-to-have item, but I use it daily.

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1714839] Re: Xorg freezes on zesty default 4.10 kernel

[Rob Ludwick]

** Attachment added: "Kernel log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+attachment/4943840/+files/kern.log

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+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 1714839] Re: Xorg freezes on zesty default 4.10 kernel

[Rob Ludwick]

Workaround is to boot into the old 4.8 kernel.

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+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 1714839] [NEW] Xorg freezes on zesty default 4.10 kernel

[Rob Ludwick]

Public bug reported:

When running the 4.10 kernel I get the following errors an a X lockup
when trying to login as a user.

kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Sep  3 18:33:15 2017
DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
   Subsystem: Dell Device [1028:07be]
InstallationDate: Installed on 2017-03-09 (178 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
MachineType: Dell Inc. XPS 15 9560
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
dmi.bios.date: 01/09/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.3
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1

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


** Tags: 4.10 amd64 apport-bug freeze ubuntu 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/1714839

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1699086] [NEW] add-apt-repository crashes on non-ascii names in PGP keys

[Rob Lazzurs]

Public bug reported:

When adding the PHP 7.1 repo into Ubuntu 16.04 LTS I get the following
error.

Command;
add-apt-repository ppa:ondrej/php -y

Output;
gpg: keyring `/tmp/tmprs_t5_d6/secring.gpg' created
gpg: keyring `/tmp/tmprs_t5_d6/pubring.gpg' created
gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
gpg: /tmp/tmprs_t5_d6/trustdb.gpg: trustdb created
gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur�" imported
gpg: Total number processed: 1
gpg:   imported: 1  (RSA: 1)
'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128)

The command exits with code 1.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  add-apt-repository crashes on non-ascii names in PGP keys

Status in software-properties package in Ubuntu:
  New

Bug description:
  When adding the PHP 7.1 repo into Ubuntu 16.04 LTS I get the following
  error.

  Command;
  add-apt-repository ppa:ondrej/php -y

  Output;
  gpg: keyring `/tmp/tmprs_t5_d6/secring.gpg' created
  gpg: keyring `/tmp/tmprs_t5_d6/pubring.gpg' created
  gpg: requesting key E5267A6C from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmprs_t5_d6/trustdb.gpg: trustdb created
  gpg: key E5267A6C: public key "Launchpad PPA for Ond\xc5\x99ej Sur�" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  'ascii' codec can't decode byte 0xc5 in position 92: ordinal not in range(128)

  The command exits with code 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1699086/+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 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)

[Rob Glenn]

I just completed a fresh install of Ubuntu 16.04 with a brand new Asus
Xonar DGX.  I can confirm the bug exists and also that the alsamixer
workaround is sticky across reboots.  While the current workaround is
much better than nothing, I' d like a way to have sound on both speakers
and headphones at once, the alsamixer solution appears to offer a one-
or-the-other switch but not both.  Anyone figure out a solution for
this?

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

Title:
  No sound on ASUS Xonar DGX Soundcard (16.04)

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Hello,
  On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), 
Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. 
Tested with the app to test speakers, Firefox, VLC, and checked with 
pavucontrol, the progress bar indicate that a sound is played on the card, but 
no sound on the speakers.

  I report this bug because it works on the same version with the
  integrated card of my motherboard. (ASUS H87-PLUS)

  On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all
  defaults params)

  The speakers connected are the Logitech Z9600 (by 3 jacks), and I
  precise that they are correctly plugged in, etc..., it works when I
  connect it to the integrated sound card of my motherboard (and if I
  use Ubuntu 14.04 LTS)

  I don't know if it's a normal development bug, but in doubt I report it.
  Thank you,
  Valentin Crône

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1551385/+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 1661564] [NEW] package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

[Rob Moore]

Public bug reported:

I got the error notifications in the time between my password being
confirmed and the icons/desktop loading onto the screen, ie when the
screen contained only the background image.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.8
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
AptOrdering:
 libgnutls-openssl27: Install
 libgnutls30: Install
 ntfs-3g: Install
 libxpm4: Install
 l
Architecture: amd64
Date: Fri Feb  3 01:16:51 2017
DuplicateSignature:
 package:initramfs-tools:0.122ubuntu8.8
 Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
 update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
 dpkg: error processing package initramfs-tools (--configure):
  subprocess installed post-installation script was killed by signal 
(Terminated)
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
InstallationDate: Installed on 2016-10-19 (107 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade:
  subprocess installed post-installation script was killed by signal
  (Terminated)

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I got the error notifications in the time between my password being
  confirmed and the icons/desktop loading onto the screen, ie when the
  screen contained only the background image.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  AptOrdering:
   libgnutls-openssl27: Install
   libgnutls30: Install
   ntfs-3g: Install
   libxpm4: Install
   l
  Architecture: amd64
  Date: Fri Feb  3 01:16:51 2017
  DuplicateSignature:
   package:initramfs-tools:0.122ubuntu8.8
   Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
   update-initramfs: Generating /boot/initrd.img-4.4.0-62-generic
   dpkg: error processing package initramfs-tools (--configure):
subprocess installed post-installation script was killed by signal 
(Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2016-10-19 (107 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661564/+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 1577596] Re: ntpd not started when using ntpdate

[Rob X]

Hi,

there is a much easier solution.
"/etc/network/if-up.d/ntpdate" use "/usr/sbin/ntpdate-debian" which read the 
configfile "/etc/default/ntpdate" (man ntpdate-debian). If you modify 
/etc/default/ntpdate with NTPOPTIONS="-u" then "/usr/sbin/ntpdate-debian" use 
an unpriviledge port (>1023) if ifup is running and don't block port udp/123 at 
the start of ntpd.

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

Title:
  ntpd not started when using ntpdate

Status in init-system-helpers package in Ubuntu:
  Confirmed
Status in ntp package in Ubuntu:
  Won't Fix

Bug description:
  After updating from 14.04 to 16.04 on a number of my systems, ntpd no
  longer starts at boot on any of those systems.

  `systemctl status ntp` shows:
 ntp.service - LSB: Start NTP daemon
 Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
 Active: inactive (dead)
   Docs: man:systemd-sysv-generator(8)
  May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon.
  May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon.

  Manually starting it using `systemctl start ntp` works fine.  However,
  systemd does not seem to want to start it automatically at boot time.


  As best as I can tell based on trial and error, there is something
  special about the combination of the service being named "ntp.service"
  and the service depending on network.target.  However, I haven't been
  able to identify exactly what is causing this.

  If I copy the init script to any other name, everything works fine:
  cp /etc/init.d/ntp /etc/init.d/ntpd
  Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd"
  systemctl enable ntpd
  # After a reboot, ntpd.service is started, but ntp.service is not.

  If I remove "$network" from the "# Required-Start: $network $remote_fs
  $syslog" line in /etc/init.d/ntp, then systemd starts it automatically
  ... But of course it is started before the network comes up, so it
  fails.

  If I replace /etc/init.d/ntp with a file containing only the following, 
systemd won't try to start it automatically at boot:
  #!/bin/sh
  ### BEGIN INIT INFO
  # Provides: ntp
  # Required-Start: $network
  # Required-Stop: $network
  # Default-Start: 2 3 4 5
  # Default-Stop: 1
  # Short-Description: Start NTP daemon
  ### END INIT INFO
  echo "script was run" >> /ntp.log

  If I rename that same dummy script to /etc/init.d/ntp2, it is started
  automatically at boot.

  However, grepping the systemd source code and my systemd config files for ntp 
doesn't seem to find anything that might cause this behavior:
  /etc/systemd# grep -iR ntp *
  timesyncd.conf:#NTP=
  timesyncd.conf:#FallbackNTP=ntp.ubuntu.com
  /lib/systemd# grep -R ntp *
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd
  
system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd
  Binary file systemd-networkd matches
  Binary file systemd-timedated matches
  Binary file systemd-timesyncd matches

  What else can I do to debug this further?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

[Rob Ward]

I am running 16.04 LTS on a MacBook Pro and it is dropping the nm-applet
icon after a resume.  I have a suspicion that it was reliable until I
created a second user on the computer.  Then it would appear for one
person and not the other, and when produced in the other it disappeared
from the previous user. I thought I had it solved but then when I left
it a while and it had to wake up and resume the Icon was gone again.  I
have a suspicion that permissions are involved, the setup for nm-applet
appears to be written for only one user to access it?? The rest should
just accept it?  At least I have it reliably beginning on a cold boot
for either user or swap of user, but not resume apparently. I think my
attempts (successful to some degree) have only been superficial and not
getting at the heart of matter.

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

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Fix Released
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Won't Fix
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /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/1422143/+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 1633291] [NEW] package click-apparmor 0.3.17 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Rob Moore]

Public bug reported:

This occurred as part of an upgrade to 16.10.

It was part of a number of failed upgrades:

Errors were encountered while processing:
 click
 click-apparmor
 url-dispatcher:amd64
 ubuntu-app-launch
 ubuntu-system-settings
 url-dispatcher-tools
 ubuntu-app-launch-tools
 libunity-scopes1.0:amd64
 ubuntu-system-settings-online-accounts
 unity8
 account-plugin-ubuntuone
 unity-plugin-scopes:amd64
 unity-greeter-session-broadcast
 unity8-desktop-session
 ubuntu-push-client
 unity-scope-click
 account-plugin-facebook
 pay-service
 unity8-common
 unity8-private:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: click-apparmor 0.3.17
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8
AptOrdering:
 ubuntu-release-upgrader-gtk:amd64: Install
 ubuntu-release-upgrader-core:amd64: Install
 python3-distupgrade:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Oct 13 20:54:48 2016
DuplicateSignature:
 package:click-apparmor:0.3.17
 Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package click (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-10 (186 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: click-apparmor
Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package click-apparmor 0.3.17 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  This occurred as part of an upgrade to 16.10.

  It was part of a number of failed upgrades:

  Errors were encountered while processing:
   click
   click-apparmor
   url-dispatcher:amd64
   ubuntu-app-launch
   ubuntu-system-settings
   url-dispatcher-tools
   ubuntu-app-launch-tools
   libunity-scopes1.0:amd64
   ubuntu-system-settings-online-accounts
   unity8
   account-plugin-ubuntuone
   unity-plugin-scopes:amd64
   unity-greeter-session-broadcast
   unity8-desktop-session
   ubuntu-push-client
   unity-scope-click
   account-plugin-facebook
   pay-service
   unity8-common
   unity8-private:amd64
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click-apparmor 0.3.17
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  AptOrdering:
   ubuntu-release-upgrader-gtk:amd64: Install
   ubuntu-release-upgrader-core:amd64: Install
   python3-distupgrade:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Oct 13 20:54:48 2016
  DuplicateSignature:
   package:click-apparmor:0.3.17
   Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package click (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-10 (186 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.3.17 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1633291/+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 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)

[rob cain]

I had exactly the same problem (ubuntu 16.04 latest). Just started
happenning, no apparent cause or changes beforehand.

Tried all the usual suggestions: eg:

a) rm -r ~/.config/pulse; pulseaudio -k - reboot
b) Open VLC,Go to Preferences,then to Sound,click in the reset preferences 
button,Close VLC
c) sudo alsa force-reload
d) alsamixer - auto-mute - disable

- worked for a little while,but then came back again.

Just done Anthony's workaround above (#18) - & so far it has worked
(thanks Anthony). just have to remember how to re-enable it agan
whenever i want to use headphones in future.

Seem to recall this same/similar problem plagued users on Ubuntu 12.04
for a while.

We seem to be going backwards a little with 16.04. Looking forward to a
fix.

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

Title:
  Volume notification keeps popping up constantly(the notifyosd bubble
  on top-right corner)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
  preserving the home directory which is mounted in a separate
  partition. Even during the installation I had constant volume
  notification bubble appearing on the top-right corner of my screen, it
  would come and go about twice every minute. I just thought it was due
  to installing hardware drivers or something but the problem persisted
  even when I booted into the freshly installed system. I did some
  searching and two users reported the exact problem. And one more
  suggested this happens because constant disconnect and reconnect of
  the sound card which makes sense as the sound settings flashes briefly
  during every popup. Someone on IRC suggested to kill pulseaudio and
  thus restart it, that does not fix the issue. I also tried the Live
  environment thinking it might be due to some old config files in home
  partition (which was preserved during upgrade), but this problem
  happens in the live environment as well, which makes sense because it
  was present during installation as well.

  Users with the same issue:
  http://ubuntuforums.org/showthread.php?t=2323815
  http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04
  
http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  sidd   1651 F pulseaudio
   /dev/snd/controlC0:  sidd   1651 F pulseaudio
   /dev/snd/controlC1:  sidd   1651 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 12:31:12 2016
  InstallationDate: Installed on 2016-05-23 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0705
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 EVO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1594634] Re: ZFS on iscsi target fails at boot/shutdown

[Rob]

** Package changed: systemd (Ubuntu) => zfs

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

Title:
  ZFS on iscsi target fails at boot/shutdown

Status in Native ZFS for Linux:
  New

Bug description:
  I've got a ZFS volume on an ISCSI target, once the system boots I can
  bring it online.

  My ISCSI target shows up as:

  root@test:/home/rob# lsblk
  NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
  sda  8:00  8.1T  0 disk

  root@test:/home/rob# zpool status
pool: data2
   state: ONLINE
scan: none requested
  config:

NAMESTATE READ WRITE CKSUM
data2   ONLINE   0 0 0
  sda   ONLINE   0 0 0

  errors: No known data errors

  root@test:/home/rob# df -h
  Filesystem  Size  Used Avail Use% Mounted on
  --- snip --
  data2   3.1T 0  3.1T   0% /data2
  data2/backup3.2T  165G  3.1T   6% /data2/backup
  data2/test 7.7T  4.7T  3.1T  61% /data2/test


  However in the case of a system shutdown/reboot the system tries to
  unmount the disk after the network has been brought down which
  obviously fails.

  When booting the system the zpool never gets imported as the 'zfs-
  import-cache.service' runs before the iscsi target is initiated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/1594634/+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 1576747] Re: Network manager applet unable to control wifi after suspend in 16.04

[Rob Frohne]

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

I find that I can:

$ killall nm-applet && nm-applet&

and it is back working.  I haven't been successful getting that to work
in a script upon resume yet though.

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

Title:
  Network manager applet unable to control wifi after suspend in 16.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After resume from suspend network manager no longer allows me to
  control my wifi card, view available wireless networks, or select new
  ones.  Oddly enough, I'm still able to communicate on the network that
  I was connected to prior to suspend.

  Running
  # sudo service network-manager restart
  resolves the issue until the next suspend/resume.

  I'll copy what I think is the relevant  portion of syslog below
  __
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
wake requested (sleeping: yes  enabled: yes)
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4971] manager: 
waking up...
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.4972] device 
(enp0s31f6): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 
37]
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19059]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19059]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Started Run anacron jobs.
  Apr 29 09:04:20 x1 systemd[1]: Reloading Laptop Mode Tools.
  Apr 29 09:04:20 x1 anacron[19143]: Anacron 2.3 started on 2016-04-29
  Apr 29 09:04:20 x1 anacron[19143]: Will run job `cron.daily' in 5 min.
  Apr 29 09:04:20 x1 anacron[19143]: Jobs will be executed sequentially
  Apr 29 09:04:20 x1 laptop-mode: Laptop mode
  Apr 29 09:04:20 x1 laptop_mode[19145]: Laptop mode
  Apr 29 09:04:20 x1 laptop-mode: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 laptop_mode[19145]: enabled, not active [unchanged]
  Apr 29 09:04:20 x1 systemd[1]: Reloaded Laptop Mode Tools.
  Apr 29 09:04:20 x1 kernel: [180451.937599] e1000e: enp0s31f6 NIC Link is Down
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.5997] device 
(wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180451.940588] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180451.941150] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.942063] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180451.943308] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 kernel: [180452.080430] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.080804] iwlwifi :04:00.0: L1 Enabled - 
LTR Enabled
  Apr 29 09:04:20 x1 kernel: [180452.081573] iwlwifi :04:00.0: can't access 
the RSA semaphore it is write protected
  Apr 29 09:04:20 x1 NetworkManager[849]:   [1461938660.8179] device 
(enp0s31f6): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  Apr 29 09:04:20 x1 kernel: [180452.157407] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:20 x1 kernel: [180452.158711] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.364579] IPv6: ADDRCONF(NETDEV_UP): 
enp0s31f6: link is not ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.0266] manager: 
NetworkManager state is now CONNECTED_LOCAL
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: dbus: Failed to construct signal
  Apr 29 09:04:21 x1 wpa_supplicant[1102]: Could not read interface 
p2p-dev-wlp4s0 flags: No such device
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): supplicant interface state: starting -> ready
  Apr 29 09:04:21 x1 NetworkManager[849]:   [1461938661.1095] device 
(wlp4s0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
  Apr 29 09:04:21 x1 kernel: [180452.450294] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: 
link is not ready
  Apr 29 09:04:21 x1 kernel: [180452.551779] [drm] RC6 on
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1646] device 
(wlp4s0): supplicant interface state: ready -> inactive
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1678] policy: 
auto-activating connection 'chiluks-5g 1'
  Apr 29 09:04:24 x1 NetworkManager[849]:   [1461938664.1688] device 
(wlp4s0): Activation: starting connection 'chiluks-5g 1' 
(8c69564c-5b6f-4ab4-8e6e-ee3157160892)
  

[Touch-packages] [Bug 1612739] [NEW] Software-Properties-gtk Won't open

[Rob]

Public bug reported:

robert@robert-K56CA:~$ software-properties-gtk
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
 PyGIWarning: Gdk was imported without specifying a version first. Use 
gi.require_version('Gdk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import GObject, Gdk, Gtk, Gio, GLib
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
 PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
  from gi.repository import GObject, Gdk, Gtk, Gio, GLib

(software-properties-gtk:28953): Gtk-WARNING **: Theme directory  of
theme oxygen has no size field

Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 101, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 172, in __init__
self.show_keys()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 867, in show_keys
for key in self.apt_key.list():
  File "/usr/lib/python3/dist-packages/softwareproperties/AptAuth.py", line 78, 
in list
for line in p:
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xdf in position 3914: 
invalid continuation byte
robert@robert-K56CA:~$

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Software-Properties-gtk Won't open

Status in software-properties package in Ubuntu:
  New

Bug description:
  robert@robert-K56CA:~$ software-properties-gtk
  
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
 PyGIWarning: Gdk was imported without specifying a version first. Use 
gi.require_version('Gdk', '3.0') before import to ensure that the right version 
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib
  
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py:40:
 PyGIWarning: Gtk was imported without specifying a version first. Use 
gi.require_version('Gtk', '3.0') before import to ensure that the right version 
gets loaded.
from gi.repository import GObject, Gdk, Gtk, Gio, GLib

  (software-properties-gtk:28953): Gtk-WARNING **: Theme directory  of
  theme oxygen has no size field

  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 101, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 172, in __init__
  self.show_keys()
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 867, in show_keys
  for key in self.apt_key.list():
File "/usr/lib/python3/dist-packages/softwareproperties/AptAuth.py", line 
78, in list
  for line in p:
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xdf in position 3914: 
invalid continuation byte
  robert@robert-K56CA:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1612739/+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 1442169] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Rob]

** Information type changed from Public to Public Security

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

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Error: [Errno 2] File o directory non esistente: 
'/proc/version_signature'
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CupsErrorLog: W [09/Apr/2015:15:58:06 +0200] CreateProfile failed: 
org.freedesktop.DBus.Error.NoReply:Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
  Date: Sat Apr  4 11:48:06 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2014-10-23 (167 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat:
   device for Canon-LBP-5975: socket://192.168.1.130
   device for EPSON-Epson-Stylus-Photo-P50: 
usb://EPSON/Stylus%20Photo%20P50?serial=4C43514B3031353929
  MachineType: System manufacturer System Product Name
  Papersize: a4
  PpdFiles:
   EPSON-Epson-Stylus-Photo-P50: Epson Stylus Photo P50 - CUPS+Gutenprint 
v5.2.10
   Canon-LBP-5975: Canon LBP-3460 Foomatic/pxlmono (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=it_IT.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=f78cce14-d9a3-4ce7-a8b3-ec55d7448ce8 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7fca89173984 : cmpq   
$0x0,(%rdi)
   PC (0x7fca89173984) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to vivid on 2015-03-31 (8 days ago)
  UserGroups:
   
  dmi.bios.date: 05/15/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0307
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H61-M LX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0307:bd05/15/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

Re: [Touch-packages] [Bug 1444688] Re: WLAN to 3G connection does not connect automatically

[Rob Cec]

It is solved.

Many thanks
Br
Robcec

Am 02.08.2016 11:26 schrieb "flohack" :

> Is this still an issue? For me this works I would say...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1444688
>
> Title:
>   WLAN to 3G connection does not connect automatically
>
> Status in indicator-network package in Ubuntu:
>   Confirmed
>
> Bug description:
>   when a WLAN connection interrupts, the 3G connection has not the
>   ability to connect automatically. on the other hand as soon as the
>   smartphone recognize a WLAN the smartphone will connect to it.
>
>   Ubuntu 14.10 (r20)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1444688/+subscriptions
>

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

Title:
  WLAN to 3G connection does not connect automatically

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  when a WLAN connection interrupts, the 3G connection has not the
  ability to connect automatically. on the other hand as soon as the
  smartphone recognize a WLAN the smartphone will connect to it.

  Ubuntu 14.10 (r20)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1444688/+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 1312051] Re: Upstart init process consuming all ram

[Rob Teszka]

I have been getting this bug repeatedly on 16.04 LTS. After about say 2
hours of uptime everything is extremely slow and unresponsive, even just
editing text files. I have to log into a different console with
ctrl+alt+f1 to do anything. According to top, upstart is using about
100% CPU and around 40% memory. It's intermittent, only happens about
every 4-5 reboots or so, but boy is it annoying. Any suggestions? Any
logs I can post to help diagnose?

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

Title:
  Upstart init process consuming all ram

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 14.04 amd64  Upstart init process keeps growing in ram. 
  It's about 0.1 MiB every 10s.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 24 10:33:58 2014
  InstallationDate: Installed on 2011-09-05 (961 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/hostname-root ro quiet splash zswap.enabled=1 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-02-07 (75 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: 
'/etc/at.deny']
  modified.conffile..etc.dconf.db.gdm: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.iscsi.iscsid.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-12-20T12:14:24.844783
  mtime.conffile..etc.dconf.db.gdm: 2014-02-21T11:46:26.072553
  mtime.conffile..etc.default.cups: 2014-03-11T16:01:34.805892
  mtime.conffile..etc.default.whoopsie: 2013-10-23T11:36:50.678661
  mtime.conffile..etc.iscsi.iscsid.conf: 2013-07-10T17:05:34.637955

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1312051/+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 1583246] Re: System freezes after returning from locked screen

[Rob Moore]

I experienced this issue (or something similar) yesterday. I used the
alt-sysrq-1 and alt-sysrq-t combo mentioned in the document linked to in
the last comment and after sometime the machine started responding
again. I captured the kern.log and will attach it here in case it's
useful.

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1583246/+attachment/4697121/+files/kern.log

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

Title:
  System freezes after returning from locked screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Quite frequently when I lock my screen (or it locks itself) and I
  unlock it the system is responsive for a few seconds but then
  completely freezes. I can't reboot but have to turn off the power on
  the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May 18 11:24:59 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2016-04-10 (37 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1583246/+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 1580444] Re: Can't plug in USB audio device "TEAC AI-101 Audio"

[rob]

I have the same problem on Ubuntu 16.04

My ChromeOS device running itss own flavor of Linux has not problem
using the device.

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

Title:
  Can't plug in USB audio device "TEAC AI-101 Audio"

Status in alsa-lib package in Ubuntu:
  New

Bug description:
  I can't use this device; it shows up in dmesg, but it seems that
  systemd hangs when trying to use udev to configure it. The important
  message (I think) is:

  usb 3-1: 13:0: cannot get min/max values for control 2 (id 13)

  AND, here is from syslog:
  May 10 23:46:59 dude systemd-udevd[302]: worker [5911] terminated by signal 9 
(Killed)
  May 10 23:46:59 dude systemd-udevd[302]: worker [5911] failed while handling 
'/devices/pci:00/:00:1a.0/usb3/3-1/3-1:1.0/sound/card3/controlC3'
  May 10 23:47:19 dude kernel: [114738.341243] usb 3-1: 13:0: cannot get 
min/max values for control 2 (id 13)

  ...

  I tried to use alsactl to force an init of this card; the very long
  log is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libasound2 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Wed May 11 00:11:40 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libasound2-data 1.1.0-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  InstallationDate: Installed on 2015-05-28 (348 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-lib
  UpgradeStatus: Upgraded to xenial on 2016-05-09 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1580444/+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 1581560] Re: system crash when attaching external display

[Rob Latham]

The 'bios-outdated-1.13' tag confuses me.

It's true that I am running  (dmidecode says...) Vendor: LENOVO Version:
N14ET29W (1.07 )

but there is no mention of display fixes in the release notes that
accompany n14ur12w (1.13).

I can update my bios but wanted to understand if the tag addition was
for fixing a known issue or was something I should try to see if it
helps.

As a reminder, Ubuntu-15.10 handled this display fine with the same bios
version.

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

Title:
  system crash when attaching external display

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
  and reboots when I attach an external display.

  Process: 
  -  put laptop to sleep.
  - come into work the next day
  - open up laptop
  - plug in external display
  - observe bug

  Expected behavior: I can attach the external display
  Observed behavior: system shows black screen on both laptop and display and 
after a minute or two reboots.  Laptop drives external display fine after 
reboot.

  I ssh to the laptop from another machine and monitored
  /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors.  All I
  see in those files before the lockup is this, from Xorg.0.log:

  [ 34289.447] (II) intel(0): Enabled output DP1-8
  [ 34289.448] (II) intel(0): Enabled output DP1-1
  [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440
  [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 
0,
  (0, 0), rotation normal, reflection none

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 09:24:07 2016
  DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2015-09-10 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BS0031US
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BS0031US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BS0031US
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  drirc:
   
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri May 13 09:04:56 2016
  xserver.configfile: default
  xserver.errors:
   
  

[Touch-packages] [Bug 1581560] Re: system crash when attaching external display

[Rob Latham]

I tried an upstream kernel ( 4.4.12-040412-generic #201606011712 ).
Attaching after suspend/resume no longer results in a crash.

The screen frequently fails to restore on the first try.  dmesg has
these lines in that case:

[drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22
[drm] GPU HANG: ecode 8:-1:0x, reason: Kicking stuck wait on blitter 
ring, action: continue
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO 
underrun

But, in an improvement from the Ubuntu kernel, I can unplug and try
again with success.

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

Title:
  system crash when attaching external display

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
  and reboots when I attach an external display.

  Process: 
  -  put laptop to sleep.
  - come into work the next day
  - open up laptop
  - plug in external display
  - observe bug

  Expected behavior: I can attach the external display
  Observed behavior: system shows black screen on both laptop and display and 
after a minute or two reboots.  Laptop drives external display fine after 
reboot.

  I ssh to the laptop from another machine and monitored
  /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors.  All I
  see in those files before the lockup is this, from Xorg.0.log:

  [ 34289.447] (II) intel(0): Enabled output DP1-8
  [ 34289.448] (II) intel(0): Enabled output DP1-1
  [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440
  [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 
0,
  (0, 0), rotation normal, reflection none

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 13 09:24:07 2016
  DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
  InstallationDate: Installed on 2015-09-10 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BS0031US
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago)
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BS0031US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BS0031US
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  drirc:
   
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Touch-packages] [Bug 1594634] [NEW] ZFS on iscsi target fails at boot/shutdown

[Rob]

Public bug reported:

I've got a ZFS volume on an ISCSI target, once the system boots I can
bring it online.

My ISCSI target shows up as:

root@test:/home/rob# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda  8:00  8.1T  0 disk

root@test:/home/rob# zpool status
  pool: data2
 state: ONLINE
  scan: none requested
config:

NAMESTATE READ WRITE CKSUM
data2   ONLINE   0 0 0
  sda   ONLINE   0 0 0

errors: No known data errors

root@test:/home/rob# df -h
Filesystem  Size  Used Avail Use% Mounted on
--- snip --
data2   3.1T 0  3.1T   0% /data2
data2/backup3.2T  165G  3.1T   6% /data2/backup
data2/test 7.7T  4.7T  3.1T  61% /data2/test


However in the case of a system shutdown/reboot the system tries to
unmount the disk after the network has been brought down which obviously
fails.

When booting the system the zpool never gets imported as the 'zfs-
import-cache.service' runs before the iscsi target is initiated.

** 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/1594634

Title:
  ZFS on iscsi target fails at boot/shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  I've got a ZFS volume on an ISCSI target, once the system boots I can
  bring it online.

  My ISCSI target shows up as:

  root@test:/home/rob# lsblk
  NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
  sda  8:00  8.1T  0 disk

  root@test:/home/rob# zpool status
pool: data2
   state: ONLINE
scan: none requested
  config:

NAMESTATE READ WRITE CKSUM
data2   ONLINE   0 0 0
  sda   ONLINE   0 0 0

  errors: No known data errors

  root@test:/home/rob# df -h
  Filesystem  Size  Used Avail Use% Mounted on
  --- snip --
  data2   3.1T 0  3.1T   0% /data2
  data2/backup3.2T  165G  3.1T   6% /data2/backup
  data2/test 7.7T  4.7T  3.1T  61% /data2/test


  However in the case of a system shutdown/reboot the system tries to
  unmount the disk after the network has been brought down which
  obviously fails.

  When booting the system the zpool never gets imported as the 'zfs-
  import-cache.service' runs before the iscsi target is initiated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1594634/+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 1537528] Re: byobu-config segfault with screen backend

[Rob J]

Affects me as well, 5.87-1.

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

Title:
  byobu-config segfault with screen backend

Status in byobu package in Ubuntu:
  In Progress
Status in newt package in Ubuntu:
  Confirmed
Status in byobu package in Debian:
  New

Bug description:
  When running byobu with the screen backend byobu-config segfaults when
  trying to open it by pressing F9.

  Steps to reproduce.

  1. Configure byobu to use screen for the backend
  2. Press F9 to open the configuration menu
  3. The console flashes then returns to your shell window.

  Running byobu-config manually within a byobu screen session shows it's
  segfaulting. It does not crash running it outside of screen.

  byobu:
Installed: 5.101-0ubuntu1~wily
Candidate: 5.101-0ubuntu1~wily
Version table:
   *** 5.101-0ubuntu1~wily 0
  500 http://ppa.launchpad.net/byobu/ppa/ubuntu/ wily/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.97-0ubuntu1 0
  500 http://mirror.us.leaseweb.net/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/byobu/+bug/1537528/+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 1186662] Re: isc-dhcp-server fails to renew lease file

[Rob Traders]

I'm fighting since 14.04 LTS with this lease file issue. The fixes
provided in the release of isc-dhcp-server 4.3.3-5ubuntu12 does not fix
the behaviour in 16.04 LTS (xenial) for me. The reason is the
configuration of apparmaor for the binary /usr/sbin/dhcpd, which prevent
the manipulation of the leases file. I tried to fix the capabilities,
but can't find a solution. The settings "capability dac_override" has no
effect.

Temporary I disabled apparmor interception for isc-dhcpd-server by symlinking 
to disable folder. 
# ln -s /etc/apparmor.d/usr.sbin.dhcpd /etc/apparmor.d/disable/
and restartet the dhcpd. This solves the problem, but it let the dhcpd be 
unprotected by apparmor.

To fix it finaly, please provide a working
/etc/apparmor.d/usr.sbin.dhcpd with the required policy file.

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

Title:
  isc-dhcp-server fails to renew lease file

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Triaged

Bug description:
  After raring upgrade, the dhcp server fails to renew lease file when
  it tries to (about every hour).

  The syslog says:
  dhcpd: Can't create new lease file: Permission denied

  It looks like a permission problem, because

  # chown -R dhcpd:dhcpd /var/lib/dhcp

  the above command temporarily solves the issue, until dhcpd is
  restarted: at that time, the ownership of the directory and the lease
  file is set back to root:root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1581560] Re: system crash when attaching external display

[Rob Latham]

Sometimes, my laptop does not freeze.  Just now I was able to see the
external display upon my second attempt, and found 8 backtraces in
dmesg:

[26529.773617] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed
 to enable link training
[26529.776319] [drm:intel_dp_link_training_channel_equalization [i915]] *ERROR* 
failed to start channel equalization
[26529.778857] [drm:intel_mst_pre_enable_dp [i915]] *ERROR* failed to allocate v
cpi
[26529.845810] [ cut here ]
[26529.845837] WARNING: CPU: 3 PID: 1780 at 
/build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12740 
intel_modeset_check_state+0x5b3/0x8a0 [i915]()
[26529.845838] encoder detached but still enabled on pipe A.
[26529.845839] Modules linked in: cpuid pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm rfcomm bnep binfmt_misc 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media btusb btrtl btbcm btintel bluetooth intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 kvm 
snd_hda_codec_hdmi irqbypass crct10dif_pclmul crc32_pclmul aesni_intel iwlmvm 
aes_x86_64 lrw gf128mul mac80211 glue_helper snd_seq_midi snd_seq_midi_event 
ablk_helper snd_rawmidi cryptd input_leds joydev snd_hda_codec_realtek iwlwifi 
serio_raw snd_hda_codec_generic thinkpad_acpi nvram cfg80211 snd_hda_intel 
intel_pch_thermal snd_hda_codec mei_me snd_hda_core mei lpc_ich snd_hwdep 
snd_pcm shpchp snd_seq snd_seq_device snd_timer snd soundcore
[26529.845870]  mac_hid parport_pc ppdev lp parport autofs4 ses enclosure uas 
usb_storage i915 i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
e1000e sysimgblt ahci fb_sys_fops libahci drm ptp pps_core wmi video fjes
[26529.845882] CPU: 3 PID: 1780 Comm: Xorg Tainted: GW  OE   
4.4.0-22-generic #40-Ubuntu
[26529.845884] Hardware name: LENOVO 20BS0031US/20BS0031US, BIOS N14ET29W (1.07 
) 05/08/2015
[26529.845885]  0286 88216a49 880034c97b08 
813e9c53
[26529.845887]  880034c97b50 c027ca50 880034c97b40 
81080fb2
[26529.845889]  8802443c4318 8800356b1000 8802443c4348 
8802443c4330
[26529.845890] Call Trace:
[26529.845895]  [] dump_stack+0x63/0x90
[26529.845898]  [] warn_slowpath_common+0x82/0xc0
[26529.845899]  [] warn_slowpath_fmt+0x5c/0x80
[26529.845916]  [] intel_modeset_check_state+0x5b3/0x8a0 
[i915]
[26529.845932]  [] intel_atomic_commit+0x4bb/0x6f0 [i915]
[26529.845947]  [] drm_atomic_commit+0x37/0x60 [drm]
[26529.845954]  [] drm_atomic_helper_set_config+0x76/0xb0 
[drm_kms_helper]
[26529.845964]  [] drm_mode_set_config_internal+0x62/0x100 
[drm]
[26529.845974]  [] drm_mode_setcrtc+0x3d2/0x4f0 [drm]
[26529.845981]  [] drm_ioctl+0x152/0x540 [drm]
[26529.845984]  [] ? __set_current_blocked+0x36/0x60
[26529.845992]  [] ? drm_mode_setplane+0x1b0/0x1b0 [drm]
[26529.845995]  [] do_vfs_ioctl+0x29f/0x490
[26529.845997]  [] ? fpu__restore_sig+0x4d/0x60
[26529.845999]  [] SyS_ioctl+0x79/0x90
[26529.846002]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[26529.846004] ---[ end trace 1dc2836a34f42c84 ]---


[26530.067034] [ cut here ]
[26530.067056] WARNING: CPU: 3 PID: 1780 at 
/build/linux-FvcHlK/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12732 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[26530.067057] encoder's enabled state mismatch (expected 1, found 0)
[26530.067057] Modules linked in: cpuid pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm rfcomm bnep binfmt_misc 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core 
v4l2_common videodev media btusb btrtl btbcm btintel bluetooth intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel arc4 kvm 
snd_hda_codec_hdmi irqbypass crct10dif_pclmul crc32_pclmul aesni_intel iwlmvm 
aes_x86_64 lrw gf128mul mac80211 glue_helper snd_seq_midi snd_seq_midi_event 
ablk_helper snd_rawmidi cryptd input_leds joydev snd_hda_codec_realtek iwlwifi 
serio_raw snd_hda_codec_generic thinkpad_acpi nvram cfg80211 snd_hda_intel 
intel_pch_thermal snd_hda_codec mei_me snd_hda_core mei lpc_ich snd_hwdep 
snd_pcm shpchp snd_seq snd_seq_device snd_timer snd soundcore
[26530.067085]  mac_hid parport_pc ppdev lp parport autofs4 ses enclosure uas 
usb_storage i915 i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
e1000e sysimgblt ahci fb_sys_fops libahci drm ptp pps_core wmi video fjes
[26530.067096] CPU: 3 PID: 1780 Comm: Xorg Tainted: GW  OE   
4.4.0-22-generic #40-Ubuntu
[26530.067097] Hardware name: LENOVO 20BS0031US/20BS0031US, BIOS N14ET29W (1.07 
) 05/08/2015
[26530.067098]  0286 88216a49 880034c97b08 
813e9c53
[26530.067100]  880034c97b50 c027ca50 880034c97b40 
81080fb2
[26530.067101]  8802443c4318 880035505b00 8802443c4348 
8802443c4330
[26530.067103] Call Trace:
[26530.067107]  

[Touch-packages] [Bug 1583246] [NEW] System freezes after returning from locked screen

[Rob Moore]

Public bug reported:

Quite frequently when I lock my screen (or it locks itself) and I unlock
it the system is responsive for a few seconds but then completely
freezes. I can't reboot but have to turn off the power on the machine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May 18 11:24:59 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-22-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-21-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-22-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:060d]
   Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
InstallationDate: Installed on 2016-04-10 (37 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
MachineType: Dell Inc. Dell Precision M3800
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: Dell Precision M3800
dmi.board.vendor: Dell Inc.
dmi.board.version: A10
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/17/2015:svnDellInc.:pnDellPrecisionM3800:pvrA10:rvnDellInc.:rnDellPrecisionM3800:rvrA10:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Dell Precision M3800
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  System freezes after returning from locked screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Quite frequently when I lock my screen (or it locks itself) and I
  unlock it the system is responsive for a few seconds but then
  completely freezes. I can't reboot but have to turn off the power on
  the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May 18 

[Touch-packages] [Bug 1581560] [NEW] system crash when attaching external display

[Rob Latham]

Public bug reported:

After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
and reboots when I attach an external display.

Process: 
-  put laptop to sleep.
- come into work the next day
- open up laptop
- plug in external display
- observe bug

Expected behavior: I can attach the external display
Observed behavior: system shows black screen on both laptop and display and 
after a minute or two reboots.  Laptop drives external display fine after 
reboot.

I ssh to the laptop from another machine and monitored /var/log/syslog,
/var/log/Xorg.0.log, and ~/.xsession-errors.  All I see in those files
before the lockup is this, from Xorg.0.log:

[ 34289.447] (II) intel(0): Enabled output DP1-8
[ 34289.448] (II) intel(0): Enabled output DP1-1
[ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440
[ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0,
(0, 0), rotation normal, reflection none

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri May 13 09:24:07 2016
DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed
 virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227]
InstallationDate: Installed on 2015-09-10 (245 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20BS0031US
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago)
dmi.bios.date: 05/08/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N14ET29W (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BS0031US
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BS0031US
dmi.product.version: ThinkPad X1 Carbon 3rd
dmi.sys.vendor: LENOVO
drirc:
 
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri May 13 09:04:56 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4669 
 vendor AUO
xserver.version: 2:1.18.3-1ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  system crash when attaching external display

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes
  and reboots when I attach an external display.

  Process: 
  -  put laptop to sleep.
  - come into work the next day
  - open up laptop
  - plug in external display
  - observe bug

  Expected behavior: I can attach the 

[Touch-packages] [Bug 1576462] [NEW] multiple desktops (3x3), hitting super in an empty desktop does not bring up the dash

[Rob]

Public bug reported:

ubuntu 16.04 upgrade install from 15.10
multiple virtual desktops created in a 3x3 matrix
In an empty virtual desktop, hitting  does not bring up the dash.
If another program is already open in a virtual desktop, then hitting  
dies bring up the dash

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dash 0.5.8-2.1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 28 20:58:28 2016
InstallationDate: Installed on 2015-04-26 (368 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: dash
UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)

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


** Tags: amd64 apport-bug dash xenial

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

Title:
  multiple desktops (3x3), hitting super in an empty desktop does not
  bring up the dash

Status in dash package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 upgrade install from 15.10
  multiple virtual desktops created in a 3x3 matrix
  In an empty virtual desktop, hitting  does not bring up the dash.
  If another program is already open in a virtual desktop, then hitting  
dies bring up the dash

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dash 0.5.8-2.1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 20:58:28 2016
  InstallationDate: Installed on 2015-04-26 (368 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1576462/+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 1573786] [NEW] gdb Process record does not support instruction 0xc5

[Rob Latham]

Public bug reported:

the 'process record' feature of gdb allows reverse debugging.  neato.
but on Ubuntu-16.04 it fails to work, complaining about an unhandled
instruction.

% gdb simple 
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from simple...done.
(gdb) b main
Breakpoint 1 at 0x400db7: file 
/home/robl/work/mpich/src/mpi/romio/test/simple.c, line 26.
(gdb) run
Starting program: /home/robl/work/build/mpich-logfs/src/mpi/romio/test/simple 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, main (argc=1, argv=0x7fffd698)
at /home/robl/work/mpich/src/mpi/romio/test/simple.c:26
26  {
(gdb) record
(gdb) continue
Continuing.
Process record does not support instruction 0xc5 at address 0x77dee6e7.
Process record: failed to record execution log.

Program stopped.
_dl_runtime_resolve_avx () at ../sysdeps/x86_64/dl-trampoline.h:81
81  ../sysdeps/x86_64/dl-trampoline.h: No such file or directory.


If we examine the address we see this:

(gdb) x/i 0x77dee6e7
=> 0x77dee6e7 <_dl_runtime_resolve_avx+71>: vmovdqa %ymm0,(%rsp)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gdb 7.11-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 22 15:34:03 2016
InstallationDate: Installed on 2015-09-10 (225 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: gdb
UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  gdb Process record does not support instruction 0xc5

Status in gdb package in Ubuntu:
  New

Bug description:
  the 'process record' feature of gdb allows reverse debugging.  neato.
  but on Ubuntu-16.04 it fails to work, complaining about an unhandled
  instruction.

  % gdb simple 
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from simple...done.
  (gdb) b main
  Breakpoint 1 at 0x400db7: file 
/home/robl/work/mpich/src/mpi/romio/test/simple.c, line 26.
  (gdb) run
  Starting program: /home/robl/work/build/mpich-logfs/src/mpi/romio/test/simple 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

  Breakpoint 1, main (argc=1, argv=0x7fffd698)
  at /home/robl/work/mpich/src/mpi/romio/test/simple.c:26
  26  {
  (gdb) record
  (gdb) continue
  Continuing.
  Process record does not support instruction 0xc5 at address 0x77dee6e7.
  Process record: failed to record execution log.

  Program stopped.
  _dl_runtime_resolve_avx () at ../sysdeps/x86_64/dl-trampoline.h:81
  81  ../sysdeps/x86_64/dl-trampoline.h: No such file or directory.

  
  If we examine the address we see this:

  (gdb) x/i 0x77dee6e7
  => 0x77dee6e7 <_dl_runtime_resolve_avx+71>: vmovdqa %ymm0,(%rsp)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdb 7.11-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 15:34:03 2016
  InstallationDate: Installed on 2015-09-10 (225 days ago)
  InstallationMedia: 

[Touch-packages] [Bug 1567070] [NEW] gmail often called/contacted are not synchronized with device

[Rob Cec]

Public bug reported:

when i look to my gmail account on a pc I can find all contacts. when I
look to my synchronized ubuntu device BQ 4.5 i can not find a all my
contacts. The reason i found i the following. all contact markt as often
called/contacted are not synchronized with my device.

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gmail often called/contacted are not synchronized with device

Status in address-book-app package in Ubuntu:
  New

Bug description:
  when i look to my gmail account on a pc I can find all contacts. when
  I look to my synchronized ubuntu device BQ 4.5 i can not find a all my
  contacts. The reason i found i the following. all contact markt as
  often called/contacted are not synchronized with my device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1567070/+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 1354163] Re: Record Route option broken in iputils-ping

[Rob M]

Why did you change this to fix released?  I do not see any updates that
address this issue.

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

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

Title:
  Record Route option broken in iputils-ping

Status in iputils package in Ubuntu:
  Confirmed

Bug description:
  using ping -R does not function properly in Ubuntu 14.04.

  Copying a ping binary from a Debian machine with the same version of
  iputils-ping installed works as intended.

  Expected behavior (Debian binary)

  root@tserv21:~# ./ping -R  209.51.169.78
  PING 209.51.169.78 (209.51.169.78) 56(124) bytes of data.
  64 bytes from 209.51.169.78: icmp_seq=1 ttl=61 time=9.60 ms
  RR: 216.66.38.58
  184.105.223.129
  184.105.222.93
  209.51.169.77
  209.51.169.78
  209.51.169.78
  184.105.222.94
  184.105.223.130
  216.66.38.57

  ^C
  --- 209.51.169.78 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 9.605/9.605/9.605/0.000 ms

  Faulty behavior (Ubuntu system binary).  Note each hop is replaced
  with the target address.

  root@tserv21:~# ping -R  209.51.169.78
  PING 209.51.169.78 (209.51.169.78) 56(124) bytes of data.
  64 bytes from 209.51.169.78: icmp_seq=1 ttl=61 time=10.5 ms
  RR: 209.51.169.78
  209.51.169.78
  209.51.169.78
  209.51.169.78
  209.51.169.78
  209.51.169.78
  209.51.169.78
  209.51.169.78
  209.51.169.78

  ^C
  --- 209.51.169.78 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 10.533/10.533/10.533/0.000 ms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1354163/+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 1551351] Re: dhclient does not renew leases

[Rob Whyte]

Since I am running dhclient -d eth0 I have not been disconnected.  I do
not intend to run dhclient this way, it is a part of the minimal system
and should work in the background with no intervention. Who is actively
working on this bug from Cannonical?

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

Title:
  dhclient does not renew leases

Status in bind9 package in Ubuntu:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in bind9 source package in Xenial:
  Confirmed
Status in isc-dhcp source package in Xenial:
  Confirmed

Bug description:
  Release: Xenial

  I think this only recently started after some bind9 updates triggered a 
rebuild. When booting dhclient gets started and acquires an IP address, but it 
does seem to lock up somewhere as it does not renew the lease.
  In my environment I set the lease time to 5 minutes, so I notice such things 
rather soon. I looked on the dhcp server side but saw any further dhcp messages 
come in from the client side.

  Related bugs:
   * bug 1551415:  systemctl stop networking hang / timeout 

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Feb 29 12:32:52 2016
  DhclientLeases:

  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1551351] Re: dhclient does not renew leases

[Rob Whyte]

I too have struggled with this on my server, leaving us without internet
until sudo dhclient eth0 or the interace is taken down and brought back
up.

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

Title:
  dhclient does not renew leases

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Release: Xenial

  I think this only recently started after some bind9 updates triggered a 
rebuild. When booting dhclient gets started and acquires an IP address, but it 
does seem to lock up somewhere as it does not renew the lease.
  In my environment I set the lease time to 5 minutes, so I notice such things 
rather soon. I looked on the dhcp server side but saw any further dhcp messages 
come in from the client side.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Feb 29 12:32:52 2016
  DhclientLeases:
   
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351/+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 1186662] Re: isc-dhcp-server fails to renew lease file

[Rob Whyte]

After installing Xenial server last week I had problems from the get go
with isc-dhcp-server and client. As it is my gateway I have had a great
deal of trouble. Your suggestions in comment 37 seem to address them, am
waiting to see if my next ISP dhcp renewal leaves me disconnected again.
Effected packages for me are 4.4.4-5ubuntu7 and 4.4.4-5ubuntu8.

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

Title:
  isc-dhcp-server fails to renew lease file

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Triaged

Bug description:
  After raring upgrade, the dhcp server fails to renew lease file when
  it tries to (about every hour).

  The syslog says:
  dhcpd: Can't create new lease file: Permission denied

  It looks like a permission problem, because

  # chown -R dhcpd:dhcpd /var/lib/dhcp

  the above command temporarily solves the issue, until dhcpd is
  restarted: at that time, the ownership of the directory and the lease
  file is set back to root:root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1535952] Re: isc-dhcp-server.service fails on xenial with "Can't open lease database /var/lib/dhcp/dhcpd.leases: No such file or directory"

[Rob Whyte]

Still seeing this bug in 4.3.3-5ubuntu7 and 4.3.3-5ubuntu8. Has it been
re-introduced?

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

Title:
  isc-dhcp-server.service fails on xenial with "Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory"

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  While investigating a DHCP issue on MAAS, I installed a fresh xenial
  on a LXC container and installed the isc-dhcp-server package. It fails
  to start with a syslog entry like "dhcpd[8090]: Can't open lease
  database /var/lib/dhcp/dhcpd.leases: No such file or directory --.

  From the machine:

  root@xenial-dhcp-test:~# lsb_release -rd
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  root@xenial-dhcp-test:~# dpkg -l isc* | cat
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name VersionArchitecture Description
  
+++--==--=
  ii  isc-dhcp-client  4.3.3-5ubuntu1 amd64DHCP client for 
automatically obtaining an IP address
  un  isc-dhcp-client-ddns (no description 
available)
  ii  isc-dhcp-common  4.3.3-5ubuntu1 amd64common files used by all 
of the isc-dhcp packages
  ii  isc-dhcp-server  4.3.3-5ubuntu1 amd64ISC DHCP server for 
automatic IP address assignment
  un  isc-dhcp-server-ldap (no description 
available)

  root@xenial-dhcp-test:~# systemctl status isc-dhcp-server.service
  ● isc-dhcp-server.service - ISC DHCP IPv4 server
 Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Tue 2016-01-19 23:43:40 UTC; 6min 
ago
   Docs: man:dhcpd(8)
Process: 8090 ExecStart=/bin/sh -ec  CONFIG_FILE=/etc/dhcp/dhcpd.conf;  
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi;  
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES (code=exited, status=1/FAILURE)
Process: 8081 ExecStartPre=/bin/chown dhcpd:dhcpd /run/dhcp-server 
(code=exited, status=0/SUCCESS)
   Main PID: 8090 (code=exited, status=1/FAILURE)

  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: Can't open lease database 
/var/lib/dhcp/dhcpd.leases: No suc...y --
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: check for failed database rewrite 
attempt!
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: Please read the dhcpd.leases 
manual page if you
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: don't know what to do about this.
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: If you think you have received 
this message due to a bug rather
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: than a configuration issue please 
read the section on submitting
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: bugs on either our web page at 
www.isc.org or in the README file
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: before submitting a bug.  These 
pages explain the proper
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: process and the information we 
find helpful for debugging..
  Jan 19 23:43:40 xenial-dhcp-test sh[8090]: exiting.
  Hint: Some lines were ellipsized, use -l to show in full.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1535952/+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 1550289] Re: after my isp lease is due to be renewed isc-dhcp-client does not seem to be renewing, have to take interface down on internet and up again before a new external ip i

[Rob Whyte]

Downgraded to 4.3.3-5ubuntu7 and the same behaviour occurs. Do not seem
to see anything in logs, I take down interface and bring it up to get a
new ip. network cards are intel 82541GI on a dell poweredge 2850.

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

Title:
  after my isp lease is due to be renewed isc-dhcp-client does not seem
  to be renewing, have to take interface down on internet and up again
  before a new external ip is assigned.

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  i am using xenial as a gateway, having problems maintaining an
  internet connection without having to manuallly if down and up the
  internet interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Feb 26 22:22:11 2016
  InstallationDate: Installed on 2016-02-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1550289/+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 1550289] [NEW] after my isp lease is due to be renewed isc-dhcp-client does not seem to be renewing, have to take interface down on internet and up again before a new external ip

[Rob Whyte]

Public bug reported:

i am using xenial as a gateway, having problems maintaining an internet
connection without having to manuallly if down and up the internet
interface.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Fri Feb 26 22:22:11 2016
InstallationDate: Installed on 2016-02-24 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=screen.linux
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed xenial

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

Title:
  after my isp lease is due to be renewed isc-dhcp-client does not seem
  to be renewing, have to take interface down on internet and up again
  before a new external ip is assigned.

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  i am using xenial as a gateway, having problems maintaining an
  internet connection without having to manuallly if down and up the
  internet interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Fri Feb 26 22:22:11 2016
  InstallationDate: Installed on 2016-02-24 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160219)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=screen.linux
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1550289/+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 1545108] Re: crontab ignores the day of month, and executes based only on the time and the weekday.

[Rob]

So, I just learned that if I have a crontab with both the day of month
and day of week fields set, it will run on both the given weekday and
given the day of the month, and to have a crontab only work on a certain
day of the month, the day of week field should be set to an asterisk.

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

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

Title:
  crontab ignores the day of month, and executes based only on the time
  and the weekday.

Status in cron package in Ubuntu:
  Invalid

Bug description:
  here is my crontab:

45   5   * * 1-5   pkill -f flash
48   6   * * 1-5   musicalarm
50   9   * * 1-5   mpc random off
30   7   5 2   5   echo -e "I'm not coming in today.\n\nHave a good 
one!" | mail -s "No pikupordropov needed" em...@example.com

  Obviously I have changed the email a bit, but it gives you an idea.
  The email got sent today, even though it is clearly not the 5th of
  February. Something similar happened a couple days ago (another
  command that was scheduled for that day, but earlier in the month).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cron 3.0pl1-124ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Feb 12 10:33:41 2016
  InstallationDate: Installed on 2014-02-04 (738 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: cron
  UpgradeStatus: Upgraded to trusty on 2014-07-20 (571 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1545108/+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 1545108] [NEW] crontab ignores the day of month, and executes based only on the time and the weekday.

[Rob]

Public bug reported:

here is my crontab:

  45   5   * * 1-5   pkill -f flash
  48   6   * * 1-5   musicalarm
  50   9   * * 1-5   mpc random off
  30   7   5 2   5   echo -e "I'm not coming in today.\n\nHave a good 
one!" | mail -s "No pikupordropov needed" em...@example.com

Obviously I have changed the email a bit, but it gives you an idea. The
email got sent today, even though it is clearly not the 5th of February.
Something similar happened a couple days ago (another command that was
scheduled for that day, but earlier in the month).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cron 3.0pl1-124ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Fri Feb 12 10:33:41 2016
InstallationDate: Installed on 2014-02-04 (738 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: cron
UpgradeStatus: Upgraded to trusty on 2014-07-20 (571 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  crontab ignores the day of month, and executes based only on the time
  and the weekday.

Status in cron package in Ubuntu:
  New

Bug description:
  here is my crontab:

45   5   * * 1-5   pkill -f flash
48   6   * * 1-5   musicalarm
50   9   * * 1-5   mpc random off
30   7   5 2   5   echo -e "I'm not coming in today.\n\nHave a good 
one!" | mail -s "No pikupordropov needed" em...@example.com

  Obviously I have changed the email a bit, but it gives you an idea.
  The email got sent today, even though it is clearly not the 5th of
  February. Something similar happened a couple days ago (another
  command that was scheduled for that day, but earlier in the month).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cron 3.0pl1-124ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Fri Feb 12 10:33:41 2016
  InstallationDate: Installed on 2014-02-04 (738 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: cron
  UpgradeStatus: Upgraded to trusty on 2014-07-20 (571 days ago)

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

[Rob]

Public bug reported:

-

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Jan  3 00:18:13 2016
DistUpgraded: 2015-12-21 15:51:49,774 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-39-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-22-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Device [104d:90b7]
   Subsystem: Sony Corporation Device [104d:90b7]
InstallationDate: Installed on 2013-12-23 (740 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Sony Corporation SVF15A1C5E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=f3191322-4027-4a8a-8d72-1ada9c5fb35e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to wily on 2015-12-21 (12 days ago)
dmi.bios.date: 03/26/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0200DA
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0200DA:bd03/26/2013:svnSonyCorporation:pnSVF15A1C5E:pvrC10HKMJV:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVF15A1C5E
dmi.product.version: C10HKMJV
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sun Jan  3 00:08:09 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5563 
 vendor CMN
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu wily

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

Title:
  -

Status in xorg package in Ubuntu:
  New

Bug description:
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jan  3 00:18:13 2016
  DistUpgraded: 2015-12-21 15:51:49,774 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-39-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-22-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Device [104d:90b7]
 Subsystem: Sony Corporation Device [104d:90b7]
  InstallationDate: Installed on 2013-12-23 (740 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Sony Corporation SVF15A1C5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 

[Touch-packages] [Bug 1301015] Re: Networking does not restart

[Rob Shepherd]

This is another sign of a good distribution going backwards.

I need to change a large VM cluster from DHCP to static over SSH using
automation tools

/etc/init.d/networking restart used to work remotely for this. What the
heck am I supposed to do now?

Clearly everybody used /etc/init.d/networking . Can it not be
retrofitted to be a supported function?

Can anybody confirm a method of reliably reloading the network config
remotely over SSH ?

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1301015] Re: Networking does not restart

[Rob Shepherd]

This does not work for me.

 ifdown eth0 && ifup eth0

as root, running over ssh and screen and the machine has disappeared.


Unfortunately our test machines are not VMs with local access only to the 
console.
I now have a long round trip journey to the datacenter.  

What a waste of time.  FFS

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1518289] Re: front headphone jack recognised by alsa but ignored by pulseaudio

[Rob]

re disabled auto mute, the problem was detected while auto mute was enabled.  I 
only disabled it while experimenting with alsamixer, and did not change it back 
because it did not affect my user experience at all.
Perhaps it is relevant to know that I keep a set of old self powered computer 
speakers permanently connected to the rear line output jack, and control 
whether they make noise or not by altering the levels on the speakers - so 
afaik the computer has no awareness of whether they are making noise or not, 
they will just always appear connected.

Would it be useful if I test again and/or regenerate files with auto
mute enabled?

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

Title:
  front headphone jack recognised by alsa but ignored by pulseaudio

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Summary:
  PC has 
  Card: HD-Audio Generic
  Chip: Realtek ALC887-VD
  Ubuntu 15.10 64-bit
  pulseaudio 1:6.0-0ubuntu13
  - working rear audio jack connected to speakers - volume controlled from 
Settings>Sound>Sound Output tab.
  - nonworking front headphone jack  - no corresponding output device in 
Settings>Sound>Sound Output tab.  (not affected by whether or not headphones 
are connected at boot time)
  However front headphone jack is visible (muted) in alsamixer, and volume can 
be unmuted and raised in current session - returns to muted on reboot.

  Detail:
  This desktop PC was previously running trusty with front headphone jack 
working normally - if audio on rear jack there was audio in headphones.  I do 
not remember now whether the audio volume was separately controlled as a second 
output device, either would have worked fine for me.
  Fresh install of wily on a new disk resulted in working rear audio jack, but 
non-working front headphone jack.
  The ubuntu Settings>Sound Output tab shows only one device for sound output: 
"Line Out - Built-in Audio".

  My expectation is that the volume level of the headphone jack should
  initially be set to a non-zero level.

  After exploring various options, I discovered that the front headphone
  jack is visible in alsamixer but displayed as level 0 and muted.  It
  can be made to work in the current session by unmuting and setting to
  a non-zero level.

  Adjusting volume and balance in the ubuntu Settings>Sound Output tab
  affects the audio output levels to the headphone jack in the way one
  might expect, but when the settings are changed while alsamixer is
  open (eg left right balance), the vertical bars for the headphone
  level do not move as they do for all other output jacks.  But when the
  surround sound profile is changed in the Settings>Sound Output tab,
  both actual headphone volume and headphone volume bars in alsamixer
  drop to 0 with muting.

  In any event, on reboot the jack is muted again and needs to be reset
  in alsamixer.

  Following online advice, I unsuccessfully tried various ways to make
  the unmuted settings survive a reboot - eg running alsamixer under
  sudo, alsactl store.

  Eventually I looked at the contents of the /var/lib/alsa/asound.state
  file and realised that the unmuted state was properly set in the file
  and was unchanged on reboot.

  The muting was being caused by pulseaudio.

  I was able to verify this by unmuting in alsamixer and restarting
  pulseaudio without rebooting - the output was muted again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jane   1189 F pulseaudio
jane   1491 F alsamixer
   /dev/snd/controlC0:  jane   1189 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 20 20:26:26 2015
  InstallationDate: Installed on 2015-11-17 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FM2-A75MA-E35 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.1:bd09/24/2012:svnMSI:pnMS-7721:pvr1.0:rvnMSI:rnFM2-A75MA-E35(MS-7721):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7721
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage