[Touch-packages] [Bug 2056556] [NEW] apt-add-repository incorrectly forces lowercase

[Malcolm Scott]

Public bug reported:

I have a local APT repository with a non-lowercase suite identifier.
apt-add-repository always forces it into lowercase, which causes apt to
emit warnings when it notices the mismatch:

$ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
Repository: 'deb http://example.com/ foobar Baz'
Description:
Archive for codename: foobar components: Baz
More info: http://example.com/
Adding repository.
Press [ENTER] to continue or Ctrl-c to cancel.
(...)
$ sudo apt update
(...)
W: Conflicting distribution: http://example.com/deb foobar InRelease (expected 
foobar but got FooBar)

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

Title:
  apt-add-repository incorrectly forces lowercase

Status in software-properties package in Ubuntu:
  New

Bug description:
  I have a local APT repository with a non-lowercase suite identifier.
  apt-add-repository always forces it into lowercase, which causes apt
  to emit warnings when it notices the mismatch:

  $ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
  Repository: 'deb http://example.com/ foobar Baz'
  Description:
  Archive for codename: foobar components: Baz
  More info: http://example.com/
  Adding repository.
  Press [ENTER] to continue or Ctrl-c to cancel.
  (...)
  $ sudo apt update
  (...)
  W: Conflicting distribution: http://example.com/deb foobar InRelease 
(expected foobar but got FooBar)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056556/+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 2052740] [NEW] Crossed circle keeps popping up on my screen

[Malcolm Chikadibia Iheremelam]

Public bug reported:

I noticed this crossed circle when i started using linux (pop_os).
Initially it seemed insignificant and harmless, but over time it started
affecting typing with my keyboard. It also affected my video playback -
always pausing the video.

I installed the ubuntu distro with hopes of eliminating the problem, but
it still persists. The only improvement is that the crossed circle
doesn't interfer with my keyboard and video playback for now, despite it
still appears on my screen. But i believe it's just a matter of time
before the interference resumes.

I have attached a screenshot to this report containing the crossed
circle symbol.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb  8 22:38:11 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation GeminiLake [UHD Graphics 605] [8086:3184] (rev 03) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company GeminiLake [UHD Graphics 605] [103c:84d4]
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson 
Peak (JfP)
 Bus 001 Device 003: ID 04f3:250e Elan Microelectronics Corp. Touchscreen
 Bus 001 Device 002: ID 0bda:58ed Realtek Semiconductor Corp. HP Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 15-bs2xx
ProcEnviron:
 LANGUAGE=en_NG:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_NG
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_3903w5@/vmlinuz-6.2.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_3903w5 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2022
dmi.bios.release: 15.71
dmi.bios.vendor: Insyde
dmi.bios.version: F.71
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84D4
dmi.board.vendor: HP
dmi.board.version: 94.30
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 94.30
dmi.modalias: 
dmi:bvnInsyde:bvrF.71:bd11/14/2022:br15.71:efr94.30:svnHP:pnHPLaptop15-bs2xx:pvrType1ProductConfigId:rvnHP:rn84D4:rvr94.30:cvnHP:ct10:cvrChassisVersion:sku4ND16UA#ABA:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-bs2xx
dmi.product.sku: 4ND16UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1
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 wayland-session

** Attachment added: "Screenshot showing the dark crossed circle at the base of 
my display"
   
https://bugs.launchpad.net/bugs/2052740/+attachment/5745284/+files/Screenshot%20from%202024-02-08%2022-38-53.png

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

Title:
  Crossed circle keeps popping up on my screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I noticed this crossed circle when i started using linux (pop_os).
  Initially it seemed insignificant and harmless, but over time it
  started affecting typing with my keyboard. It also affected my video
  playback - always pausing the video.

  I installed the ubuntu distro with hopes of eliminating the problem,
  but it still persists. The only improvement is that the crossed circle
  doesn't interfer with my keyboard and video playback for now, despite
  it still appears on my screen. But i believe it's just a matter of
  time before the interference resumes.

  I have attached a screenshot to this report containing the crossed
  circle symbol.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon 

[Touch-packages] [Bug 2016408] Re: Running all KDE (Qt) apps on Wayland - apps bad working

[Malcolm Priestley]

Workaround for Kaffeine on Wayland is run with -platform xcb

open terminal

kaffeine -platform xcb

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

Title:
  Running all KDE (Qt) apps on Wayland - apps bad working

Status in Yaru Theme:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in yaru-theme package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  on Ubuntu 23.04 all KDE apps work not properly. When I run KDE apps (like 
clementine, kaffeine, smplayer), the cursor on HDPi monitor (scale 200%) is so 
huge than in Gnome apps. KDE apps discrespect windows decorations (like max, 
min, close buttons - I have them on the left site, but kde apps have it on 
right site). When I start smplayer, it crashes because can't play video over 
mplayer/mpv player...blank window and crashes.

  Same problems here:
  
https://www.reddit.com/r/kde/comments/xev3jq/is_there_a_way_to_make_smplayermpv_work_under/

  Solution for me is run KDE apps like:
  QT_QPA_PLATFORM=xcb smplayer

  If i try tu run application like that, everything is working properly.
  Can you pleas repair it on Ubuntu 23.04 for wayland?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 16 11:16:28 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed
   v4l2loopback/0.12.7, 6.2.0-20-generic, x86_64: installed (WARNING! Diff 
between built and installed module!)
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]
  InstallationDate: Installed on 2023-04-14 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Daily amd64 (20230414)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=d6cce96a-9549-40b0-8d45-aeb37eabc158 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1805
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170 PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1805:bd05/13/2016:br5.11:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2016408/+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 1943312] Re: dependency problems of version 3.4.2-1ubuntu3

[Malcolm Priestley]

I have same problem reinstalling libffi8ubuntu1 wants to remove the
entire ubuntu-desktop in impish.

I am sure it's just waiting for an update to this package.

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

Title:
  dependency problems of version 3.4.2-1ubuntu3

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  Have both libffi8ubuntu1:amd64 and libffi8ubuntu1:i386 installed
  previously. Got these after upgrading to 3.4.2-1ubuntu3

  dpkg: dependency problems prevent configuration of libffi8:amd64:
   libffi8:i386 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:amd64 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:amd64 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of libffi8:i386:
   libffi8:amd64 (3.4.2-1ubuntu3) breaks libffi8ubuntu1 and is unpacked but not 
configured.
libffi8:i386 (3.4.2-1ubuntu3) provides libffi8ubuntu1.

  dpkg: error processing package libffi8:i386 (--configure):
   dependency problems - leaving unconfigured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943312/+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 1898944] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Malcolm Durie]

Public bug reported:

Installation gave and error about intramfs-tools and repository being
out of date when upgrading from 18.04LTS to latest 20.04.01.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Oct  7 23:01:56 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-01-11 (1731 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-07 (0 days ago)

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


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Installation gave and error about intramfs-tools and repository being
  out of date when upgrading from 18.04LTS to latest 20.04.01.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct  7 23:01:56 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-11 (1731 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-10-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1898944/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore

[Malcolm Scott]

Any progress on this?  This is a serious regression for us which makes
preseed substantially less functional in bionic...

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

Title:
  apt-setup uses apt-key but probably should not anymore

Status in apt-setup package in Ubuntu:
  Confirmed
Status in gnupg package in Ubuntu:
  Confirmed
Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  In di if the kernel is in a private PPA we seed di using

  d-i apt-setup/local0/key string
  http://keyserver.ubuntu.com:11371/pks/lookup?op=get=

  this used to work in xenial, but in bionic this fails and therefore
  apt update fails in base-installer. May be because add-apt-key is not
  installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop

[Malcolm O'Brien-Rogers]

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

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

Title:
  hud-service is eating up 100% of one of my CPUs in a poll loop

Status in Unity HUD:
  New
Status in unbuntu-fr Scripts - apt:
  Confirmed
Status in hud package in Ubuntu:
  In Progress

Bug description:
  hud-service is polling like crazy:

  Context Switches:
PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
2295 hud-service  46084.6342.94 46127.58 (very high)
2325 hud-service  0.09 0.00 0.09 (very low)
2329 hud-service  0.07 0.00 0.07 (very low)
2340 hud-service  0.05 0.00 0.05 (very low)
   Total  46084.8442.94 46127.78

  File I/O operations:
   No file I/O operations detected.

  System calls traced:
PID  Process  Syscall   CountRate/Sec
2295 hud-service  poll 83   23124.8503
2295 hud-service  write10   0.2313
2295 hud-service  sendmsg   4   0.0925
2325 hud-service  restart_syscall   1   0.0231
2329 hud-service  restart_syscall   1   0.0231
2340 hud-service  restart_syscall   1   0.0231
   Total  100   23125.2435

  (gdb) where
  #0  0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #2  0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #3  0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #4  0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #5  0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #6  0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #7  0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #8  0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2
  #9  0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() ()
  #17 0x00441e43 in hud::service::WindowImpl::activate() ()
  #18 0x00439f6a in 
hud::service::QueryImpl::updateToken(QSharedPointer) ()
  #19 0x0043a672 in hud::service::QueryImpl::refresh() ()
  #20 0x0044b115 in ?? ()
  #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #22 0x0045662a in 
hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString 
const&, unsigned int) ()
  #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #24 0x00467361 in 
ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, 
QString const&, unsigned int) ()
  #25 0x004678bd in ?? ()
  #26 0x00467c63 in 
ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, 
void**) ()
  #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #28 0x7fda8435e22e in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, 
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #33 0x7fda84382cd3 in ?? () from 

[Touch-packages] [Bug 1650555] Re: nsswitch.conf configuration doesn't work with mdns hosts

[Sebastian Malcolm]

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

Use the re-ordering of hosts line in nsswitch.conf posted by Mark Tearle in 
#1641328:
   files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns

This is better than removing "resolve [!UNAVAIL=return]" because recent Ubuntu 
releases should continue to use systemd-resolved for name resolution. It's man 
page explains several benefits, see:
 https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html

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

Title:
  nsswitch.conf configuration doesn't work with mdns hosts

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts
  doesn't work anymore (it used to in xenial)

  I can resolve names with avahi-resolve but ssh,ping,etc. fail to
  resolve.

  After some digging I found out that what's causing it is the "resolve"
  option in /etc/nsswitch.conf:

  hosts:  files resolve [!UNAVAIL=return] mdns4_minimal
  [NOTFOUND=return] dns

  Changing it to

  hosts:  files mdns4_minimal [NOTFOUND=return] dns

  (as it was on xenial) makes mDNS work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 15:16:38 2016
  InstallationDate: Installed on 2016-10-22 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650555/+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 1650555] Re: nsswitch.conf configuration doesn't work with mdns hosts

[Sebastian Malcolm]

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

** This bug has been marked a duplicate of bug 1641328
   Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS 
lookups to fail -- breaks network printing

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

Title:
  nsswitch.conf configuration doesn't work with mdns hosts

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  On a fresh Ubuntu 16.10 (yakkety) install, resolution of mDNS hosts
  doesn't work anymore (it used to in xenial)

  I can resolve names with avahi-resolve but ssh,ping,etc. fail to
  resolve.

  After some digging I found out that what's causing it is the "resolve"
  option in /etc/nsswitch.conf:

  hosts:  files resolve [!UNAVAIL=return] mdns4_minimal
  [NOTFOUND=return] dns

  Changing it to

  hosts:  files mdns4_minimal [NOTFOUND=return] dns

  (as it was on xenial) makes mDNS work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Dec 16 15:16:38 2016
  InstallationDate: Installed on 2016-10-22 (54 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650555/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked

[Malcolm]

Yes, I can confirm the alarm does sound but only when you pick the phone
up and turn on the screen.

However, this is after (10 minutes in my case) it should have sounded



From: boun...@canonical.com  on behalf of Michal 
Predotka 
Sent: 14 October 2016 23:05
To: malcolm_h...@outlook.com
Subject: [Bug 1588526] Re: [mako] Alarm doesn't ring when screen locked

Comment #13 describes a problem with a different alarm sound played then
expected. I believe that could be the same situation as in bug #1596924
(sound change need to be confirmed)

--
You received this bug notification because you are subscribed to a
duplicate bug report (1631863).
https://bugs.launchpad.net/bugs/1588526

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+subscriptions

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1560762] [NEW] iSCSI root with multiple NICs fails ifdown -a

[Malcolm Weir]

Public bug reported:

Ubuntu 14.04.4 LTS
ifupdown version  0.7.47.2ubuntu4.4

In /etc/init/networking.conf, there is a test for an iSCSI filesystem
mounted by the initramfs, which tests to see if the file
/etc/iscsi/iscsi.initramfs exists. If that file exists, the script exits
immediately, which means that the event "deconfiguring-networking" never
occurs.

The correct behavior would seem to be to detect which interface is being
used for the iSCSI mount, and exclude just that interface from the
"ifdown" command just after the event emission.

I.e. if the iSCSI volume is using eth2, then the ifdown command should
be called as "ifdown -a --exclude=lo0 --exclude=eth2"

Appropriate code might be:


# networking - configure virtual network devices
#
# This task causes virtual network devices that do not have an associated
# kernel object to be started on boot.

description "configure virtual network devices"

emits static-network-up
emits net-device-up
emits deconfiguring-networking

start on (local-filesystems
and (stopped udevtrigger or container)) or runlevel [2345] or stopped 
networking RESULT=failed PROCESS=post-stop EXIT_STATUS=100
stop on unmounted-remote-filesystems

pre-start script
if [ "$UPSTART_EVENTS" = "stopped" ] && [ "$UPSTART_JOB" = "networking" ] 
&& [ "$EXIT_STATUS" = "100" ]; then
exit 0
fi

mkdir -p /run/network
ifup -a
end script

post-stop script
if [ -z "$UPSTART_STOP_EVENTS" ]; then
echo "Stopping or restarting the networking job is not supported."
echo "Use ifdown & ifup to reconfigure desired interface."
exit 100
fi

log_warning_msg() {
echo $*
}

# These checks were taken from the Debian ifupdown.networking.init script
check_network_file_systems() {
[ -e /proc/mounts ] || return 0

if [ -e /etc/iscsi/iscsi.initramfs ]; then
if [ -e /dev/.initramfs/open-iscsi.interface ]
then
EXCL_NIC=`cat /dev/.initramfs/open-iscsi.interface`
log_warning_msg "not deconfiguring specific network interface 
${EXCL_NIC}: iSCSI root is mounted."
EXCLUDE=" --exclude=${EXCL_NIC}"
else
log_warning_msg "not deconfiguring network interfaces: iSCSI 
root is mounted."
fi
exit 0
fi

while read DEV MTPT FSTYPE REST; do
case $DEV in
/dev/nbd*|/dev/nd[a-z]*|/dev/etherd/e*)
log_warning_msg "not deconfiguring network interfaces: network 
devices still mounted."
exit 0
;;
esac
case $FSTYPE in

nfs|nfs4|smbfs|ncp|ncpfs|cifs|coda|ocfs2|gfs|pvfs|pvfs2|fuse.httpfs|fuse.curlftpfs)
log_warning_msg "not deconfiguring network interfaces: network 
file systems still mounted."
exit 0
;;
esac
done < /proc/mounts
}

check_network_swap() {
[ -e /proc/swaps ] || return 0

while read DEV MTPT FSTYPE REST; do
case $DEV in
/dev/nbd*|/dev/nd[a-z]*|/dev/etherd/e*)
log_warning_msg "not deconfiguring network interfaces: network 
swap still mounted."
exit 0
;;
esac
done < /proc/swaps
}

check_network_file_systems
check_network_swap

# Anything that manages network interfaces *MUST* wait for this event
initctl emit deconfiguring-networking
ifdown -a --exclude=lo ${EXCLUDE}
end script

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

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

Title:
  iSCSI root with multiple NICs fails ifdown -a

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.4 LTS
  ifupdown version  0.7.47.2ubuntu4.4

  In /etc/init/networking.conf, there is a test for an iSCSI filesystem
  mounted by the initramfs, which tests to see if the file
  /etc/iscsi/iscsi.initramfs exists. If that file exists, the script
  exits immediately, which means that the event "deconfiguring-
  networking" never occurs.

  The correct behavior would seem to be to detect which interface is
  being used for the iSCSI mount, and exclude just that interface from
  the "ifdown" command just after the event emission.

  I.e. if the iSCSI volume is using eth2, then the ifdown command should
  be called as "ifdown -a --exclude=lo0 --exclude=eth2"

  Appropriate code might be:

  
  # networking - configure virtual network devices
  #
  # This task causes virtual network devices that do not have an associated
  # kernel object to be started on boot.

  description "configure virtual network devices"

  emits static-network-up
  emits net-device-up
  emits deconfiguring-networking

  start on (local-filesystems
 

[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

[Malcolm Brown]

I have two notebook computers - a Toshiba and a Fujitsu both of which
are very old and are both dual boot computers with Windows 7 and Ubuntu
14.04 LTE 32 bit. Both computers and both operating systems work fine
with Bluetooth linking to a Bose mini soundlink speaker for playing
music. I use a USB bluetooth dongle for the link and all works well.

However, with a much newer laptop, a Toshiba Satellite Pro C50-A-1K9
running the 64 bit version of Ubuntu 14.04 LTE I cannot get bluetooth to
work despite using the same dongle and the same speaker. The first time
it finds the device, attempts to pair, but asks that a particular 4
digit code be entered from the device. This is of course impossible as
the Bose mini soundlink speaker does not have a keypad! Further attempts
to search for bluetooth devices after this first time find nothing. If I
then go back to the old notepad computers they also cannot find the
device at all with either Windows or Ubuntu 14.04 32 bit. I strongly
suspect that the 64 bit version of Ubuntu 14.04 LTE has sent a code to
the speaker which prevents it linking via bluetooth thereafter.

If anyone else has the Bose mini soundlink speaker and needs to overcome
this problem, then

Perform a factory reset on the speaker by first turning it on then
holding down the bluetooth button for about ten seconds when the speaker
beeps and will now work again with the old computers and windows 7 or
Ubuntu 14.04 LTE 32 bit.

Hope a skilled programmer finds the bug!

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman:
  New
Status in blueman package in Ubuntu:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1283003/+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 1449001] [NEW] systemd-resolved: please do not use Google public DNS by default

[Malcolm Scott]

Public bug reported:

systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.) in
the absence of other configured DNS servers.

systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
installed by default and will behave in this way if enabled by the user.

$ cat /etc/systemd/resolved.conf 
(...)
# Entries in this file show the compile time defaults.
(...)
#FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

This raises privacy concerns since in the event of accidental
misconfiguration DNS queries will be sent unencrypted across the
internet, and potentially also security concerns given systemd-resolved
does not perform DNSSEC validation and is not particularly well hardened
against malicious responses e.g. from a MITM
(http://www.openwall.com/lists/oss-security/2014/11/12/5).

I believe that it would be better to fail safe if no DNS server is
configured -- i.e. have DNS lookups fail; it's better that the user is
aware of their misconfiguration, rather than silently sending their
queries to Google.  The user can intentionally opt to use Google public
DNS if they wish.


Steps to reproduce:
1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
2. Reboot, or otherwise clear relevant state
3. sudo service systemd-resolved start
4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by default), 
observe that DNS lookups probably still work, and queries are being sent to one 
of Google's servers


Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.


This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco d'Itri: Short summary: have a resolv.conf 
file or use DHCP).  I would argue that it's safest not to have fallback DNS 
servers configured at all by default.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: Debian Bug tracker #761658
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658

** Also affects: systemd via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd-resolved: please do not use Google public DNS by default

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

Bug description:
  systemd-resolved will fall back to Google public DNS (8.8.8.8, etc.)
  in the absence of other configured DNS servers.

  systemd-resolved is not enabled by default in Ubuntu 15.04, but it is
  installed by default and will behave in this way if enabled by the
  user.

  $ cat /etc/systemd/resolved.conf 
  (...)
  # Entries in this file show the compile time defaults.
  (...)
  #FallbackDNS=8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844

  This raises privacy concerns since in the event of accidental
  misconfiguration DNS queries will be sent unencrypted across the
  internet, and potentially also security concerns given systemd-
  resolved does not perform DNSSEC validation and is not particularly
  well hardened against malicious responses e.g. from a MITM
  (http://www.openwall.com/lists/oss-security/2014/11/12/5).

  I believe that it would be better to fail safe if no DNS server is
  configured -- i.e. have DNS lookups fail; it's better that the user is
  aware of their misconfiguration, rather than silently sending their
  queries to Google.  The user can intentionally opt to use Google
  public DNS if they wish.


  Steps to reproduce:
  1. Remove existing DNS configuration (from /etc/network/interfaces, 
/etc/resolv.conf, /etc/resolvconf/resolv.conf.d/*)
  2. Reboot, or otherwise clear relevant state
  3. sudo service systemd-resolved start
  4. Note that Google's servers are listed in /run/systemd/resolve/resolv.conf
  5. If systemd-resolved is enabled in /etc/nsswitch.conf (it isn't by 
default), observe that DNS lookups probably still work, and queries are being 
sent to one of Google's servers

  
  Possible workaround/bugfix: ship a resolved.conf which clears the FallbackDNS 
parameter.

  
  This issue has been discussed in the Debian BTS 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761658).  My interpretation 
of the Debian package maintainer's position is that a user concerned with the 
privacy implications shouldn't let systemd get into a state where it uses the 
fallback DNS servers (quoting Marco 

[Touch-packages] [Bug 1351564] Re: chvt sometimes hangs, causing hibernation to fail

[Malcolm Scott]

chvt makes two ioctl calls, one to change the VT and one to wait for the
new VT to become active.  There's a race condition here; if something
changes the VT back before the second ioctl, chvt will block
indefinitely (or until something else changes to the correct VT).

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

Title:
  chvt sometimes hangs, causing hibernation to fail

Status in “kbd” package in Ubuntu:
  Confirmed

Bug description:
  This is probably in relation with bug #1350220, which deals with a
  failure in hibernation. It appears that this is caused by chvt not
  terminating a some points in the hibernation scripts. Yet I do not
  know whether the scripts or chvt are to blame.

  When I initiate an hibernation on my computer, the following
  frequently happens (about 50% of the time) :

  1. screen goes black (normal) ;
  2. instead of showing the progress of the writing of RAM to disk in console 
mode, the screen remains black ;
  3. the screensaver prompt for login appears ;
  4. after returning to desktop, I see that the network card is not functioning.

  Further debugging (PM_DEBUG=true) shows that the blocking point lies
  in 99video and is chvt 63. I tried to hibernate with --quirk-no-
  chvt. This allows the script 99video to terminate (because it does not
  try a chvt 63) and the hibernation process itself to engage. However,
  my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a
  chvt 63 too, which is not controlled by the --quirk-no-chvt.

  So I experienced again a return to desktop with a chvt process not
  progressing. I killed it and hibernation took place, without any
  visual clue. On booting the system again, thaw took place correctly
  but the system was not usable because I did not get access to a
  console (graphical or text). Indeed, the pm-suspend.log shows that
  chvt 8 did not return.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kbd 1.15.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4
  Uname: Linux 3.13.0-32-generic-tuxonice x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug  2 09:52:13 2014
  InstallationDate: Installed on 2014-07-18 (14 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  SourcePackage: kbd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/+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 1350220] Re: hibernation fails because chvt hangs

[Malcolm Scott]

There's a race in chvt (see my comment at
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1351564/comments/4)
which may be to blame.  I suspect something on my system (Nvidia
driver?) is almost always winning this race, so chvt almost always
blocks and I can't suspend.

Perhaps pm-utils should use another more-reliable way of blanking the
screen?

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

Title:
  hibernation fails because chvt hangs

Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  EDIT : initial title was hibernation fails because 99video does not
  terminate

  When I initiate an hibernation on my computer, the following
  frequently happens (about 50% of the time) :

  1. screen goes black (normal) ;
  2. instead of showing the progress of the writing of RAM to disk in console 
mode, the screen remains black ;
  3. the screensaver prompt for login appears ;
  4. after returning to desktop, I see that the network card is not functioning 
;
  5. /var/log/pm-suspend.log last line is Running hook 
/usr/lib/pm-utils/sleep.d/99video hibernate hibernate:.

  Indeed, a ps -ef | grep 99video shows that the /usr/lib/pm-
  utils/sleep.d/99video script is still running.

  If I kill this script, pm-utils logs /usr/lib/pm-
  utils/sleep.d/99video hibernate hibernate: Returned exit code 143.,
  aborts hibernation and then runs the hooks for thaw.

  I can then try again to hibernate, and it works : I never had this bug
  trigger twice in a row.

  This bug did not occur when I was running Ubuntu 12.04 and the
  corresponding kernels (but back then I was also using the video card
  driver from AMD's website instead of fglrx-updates).

  
  EDIT : further debugging (PM_DEBUG=true) shows that the blocking point in 
99video is chvt 63. I tried to hibernate with --quirk-no-chvt. This allows 
the script 99video to terminate and the hibernation process itself to engage. 
However, my hibernation module, /usr/lib/pm-utils/module.d/hibernate, does a 
chvt 63 too, which is not controlled by the --quirk-no-chvt.

  So I experienced again a return to desktop with a chvt process not
  progressing. I killed it and hibernation took place, without any
  visual clue. On booting the system again, thaw took place correctly
  but the system was not usable because I did not get access to a
  console (graphical or text). Indeed, the pm-suspend.log shows that
  chvt 8 did not return.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57~ppa1-generic-tuxonice 3.13.11.4
  Uname: Linux 3.13.0-32-generic-tuxonice x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul 30 08:47:17 2014
  InstallationDate: Installed on 2014-07-18 (11 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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