date:20180503

I'm not suggesting waiting for 5.49, kind of. This bug will be fixed in
an update to 5.48.

Policy however requires that we always fix the development release
first. So Ubuntu 18.10 will probably need to receive bluez 5.49 before
we can get approval for a bluez 5.48 update to Ubuntu 18.04.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread netslovdlyasnov

For PRIME users: as a workaround you can make you X session work with
Intel driver with this minimal xorg.conf

Section "ServerLayout"
Identifier "layout"
Screen  0  "Screen0" 0 0
Option "Xinerama" "0"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName  "Unknown"
Option "DPMS" "on"
EndSection

Section "Device"
Identifier "intel"
Driver "intel"
Option "AccelMethod" "sna"
Option "TearFree" "true"
BusID  "PCI:0@0:2:0"
EndSection

Section "Screen"
Identifier "intel"
Device "intel"
Monitor"Monitor0"
EndSection

Section "Screen"
Identifier "Screen0"
Device "intel"
Monitor"Monitor0"
DefaultDepth24
SubSection "Display"
Virtual 1920 1080
Depth   24
EndSubSection
EndSection

Make sure to put your own BusID and screen size. Both are mandatory.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768906] Re: Xorg crash

2018-05-03 Thread dino99

Be sure to purge the previous used nvidia driver before testing a new one 
(settings removal).
Do you get the same issue if 'nouveau' driver is used ? (nvidia purged, and 
reboot)

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset 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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this

[Touch-packages] [Bug 1768906] Re: Xorg crash

Same symptoms with a brand new GTX 1070 ti :(

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset 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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-05-03 Thread Julien MARY

So far, I can't wait for 5.49 when 5.46 is fixing my trouble.  So I
downgraded to have my audio chain usable, which was not the case at with
5.48 : Can't connect at ll my UE BOOM with Dell 5540.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1769029] [NEW] Display on Dell 1440x900 is not available

2018-05-03 Thread VK Joseph

Public bug reported:

Monitor resolution is limited to 1024x768 with no option for higher
resolution

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May  4 09:44:54 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
InstallationDate: Installed on 2018-05-03 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2007
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FG
dmi.board.name: 945GZM-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: 945GZM-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Display on Dell 1440x900 is not available

Status in xorg package in Ubuntu:
  New

Bug description:
  Monitor resolution is limited to 1024x768 with no option for higher
  resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 09:44:54 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte

[Touch-packages] [Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

Mike, I agree we need smarter defaults and have proposed that for 18.10
here: https://trello.com/c/i3JvebJ9

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work

2018-05-03 Thread Mike

I had GNOME (rather than Unity) as my default desktop before upgrading
to 18.04, and I strongly believe that my settings should have been
respected rather than overridden to the installation default. Whatever
the merits of the choice of installation default, it seems clear error
to impose it over a previously existing GNOME installation.

My touchpad has hardware left and right buttons, and it is my
understanding that it should therefore not default to "finger" mode but
should instead default to "area" mode. I was not able to get two-finger
secondary click to work in "finger" mode at all. The laptop is an Acer
V3-574 and the touchpad identifies in dmesg as follows:

hid-multitouch 0018:04F3:300B.0001: Ignoring the extra HID_DG_INPUTMODE
input: ELAN0501:00 04F3:300B Touchpad as 
/devices/pci:00/INT3432:00/i2c-0/i2c-ELAN0501:00/0018:04F3:300B.0001/input/input8
hid-multitouch 0018:04F3:300B.0001: input,hidraw0: I2C HID v1.00 Mouse 
[ELAN0501:00 04F3:300B] on i2c-ELAN0501:00

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

Title:
  Gnome Shell: Touchpad right click (bottom right) area does not work

Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  The right (second) touchpad click does not work.
  It ceased to work about three months ago.
  ubuntu 18,04 aser ex2519

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+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 1769022] [NEW] ubuntu 18.04 freezes after the login

2018-05-03 Thread Ghassan Mina

Public bug reported:

I am not able to log to ubuntu 18.04 after the upgrade. When I login I
get setup screen with the word "Welcome" and the system freezes

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu May  3 23:29:56 2018
DistUpgraded: 2018-05-03 01:59:32,397 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: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
   Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
InstallationDate: Installed on 2016-11-19 (530 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 129925U
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
dmi.bios.date: 07/20/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 54CN18WW
dmi.board.asset.tag: Base Board Asset Tag Unknown
dmi.board.name: Torpedo
dmi.board.vendor: LENOVO
dmi.board.version: 109-C06210-00B
dmi.chassis.asset.tag: Chassis Asset Tag Unknown
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Chassis Version Unknown
dmi.modalias: 
dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
dmi.product.family: IDEAPAD
dmi.product.name: 129925U
dmi.product.version: Ideapad Z575
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May  3 22:52:41 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  New

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 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: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
  InstallationDate: Installed on 2016-11-19 (530 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 129925U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 54CN18WW
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Torpedo
  dmi.board.vendor: LENOVO
  dmi.board.version: 109-C06210-00B
  dmi.chassis.asset.tag: Chassis Asset Tag Unknown
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Chassis Version Unknown
  dmi.modalias:

[Touch-packages] [Bug 1768906] Re: Xorg crash

Should I set this back to new?

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset 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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

This is the debdiff. Sponsor team, please help submit the build request
to the queue.

thx.


** Description changed:

  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.
  
  Expected result:
  Output and input audio should work in front and rear panel.
  
  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.
  
+ SRU Document:
  
- So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.
+ [Impact]
  
- And we have several Lenovo machines like Lenovo P520 which have 2
- analogue audio codecs on them, to make the audio work on those machines,
- the kernel needs 3 patches for alsa driver, and those 3 patches are
- already in the linux kernel from linux-4.12, kernel is not a blocking
- issue under ubuntu 18.04:
+ We have several Lenovo machines like Lenovo P520 which have 2 analogue
+ audio codecs on them, the internal speaker and front headset are
+ connected to the 1st codec, the Rear mic, Line in and Line out are
+ connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
+ lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
+ front headset) on the 1st codec can work. To make all audio devices work
+ on this machine, upstream provided 3 patches for kernel audio driver and
+ 5 patches for alsa-lib. The kernel patches are already in the
+ linux-4.12, so this is not a problem anymore under 18.04 since we use
+ linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport
+ them to v1.1.3-5, the 5 patches are list as below:
  
- 7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
- 56798e6b ALSA: hda - Use a helper function for renaming kctl names
- ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420
+ 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
+ 4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
+ b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
+ 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
+ 81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)
  
+ Some explanation for these 5 patches, to make the audio work, the alsa-
+ lib needs to add an audio configuration file and verb conf file for
+ lenovo machines with dual codecs, these two files are put in a folder
+ named by card_long_name, and the name of configuration file itself is
+ also named by card_long_name, this is implemented by the patches of NO.
+ 3rd and 5th.
  
- Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:
+ But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
+  
+ [Test Case]
  
- 2b9b3f01 ucm: Assure the user input card name not to exceed max size of
- card long name (it is in the alsa-lib v1.1.4)
+ On the Lenovo machines with dual codecs (p520), I insatlled the
+ libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
+ alsa-lib can find the conf file and can parse the conf file
+ successfully, and I tested the internal speaker, front headset, rear
+ mic, line out and line in, all audio devices work well.
  
- 4b9297e6 ucm: Load device-specific configuration file based on the card
- long name (it is in the alsa-lib v1.1.4)
+ On a HP and Dell machines without dual codecs, I insatlled the
+ libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
+ alsa-lib can't find conf file by card_long_name and card_name, the
+ pulseaudio will drive the sound card as before, so all audio functions
+ worked well as before.
  
- b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
- the alsa-lib v1.1.6)
+ [Regression Potential]
  
- 181f8e25 ucm: adding the folder of card_long_name when finding verb conf
- file (it is in the alsa-lib v1.1.6+)
+ After adding these 5 patches, there 2 two changes introduced into the
+ alsa-lib v1.1.3-5ubuntu1:
  
- 81db276f conf/ucm: increase the input volume for LineIn (it is in the
- alsa-lib v1.1.6+)
+ 1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
+ 2) before: the ucm parser will search the conf

[Touch-packages] [Bug 1768991] Missing required logs.

2018-05-03 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1768991

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+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 1768991] Re: outputsounddoesnotwork

I agree, that looks relevant:

[ 4849.250374] Audio Port: ASoC: no backend DAIs enabled for Audio Port

which comes from the kernel, sound/soc/soc-pcm.c:

/* there is no point preparing this FE if there are no BEs */
if (list_empty(>dpcm[stream].be_clients)) {
dev_err(fe->dev, "ASoC: no backend DAIs enabled for %s\n",
fe->dai_link->name);
ret = -EINVAL;
goto out;
}


** Summary changed:

- outputsounddoesnotwork
+ [bytchtes8316] Sound does not work

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

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

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+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 1768991] Re: [bytchtes8316] Sound does not work

The same hardware is mentioned in
https://bugzilla.kernel.org/show_bug.cgi?id=189261, although it appears
that's not what the original reporter of that bug has.

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+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 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

** Changed in: bluez (Ubuntu)
   Importance: High => Medium

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

** Description changed:

  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.
+ 
+ Update: Actually the crash occurs on slow-ish systems due to a race
+ condition. It's not strictly only hi-DPI machines - that's just the most
+ common place it is experienced.
  
  ---
  
  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
  
  ---
  
  WORKAROUND:
  
  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
  
  ---
  
  Crashed in a VM in the middle of installation. The host is Bionic up to
  date.
  
  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

You will get the same behaviour using the cairo fix too:
https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6

** Changed in: cairo (Ubuntu)
   Importance: Undecided => High

** Changed in: cairo (Ubuntu Bionic)
   Importance: Undecided => High

** No longer affects: glib2.0 (Ubuntu)

** No longer affects: glib2.0 (Ubuntu Bionic)

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions

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

[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

2018-05-03 Thread Erika

I am having this issue with Ubuntu 18.04 fresh install on Gigabyte Aero 15X v8.
Mouse is bluetooth Digio2 Trackball. After sleep, on/off switch is broken. Must 
remove and re-add from bluetooth settings.

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

"Expired" is a misnomer. It just moved to
https://gitlab.gnome.org/GNOME/gtk/issues/539

Since we can't change that status, and shouldn't, I have just removed
the gtk task. See the above link instead.

** No longer affects: gtk

** Description changed:

+ Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539
+ 
  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539

  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1698083/+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 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

** Changed in: alsa-lib (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  
  So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

  And we have several Lenovo machines like Lenovo P520 which have 2
  analogue audio codecs on them, to make the audio work on those
  machines, the kernel needs 3 patches for alsa driver, and those 3
  patches are already in the linux kernel from linux-4.12, kernel is not
  a blocking issue under ubuntu 18.04:

  7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
  56798e6b ALSA: hda - Use a helper function for renaming kctl names
  ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

  
  Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size
  of card long name (it is in the alsa-lib v1.1.4)

  4b9297e6 ucm: Load device-specific configuration file based on the
  card long name (it is in the alsa-lib v1.1.4)

  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
  in the alsa-lib v1.1.6)

  181f8e25 ucm: adding the folder of card_long_name when finding verb
  conf file (it is in the alsa-lib v1.1.6+)

  81db276f conf/ucm: increase the input volume for LineIn (it is in the
  alsa-lib v1.1.6+)

  To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
  minor change to resolve the patch conflict. And I attached 5 patches
  to this bug, these patches can be successfully applied to v1.1.3-5
  without any change.

  After applying this patches, the ucm searcher will look for folder
  according to card_long_name first, if it fails, it will fallback to
  use card_name as before, so these 5 patches are safe and will not
  introduce any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1768830/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Jaume

Same problem here with a Dell XPS 15 9560 after Kubuntu 17.10 -> 18.04 upgrade.
Finally solved after lots of retries and reboots. I have now:
Graphics Drivers PPA 
(https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
- sudo add-apt-repository ppa:graphics-drivers/ppa
- sudo apt update
- sudo apt dist-upgrade
Replaced manually nvidia 390 drivers by the newest 396
Purged nouveau package because I saw a "segmentation fault" log in 
/var/log/Xorg.0.log
- sudo apt purge xserver-xorg-video-nouveau
- sudo vi /etc/X11/xorg.conf -> uncomment line #Driver "nvidia" of Section 
"Device". So my xorg.conf file is exactly the same as the pasted in comment #77 
without the last Section "Monitor".
- sudo reboot

After the reboot I see my previous sddm login screen instead of a tty
and I can login normally :)

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation

2018-05-03 Thread James Cobban

I had this issue yesterday on 17.10.  The IPV4 address for my Ethernet
interface vanished.  I could not find any option in the network portion
of settings to ask the DHCP for the IP address, and sudo service
network-manager restart did not recover, so I rebooted the system.  This
is obviously an extremely rare situation and I do not know how to
reproduce it.  If there is no notification that the network manager can
register for to detect this situation automatically then there should be
a reinitialize button in the network settings GUI.

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

Title:
  IPv4 Address Lost 8 Days After Previous DHCP Allocation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired
  ethernet connection to my office's network.  This happened this
  morning and previously happened 8 days ago.

  The network uses a Windows Small Business Server as its main Active
  Domain Domain Controller which includes a DHCP service.  There are
  several other Ubuntu 16.04 machines on the network that do not seem to
  experience this issue.  This is an IPv4 only network, no IPv6 services
  are configures and IPv6 is disabled on most machines.

  My PC has two wired network ports.  One connects to the office network
  and uses DHCP to get an IPv4 address.  The other connects to a switch
  on my desk that has test equipment connected to it and uses a static
  IPv4 address.

  I have the output from: 
   ll /var/lib/NetworkManager
   nmcli -p c
   nmcli -p c show TN\ Wired
  Taken; after the renewal of the address eight days ago, this morning before I 
"Disconnect"ed the connection from the drop down menu and after I reconnected 
and an IPv4 address was re-acquired.  If any of this would be helpful, please 
let me know and I shall post it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 31 09:55:10 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-12 (690 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 172.16.20.21 dev eth0  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   172.16.20.0/24 dev eth0  proto kernel  scope link  src 172.16.20.67  metric 
100 
   192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.10  metric 
100
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-11T09:44:29.848008
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  TN 
Wired  decbd8d4-b045-4214-88c3-904bcabaa386  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   eth1ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Test 
Network  c2e4c3e8-027e-4201-8486-824d32ee164f  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+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 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation

2018-05-03 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  IPv4 Address Lost 8 Days After Previous DHCP Allocation

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My Ubuntu 16.04 desktop frequently loses the IPv4 address on its wired
  ethernet connection to my office's network.  This happened this
  morning and previously happened 8 days ago.

  The network uses a Windows Small Business Server as its main Active
  Domain Domain Controller which includes a DHCP service.  There are
  several other Ubuntu 16.04 machines on the network that do not seem to
  experience this issue.  This is an IPv4 only network, no IPv6 services
  are configures and IPv6 is disabled on most machines.

  My PC has two wired network ports.  One connects to the office network
  and uses DHCP to get an IPv4 address.  The other connects to a switch
  on my desk that has test equipment connected to it and uses a static
  IPv4 address.

  I have the output from: 
   ll /var/lib/NetworkManager
   nmcli -p c
   nmcli -p c show TN\ Wired
  Taken; after the renewal of the address eight days ago, this morning before I 
"Disconnect"ed the connection from the drop down menu and after I reconnected 
and an IPv4 address was re-acquired.  If any of this would be helpful, please 
let me know and I shall post it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 31 09:55:10 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-12 (690 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 172.16.20.21 dev eth0  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   172.16.20.0/24 dev eth0  proto kernel  scope link  src 172.16.20.67  metric 
100 
   192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.10  metric 
100
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-03-11T09:44:29.848008
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   eth0ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  TN 
Wired  decbd8d4-b045-4214-88c3-904bcabaa386  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   eth1ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Test 
Network  c2e4c3e8-027e-4201-8486-824d32ee164f  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-03 Thread PJSingh5000

I tried the patch for /usr/lib/ubiquity/ubiquity/misc.py in a virtual
machine.

Instead of corrupted graphics in the Ubiquity window, I saw a blank
white area above the "Copying files..." progress bar.

After a few seconds, the Ubiquity slide show appeared as usual, and I
did *not* get a crash.

I will also try this on actual hardware.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 1768991] Bug is not a security issue

2018-05-03 Thread Seth Arnold

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  outputsounddoesnotwork

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768991/+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 1768991] Re: outputsounddoesnotwork

2018-05-03 Thread Seth Arnold

This looks related:

[ 4849.250374]  Audio Port: ASoC: no backend DAIs enabled for Audio Port

Also, your USB mass storage device may have troubles. (Probably not
related to this.)

Thanks

** Information type changed from Private Security to Public

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

Title:
  outputsounddoesnotwork

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768991/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-03 Thread Pham Hong Nhat

Offer some bounty then. Probably someone will help if you offer him a
few hundred bucks.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-03 Thread Azur

Wow, nobody want's to help us with this...

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in

2018-05-03 Thread Seth Arnold

** Information type changed from Private Security to Public

** Also affects: account-plugins (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

Status in account-plugins package in Ubuntu:
  New
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  apart from kde config telepathy accounts package install error, I even
  cant update ubuntu base as i try every time the results is broken
  file. then it asks me to report the bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Sun Apr 29 07:05:33 2018
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2018-04-26 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+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 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1617564, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

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

Title:
  package kaccounts-providers (not installed) failed to install/upgrade:
  trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

Status in account-plugins package in Ubuntu:
  New
Status in kaccounts-providers package in Ubuntu:
  New

Bug description:
  apart from kde config telepathy accounts package install error, I even
  cant update ubuntu base as i try every time the results is broken
  file. then it asks me to report the bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Sun Apr 29 07:05:33 2018
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2018-04-26 (6 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-03 Thread ausiasbcn

It's supposed to be a community, everybody tries to help best he can.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

2018-05-03 Thread Brian Murray

Hello errors.ubuntu.com, or anyone else affected,

Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.17 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apport (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Committed

Bug description:
  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.

  [Regression Potential]
  The test being modified is designed to not report crashes that happen during 
logout. It's possible that some reports don't have a Date in them but in that 
case we couldn't compare the logind_session information to the Date anyway so 
those crashes would have been reported anyway. Regardless, the potential is 
that we'll have some more crashes reported about things crashing on logout 
which is better than the hundreds of crashes we get like this one.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Tom

Today I got all working, but although prime-select query showed me
"nvidia", nvidia drivers were not loaded and nvidia-settings did not
start. I regret that I decided to run "sudo prime-select intel". Login
worked but it broke suspend mode and my logout/shutdown times are
horrible: 1,5 minutes.

* This makes the intel mode unusable for the XPS and I think all optimus
prime Nvidia laptops, so if you need that, downgrage to 17.10 might be
only solution for now ?

Running prime-select nvidia gives good performance and suspend and
logout work again, but with running fans and hot laptop.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1670935] Re: package libpng12-0 1.2.50-1ubuntu2.14.04.2 [modified: usr/share/doc-base/libpng12 usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/l

2018-05-03 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libpng12-0 1.2.50-1ubuntu2.14.04.2 [modified: usr/share/doc-
  base/libpng12 usr/share/doc/libpng12-0/ANNOUNCE
  usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz
  usr/share/doc/libpng12-0/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libpng12-0/README.gz', which is different from other
  instances of package libpng12-0:i386

Status in libpng package in Ubuntu:
  Confirmed

Bug description:
  Also, I am not able to install Teamviewer in my system.+

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpng12-0 1.2.50-1ubuntu2.14.04.2 [modified: 
usr/share/doc-base/libpng12 usr/share/doc/libpng12-0/ANNOUNCE 
usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz 
usr/share/doc/libpng12-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Mar  8 10:27:46 2017
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.9
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.9
   zlib1g 1:1.2.8.dfsg-1ubuntu1
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DpkgTerminalLog:
   Preparing to unpack .../libpng12-0_1.2.50-1ubuntu2.14.04.2_i386.deb ...
   Unpacking libpng12-0:i386 (1.2.50-1ubuntu2.14.04.2) over (1.2.49-1+deb7u2) 
...
  DuplicateSignature: package:libpng12-0:1.2.50-1ubuntu2.14.04.2 [modified: 
usr/share/doc-base/libpng12 usr/share/doc/libpng12-0/ANNOUNCE 
usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz 
usr/share/doc/libpng12-0/changelog.Debian.gz]:trying to overwrite shared 
'/usr/share/doc/libpng12-0/README.gz', which is different from other instances 
of package libpng12-0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libpng12-0/README.gz', which is different from other instances 
of package libpng12-0:i386
  InstallationDate: Installed on 2017-01-17 (49 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: libpng
  Title: package libpng12-0 1.2.50-1ubuntu2.14.04.2 [modified: 
usr/share/doc-base/libpng12 usr/share/doc/libpng12-0/ANNOUNCE 
usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz 
usr/share/doc/libpng12-0/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libpng12-0/README.gz', which is different 
from other instances of package libpng12-0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpng/+bug/1670935/+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 1768967] Re: Screen randomly flips 180 degrees

2018-05-03 Thread Jason Yundt

** Summary changed:

- Screen randomly flips 180 degreese twice
+ Screen randomly flips 180 degrees

** Description changed:

- I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen
- will become flipped, go black for a second, and then return to normal.
+ I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest-
+ gtk, the laptop has a ST LIS3LV02DL Accelerometer with three axes. Axes
+ 0 and 2 remain at 0 (center) no matter what I do. Axis 1 on the other
+ hand senses how much the base of the laptop (the lower half of the clam
+ shell, the part with the keyboard), is tilted. When the laptop is level,
+ the Axis's value should be 0, but it can be anywhere from -20 to 20
+ while the laptop is being typed on. When its reading is above 0, the
+ screen flips. These two facts cause the screen to flip seemingly
+ randomly while it's being used.
+ 
+ Workarround: Lock the screen orientation in GNOME.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 15:53:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:21b7]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:21b7]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
-  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
-  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 002: ID 8087:8000 Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: Classis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242
  dmi.product.name: HP Pavilion 350 G1 Notebook PC
  dmi.product.version: 05A620300
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Screen randomly flips 180 degrees

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 18.04 on an HP 350 G1 laptop. According to jstest-
  gtk, the laptop has a ST

[Touch-packages] [Bug 1583182] Re: error on 01ifupdown script

2018-05-03 Thread Salamander

I had the problem of ubuntu-fan not being installed after the upgrade to
17.10/18.04, please mark ubuntu-fan as a dependency to NetworkManager or
something to fix this. It was by pure chance I ended up here to find a
way to debug this problem.

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

Title:
  error on 01ifupdown script

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

Bug description:
  When bring the interface up or down I see this message on the logs

  May 18 10:03:36 count0 nm-dispatcher[8608]: req:1 'up' [enp2s0], 
"/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script 
'/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
  May 18 10:03:36 count0 NetworkManager[791]:   [1463576616.8466] 
dispatcher: (29) 01ifupdown failed (failed): Script 
'/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.

  
  Tracing the problem I see that the call to /usr/sbin/fanctl is done with 
incorrect parameters.

  If I execute 
  /etc/NetworkManager/dispatcher.d/01ifupdown enp2s0 down

  I get this error
  run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 1

  ubuntu-fan is doing the call in following way

  /usr/sbin/fanctl net "$MODE" "$IFACE"

  and the parameters passed by ubuntu-fan are

  $MODE=stop
  $IFACE=enp2s0

  
  but fanctl expect other parameters as showed on the script's header

  
  --
  details

  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy network-manager
  network-manager:
Installed: 1.1.93-0ubuntu4
Candidate: 1.1.93-0ubuntu4
Version table:
   *** 1.1.93-0ubuntu4 500
  500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 18 10:50:24 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (24 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-76f79dfb13e0  proto kernel  scope link  src 172.18.0.1 
linkdown 
   192.168.1.0/24 dev enp2s0  proto kernel  scope link  src 192.168.1.8  metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   br-76f79dfb13e0  bridgeconnected  
/org/freedesktop/NetworkManager/Devices/2  br-76f79dfb13e0 
0a9f5c9b-cd67-4fb8-a72d-1811ca6fbb68  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   docker0  bridgeconnected  
/org/freedesktop/NetworkManager/Devices/3  docker0 
e5f99f7d-532f-4c52-8749-c78afa9271dd  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   enp2s0   ethernet  connected  
/org/freedesktop/NetworkManager/Devices/0  Wired connection 1  
ee3ec6ee-7242-4956-9d19-20ccb19c5fe5  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   lo   loopback  unmanaged  
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1583182/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2018-05-03 Thread kororos

I am having the same problem with Ubuntu 18.04 LTS release

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1768967] [NEW] Screen randomly flips 180 degreese twice

2018-05-03 Thread Jason Yundt

Public bug reported:

I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen
will become flipped, go black for a second, and then return to normal.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May  3 15:53:15 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:21b7]
InstallationDate: Installed on 2018-05-03 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 001 Device 002: ID 8087:8000 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=1a8b0eca-695f-444c-9cb1-558fe4916595 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 21B7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 46.0B
dmi.chassis.asset.tag: Classis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd10/17/2014:svnHewlett-Packard:pnHPPavilion350G1NotebookPC:pvr05A620300:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN G=N L=CON B=HP S=242
dmi.product.name: HP Pavilion 350 G1 Notebook PC
dmi.product.version: 05A620300
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Screen randomly flips 180 degreese twice

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen
  will become flipped, go black for a second, and then return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 15:53:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:21b7]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd 
(Foxlink) Webcam
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 350 G1 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

2018-05-03 Thread Andrea Azzarone

Fix for ubiquity proposed here:
https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 1753333] Re: Using "Software and Updates -> Additional Drivers" to Switch Fails

2018-05-03 Thread Brian Murray

Hello Chris, or anyone else affected,

Accepted software-properties into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.24.32.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: software-properties (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  Using "Software and Updates -> Additional Drivers" to Switch Fails

Status in software-properties package in Ubuntu:
  In Progress
Status in software-properties source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Currently, the Additional Drivers tool uninstalls only the driver package 
that ships the modaliases. When it comes to the NVIDIA drivers (>=390), that 
package is only a meta-package. Removing the meta-package will not uninstall 
the driver.

  We should make sure to uninstall all its nvidia related dependencies,
  not only the meta-package.

  [Test Case]
  1) Open the "Software & Updates" app, and select the "Additional Drivers" tab

  2) Uninstall the NVIDIA 390 driver

  3) Check that, for example, the nvidia-dkms-390 package was
  uninstalled:

  apt-cache policy nvidia-dkms-390

  The package will be reported as installed, because the current code
  didn't remove it.

  [Regression Potential]
  Relatively low, as the change in behaviour only affects the nvidia driver, 
and it only causes the Additional Drivers tool to remove dependencies of the 
meta-package that have the "nvidia" string in their name.

  __
  When you are in the initial install state, you can easily switch from the 
Nouvea drivers to the Nvidia drivers by choosing the option in "Software and 
Updates -> Additional Drivers".  However, when you attempt to switch back (by 
selecting the nouveau option and clicking Apply), and subsequently reboot, your 
system will still come up using the Nvidia drivers, and you will WTF.

  And then, if you visit Additional Drivers, you will be presented with
  grayed out options for both nvidia and nouvea, and the only selectable
  option will be "continue using manually installed driver".

  The reason for this is that the tool, when reselecting nvidia in the
  GUI, uninstalls the nvidia-drivers-390 package, but because it's a
  metapackage (or at least I presume this is the reason), it doesn't
  uninstall its dependencies, which causes the Additional Drivers tool
  to believe it's in a non-automanaged state, and the nvidia drivers
  never actually get uninstalled.

  You can fix it by doing an apt autoremove and rerunning the Additional
  Drivers tool.  But obviously there is no real way for inexperienced
  users to know this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/175/+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 1768943] Re: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1768941, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1768941
   package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-
  dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  16

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768943/+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 1768941] Re: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

** Tags removed: need-duplicate-check

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-
  dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768941/+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 1768943] [NEW] package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

2018-05-03 Thread Jeffrey Manning

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

Public bug reported:

Encountered error message about this after upgrading from 14.04.05 to 16

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: uuid-runtime 2.27.1-6ubuntu3.4
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu May  3 17:57:04 2018
ErrorMessage: pre-dependency problem - not installing uuid-runtime
InstallationDate: Installed on 2018-05-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: util-linux
Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-
  dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  16

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768943/+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 1768933] Re: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

** Tags removed: need-duplicate-check

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

Title:
  package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade:
  pre-dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768933/+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 1768941] [NEW] package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

2018-05-03 Thread Jeffrey Manning

Public bug reported:

Encountered error message about this after upgrading from 14.04.05 to 18

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: uuid-runtime 2.27.1-6ubuntu3.4
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu May  3 17:57:04 2018
ErrorMessage: pre-dependency problem - not installing uuid-runtime
InstallationDate: Installed on 2018-05-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: util-linux
Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: pre-
  dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.27.1-6ubuntu3.4 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768941/+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 1701289] Re: gnome-shell crashed with signal 5 in XIGetClientPointer() from gdk_x11_display_get_default_seat()

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  gnome-shell crashed with signal 5 in XIGetClientPointer() from
  gdk_x11_display_get_default_seat()

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/fb179bc620e408d216f4b8700f714e6ebb2ebf09

  ---

  cant login to gnome desktop

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 29 16:14:29 2017
  DisplayManager: lightdm
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-03-25 (96 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=sv
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1701289/+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 1768933] [NEW] package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: pre-dependency problem - not installing uuid-runtime

2018-05-03 Thread Jeffrey Manning

Public bug reported:

Encountered error message about this after upgrading from 14.04.05 to 18

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: uuid-runtime 2.20.1-5.1ubuntu20.9
ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
Uname: Linux 4.4.0-122-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Thu May  3 17:57:04 2018
ErrorMessage: pre-dependency problem - not installing uuid-runtime
InstallationDate: Installed on 2018-05-03 (0 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: util-linux
Title: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade:
  pre-dependency problem - not installing uuid-runtime

Status in util-linux package in Ubuntu:
  New

Bug description:
  Encountered error message about this after upgrading from 14.04.05 to
  18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: uuid-runtime 2.20.1-5.1ubuntu20.9
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu May  3 17:57:04 2018
  ErrorMessage: pre-dependency problem - not installing uuid-runtime
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: util-linux
  Title: package uuid-runtime 2.20.1-5.1ubuntu20.9 failed to install/upgrade: 
pre-dependency problem - not installing uuid-runtime
  UpgradeStatus: Upgraded to xenial on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1768933/+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 1768906] Re: Xorg crash

Same thing happens with nvidia-346.

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset 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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list:

[Touch-packages] [Bug 1515561] Re: Windows flash black briefly before being drawn

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Windows flash black briefly before being drawn

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  Since 3.18, windows flash black for a split second before they are
  drawn. It's visually disruptive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1515561/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread iuuuuan

I have managed to work nvidia binary drivers version 340.102 with kernel
4.15 with patch https://pastebin.com/raw/fVJVvQy7 , which is mentioned
on https://devtalk.nvidia.com/default/topic/1026911/linux/4-15-rc1
-patches-for-384-98-and-340-104.

My nvidia m720 graphics is working again on Ubuntu 18.04.

1. Install prerequisites
# apt-get install build-essential libc6:i386

2. Download nvidia binary drivers from http://www.nvidia.com/content
/DriverDownload-March2009/confirmation.php?url=/XFree86/Linux-
x86_64/340.104/NVIDIA-Linux-x86_64-340.104.run=us=TITAN

3. Download patch for nvidia binary drivers in same directory
# wget -O nv_patch_340.104_linux_kernel_4.15 https://pastebin.com/raw/fVJVvQy7

4. Boot ubuntu in single mode https://linuxconfig.org/how-to-boot-
ubuntu-18-04-into-emergency-and-rescue-mode (How to access
emergency.target at boot)

5. Enter root password

6. Unload nouveau driver
# rmmod nouveau

7. Blacklist nouveau driver
# echo "blacklist nouveau" > /etc/modprobe.d/blacklist-nouveau.conf
# echo "options nouveau modeset=0" >> /etc/modprobe.d/blacklist-nouveau.conf

File /etc/modprobe.d/blacklist-nouveau.conf should have following
entries:

blacklist nouveau
options nouveau modeset=0

8. Update initial ramdisk
# update-initramfs -u

9. Go to directory which contains downloaded nvidia-340 binary driver and set 
executable attribute
# chmod +x NVIDIA-Linux-x86_64-340.104.run

10. Apply the patch to driver (maybe this could be done after downloading 
kernel 4.15 patch - have not tried it ...) 
# ./NVIDIA-Linux-x86_64-340.104.run --apply-patch 
nv_patch_340.104_linux_kernel_4.15

This will build custom NVIDIA binary driver package with name NVIDIA-
Linux-x86_64-340.104-custom.run

11. Set executable attribute for custom driver package
# chmod +x NVIDIA-Linux-x86_64-340.104-custom.run

12. Install the driver with command
# ./NVIDIA-Linux-x86_64-340.104-custom.run

Ignore errors and enable DKMS

13. Reboot computer
# reboot

Nvidia driver 340.120 should be loaded now and graphics fully working.
This method is to complicated so I will also try methods mention in #112
and #113.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768906] Re: Xorg crash

2018-05-03 Thread dino99

With that card, use nvidia-331 or 346 instead.

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset 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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:

[Touch-packages] [Bug 1768912] [NEW] Wifi connection drops regularly

2018-05-03 Thread resplin

Public bug reported:

Description: A few times an hour the networking drops for around 20
seconds. It then automatically reconnects. The only clearly related
message in journalctl is the DHCPREQUEST / DCHPACK followed the
messages:

Starting Network Manager Script Dispatcher Service...
bound to X.X.X.X -- renewal in 1692 seconds.
[system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Started Network Manager Script Dispatcher Service.
req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...

That makes me think that Network Manager silently died and was
restarted.

Notes:
* The system is a new Dell Precision 5520 with a Qualcomm Atheros QCA6174 
802.11ac Wireless Network Adapter (rev 32)
* This system started as a clean install of Ubuntu 18.04 Beta on March 31, 2018
* The wireless networking was stable from install until a system update on 
April 27, 2018
* The wired networking is completely stable.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May  3 10:36:25 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-03-31 (32 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180331)
IpRoute:
 default via 10.4.0.1 dev wlp2s0 proto dhcp metric 600 
 10.4.0.0/20 dev wlp2s0 proto kernel scope link src 10.4.3.151 metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp2s0   wifi  connected
/org/freedesktop/NetworkManager/Devices/3  Evernym 
c5f3aef0-8286-4268-a8e4-7b7272491d34  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enx1065308d9647  ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
 lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  disabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  Wifi connection drops regularly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description: A few times an hour the networking drops for around 20
  seconds. It then automatically reconnects. The only clearly related
  message in journalctl is the DHCPREQUEST / DCHPACK followed the
  messages:

  Starting Network Manager Script Dispatcher Service...
  bound to X.X.X.X -- renewal in 1692 seconds.
  [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
  Started Network Manager Script Dispatcher Service.
  req:1 'dhcp4-change' [wlp2s0]: new request (1 scripts)
  req:1 'dhcp4-change' [wlp2s0]: start running ordered scripts...

  That makes me think that Network Manager silently died and was
  restarted.

  Notes:
  * The system is a new Dell Precision 5520 with a Qualcomm Atheros QCA6174 
802.11ac Wireless Network Adapter (rev 32)
  * This system started as a clean install of Ubuntu 18.04 Beta on March 31, 
2018
  * The wireless networking was stable from install until a system update on 
April 27, 2018
  * The wired networking is completely stable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 10:36:25 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-31 (32 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180331)
  IpRoute:
   default via 10.4.0.1 dev wlp2s0 proto dhcp metric 600 
   10.4.0.0/20 dev wlp2s0

[Touch-packages] [Bug 1768906] [NEW] Xorg crash

Public bug reported:

When attempting to log in to a newly updated bionic beaver via the
display manager (I think this is the right term), I immediately see a
crash, a return to the user selection/login screen and a no-longer
functioning keyboard and mouse. This happens both with the proprietary
driver installed drivers and with the apt installed nvidia-driver-396.

some interesting tidbits from the syslog file are:

May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: 
"wfb"
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadSubModule: 
"fb"
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) found, 
but none have a usable configuration.
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset 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  396.24  Thu Apr 26 00:10:09 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu May  3 09:28:59 2018
DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
MachineType: ASUS All Series
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
dmi.bios.date: 08/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAXIMUS VI GENE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May  3 09:20:03 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic crash possible-manual-nvidia-install 
third-party-packages ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user

[Touch-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Expired
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Invalid
Status in mutter source package in Artful:
  Fix Released
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1719043/+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 1598295] Re: $GTK_IM_MODULE ignored after upgrade

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  $GTK_IM_MODULE ignored after upgrade

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  After upgrade trusty → xenial, Compose key stopped producing
  configured through ~/.XCompose characters for GTK3 only apps. To be
  sure that its the GTK problem, I created a simple GTK3 window with
  textbox, launched it like:

  $ GTK_IM_MODULE=xim XMODIFIERS=@im=none ./a

  and the textbox produces wrong characters for Compose key. (the
  variables are actually set globally, I wrote them here just for
  clarity).

  XCompose works fine for all other toolkit's apps, including GTK2 and
  Qt ones.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy libgtk-3-0
  libgtk-3-0:
Installed: 3.18.9-1ubuntu3
Candidate: 3.18.9-1ubuntu3
Version table:
   *** 3.18.9-1ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  «Compose + - + space» would produce «— » in GTK3 apps.

  4) What happened instead

  «Compose + - + space» producing «~» in GTK3 apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1598295/+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 1758865] Re: regression artful sru upgrade

2018-05-03 Thread Dimitri John Ledkov

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  regression artful sru upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Artful:
  Fix Committed

Bug description:
  systemd upgrades are now failing in my build chroots, and I suspect it
  is related to this change.

  Setting up systemd (234-2ubuntu12.3) ...
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  [/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace specifiers: 
/tmp/systemd-private-%b-*
  [/usr/lib/tmpfiles.d/tmp.conf:16] Failed to replace specifiers: 
/tmp/systemd-private-%b-*/tmp
  [/usr/lib/tmpfiles.d/tmp.conf:17] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*
  [/usr/lib/tmpfiles.d/tmp.conf:18] Failed to replace specifiers: 
/var/tmp/systemd-private-%b-*/tmp
  ACL operation on "/var/log/journal" failed: No such file or directory
  ACL operation on "/var/log/journal" failed: No such file or directory
  chmod() of /var/log/journal via /proc/self/fd/3 failed: No such file or 
directory
  dpkg: error processing package systemd (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   systemd
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1758865/+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 1768755] Re: Missing links to libGL.so and libglapi.so

2018-05-03 Thread Hans Joachim Desserud

** Tags added: bionic

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

Title:
  Missing links to libGL.so and libglapi.so

Status in mesa package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain
  the symbolic links libGL.so and libglapi.so.

  Thus, it is not possible to use the -lGL option to compile a
  program...

  System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
  Package: libgl1-mesa-dev:amd64 18.0.0~rc5-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768755/+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 1768261] Re: Videos are getting stuck randomly at frames

2018-05-03 Thread Rishabh Lohia

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

** This bug has been marked a duplicate of bug 1752938
   Upgrading Ubuntu 18.04 disables GPU hardware acceleration

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

Title:
  Videos are getting stuck randomly at frames

Status in xorg package in Ubuntu:
  New

Bug description:
  Updated Ubuntu to 18.04 (from 17.10) and this problem started. Videos,
  on VLC and on Youtube, Twitch etc. on Chrome get stuck on frames. The
  video seek time also gets stuck at that frame, and then suddenly the
  video skips ahead. Audio has no issues. I am assuming it's a problem
  with the video drivers.

  I have dual graphics cards, one integrated and one dedicated(AMD
  Radeon HD 8670M). I guess my problem is similar to
  https://askubuntu.com/questions/1029205/video-playback-performance-
  issue-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May  1 19:40:21 2018
  DistUpgraded: 2018-04-26 21:50:03,842 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: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea]
  InstallationDate: Installed on 2016-01-21 (830 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Inspiron 5537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=d287f35b-0011-4adf-a2f4-3626718405ff ro quiet splash radeon.modeset=1 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 04NGGW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron5537:pvrA08:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1805010730.6487e7~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1805010730.6487e7~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768261/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread claudio@ubuntu

Forgot to add:
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1" 
(see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when 
you install the binary drivers). Performance: very good.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread claudio@ubuntu

There are two setups where the solution is with my setup (NVIDIA Corporation 
GK107M [GeForce GT 750M], laptop with nvidia and intel):
- Use Wayland with nouveau drivers: performance OK.
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1" 
(see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when 
you install the binary drivers).

What doesn't work (black or too slow):
- nvidia drivers.
- nvidia drivers with intel selected by prime.
- nouveau drivers on Xorg.

Here are the more expanded instructions. Be sure to know what you do,
you won't loose files, but you may make your system unbootable if you
type an error.

1. Make sure nvidia is not blacklisted. E.g. remove bumblebee. Have a look in 
/etc/modules and /etc/modprobe.d/*:
$ sudo apt-get remove --purge bumblebee
$ grep nvidia /etc/modules /etc/modprobe.d/*

"blacklist nvidia" is what's mostly used.

2. Add "modeset=1" to grub:
$ sudo vi /etc/default/grub
(or sudo nano /etc/default/grub)

Add nvidia-drm.modeset=1 to the GRUB_CMDLINE line (with the quotes):
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"

Activate the changes:
$ sudo update-grub

4. Install Nvidia drivers:
$ sudo ubuntu-drivers autoinstall
$ sudo prime-select nvidia

5. Reboot

Be warned that modeset=1 disabled the virtual consoles (ctl+alt+f).

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  apport-gtk crashed with SIGSEGV in
  _gtk_style_provider_private_get_settings(provider=0x0)
  [gtkstyleproviderprivate.c:123]

Status in Apport:
  New
Status in GTK+:
  Expired
Status in apport package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347

  ---

  Crash displayed after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  1 22:13:24 2016
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208
  InterpreterPath: /usr/bin/python3.5
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  SegvAnalysis:
   Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi
   PC (0x7f3a0219cb89) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1552577/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Jean-Sébastien Herbaux

I've upgraded from ubuntu 17.10 to 18.04 and I got the same issue.

When I boot on my laptop with a gtx 1070, I can see on my laptop screen
and my monitor connected through a USB-C adapter the startup console
starting all the modules. On the other hand I have the login screen
working well on my external monitor (through HDMI).

It is important to notice that I cannot detect any of the two others
display through the device manager or any command.

I believe that the monitor connected through HDMI only is using the
integrated Intel GPU while my two other screens uses the nvidia graphic
card.

This bug is definitively not fixed at all and it is astonishing to see
that it has been marked as 'resolved' while a lot of users are still
getting blocked from using their computer (personal or work...).

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

2018-05-03 Thread Dave English

My workaround for slack-desktop was to install using snap:

sudo snap install slack --classic

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1767096] Re: Random Xorg crashes

2018-05-03 Thread spodin

also, in `/var/log/Xorg.1.log.old`

I see such error:

[ 16706.342] (EE) 
Fatal server error:
[ 16706.342] (EE) Cannot run in framebuffer mode. Please specify busIDs
for all framebuffer devices
[ 16706.342] (EE) 
[ 16706.342] (EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
[ 16706.342] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
[ 16706.342] (EE) 
[ 16706.382] (EE) Server terminated with error (1). Closing log file.

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

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767096/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Nicolae Righeriu

I'm running Ubuntu 18 (although I had exactly the same issue on 16 too)
and instalation of Nvidia drivers works fine, until I choose to change
to Intel graphics card. Then, after rebooting I can't open the Nvidia
GUI anymore. This means I can't use my Hdmi port. Seems like I'll have
to get back to Windows for a while because of this matter unfortunately

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Nicolae Righeriu

no fix is released, please change the status. Things are definetly not
fine yet

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-03 Thread Tim Richardson

This is not a new problem, and it affects every gdm3-based distro that I have 
used. Long story short; if you want to use modeset=1 with nvidia to get rid of 
tearing (which would be every linux Optimus user on the planet), gdm3 doesn't 
work. No one seems to know why. 
Change your display manager to lightdm and enjoy life again. I have two Optimus 
laptops. 

sudo dpkg-reconfigure lightdm

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768843] Re: Dependencies not being flagged for install upon installing a new package

2018-05-03 Thread Julian Andres Klode

libvirt-bin should not be necessary.  gnome-boxes recommends qemu-
system-x86 so it should be installed on most systems; and libvirt-daemon
recommends qemu-kvm so that should be installed too. Both are not
integral parts of gnome boxes though, it works fine without it (e.g.
managing remote machines I think).

In any case, reassigning to gnome-boxes.

** Package changed: apt (Ubuntu) => gnome-boxes (Ubuntu)

** Summary changed:

- Dependencies not being flagged for install upon installing a new package
+ gnome-boxes install does not install qemu(-kvm)

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

Title:
  gnome-boxes install does not install qemu(-kvm)

Status in gnome-boxes package in Ubuntu:
  New

Bug description:
  For example, the Ubuntu Software Center and 'apt' tool within the
  Terminal do not recognize and flag the packages 'qemu' "qemu-kvm" and
  'libvirt-bin' for install upon installation of the gnome-boxes
  package.

  Gnome-boxes requires these packages to virtualize, and should be
  flagged and installed as part of the default.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:25:35 2018
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1768843/+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 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

2018-05-03 Thread dino99

** Tags removed: verification-needed

** Tags removed: severity-medium

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Trusty:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+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 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

2018-05-03 Thread Lonnie Lee Best

** Tags added: bionic

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1723403/+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 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

2018-05-03 Thread bugproxy

** Tags added: severity-medium

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Trusty:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+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 1768843] Re: Dependencies not being flagged for install upon installing a new package

2018-05-03 Thread Jeb E.

https://askubuntu.com/questions/836703/gnome-boxes-iso-issue

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

Title:
  Dependencies not being flagged for install upon installing a new
  package

Status in apt package in Ubuntu:
  New

Bug description:
  For example, the Ubuntu Software Center and 'apt' tool within the
  Terminal do not recognize and flag the packages 'qemu' "qemu-kvm" and
  'libvirt-bin' for install upon installation of the gnome-boxes
  package.

  Gnome-boxes requires these packages to virtualize, and should be
  flagged and installed as part of the default.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:25:35 2018
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768843/+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 1768841] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Sun Apr 29 10:24:57 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-28 (4 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1768841/+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 1768841] [NEW] package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-05-03 Thread Mukesh Joshi

Public bug reported:

package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
install/upgrade: subprocess installed post-installation script returned
error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Sun Apr 29 10:24:57 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-04-28 (4 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Sun Apr 29 10:24:57 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-28 (4 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1768841/+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 1768843] [NEW] Dependencies not being flagged for install upon installing a new package

2018-05-03 Thread Jeb E.

Public bug reported:

For example, the Ubuntu Software Center and 'apt' tool within the
Terminal do not recognize and flag the packages 'qemu' "qemu-kvm" and
'libvirt-bin' for install upon installation of the gnome-boxes package.

Gnome-boxes requires these packages to virtualize, and should be flagged
and installed as part of the default.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May  3 09:25:35 2018
InstallationDate: Installed on 2018-05-01 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bin bionicvm i386 kvm libvirt qemu x64 x86

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

Title:
  Dependencies not being flagged for install upon installing a new
  package

Status in apt package in Ubuntu:
  New

Bug description:
  For example, the Ubuntu Software Center and 'apt' tool within the
  Terminal do not recognize and flag the packages 'qemu' "qemu-kvm" and
  'libvirt-bin' for install upon installation of the gnome-boxes
  package.

  Gnome-boxes requires these packages to virtualize, and should be
  flagged and installed as part of the default.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:25:35 2018
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768843/+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 137606] Re: an icon view for the fileselectors would be useful

** Changed in: gtk
   Status: In Progress => Expired

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

Title:
  an icon view for the fileselectors would be useful

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: nautilus

  When using nautilus in lookup mode, i.e. browse for a file for opening
  or selecting, the list of files is always in list mode. It would be
  very handy when one can change to icon mode, because then there's
  automatically a preview.

  This has especially much value when browsing for an image, say for
  adding an attachmant in a gmail message within firefox.

  Note. special lookup screens for example eog already have a preview,
  but this is a special mode, this should be generic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/137606/+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 1281617] Re: Missing padding above menu's first item and below last item

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Missing padding above menu's first item and below last item

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Problem occurs with: light-themes 13.04+13.10.20131014-0ubuntu1, Ubuntu 13.10
  Does not occur with: light-themes 0.1.8.11, Ubuntu 11.04

  1. Position the pointer on an empty area of the desktop, or of a Nautilus 
window's main pane.
  2. Without moving the pointer at all, either hold down the right mouse 
button, or click once.
  3. Release the button, or click again.

  What happens:
  2. A shortcut menu opens with "New Folder" highlighted.
  3. A new folder is created.

  What should happen:
  2. A shortcut menu opens with nothing highlighted.
  3. Nothing.

  This is a regression of bug 626462. I noticed the problem during a
  usability test in 2009 or 2010, when someone tapped absent-mindedly on
  the right mouse button and created a folder without realizing it.

  The fix is to add as much padding above every menu's first item, and
  below its last item, as there is above or below a menu separator (as
  illustrated in bug 659866).

  Fixing this would also help avoid accidentally closing a menu in the
  menu bar, when its first item is a submenu or other control that is
  dangerously close to other items in the menu bar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1281617/+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 328444] Re: gnome-terminal shortcuts: Alt+Shift+1 shows as Alt+! etc.

** Changed in: gnome-terminal
   Status: Confirmed => Expired

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

Title:
  gnome-terminal shortcuts: Alt+Shift+1 shows as Alt+! etc.

Status in GNOME Terminal:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-terminal

  Using Jaunty alpha 4, updating packages daily.

  I use irssi a lot, using gnome-terminal. By default irssi uses Alt+num
  to change windows, gnome-terminal uses Alt+num to change tabs. When
  multiple tabs are open, Alt+num keypress is catched by gnome-terminal,
  so I decided to bind tab keys differently:

  Alt-Shift-1 -> Tab 1
  Alt-Shift-2 -> Tab 2
  etc.

  The keypresses function just fine, but they are displayed like this:

  Alt-Shift-1 -> Alt-!
  Alt-Shift-2 -> Alt-@
  etc. (depends on keymap used)

  This behavious is, in my opinion, wrong.

  See screenshot (Finnish keymap used).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/328444/+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 1696710] Re: Ubuntu 16.04.02: depmod: WARNING: needs unknown symbol .TOC.

2018-05-03 Thread Juerg Haefliger

Verified that the new package fixes the issue.

** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty

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

Title:
  Ubuntu 16.04.02: depmod: WARNING:  needs unknown symbol
  .TOC.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Trusty:
  Fix Committed
Status in kmod source package in Xenial:
  Fix Released

Bug description:
  == Comment: #0 - Douglas Miller  - 2017-01-24 07:59:54 ==
  ---Problem Description---
  depmod does not handle .TOC symbol on powerpc platforms
   
  Contact Information = Douglas Miller  
   
  ---uname output---
  Linux p8le03 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:40:06 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = other 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Compile kernel, during modules_install target the messages appear. PPC64 
modules have a .TOC symbol which is required. It may be the only symbol with a 
period in the name, and so tools that restrict symbols based on a pattern may 
neglect to include .TOC.
   
  Userspace tool common name: depmod 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libkmod2:ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Douglas Miller :
  -Attach ltrace and strace of userspace application.

  == Comment: #3 - Douglas Miller  - 2017-01-24 08:12:58 ==
  kmod package:

  # dpkg --list |grep kmod
  ii  kmod   22-1ubuntu4
 ppc64el  tools for managing Linux kernel modules
  ii  libkmod2:ppc64el   22-1ubuntu4
 ppc64el  libkmod shared library

  == Comment: #7 - Douglas Miller  - 2017-06-07 16:20:38 ==
   I was doing a build of upstream origin/master on Ubuntu 16.04.2 fresh 
install and still getting these messages. In the "make modules_install" output 
I see:

  ...
DEPMOD  4.12.0-rc4
  depmod: WARNING: 
/lib/modules/4.12.0-rc4/kernel/arch/powerpc/kernel/rtas_flash.ko needs unknown 
symb
  ol .TOC.
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1696710/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

2018-05-03 Thread sojusnik

Please change it to "confirmed". That's still a relevant issue.

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

Status in GTK+:
  Expired
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1698083/+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 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

This tarball file contains those 5 patches mentioned in the bug
description.

** Description changed:

Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.
+
+
+ So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.
+
+ And we have several Lenovo machines like Lenovo P520 which have 2
+ analogue audio codecs on them, to make the audio work on those machines,
+ the kernel needs 3 patches for alsa driver, and those 3 patches are
+ already in the linux kernel from linux-4.12, kernel is not a blocking
+ issue under ubuntu 18.04:
+
+ 7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
+ 56798e6b ALSA: hda - Use a helper function for renaming kctl names
+ ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420
+
+
+ Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib.
Because the ucm configuration files are named by card_long_name, these 5
patches intends to introduce the card_long_name searching for ucm and the
configuration folder/files for Lenovo machines with dual analogue codecs. the 5
patches are:
+
+ 2b9b3f01 ucm: Assure the user input card name not to exceed max size of
+ card long name (it is in the alsa-lib v1.1.4)
+
+ 4b9297e6 ucm: Load device-specific configuration file based on the card
+ long name (it is in the alsa-lib v1.1.4)
+
+ b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
+ the alsa-lib v1.1.6)
+
+ 181f8e25 ucm: adding the folder of card_long_name when finding verb conf
+ file (it is in the alsa-lib v1.1.6+)
+
+ 81db276f conf/ucm: increase the input volume for LineIn (it is in the
+ alsa-lib v1.1.6+)
+
+ To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
+ minor change to resolve the patch conflict. And I attached 5 patches to
+ this bug, these patches can be successfully applied to v1.1.3-5 without
+ any change.
+
+ After applying this patches, the ucm searcher will look for folder
+ according to card_long_name first, if it fails, it will fallback to use
+ card_name as before, so these 5 patches are safe and will not introduce
+ any regression.

** Attachment added: "patches.tar.bz2"

https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1768830/+attachment/5132947/+files/patches.tar.bz2

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

Title:
the audio can't work on Lenovo machines with dual analogue codecs
under ubuntu 18.04

Status in HWE Next:
New
Status in alsa-lib package in Ubuntu:
New

Bug description:
Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.

So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

And we have several Lenovo machines like Lenovo P520 which have 2
analogue audio codecs on them, to make the audio work on those
machines, the kernel needs 3 patches for alsa driver, and those 3
patches are already in the linux kernel from linux-4.12, kernel is not
a blocking issue under ubuntu 18.04:

7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
56798e6b ALSA: hda - Use a helper function for renaming kctl names
ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib.
Because the ucm configuration files are named by card_long_name, these 5
patches intends to introduce the card_long_name searching for ucm and the
configuration folder/files for Lenovo machines with dual analogue codecs. the 5
patches are:

2b9b3f01 ucm: Assure the user input card name not to exceed max size
of card long name (it is in the alsa-lib v1.1.4)

4b9297e6 ucm: Load device-specific configuration file based on the
card long name (it is in the alsa-lib v1.1.4)

b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
in the alsa-lib v1.1.6)

181f8e25 ucm: adding the folder of card_long_name when finding verb
conf file (it is in the alsa-lib v1.1.6+)

81db276f conf/ucm: increase the input volume for LineIn (it is in the
alsa-lib v1.1.6+)

To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
minor change to resolve the patch conflict. And I attached 5

[Touch-packages] [Bug 1768831] Re: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2018-05-03 Thread Rachel Greenham

belately thought of trying: running sudo update-initramfs -k all -c
produced no errors for both currently installed kernels:

rachel@spitfire:~$ sudo update-initramfs -k  all -c
update-initramfs: Generating /boot/initrd.img-4.15.0-21-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic

FWIW...

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

Title:
  package initramfs-tools 0.130ubuntu3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  kernel upgrade appeared to go OK actually; on the *second* reboot
  after that, this appeared after login.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:37:48 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-20 (71 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768831/+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 1768830] [NEW] the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

Public bug reported:

Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.


So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

And we have several Lenovo machines like Lenovo P520 which have 2
analogue audio codecs on them, to make the audio work on those machines,
the kernel needs 3 patches for alsa driver, and those 3 patches are
already in the linux kernel from linux-4.12, kernel is not a blocking
issue under ubuntu 18.04:

7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
56798e6b ALSA: hda - Use a helper function for renaming kctl names
ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420


Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

2b9b3f01 ucm: Assure the user input card name not to exceed max size of
card long name (it is in the alsa-lib v1.1.4)

4b9297e6 ucm: Load device-specific configuration file based on the card
long name (it is in the alsa-lib v1.1.4)

b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
the alsa-lib v1.1.6)

181f8e25 ucm: adding the folder of card_long_name when finding verb conf
file (it is in the alsa-lib v1.1.6+)

81db276f conf/ucm: increase the input volume for LineIn (it is in the
alsa-lib v1.1.6+)

To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
minor change to resolve the patch conflict. And I attached 5 patches to
this bug, these patches can be successfully applied to v1.1.3-5 without
any change.

After applying this patches, the ucm searcher will look for folder
according to card_long_name first, if it fails, it will fallback to use
card_name as before, so these 5 patches are safe and will not introduce
any regression.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: alsa-lib (Ubuntu)
 Importance: Critical
 Status: New


** Tags: originate-from-1735041 sutton

** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)

** Summary changed:

- the audio can't work on Lenovo machines with dual analogue cocecs underubuntu 
18.04
+ the audio can't work on Lenovo machines with dual analogue codecs under 
ubuntu 18.04

** Tags added: originate-from-1735041 sutton

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  
  So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

  And we have several Lenovo machines like Lenovo P520 which have 2
  analogue audio codecs on them, to make the audio work on those
  machines, the kernel needs 3 patches for alsa driver, and those 3
  patches are already in the linux kernel from linux-4.12, kernel is not
  a blocking issue under ubuntu 18.04:

  7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
  56798e6b ALSA: hda - Use a helper function for renaming kctl names
  ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

  
  Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size
  of card long name (it is in the alsa-lib v1.1.4)

  4b9297e6 ucm: Load device-specific configuration file based on the
  card long name (it is in the alsa-lib v1.1.4)

  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
  in the alsa-lib v1.1.6)

  181f8e25 ucm: adding the folder of card_long_name when finding verb
  conf file (it is in the alsa-lib v1.1.6+)

  81db276f conf/ucm: increase the input volume for LineIn (it is in the

[Touch-packages] [Bug 1768831] [NEW] package initramfs-tools 0.130ubuntu3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2018-05-03 Thread Rachel Greenham

Public bug reported:

kernel upgrade appeared to go OK actually; on the *second* reboot after
that, this appeared after login.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 13:37:48 2018
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-02-20 (71 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package initramfs-tools 0.130ubuntu3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  kernel upgrade appeared to go OK actually; on the *second* reboot
  after that, this appeared after login.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 13:37:48 2018
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-20 (71 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768831/+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 1085976] Re: Documentation has "FIXME" items that are unfixed

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Documentation has "FIXME" items that are unfixed

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  The Ubuntu package libgtk-3-doc supplies the items of interest...
  In the directory /usr/share/doc/libgtk-3-doc/gtk3 there are 3 files that 
contain FIXME content

  In that directory:
  # grep FIXME *
  GtkApplication.html:FIXME: MISSING XINCLUDE CONTENT
  GtkBuilder.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:  FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT
  #

  I am just starting with GTK+ and Glade, so having this instead of the
  first code sample in the gtk-getting-started page is a show-stopper.
  I suggest it's as urgent as documentation bugs get.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgtk-3-doc 3.4.2-0ubuntu0.5
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: i386
  Date: Mon Dec  3 05:59:17 2012
  Dependencies:
   
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1085976/+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 543611] Re: emacsclient -c randomly crashes emacs about 1 in every 5 to 10 times

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  emacsclient -c randomly crashes emacs about 1 in every 5 to 10 times

Status in GNU Emacs:
  Fix Released
Status in GTK+:
  Expired
Status in emacs23 package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: emacs23

  I am trying to start using emacs --daemon and emacsclient, so that I
  can easily have multiple emacs windows sharing a single process.
  However, my attempts are frustrated by the fact that when I use
  "emacsclient -c" to create a new window in an exising emacs session,
  emacs crashes about 1 in 5 times. It seems completely random.

  Here's what I've been using to reproduce this:

  x=0; emacs23 -Q --daemon &>/dev/null; while emacsclient -c
  &>/dev/null; do x=$(( $x + 1 )); done; echo "Created $x windows before
  crash."

  
  That will start the daemon, and then keep spawning new emacs windows as long 
as the daemon is running. Just keep closing the windows, and new ones will pop 
up. Every time I do this command, I get a different number of windows before 
emacs crashes. On my last five tries, I have gotten 7, 17, 12, 18, and 24 
windows. Hence my claim of randomness.

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Mar 21 10:34:10 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: nvidia wl
  Package: emacs23 23.1+1-4ubuntu3.1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.31-13bfsbfq1.43-generic
  SourcePackage: emacs23
  Uname: Linux 2.6.31-13bfsbfq1-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/emacs/+bug/543611/+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 803824] Re: Can't change the gtkfilechooser view

** Changed in: gtk
   Status: In Progress => Expired

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

Title:
  Can't change the gtkfilechooser view

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When using File open in an application the Nautilus File Dialog shows up. It 
has severe shortcomings (see attached screenshot):
  (1) Hidden files show or don't show based on the selection made in Nautilus 
earlier. No UI (e.g. at (2)) is provided to toggle (Ctrl+H seems to work)
  (3) display is always in detail mode Ctrl1-3 or Ctlr+- to alter the display 
don't work.

  Show/Hide hidden files is available through keyboard shortcuts or rightclick, 
so a UI element is a nice-to-have.
  The lack of display settings (e.g. specify columns like in the main window) 
like icons/list/details is a usability issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/803824/+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 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.

2018-05-03 Thread Jan Niklas Hasse

New upstream bug: https://gitlab.gnome.org/GNOME/gtk/issues/322

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

Title:
  Right-click should not pre-light first option, too easy to
  accidentally select the first Context-menu option.

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When I right click in nautilus, the context menu appear. If I right
  click on a menu item, the function of that menu item is performed.
  This is very annoying, because when the context menu appears, the
  mouse is at the first menu item, so if you accidentally right click
  two times, you will surely perform the function of the first menu
  item! Everytime I right click in desktop, i probably create a new
  Folder!

  I think there maybe 2 solutions to this:
  - To perform the function of a menu item, only left click is allowed.
  - When the user right click, the context menu will appear at a bit lower 
position, so the mouse will not be at the first menu item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/410636/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

** Changed in: cairo
   Status: Unknown => Confirmed

** Changed in: cairo
   Importance: Unknown => Medium

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

A patch to fix the crash is here:
https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6

If we fail to get cairo fixed for any reason, it's probably possible to
do a workaround/fix in ubiquity. But I think there are now multiple
reasons to fix cairo as first preference.

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

** Also affects: cairo via
   https://bugs.freedesktop.org/show_bug.cgi?id=98883
   Importance: Unknown
   Status: Unknown

** Changed in: ubiquity (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Andrea Azzarone (azzar1)

** Changed in: ubiquity (Ubuntu Bionic)
 Assignee: Daniel van Vugt (vanvugt) => Andrea Azzarone (azzar1)

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

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

** Changed in: cairo (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: cairo (Ubuntu)
   Status: New => In Progress

** Changed in: cairo (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: cairo (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in cairo source package in Bionic:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions

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

[Touch-packages] [Bug 439239] Re: Selecting a folder to save to loses focus on file name

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Selecting a folder to save to loses focus on file name

Status in GTK+:
  Expired
Status in One Hundred Papercuts:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  This bug has occured multiple times before, however the fixes no
  longer seem to be working:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/130224,
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/22322, and
  their duplicates.

  In short: the task of saving a file is broken as soon as the user
  chooses a different folder.  Typing no longer renames the file but
  instead starts searching for folders in the list, however the text
  selecting the filename is still highlighted.

  I believe the task of naming a file to save is much more common than
  having to do a text search to find a folder to save to (they're
  already alphabetically ordered).  Accordingly, the filename should
  never lose focus, even when the user is active inside the other parts
  of the file save dialog (eg making/selecting a folder to save to).

  
  To reproduce: in Gedit, make a new file and File->Save as.  Click a folder 
and then start typing.  A similar thing happens if you save a picture in 
Firefox.

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Sep 30 01:55:52 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: libgtk2.0-0 2.18.0-1ubuntu2
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
  SourcePackage: gtk+2.0
  Uname: Linux 2.6.31-11-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/439239/+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 1164829] Re: Place an "Add Printer" button on print dialog

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Place an "Add Printer" button on print dialog

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When I print a document (by choosing File then Print) I am able to
  select any installed printer  But, sometimes I want to use a printer
  on the network and I have not installed it yet.  I really wish there
  was a button on the print dialog box (from File/Print) that would be
  labeled "Add Printer" that would take me to the printers/add a printer
  dialog box.  That way, I could add the printer I want and have it
  listed in the list of printers without me having to leave the
  application, go to the printers application, add a printer, return to
  the original application and choose File and Print then choose the new
  printer.

  This is like when you save a document and you realize the folder you
  want does not exist, you don't have to exit and go to Nautilus, create
  the folder, then return to the application to save the file in the new
  folder.  You just select the Create a New folder button when you save
  the file.  Same idea with the printer - when you print and the printer
  does not exist click on a button that allows you to add it right then.

  Note, I am not suggesting that network printers be automatically
  installed.  Just add a button on the File/Print dialog box that takes
  you to Printer/Add New Printer box.  No other OS makes it this easy to
  allow you to add a printer at the time when you print a document so
  this would be helpful.  Also helpful for the new person who wants to
  print something to a network printer and when they don't see it in the
  list of installed printers, they wouldn't have to ask "where do I go
  to add a printer" since the button would be right there.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1164829/+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 410636] Re: Right-click should not pre-light first option, too easy to accidentally select the first Context-menu option.

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Right-click should not pre-light first option, too easy to
  accidentally select the first Context-menu option.

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When I right click in nautilus, the context menu appear. If I right
  click on a menu item, the function of that menu item is performed.
  This is very annoying, because when the context menu appears, the
  mouse is at the first menu item, so if you accidentally right click
  two times, you will surely perform the function of the first menu
  item! Everytime I right click in desktop, i probably create a new
  Folder!

  I think there maybe 2 solutions to this:
  - To perform the function of a menu item, only left click is allowed.
  - When the user right click, the context menu will appear at a bit lower 
position, so the mouse will not be at the first menu item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/410636/+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 1480387] Re: Clicking a date to go back or forward a month causes repeated jumps between two dates

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Clicking a date to go back or forward a month causes repeated jumps
  between two dates

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  I asked in #ubuntu-desktop and people couldn't reproduce this in vivid
  or trusty. It happened for me in the most recent wily iso.

  Open the indicator, click one of the greyed dates at the start or end
  of the month (sometimes requires more than one go). The active date
  starts to repeatedly jump between this date and another one. I ran
  with G_MESSAGES_DEBUG=all and when it's happening this is spammed (I
  clicked a date in 2015-05).

  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-30 00:00:00..2015-06-30 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed
  (process:32382): Indicator-Datetime-DEBUG: PlannerMonth 0x2727310 setting 
calendar month range: [2015-05-01 00:00:00..2015-05-31 23:59:59]
  (process:32382): Indicator-Datetime-DEBUG: 0x2728730 setting date range to 
[2015-05-29 00:00:00..2015-06-29 00:00:00]
  (process:32382): Indicator-Datetime-DEBUG: rebuilding because the date range 
changed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jul 31 17:09:43 2015
  InstallationDate: Installed on 2012-10-07 (1026 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to wily on 2013-05-07 (815 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1480387/+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 1685878] Re: Gedit bottom scroll bar goes on top of final line