[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2019-11-23 Thread Launchpad Bug Tracker
This bug was fixed in the package lvm2 - 2.03.02-2ubuntu7

---
lvm2 (2.03.02-2ubuntu7) focal; urgency=medium

  * Include raid1 in the list of modules installed by the initramfs hook,
as this is not a kernel module dependency of dm-raid but if the user's
root disk is configured as RAID1 it is definitely required.
Closes: #841423, LP: #1509717.

 -- Steve Langasek   Fri, 22 Nov 2019
13:59:47 -0800

** Changed in: lvm2 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  New
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Triaged
Status in lvm2 package in Debian:
  Incomplete

Bug description:
  After upgrading to Wily, raid1 LVs don't activate during the initrd
  phase. Since the root LV is also RAID1-mirrored, the system doesn't
  boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-23 Thread John Hartley
Paul & Co,

I have raised as "possible" kernel fix required here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721

Cheers,

Zebity

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+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 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-23 Thread John Hartley
Hi Paul,

thanks for pointing out upstream kernel update.

Where would this get pulled through into Ubuntu ?

To close this off I believe we should link to to either pending pull
request or raise as issue with Kernel to get pull request into Ubuntu
going.

This bug is currently in org, but looks like it needs to be linked to
something in kernel somewhere ...

Cheers,

Zebity

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+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 1853714] Re: libpam-runtime misconfigurred module option in /etc/pam.d/sshd

2019-11-23 Thread Steve Langasek
This file is from the openssh package, not from pam.  Reassigning.

> Current version runs update of dynamic part of motd on every login
> by ssh, what is slowing it significantly and clearly is not what author had 
> in mind.

It is not intended that it significantly slow the login.  But it is
intended that the motd always be up to date when shown to the user at
login.  So calling pam_motd.so only with 'noupdate' is certainly not the
expected behavior.

The current design of update-motd is that each of the individual scripts
installed in /etc/update-motd.d are expected to ensure that they have a
reasonable up-to-date local cache of their information in the common
case which is updated out of band, such that the motd updating only has
to run a short sequence of shell scripts to concatenate information into
the motd file.  If you have an /etc/update-motd.d script that is not
behaving this way, please help us identify which it is so that we can
resolve this.

I don't think there is actually a bug in the contents of
/etc/pam.d/sshd.

** Package changed: pam (Ubuntu) => openssh (Ubuntu)

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

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

Title:
  libpam-runtime misconfigurred module option in /etc/pam.d/sshd

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version:  Ubuntu 18.04.3 LTS
  libpam-runtime: 1.1.8-3.6ubuntu2.18.04.1

  In file /etc/pam.d/sshd there is part:

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  sessionoptional pam_motd.so  motd=/run/motd.dynamic
  sessionoptional pam_motd.so noupdate

  
  but it should be:

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  sessionoptional pam_motd.so noupdate motd=/run/motd.dynamic

  
  Current version runs update of dynamic part of motd on every login by ssh, 
what is slowing it significantly and clearly is not what author had in mind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1853714/+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 1853714] [NEW] libpam-runtime misconfigurred module option in /etc/pam.d/sshd

2019-11-23 Thread Harvald
Public bug reported:

Ubuntu version:  Ubuntu 18.04.3 LTS
libpam-runtime: 1.1.8-3.6ubuntu2.18.04.1

In file /etc/pam.d/sshd there is part:

# Print the message of the day upon successful login.
# This includes a dynamically generated part from /run/motd.dynamic
# and a static (admin-editable) part from /etc/motd.
sessionoptional pam_motd.so  motd=/run/motd.dynamic
sessionoptional pam_motd.so noupdate


but it should be:

# Print the message of the day upon successful login.
# This includes a dynamically generated part from /run/motd.dynamic
# and a static (admin-editable) part from /etc/motd.
sessionoptional pam_motd.so noupdate motd=/run/motd.dynamic


Current version runs update of dynamic part of motd on every login by ssh, what 
is slowing it significantly and clearly is not what author had in mind.

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

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

Title:
  libpam-runtime misconfigurred module option in /etc/pam.d/sshd

Status in pam package in Ubuntu:
  New

Bug description:
  Ubuntu version:  Ubuntu 18.04.3 LTS
  libpam-runtime: 1.1.8-3.6ubuntu2.18.04.1

  In file /etc/pam.d/sshd there is part:

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  sessionoptional pam_motd.so  motd=/run/motd.dynamic
  sessionoptional pam_motd.so noupdate

  
  but it should be:

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  sessionoptional pam_motd.so noupdate motd=/run/motd.dynamic

  
  Current version runs update of dynamic part of motd on every login by ssh, 
what is slowing it significantly and clearly is not what author had in mind.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1853714/+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 1563781] Re: Flickering and invisible mouse pointer after wakeup from suspend

2019-11-23 Thread Dominik Schrempf
I have a new laptop (X270) and cannot confirm this issue anymore.

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

Title:
  Flickering and invisible mouse pointer after wakeup from suspend

Status in Light Display Manager:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I run Arch linux on a Thinkpad X230

  uname -a
  Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 
x86_64 GNU/Linux

  I use xmonad and a custom .xinitrc to start my session.  I run `light-
  locker --lock-on-suspend` there and xmonad.

  - When I wake up my laptop from suspend, the login screen shows up as 
expected.
  - After about 2 second, the screen flickers once and the login screen shows 
up again.
  - If I start typing a password before the flickering, the input field will be 
reset upon flickering.  Usually I end up with my password half-typed and a 
wrong password notice.
  - After logging back into the session, there is no mouse pointer.
  - Going to VT1 and back to VT7 restores the pointer.

  Please find the lightdm and journalctl logs below.  I am happy to
  provide more logs and info.

  Thanks,
  Dominik

  The lightdm log:
  [+14840.86s] DEBUG: Seat seat0: Creating greeter session
  [+14840.86s] DEBUG: Seat seat0: Creating display server of type x
  [+14840.86s] DEBUG: Using VT 8
  [+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8
  [+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to 
/run/lightdm/root/:1
  [+14840.86s] DEBUG: DisplayServer x-1: Launching X Server
  [+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth 
/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
  [+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server 
:1
  [+14841.11s] DEBUG: Seat seat0 changes active session to 
  [+14841.36s] DEBUG: Got signal 10 from process 16458
  [+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1
  [+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1
  [+14841.36s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
  [+14841.36s] DEBUG: Session pid=16473: Started with service 
'lightdm-greeter', username 'lightdm'
  [+14841.37s] DEBUG: Session pid=16473: Authentication complete with return 
value 0: Success
  [+14841.37s] DEBUG: Seat seat0: Session authenticated, running command
  [+14841.37s] DEBUG: Session pid=16473: Running command 
/usr/sbin/lightdm-gtk-greeter
  [+14841.37s] DEBUG: Creating shared data directory 
/var/lib/lightdm-data/lightdm
  [+14841.37s] DEBUG: Session pid=16473: Logging to 
/var/log/lightdm/x-1-greeter.log
  [+14841.41s] DEBUG: Activating VT 8
  [+14841.41s] DEBUG: Locking login1 session c2
  [+14841.41s] DEBUG: Activating login1 session c16
  [+14841.41s] DEBUG: Seat seat0 changes active session to c16
  [+14841.41s] DEBUG: Session c16 is already active
  [+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 
resettable=false
  [+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for 
dominik
  [+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', 
username 'dominik'
  [+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM
  [+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s)
  [+14846.18s] DEBUG: Session pid=16473: Continue authentication
  [+14846.20s] DEBUG: Session pid=16510: Authentication complete with return 
value 0: Success
  [+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: 
Success
  [+14846.20s] DEBUG: Session pid=16473: User dominik authorized
  [+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8
  [+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik
  [+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik
  [+14846.26s] DEBUG: Unlocking login1 session c2
  [+14846.26s] DEBUG: Activating VT 7
  [+14846.45s] DEBUG: Seat seat0: Stopping greeter
  [+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM
  [+14846.45s] DEBUG: Activating login1 session c2
  [+14846.46s] DEBUG: Session pid=16510: Exited with return value 0
  [+14846.46s] DEBUG: Seat seat0: Session stopped
  [+14846.46s] DEBUG: Seat seat0 changes active session to c2
  [+14846.46s] DEBUG: Session c2 is already active
  [+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel
  [+14846.50s] DEBUG: Session pid=16473: Exited with return value 0
  [+14846.50s] DEBUG: Seat seat0: Session stopped
  [+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require 
it
  [+14846.50s] DEBUG: Sending signal 15 to process 16458
  [+14846.51s] DEBUG: Process 16458 exited with return value 0
  [+14846.51s] DEBUG: DisplayServer x-1: X server 

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2019-11-23 Thread Kent Lion
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

I'm posting here instead of the bug at: https://bugs.launchpad.net/bugs/1676547
because it got me on the path that may have solved the problem (time will tell).
My /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf also 
contained:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan
When I cleared it out and rebooted, it was still empty and the problem was 
still there. At that point, I noticed that when I clicked on the Network 
Manager applet (↑↓) it displayed the lines:
Ethernet Network (gray title)
Wired connection 1
Disconnect
enp0s25
VPN Connections
Enable Networking (checkbox)
Connection Information
Edit Connections...

But the machine has only one ethernet card, so I chose Edit Connections... and 
changed the connection name to the device name enp0s25. Using ifdown -a worked 
fine, but ifup -a gave me a long pause followed by:
sudo unable to resolve host [hostname]: Resource temporarily unavailable
When I then clicked on the Network Manager applet it showed enp0s25 above AND 
below Disconnect. When I then clicked Disconnect and then clicked enp0s25, it 
reconnected just fine. If I delete or restore the original 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf, it stops 
working; the file must be empty. On the machine I'm typing this on (also 
updated Bionic 64), 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is not empty, 
but I don't do file sharing on it. Now that the other machine is working, I 
find I can access its shared folders on my network without a problem.

So this bug probably has more than one cause. It's as if network
connection information is being taken from at least 2 different
locations, and one or more of them has/have been forgotten but should be
gone.

I do note that when I click Edit Connections... the connection
information does not necessarily agree with what's in
/etc/network/interfaces, in particular netmask refuses to keep the value
255.255.255.0 and reverts to 24 (could 24 refer to /24 in
192.168.15.109/24 ?), which is not the netmask /etc/network/interfaces
requires for a static IP setting.

My problem began with a clean install from a freshly downloaded ISO of
Xubuntu 18.04 LTS 64 bit desktop (not server). Networking and Internet
worked, but while setting it up for file sharing over the network (as
the machine it replaced had done), I eventually lost all network access,
and the network manager applet refused to connect, even when it said it
"connection established"...before changing to say "disconnected". I
previously reported a bug that suddenly disappeared by itself for a few
months and that then recently reappeared: after some minutes connected
to the Internet, my network connection would suddenly disconnect, and
I'd have to reconnect it in the Network Manager applet. So I just made
the change to it's name on that machine, and we'll see if that solves
the problem or not (it's a pain to reproduce, because it requires
rebooting and waiting an unknown amount of time.

Getting file sharing in Linux is like finding an Android app: multiple
choices to try, only to discover that none (or almost none) does the
minimum that is reasonable to expect from it.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+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 1685754] Re: gnome-terminal unduly forces umask=0022

2019-11-23 Thread David
Is there any workaround for Nautilus?
I tried with /etc/systemd/user/nautilus.service.d/umask.conf and 
/etc/systemd/user/Nautilus.service.d/umask.conf but nothing seems to work.
Thanks in advance!

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

Title:
  gnome-terminal unduly forces umask=0022

Status in gedit:
  Invalid
Status in gnome-session:
  New
Status in GNOME Terminal:
  Unknown
Status in Nautilus:
  Confirmed
Status in dbus package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  In order to set the default umask of my users to 027 or 007, I
  followed the instructions provided in 'man pam_umask' :

  In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
  'umask=007' (for myself).

  Then, MOST graphical applications systematically run with the correct
  umask.

  In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
  it systematically displays 0007.

  But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
  it systematically displays 0022.

  That is BAD, and is a security issue.

  
  Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
  UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
  if  [ "$UMASK" ];  then
umask  "${UMASK#$USER:*,umask=}"
  fi

  
  In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.

  Thank you in advance for a quick correction.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 24 08:36:58 2017
  InstallationDate: Installed on 2017-03-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+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 1742482] Re: firefox is used to open ftp share files

2019-11-23 Thread Janghou
Ubuntu 19.10

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

Title:
  firefox is used to open ftp share files

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04
  Nautilus 1:3.26.0-0ubuntu1
  Bluefish 2.2.10

  When I open a .php file from a FTP server browsed with Nautilus,
  Chrome is opened instead of the default application Bluefish.

  Steps to reproduce:
  1. Connect to an FTP server via Nautilus
  2a. Double-click on a .php file: chrome opens and the file is downloaded
  2b. Right click and select 'open with' and then Bluefish: the file is opened 
in bluefish as expected

  So, on the double-click from Nautilus the wrong app (chrome!) is
  opened even if the .php files are associated with bluefish.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluefish 2.2.9-1
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 10 17:12:27 2018
  ExecutablePath: /usr/bin/bluefish
  InstallationDate: Installed on 2015-12-07 (765 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bluefish
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742482/+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 1742482] Re: firefox is used to open ftp share files

2019-11-23 Thread Janghou
Not only Firefox, also Chrome and Opera are x-scheme-handler/ftp
handlers.

IMHO this is a Nautilus bug, because it DOES SHOW *open with Text
Editor* on a txt file, and it DOES NOT do that.

But it DOES work when you select *Open with other application* and then
select *Text Editor*.

IMHO the handling in the context menu should be the default in Nautilus.

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

Title:
  firefox is used to open ftp share files

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04
  Nautilus 1:3.26.0-0ubuntu1
  Bluefish 2.2.10

  When I open a .php file from a FTP server browsed with Nautilus,
  Chrome is opened instead of the default application Bluefish.

  Steps to reproduce:
  1. Connect to an FTP server via Nautilus
  2a. Double-click on a .php file: chrome opens and the file is downloaded
  2b. Right click and select 'open with' and then Bluefish: the file is opened 
in bluefish as expected

  So, on the double-click from Nautilus the wrong app (chrome!) is
  opened even if the .php files are associated with bluefish.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluefish 2.2.9-1
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 10 17:12:27 2018
  ExecutablePath: /usr/bin/bluefish
  InstallationDate: Installed on 2015-12-07 (765 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: bluefish
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742482/+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 1728709] Re: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc

2019-11-23 Thread Ubfan
This documentation problem still present after two years in 18.04.

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

Title:
  bash man page has a typo, repeating .bashrc when one should be
  /etc/bash.bashrc

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  The INVOCATION section of the man page has the text

  "reads and executes commands from ~/.bashrc and ~/.bashrc, if these
  files exist and are readable"

  which repeats "~/.bashrc".  By experiment, I find it probable that the
  first of these .bashrc references should read "/etc/bash.bashrc".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 30 13:28:43 2017
  InstallationDate: Installed on 2016-08-08 (447 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1728709/+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 1728709] Re: bash man page has a typo, repeating .bashrc when one should be /etc/bash.bashrc

2019-11-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: bash (Ubuntu)
   Status: New => Confirmed

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

Title:
  bash man page has a typo, repeating .bashrc when one should be
  /etc/bash.bashrc

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  The INVOCATION section of the man page has the text

  "reads and executes commands from ~/.bashrc and ~/.bashrc, if these
  files exist and are readable"

  which repeats "~/.bashrc".  By experiment, I find it probable that the
  first of these .bashrc references should read "/etc/bash.bashrc".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bash 4.3-14ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Oct 30 13:28:43 2017
  InstallationDate: Installed on 2016-08-08 (447 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1728709/+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 1853374] Re: pulseaudio disables GP107GL output every so often

2019-11-23 Thread Ian
** Attachment added: "Output of pa-info for user2, currently with sound card 
showing as disabled"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5307313/+files/pa-info-user2

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

Title:
  pulseaudio disables GP107GL output every so often

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrading to 19.10, the sound output on this PC stops.

  Looking at the volume control's 'sound settings', the GP107GL High
  Definition Audio Controller (digital stereo HMDI 2 output) is
  disabled.

  Doing

  pluseaudio -k

  restores it.

  Possibly relevant from syslog:

  Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2
  Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 4
  Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1853374] Re: pulseaudio disables GP107GL output every so often

2019-11-23 Thread Ian
** Attachment added: "Output of pa-info for user1, currently with sound"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+attachment/5307312/+files/pa-info-user1

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

Title:
  pulseaudio disables GP107GL output every so often

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrading to 19.10, the sound output on this PC stops.

  Looking at the volume control's 'sound settings', the GP107GL High
  Definition Audio Controller (digital stereo HMDI 2 output) is
  disabled.

  Doing

  pluseaudio -k

  restores it.

  Possibly relevant from syslog:

  Nov 18 07:48:51 example kernel: [42392.063211] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 07:51:04 example kernel: [42524.900935] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2
  Nov 18 08:05:23 example kernel: [43383.465647] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 09:34:08 example kernel: [48708.806452] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 4
  Nov 18 13:32:46 example kernel: [63026.605375] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:13 example kernel: [63114.281953] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 3
  Nov 18 13:34:40 example kernel: [63141.350110] snd_hda_codec_hdmi 
hdaudioC0D0: HDMI: invalid ELD data byte 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853374/+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 1851935] Re: iio-sensor-proxy can't find i2c-BOSC0200:00/iio:device0

2019-11-23 Thread Giovanni Caligaris
Anyone?

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

Title:
  iio-sensor-proxy can't find i2c-BOSC0200:00/iio:device0

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I have a tablet by ALLDOCUBE iWork10 Pro i15-TD and the orientation of
  the screen is wrong. Currently when sitting on landscape it gives me
  bottom-up when it should be right-up

  $ monitor-sensor 
  Waiting for iio-sensor-proxy to appear
  +++ iio-sensor-proxy appeared
  === Has accelerometer (orientation: bottom-up)
  === No ambient light sensor
  Accelerometer orientation changed: bottom-up
  Accelerometer orientation changed: right-up
  Accelerometer orientation changed: bottom-up

  Also, the systemd service has a hard time finding the sensor.

  iio-sensor-proxy.service - IIO Sensor Proxy service
 Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; 
vendor preset: enabled)
 Active: active (running) since Sat 2019-11-09 12:51:33 GMT; 18min ago
   Main PID: 4182 (iio-sensor-prox)
  Tasks: 3 (limit: 4566)
 CGroup: /system.slice/iio-sensor-proxy.service
 └─4182 /usr/sbin/iio-sensor-proxy

  Nov 09 12:51:33 tablet-i1002SG systemd[1]: Starting IIO Sensor Proxy 
service...
  Nov 09 12:51:33 tablet-i1002SG systemd[1]: Started IIO Sensor Proxy service.
  Nov 09 12:51:33 tablet-i1002SG iio-sensor-prox[4182]: Could not find trigger 
name associated with 
/sys/devices/pci:00/808622C1:02/i2c-2/i2c-BOSC0200:00/iio:device0

  I have created file /lib/udev/hwdb.d/61-sensor-local.hwdb

  sensor:modalias:acpi:BOSC0200*:dmi*
   ACCEL_MOUNT_MATRIX=1, 0, 0; 0, 1, 0; 0, 0, 1

  And have updated after

  sudo systemd-hwdb update
  sudo udevadm trigger

  After running udevadm info -export-db | grep ACCEL it will not find
  anything.

  Help please.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1851935/+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 1853709] [NEW] lightdm does not greet or present login prompt when resuming from laptop suspend

2019-11-23 Thread Connor Kuehl
Public bug reported:

Expected result: when opening laptop lid the lock screen presents itself
so I can unlock my session

Actual result: the contents of my desktop are visible (windows, etc) and
I can move my mouse cursor around but I cannot interact with the desktop
session at all. Hovering over UI elements or clicking them has no
effect.

In order to get the login prompt I have to ctrl+alt+f1, login at the
console, and run sudo systemctl restart lightdm, then I can login
normally and resume whatever I was doing from before I closed the laptop
lid.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: lightdm 1.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Nov 23 09:08:32 2019
InstallationDate: Installed on 2019-11-09 (14 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  lightdm does not greet or present login prompt when resuming from
  laptop suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  Expected result: when opening laptop lid the lock screen presents
  itself so I can unlock my session

  Actual result: the contents of my desktop are visible (windows, etc)
  and I can move my mouse cursor around but I cannot interact with the
  desktop session at all. Hovering over UI elements or clicking them has
  no effect.

  In order to get the login prompt I have to ctrl+alt+f1, login at the
  console, and run sudo systemctl restart lightdm, then I can login
  normally and resume whatever I was doing from before I closed the
  laptop lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 23 09:08:32 2019
  InstallationDate: Installed on 2019-11-09 (14 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+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 1853707] [NEW] Whose system stopped responding because of single program's fault - no way out, had to force power off

2019-11-23 Thread teo1978
Public bug reported:

What I did was:

- install LibreCAD (by adding their ppa and then using apt-get)
- open it
- try to open the attached .dwf file

LibreCAD hanged and the whole system stopped responding. The mouse
button stopped moving, the system wouldn't respond to keyboard strokes,
AND not even Ctrl+Alt+F1 worked to open a virtual terminal where I could
have tried killing some process.

Obviously there's a bug in LibreCAD, but no matter how badly a buggy (or
even evil) process behaves, if a single misbehaving program can cause
the whole OS to stall in a way that you cannot recover from, then by
definition there's a bug in the OS.

You must ALWAYS be able to kill the offending program and resume normal
operation without having to stop one single application other than the
offending one.

I have no idea whether the bug is actually in Xorg or somewhere else;
the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't
work. I might very well be wrong but I believe xorg is responsible for
providing the virtual terminal via ctrl+alt+f1?

Either way, that MUST ALWAYS be available no matter how badly things go.

That a single program hanging causes me to have to force-power down the
computer is outrageous.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197
Uname: Linux 4.4.0-169-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Nov 23 17:27:22 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
 NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
InstallationDate: Installed on 2013-10-11 (2233 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.07
dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.07
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
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: Sat Nov 23 17:25:58 2019
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

** Attachment added: "wecancut.dwg"
   
https://bugs.launchpad.net/bugs/1853707/+attachment/5307277/+files/wecancut.dwg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is 

[Touch-packages] [Bug 1563781] Re: Flickering and invisible mouse pointer after wakeup from suspend

2019-11-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: lightdm (Ubuntu)
   Status: New => Confirmed

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

Title:
  Flickering and invisible mouse pointer after wakeup from suspend

Status in Light Display Manager:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I run Arch linux on a Thinkpad X230

  uname -a
  Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 
x86_64 GNU/Linux

  I use xmonad and a custom .xinitrc to start my session.  I run `light-
  locker --lock-on-suspend` there and xmonad.

  - When I wake up my laptop from suspend, the login screen shows up as 
expected.
  - After about 2 second, the screen flickers once and the login screen shows 
up again.
  - If I start typing a password before the flickering, the input field will be 
reset upon flickering.  Usually I end up with my password half-typed and a 
wrong password notice.
  - After logging back into the session, there is no mouse pointer.
  - Going to VT1 and back to VT7 restores the pointer.

  Please find the lightdm and journalctl logs below.  I am happy to
  provide more logs and info.

  Thanks,
  Dominik

  The lightdm log:
  [+14840.86s] DEBUG: Seat seat0: Creating greeter session
  [+14840.86s] DEBUG: Seat seat0: Creating display server of type x
  [+14840.86s] DEBUG: Using VT 8
  [+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8
  [+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to 
/run/lightdm/root/:1
  [+14840.86s] DEBUG: DisplayServer x-1: Launching X Server
  [+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth 
/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
  [+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server 
:1
  [+14841.11s] DEBUG: Seat seat0 changes active session to 
  [+14841.36s] DEBUG: Got signal 10 from process 16458
  [+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1
  [+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1
  [+14841.36s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
  [+14841.36s] DEBUG: Session pid=16473: Started with service 
'lightdm-greeter', username 'lightdm'
  [+14841.37s] DEBUG: Session pid=16473: Authentication complete with return 
value 0: Success
  [+14841.37s] DEBUG: Seat seat0: Session authenticated, running command
  [+14841.37s] DEBUG: Session pid=16473: Running command 
/usr/sbin/lightdm-gtk-greeter
  [+14841.37s] DEBUG: Creating shared data directory 
/var/lib/lightdm-data/lightdm
  [+14841.37s] DEBUG: Session pid=16473: Logging to 
/var/log/lightdm/x-1-greeter.log
  [+14841.41s] DEBUG: Activating VT 8
  [+14841.41s] DEBUG: Locking login1 session c2
  [+14841.41s] DEBUG: Activating login1 session c16
  [+14841.41s] DEBUG: Seat seat0 changes active session to c16
  [+14841.41s] DEBUG: Session c16 is already active
  [+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 
resettable=false
  [+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for 
dominik
  [+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', 
username 'dominik'
  [+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM
  [+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s)
  [+14846.18s] DEBUG: Session pid=16473: Continue authentication
  [+14846.20s] DEBUG: Session pid=16510: Authentication complete with return 
value 0: Success
  [+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: 
Success
  [+14846.20s] DEBUG: Session pid=16473: User dominik authorized
  [+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8
  [+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik
  [+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik
  [+14846.26s] DEBUG: Unlocking login1 session c2
  [+14846.26s] DEBUG: Activating VT 7
  [+14846.45s] DEBUG: Seat seat0: Stopping greeter
  [+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM
  [+14846.45s] DEBUG: Activating login1 session c2
  [+14846.46s] DEBUG: Session pid=16510: Exited with return value 0
  [+14846.46s] DEBUG: Seat seat0: Session stopped
  [+14846.46s] DEBUG: Seat seat0 changes active session to c2
  [+14846.46s] DEBUG: Session c2 is already active
  [+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel
  [+14846.50s] DEBUG: Session pid=16473: Exited with return value 0
  [+14846.50s] DEBUG: Seat seat0: Session stopped
  [+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require 
it
  [+14846.50s] DEBUG: Sending signal 15 to process 16458
  [+14846.51s] DEBUG: Process 16458 exited 

[Touch-packages] [Bug 1563781] Re: Flickering and invisible mouse pointer after wakeup from suspend

2019-11-23 Thread Paul White
Is this still an issue?

** Package changed: ubuntu => lightdm (Ubuntu)

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

** Changed in: lightdm
   Status: New => Incomplete

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

Title:
  Flickering and invisible mouse pointer after wakeup from suspend

Status in Light Display Manager:
  Incomplete
Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I run Arch linux on a Thinkpad X230

  uname -a
  Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 
x86_64 GNU/Linux

  I use xmonad and a custom .xinitrc to start my session.  I run `light-
  locker --lock-on-suspend` there and xmonad.

  - When I wake up my laptop from suspend, the login screen shows up as 
expected.
  - After about 2 second, the screen flickers once and the login screen shows 
up again.
  - If I start typing a password before the flickering, the input field will be 
reset upon flickering.  Usually I end up with my password half-typed and a 
wrong password notice.
  - After logging back into the session, there is no mouse pointer.
  - Going to VT1 and back to VT7 restores the pointer.

  Please find the lightdm and journalctl logs below.  I am happy to
  provide more logs and info.

  Thanks,
  Dominik

  The lightdm log:
  [+14840.86s] DEBUG: Seat seat0: Creating greeter session
  [+14840.86s] DEBUG: Seat seat0: Creating display server of type x
  [+14840.86s] DEBUG: Using VT 8
  [+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8
  [+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
  [+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to 
/run/lightdm/root/:1
  [+14840.86s] DEBUG: DisplayServer x-1: Launching X Server
  [+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth 
/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
  [+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server 
:1
  [+14841.11s] DEBUG: Seat seat0 changes active session to 
  [+14841.36s] DEBUG: Got signal 10 from process 16458
  [+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1
  [+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1
  [+14841.36s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
  [+14841.36s] DEBUG: Session pid=16473: Started with service 
'lightdm-greeter', username 'lightdm'
  [+14841.37s] DEBUG: Session pid=16473: Authentication complete with return 
value 0: Success
  [+14841.37s] DEBUG: Seat seat0: Session authenticated, running command
  [+14841.37s] DEBUG: Session pid=16473: Running command 
/usr/sbin/lightdm-gtk-greeter
  [+14841.37s] DEBUG: Creating shared data directory 
/var/lib/lightdm-data/lightdm
  [+14841.37s] DEBUG: Session pid=16473: Logging to 
/var/log/lightdm/x-1-greeter.log
  [+14841.41s] DEBUG: Activating VT 8
  [+14841.41s] DEBUG: Locking login1 session c2
  [+14841.41s] DEBUG: Activating login1 session c16
  [+14841.41s] DEBUG: Seat seat0 changes active session to c16
  [+14841.41s] DEBUG: Session c16 is already active
  [+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 
resettable=false
  [+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for 
dominik
  [+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', 
username 'dominik'
  [+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM
  [+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s)
  [+14846.18s] DEBUG: Session pid=16473: Continue authentication
  [+14846.20s] DEBUG: Session pid=16510: Authentication complete with return 
value 0: Success
  [+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: 
Success
  [+14846.20s] DEBUG: Session pid=16473: User dominik authorized
  [+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8
  [+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik
  [+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik
  [+14846.26s] DEBUG: Unlocking login1 session c2
  [+14846.26s] DEBUG: Activating VT 7
  [+14846.45s] DEBUG: Seat seat0: Stopping greeter
  [+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM
  [+14846.45s] DEBUG: Activating login1 session c2
  [+14846.46s] DEBUG: Session pid=16510: Exited with return value 0
  [+14846.46s] DEBUG: Seat seat0: Session stopped
  [+14846.46s] DEBUG: Seat seat0 changes active session to c2
  [+14846.46s] DEBUG: Session c2 is already active
  [+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel
  [+14846.50s] DEBUG: Session pid=16473: Exited with return value 0
  [+14846.50s] DEBUG: Seat seat0: Session stopped
  [+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require 
it
  [+14846.50s] DEBUG: Sending signal 15 

[Touch-packages] [Bug 1563781] [NEW] Flickering and invisible mouse pointer after wakeup from suspend

2019-11-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello,
I run Arch linux on a Thinkpad X230

uname -a
Linux schwarzbaer 4.4.5-1-ARCH #1 SMP PREEMPT Thu Mar 10 07:38:19 CET 2016 
x86_64 GNU/Linux

I use xmonad and a custom .xinitrc to start my session.  I run `light-
locker --lock-on-suspend` there and xmonad.

- When I wake up my laptop from suspend, the login screen shows up as expected.
- After about 2 second, the screen flickers once and the login screen shows up 
again.
- If I start typing a password before the flickering, the input field will be 
reset upon flickering.  Usually I end up with my password half-typed and a 
wrong password notice.
- After logging back into the session, there is no mouse pointer.
- Going to VT1 and back to VT7 restores the pointer.

Please find the lightdm and journalctl logs below.  I am happy to
provide more logs and info.

Thanks,
Dominik

The lightdm log:
[+14840.86s] DEBUG: Seat seat0: Creating greeter session
[+14840.86s] DEBUG: Seat seat0: Creating display server of type x
[+14840.86s] DEBUG: Using VT 8
[+14840.86s] DEBUG: Seat seat0: Starting local X display on VT 8
[+14840.86s] DEBUG: DisplayServer x-1: Logging to /var/log/lightdm/x-1.log
[+14840.86s] DEBUG: DisplayServer x-1: Writing X server authority to 
/run/lightdm/root/:1
[+14840.86s] DEBUG: DisplayServer x-1: Launching X Server
[+14840.86s] DEBUG: Launching process 16458: /usr/sbin/X :1 -seat seat0 -auth 
/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
[+14840.86s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1
[+14841.11s] DEBUG: Seat seat0 changes active session to 
[+14841.36s] DEBUG: Got signal 10 from process 16458
[+14841.36s] DEBUG: DisplayServer x-1: Got signal from X server :1
[+14841.36s] DEBUG: DisplayServer x-1: Connecting to XServer :1
[+14841.36s] DEBUG: Seat seat0: Display server ready, starting session 
authentication
[+14841.36s] DEBUG: Session pid=16473: Started with service 'lightdm-greeter', 
username 'lightdm'
[+14841.37s] DEBUG: Session pid=16473: Authentication complete with return 
value 0: Success
[+14841.37s] DEBUG: Seat seat0: Session authenticated, running command
[+14841.37s] DEBUG: Session pid=16473: Running command 
/usr/sbin/lightdm-gtk-greeter
[+14841.37s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+14841.37s] DEBUG: Session pid=16473: Logging to 
/var/log/lightdm/x-1-greeter.log
[+14841.41s] DEBUG: Activating VT 8
[+14841.41s] DEBUG: Locking login1 session c2
[+14841.41s] DEBUG: Activating login1 session c16
[+14841.41s] DEBUG: Seat seat0 changes active session to c16
[+14841.41s] DEBUG: Session c16 is already active
[+14841.58s] DEBUG: Session pid=16473: Greeter connected version=1.16.7 
resettable=false
[+14841.76s] DEBUG: Session pid=16473: Greeter start authentication for dominik
[+14841.76s] DEBUG: Session pid=16510: Started with service 'lightdm', username 
'dominik'
[+14841.77s] DEBUG: Session pid=16510: Got 1 message(s) from PAM
[+14841.77s] DEBUG: Session pid=16473: Prompt greeter with 1 message(s)
[+14846.18s] DEBUG: Session pid=16473: Continue authentication
[+14846.20s] DEBUG: Session pid=16510: Authentication complete with return 
value 0: Success
[+14846.20s] DEBUG: Session pid=16473: Authenticate result for user dominik: 
Success
[+14846.20s] DEBUG: Session pid=16473: User dominik authorized
[+14846.20s] DEBUG: Session pid=16473: Greeter sets language en_US.utf8
[+14846.26s] DEBUG: Session pid=16473: Greeter requests session xmonad-dominik
[+14846.26s] DEBUG: Seat seat0: Returning to existing user session dominik
[+14846.26s] DEBUG: Unlocking login1 session c2
[+14846.26s] DEBUG: Activating VT 7
[+14846.45s] DEBUG: Seat seat0: Stopping greeter
[+14846.45s] DEBUG: Session pid=16473: Sending SIGTERM
[+14846.45s] DEBUG: Activating login1 session c2
[+14846.46s] DEBUG: Session pid=16510: Exited with return value 0
[+14846.46s] DEBUG: Seat seat0: Session stopped
[+14846.46s] DEBUG: Seat seat0 changes active session to c2
[+14846.46s] DEBUG: Session c2 is already active
[+14846.50s] DEBUG: Session pid=16473: Greeter closed communication channel
[+14846.50s] DEBUG: Session pid=16473: Exited with return value 0
[+14846.50s] DEBUG: Seat seat0: Session stopped
[+14846.50s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+14846.50s] DEBUG: Sending signal 15 to process 16458
[+14846.51s] DEBUG: Process 16458 exited with return value 0
[+14846.51s] DEBUG: DisplayServer x-1: X server stopped
[+14846.51s] DEBUG: Releasing VT 8
[+14846.51s] DEBUG: DisplayServer x-1: Removing X server authority 
/run/lightdm/root/:1
[+14846.51s] DEBUG: Seat seat0: Display server stopped
[+14851.68s] DEBUG: Seat seat0 changes active session to 
[+14852.11s] DEBUG: Seat seat0 changes active session to c2
[+14852.11s] DEBUG: Session c2 is already active

Journalctl starting at suspend:
Mar 30 12:32:21 schwarzbaer kernel: ACPI: Waking up from system sleep state S3
Mar 30 12:32:21 schwarzbaer kernel: ehci-pci :00:1d.0: System 

[Touch-packages] [Bug 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-23 Thread Paul Mundt
Thanks for the tip - now that we know we have the same graphics chip,
it's obviously a G200 driver issue. Looking at the kernel history, we
find:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e

which includes:

mgag200:
   - cursor support fix

Which would suggest that this has since been fixed upstream, and it's
just a matter of time until it hits the ubuntu repositories.

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340/+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 1852001] Re: Xorg freeze on high disk or cpu load or random

2019-11-23 Thread JPT
Occurs after a few seconds with this setting: 
- Kernel 5.3.10-050310-generic
- swap available
- moving a 10 GB partition with gparted (high disk load on a USB attached SSD)
- xserver-xorg-video-intel installed

disabling swap solved the problem.

also the mouse hangs when window animations are active.

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

Title:
  Xorg freeze on high disk or cpu load or random

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've got massive problems with GUI on my PC.

  The attached logs are from the following setting: 
  - high disk load (f3write)
  - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan)
  - no swap available

  These are the parameters (disk load, kernel, swap) I am fiddling with
  to find out the cause, see below.

  In general 
  - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo
  - more likely to happen with high disk or CPU load, but not necessarily.
  - less likely with the 4.x kernel mentioned above. 

  I just installed the following kernels from kernel-ppa:
  5.3.10-050310-generic 
  5.4.0-050400rc6-generic
  5.4.0-997-generic (drm-intel-next)
  Now I am waiting for the freeze to occur again. 

  The problem started about half a year ago. 
  There have been three changes that happened at the time and could be the cause
  - switch to kernel 5.x
  - update to Ubuntu 19.4
  - swapped motherboard, CPU and RAM. 

  The hassle started with the following scenario, repeated often: 
  - high disk load
  - PC becomes laggy
  - soon dies/freezes

  The longer I waited, the deeper the lockdown went. but I don't know the exact 
details. 
  The first cause I found was kswapd running amok and take the system with it. 
Workaround: add swap space. 

  Now the problem shifted: Whenever I got high disk load (eg dd 100 GB
  of data) the kernel swaps likle crazy and makes the GUI first lag soon
  freeze. but no excessive CPU load any more, as kswapd does not go
  crazy.

  Again I found a workaround: 
  the above mentioned 4.x kernel. In this case the GUI lags as expected from a 
heavily swapping system. nothing more. 
  but still sometimes the GUI simply freezes (the error reported at the top)

  Another workaround is to completely remove swap. Let's see what
  happens, if kswapd goes amok again.

  I am not sure as how these problems are related.

  I did extensive hardware check like
  - memtest86 newest version, no "may be vulnerable to high frequency row 
hammering"
  - smart

  do you suggest any burn in test suites?

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18
  Uname: Linux 4.15.0-1050-oem x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Nov 10 15:55:14 2019
  DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb 
http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled 
on upgrade to eoan' was disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 
(Desktop 9 Series) [1462:7b16]
  InstallationDate: Installed on 2017-12-16 (693 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: Micro-Star International Co., Ltd. MS-7B16
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem 
root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago)
  dmi.bios.date: 08/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B360 GAMING PRO CARBON (MS-7B16)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7B16
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  

[Touch-packages] [Bug 1851340] Re: Ubuntu 19.10 upgrade results in invisible mouse cursor

2019-11-23 Thread John Hartley
I have now done further testing and can confirm that this is more than
just upgrade issue.

I have done the following tests:

A) Fresh 19.04 Desktop Install

A.1) Boot - Ubuntu 19.04 Desktop CD-ROM image via USB - Mouse / Cursor ok
A.2) Do clean disk install of 19.04 Desktop (Minimal Install Option selected) & 
Reboot. On reboot - Mouse / Curser ok
A.3) Disable Wayland and reboot - Mouse / Cursor ok
A.4) Do in place upgrade to 19.10 & reboot - Mouse / Cursor - Stopped Working

B) Attempt Fresh 19.10 Desktop Install

B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor
not visible

So I have unable to proceed with clean 19.10 install as there was no
mouse cursor visible.

So problem is to upgrade related but a general one for 19.10 release.

Both my testing and Paul Bundt's was on server boxes:
Dell Server with Matrox G200 and Lenovo x3650 with Matrox G200.

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

Title:
  Ubuntu 19.10 upgrade results in invisible mouse cursor

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Following in place upgrade of Ubuntu 19.04 -> 19.10 I no longer have
  visible cursor with my Gnone desktop.

  I have found the same problem when upgrading 2 machines from Ubuntu
  19.04 -> 19.10.

  Reproducing problem is easy:

  1. Open Ubuntu Update Window
  2. Select "Upgrade"
  3. On completion of update (after reboot) cursor is no longer visible.
  4. This applies to display connected to VGA port on host with USB Keyboard + 
Mouse

  While the connected display has no visible cursor and so is usable, I
  have always used X11VNC Server to provide network GUI access. On the
  remote X11VNC display I see and can use the cursor.

  This bug report is being sent via Remote X11VNC window, as I cannot
  use the main VGA display window (due to lack of visible cursor)

  I have done search online and thought that maybe issue was with my USB
  Mighty Mouse, so I also tried with Logitech M100R USB Mouse. Same
  result, no visible mouse cursor.

  I have done: "grep usb /var/log/syslog" and can see many USB events,
  including both Apple and Logitech mouse detection events.

  NOTE:

  Due to compatibility issue with X11VNC, I have disable Wayland on both
  machines by adding the following option to: /etc/gdm3/custom.conf

  WaylandEnable=false

  Regards,

  John Hartley.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 18:25:23 2019
  DistUpgraded: 2019-11-05 15:20:04,402 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Matrox Electronics Systems Ltd. G200eR2 [102b:0534] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G200eR2 [1d49:0a01]
  InstallationDate: Installed on 2018-12-17 (322 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO System x3650 M5: -[8871AC1]-
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=3b8f415b-7e78-461c-83df-64f1f1a7826a ro ipv6.disable=1 quiet splash 
iommu=1 intel_iommu=on ipv6.disable=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-05 (0 days ago)
  dmi.bios.date: 06/03/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: -[TCE140H-2.91]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 01KN179
  dmi.board.vendor: LENOVO
  dmi.board.version: NULL
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone:
  dmi.product.family: System X
  dmi.product.name: System x3650 M5: -[8871AC1]-
  dmi.product.sku: (none)
  dmi.product.version: 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage 

[Touch-packages] [Bug 1853373] Re: Print problems for double sided, multiple copies

2019-11-23 Thread Paul White
** Package changed: ubuntu => cups (Ubuntu)

** Tags added: eoan

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

Title:
  Print problems for double sided, multiple copies

Status in cups package in Ubuntu:
  New

Bug description:
  My HP Envy 5030 driver in Ubuntu 19.10 allows for double sided and
  multiple copy printing, however, I am experiencing an issue where only
  one copy prints.

  It prints fine, double sided, but only one copy is spooled.

  Looking at the bug list here, there was a similar issue with Evince
  and LibreOffice documents back in 2010.

  I'm not using any office software to print my PDF file, only the in-
  built Document Viewer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1853373/+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 1853373] [NEW] Print problems for double sided, multiple copies

2019-11-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My HP Envy 5030 driver in Ubuntu 19.10 allows for double sided and
multiple copy printing, however, I am experiencing an issue where only
one copy prints.

It prints fine, double sided, but only one copy is spooled.

Looking at the bug list here, there was a similar issue with Evince and
LibreOffice documents back in 2010.

I'm not using any office software to print my PDF file, only the in-
built Document Viewer.

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

-- 
Print problems for double sided, multiple copies
https://bugs.launchpad.net/bugs/1853373
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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


Re: [Touch-packages] [Bug 1853525] [NEW] no python 2.7.17 in LTS version

2019-11-23 Thread Beyo
The test procedure should be as follows:

Get the EPFImporter tool
https://affiliate.itunes.apple.com/resources/documentation/epfimporter/
Set up your database
Get the simple minimal dump from here
https://drive.google.com/file/d/1s1VmE-7NGsUoiBjvBQ1iaalUjYSNPh9w/view?usp=sharing
try to import EPFImport.py full/*

These are only information I can provide to test at the moment, hope
this helps a little bit

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

Title:
  no python 2.7.17 in LTS version

Status in python2.7 package in Ubuntu:
  New

Bug description:
  Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version
  this version broke my scripts and get me segmentation fault each time I 
trying to do something.
  IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. 
so why I have .15 and in RC1 version.

  Who is maintainer of this package that sleeps so long.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+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 1799265] Re: avahi-daemon high cpu, unusable networking

2019-11-23 Thread Dan
That's with avahi-daemon 0.7-4ubuntu5

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

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  New
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/1799265/+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 1799265] Re: avahi-daemon high cpu, unusable networking

2019-11-23 Thread Dan
I'm seeing exactly the same issue on Ubuntu 19.04

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

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  New
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/avahi/+bug/1799265/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-11-23 Thread Richard Khoury
And same for me, as #21 and #22.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1853684] [NEW] memory leak in g_param_value_defaults() (glib2.0, 2.63.1-2)

2019-11-23 Thread Thomas Haller
Public bug reported:

There is a memory leak in glib 2.63.1.

https://bugs.launchpad.net/ubuntu/+source/glib2.0/2.63.1-2

Fixed upstream:

https://gitlab.gnome.org/GNOME/glib/merge_requests/1220


This causes NetworkManager CI tests to fail on Ubuntu 20.04, and it seems quite 
serious (being in a popular function, at least when using for libnm).

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  memory leak in g_param_value_defaults() (glib2.0, 2.63.1-2)

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  There is a memory leak in glib 2.63.1.

  https://bugs.launchpad.net/ubuntu/+source/glib2.0/2.63.1-2

  Fixed upstream:

  https://gitlab.gnome.org/GNOME/glib/merge_requests/1220

  
  This causes NetworkManager CI tests to fail on Ubuntu 20.04, and it seems 
quite serious (being in a popular function, at least when using for libnm).

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