date:20180527

Manfred Steiner:

1) What is "Beamer"? Is this a program available from the Ubuntu
repositories, a piece of hardware, etc.?

2) To clarify the table in #10, it appears the only part that isn't as
expected is how after configuring the Internal LCD to be off and VGA to
be active, you restart, and at the login screen the Internal LCD is
turned on, while the external VGA is not displaying. However, you are
expecting that the external VGA is on, while Internal LCD is off.
Correct?

To use your table to further clarify:

.. Connected ... Internal LCD ... VGA...GOOD?
-
First time ... Monitor on VGA .. L+S  E ... Yes
After Login .. Monitor on VGA .. S .. E ... Yes
After reconfiguration  Monitor on VGA .. Off  S ... Yes
After Restart  Monitor on VGA .. Off  L+S . Yes
After Login .. Monitor on VGA .. Off  S ... Yes
Restart with Beamer .. Beamer on VGA ... L+S  E ... No
Restart with Monitor . Monitor on VGA .. L+S  E ... No
After Login .. Monitor on VGA .. Off  S ... Yes

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor

Formatted table again, is there any way to edit a posted entry or to
format (markdown, ..)?

.. Connected ... Internal LCD ... VGA
--
First time ... Monitor on VGA .. L+S  E
After Login .. Monitor on VGA .. S .. E
After reconfiguration  Monitor on VGA .. Off  S
After Restart  Monitor on VGA .. Off  L+S
After Login .. Monitor on VGA .. Off  S
Restart with Beamer .. Beamer on VGA  .. L+S  E
Restart with Monitor . Monitor on VGA .. L+S  E
After Login .. Monitor on VGA .. Off  S

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773484] Re: Login screen not moved to used monitor

I hope this table is correct. I will verify it as soon as possible (when I have 
a beamer).
Reconfiguration is done with GUI Display dialog (to LCD off and VGA as active 
display).
L+S ... Login/System bar
E   ... Empty screen
Off ... Screen off
S   ... Normal working screen with system bar ...

 ConnectedInternal LCD   VGA
--
First time   Monitor on VGA   L+SE
After Login  Monitor on VGA   S  E
After reconfigurationMonitor on VGA   OffS
After RestartMonitor on VGA   OffL+S
After Login  Monitor on VGA   OffS
Restart with Beamer  Beamer on VGAL+SE
Restart with Monitor Monitor on VGA   L+SE
After Login  Monitor on VGA   OffS

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1762385] Re: dell_wmi: Unknown key codes

2018-05-27 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  dell_wmi: Unknown key codes

Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * Bogus keycode messages produced by the kernel / user annoyance
   * rfkill keyboard shortcuts not working as intended on some Dell machines

  [Test Case]

   * check that there are no spurious kernel messages about unknown keys
  in journalctl upon RFKill key presses

   * check that RFKill key presses work correctly and kill/restore RF
  capabilities

  [Regression Potential]

   * The change is scoped to particular SKUs and thus should only affect them
   * It is related to matching gsd support, which is in-place on xenial and up

  [Solution]
  Cherrypick upstream commit 
https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f

  [Original Bug report]

  RFKill key produces these messages in kernel log:

  dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed

  This key code is a notification and should be added as KEY_IGNORE
  here:
  https://github.com/torvalds/linux/blob/master/drivers/platform/x86
  /dell-wmi.c#L263

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dmig   2737 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 18:09:03 2018
  InstallationDate: Installed on 2018-03-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  MachineType: Dell Inc. Inspiron 5379
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic 
root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.0
  dmi.board.name: 0C6J64
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5379
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1772844] Re: snapd didn't initialize all the seeded snaps

2018-05-27 Thread Yuan-Chen Cheng

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Confirmed
Status in snapd:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

2018-05-27 Thread Tom McLaughlin

I confirm that 237-3ubuntu10.1 works also

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+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 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

Does the problem occur only in Xorg sessions or Wayland too?

Please run 'apport-collect 1773651' to help us get more information
about the machine.

** Changed in: gnome-desktop (Ubuntu)
   Status: New => Incomplete

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

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Incomplete

** Tags added: nouveau

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

Status in gnome-desktop package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete
Status in software-properties package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Incomplete

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1773549] Re: Pulse audio does not remember default sink

I agree it could be better. If you would like to suggest ways to improve
that module, please report them to the developers here:

  https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  It seems like pulseaudio is picking the wrong audio sink as a default
  in different scenarios.

  On my computer I have the default onboard Intel HDA audio as well as a
  USB headset. On the network, there is one pulse instance advertising
  itself.

  I always set the onboard audio as the default audio sink. However,
  after every reboot or resume or `pulseaudio -k`, the wrong sink is
  picked (and the one I set previously is *not* picked).

  When I enable discovery of remote pulse instances, sometimes the one
  on my network is picked as default, but sometimes my headset is picked
  instead of the onboard sink. Then again, if I disable discovery
  sometimes the onboard sink gets picked as default. There seems to be
  no clear pattern on when it selects what.

  I have even entered the following in /etc/pulse/default.pa:

  set-default-sink alsa_output.pci-_00_1b.0.analog-stereo
  set-default-source 
alsa_input.usb-SteelSeries_SteelSeries_Arctis_7-00.analog-mono

  But this doesn't have any effect at all.

  I also noticed that *sometimes*, pulse updates the file at
  `~/.config/pulse/f8a78acf499a402aa80f90af9ef5c15c-default-sink` to
  point to the correct audio sink that I selected in `pavucontrol`, but
  not always. Even if I write to that file manually to select a default
  sink, the file gets overwritten by pulse on the next start with the
  default sink that it chose.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  devkid 3487 F pulseaudio
   /dev/snd/controlC2:  devkid 3487 F pulseaudio
   /dev/snd/pcmC0D0p:   devkid 3487 F...m pulseaudio
   /dev/snd/controlC0:  devkid 3487 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat May 26 17:07:55 2018
  ExecutablePath: /usr/bin/pulseaudio
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-05-26T17:01:12.271701

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773549/+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 1760910] Re: Gdebi crash in Ubuntu Studio 18.04

2018-05-27 Thread Francis Marsden

Same problem here, using Xubuntu 18.04. (Clean install, not upgrade)  If
I click on a .deb file and choose "open with gdebi", the gui opens and
checks for depencies, but when "install" is clicked the gui disappears
(crashes).  But if I open gdebi via terminal, it works fine.

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

Title:
  Gdebi crash in Ubuntu Studio 18.04

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  Gdebi opens normal, but when you click install package, it closes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
  Uname: Linux 4.15.0-13-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Apr  3 12:31:17 2018
  InstallationDate: Installed on 2018-03-29 (4 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180328)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1760910/+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 1773710] [NEW] package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить

2018-05-27 Thread pavel kkkko

Private bug reported:

/

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libxml2-utils 2.9.4+dfsg1-6.1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Mon May 28 01:09:15 2018
ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
InstallationDate: Installed on 2018-05-20 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Нет такого файла или каталога: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: libxml2
Title: package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to install/upgrade: 
пакет абсолютно неработоспособен; перед настройкой его  следует переустановить
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

** Information type changed from Public to Private

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

Title:
  package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to
  install/upgrade: пакет абсолютно неработоспособен; перед настройкой
  его  следует переустановить

Status in libxml2 package in Ubuntu:
  New

Bug description:
  /

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libxml2-utils 2.9.4+dfsg1-6.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon May 28 01:09:15 2018
  ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
  InstallationDate: Installed on 2018-05-20 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Нет такого файла или каталога: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: libxml2
  Title: package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to 
install/upgrade: пакет абсолютно неработоспособен; перед настройкой его  
следует переустановить
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1773710/+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 1754686] Re: libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like slack-desktop

2018-05-27 Thread arooni

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

Would love a way to install libcurl3 alongside libcurl4.  Right now vpn
unlimited doesn't work either because it depends on libcurl3

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

Title:
  libcurl4 Conflicts: libcurl3 - prevents install of 3rd party apps like
  slack-desktop

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Updating the curl package pulls in libcurl4, which for some reason
  forces libcurl3 to be removed. This prevents 3rd party apps that still
  build against libcurl3 from being installed. Isn't there a more
  graceful way to effect the transition from libcurl3 to libcurl4?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libcurl4 7.58.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:10:10 2018
  EcryptfsInUse: Yes
  SourcePackage: curl
  UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754686/+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 1773697] Re: [USB-Audio - PX USB, playback] No sound at all after kernel upgrade

2018-05-27 Thread DSHR

Syslog output from non working kernel with failed probe message:

May 27 22:12:55 ThinkPad-T550 kernel: [   50.880075] usb 2-3: new full-speed 
USB device number 5 using xhci_hcd
May 27 22:12:55 ThinkPad-T550 kernel: [   51.040249] usb 2-3: New USB device 
found, idVendor=19b5, idProduct=0021
May 27 22:12:55 ThinkPad-T550 kernel: [   51.040251] usb 2-3: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
May 27 22:12:55 ThinkPad-T550 kernel: [   51.040252] usb 2-3: Product: PX USB
May 27 22:12:55 ThinkPad-T550 kernel: [   51.040254] usb 2-3: Manufacturer: 
Bowers & Wilkins
May 27 22:12:55 ThinkPad-T550 kernel: [   51.040255] usb 2-3: SerialNumber: 
ABCDEF0123456789
May 27 22:12:55 ThinkPad-T550 mtp-probe: checking bus 2, device 5: 
"/sys/devices/pci:00/:00:14.0/usb2/2-3"
May 27 22:12:55 ThinkPad-T550 mtp-probe: bus: 2, device: 5 was not an MTP device
May 27 22:12:55 ThinkPad-T550 kernel: [   51.074237] hidraw: raw HID events 
driver (C) Jiri Kosina
May 27 22:12:55 ThinkPad-T550 kernel: [   51.099805] snd-usb-audio: probe of 
2-3:1.0 failed with error -22
May 27 22:12:55 ThinkPad-T550 kernel: [   51.107942] usb 2-3: 2:1: cannot get 
min/max values for control 2 (id 2)
May 27 22:12:55 ThinkPad-T550 kernel: [   51.107984] snd-usb-audio: probe of 
2-3:1.1 failed with error -22
May 27 22:12:55 ThinkPad-T550 kernel: [   51.112502] usbcore: registered new 
interface driver snd-usb-audio
May 27 22:12:55 ThinkPad-T550 kernel: [   51.115517] usbcore: registered new 
interface driver usbhid
May 27 22:12:55 ThinkPad-T550 kernel: [   51.115518] usbhid: USB HID core driver
May 27 22:12:55 ThinkPad-T550 kernel: [   51.121643] input: Bowers & Wilkins PX 
USB as /devices/pci:00/:00:14.0/usb2/2-3/2-3:1.2/0003:19B5:0021.000
1/input/input19

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

Title:
  [USB-Audio - PX USB, playback] No sound at all after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly -
  it seems to hinder the audio system to recognize the USB-device as a
  sound device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:

[Touch-packages] [Bug 1773700] [NEW] [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all

2018-05-27 Thread remi

Public bug reported:

I just installed ubuntu, and immediately had problems of very loud and 
crackling sound no matter what sound I played.
I tried the three solutions listed here 
https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in 
no sound at all, and now even if I revert back everything, I can't get any 
sound out from the speakers.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
 /dev/snd/controlC0:  remuth 1038 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun May 27 22:37:20 2018
InstallationDate: Installed on 2018-05-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
 /dev/snd/controlC0:  remuth 1038 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX390UAK.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX390UAK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX390UAK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1773700

Title:
  [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I just installed ubuntu, and immediately had problems of very loud and 
crackling sound no matter what sound I played.
  I tried the three solutions listed here 
https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in 
no sound at all, and now even if I revert back everything, I can't get any 
sound out from the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
   /dev/snd/controlC0:  remuth 1038 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 22:37:20 2018
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   remuth 1038 F...m pulseaudio
   /dev/snd/controlC0:  remuth 1038 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX390UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX390UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX390UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773700/+subscriptions

-- 
Mailing list:

[Touch-packages] [Bug 1773697] [NEW] [USB-Audio - PX USB, playback] No sound at all after kernel upgrade

2018-05-27 Thread DSHR

Public bug reported:

Bug report has been generated on a partially working configuration. That
allows ubuntu-bug to do more work.

USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones started
working when upgrading kernel from 4.13 to 4.15 series. Then it suddenly
stopped working again on newer kernels. The bug report has been
generated on the latest working mainline kernel 4.15.7. All newer
kernels have some usb quirks in place, which should fix the playback
sample rates to 48 kHz. The quirk seems not to be working correctly - it
seems to hinder the audio system to recognize the USB-device as a sound
device.

The Headphones work on kernels before 4,15.7 when manually configuring
pulseaudio to a default samplerate of 48 kHz.

PX Headphones are on the newest firmware level.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
Uname: Linux 4.15.7-041507-lowlatency x86_64
AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  dshr   2729 F pulseaudio
 /dev/snd/controlC1:  dshr   2729 F pulseaudio
 /dev/snd/controlC0:  dshr   2729 F pulseaudio
CurrentDesktop: GNOME
Date: Sun May 27 22:21:53 2018
InstallationDate: Installed on 2016-02-05 (841 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/zsh
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
Symptom_Card: PX USB - PX USB
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  dshr   2729 F pulseaudio
 /dev/snd/controlC1:  dshr   2729 F pulseaudio
 /dev/snd/controlC0:  dshr   2729 F pulseaudio
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [USB-Audio - PX USB, playback] No sound at all
UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
dmi.bios.date: 06/23/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: N11ET33W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20CJS00Q00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T550
dmi.product.name: 20CJS00Q00
dmi.product.version: ThinkPad T550
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1773697

Title:
  [USB-Audio - PX USB, playback] No sound at all after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly -
  it seems to hinder the audio system to recognize the USB-device as a
  sound device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64

[Touch-packages] [Bug 1773484] Re: Login screen not moved to used monitor

Manfred Steiner:

1) When the display is set to mirror, at the login screen does it show
up on one monitor or both?

2) When the display is set to mirror, after you login does the system
bar show up on one monitor or both?

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773685] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-05-27 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  IDK Anything about this

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  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
  Date: Sun May 27 13:47:30 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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/1773685/+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 1773687] Re: [bionic] no unattended installation

2018-05-27 Thread Dustin Kirkland 

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

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1773687/+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 1743553] Re: [Typo] Missing word in Zesty Man Page for e4defrag

2018-05-27 Thread Theodore Ts'o

Thanks, fixed in upstream e2fsprogs-maint.   Will be in next 1.44.x
release of e2fsprogs.

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

Title:
  [Typo] Missing word in Zesty Man Page for e4defrag

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Location: First sentence, second paragraph, Notes section.
  http://manpages.ubuntu.com/manpages/zesty/man8/e4defrag.8.html

  Original: "It safe to run e4defrag on a file  while  it  is  actively
  in  use  by another  application."

  Text should state "It is safe to run..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1743553/+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 1773693] [NEW] xserver-xorg-video-nouveau requires reboot to apply changes

Public bug reported:

Using update-manager to install or update xserver-xorg-video-nouveau
should prompt to reboot

** Affects: plasma-discover (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  xserver-xorg-video-nouveau requires reboot to apply changes

Status in plasma-discover package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Using update-manager to install or update xserver-xorg-video-nouveau
  should prompt to reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1773693/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

2018-05-27 Thread Theodore Ts'o

The blog post here:
https://raid6.com.au/posts/fs_ext4_external_journal_caveats/

is not generally true.   What journal_async_commit does is convert the
sequence:

1.  write journal blocks
2.  cache flush
3.  write journal commit block
4.  cache flush

... to:

1.  write journal blocks
2.  write journal commit block
3.  cache flush

This tends to make a lot of difference on HDD's from a performance
perspective, because a cache flush commands are so expensive.   On an
SSD with a competently implemented flash translation layer (FTL), it
shouldn't make much of a difference from a performance perspective, and
it shouldn't hardly any difference from write endurance perspective.

The way flash works is that flash chips are organized into erase blocks,
which might be say, 64k.   This is the minimal size must be erased as a
unit.  Once an erase block is cleared (which is the slow operation) it
can be written a flash page (typically 4k in size) at a time.  Once a
flash page is written, it can't be erased except by erasing the entire
erase block.   If most of the erase blocks are filled, either with real
data, or with garbage (former data contents which have been superceded),
then it might be necessary to copy the still-used data contents to other
erase blocks, so that an erase block can be emptied so it can be erased.
If it is necessary to do those extra copies before the erase block can
be rebase, this is cause of the "write amplifification" effect.

However, doing an extra CACHE FLUSH operation (which is what
journal_async_commit eliminates) should not make any difference on any
competently implemented FTL on a normal SSD.

The place where it make a difference is on what gets referred to as
"cost optimized" flash in polite company, or "crap flash" by more honest
engineers.  You will most often find this in eMMC flash or SD cards
found in the cash register aisle of Micro Center (assuming of course,
that you actually get honestly labelled flash as opposed to a SD card
claiming to have 1G of flash, but which is only backed by 16 MB of flash
--- such that the 16MB + 4k write will end up overwriting previously
written data).In these "cost optimized" flash, the FTL may end up
mapping each 64k erase page to a 64k LBA address space.  In that case, a
4k write followed by a cache flush will end up being the equivalent of a
64k flash erase/write.  In the even more awful "crappy flash", each 64k
erase block is direct mapped to a 64k LBA address space.  In that case,
if you are constantly overwriting any portion of the flash (either the
FAT table for FAT file systems, or the journal in ext4), then those
erase blocks will get worn out first --- and once they are worn out, the
flash device becomes broken.

But I emphasize that this is really only a problem for crap flash.  For
a normal SSD with a competent FTL, the use of journal_async_commit (or
not using journal_async_commit) should not make any real difference to
how long your flash device lasts.

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1773693] Re: xserver-xorg-video-nouveau requires reboot to apply changes

Also with plasma-discover

** Also affects: plasma-discover (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  xserver-xorg-video-nouveau requires reboot to apply changes

Status in plasma-discover package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New

Bug description:
  Using update-manager to install or update xserver-xorg-video-nouveau
  should prompt to reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1773693/+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 1773687] Re: [bionic] no unattended installation

2018-05-27 Thread Dirk Eddelbuettel

Also, it is not the package per se but possibly the debconf settings --
installing tzdata_2018e-1 from Debian reveals the same issue.

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1773687/+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 1187981] Re: symbol conflicts in libtimezonemap1

2018-05-27 Thread Bug Watch Updater

** Changed in: gnome-control-center
   Status: Incomplete => Confirmed

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

Title:
  symbol conflicts in libtimezonemap1

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in libtimezonemap package in Ubuntu:
  Incomplete
Status in ubiquity package in Ubuntu:
  Incomplete
Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  In gnome-control-center 3.8 all built in panels are statically linked.
  When the indicator-datetime panel loads it is picking up the symbols
  from the gnome datetime panel rather than the ones in libtimezonemap1,
  causing g-c-c to segfault.

  All public symbols in libtimezonemap1 need to renamed to avoid
  conflict. Likewise this might apply to any other g-c-c plugins that
  have code cut+paste from the built in gnome panels.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-datetime 12.10.3daily13.05.06.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3
  Uname: Linux 3.9.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu1
  Architecture: amd64
  Date: Thu Jun  6 12:35:40 2013
  InstallationDate: Installed on 2012-09-23 (256 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MarkForUpload: True
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1187981/+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 1773687] [NEW] [bionic] no unattended installation

2018-05-27 Thread Dirk Eddelbuettel

Public bug reported:

Package: tzdata
Version: 2018d-1
Ubuntu release: 18.04

There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
When running 

   apt-get install tzdata

I now _always_ drop into an interactive selection of the timezone 'area'
and 'zone'. This was not the case before; it is also not the case in
Debian 'unstable' right now.

I looked into the postinst script, but I can't figure out where the
preseeded info would be. I tried debconf-set-selections with a preseed
file, but no luck.

This blocks usage of tzdata in Docker containers and is there for a bit
annoying.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: tzdata 2017c-0ubuntu0.17.10
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 27 13:17:42 2018
InstallationDate: Installed on 2017-12-31 (147 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
PackageArchitecture: all
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: tzdata
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1773687/+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 1773687] Re: [bionic] no unattended installation

2018-05-27 Thread Dirk Eddelbuettel

Note that I filed this on my 17.10 machine so the final paragraph is
mildly inaccurate.

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

Title:
  [bionic] no unattended installation

Status in tzdata package in Ubuntu:
  New

Bug description:
  Package: tzdata
  Version: 2018d-1
  Ubuntu release: 18.04

  There appears to be a regression with the preseeding data for tzdata in the 
18.04 release.
  When running 

 apt-get install tzdata

  I now _always_ drop into an interactive selection of the timezone
  'area' and 'zone'. This was not the case before; it is also not the
  case in Debian 'unstable' right now.

  I looked into the postinst script, but I can't figure out where the
  preseeded info would be. I tried debconf-set-selections with a preseed
  file, but no luck.

  This blocks usage of tzdata in Docker containers and is there for a
  bit annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: tzdata 2017c-0ubuntu0.17.10
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 27 13:17:42 2018
  InstallationDate: Installed on 2017-12-31 (147 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1773687/+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 1773685] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-05-27 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  IDK Anything about this

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  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
  Date: Sun May 27 13:47:30 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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/1773685/+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 1773685] [NEW] package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2018-05-27 Thread Joshua Griffin

Public bug reported:

IDK Anything about this

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
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
Date: Sun May 27 13:47:30 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2018-05-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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/1773685

Title:
  package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  IDK Anything about this

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  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
  Date: Sun May 27 13:47:30 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-05-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 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/1773685/+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 1773484] Re: Login screen not moved to used monitor

Screenshot of internal LCD and external VGA in mirror configuration in
attachment.

** Attachment added: "screenshot_lcdAndvga_mirrored.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+attachment/5145283/+files/screenshot_lcdAndvga_mirrored.png

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1773660] Re: Crontab fails with 'Permission denied'

2018-05-27 Thread nmaxx

** Tags added: bionic

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

Title:
  Crontab fails with 'Permission denied'

Status in cron package in Ubuntu:
  New

Bug description:
  It is the same tab that was running on 16.04. I have web searched the
  issue, and reported to the Mate forum, without solution. I am not a
  newbie, I know about permissions, and I have tried everything. My user
  account is added to the crontab group. The file in
  /var/spool/cron/crontabs/ has the correct permissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1773660/+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 1773660] [NEW] Crontab fails with 'Permission denied'

2018-05-27 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

It is the same tab that was running on 16.04. I have web searched the
issue, and reported to the Mate forum, without solution. I am not a
newbie, I know about permissions, and I have tried everything. My user
account is added to the crontab group. The file in
/var/spool/cron/crontabs/ has the correct permissions.

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

-- 
Crontab fails with 'Permission denied'
https://bugs.launchpad.net/bugs/1773660
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cron in Ubuntu.

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

[Touch-packages] [Bug 1773660] Re: Crontab fails with 'Permission denied'

2018-05-27 Thread nmaxx

** Project changed: canonical-identity-provider => cron (Ubuntu)

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

Title:
  Crontab fails with 'Permission denied'

Status in cron package in Ubuntu:
  New

Bug description:
  It is the same tab that was running on 16.04. I have web searched the
  issue, and reported to the Mate forum, without solution. I am not a
  newbie, I know about permissions, and I have tried everything. My user
  account is added to the crontab group. The file in
  /var/spool/cron/crontabs/ has the correct permissions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1773660/+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 1729558] Re: [regression] In Java apps like Netbeans, dark menu bars don't look good for disabled elements

2018-05-27 Thread Launchpad Bug Tracker

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

** Changed in: openjdk-9 (Ubuntu)
   Status: New => Confirmed

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

Title:
  [regression] In Java apps like Netbeans, dark menu bars don't look
  good for disabled elements

Status in Ubuntu theme:
  Invalid
Status in openjdk-8 package in Ubuntu:
  Confirmed
Status in openjdk-9 package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  This fix, #961679, specifically Ambiance/gtk-2.0/gtkrc:346
  (http://bazaar.launchpad.net/~ubuntu-art-pkg/ubuntu-
  themes/trunk/revision/583), makes disabled elements in menus look
  terrible.

  Unfortunately I'm not aware of an easy way to get screenshots of open
  menus, so hopefully these attached phone pictures of Netbeans are
  enough to illustrate the issue.

  As you can see it is hard to tell the difference between what is
  disabled and what isn't, and the disabled items look fuzzy (easier to
  observe on monitor).

  I really don't see the issue with lighter menus, but if they must stay
  dark then the readability / contrast of disabled items needs to be
  fixed.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1729558/+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 282196] Re: pkcs15-tool fails with Cryptoflex e-gate 32 k in Broadcom 5800 cardreader

2018-05-27 Thread David Ward

Comment #10 indicates this was fixed in OpenSC 0.12.2, which was
released in precise (before it reached end-of-life).

opensc (0.12.2-2ubuntu1) precise; urgency=low

  * Merge from Debian testing. (LP: #979986)  Remaining changes:
- debian/patches/missing-libs.patch: Add libraries to allow opensc to build
- debian/opensc.docs: include html documentation
- debian/control: Depend on pcscd
- debian/control: Add dh-autoreconf as build-dependency
- debian/rules: Call autoreconf sequence to rebuild autotools files
- debian/opensc.install: Added profiles

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

** Changed in: pcsc-lite (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  pkcs15-tool fails with Cryptoflex e-gate 32 k in Broadcom 5800
  cardreader

Status in opensc package in Ubuntu:
  Fix Released
Status in pcsc-lite package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: opensc

  root@e6500:~# lsb_release -rd
  Description:  Ubuntu intrepid (development branch)
  Release:  8.10

  root@e6500:~# apt-cache policy opensc
  opensc:
Installiert: 0.11.4-5ubuntu1
Kandidat: 0.11.4-5ubuntu1
Versions-Tabelle:
   *** 0.11.4-5ubuntu1 0
  500 http://de.archive.ubuntu.com intrepid/universe Packages
  100 /var/lib/dpkg/status

  Expected result:

  pkcs15-tool -D should show a number of objects installed on card. This
  happens as expected with a OpenPGP card:

  ---cut here---
  root@e6500:~# pkcs15-tool -D
  PKCS#15 Card [OpenPGP Card]:
Version: 257
Serial number  : d27600012401010100011117
Manufacturer ID: OpenPGP project
Language   : de
Flags  : Login required, PRN generation, EID compliant

  PIN [Signature PIN]
Com. Flags: 0x3
ID: 01
Flags : [0x13], case-sensitive, local, initialized
Length: min_len:0, max_len:254, stored_len:254
Pad char  : 0x00
Reference : 1
Type  : ascii-numeric
Path  : 3f00
Tries left: 3

  ...etc.
  ---cut here---

  Real result: With a Cryptoflex e-gate 32k following happens if
  Broadcom 5800 cardreader is used:

  ---cut here---
  root@e6500:~# pkcs15-tool -D
  [pkcs15-tool] reader-pcsc.c:255:pcsc_transmit: unable to transmit
  [pkcs15-tool] apdu.c:394:do_single_transmit: unable to transmit APDU
  [pkcs15-tool] iso7816.c:127:iso7816_read_binary: APDU transmit failed: 
Transmit failed
  [pkcs15-tool] card.c:430:sc_read_binary: returning with: Transmit failed
  [pkcs15-tool] pkcs15.c:761:sc_pkcs15_bind: returning with: Unsupported card
  PKCS#15 initialization failed: Unsupported card
  ---cut here---

  If ReinerSCT cyberflex or Cryptoflex USB is used, smartcard behaves as
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opensc/+bug/282196/+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 1601997] Re: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs

2018-05-27 Thread Simon Iremonger

FWIW: e2fsprogs PPA created and discussion of backports/updates should happen
on this linked-bug:-
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874 -- if you are
interested in xenial/older e2fsprogs compatibility please subscribe to that bug
#1365874 .

I also spotted e2fsprogs 1.44.2 has fix against crashing from malicious-
filesystems, remains to be seen if this and further future fixes may
ultimately warrant update to bionic's 1.44.1 .

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

Title:
Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is
incompatible with older (LTS) e2fsprogs

Status in e2fsprogs package in Ubuntu:
Won't Fix

Bug description:
Ubuntu 16.10 installer sets metadata_csum option on ext4 partition
which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04
LTS, 16.04 LTS).

Steps to reproduce:
1. Download Ubuntu 16.10 installation media.
2. Install Ubuntu.
3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro.

Expected results:
User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10.

Actual results:
User can not check and fix errors on ext4 filesystem because of lack of
'metadata_csum' option in previous LTS Ubuntu versions.
The only one working solution was to scan from 16.10 live install media.

Note:
it is known, that Dan Watkins disabled metadata_csum when creating ext4
filesystems ( see
http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305
). It is good solution.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: e2fsprogs 1.43.1-1
ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
Uname: Linux 4.4.0-30-generic i686
ApportVersion: 2.20.2-0ubuntu1
Architecture: i386
CurrentDesktop: Unity
Date: Mon Jul 11 23:42:49 2016
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

2018-05-27 Thread Simon Iremonger

Here is the PPA for all architectures, please test :-
https://launchpad.net/~ubuntu-iremonger/+archive/ubuntu/e2fsprogs-xenial

That is currently a backport of the version in bionic release itself,
but maintains the xenial mke2fs.conf defaults [creating filesystems
without 64bit,metadata_csum] for compatibility.

I notice e2fsprogs in cosmic [1.44.2] introduces an anti-crash-fix [filesystems 
designed to crash e2fsck!].  Exactly what versions should then be considered 
for xenial-backports and xenial-updates, and if any updates to bionic should 
also be considered, is another matter!.
Debian already have 1.44.2 backported to stretch (their current LTS release), 
for example.

"-updates" versions might not, for example, want to update the comerr
development headers and other potential compatibility regression areas,
who knows?.

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

2018-05-27 Thread Marc Peña

That's great Simon! I will test it once it's ready then.

Regarding (b): wouldn't it be easier to try to get the package in 
xenial-backports then?
That repo it's activated by default, but as I can read here: 
https://help.ubuntu.com/community/UbuntuBackports

On releases before (but not including) Ubuntu 11.04 (Natty Narwhal), apt
defaulted to always installing packages from Backports. On later
releases, apt only installs packages from Backports when they are
explicitly requested.

So the risk would be much lower.

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1773656] Re: package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2018-05-27 Thread Apport retracing service

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

Title:
  package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in util-linux package in Ubuntu:
  New

Bug description:
  package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun May 27 16:17:17 2018
  DuplicateSignature:
   package:util-linux:2.30.1-0ubuntu4.2
   Setting up util-linux (2.30.1-0ubuntu4.2) ...
   /var/lib/dpkg/info/util-linux.postinst: 17: 
/var/lib/dpkg/info/util-linux.postinst: update-rc.d: not found
   dpkg: error processing package util-linux (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: util-linux
  Title: package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: Upgraded to artful on 2018-03-05 (83 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1773656/+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 1773656] [NEW] package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2018-05-27 Thread Sklyarov Yurii

Public bug reported:

package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
subprocess installed post-installation script returned error exit status
127

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: util-linux 2.30.1-0ubuntu4.2
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
Date: Sun May 27 16:17:17 2018
DuplicateSignature:
 package:util-linux:2.30.1-0ubuntu4.2
 Setting up util-linux (2.30.1-0ubuntu4.2) ...
 /var/lib/dpkg/info/util-linux.postinst: 17: 
/var/lib/dpkg/info/util-linux.postinst: update-rc.d: not found
 dpkg: error processing package util-linux (--configure):
  subprocess installed post-installation script returned error exit status 127
ErrorMessage: subprocess installed post-installation script returned error exit 
status 127
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: util-linux
Title: package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
UpgradeStatus: Upgraded to artful on 2018-03-05 (83 days ago)

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


** Tags: amd64 apport-package artful

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

Title:
  package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in util-linux package in Ubuntu:
  New

Bug description:
  package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: util-linux 2.30.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun May 27 16:17:17 2018
  DuplicateSignature:
   package:util-linux:2.30.1-0ubuntu4.2
   Setting up util-linux (2.30.1-0ubuntu4.2) ...
   /var/lib/dpkg/info/util-linux.postinst: 17: 
/var/lib/dpkg/info/util-linux.postinst: update-rc.d: not found
   dpkg: error processing package util-linux (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: util-linux
  Title: package util-linux 2.30.1-0ubuntu4.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127
  UpgradeStatus: Upgraded to artful on 2018-03-05 (83 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1773656/+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 1766542] Re: Installation blocks when the machine is behind a proxy server

2018-05-27 Thread Francis Ginther

** Tags added: id-5af9ea356db8cb2d4eb3d4e7

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

Title:
  Installation blocks when the machine is behind a proxy server

Status in OEM Priority Project:
  Confirmed
Status in apt package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Incomplete
Status in apt source package in Bionic:
  New
Status in ubiquity source package in Bionic:
  New

Bug description:
  When the machine is behind a proxy server, the installation will block
  for a while (several minutes) to retrieve the package lists. The
  timeouts are too long and makes user feels the machine may have some
  problems.

  The symptom is similar with bug #14599, but it seems the apt-setup
  module was rewritten.

  Another method to trigger this issue is to make the machine cannot
  access to the Internet, for instance: a wrong gateway.

  Image: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766542/+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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-05-27 Thread Francis Ginther

** Tags added: id-5afdc48d9d556db07dc88b67

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Confirmed

Bug description:
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  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
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  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: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1768905/+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 1771345] Re: lscpu possible crash in min/max frequency

2018-05-27 Thread Francis Ginther

** Tags added: id-5a2eb607f4872474ec5e0a80

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

Title:
  lscpu possible crash in min/max frequency

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  lscpu prior to 2.32 does not correctly check for NULL members in min/max CPU 
frequency arrays and can call atof() on them, leading to crashes. It seems 
that's what caused the verification to fail for bug 1732865. The following 
fixes have been committed upstream:

  from 2.30: https://github.com/karelzak/util-
  linux/commit/0145d84a381fc2fcd7d37e0dbf3d9dff69609ecd

  from 2.32: https://github.com/karelzak/util-
  linux/commit/95f09bc63c564c50ec2c393352801cc056faaea2

  I plan to backport them to xenial (both patches); and artful, bionic
  (second patch, they are > 2.30).

  [Regression potential]
  The worst possible regression is that lscpu would fail to correctly report 
min/max frequencies, but it seems unlikely, as we're only adding checks against 
null pointers / move an atof into a loop.

  [Test case]
  Extract attached segvtest.tar.gz and run lscpu -s segvtest and check that it 
does not crash (this removes min mhz file for cpu #0 for testing).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1771345/+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 1773650] Re: systemd-journald crashed with SIGABRT in __pthread_join()

2018-05-27 Thread Apport retracing service

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

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 #1747829, 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.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145168/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145171/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145179/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145181/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145182/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145183/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1773650/+attachment/5145185/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1747829

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in __pthread_join()

Status in systemd package in Ubuntu:
  New

Bug description:
  I think I ran OOM

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.4
  ProcVersionSignature: Ubuntu 4.13.0-44.49-generic 4.13.16
  Uname: Linux 4.13.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CrashCounter: 1
  Date: Sat May 26 18:04:08 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-10-13 (225 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  MachineType: LENOVO 20HN0016GE
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-44-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __pthread_join (threadid=140682808243968, thread_return=0x0) at 
pthread_join.c:90
   ?? () from /lib/systemd/libsystemd-shared-234.so
   ?? () from /lib/systemd/libsystemd-shared-234.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-234.so
   ?? () from /lib/systemd/libsystemd-shared-234.so
  Title: systemd-journald crashed with SIGABRT in __pthread_join()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/23/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET46W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HN0016GE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET46W(1.24):bd10/23/2017:svnLENOVO:pn20HN0016GE:pvrThinkPadX270:rvnLENOVO:rn20HN0016GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HN0016GE
  dmi.product.version: ThinkPad X270
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773650/+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 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

It should be installed somehow.

When I installed ubuntu I was running the discrete graphics card so
nvidia proprietary drivers installed automatically. Then I wanted to
switch to nouveau and that package is missing.

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

Status in gnome-desktop package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1773651] [NEW] xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

Public bug reported:

When I switch from nvidia to nouveau from software-properties-gtk and
reboot, with the nouveau driver already running, I experience graphic
glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
missing.

See bugs here:

https://bugs.freedesktop.org/show_bug.cgi?id=106657
https://gitlab.gnome.org/GNOME/nautilus/issues/426

** Affects: gnome-desktop (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-desktop (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- xserver-xorg-video-nouveau is required to display properly gnome graphics 
with nouveau driver
+ xserver-xorg-video-nouveau is required with nouveau driver to display 
properly gnome apps

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

Status in gnome-desktop package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  When I switch from nvidia to nouveau from software-properties-gtk and
  reboot, with the nouveau driver already running, I experience graphic
  glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
  missing.

  See bugs here:

  https://bugs.freedesktop.org/show_bug.cgi?id=106657
  https://gitlab.gnome.org/GNOME/nautilus/issues/426

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1773651/+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 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming

2018-05-27 Thread Simon Iremonger

Marc,  Briefly just to let you know I'm working on a PPA for bionic e2fsprogs 
backport to xenial, will update when thats' ready.  Turns out that:-
(a) Ubuntu devs are rather tied-up fixing bionic18.04 bugs, and
(b) to do a good SRU would need much regression-testing and somebody to push it 
forwards.

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

Title:
  Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata
  checksumming

Status in e2fsprogs package in Ubuntu:
  Triaged

Bug description:
  In the Trusty release notes "Metadata checksumming" is listed as one
  of the tech highlights of kernel 3.13.

  https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS

  However, the userland tools do not support this kernel feature. To the
  best of my knowledge this will be supported in 1.43, and won't be
  backported to 1.42.

  IMHO this is very misleading. It's like a car salesperson sold you a
  sports car with an V8 engine. After you drove it home, you opened the
  hood and realized only 6 cylinders are working because 2 of the spark
  plugs were not included, and you have to buy aftermarket ones.

  BTW, I've been following the development of e2fsprogs for over a
  year. 1.43  release has been in limbo for God knows how long :(
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+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 1768633] Re: desktop or window fallen over after standby

Stefan Helmert, I do not see any visual imperfections in the screenshot
you most recently attached. Could you please advise?

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

Title:
  desktop or window fallen over after standby

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  after wake up from standby the screen was flickering and a window was
  fallen over

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  2 21:04:50 2018
  DistUpgraded: 2017-08-25 15:00:28,865 DEBUG /openCache(), new cache size 89089
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  MachineType: LENOVO 2441CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=d69762cf-74da-49ec-97d9-c040c9e21557 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (250 days ago)
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2441CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA9WW(2.69):bd09/26/2017:svnLENOVO:pn2441CTO:pvrThinkPadW530:rvnLENOVO:rn2441CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2441CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  2 20:59:06 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -2
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4589 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+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 1773484] Re: Login screen not moved to used monitor

Manfred Steiner, with only the VGA monitor connected, and the output
sent to both the laptop internal monitor, and external monitor, could
you please provide a screenshot of the Settings > Devices > Display GUI
menu?

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1762122] Re: drm_kms_helper.edid_firmware not working anymore on Ubuntu 18.04

2018-05-27 Thread Launchpad Bug Tracker

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

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

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

Title:
  drm_kms_helper.edid_firmware not working anymore on Ubuntu 18.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I installed today Ubuntu 18.04. I have a secondary monitor (Acer
  AL1914), which does not provide a EDID, so I created one and usually
  loaded directly from the kernel at startup.

  The EDID is located here:
  /lib/firmware/edid/al1914.bin

  The kernel command line is this:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash 
drm_kms_helper.edid_firmware=VGA-1:edid/al1914.bin"

  On Ubuntu 16.04, this worked perfectly. Now, the additional mode from
  the edid is not present among the resolutions available (I have to
  create a new one and add it with cvt and xrandr once the system is
  loaded).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  8 08:27:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d8]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-04-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=088e46ca-c64d-43c6-8c68-0f92cb2917b6 ro quiet splash 
drm_kms_helper.edid_firmware=VGA-1:edid/al1914.bin vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350V5C-S08IT
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S08IT:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 350V5C/351V5C/3540VC/3440VC
  dmi.product.version: P09ABE.012.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS 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-1ubuntu3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762122/+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 1773484] Re: Login screen not moved to used monitor

The issue of the Bug description is the most important, because it will affect 
most of users. This issue has no link to the i-tec adapter issue, it is also 
visible when the adapter is not connected.
I remember that the situation now (on Ubuntu 18.04) is compareable with the 
situation on Ubuntu 12.04 (maybe also 14.04). In 16.04 this issue was solved in 
a perfect way (system menues and login dialog follows the mouse pointer to the 
desired display).

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 16.04 the login screen and system menu bar, ... is moved to
  the monitor where the mouse pointer is located. On Ubuntu 18.04 login
  dialog and system menues are restricted to the main monitor.

  So if you have a notebook with defect lcd display you can work with it
  using Ubuntu 16.04 and an external monitor, but you cannot work with
  Ubuntu 18.04, because you are not able to login!

  This problem was also asked on:
  
https://askubuntu.com/questions/1031808/problem-with-login-screen-with-dual-monitor-on-ubuntu-18-04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 07:04:47 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-04-30 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20AQ007TGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=28805c99-e27d-49f9-a2e5-17f85980a6d6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET77WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ007TGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQ007TGE:pvrThinkPadT440s:rvnLENOVO:rn20AQ007TGE:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20AQ007TGE
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773484/+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 1768633] Re: desktop or window fallen over after standby

2018-05-27 Thread Stefan Helmert

tried now nvidia 396.24, got simmilar problems

I think it does not depend on nvidia drivers. The internal display ist
connected to intel graphics. Switching nvidia gpu off does not change
anything.

** Attachment added: "screenshot graphic problems"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+attachment/5145128/+files/Bildschirmfoto%20vom%202018-05-27%2012-06-37.png

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

Title:
  desktop or window fallen over after standby

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  after wake up from standby the screen was flickering and a window was
  fallen over

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  2 21:04:50 2018
  DistUpgraded: 2017-08-25 15:00:28,865 DEBUG /openCache(), new cache size 89089
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  MachineType: LENOVO 2441CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=d69762cf-74da-49ec-97d9-c040c9e21557 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (250 days ago)
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA9WW (2.69 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2441CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ETA9WW(2.69):bd09/26/2017:svnLENOVO:pn2441CTO:pvrThinkPadW530:rvnLENOVO:rn2441CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2441CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  2 20:59:06 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -2
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4589 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+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 1773637] [NEW] Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-05-27 Thread Yoshee

Public bug reported:

I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

Section "Device"
Identifier "nvidia"
#Driver "nvidia"
BusID "PCI:10@0:0:0"
Option "ConstrainCursor" "off"
EndSection

As the installtion routine backuped my xorg.conf I could verify that the
line hadn't been commented out before upgrading. Removing the "#" solved
the problem.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
.proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0a:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 27 11:43:16 2018
DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-20-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d]
   Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d]
InstallationDate: Installed on 2017-11-02 (205 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago)
dmi.bios.date: 11/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 229D
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.15
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null
dmi.product.name: HP ENVY 17 Notebook PC
dmi.product.version: 097312405F1620180
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.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 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/1773637

Title:
  Distribution upgrade to 18.04: used nvidia display driver is commented
  out

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade.
  After the installation had finished, Xorg wouldn't start. I later found out 
that this was because the installation routine had commented out the nvidia 
display driver I used in the xorg.conf:

  Section "Device"
  Identifier "nvidia"
  #Driver "nvidia"
  BusID "PCI:10@0:0:0"
  Option "ConstrainCursor" "off"
  EndSection

  As the installtion routine backuped my xorg.conf I could verify that
  the line hadn't been commented out before upgrading. Removing the "#"
  solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64

[Touch-packages] [Bug 1773549] Re: Pulse audio does not remember default sink

2018-05-27 Thread Alfred Krohmer

Oh, thanks for the hint. I didn't know that this module was loaded. But
then the behavior of the module-switch-on-connect module is somehow
inconsistent. The USB headset is always attached to the computer
(wireless USB receiver) so there should be no reason that pulse should
select that one over the onboard sink (considering that I had selected
the onboard sink as default before). Also network sinks should not
really be preferred via that module (that just doesn't seem right to
me).

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

Title:
Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
Triaged

Bug description:
It seems like pulseaudio is picking the wrong audio sink as a default
in different scenarios.

On my computer I have the default onboard Intel HDA audio as well as a
USB headset. On the network, there is one pulse instance advertising
itself.

I always set the onboard audio as the default audio sink. However,
after every reboot or resume or `pulseaudio -k`, the wrong sink is
picked (and the one I set previously is *not* picked).

When I enable discovery of remote pulse instances, sometimes the one
on my network is picked as default, but sometimes my headset is picked
instead of the onboard sink. Then again, if I disable discovery
sometimes the onboard sink gets picked as default. There seems to be
no clear pattern on when it selects what.

I have even entered the following in /etc/pulse/default.pa:

set-default-sink alsa_output.pci-_00_1b.0.analog-stereo
set-default-source
alsa_input.usb-SteelSeries_SteelSeries_Arctis_7-00.analog-mono

But this doesn't have any effect at all.

I also noticed that *sometimes*, pulse updates the file at
`~/.config/pulse/f8a78acf499a402aa80f90af9ef5c15c-default-sink` to
point to the correct audio sink that I selected in `pavucontrol`, but
not always. Even if I write to that file manually to select a default
sink, the file gets overwritten by pulse on the next start with the
default sink that it chose.

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
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: devkid 3487 F pulseaudio
/dev/snd/controlC2: devkid 3487 F pulseaudio
/dev/snd/pcmC0D0p: devkid 3487 F...m pulseaudio
/dev/snd/controlC0: devkid 3487 F pulseaudio
CurrentDesktop: MATE
Date: Sat May 26 17:07:55 2018
ExecutablePath: /usr/bin/pulseaudio
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77A-G43 (MS-7758)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7758
dmi.product.version: 1.0
dmi.sys.vendor: MSI
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2018-05-26T17:01:12.271701

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773549/+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 1773516] Re: [Lenovo Yoga 300-11IBY] Right click not working

2018-05-27 Thread Timo Aaltonen

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

** This bug has been marked a duplicate of bug 1759300
   Gnome Shell: Touchpad right click (bottom right) area does not work

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

Title:
  [Lenovo Yoga 300-11IBY] Right click not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The right click is not working on Lenovo Yoga touch pad after upgrade
  to 18.04, worked minutes before on 17.10.

  I think it works on the Think Pad out-of-the-box (after upgrade from
  17.10), if that helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat May 26 10:34:57 2018
  DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3908]
  InstallationDate: Installed on 2018-01-18 (128 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: LENOVO 80M0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C0CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Mini
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J33995WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 300-11IBY
  dmi.modalias: 
dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80M0
  dmi.product.version: Lenovo YOGA 300-11IBY
  dmi.sys.vendor: LENOVO
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773516/+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 1773575] Re: dual vga

mustafa, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/comments/5
regarding this being resolved. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

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

Title:
  dual vga

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i have a laptop dell which has two vga one from intel and the other
  one is amd. i tried to update the drivers in one way or another every
  thing stoped and i can not use the gui anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat May 26 22:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2018-01-10 (136 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 5521
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
  dmi.bios.date: 07/31/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0C46Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 5521
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue May 22 09:07:33 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 927 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/+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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

** Changed in: bluez (Ubuntu)
   Status: Confirmed => In Progress

-- 
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:
  In Progress
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

Re: [Touch-packages] [Bug 1773575] Re: dual vga

2018-05-27 Thread mustafa

yes it solved my problem thanks alot i could not find such a solution
online. you saved my day

On Sun, May 27, 2018 at 8:34 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> mustafa:
>
> 1) Regarding crash files, you would not want to attach them, as they may
> contain sensitive information you don't want to reveal publicly.
>
> Instead, one may report them in a privacy respectful way via a terminal:
> ubuntu-bug /var/crash/FILENAME.crash
>
> where FILENAME is the name of the crash file.
>
> 2) It is advised to immediately back up your data (config files, list of
> what apps you have installed, etc.), so that in the event of a disaster
> (hardware failure, OS stops working entirely, etc.) you may perform a
> clean install and bring the OS back to the desired state. Stating "i do
> not want to lose my server configuration and reinstall Ubuntu and all
> the configuration and apps that i used" doesn't mean you won't have to
> do it. This is a matter of how prepared are you if you must.
>
> 3) Post the results of the following terminal command:
> history
>
> 4) To confirm a WORKAROUND, if you install the package gnome-session-
> flashback and login to GNOME (Metacity), does this allow you to use the
> GUI again?
>
> ** Attachment removed: "_usr_lib_x86_64-linux-gnu_
> unity_compiz-config-profile-setter.1000_copy.crash"
>https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/
> 1773575/+attachment/5145036/+files/_usr_lib_x86_64-linux-
> gnu_unity_compiz-config-profile-setter.1000_copy.crash
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773575
>
> Title:
>   dual vga
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   i have a laptop dell which has two vga one from intel and the other
>   one is amd. i tried to update the drivers in one way or another every
>   thing stoped and i can not use the gui anymore
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
>   Uname: Linux 4.13.0-43-generic x86_64
>   .tmp.unity_support_test.1:
>
>   ApportVersion: 2.20.1-0ubuntu2.17
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Sat May 26 22:00:13 2018
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
>Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M]
> [1002:6601] (rev ff) (prog-if ff)
>   InstallationDate: Installed on 2018-01-10 (136 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   MachineType: Dell Inc. Inspiron 5521
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
>   dmi.bios.date: 07/31/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A14
>   dmi.board.name: 0C46Y8
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A14
>   dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:
> pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
>   dmi.product.family: 103C_5335KV
>   dmi.product.name: Inspiron 5521
>   dmi.product.version: A14
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.83-1~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>   xserver.bootTime: Tue May 22 09:07:33 2018
>   xserver.configfile: default
>   xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id 927
>vendor LGD
>   xserver.version:

[Touch-packages] [Bug 1773549] Re: Pulse audio does not remember default sink

Actually this bug could still be kept open. We have a design proposal
for fixing it already:

 https://trello.com/c/aI3BX3ax

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: pulseaudio (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  It seems like pulseaudio is picking the wrong audio sink as a default
  in different scenarios.

  On my computer I have the default onboard Intel HDA audio as well as a
  USB headset. On the network, there is one pulse instance advertising
  itself.

  I always set the onboard audio as the default audio sink. However,
  after every reboot or resume or `pulseaudio -k`, the wrong sink is
  picked (and the one I set previously is *not* picked).

  When I enable discovery of remote pulse instances, sometimes the one
  on my network is picked as default, but sometimes my headset is picked
  instead of the onboard sink. Then again, if I disable discovery
  sometimes the onboard sink gets picked as default. There seems to be
  no clear pattern on when it selects what.

  I have even entered the following in /etc/pulse/default.pa:

  set-default-sink alsa_output.pci-_00_1b.0.analog-stereo
  set-default-source 
alsa_input.usb-SteelSeries_SteelSeries_Arctis_7-00.analog-mono

  But this doesn't have any effect at all.

  I also noticed that *sometimes*, pulse updates the file at
  `~/.config/pulse/f8a78acf499a402aa80f90af9ef5c15c-default-sink` to
  point to the correct audio sink that I selected in `pavucontrol`, but
  not always. Even if I write to that file manually to select a default
  sink, the file gets overwritten by pulse on the next start with the
  default sink that it chose.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  devkid 3487 F pulseaudio
   /dev/snd/controlC2:  devkid 3487 F pulseaudio
   /dev/snd/pcmC0D0p:   devkid 3487 F...m pulseaudio
   /dev/snd/controlC0:  devkid 3487 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat May 26 17:07:55 2018
  ExecutablePath: /usr/bin/pulseaudio
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-05-26T17:01:12.271701

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773549/+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 1773549] Re: Pulse audio does not remember default sink

Ubuntu is intentionally designed to automatically prefer the USB (or
Bluetooth) audio over the internal audio.

It sounds like you want to disable that feature, so just remove/comment
these lines from /etc/pulse/default.pa:

  ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794)
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif


** Changed in: pulseaudio (Ubuntu)
   Status: New => Invalid

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  It seems like pulseaudio is picking the wrong audio sink as a default
  in different scenarios.

  On my computer I have the default onboard Intel HDA audio as well as a
  USB headset. On the network, there is one pulse instance advertising
  itself.

  I always set the onboard audio as the default audio sink. However,
  after every reboot or resume or `pulseaudio -k`, the wrong sink is
  picked (and the one I set previously is *not* picked).

  When I enable discovery of remote pulse instances, sometimes the one
  on my network is picked as default, but sometimes my headset is picked
  instead of the onboard sink. Then again, if I disable discovery
  sometimes the onboard sink gets picked as default. There seems to be
  no clear pattern on when it selects what.

  I have even entered the following in /etc/pulse/default.pa:

  set-default-sink alsa_output.pci-_00_1b.0.analog-stereo
  set-default-source 
alsa_input.usb-SteelSeries_SteelSeries_Arctis_7-00.analog-mono

  But this doesn't have any effect at all.

  I also noticed that *sometimes*, pulse updates the file at
  `~/.config/pulse/f8a78acf499a402aa80f90af9ef5c15c-default-sink` to
  point to the correct audio sink that I selected in `pavucontrol`, but
  not always. Even if I write to that file manually to select a default
  sink, the file gets overwritten by pulse on the next start with the
  default sink that it chose.

  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
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  devkid 3487 F pulseaudio
   /dev/snd/controlC2:  devkid 3487 F pulseaudio
   /dev/snd/pcmC0D0p:   devkid 3487 F...m pulseaudio
   /dev/snd/controlC0:  devkid 3487 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat May 26 17:07:55 2018
  ExecutablePath: /usr/bin/pulseaudio
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7758
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-05-26T17:01:12.271701

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1773549/+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 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

2018-05-27 Thread Bug Watch Updater

** Changed in: systemd (Debian)
   Status: New => Fix Released

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

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed
Status in systemd package in Debian:
  Fix Released

Bug description:
  [Impact]
  systemd used to pre-depend on the libraries used by systemctl or something, 
but now systemctl uses libsystemd-shared, and there are no pre-depends for 
that, meaning that systemctl fails in maintainer scripts of other packages.

  [Test case]
  Grab the apt-clone file from comment #20 in bug 1766890, and upgrade it to 
bionic with apt dist-upgrade -o APT::Immediate-Configure=0. Make sure to not 
see error about missing libraries in systemctl.

  [Regression potential]
  Installation ordering changes. Might make things harder for apt to solve.

  [Other info]
  Debian 897986

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771791/+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 1773575] Re: dual vga