[Touch-packages] [Bug 2061140] Re: dropbear-initramfs package fails to install on Ubuntu 24.04 beta server

[Johan Ehnberg]

Indeed, looks like this issue is related to initramfs-tools, be that
through an incompatibility introduced in either.

I tested with the package in Debian Sid dropbear-initramfs (2024.84-1)
and got the same error. Meanwhile, on a Debian Sid install, it works.

Based on the above, I added initramfs-tools as affected package.

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

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

Title:
  dropbear-initramfs package fails to install on Ubuntu 24.04 beta
  server

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dropbear-initramfs seems to fail on not figuring out what the root
  device is. This applies both to  autoinstall and manual install and is
  observed on today's beta (ubuntu-24.04-beta-live-server-amd64.iso on
  2024-04-12)

  ubuntu@ubuntu-server:~$ sudo apt install dropbear-initramfs 
  [sudo] password for ubuntu: 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  dropbear-initramfs is already the newest version (2022.83-4).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Setting up initramfs-tools (0.142ubuntu24) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.142ubuntu24) ...
  update-initramfs: Generating /boot/initrd.img-6.8.0-22-generic
  dropbear: WARNING: Couldn't find ~root, SSH login to initramfs won't work!
  E: /usr/share/initramfs-tools/hooks/dropbear failed with return 1.
  update-initramfs: failed for /boot/initrd.img-6.8.0-22-generic with 1.
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned 
  error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  needrestart is being skipped since dpkg has failed
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/2061140/+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 2018013] [NEW] package ca-certificates 20230311 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 3

[Johan F]

Public bug reported:

do-release upgrade
from 22.10-> 23.04

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: ca-certificates 20230311
ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Apr 28 17:38:06 2023
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 3
InstallationDate: Installed on 2022-07-28 (274 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: ca-certificates
Title: package ca-certificates 20230311 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 3
UpgradeStatus: Upgraded to lunar on 2023-04-28 (0 days ago)
modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package lunar

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

Title:
  package ca-certificates 20230311 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 3

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  do-release upgrade
  from 22.10-> 23.04

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: ca-certificates 20230311
  ProcVersionSignature: Ubuntu 5.19.0-41.42-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr 28 17:38:06 2023
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 3
  InstallationDate: Installed on 2022-07-28 (274 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: ca-certificates
  Title: package ca-certificates 20230311 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 3
  UpgradeStatus: Upgraded to lunar on 2023-04-28 (0 days ago)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2018013/+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 1973306] Re: packages freezes on authentification with Wayland

[Johan Van Hoorde]

Dear Mr. Bacher,

I have done what you asked me to do. See attached file.

When unlocking the user account panel, everything funtions as it should, 
without any issue. As stated before the problem only occurs within 
Wayland sessions and never within an Xorg one.

I have added the same information in the bug report itself.

I wish you and the team good luck in resolving the bug. It might not be 
a crucial one, but it still remains quite disturbing.

Best regards,

Johan Van Hoorde
jo...@van-hoorde.nl
Tel. +31 647 601 667

Il 11-07-2022 09:28, Sebastien Bacher ha scritto:
> Thank you for your bug report. Could you do
>
> $ journalctl -f
>
> on a cmdline, trigger the bug and copy the log of what is printed to the
> report?
>
> And could you try if you get a similar issue if you trigger the prompt
> by going to settings->user accounts and unlock the panel?
>
> ** Changed in: software-properties (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: software-properties (Ubuntu)
> Status: New => Incomplete
>

** Attachment added: "Bug_report_journalctl_1607_22.pdf"
   
https://bugs.launchpad.net/bugs/1973306/+attachment/5603471/+files/Bug_report_journalctl_1607_22.pdf

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64
  Kernel: 5.15.0-30-generic
  Uptime: 13 mins
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16
  Resolution: 1920x1080
  DE: GNOME 42.0
  WM: Mutter
  WM Theme: Adwaita
  Theme: Adwaita [GTK2/3]
  Icons: Numix [GTK2/3]
  Terminal: gnome-terminal
  CPU: Intel i7-10510U (8) @ 4.900GHz
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+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 1973306] Re: packages freezes on authentification with Wayland

[Johan Van Hoorde]

** Attachment added: "Bug_report_journalctl_1607_22.pdf"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+attachment/5603470/+files/Bug_report_journalctl_1607_22.pdf

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64
  Kernel: 5.15.0-30-generic
  Uptime: 13 mins
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16
  Resolution: 1920x1080
  DE: GNOME 42.0
  WM: Mutter
  WM Theme: Adwaita
  Theme: Adwaita [GTK2/3]
  Icons: Numix [GTK2/3]
  Terminal: gnome-terminal
  CPU: Intel i7-10510U (8) @ 4.900GHz
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+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 1973306] Re: packages freezes on authentification with Wayland

[Johan Van Hoorde]

I have done what was asked. This is the reported journal line:

jul 16 12:00:28 johan-NL40-50CU polkitd(authority=local)[821]: Operator
of unix-session:2 FAILED to authenticate to gain authorization for
action com.ubuntu.softwareproperties.applychanges for system-bus-
name::1.135 [/usr/bin/python3 /usr/bin/software-properties-gtk] (owned
by unix-user:johan)

jul 16 12:00:28 johan-NL40-50CU software-properties-gtk.desktop[5300]:
ERROR:root:Authentication canceled, changes have not been saved

I have also unlocked the user account panel. This worked fine without
any issue. As stated earlier the authentication problem occurs only
within a Wayland session and never within an Xorg one.

I also include the report line in a separate attachment.

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64
  Kernel: 5.15.0-30-generic
  Uptime: 13 mins
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16
  Resolution: 1920x1080
  DE: GNOME 42.0
  WM: Mutter
  WM Theme: Adwaita
  Theme: Adwaita [GTK2/3]
  Icons: Numix [GTK2/3]
  Terminal: gnome-terminal
  CPU: Intel i7-10510U (8) @ 4.900GHz
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+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 1973306] Re: packages freezes on authentification with Wayland

[Johan Van Hoorde]

** Description changed:

  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu LTS
  20.04 towards the LTS 22.04 with Wayland as default.
  
  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.
  
  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if the
  user switches back to an Xorg session.
  
  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.
  
  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.
  
  My system:
  
- OS: Ubuntu 22.04 LTS x86_64 
- Kernel: 5.15.0-30-generic 
- Uptime: 13 mins 
+ OS: Ubuntu 22.04 LTS x86_64
+ Kernel: 5.15.0-30-generic
+ Uptime: 13 mins
  Packages: 1940 (dpkg), 17 (flatpak),
- Shell: bash 5.1.16 
- Resolution: 1920x1080 
- DE: GNOME 42.0 
- WM: Mutter 
- WM Theme: Adwaita 
- Theme: Adwaita [GTK2/3] 
- Icons: Numix [GTK2/3] 
- Terminal: gnome-terminal 
- CPU: Intel i7-10510U (8) @ 4.900GHz 
+ Shell: bash 5.1.16
+ Resolution: 1920x1080
+ DE: GNOME 42.0
+ WM: Mutter
+ WM Theme: Adwaita
+ Theme: Adwaita [GTK2/3]
+ Icons: Numix [GTK2/3]
+ Terminal: gnome-terminal
+ CPU: Intel i7-10510U (8) @ 4.900GHz
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  New

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64
  Kernel: 5.15.0-30-generic
  Uptime: 13 mins
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16
  Resolution: 1920x1080
  DE: GNOME 42.0
  WM: Mutter
  WM Theme: Adwaita
  Theme: Adwaita [GTK2/3]
  Icons: Numix [GTK2/3]
  Terminal: gnome-terminal
  CPU: Intel i7-10510U (8) @ 4.900GHz
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+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 1973306] [NEW] packages freezes on authentification with Wayland

[Johan Van Hoorde]

Public bug reported:

I want to report an issue which might well have been reported already,
although i could not find it. A few weeks ago I switched from Ubuntu LTS
20.04 towards the LTS 22.04 with Wayland as default.

I discovered that there is a sort of incompatibility between the
software-properties-package and the Wayland protocol, which occurs
systematically and never occurs when switching back to Xorg.

When one tries to add or change a rule in ‘other software’ the
application always freezes when the user is asked to authenticate. As
soon a one cancels the authentification procedure it unfreezes almost
immediately, but freezes again when the user retries to complete the
adding or alteration procedure. As said, this error never occurs if the
user switches back to an Xorg session.

See screenshot: the window with the communication 'software & updates
does not respond' and with the choice to close or to wait is hidden
behind the authentification window.

I am not really sure whether this bug has to be reported as a security
issue, but certainly the software-properties-package is of utmost
importance for a stable and secure OS.

My system:

OS: Ubuntu 22.04 LTS x86_64 
Kernel: 5.15.0-30-generic 
Uptime: 13 mins 
Packages: 1940 (dpkg), 17 (flatpak),
Shell: bash 5.1.16 
Resolution: 1920x1080 
DE: GNOME 42.0 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Numix [GTK2/3] 
Terminal: gnome-terminal 
CPU: Intel i7-10510U (8) @ 4.900GHz 
GPU: Intel CometLake-U GT2 [UHD Grap
Memory: 2992MiB / 64007MiB

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

** Attachment added: "Software_freeze1.png"
   
https://bugs.launchpad.net/bugs/1973306/+attachment/5589516/+files/Software_freeze1.png

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  New

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64 
  Kernel: 5.15.0-30-generic 
  Uptime: 13 mins 
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16 
  Resolution: 1920x1080 
  DE: GNOME 42.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Adwaita [GTK2/3] 
  Icons: Numix [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-10510U (8) @ 4.900GHz 
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1973306/+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 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

[Johan Ehnberg]

I can confirm the workaround by boxeus works on Ubuntu 20.04 LTS. To
improve on that, the lines can be added to the /etc/dropbear-
initramfs/config config file instead to avoid upgrade issues. It is
loaded towards the end of /usr/share/initramfs-tools/scripts/init-
bottom/dropbear anyway.

Automation two-liner:
echo -e "rm /run/net-*.conf\nrm /run/netplan/*.yaml" >> 
/etc/dropbear-initramfs/config
update-initramfs -u

After that, netplan actually works again.

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

Title:
  DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  On bionic, setting the network interface up (e.g. eno1) with DHCP now
  causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
  written. The former gets imported by netplan after boot and causes the
  DHCP lease from the initrd to be around forever, which I think goes
  against the intent of DROPBEAR_IFDOWN=*.

  I have brewed up a workaround script that lives in /etc/initramfs-
  tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:

  
    8< cut >8 
  #!/bin/sh

  PREREQ=""

  prereqs() {
  echo "$PREREQ"
  }

  case "$1" in
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /scripts/functions

  log_begin_msg "Deleting all network configuration that systemd could try to 
import"
  rm /run/net-*.conf
  rm /run/netplan/*.yaml
  log_end_msg
    8< cut >8 

  I think that dropbear-intiramfs's init-bottom script should do this in
  addition to downing the interfaces that it finds via the
  DROPBEAR_IFDOWN pattern. Do you agree?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+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 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

[Johan Ehnberg]

Which version of Mint (or which upstream Ubuntu it is based on?) I
wonder if there is a way to get those rows into the configs rather than
editing packaged files?

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

Title:
  DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  On bionic, setting the network interface up (e.g. eno1) with DHCP now
  causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
  written. The former gets imported by netplan after boot and causes the
  DHCP lease from the initrd to be around forever, which I think goes
  against the intent of DROPBEAR_IFDOWN=*.

  I have brewed up a workaround script that lives in /etc/initramfs-
  tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:

  
    8< cut >8 
  #!/bin/sh

  PREREQ=""

  prereqs() {
  echo "$PREREQ"
  }

  case "$1" in
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /scripts/functions

  log_begin_msg "Deleting all network configuration that systemd could try to 
import"
  rm /run/net-*.conf
  rm /run/netplan/*.yaml
  log_end_msg
    8< cut >8 

  I think that dropbear-intiramfs's init-bottom script should do this in
  addition to downing the interfaces that it finds via the
  DROPBEAR_IFDOWN pattern. Do you agree?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+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 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Johan Segerstedt]

I, too, confirm that the proposed updates solve the audio issue (for my
system info, please see the initial information in the bug report).

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Committed
Status in alsa-ucm-conf source package in Groovy:
  Fix Committed
Status in alsa-lib source package in Hirsute:
  Fix Committed
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.modalias: 

[Touch-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Johan Segerstedt]

The testing package of libasound2 built by @hui.wang has resolved the
issue for me as well. Thank you!

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1901922/+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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Johan Segerstedt]

I have reported the issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1030
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1901922/+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 1901922] [NEW] No sound output device on startup

[Johan Segerstedt]

Public bug reported:

After logging in, only a dummy device is available for audio playback
(resulting in no audible playback). When running "pactl load-module
module-detect" the sound card shows up, and playback works as expected.

If pulseaudio is restarted with "pulseaudio -k" the playback device
disappears again. Running the above command get things working again.

If I change the following section in /etc/pulse/default.pa from:

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev 
support)
load-module module-detect
.endif

To:

### Automatically load driver modules depending on the hardware available
#.ifexists module-udev-detect.so
#load-module module-udev-detect
#.else
### Use the static hardware detection module (for systems that lack udev 
support)
load-module module-detect
#.endif

Things start working as they should after running "pulseaudio -k".

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Oct 28 17:21:02 2020
InstallationDate: Installed on 2020-10-23 (4 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2020
dmi.bios.release: 1.9
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET40W(1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UDCTO1WW
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.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UDCTO1WW
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy

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

Title:
  No sound output device on startup

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  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.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: 

[Touch-packages] [Bug 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

[Johan Ehnberg]

It seems the workaround above does not work on Ubuntu 20.04.

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

Title:
  DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On bionic, setting the network interface up (e.g. eno1) with DHCP now
  causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
  written. The former gets imported by netplan after boot and causes the
  DHCP lease from the initrd to be around forever, which I think goes
  against the intent of DROPBEAR_IFDOWN=*.

  I have brewed up a workaround script that lives in /etc/initramfs-
  tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:

  
    8< cut >8 
  #!/bin/sh

  PREREQ=""

  prereqs() {
  echo "$PREREQ"
  }

  case "$1" in
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /scripts/functions

  log_begin_msg "Deleting all network configuration that systemd could try to 
import"
  rm /run/net-*.conf
  rm /run/netplan/*.yaml
  log_end_msg
    8< cut >8 

  I think that dropbear-intiramfs's init-bottom script should do this in
  addition to downing the interfaces that it finds via the
  DROPBEAR_IFDOWN pattern. Do you agree?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+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 1880740] [NEW] Provide a straightforward way to reset networking after initramfs

[Johan Ehnberg]

Public bug reported:

Since initramfs networking is rather limited, a simple flag to reset
networking afterwards (or not to generate netplan files) would be
valuable. The intended effect is to allow fully featured networking
tools to set up the network afterwards.

Use cases include the following, in comination with networking-enabled 
initramfs:
* Multiple IPs on a single interface
* Adding search domains
* Unlocking root over SSH on a different network than will be used afterwards
* Using DHCP for initramfs and static later

There are numerous workarounds floating around, as well as questions on
this behaviour. Netplan has made this even more difficult to get around,
since it does not provide an equivalent to 'service networking restart'.
As of Ubuntu 20.04, I have not even found any workaround that actually
works.

Related:
dropbear-initramfs IFDOWN not working LP #1813394
Alternative approach with netplan in initramfs LP #1880717
What is creating /run/netplan/eth0.yaml? askubuntu #1228433

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

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

Title:
  Provide a straightforward way to reset networking after initramfs

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Since initramfs networking is rather limited, a simple flag to reset
  networking afterwards (or not to generate netplan files) would be
  valuable. The intended effect is to allow fully featured networking
  tools to set up the network afterwards.

  Use cases include the following, in comination with networking-enabled 
initramfs:
  * Multiple IPs on a single interface
  * Adding search domains
  * Unlocking root over SSH on a different network than will be used afterwards
  * Using DHCP for initramfs and static later

  There are numerous workarounds floating around, as well as questions
  on this behaviour. Netplan has made this even more difficult to get
  around, since it does not provide an equivalent to 'service networking
  restart'. As of Ubuntu 20.04, I have not even found any workaround
  that actually works.

  Related:
  dropbear-initramfs IFDOWN not working LP #1813394
  Alternative approach with netplan in initramfs LP #1880717
  What is creating /run/netplan/eth0.yaml? askubuntu #1228433

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880740/+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 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

[Johan Ehnberg]

Digging even further back, it turns out that IFDOWN is in itself a
workaround for an equal issue dating back to ~2012. As such, the core of
the issue lies with how initramfs network setup overrides netplan.
Adding that package.

Given the very limited setup /etc/initramfs-tools/initramfs.conf allows
(including the DHCP default mentioned in the description), there is a
case to be made for allowing admins to rely on the full config rather
than initramfs for their network setup.

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

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

Title:
  DROPBEAR_IFDOWN=* takes interface down but leaves netplan config

Status in dropbear package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On bionic, setting the network interface up (e.g. eno1) with DHCP now
  causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
  written. The former gets imported by netplan after boot and causes the
  DHCP lease from the initrd to be around forever, which I think goes
  against the intent of DROPBEAR_IFDOWN=*.

  I have brewed up a workaround script that lives in /etc/initramfs-
  tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:

  
    8< cut >8 
  #!/bin/sh

  PREREQ=""

  prereqs() {
  echo "$PREREQ"
  }

  case "$1" in
  prereqs)
  prereqs
  exit 0
  ;;
  esac

  . /scripts/functions

  log_begin_msg "Deleting all network configuration that systemd could try to 
import"
  rm /run/net-*.conf
  rm /run/netplan/*.yaml
  log_end_msg
    8< cut >8 

  I think that dropbear-intiramfs's init-bottom script should do this in
  addition to downing the interfaces that it finds via the
  DROPBEAR_IFDOWN pattern. Do you agree?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dropbear/+bug/1813394/+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 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container

[Johan Ehnberg]

Workaround:
echo "Set disable_coredump false" | sudo tee -a /etc/sudo.conf

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

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

Title:
  "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when
  using sudo in 20.04 LXD container

Status in lxd package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  I fired up a LXD container using ubuntu-daily:f on my machine and
  every time I issue a comment inside the container using sudo, I get
  this error:

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.31-1ubuntu1
    Candidate: 1.8.31-1ubuntu1
    Version table:
   *** 1.8.31-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  This is not an issue on Bionic:
  bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.21p2-3ubuntu1.2
    Candidate: 1.8.21p2-3ubuntu1.2
    Version table:
   *** 1.8.21p2-3ubuntu1.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.21p2-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  From the redhat bug, the described workaround does clear these
  messages up:

  # set disable_coredump false

  Once I've done that, the error messages go away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1868456/+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 1868456] Re: "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container

[Johan Ehnberg]

Container management seems to be the source of the error, sudo just
suppresses it. So a potential fix is in LXD or related packages.

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

Title:
  "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when
  using sudo in 20.04 LXD container

Status in lxd package in Ubuntu:
  New
Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  I fired up a LXD container using ubuntu-daily:f on my machine and
  every time I issue a comment inside the container using sudo, I get
  this error:

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.31-1ubuntu1
    Candidate: 1.8.31-1ubuntu1
    Version table:
   *** 1.8.31-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  This is not an issue on Bionic:
  bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.21p2-3ubuntu1.2
    Candidate: 1.8.21p2-3ubuntu1.2
    Version table:
   *** 1.8.21p2-3ubuntu1.2 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.8.21p2-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  From the redhat bug, the described workaround does clear these
  messages up:

  # set disable_coredump false

  Once I've done that, the error messages go away.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1868456/+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 1659719] Re: ssh can't call a binary from a snap without the full path

[Johan Ehnberg]

This is fairly problematic when core functionality that is orchestrated
in the cloud moves from deb to snap. In our example, lxc (LXD command
line tool) was assumed to be in the path when building the
orchestration. Using the full path makes it less portable. It also makes
managing multiple releases a pain since some hosts may run the snap,
others installed by dpkg.

Is there any update on the intended direction?

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Committed
Status in openssh package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  ssh can't call a binary from a snap, it will only work using the full
  path.

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1868392] Re: Touchscreen not working in 5.3.0-42

[Johan]

Forgot to say, the bug report was done with kernel 5.3.0-40 with a
working touch screen.

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

Title:
  Touchscreen not working in 5.3.0-42

Status in xorg package in Ubuntu:
  New

Bug description:
  My Asus Zenbook touch screen works in 5.3.0-40, but stops working when
  I boot into the 5.3.0-42 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Mar 21 17:52:19 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-40-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13ff]
 Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:13ff]
  InstallationDate: Installed on 2020-02-11 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX481FL_UX481FL
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=af_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=c157ba74-8933-4447-9f11-e965279079be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX481FL.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX481FL
  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.:bvrUX481FL.206:bd08/06/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX481FL_UX481FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX481FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX481FL_UX481FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868392/+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 1868392] [NEW] Touchscreen not working in 5.3.0-42

[Johan]

Public bug reported:

My Asus Zenbook touch screen works in 5.3.0-40, but stops working when I
boot into the 5.3.0-42 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Mar 21 17:52:19 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-40-generic, x86_64: installed
 nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:13ff]
   Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:13ff]
InstallationDate: Installed on 2020-02-11 (38 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX481FL_UX481FL
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=af_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=c157ba74-8933-4447-9f11-e965279079be ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX481FL.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX481FL
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.:bvrUX481FL.206:bd08/06/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX481FL_UX481FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX481FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX481FL_UX481FL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan kubuntu 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/1868392

Title:
  Touchscreen not working in 5.3.0-42

Status in xorg package in Ubuntu:
  New

Bug description:
  My Asus Zenbook touch screen works in 5.3.0-40, but stops working when
  I boot into the 5.3.0-42 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: 

[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

The slowness might have caused by some apparmor probs:
pr 11 15:16:58 zander kernel: [13422.621558] audit: type=1400 
audit(1554988618.771:27): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=13888 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:20:43 zander kernel: [13647.282091] audit: type=1400 
audit(1554988843.431:28): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=20908 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:25:43 zander kernel: [13947.374877] audit: type=1400 
audit(1554989143.520:29): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=27940 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:28:24 zander kernel: [14108.309867] audit: type=1400 
audit(1554989304.459:30): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=424 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:28:46 zander kernel: [14130.333125] audit: type=1400 
audit(1554989326.483:31): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=1116 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:00 zander kernel: [14984.432581] audit: type=1400 
audit(1554990180.581:32): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26456 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:03 zander kernel: [14987.725323] audit: type=1400 
audit(1554990183.873:33): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26546 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:05 zander kernel: [14989.287668] audit: type=1400 
audit(1554990185.433:34): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26584 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:06 zander kernel: [14990.386287] audit: type=1400 
audit(1554990186.533:35): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26610 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:54:37 zander dbus-daemon[859]: [system] Activating service 
name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.167' (uid=1000 
pid=14054 comm="/usr/bin/python3 /usr/share/system-config-printer/" 
label="unconfined") (using servicehelper)
Apr 11 15:54:37 zander dbus-daemon[859]: [system] Successfully activated 
service 'org.opensuse.CupsPkHelper.Mechanism'
Apr 11 15:55:43 zander kernel: [15747.355081] audit: type=1400 
audit(1554990943.501:36): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=15434 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:58:20 zander kernel: [15904.185434] audit: type=1400 
audit(1554991100.336:37): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=21257 
comm="apparmor_parser"
Apr 11 15:58:20 zander kernel: [15904.185716] audit: type=1400 
audit(1554991100.336:38): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="/usr/sbin/cupsd" pid=21257 comm="apparmor_parser"

Did aa-disable cupsd and it seems faster.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  

[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

I have a situation that is similar but not with a windows server.

I have an experimental server which is installed with Ubuntu Disco.
Queues are authenticated with kerberos. This is IPP-Everywhere queues.

I have a client with Ubuntu 18.04.2 LTS.

Printing did not work with cups-2.2.7-1ubuntu2.4 on the client. Same
symptoms as described here, cannot print, authentication prompt despite
valid kerberos tickets.

I compiled upstream cups 2.2.7 with Eskos fix-password-prompt.patch AND
the kerberos truncate patch from #13 and installed it on the client.

It works, but printing is very slow, at least from firefox.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

Is this fix available in Disco?

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1783298/+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 1818679] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Johan GAUB]

Hello Arnold,

I thank you for your answer.

It looks like openssh-server was not installed.

Then, I installed it and I have this message after doing a "sshd -t" :
Could not load host key: /etc/ssh/ssh_host_rsa_key
Could not load host key: /etc/ssh/ssh_host_ecdsa_key
Could not load host key: /etc/ssh/ssh_host_ed25519_key

The folder /var/run/sshd exists but have nothing inside it.

Hope this will resovle the issue.

Regards

Johan


Le mar. 5 mars 2019 à 19:20, Seth Arnold <1818...@bugs.launchpad.net> a
écrit :

> Hello, can you please run this command and report back the results?
>
> ls -ld /
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1818679
>
> Title:
>   package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
>   le sous-processus script post-installation installé a retourné une
>   erreur de sortie d'état 1
>
> Status in openssh package in Ubuntu:
>   New
>
> Bug description:
>   I can't tell you anything. There was a error message without specific
>   details.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: openssh-server 1:7.2p2-4ubuntu2.8
>   ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
>   Uname: Linux 4.4.0-142-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: amd64
>   Date: Tue Mar  5 06:48:59 2019
>   ErrorMessage: le sous-processus script post-installation installé a
> retourné une erreur de sortie d'état 1
>   InstallationDate: Installed on 2016-08-12 (935 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.5
>apt  1.2.29ubuntu0.1
>   SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit
> code 255: Missing privilege separation directory: /var/run/sshd
>   SourcePackage: openssh
>   Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to
> install/upgrade: le sous-processus script post-installation installé a
> retourné une erreur de sortie d'état 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1818679/+subscriptions
>

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  le sous-processus script post-installation installé a retourné une
  erreur de sortie d'état 1

Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I can't tell you anything. There was a error message without specific
  details.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Mar  5 06:48:59 2019
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2016-08-12 (935 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1818679/+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 1818679] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Johan GAUB]

Public bug reported:

I can't tell you anything. There was a error message without specific
details.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.8
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue Mar  5 06:48:59 2019
ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
InstallationDate: Installed on 2016-08-12 (935 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29ubuntu0.1
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
Missing privilege separation directory: /var/run/sshd
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  le sous-processus script post-installation installé a retourné une
  erreur de sortie d'état 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I can't tell you anything. There was a error message without specific
  details.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Mar  5 06:48:59 2019
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2016-08-12 (935 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1818679/+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 1779340] [NEW] systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge

[Johan Ehnberg]

Public bug reported:

The following simple netplan config results in a 2-minut unneccessary
delay on boot. Everything works like it should in the end. The bridge
has no interfaces due to a regression in Ubuntu migrating to netplan
(see https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341).

ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
enp4s0:
  dhcp4: yes
  dhcp6: yes

ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml
network:
  version: 2
  bridges:
br1:
  addresses: [10.1.0.9/16]
  interfaces: []

ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0
#!/bin/sh
set -e
 if [ "$IFACE" = tap0 ]; then
  brctl addif br1 tap0
  ip link set tap0 promisc on
  ifmetric tap0 5
fi

ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b
-- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 
UTC. --
Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be 
Configured...
Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:19 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 13:58:21 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
Jun 29 14:00:16 molnix3 systemd-networkd-wait-online[1468]: Event loop failed: 
Connection timed out
Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
Jun 29 14:00:16 molnix3 systemd[1]: Failed to start Wait for Network to be 
Configured.

ubuntu@molnix3:~$ /lib/systemd/systemd-networkd-wait-online
managing: br1
managing: enp4s0
ignoring: lo

ubuntu@molnix3:~$ networkctl
IDX LINK TYPE   OPERATIONAL SETUP
  1 lo   loopback   carrier unmanaged
  2 enp4s0   ether  routableconfigured
  3 br1  ether  routableconfigured
  4 tap0 ether  routableunmanaged

4 links listed.

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

** Description changed:

  The following simple netplan config results in a 2-minut unneccessary
  delay on boot. Everything works like it should in the end. The bridge
  has no interfaces due to a regression in Ubuntu migrating to netplan
- (see separate bug).
+ (see https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341).
  
- ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml 
+ ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
-   version: 2
-   renderer: networkd
-   ethernets:
- enp4s0:
-   dhcp4: yes
-   dhcp6: yes
+   version: 2
+   renderer: networkd
+   ethernets:
+ enp4s0:
+   dhcp4: yes
+   dhcp6: yes
  
- ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml 
+ ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml
  network:
-   version: 2
-   bridges:
- br1:
-   addresses: [10.1.0.9/16]
-   interfaces: []
+   version: 2
+   bridges:
+ br1:
+   addresses: [10.1.0.9/16]
+   interfaces: []
  
- ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0 
+ ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0
  #!/bin/sh
  set -e
-  if [ "$IFACE" = tap0 ]; then
-   brctl addif br1 tap0
-   ip link set tap0 promisc on
-   ifmetric tap0 5
+  if [ "$IFACE" = tap0 ]; then
+   brctl addif br1 tap0
+   ip link set tap0 promisc on
+   ifmetric tap0 5
  fi
  
  ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b
  -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 
UTC. --
  Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be 
Configured...
  Jun 29 13:58:16 

[Touch-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Johan Marius Wesselink]

Tested the scilab 5.5.2 for ubuntu which works great. 
However, I did not test it before applying the jogl2 patch :-o.  

Had a look at the source and it seems that the Ubuntu version is patched to use 
the
generic version of jogl2. 

I would like to try and get this patch integrated in the Scilab source tree. 
Probably a difficult and slow process.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1742894/+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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Johan Marius Wesselink]

I tested the proposed package on Lubuntu 17.10.

I tested some example programs they use either:
GLProfile glp = GLProfile.getDefault();
Or they use the GLCanvas default constructor.

Before this version all these examples emitted the typical error found
in the previous version of jogl2. The new package RESOLVED this problem.

I noticed after some experimenting that replacing getDefault with 
get(GLProfile.GL2);
also solved the problem. Then I found this thread.

I build scilab from source using the git repository. This is the master
and future 6.1 version it has the same problem. However, scilab 6 and
higher have the jogl2 library prebuild and distributed as a thirdparty
library. Removing this library doesn't work. The problem is that the
scirender module and the gui modules depend on the old syntax. The Java
path in the past was javax.media. In newer version of jogl2 this changed
to com.jogamp. This means that besides removing the faulty library from
scilab the modules scirender and gui need to be patched. I did just this
in the last days. The git master branch version 6.1 build and works with
the new jogl2 version. I noticed however one regression bug the cursor
selection in the plot window work kind of inverted. This is an old bug
which I have seen before.

So, yes this fixes the jogl2 bug. But, no likely not the scilab bug.
Depends how you get scilab and which version probably.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1742894/+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 123920] Re: Bluetooth Logitech Dinovo Keyboard/Mouse don't work

[Johan Leckström]

It works for me 

Den 29 maj 2017 11:47 skrev "Daniel van Vugt" :

> Can anyone confirm if this bug still exists with Logitech Dinovos in a
> current Ubuntu release?
>
> ** Changed in: bluez (Ubuntu)
>Status: Triaged => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/123920
>
> Title:
>   Bluetooth Logitech Dinovo Keyboard/Mouse don't work
>
> Status in Bluez Utilities:
>   New
> Status in Bluez-utils:
>   New
> Status in Linux Mint:
>   Invalid
> Status in Unity:
>   Invalid
> Status in bluez package in Ubuntu:
>   Incomplete
> Status in linux package in Ubuntu:
>   Invalid
> Status in linux-source-2.6.22 package in Ubuntu:
>   Won't Fix
> Status in udev package in Ubuntu:
>   Invalid
>
> Bug description:
>   Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse
> will work until Nautilus starts.  After Nautilus starts the keyboard and
> mouse are unresponsive and do not work.
>   I tried reconnecting the keyboard and mouse by using the discovery
> buttons on both the Bluetooth Dongle and Input device.  The problem still
> persists.
>   Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ
> motherboard.  Logitech Dinovo media keyboard and mx1000 laser bluetooth
> mouse, with logitech mini bluetooth receiver.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/bluez/+bug/123920/+subscriptions
>

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

Title:
  Bluetooth Logitech Dinovo Keyboard/Mouse don't work

Status in Bluez Utilities:
  New
Status in Bluez-utils:
  New
Status in Linux Mint:
  Invalid
Status in Unity:
  Invalid
Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Invalid
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix
Status in udev package in Ubuntu:
  Invalid

Bug description:
  Testing Gutsy Gibbon Tribe 2 LiveCD and bluetooth keyboard and mouse will 
work until Nautilus starts.  After Nautilus starts the keyboard and mouse are 
unresponsive and do not work.
  I tried reconnecting the keyboard and mouse by using the discovery buttons on 
both the Bluetooth Dongle and Input device.  The problem still persists.
  Using Intel P4 2.8 Ghz Processor, 3 GB ddr400 ram, Intel D875PBZ motherboard. 
 Logitech Dinovo media keyboard and mx1000 laser bluetooth mouse, with logitech 
mini bluetooth receiver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/123920/+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 1685882] [NEW] Dbus error when starting Dropbox

[Debal Johan]

Public bug reported:

Dropbox isn't running!
Starting Dropbox...Dropbox isn't running!
Done!
xxx@wsxx:~$ 
** (dropbox:8684): WARNING **: Couldn't connect to accessibility bus: Failed to 
connect to socket /tmp/dbus-688PGh4rgi: Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Apr 24 20:32:19 2017
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Dbus error when starting Dropbox

Status in dbus package in Ubuntu:
  New

Bug description:
  Dropbox isn't running!
  Starting Dropbox...Dropbox isn't running!
  Done!
  xxx@wsxx:~$ 
  ** (dropbox:8684): WARNING **: Couldn't connect to accessibility bus: Failed 
to connect to socket /tmp/dbus-688PGh4rgi: Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 24 20:32:19 2017
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1685882/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Johan Boule]

** Tags added: zesty

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Johan Boule]

The bug is still here in Ubuntu 17.10.
Tested by opening gedit, and adding a second tab : my eyes can hardly tell 
which tab is active.

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Johan Tol]

The same for me today. After upgrading to 16.10 I had no connection via
VPN. Deleting the line "dns=dnsmasq" from
/etc/NetworkManager/Networkmanager.conf followed by 'sudo service
NetworkManager restart" did the trick for me. The connection was very
slow though, but I don't know if that is related to the problem. I also
don't know what the "penalty" is for removing the dns=dnsmasq line.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

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

Bug description:
  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1624317/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Johan Tol]

This fix doesn't work for me (Dell Latitude E6540, Ubuntu 16.04);
/var/log/syslog mentions instead:

Error calling EVIOCSKEYCODE on device node '/dev/input/event17' (scan
code 0x100150, key code 190): Invalid argument

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Johan Boule]

In Unbuntu 16.10, the easy fix in ~/.config/gtk-3.0/gtk.css does not
work anymore.

I used to simply have this in that file :

  .notebook tab:active {
background-color: @selected_bg_color;
  }

But now, gedit does not take it into account anymore (neither gnome-
terminal but afaik they unfortunately hacked something specific just to
workaround the problem locally, and indeed it's now better-looking in
that app now).

Does anyone know what's the new css class to style to get *all* gtk tabs
look fine ?

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1307593] Re: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all

[Carl-Johan Kjellander]

This happened to me when installing a new graphics card.

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

Title:
  [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound was ok on 12.04.4 but I've had no sound on my headphones since
  upgrading to 13.10.  Sound works on HDMI to screen.  Have tried to fix
  problem by trying fixes listed in No sound in Ubuntu 13.10 web pages
  but nothing worked for me.

  Ubuntu 13.10 64-bit  Memory 7.7 GiB  CPU intel core i5-4570  Graphics
  Intel Haswell Desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simon  9189 F pulseaudio
   /dev/snd/controlC0:  simon  9189 F pulseaudio
  Date: Mon Apr 14 16:57:27 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-02 (12 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  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/controlC1:  simon  9189 F pulseaudio
   /dev/snd/controlC0:  simon  9189 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/07/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H87N-WIFI
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1307593/+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 1567841] Re: One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

I have tried the daily-current, and I could not reproduce the bug by
running it for 20 hours, and usually I can trigger the bug within an
hour.

But, I could get the livecd to match my current setup exactly. For one
thing it uses unity and not gnome-shell, and I can't install things
temporarily with apt-get. So I had to use a statically compiled chromium
instead of google chrome.

I have found two ways of triggering the bug, and it is still there on
"Ubuntu 14.04.5 LTS", and that is by letting one of these two links run
for a long time in google chrome.

http://xkcd.com/1663/
 or
https://vicandblood.itch.io/dopesmoker

And it only happens with Chrome and not Firefox.

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:04bb]
  InstallationDate: Installed on 

[Touch-packages] [Bug 1631528] [NEW] Blank screen after grub menu

[Johan Nilsson]

Public bug reported:

After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some
problems booting. After the grub menu the screen goes blank and nothing
happens after that. I think the system is booting properly apart from
the screen not showing anything, I can change the volume using the
hardware keys and I can connect with SSH from another machine. I've
found two workarounds for this problem.

1) Select recovery mode from the grub meny and then resume normal boot,
however, the screen resolution is not set properly.

2) Change my grub config file to boot into text mode. I commented out the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
and changed
GRUB_CMDLINE_LINUX=""
to
GRUB_CMDLINE_LINUX=”text"
and uncommented the line
#GRUB_TERMINAL=console

After running sudo update-grub and rebooting the system boots into MATE
and the correct screen resolution is set.

I've collected dmesg after a "blank screen" boot, let me know if there
is anything else I should provide.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Oct  7 22:41:04 2016
InstallationDate: Installed on 2016-10-06 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug freeze xenial

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1631528/+attachment/4757005/+files/dmesg.txt

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

Title:
  Blank screen after grub menu

Status in xorg package in Ubuntu:
  New

Bug description:
  After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some
  problems booting. After the grub menu the screen goes blank and
  nothing happens after that. I think the system is booting properly
  apart from the screen not showing anything, I can change the volume
  using the hardware keys and I can connect with SSH from another
  machine. I've found two workarounds for this problem.

  1) Select recovery mode from the grub meny and then resume normal
  boot, however, the screen resolution is not set properly.

  2) Change my grub config file to boot into text mode. I commented out the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  and changed
  GRUB_CMDLINE_LINUX=""
  to
  GRUB_CMDLINE_LINUX=”text"
  and uncommented the line
  #GRUB_TERMINAL=console

  After running sudo update-grub and rebooting the system boots into
  MATE and the correct screen resolution is set.

  I've collected dmesg after a "blank screen" boot, let me know if there
  is anything else I should provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Oct  7 22:41:04 2016
  InstallationDate: Installed on 2016-10-06 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631528/+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 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied

[Johan Ehnberg]

** Description changed:

- fstrun daily cronjob output in an unprivileged LXD container:
+ fstrun weekly cronjob output in an unprivileged LXD container:
  
  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted
  
- 
  There is a github issue:
  
  https://github.com/lxc/lxd/issues/2030
  
- 
- The outcome is that it's purely an fstrim misbehaviour, it could be smarter.
- 
+ The outcome is that it's purely an fstrim misbehaviour, it could be
+ smarter.
  
  Stephane Graber comment:
  
- 
- 
- As all of this is handled by the kernel, there isn't anything we can do about 
it in LXD.
+ As all of this is handled by the kernel, there isn't anything we can do
+ about it in LXD.
  
  I think fstrim should be made slightly more clever:
  
  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
-  LANGUAGE=en_US:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  fstrun weekly cronjob output in an unprivileged LXD container:

  /etc/cron.weekly/fstrim:
  fstrim: cannot open /dev/.lxd-mounts: Permission denied
  fstrim: /dev/fuse: not a directory
  fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted

  There is a github issue:

  https://github.com/lxc/lxd/issues/2030

  The outcome is that it's purely an fstrim misbehaviour, it could be
  smarter.

  Stephane Graber comment:

  As all of this is handled by the kernel, there isn't anything we can
  do about it in LXD.

  I think fstrim should be made slightly more clever:

  * Don't run on bind-mounts (you can detect bind-mounts by parsing 
/proc/self/mountinfo instead of /proc/mounts)
  * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, 
only log actual failures which would likely be EINVAL or memory related errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sun Jun  5 19:49:04 2016
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+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 762349] Re: [SRU] Difficult to distinguish which tab is selected

[Johan Boule]

The current fix is only a workaround that's specific to the terminal app, while 
the bug appears to be broader issue assigned to the ubuntu-themes package.
I can confirm that the problem persists for other apps. Try gedit for example.
Can you please reopen the bug ?

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

Title:
  [SRU] Difficult to distinguish which tab is selected

Status in Ayatana Design:
  Fix Committed
Status in Ubuntu theme:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]
   * When a user opens multiple tabs in GNOME terminal all tabs are styled in a 
*very* visually similar manner.  This makes it very hard to distinguish between 
the current active tab and all the others and on a HiDPI screen pretty much 
impossible.

  * This fix has been ack'd by design and was targeted for X but didn't
  get reviewed and OK'd in time.  Design team have approved this
  styling.

  * This bug is fixed by extending the CSS specifically for Terminal
  (i.e. no other applications are affected) giving the active tab a
  darker background colour (using only theme defined colours) and
  reworks the borders around the tabs to remove the graduated image
  borders that only look right on a light coloured background.  Changes
  have been made for both Ambiance and Radiance.

  [Test Case]
   * On a stock 16.04 install open GNOME Terminal (ctrl-alt-t)
   * Open five new tabs (ctrl-shift-t)
   * Click on the tab in the middle
   * Note that it is hard to see at a glance which tab is currently selected
   * Close Terminal and all open tabs.
   * Install the patched theme
   * Open Terminal and open five new tabs
   * Click on the tab in the middle and note that it takes on a light grey 
background compared to the unselected tabs which are dark grey.

  [Regression Potential]
   * The patch only addresses tabs that are placed at the top of the window. 
However this is the only option in Terminal, so should not cause any problems.
   * There is a work-around to match the "actions bar" (the bit with the 
dropdown selector and + button).  This bug is supposed to be fixed in v3.20 and 
could be removed.  This is commented in the CSS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Shortly after its introduction I migrated to Ubuntu 16.04. Today I
rolled back the "uxa"-workaround by deleting the 20-intel.conf file from
/etc/X11/xorg.conf.d (I didn't have one before the workaround). After a
couple of hours I still haven't had a single crash. I guess 16.06 solved
the problem.

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  WORKAROUND: /etc/X11/xorg.conf.d/20-intel.conf

  with the following content:

  Section "Device"
   Identifier "Card0"
   Driver "Intel"
   Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  

[Touch-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

typo: 16.06 --> 16.04

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  WORKAROUND: /etc/X11/xorg.conf.d/20-intel.conf

  with the following content:

  Section "Device"
   Identifier "Card0"
   Driver "Intel"
   Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 

[Touch-packages] [Bug 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Johan Tol]

In /lib/udev/hwdb.d/60-keyboard.hwdb I see the following related to scan
code 150:

# Dell Latitude microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnLatitude*
# Dell Precision microphone mute
evdev:name:Dell WMI hotkeys:dmi:bvn*:bvr*:bd*:svnDell*:pnPrecision*
 KEYBOARD_KEY_150=f20  # Mic mute toggle, should be micmute

Is that related to the error message?

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

[Johan Tol]

I have exactly the same message for my Dell Latitude E6540.

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

Title:
  systemd-udevd: Error calling EVIOCSKEYCODE on device node
  '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  the symptom is this error message in my system's logs:

  juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling
  EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key
  code 190): Invalid argument

  According to /proc/bus/input/devices the corresponding input device
  is:

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Dell WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input10
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=13
  B: KEY=1000b0400 0 e 0
  B: MSC=10

  This laptop is a Dell Latitude E6520.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: udev 229-4ubuntu6
  Uname: Linux 4.6.3-040603-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  CustomUdevRuleFiles: 60-ssd-scheduler.rules
  Date: Wed Jun 29 17:43:01 2016
  EcryptfsInUse: Yes
  MachineType: Dell Inc. Latitude E6520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic 
root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup 
mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0NVF5K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6520
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415/+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 1582191] [NEW] Boot stalls for 90 seconds on mdadm

[Johan Ehnberg]

Public bug reported:

On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for
exactly 90 seconds when using a fairly complex partitioning setup. After
this, everything works as expected.

The partitioning is as follows:
/sda GPT
/sda1 ESP (/boot/efi)
/sda2 raid1 md0 ext4 (/boot)
/sda3 raid1 md1 luks,passphrase ext4 (/)
/sda4 raid1 md2 luks,key zfs
/sdb GPT
/sdb1 ESP (copy of /boot/efi)
/sdb2 raid1 md0 ext4 (/boot)
/sdb3 raid1 md1 luks,passphrase ext4 (/)
/sdb4 raid1 md2 luks,key zfs
/sdc GPT
/sdc1 luks,key xfs
/sdd GPT
/sdd1 luks,key xfs
/sdd2 luks,random swap

This may be an installer or mdadm bug instead - I have not been able to
exactly determine the cause of the bug.

I have several identical servers, all showing the same symptom, so it
should not be due to broken hardware (although design flaws are on the
table).

The key seems to be in these lines from journalctl:
...
May 16 14:06:08 molnix kernel: bridge: automatic filtering via arp/ip/ip6tables 
has been deprecated. Update your scripts to load br_netfilter if you need this.
May 16 14:06:08 molnix kernel: device eno1 entered promiscuous mode
May 16 14:06:08 molnix systemd-udevd[689]: Process '/lib/udev/hdparm' failed 
with exit code 5.
May 16 14:06:08 molnix systemd-udevd[701]: Process '/lib/udev/hdparm' failed 
with exit code 5.
May 16 14:06:08 molnix systemd-udevd[707]: Process '/lib/udev/hdparm' failed 
with exit code 5.
May 16 14:06:08 molnix systemd[1]: Started Monitoring of LVM2 mirrors, 
snapshots etc. using dmeventd or progress polling.
May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental 
/dev/sda2 --offroot' failed with exit code 1.
May 16 14:06:08 molnix systemd-udevd[707]: Process '/sbin/mdadm --incremental 
/dev/sda3 --offroot' failed with exit code 1.
May 16 14:06:08 molnix systemd[1]: Found device Samsung_SSD_850_EVO_250GB 
EFI\x20System\x20Partition.
May 16 14:06:08 molnix systemd-udevd[708]: Process '/sbin/mdadm --incremental 
/dev/sda4 --offroot' failed with exit code 1.
May 16 14:06:08 molnix systemd-udevd[689]: Process '/sbin/mdadm --incremental 
/dev/sdb3 --offroot' failed with exit code 1.
May 16 14:06:08 molnix systemd[1]: Reached target Local File Systems (Pre).
May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental 
/dev/sdb4 --offroot' failed with exit code 1.
May 16 14:06:08 molnix systemd-udevd[699]: Process '/sbin/mdadm --incremental 
/dev/sdb2 --offroot' failed with exit code 1.
May 16 14:06:08 molnix systemd-udevd[706]: Process '/lib/udev/hdparm' failed 
with exit code 5.
May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: The BMC does not support 
clearing the recv irq bit, compensating, but the BMC needs to be fixed.
May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 
0x002a7c, prod_id: 0x086d, dev_id: 0x20)
...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Mon May 16 14:17:31 2016
InstallationDate: Installed on 2016-05-15 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
MachineType: Supermicro Super Server
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=0ca65308-3f70-4231-8f5f-e68583a6d5b3 ro
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf

 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X10SDV-4C-TLN4F
dmi.board.vendor: Supermicro
dmi.board.version: 2.00
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/04/2016:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-4C-TLN4F:rvr2.00:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: Super Server
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

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


** Tags: amd64 apport-bug xenial

** Description changed:

  On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for
  exactly 90 seconds when using a fairly complex partitioning setup. After
  this, everything works as expected.
  
  The partitioning is as follows:
  /sda GPT
  /sda1 ESP (/boot/efi)
  /sda2 raid1 md0 ext4 (/boot)
  /sda3 raid1 md1 luks,passphrase ext4 (/)
  /sda4 raid1 md2 luks,key zfs
  /sdb GPT
  /sdb1 ESP (copy of /boot/efi)
  

[Touch-packages] [Bug 1576167] Re: Percentage bars are ugly

[Johan Boule]

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

The ugliness is beyond comprehension. Someone is sadistically toying around 
with our poor eyes and this is a rather unpleasant feeling.
Before you fix something, that thing needs to be broken in the first place, 
right ? Well done then.
It's unfortunate the person who did this change didn't put his efforts on 
fixing bug #762349 instead.
What's the next step ? Shall we try removing the orange border and keep only 
the white colour ?

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

Title:
  Percentage bars are ugly

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  The percentage bars showing progress are orange background with a
  white centre and black text.

  * The black text is unreadable on orange
  * The white centre of the scroll bar looks strange, like the progress bar has 
had the middle hollowed out

  To reproduce

  Open software properties
  Toggle the Source code option in the first tab
  Press close button
  At next dialog, choose reload
  Expand twisty to show details of the software update.

  See screenshot

  I'd expect the text to be readable white on solid orange or black on
  solid white.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: software-properties-gtk 0.96.20
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 28 12:28:50 2016
  InstallationDate: Installed on 2016-04-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1576167/+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 762349] Re: Difficult to distinguish which tab is selected

[Johan Boule]

I really hope the 16.04.1 point release will finally get someone to push a fix 
to this otherwise we're going to live with this for several more years.
I'm re-enabling my custom ~/.config/gtk-3.0/gtk.css once again.

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

Title:
  Difficult to distinguish which tab is selected

Status in Ayatana Design:
  New
Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  Binary package hint: unity

  In tabbed interfaces such as in gnome-terminal under unity it is
  difficult to visually distinguish the selected tab from the unselected
  ones.

  In the attached screenshot, gnome-terminal has three tabs open, and
  the third one is selected.  If you look close you can see the text is
  slightly whiter than the other tabs, and the border is a little more
  prominent but to my old man eyes it's really hard to see it at a
  glance.

  Under metacity, the difference is more notable (or at least, the theme
  is different).

  My guess is this is a theme issue rather than unity, but I'm unsure.
  If it is just a theme issue please refile to the right project.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.8-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Fri Apr 15 17:41:12 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 762349] Re: Difficult to distinguish which tab is selected

[Johan Boule]

Since this simple theme bug has not been fixed for 5 years, despite
being a annoying usability issue, I have to ask what's needed to be able
to eventually see a fix coming.

Is there something that makes it technically harder than it seems to be to 
correct the theme ?
Who's in charge of the gtk theming issues ?
Has this bug been assigned to the right person ?

How can we make it progress ?

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

Title:
  Difficult to distinguish which tab is selected

Status in Ayatana Design:
  New
Status in Ubuntu theme:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress
Status in ubuntu-themes source package in Xenial:
  In Progress

Bug description:
  Binary package hint: unity

  In tabbed interfaces such as in gnome-terminal under unity it is
  difficult to visually distinguish the selected tab from the unselected
  ones.

  In the attached screenshot, gnome-terminal has three tabs open, and
  the third one is selected.  If you look close you can see the text is
  slightly whiter than the other tabs, and the border is a little more
  prominent but to my old man eyes it's really hard to see it at a
  glance.

  Under metacity, the difference is more notable (or at least, the theme
  is different).

  My guess is this is a theme issue rather than unity, but I'm unsure.
  If it is just a theme issue please refile to the right project.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.8-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Fri Apr 15 17:41:12 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update

[Johan van Breda]

My system has the same problem. Looks like an un-initialized parameter.

Changes to the network via the GUI fail due to this, but nmcli still works.
That is  cumbersome, but provides a workaround.

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

Title:
  [Kubuntu] Fail to connect to wifi after a recent update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I installed the recent updates in the Update Manager and after rebooting I 
wasn't able to connect to my wifi network anymore.
  It attempts to connect to the network and fails with the following error 
message:

  Failed to update connection [network name]
  connection.gateway-ping-timeout: can not set property:
  value "46730064" of type 'guint' is invalid or out of range for property 
'gateway-ping-timeout' of type 'guint'

  I am able to use wired connection.

  1. release:
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  2. network-manager version:
  network-manager:
Installed: 1.1.93-0ubuntu3
Candidate: 1.1.93-0ubuntu3
Version table:
   *** 1.1.93-0ubuntu3 500
  500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expected the machine to connect to wifi as always

  4. it failed to connect with the above error message

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 13 06:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-01 (11 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  IpRoute:
   default via 10.100.102.1 dev enp0s31f6  proto static  metric 100 
   10.100.102.0/24 dev enp0s31f6  proto kernel  scope link  src 10.100.102.5  
metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-12T22:28:14.870844
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s31f6  ethernet  connected/org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  d956dc0d-4de6-4f45-8869-a3703d8d0d28  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0 wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569674/+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 1567841] Re: One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

[354327.154763] [TTM] Out of kernel memory
[354327.154770] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224001] [TTM] Out of kernel memory
[354327.224008] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224572] [TTM] Out of kernel memory
[354327.224574] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224585] [TTM] Out of kernel memory
[354327.224587] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224594] chrome[16008]: segfault at 10 ip 7fafe02a5b5c sp 
7ffd84ced8f0 error 4 in r600_dri.so[7fafdffef000+399000]
[355403.930696] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (262144, 2, 4096, -12)

Maybe this is related?

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro 

[Touch-packages] [Bug 1567841] Re: One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

[354327.154763] [TTM] Out of kernel memory
[354327.154770] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224001] [TTM] Out of kernel memory
[354327.224008] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224572] [TTM] Out of kernel memory
[354327.224574] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224585] [TTM] Out of kernel memory
[354327.224587] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224594] chrome[16008]: segfault at 10 ip 7fafe02a5b5c sp 
7ffd84ced8f0 error 4 in r600_dri.so[7fafdffef000+399000]
[355403.930696] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (262144, 2, 4096, -12)

Maybe this is related?

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro 

[Touch-packages] [Bug 1567841] [NEW] One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

Public bug reported:

I run a setup of 2 radeon graphics cards, with 3 screens, in the
following layout from left to right counting from 0:

Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

I have been running this setup for a year and it has worked fine. This
monday I updated some packages and did a reboot, and I usually reboot
just once a month cause I patch my running kernel with uptrack.

After the reboot I started noticing problems with the second card, Card
1 above. With a mean time between failures of about an hour, the second
card freezes the screen, I usually notice that the mouse pointer isn't
visible anymore when I move it across from one screen to the middle one.
For future reference, the window I have on the middle screen is a
fullscreen emacs window.

I have tried the following kernels: vmlinuz-3.13.0-77-generic,
vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

All have the same problem. And nothing shows up in dmesg when the freeze
occurs, or in the Xorg.0.log, I made copies from before and after a
freeze.

If I move the mouse, that I can't see, onto the middle screen, make
emacs the active window (again I can't see this), scroll around a bit
with the arrow keys and take a screenshot, the screenshot shows the
correctly scrolled window, so the big X buffer is actually correctly
updated.

If I CTRL-ALT-L to lock the screens, they all go black, but when you
press enter only the screens on Card 0 shows the lock screen, the middle
one again shows frozen emacs.

CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
middle, you've guessed it, frozen emacs.

If I go to the menu and select Switch user, surprise! Now the frozen
screen is gone and it is a gray login screen with the login menu
actually on the screen to the right.

Log back into my still running user, boooh, it again shows the same
frozen emacs.

Switch to a completely new user, screen in middle is correct and
working.

And lastly if I log out completely from my user and log in again the
screen is now unfrozen, but I have lots of work and it is really really
annoying to have to log out 8 times during a day at work.

I'm gonna try one more ancient kernel just to see if there have been
some changes to drm or the radeon driver, but I am pretty stumped on
this one. It all worked fine last week.

Description:Ubuntu 14.04.4 LTS
Release:14.04
Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr  8 10:38:17 2016
DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
 Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:04bb]
InstallationDate: Installed on 2012-03-13 (1486 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-77-generic 
root=/dev/mapper/fiskgunnar-root ro nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2015-03-16 (388 days ago)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0906
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd12/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name

[Touch-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 

[Touch-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

This issue seems to be resolved in Xenial.

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9

To manage 

Re: [Touch-packages] [Bug 1358467] Re: Time and date not always there

[Johan Wysneus]

Thanks for your email. I reported this a long time ago and the problem 
seems to have disappeared in the meantime.

Regards
Johan


On 28/02/2016 23:20, Christopher M. Penalver wrote:
> Johan Wysneus, thank you for reporting this and helping make Ubuntu
> better.
>
> Could you please provide the full computer model as noted on the sticker
> of the computer itself (not from the Bug Description)?
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Time and date not always there

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The time and date is not always displayed in the top right corner
  after boot up. Sometimes I have to reboot several times before time
  and date is displayed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 18 21:34:17 2014
  DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=a83be82f-cfd0-44f3-b18a-2e3c7a637068 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (86 days ago)
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01KY.M008.20100430.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: N150P/N210P/N220P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: N150P/N210P/N220P
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Aug 18 16:41:23 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12336 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1358467/+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 1404302] Re: liblttng-ust0 Error opening shm /lttng-ust-wait-5 - do not link liblttng-ust!

[Johan Guerreros]

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: Fix Committed => In Progress

** Changed in: canonical-developer-experience
   Status: Confirmed => Fix Released

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  liblttng-ust0 Error opening shm /lttng-ust-wait-5 - do not link
  liblttng-ust!

Status in Client Developer Experience:
  Fix Released
Status in platform-api:
  Invalid
Status in content-hub package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in ubuntu-app-launch package in Ubuntu:
  Invalid
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Confined apps don't have access to this and continuously produce this
  error message in stderr:

  libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in
  get_wait_shm() at lttng-ust-comm.c:958)

  
  This is printed to the application's log about once every other second and 
makes it hard to read the application's own debug output. For a better app 
developer experience this message should be silenced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1404302/+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 1547910] [NEW] package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to install/upgrade: package libhcrypto4-heimdal:i386 is already installed and configured

[johan Gissberg]

Public bug reported:

Trying to install World of warships via PlayOnLinux when this problem
occured

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 600:0:115:153451:2016-02-20 16:48:41.722852706 +0100:2016-02-20 
16:48:42.722852706 +0100:/var/crash/libasn1-8-heimdal:i386.0.crash
 600:0:115:153455:2016-02-20 16:48:41.762852430 +0100:2016-02-20 
16:48:42.762852430 +0100:/var/crash/libhcrypto4-heimdal:i386.0.crash
 600:0:115:153453:2016-02-20 16:48:41.670852899 +0100:2016-02-20 
16:48:42.670852899 +0100:/var/crash/libroken18-heimdal:i386.0.crash
Date: Sat Feb 20 16:48:42 2016
DuplicateSignature: 
package:libhcrypto4-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package 
libhcrypto4-heimdal:i386 is already installed and configured
ErrorMessage: package libhcrypto4-heimdal:i386 is already installed and 
configured
InstallationDate: Installed on 2015-12-21 (60 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: heimdal
Title: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to 
install/upgrade: package libhcrypto4-heimdal:i386 is already installed and 
configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed apport-package i386 need-duplicate-check wily

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

Title:
  package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to
  install/upgrade: package libhcrypto4-heimdal:i386 is already installed
  and configured

Status in heimdal package in Ubuntu:
  New

Bug description:
  Trying to install World of warships via PlayOnLinux when this problem
  occured

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   600:0:115:153451:2016-02-20 16:48:41.722852706 +0100:2016-02-20 
16:48:42.722852706 +0100:/var/crash/libasn1-8-heimdal:i386.0.crash
   600:0:115:153455:2016-02-20 16:48:41.762852430 +0100:2016-02-20 
16:48:42.762852430 +0100:/var/crash/libhcrypto4-heimdal:i386.0.crash
   600:0:115:153453:2016-02-20 16:48:41.670852899 +0100:2016-02-20 
16:48:42.670852899 +0100:/var/crash/libroken18-heimdal:i386.0.crash
  Date: Sat Feb 20 16:48:42 2016
  DuplicateSignature: 
package:libhcrypto4-heimdal:i386:1.6~rc2+dfsg-10ubuntu1:package 
libhcrypto4-heimdal:i386 is already installed and configured
  ErrorMessage: package libhcrypto4-heimdal:i386 is already installed and 
configured
  InstallationDate: Installed on 2015-12-21 (60 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: heimdal
  Title: package libhcrypto4-heimdal:i386 1.6~rc2+dfsg-10ubuntu1 failed to 
install/upgrade: package libhcrypto4-heimdal:i386 is already installed and 
configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1547910/+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 1540294] Re: Network manager stopped working after some update

[Johan]

Latest update of network-manager (feb 04) solved the issue for me.

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

Title:
  Network manager stopped working after some update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  'sudo NetworkManager' gives:
  (NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Key file does not have group 'connectivity'

  To get network interface to work I have to do like this:
  'sudo ip link set dev eth0 down'
  'sudo dhclient eth0'

  
  Ubuntu 14.04.3 LTS

  'apt-cache policy network-manager':
  network-manager:
Installed: 0.9.8.8-0ubuntu7.2
Candidate: 0.9.8.8-0ubuntu7.2
Version table:
   *** 0.9.8.8-0ubuntu7.2 0
  500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.9.8.8-0ubuntu7.1 0
  500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
   0.9.8.8-0ubuntu7 0
  500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 10:57:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-28 (1190 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.1.1 dev eth0 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to trusty on 2016-02-01 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-02-01T11:14:17.778018
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:6612): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.8) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540294/+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 1540294] [NEW] Network manager stopped working after some update

[Johan]

Public bug reported:

'sudo NetworkManager' gives:
(NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Key file does not have group 'connectivity'

To get network interface to work I have to do like this:
'sudo ip link set dev eth0 down'
'sudo dhclient eth0'


Ubuntu 14.04.3 LTS

'apt-cache policy network-manager':
network-manager:
  Installed: 0.9.8.8-0ubuntu7.2
  Candidate: 0.9.8.8-0ubuntu7.2
  Version table:
 *** 0.9.8.8-0ubuntu7.2 0
500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 0.9.8.8-0ubuntu7.1 0
500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
 0.9.8.8-0ubuntu7 0
500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.2
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  1 10:57:19 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-10-28 (1190 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.1.1 dev eth0 
 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2016-02-01 (0 days ago)
WifiSyslog:
 
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-02-01T11:14:17.778018
nmcli-con:
 Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
 ** (process:6612): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
 Error: nmcli (0.9.8.8) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 not running unknownunknown unknown   unknown 
unknownunknown unknown

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


** Tags: amd64 apport-bug trusty

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

Title:
  Network manager stopped working after some update

Status in network-manager package in Ubuntu:
  New

Bug description:
  'sudo NetworkManager' gives:
  (NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Key file does not have group 'connectivity'

  To get network interface to work I have to do like this:
  'sudo ip link set dev eth0 down'
  'sudo dhclient eth0'

  
  Ubuntu 14.04.3 LTS

  'apt-cache policy network-manager':
  network-manager:
Installed: 0.9.8.8-0ubuntu7.2
Candidate: 0.9.8.8-0ubuntu7.2
Version table:
   *** 0.9.8.8-0ubuntu7.2 0
  500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.9.8.8-0ubuntu7.1 0
  500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
   0.9.8.8-0ubuntu7 0
  500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 10:57:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-28 (1190 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.1.1 dev eth0 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   

[Touch-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9

To 

[Touch-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Here is the output of running xrandr just after logging inm only the
third time all resolutions are found:

johan@cdh7:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
   1920x1080 60.00*+
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
johan@cdh7:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
   1920x1080 60.00*+
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
johan@cdh7:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
   1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97
23.98  
   4096x2160 24.0023.98  
   3840x2160 30.00*   25.0024.0029.9723.98  
   1920x1080i60.0050.0059.94  
   1280x1024 60.02  
   1360x768  60.02  
   1152x864  59.97  
   1280x720  60.0050.0059.94  
   1024x768  60.00  
   800x600   60.32  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   640x480   60.0059.94  
   720x400   70.08  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
johan@cdh7:~$

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Mega

[Touch-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

The problem still occurs when using  a kernel from vivid (3.19.0-35).

If I login, the resolution is not correct. If I fix the resolution
everything is fine until I logout (no need to reboot). If I login again,
the resolution is bad again.

The available resolutions seem to change from time to time. Sometimes after 
login I get only 1920x1080 when doing a login, but it drops back to 1024x768 as 
well, sometimes rescaling to 1920x1080 if I wait a bit longer (the error messag 
already appeared at that time).
After logging in and waiting approximately 20 seconds I can go to display 
options and reset my display to the full resolution( 3840x2160).

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Updating the BIOS does not solve the problem. 
Output: of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V18.5
07/19/2014
Note that this is a regression when updating from utopic to wily.

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   input  

[Touch-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Thank you Anoop for referring to 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970
The workaround presented there works for me!

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  

[Touch-packages] [Bug 1515784] [NEW] UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Public bug reported:

Hi,

After updating from vivid to wily I noticed my screen no longer boots in
UHD resolution. I can set the resolution during the session, but on next
login it returns back to full hd. This is a regression from vivid, where
the resolution worked without problem.

This happens with different window managers.

In cinnamon I get an additional error, which is solved by removing
.config/monitors.xml

none of the selected modes were compatible with the possible modes:
Trying modes for CRTC 63
CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 64
CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 65
CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 66
CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

I'm willing to invest some time in trying to find a solution.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Thu Nov 12 22:42:35 2015
DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
InstallationDate: Installed on 2011-09-07 (1527 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
MachineType: MSI MS-7846
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
dmi.bios.date: 09/24/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V18.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-E35 (MS-7846)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7846
dmi.product.version: 3.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Nov 12 22:41:25 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputLogitech USB Receiver KEYBOARD, id 10
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug resolution ubuntu wily

** Description changed:

  Hi,
  
  After updating from vivid to wily I noticed my screen no longer boots in
- UHD resolution. I can set the resolution during the setting, but on next
+ UHD resolution. I can set the resolution during the session, but on next
  login it returns back to full hd. This is a regression from vivid, where
  the resolution worked without problem.
  
  This happens with 

[Touch-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Sorry for the delay, but I was able to generate a backtrace as described
by Dirk Seidel in comment #7 and comment #8. The backtrace is attached.

** Attachment added: "gdb-X.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998/+attachment/4512905/+files/gdb-X.txt

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  

[Touch-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Sorry, I can't generate a backtrace, same problem as Dirk: after
executing "continue" in gdb my entire system freezes, so I can't get
back to the X session.

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  

[Touch-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

I have exactly the same problem since upgrading to 15.10. For me
reproducable in LibreOffice 5.0.3.2 Calc by a right mouse click followed
by selecting "Format Cells...".

Xorg.0.log.old:
[   674.409] (EE) Backtrace:
[   674.409] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55d163d7262e]
[   674.409] (EE) 1: /usr/bin/X (0x55d163bbe000+0x1b8999) [0x55d163d76999]
[   674.409] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f82b6c33000+0x352f0) 
[0x7f82b6c682f0]
[   674.409] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x24f18) [0x7f82b302ef18]
[   674.409] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x26157) [0x7f82b3030157]
[   674.409] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x2b4b1) [0x7f82b30354b1]
[   674.409] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x804e4) [0x7f82b308a4e4]
[   674.409] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x80e2c) [0x7f82b308ae2c]
[   674.409] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x82e1a) [0x7f82b308ce1a]
[   674.409] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x4197c) [0x7f82b304b97c]
[   674.409] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x59906) [0x7f82b3063906]
[   674.409] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55d163c1b654]
[   674.409] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55d163d76274]
[   674.409] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55d163c21502]
[   674.409] (EE) 14: /usr/bin/X (0x55d163bbe000+0xf495a) [0x55d163cb295a]
[   674.409] (EE) 15: /usr/bin/X (0x55d163bbe000+0xf5ef5) [0x55d163cb3ef5]
[   674.409] (EE) 16: /usr/bin/X (0x55d163bbe000+0x5818f) [0x55d163c1618f]
[   674.409] (EE) 17: /usr/bin/X (0x55d163bbe000+0x5c34b) [0x55d163c1a34b]
[   674.409] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f82b6c53a40]
[   674.409] (EE) 19: /usr/bin/X (_start+0x29) [0x55d163c046c9]
[   674.409] (EE)
[   674.409] (EE) Segmentation fault at address 0x0
[   674.409] (EE)
Fatal server error:
[   674.409] (EE) Caught signal 11 (Segmentation fault). Server aborting

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  

[Touch-packages] [Bug 1241185] Re: Should provide policy based lifecycle exceptions

[Johan Guerreros]

i created a streaming music player https://bugs.launchpad.net/cloudmusic
and users have a bad experience because of this bug fix it please

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

Title:
  Should provide policy based lifecycle exceptions

Status in QtMir:
  New
Status in unity-mir:
  Triaged
Status in unity-mir package in Ubuntu:
  Triaged

Bug description:
  Currently, unity-mir has a hard coded exception to prevent music-app
  from suspending when losing focus.  We need a way to allow other apps
  to continue playback of music, etc.  For example, I've tried to help
  get panpipe (pandora app) usable on the phone, however without the
  ability to playback continuously it isn't useful.

  Perhaps lifecycle management exceptions based on apparmor-easyprof-
  ubuntu policy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1241185/+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 683170] Re: should be possible to display only windows from the current workspace in the launcher

[Johan]

I recently moved from Opensuse with KDE (opensuse user since 2002) to Ubuntu, 
and I must say, this is the thing that annoys me the most in Unity.  I also 
feel it should be an option.
In KDE it is a tick-box.  By default it shows everything, but you can set it to 
only show the windows in your current workspace.
This is great for separating different types of activities you are busy with.
KDE takes it one step further, and you can even define more activities, each 
with its own set of workspaces, where you can even set different backgrounds 
etc.
Other than this, I like Ubuntu a lot, and can see why it is so popular, so I 
will probably keep using it regardless.

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

Title:
  should be possible to display only windows from the current workspace
  in the launcher

Status in Ayatana Design:
  Won't Fix
Status in Unity:
  Won't Fix
Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: unity

  Since unity targets desktop users as well in natty it should be
  possible to set a configuration settings (could be a gsettings key)
  that lets the launcher display only applications on the current
  workspace. While that mode might not be useful for most users it's
  something technical users using workspaces for their different
  activities are used to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/683170/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Johan Potgieter]

I need to add that I have the latest versions of both libimobiledevice4
and libimobiledevice-utils and I still get this error. I dont get any
errors when connecting to any other wifi router or via ethernet cable.
Any suggestions would be appreciated.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Johan Potgieter]

I get this on Xubuntu 14.04 whenever I connect via wifi to my ios
personal hotspot. Often it does nothing more than ask to send the report
but other times it hangs after a few minutes. I have found it so
disruptive that I am unable to get any work done while connected to my
phone. I will try some of the remedies and hopefully it will sort out my
issue.

I wanted to add this note as I didn't see any mention of this happening
while connecting to a personal hotspot, as is the case with me.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1467588] Re: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. (proces

[Johan]

I have the same problem on Ubuntustudio
Platform:- x86_64
Distribution:-   Ubuntu 15.04
Desktop environment:-   Ubuntu Studio 

$ gstreamer-properties

Gtk-Message: GtkDialog mapped without a transient parent. This is
discouraged.

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

Title:
  Gtk-Message: GtkDialog mapped without a transient parent. This is
  discouraged. Gtk-Message: GtkDialog mapped without a transient parent.
  This is discouraged.  (process:17035): GLib-CRITICAL **:
  g_slice_set_config: assertion 'sys_page_size == 0' failed

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
  Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.

  (process:17035): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.1
  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
  Date: Mon Jun 22 16:56:16 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-20-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-21-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1854]
  InstallationDate: Installed on 2015-06-02 (20 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Hewlett-Packard HP 2000 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=9ac32e8e-1bbd-4aa9-8f25-2b79e4052d96 ro quiet splash
  SourcePackage: unity
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.3A
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1854
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 64.2A
  dmi.chassis.asset.tag: 5CG3400HTV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.3A:bd06/13/2013:svnHewlett-Packard:pnHP2000NotebookPC:pvr088F130059160:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 2000 Notebook PC
  dmi.product.version: 088F130059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Mon Jun 22 15:28:27 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 845 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1467588/+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 762349] Re: Difficult to distinguish which tab is selected

[Johan Boule]

echo '.notebook tab:active { background-color: @selected_bg_color; }' 
~/.config/gtk-3.0/gtk.css

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

Title:
  Difficult to distinguish which tab is selected

Status in Ayatana Design:
  New
Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: unity

  In tabbed interfaces such as in gnome-terminal under unity it is
  difficult to visually distinguish the selected tab from the unselected
  ones.

  In the attached screenshot, gnome-terminal has three tabs open, and
  the third one is selected.  If you look close you can see the text is
  slightly whiter than the other tabs, and the border is a little more
  prominent but to my old man eyes it's really hard to see it at a
  glance.

  Under metacity, the difference is more notable (or at least, the theme
  is different).

  My guess is this is a theme issue rather than unity, but I'm unsure.
  If it is just a theme issue please refile to the right project.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.8-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell]
  Date: Fri Apr 15 17:41:12 2011
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=C
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to natty on 2011-04-04 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/762349/+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 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

[Johan]

This thread recommends installing Debian :D

http://www.linuxforums.org/forum/ubuntu-linux/204157-libpam-systemd-
dependency-error-unable-install-any-packages-anymo.html

I don't even know whether I can safely restart my computer in this
state. Also, 14.04 LTS DOES NOT HAVE systemd. Where did you get the
bright idea to even put the package in the repository in the first
place? Are you paying your staff too little to fix this shit? If you are
not able to program, just STOP doing it.

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Triaged
Status in systemd source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note we are also suffering from a failure with update-initramfs, not sure of 
the root cause of that one but I thought I'd mention it in case they were 
related, since they both started happening about the same time, a couple weeks 
ago. (launchpad bug #1317602)
  It all worked ok after the inital releases of 14.04, so something to do with 
a package update since then.

  
  thanks,
  Hamish

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/+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 1325142] Re: failure to update libpam-systemd in 14.04 due to missing logind init script

[Johan]

Can you explain how you can fuck up an LTS release upgrade (not even a
major upgrade)? If you just had *one* test system running, you would
have been able to reproduce this. Amateurs...

apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libpam-systemd
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
19 not fully installed or removed.
Need to get 0 B/25.5 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 424067 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_204-5ubuntu20.11_amd64.deb ...
initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart-session/1001/2593: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: warning: subprocess old pre-removal script returned error exit status 100
dpkg: trying script from the new package instead ...
initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart-session/1001/2593: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.11_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 100
initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart-session/1001/2593: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.11_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  failure to update libpam-systemd in 14.04 due to missing logind init
  script

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Trusty:
  Triaged
Status in systemd source package in Utopic:
  Fix Released

Bug description:
  Hi,

  while running inside an i386 lubuntu 14.04 chroot, upgrading libpam-
  systemd to version 204-5ubuntu20.2 fails leaving dpkg in a broken
  state. 'apt-get -f install' from within the chroot will not fix it,
  but if the build is made bootable and put into a iso/VM you can
  recover that way in a live session.

  the problem seems to be the /var/lib/dpkg/info/libpam-systemd:i386.prerm 
script failing to bring down the logind daemon with 'invoke-rc.d systemd-logind 
stop', because invoke-rd.d is only looking for the /etc/init.d/ script (doesn't 
exist) and not /etc/init/systemd-logind.conf (does exist).
  ?

  
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be upgraded:
libpam-systemd
  1 upgraded, 0 newly installed, 0 to remove and 113 not upgraded.
  3 not fully installed or removed.
  Need to get 0 B/25.2 kB of archives.
  After this operation, 1024 B of additional disk space will be used.
  (Reading database ... 113986 files and directories currently installed.)
  Preparing to unpack .../libpam-systemd_204-5ubuntu20.2_i386.deb ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: warning: subprocess old pre-removal script returned error exit status 
100
  dpkg: trying script from the new package instead ...
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error processing archive 
/var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb (--unpack):
   subprocess new pre-removal script returned error exit status 100
  invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 100
  Errors were encountered while processing:
   /var/cache/apt/archives/libpam-systemd_204-5ubuntu20.2_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Our build logs available upon request, but the scripts to setup the chroot to 
recreate it are here:

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/build_chroot_nightly.sh

https://trac.osgeo.org/osgeo/browser/livedvd/gisvm/trunk/bin/inchroot_nightly.sh

  
  In a web-search I notice a few others running into the same bug,

  chatter on irc at [18:10], http://irclogs.ubuntu.com/2013/05/28
  /%23ubuntu-devel.txt

  someone else's build log:
  https://launchpad.net/~qutim/+archive/qutim/+build/6039800

  launchpad bug #1323575 seems to be a duplicate of this one.

  
  perhaps related to older launchpad bug #1305395 ?

  note 

[Touch-packages] [Bug 1323068] Re: -su: cannot set terminal process group (-1): Inappropriate ioctl for device

[Carl-Johan Sveningsson]

Umm, confirmed on  Ubuntu 14.04.1 LTS, recently updated from 12...
what's this about and how can I fix it? Seems harmless so far though.

cj@rocksteady:~$ sudo su minecraft -
[sudo] password for cj:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
minecraft@rocksteady:/mnt/data/home/cj$ script /dev/null
Script started, file is /dev/null
minecraft@rocksteady:/mnt/data/home/cj$ screen -dR

I realize I get some nutty memory leak before the other dude though.
I'll investigate.

/CJ

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

Title:
  -su: cannot set terminal process group (-1): Inappropriate ioctl for
  device

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  *Not* happening in Ubuntu 12.04.4 LTS

  ubuntu-precise-daily-amd64-server-20140522 (ami-c446aeac)

  ubuntu@ip-10-0-0-30:~$ sudo su -
  root@ip-10-0-0-30:~# su - ubuntu -
  ubuntu@ip-10-0-0-30:~$ 


  Happening in Ubuntu 14.04 LTS

  ubuntu-trusty-14.04-amd64-server-20140416.1 (ami-018c9568)

  ubuntu@build:~$ sudo su -
  root@build:~# su - ubuntu -
  -su: cannot set terminal process group (-1): Inappropriate ioctl for device
  -su: no job control in this shell
  ubuntu@build:~$ 


  ***
  test with zsh (ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/zsh)
  build% sudo su -
  root@build:~# su - ubuntu -
  build%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1323068/+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 1323068] Re: -su: cannot set terminal process group (-1): Inappropriate ioctl for device

[Carl-Johan Sveningsson]

Edit: that memory leak was due to
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186, which
fixed (by removing libpam-smbpass) leaves the original ioctl error :-/

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

Title:
  -su: cannot set terminal process group (-1): Inappropriate ioctl for
  device

Status in “bash” package in Ubuntu:
  Confirmed

Bug description:
  *Not* happening in Ubuntu 12.04.4 LTS

  ubuntu-precise-daily-amd64-server-20140522 (ami-c446aeac)

  ubuntu@ip-10-0-0-30:~$ sudo su -
  root@ip-10-0-0-30:~# su - ubuntu -
  ubuntu@ip-10-0-0-30:~$ 


  Happening in Ubuntu 14.04 LTS

  ubuntu-trusty-14.04-amd64-server-20140416.1 (ami-018c9568)

  ubuntu@build:~$ sudo su -
  root@build:~# su - ubuntu -
  -su: cannot set terminal process group (-1): Inappropriate ioctl for device
  -su: no job control in this shell
  ubuntu@build:~$ 


  ***
  test with zsh (ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/zsh)
  build% sudo su -
  root@build:~# su - ubuntu -
  build%

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1323068/+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 1358466] [NEW] Display settings seems to keep changing

[Johan Wysneus]

Public bug reported:

My display settings don’t seem to stay constant, e.g. sometimes
selections are highlighted in blue and sometimes in brown.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Aug 18 21:27:53 2014
DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
InstallationDate: Installed on 2014-05-24 (86 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=a83be82f-cfd0-44f3-b18a-2e3c7a637068 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-05-24 (86 days ago)
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01KY.M008.20100430.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P/N210P/N220P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P/N210P/N220P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Aug 18 16:41:23 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12336 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2

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


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

Title:
  Display settings seems to keep changing

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My display settings don’t seem to stay constant, e.g. sometimes
  selections are highlighted in blue and sometimes in brown.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 18 21:27:53 2014
  DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 

[Touch-packages] [Bug 1358467] [NEW] Time and date not always there

[Johan Wysneus]

Public bug reported:

The time and date is not always displayed in the top right corner after
boot up. Sometimes I have to reboot several times before time and date
is displayed correctly.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Aug 18 21:34:17 2014
DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
InstallationDate: Installed on 2014-05-24 (86 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=a83be82f-cfd0-44f3-b18a-2e3c7a637068 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-05-24 (86 days ago)
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01KY.M008.20100430.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P/N210P/N220P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P/N210P/N220P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Aug 18 16:41:23 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12336 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2

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


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

Title:
  Time and date not always there

Status in “xorg” package in Ubuntu:
  New

Bug description:
  The time and date is not always displayed in the top right corner
  after boot up. Sometimes I have to reboot several times before time
  and date is displayed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Aug 18 21:34:17 2014
  DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD.