[Touch-packages] [Bug 1847183] [NEW] Intel video driver problem

[Attila Gulyas]

Public bug reported:

New to Linux/UBUNTU but expert in Windows/programming. 
Evidently my Device/Display options are very limited, when I connect a 
projector the second display can use only a low resolution, much below the 
projectors capability. I tried to check for the video driver and I got error 
messages:

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.

# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 
520] (rev 07)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompositorRunning: None
Date: Tue Oct  8 06:38:28 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a7]
   Subsystem: Dell GM108M [GeForce 930MX] [1028:07a7]
InstallationDate: Installed on 2019-10-04 (3 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 1bcf:2b96 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5480
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=372b7ab4-d94d-4af9-993d-20170a3a8fa3 ro 
resume=UUID=5876659d-5846-4aa2-a490-f4fde866001e quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.13.0
dmi.board.name: 00XT4W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn00XT4W:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5480
dmi.product.sku: 07A7
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic 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/1847183

Title:
  Intel video driver problem

Status in xorg package in Ubuntu:
  New

Bug description:
  New to Linux/UBUNTU but expert in Windows/programming. 
  Evidently my Device/Display options are very limited, when I connect a 
projector the second display can use only a low resolution, much below the 
projectors capability. I tried to check for the video driver and I got error 
messages:

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  # lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 
520] (rev 07)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Oct  8 06:38:28 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07a7]
 Subsystem: Dell GM108M [GeForce 930MX] [1028:07a7]
  InstallationDate: Installed on 2019-10-04 (3 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1bcf:2b96 

[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal

[Attila]

I have found that if I set the reboot once at 15 min, the server works
for 5-6 days. If the reboots are done once at 10 min, the server get
stuck in 24-48h max. Now I'm testing the reboots once at 20min, it
should take 10 days or more until is stuck.

Also, I have tried all "reboot=" grub options, nothing helps. The only
way to keep he server online is to set the reboot time less often. Odd!

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

I have activated RuntimeWatchdogSec=20s and ShutdownWatchdogSec=1min in
/etc/systemd/system.conf  and set the reboot, the server get stuck in
105min.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

The test server get stuck after ~9h, here is the debug log.

** Attachment added: "shutdown-log-process.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5241740/+files/shutdown-log-process.txt

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

Tested with multiple OSs, all stuck: Ubuntu 14, Fedora 29, Arch Linux
current 2019.02.01.

We received a detailed note from the next level of support with HPE and
decided to test with Ubuntu 16 (our production one) and set "ps -ef >>
/shutdown-log.txt" in to the debug.sh script. Maybe we can see something
that is not closed/terminated and prevent the server to reboot.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

This get stuck in max 5 hours. We'll try to install a non systemd
Ubuntu, like v14 to test it.

** Attachment added: "centos7.PNG"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5240612/+files/centos7.PNG

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

We installed Centos 7 and started the reboot test now. If this fail
again then is a hardware issue, if not, then it can be from Ubuntu.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

That was already tested and no luck.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

I have disabled the acpi services (acpid.path, acpid.service,
acpid.socket  and set up the reboot once at 5 min. The server get stuck
after 13h.

Something else to try?



** Attachment added: "reboot-acpi-off.zip"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5240120/+files/reboot-acpi-off.zip

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

After 5 hours of reboot the server is stuck. See the attached debug log
and ILO capture.

** Attachment added: "Ubuntu-18.zip"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5238635/+files/Ubuntu-18.zip

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

We sent all the logs and captures data to HPE and they asked to update
the BIOS to the latest one. We already using the latest firmware, 4
months past the recommended firmware. Also, we have 200 servers with
Windows 10 doing same test - reboot after each test and there are no
hangs. HPE stated that they do not have any other reports of hangs on
reboots or shutdowns for this hardware.

Any other suggestion from your side?

Meanwhile I'll do a dist-upgrade from 16.04 to 18 and do the reboot
test.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1813896] [NEW] Monitors stopped working

[Attila Fejér]

Public bug reported:

I have a Dell Latitude E7470 laptop with a docking station and two
external monitors.

I made a system update yesterday (without restart), and I tried to work
today.

When the laptop lid is laid off, all displays are black and stays that
way. When it's open, it works fine. If I lock the computer, the displays
are going black again.

Also, I cannot restart the system, it just hangs.

The only solution is to switch off the system is holding the power
button, then booting up again, with the laptop screen open.

My other colleagues with similar configurations have the same issues.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
Uname: Linux 4.15.0-44-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 30 09:58:12 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
InstallationDate: Installed on 2018-09-24 (128 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Latitude E7470
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=fd65107a-71e9-4b89-9f1e-e90f34670b9f ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.3
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic 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/1813896

Title:
  Monitors stopped working

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell Latitude E7470 laptop with a docking station and two
  external monitors.

  I made a system update yesterday (without restart), and I tried to
  work today.

  When the laptop lid is laid off, all displays are black and stays that
  way. When it's open, it works fine. If I lock the computer, the
  displays are going black again.

  Also, I cannot restart the system, it just hangs.

  The only solution is to switch off the system is holding the power
  button, then booting up again, with the laptop screen open.

  My other colleagues with similar configurations have the same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 30 09:58:12 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2018-09-24 (128 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude E7470
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=fd65107a-71e9-4b89-9f1e-e90f34670b9f ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.3
  

[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal

[Attila]

After 36h of rebooting, the system is stuck. Attached is the debug log.

** Attachment added: "shutdown-logsysd237.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5232412/+files/shutdown-logsysd237.txt

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

We will notify them if the systemd does not fix the issue. So far, after
the systemd upgrade, the server reboots fine in 24h test (reboot once at
5 min).

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

reboot=pci does not help, it get stuck after 19 hours (reboot once at 5
min). Attached is the debug log. On ILO we get the same as I sent in my
first post - see capture from the arhive.

We'll update systemd to 237 and test it.

** Attachment added: "shutdown-log-reboot-pci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5231295/+files/shutdown-log-reboot-pci.txt

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

I did not tried reboot=pci, will try now. Thanks.

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  sliu@vmlxhi-094:~$ dbus-daemon --version
  D-Bus Message Bus Daemon 1.10.6
  Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others
  This is free software; see the source for copying conditions.
  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1783499] Re: systemd: Failed to send signal

[Attila]

Here at Mozilla, we have 200 servers running on HP Moonshot system, all
have same hardware configuration and Ubuntu 16.04.2. The OS is not up to
date, we use it as is was released. We using a program to tests Firefox
source code and after each test we reboot the servers using
/sbin/reboot. After a while (between 24-48h - during this period ~6
reboots/h are made), randomly, all 200 servers get stuck at the reboot -
see the ILO capture - and to bring it back we have to power cycle each
of them.

On one of the beta servers, we have made the bellow updates/changes, set debug, 
set cron to reboot server after 5-10 min, however, the reboot freeze is still 
present:
- upgraded OS to Ubuntu 16.04.5 latest packages;
- used GRUB_CMDLINE_LINUX_DEFAULT="reboot=bios" 
- used GRUB_CMDLINE_LINUX_DEFAULT="acpi=off"
- GRUB_CMDLINE_LINUX_DEFAULT="reboot=force"
- upgraded Kernel to v4.15 (the main one from Ubuntu's repo);
- upgraded Kernel to v4.20 from https://kernel.ubuntu.com/~kernel-ppa/mainline/
- now we are testing the reboot with 4.20.3 from the above repo and working to 
update systemd.

Attached you can find the debug-log for:
- kernel 4.4.0-66-generic #87-Ubuntu - shutdown-debuglogkernel-4.4.txt
- kernel 4.15 - shutdown-log-kernel4-15.txt 
- kernel 4.20 shutdown-log-kernel420.txt
- ILO capture with the freeze ILO-reboot-freeze.PNG

Please check all this logs/capture and let us know a solution. Thanks.

** Attachment added: "UbuntuBug.zip"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5230309/+files/UbuntuBug.zip

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

Title:
  systemd: Failed to send signal

Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd: Failed to send signal.

  [3.137257] systemd[1]: Failed to send job remove signal for 109: 
Connection reset by peer
  [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change 
signal for run-rpc_pipefs.mount: Transport endpoint is not connected
  [3.142719] systemd[1]: Failed to send job remove signal for 134: 
Transport endpoint is not connected
  [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit 
change signal for auth-rpcgss-module.service: Transport endpoint is not 
connected
  [3.165359] systemd[1]: Failed to send job remove signal for 133: 
Transport endpoint is not connected
  [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed 
to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: 
Transport endpoint is not connected
  [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport 
endpoint is not connected
  [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change 
signal for proc-fs-nfsd.mount: Transport endpoint is not connected
  [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit 
change signal for systemd-modules-load.service: Transport endpoint is not 
connected
  [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport 
endpoint is not connected
  [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit 
change signal for systemd-random-seed.service: Transport endpoint is not 
connected
  [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: 
Failed to send unit change signal for 
sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not 
connected
  [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change 
signal for dev-ttyS12.device: Transport endpoint is not connected
  [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send 
unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by 
peer
  [3.547144] systemd[1]: Failed to send job change signal for 207: 
Transport endpoint is not connected

  
  How to reproduce:
  1. enable debug level journal
  LogLevel=debug in /etc/systemd/system.conf
  2. reboot the system
  3. journalctl | grep "Failed to send"

  
  sliu@vmlxhi-094:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  sliu@vmlxhi-094:~$ systemctl --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

[Touch-packages] [Bug 1746741] Re: cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

UPDATES that could have caused the work-space switcher to malfunction:

Start-Date: 2018-02-01  00:51:22
Commandline: (hidden)
Upgrade: libwebkit2gtk-4.0-37:i386 (2.18.5-0ubuntu0.16.04.1, 
2.18.6-0ubuntu0.16.04.1), gir1.2-webkit2-4.0:i386 (2.18.5-0ubuntu0.16.04.1, 
2.18.6-0ubuntu0.16.04.1), libjavascriptcoregtk-4.0-18:i386 
(2.18.5-0ubuntu0.16.04.1, 2.18.6-0ubuntu0.16.04.1), 
libwebkit2gtk-4.0-37-gtk2:i386 (2.18.5-0ubuntu0.16.04.1, 
2.18.6-0ubuntu0.16.04.1), gir1.2-javascriptcoregtk-4.0:i386 
(2.18.5-0ubuntu0.16.04.1, 2.18.6-0ubuntu0.16.04.1)
End-Date: 2018-02-01  00:51:27

Start-Date: 2018-01-29  21:21:35
Commandline: (hidden)
Upgrade: libmpx0:i386 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), 
libgcc-5-dev:i386 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), cpp-5:i386 
(5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libitm1:i386 
(5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libcilkrts5:i386 
(5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libasan2:i386 
(5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), libquadmath0:i386 
(5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), 
thunderbird-gnome-support:i386 (1:52.5.0+build1-0ubuntu0.16.04.1, 
1:52.6.0+build1-0ubuntu0.16.04.1), gcc-5-base:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), libstdc++-5-dev:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), libubsan0:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), g++-5:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), thunderbird-locale-en-gb:i386 
(1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1), 
libgfortran3:i386 (5.4.0-6ubuntu1~16.04.5, 5.4.0-6ubuntu1~16.04.6), 
thunderbird-locale-en-us:i386 (1:52.5.0+build1-0ubuntu0.16.04.1, 
1:52.6.0+build1-0ubuntu0.16.04.1), gcc-5:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), libgomp1:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), thunderbird:i386 (1:52.5.0+build1-0ubuntu0.16.04.1, 
1:52.6.0+build1-0ubuntu0.16.04.1), libatomic1:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), libcc1-0:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), libstdc++6:i386 (5.4.0-6ubuntu1~16.04.5, 
5.4.0-6ubuntu1~16.04.6), thunderbird-locale-en:i386 
(1:52.5.0+build1-0ubuntu0.16.04.1, 1:52.6.0+build1-0ubuntu0.16.04.1)
End-Date: 2018-01-29  21:21:53

Start-Date: 2018-01-27  09:48:36
Commandline: (hidden)
Upgrade: libfwup0:i386 (0.5-2ubuntu5, 0.5-2ubuntu7), libtasn1-doc:i386 
(4.7-3ubuntu0.16.04.2, 4.7-3ubuntu0.16.04.3), update-notifier-common:i386 
(3.168.5, 3.168.7), fwupdate:i386 (0.5-2ubuntu5, 0.5-2ubuntu7), 
chromium-browser:i386 (63.0.3239.84-0ubuntu0.16.04.1, 
63.0.3239.132-0ubuntu0.16.04.1), firefox-locale-en:i386 
(57.0.4+build1-0ubuntu0.16.04.1, 58.0+build6-0ubuntu0.16.04.1), 
chromium-codecs-ffmpeg-extra:i386 (63.0.3239.84-0ubuntu0.16.04.1, 
63.0.3239.132-0ubuntu0.16.04.1), libtasn1-6-dev:i386 (4.7-3ubuntu0.16.04.2, 
4.7-3ubuntu0.16.04.3), libgcab-1.0-0:i386 (0.7-1, 0.7-1ubuntu0.1), firefox:i386 
(57.0.4+build1-0ubuntu0.16.04.1, 58.0+build6-0ubuntu0.16.04.1), rsync:i386 
(3.1.1-3ubuntu1.1, 3.1.1-3ubuntu1.2), linux-firmware:i386 (1.157.14, 1.157.15), 
libtasn1-6:i386 (4.7-3ubuntu0.16.04.2, 4.7-3ubuntu0.16.04.3), 
chromium-browser-l10n:i386 (63.0.3239.84-0ubuntu0.16.04.1, 
63.0.3239.132-0ubuntu0.16.04.1), fwupdate-signed:i386 (1.11.1+0.5-2ubuntu5, 
1.11.3+0.5-2ubuntu7), update-notifier:i386 (3.168.5, 3.168.7)
End-Date: 2018-01-27  09:50:12

I believe it shouldn't have been an earlier update than 27th January.

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

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1746741] Re: cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

RE: 64-bit version OS

Hi christopher,

So, you're recommending that I abandon this bug report? Meaning that
there is no hope of being fixed? :)

I will consider shifting to 64-bit, I did in the past, only that some
thoughts are still holding me back.

Many thanks!

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

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S0JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: AH509827
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B7S0JC01
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb  1 14:11:17 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12350 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746741/+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 1746741] Re: cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

Hi again, Christopher,

Thanks for the tip! /var/log/apt is only listing some updates from the
2nd February, so that is now too helpful.

I however found my way around in Ubuntu Software Center and was able to
locate the updates by date, however, I can't exactly recall which day it
was that ruined the work-space changing. Is it safe to just copy and
post here all the updates by date? (going back a couple of days only?)

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

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S0JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: AH509827
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B7S0JC01
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb  1 14:11:17 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12350 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746741/+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 1746741] Re: cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

RE: http://cdimage.ubuntu.com/daily-live/current/

I am currently using a 32 bit version still (because of an older version
of truecrypt).

Do you, Christopher, think that if I set up bionic-desktop-amd64.iso on
a usb stick and boot to try out Ubuntu, I will be able to test the
desktop work-space switching? (as far as I remember, in the try mode,
there are no work-spaces after boot)?

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

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S0JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: AH509827
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B7S0JC01
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb  1 14:11:17 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12350 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746741/+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 1746741] Re: cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

Hi Christopher, I would like, however I can not remember, sorry. If I am
not mistaking, there was an update (the update window popped up) with
only a few KB in size... the usual "Ubuntu base" ?

If there is any way of me figuring out how o answer your question,
please let me know and I will do my best.

It is super annoying to have this work-space switching issue still on my
laptop.

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

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S0JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: AH509827
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B7S0JC01
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb  1 14:11:17 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12350 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746741/+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 1746741] Re: cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

I forgot to mention that if I am on a workspace and I click the browser
on my launchpad (the browser is already open on another workspace) then
actually nothing happens now...I used to be sent to the workspace the
browser is open, however NOW... nothing... I have to manually switch to
the workspace, using the mouse.

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

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20B7S0JC01
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: AH509827
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20B7S0JC01
  dmi.product.version: ThinkPad T440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb  1 14:11:17 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12350 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746741/+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 1746741] [NEW] cannot switch between workspaces with ctrl alt arrow after one update

[Attila]

Public bug reported:

Hello!

After the update manager popped up and I've done the update, it seems
that the ctrl alt arrows are no longer working to switch between the
workspaces?

I can still switch by using the mouse andthe icon on the launcher, it
just takes more time and Idislike that.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
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: Thu Feb  1 14:18:35 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
InstallationDate: Installed on 2015-08-06 (910 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
MachineType: LENOVO 20B7S0JC01
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=9658f381-e022-4f56-b2bb-b493ccdc4c3b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20B7S0JC01
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.asset.tag: AH509827
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20B7S0JC01:pvrThinkPadT440:rvnLENOVO:rn20B7S0JC01:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20B7S0JC01
dmi.product.version: ThinkPad T440
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
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.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Feb  1 14:11:17 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12350 
 vendor AUO
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 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/1746741

Title:
  cannot switch between workspaces with ctrl alt arrow after one update

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello!

  After the update manager popped up and I've done the update, it seems
  that the ctrl alt arrows are no longer working to switch between the
  workspaces?

  I can still switch by using the mouse andthe icon on the launcher, it
  just takes more time and Idislike that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  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: Thu Feb  1 14:18:35 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2015-08-06 (910 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: LENOVO 20B7S0JC01
  ProcEnviron:
   LANGUAGE=en_GB:en
   

[Touch-packages] [Bug 1719963] [NEW] package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 139 hibakóddal kilépett

[László Attila]

Public bug reported:

 Applicatin crashes on login

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shared-mime-info 1.5-2ubuntu0.1
Uname: Linux 4.13.4-041304-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Sep 27 09:34:46 2017
ErrorMessage: telepítve post-installation parancsfájl alfolyamat 139 hibakóddal 
kilépett
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
telepítve post-installation parancsfájl alfolyamat 139 hibakóddal kilépett
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (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 shared-mime-info in
Ubuntu.
https://bugs.launchpad.net/bugs/1719963

Title:
  package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade:
  telepítve post-installation parancsfájl alfolyamat 139 hibakóddal
  kilépett

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
   Applicatin crashes on login

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: shared-mime-info 1.5-2ubuntu0.1
  Uname: Linux 4.13.4-041304-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 27 09:34:46 2017
  ErrorMessage: telepítve post-installation parancsfájl alfolyamat 139 
hibakóddal kilépett
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.5-2ubuntu0.1 failed to install/upgrade: 
telepítve post-installation parancsfájl alfolyamat 139 hibakóddal kilépett
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1719963/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

** Attachment added: "mem.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4649398/+files/mem.txt

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This bug is resolved.  Do not follow up to this bug.  Shutdown bugs
  are specific to the software installed and its configuration.  If you
  are experiencing a shutdown hang, please file a separate bug report
  and follow the debugging instructions described in the "Debugging
  boot/shutdown problems" section of
  /usr/share/doc/systemd/README.Debian.gz to check if there are any
  hanging jobs at shutdown. Capturing a screen photo of "journalctl -b"
  in the rescue shell might be enlightening.

  [Original report]
  I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth 
shutdown screen.  Hitting esc to reveal the console showed a normal set of 
shutdown messages, ending with 'Reached target Shutdown' (paraphrased from 
memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

This still happens in 16.04 LST! As it was described several times above
the shutdown process somehow blocks/gets in a deadlock when un-mounting
the swap partitions. I did not understood exactly what happens but the
recovery console clearly shows that the swap space is still on and
vailable and there are four .swap jobs "running" (although I have a
single swap partition).

PS: The "Fix Released" status suggest for me that some work was done to
fix this issue, which supposes that the issue was clearly understood.
This is obiviously not the case here.

** Attachment added: "jobs.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4649397/+files/jobs.txt

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This bug is resolved.  Do not follow up to this bug.  Shutdown bugs
  are specific to the software installed and its configuration.  If you
  are experiencing a shutdown hang, please file a separate bug report
  and follow the debugging instructions described in the "Debugging
  boot/shutdown problems" section of
  /usr/share/doc/systemd/README.Debian.gz to check if there are any
  hanging jobs at shutdown. Capturing a screen photo of "journalctl -b"
  in the rescue shell might be enlightening.

  [Original report]
  I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth 
shutdown screen.  Hitting esc to reveal the console showed a normal set of 
shutdown messages, ending with 'Reached target Shutdown' (paraphrased from 
memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+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 1572357] Re: filelight crashed with SIGSEGV in operator&() on closing lid

[Fenyvesi Attila]

cantor and gwenview also crashes when closing the lid of the laptop.

** Information type changed from Private to Public

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

Title:
  filelight crashed with SIGSEGV in operator&() on closing lid

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Closing the laptop lid (HP Probook 6470b) causes Qt-based programmes to 
crash. 
  Similar bug reports:
  vlc - https://bugs.launchpad.net/bugs/1572313
  texmaker - https://bugs.launchpad.net/bugs/1520826

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: filelight 4:15.08.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr 20 02:35:11 2016
  ExecutablePath: /usr/bin/filelight
  InstallationDate: Installed on 2014-12-04 (502 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcCmdline: filelight
  SegvAnalysis:
   Segfault happened at: 0x7fa5a81f4271 
<_ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPointiP8QPainterP19QWidgetBackingStore+2961>:
 mov0x28(%rax),%rax
   PC (0x7fa5a81f4271) ok
   source "0x28(%rax)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: filelight
  StacktraceTop:
   QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, 
int, QPainter*, QWidgetBackingStore*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList 
const&, int, QRegion const&, QPoint const&, int, QPainter*, 
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList 
const&, int, QRegion const&, QPoint const&, int, QPainter*, 
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList 
const&, int, QRegion const&, QPoint const&, int, QPainter*, 
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
   QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList 
const&, int, QRegion const&, QPoint const&, int, QPainter*, 
QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  Title: filelight crashed with SIGSEGV in QWidgetPrivate::drawWidget()
  UpgradeStatus: Upgraded to wily on 2016-02-05 (74 days ago)
  UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare scanner sudo video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1572357/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

@dino99:
The problem is present in Xenial. Nothing changed after I upgraded to Ubuntu 
16.04 LTS preview.

** Tags added: xenial

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

Title:
  reboot hangs at 'Reached target Shutdown'

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

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

I'm just wondering if we could set some timeout for the shutdown in the
systemd configuration files.

I tried to add the following to the /usr/lib/systemd/user/shutdown.target 
config:
JobTimeoutSec=30
JobTimeoutAction=poweroff-force

but unfortunately it has no effect.

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

Title:
  reboot hangs at 'Reached target Shutdown'

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

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

I can confirm too that the issue is probably something to do with the
swap usage.

My first guess was that the problem has something to do with the
system's update, but seems that real cause is the swap usage. The
shutdown usually goes fine when the system is used only for a short time
and fails after a couple of hours of usage, when the system accumulates
some data in the swap.

I did today some test and I got the following result:
~10 hours uptime (idle), 45 MB swap usage - the showdown went fine
~50 min uptime, 2.2 GB swap usage - the showdown hangs

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

Title:
  reboot hangs at 'Reached target Shutdown'

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

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

** Attachment removed: "Shutdown process (without splash screen)"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4512903/+files/shutdown.png

** Attachment added: "Shutdown process (without splash screen)"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4515266/+files/shutdown.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/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1464917] Re: reboot hangs at 'Reached target Shutdown'

[Tőkés Attila]

I can confirm that happens with 15.10 too.

Attached a screenshot that shows a successful shutdown process (without
splash screen). The red line marks the moment where the process hangs if
the shutdown fails.

The workaround with the SysRq key presented here worked for me:
http://askubuntu.com/a/674209/93513

** Attachment added: "Shutdown process (without splash screen)"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+attachment/4512903/+files/shutdown.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/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917/+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 1319626] Re: Ubuntu One Captcha too hard to enter correctly

[Csipak Attila]

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

** This bug has been marked a duplicate of bug 1033598
   the CAPTCHA challenge in Ubuntu Software Center is much too difficult to 
solve for a real human being

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

Title:
  Ubuntu One Captcha too hard to enter correctly

Status in ubuntuone-client-data package in Ubuntu:
  Confirmed

Bug description:
  I tried to create a new Ubuntu One while setting up the Sofware Center
  suggested apps  (which required an Ubuntu One account) and ended
  frustated.

  The Captcha is really hard, I gave up on the account creation after 10
  tries, I'm a male on my twentys with normal vision and could not
  decipher the Captcha.

  Not even 4***.org captchas gives me troubles as those on the Ubuntu
  One register page.

  I suggest to improve the captchas so they're not so difficult to read,
  I can just imagie my dad would just close that window if he saw such a
  hard captcha.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntuone-client-data 13.05-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 14 21:29:17 2014
  Dependencies:
   
  InstallationDate: Installed on 2014-05-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntuone-client-data
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client-data/+bug/1319626/+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 1413600] Re: Cannot silence an incoming call with volume keys

[Attila Fülöp]

Same on BQ E4.5 with latest firmware

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

Title:
  Cannot silence an incoming call with volume keys

Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  This bug was found during regression testing.

  0. Make sure the phone is not in silent mode
  1. Create an incoming call
  2. While the DUT is playing ringtone, press volume down key

  What happens:
  The volume level is decreased but the ringtone keeps playing.

  What should happen:
  The phone should silence.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: telephony-service 0.1+15.04.20150113~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Thu Jan 22 18:32:20 2015
  InstallationDate: Installed on 2015-01-22 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150122-030204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1413600/+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 1414494] Re: reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41 Express chipset

[Csipak Attila]

Looks like today's ubuntu updates fixed the bug, which is strange. The
/var/log/apt/history.log entry produced by the update is:

Start-Date: 2015-02-03  22:51:31
Commandline: aptdaemon role='role-commit-packages' sender=':1.136'
Install: linux-image-extra-3.13.0-45-generic:amd64 (3.13.0-45.74), 
linux-image-3.13.0-45-generic:amd64 (3.13.0-45.74), 
linux-headers-3.13.0-45-generic:amd64 (3.13.0-45.74), 
linux-headers-3.13.0-45:amd64 (3.13.0-45.74)
Upgrade: linux-headers-generic:amd64 (3.13.0.44.51, 3.13.0.45.52), 
python3-software-properties:amd64 (0.92.37.2, 0.92.37.3), unzip:amd64 
(6.0-9ubuntu1.1, 6.0-9ubuntu1.2), software-properties-common:amd64 (0.92.37.2, 
0.92.37.3), linux-libc-dev:amd64 (3.13.0-44.73, 3.13.0-45.74), 
software-properties-gtk:amd64 (0.92.37.2, 0.92.37.3), linux-image-generic:amd64 
(3.13.0.44.51, 3.13.0.45.52), linux-generic:amd64 (3.13.0.44.51, 3.13.0.45.52)
End-Date: 2015-02-03  22:53:23

At first glance, I thought that the 3.13.0-45 kernel version fixed it.
But then I rebooted into kernel version 3.13.0-44, and couldn't
reproduce the original bug, neither. What caused the bug and what solved
it?

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

** Changed in: upstart (Ubuntu)
   Status: New = Incomplete

** Changed in: upstart (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41
  Express chipset

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid

Bug description:
  This bug is pretty similar to the one described in #1409279: shutdown
  from GUI results in shutdown, some seconds of silence, then reboot.
  Hardware shutdown (holding power button for 4 secs) works OK.

  Last kernel update happened on 2015.01.10, but I just started noticing
  this bug today (2015.01.25), so it may not be a kernel issue.

  WORKAROUND: shutdown -H

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-44-generic 3.13.0-44.73
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  corphicks   1877 F pulseaudio
   /dev/snd/controlC0:  corphicks   1877 F pulseaudio
   /dev/snd/controlC1:  corphicks   1877 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 25 22:20:00 2015
  HibernationDevice: RESUME=UUID=cf5c04c0-7bdb-41f5-b91c-6c9bb0fdaf90
  InstallationDate: Installed on 2014-04-30 (270 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P41T-D3
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=2e1f47f8-1d20-48a6-9354-5ba871c8bfc8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: P41T-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnP41T-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP41T-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P41T-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1414494/+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 1414494] Re: reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41 Express chipset

[Csipak Attila]

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

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

Title:
  reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41
  Express chipset

Status in linux package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  New

Bug description:
  This bug is pretty similar to the one described in #1409279: shutdown
  from GUI results in shutdown, some seconds of silence, then reboot.
  Hardware shutdown (holding power button for 4 secs) works OK.

  Last kernel update happened on 2015.01.10, but I just started noticing
  this bug today (2015.01.25), so it may not be a kernel issue.

  WORKAROUND: shutdown -H

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-44-generic 3.13.0-44.73
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  corphicks   1877 F pulseaudio
   /dev/snd/controlC0:  corphicks   1877 F pulseaudio
   /dev/snd/controlC1:  corphicks   1877 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 25 22:20:00 2015
  HibernationDevice: RESUME=UUID=cf5c04c0-7bdb-41f5-b91c-6c9bb0fdaf90
  InstallationDate: Installed on 2014-04-30 (270 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P41T-D3
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=2e1f47f8-1d20-48a6-9354-5ba871c8bfc8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: P41T-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnP41T-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP41T-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P41T-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1414494/+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 1414494] Re: reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41 Express chipset

[Csipak Attila]

Since we are not sure if this is a kernel issue, I added upstart to the
affected projects.

If someone from the upstart maintainers is able to cross out upstart as
the source of the bug, then I will open an upstream bug report against
the latest kernel.

To penalvch: halting instead of poweroff is not really a workaround
IMHO. (Maybe you meant shutdown -H, then power off via power button?)

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

Title:
  reboot after shutdown Gigabyte GA-P41T-D3 motherboard, Intel G41
  Express chipset

Status in linux package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  New

Bug description:
  This bug is pretty similar to the one described in #1409279: shutdown
  from GUI results in shutdown, some seconds of silence, then reboot.
  Hardware shutdown (holding power button for 4 secs) works OK.

  Last kernel update happened on 2015.01.10, but I just started noticing
  this bug today (2015.01.25), so it may not be a kernel issue.

  WORKAROUND: shutdown -H

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-44-generic 3.13.0-44.73
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  corphicks   1877 F pulseaudio
   /dev/snd/controlC0:  corphicks   1877 F pulseaudio
   /dev/snd/controlC1:  corphicks   1877 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 25 22:20:00 2015
  HibernationDevice: RESUME=UUID=cf5c04c0-7bdb-41f5-b91c-6c9bb0fdaf90
  InstallationDate: Installed on 2014-04-30 (270 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P41T-D3
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=2e1f47f8-1d20-48a6-9354-5ba871c8bfc8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: P41T-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd05/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnP41T-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP41T-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P41T-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1414494/+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 1008216] Re: subdownloader disappears from dash just after start

[Csipak Attila]

Could not reproduce it on Ubuntu 14.04.1 + subdownloader 2.0.14-1.1.

(BTW, the original report was filed against Ubuntu 12.04 LTS, which is
still supported... whatever... if no one bothered to confirm it for 1.5
years, I won't care neither.)

** Changed in: unity
   Status: Incomplete = Invalid

** Changed in: subdownloader (Ubuntu)
   Status: Incomplete = Invalid

** Changed in: unity (Ubuntu)
   Status: Incomplete = Invalid

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

Title:
  subdownloader disappears from dash just after start

Status in Unity:
  Invalid
Status in subdownloader package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  If I start subdownloader from dash home, the application window comes
  up and the icon appears on the dash bar, then, after less than 1 sec
  the icon disappears (at about the same time when the login popup
  appears over the subdownloader main window). The icon never ever
  appears, so if I minimize the subdownloader main window, the
  application will keep running but it won't be visible anymore to the
  average user. (Or even me - I just noticed that I had 4 instances of
  it running...)

  If subdownloader is started from gnome-terminal, the bug doesn't
  appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: subdownloader 2.0.14-1, unity 5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
  Uname: Linux 3.2.0-24-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CheckboxSubmission: e665592ec356650b8c1e4f41698ed522
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Sun Jun  3 22:13:23 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301)
  PackageArchitecture: all
  SourcePackage: subdownloader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1008216/+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 1377698] Re: /etc/default/rcS: UTC=no is being ignored

[Attila Hammer]

Not need applying a similar fix with Ubuntu Trusty? Ubuntu Trusty handle good 
the UTc=no setting?
Possible I missunderstand the issue, but if I get dmesg|grep clock command, I 
see following style output:
[1.348720] rtc_cmos 00:02: setting system clock to 2014-10-26 14:54:33 UTC 
(1414335273)
Because I using both Ubuntu and Windows, I set UTC=no setting into 
/etc/default/RCS file.
Because now happened a time zone change (I using Europe/budapest timezone), I 
ran hwclock -w --localtime command.
Next clock change need in europe/budapest timezone with 2015. last march sunday.

Attila

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

Title:
  /etc/default/rcS: UTC=no is being ignored

Status in “util-linux” package in Ubuntu:
  Fix Released

Bug description:
  This causes the greeter time to display utc  sets system time to utc
  Affects users who are in a different timezone
  Also affects users who dual boot with windows, their time will be off by 
amount different from utc to their time zone

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: initscripts 2.88dsf-41ubuntu18
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct  5 14:16:48 2014
  InstallationDate: Installed on 2014-10-05 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923)
  SourcePackage: sysvinit
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rcS: 2014-10-05T10:58:21.042693

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1377698/+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 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostp

[Attila Szász]

Thank you Julien at #7, you saved my day!

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

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libpostproc” package in Ubuntu:
  Confirmed

Bug description:
   -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Mar  3 00:57:47 2014
  Dependencies:
   gcc-4.9-base 4.9-20140222-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown]
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140222-0ubuntu1
   multiarch-support 2.19-0ubuntu2
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2013-12-12 (79 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to 
install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago)

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