[Desktop-packages] [Bug 1992187] Re: hplip not working after install in 22.04, python error

[Fabio M. Panico]

Could not understand how to implement the workaround suggested by
Alterbo Donato #4.  I would appreciate if you could clarify.

But uninstalling the package available at Ubuntu 22.04 repository and
installing the package downloaded from HP Developers
(https://developers.hp.com/hp-linux-imaging-and-printing/gethplip)
worked fine for me.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1992187

Title:
  hplip not working after install in 22.04, python error

Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  after upgrade from 20.04 to 22.04.1 (not a new installation): new 
installation of hplip
  >sudo apt install hplip hplip-gui

  Install completes without error.

  Using hplip, e.g.
  >hp-setup

  manual detection of wireless printer using IP works, printer is
  listed, but on 'next' -> process hangs (wait/termination suggested,
  wait does not help)

  alternative: (hplip installs a suite of programs)
  >hp-check(verifies installation and contact to printer, scanner
  produces normal output ending prematurely with error message:

    Saving output in log file: /home/glassel/hp-check.log

  HP Linux Imaging and Printing System (ver. 3.22.2)
  Dependency/Version Check Utility ver. 15.1

  Copyright (c) 2001-18 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Note: hp-check can be run in three modes:
  1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or
  .run) to determine if the proper dependencies are installed to successfully 
compile HPLIP.
  2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an
  already built HPLIP supplied tarball has the proper dependencies installed to 
successfully run.
  3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both
  compile- and run-time dependencies).

  Check types:
  a. EXTERNALDEP - External Dependencies
  b. GENERALDEP - General Dependencies (required both at compile and run time)
  c. COMPILEDEP - Compile time Dependencies
  d. [All are run-time checks]
  PYEXT SCANCONF QUEUES PERMISSION

  Status Types:
  OK
  MISSING   - Missing Dependency or Permission or Plug-in
  INCOMPAT  - Incompatible dependency-version or Plugin-version

  -Traceback (most recent call last):
    File "/usr/bin/hp-check", line 861, in 
  dep.core.init()
    File "/usr/share/hplip/installer/core_install.py", line 523, in init
  self.get_distro()
    File "/usr/share/hplip/installer/core_install.py", line 661, in get_distro
  if 'MX' in distro_release_name:
  NameError: name 'distro_release_name' is not defined

  further info:
  >apt-cache policy hplip
  hplip:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  > apt-cache policy hplip-gui
  hplip-gui:
    Installed: 3.22.2+dfsg0-1+klbkjammy
    Candidate: 3.22.2+dfsg0-1+klbkjammy
    Version table:
   *** 3.22.2+dfsg0-1+klbkjammy 500
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main amd64 Packages
  500 https://ppa.launchpadcontent.net/kelebek333/hplip/ubuntu 
jammy/main i386 Packages
  100 /var/lib/dpkg/status
   3.21.12+dfsg0-1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu jammy/universe i386 Packages

  ---

  I tried alternate ways to install hplip:
  hplip-3.22.6.run downloaded from hp

  this fails with an unmet dependency 'libcups2', but sudo apt install libcups2 
tells me it is
  installed (-dev version, too)

  A fresh install of cups did not help.

  Best regards ... Peter Glassel

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


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

[Desktop-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

[Fabio Augusto Miranda Martins]

Sorry for the late feedback, but sharing here:

AWS docs regarding best practices regarding cpu-starvation [1] do not
recommend disabling the irqbalance service. Quoting the doc:

> "Note: we do not recommend disabling irqbalance service. ENA driver
doesn’t provide affinity hints, and if device reset happens while
irqbalance is disabled, this might cause undesirable IRQ distribution
with multiple IRQs landing on the same CPU core."

Other customers that have hit issues with irqbalance were running very
specific workloads and were aware of the need to turn it off, so we
would prefer to keep irqbalance.

[1] https://github.com/amzn/amzn-
drivers/blob/master/kernel/linux/ena/ENA_Linux_Best_Practices.rst#cpu-
starvation

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in Ubuntu on IBM z Systems:
  Confirmed
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+subscriptions


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

[Desktop-packages] [Bug 2049061] [NEW] adsysctl update with a domain user fails if KRB5CCNAME is not set

[Fabio Augusto Miranda Martins]

Public bug reported:

In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable set,
running "adsysctl update" with a AD domain user will fail.

If you either export the variable with the path to the kerberos ticket
OR run the command "adsysctl update 
" it works.

The adsysctl command should fallback to the default location when
KRB5CCNAME is not defined or have a mechanism to query klist and find
the Kerberos tickets location.

Given that adsys can't find Kerberos tickets when `klist` does. It seems
like a feature parity issue, granted, an edge case.

Here is an example of a reproducer:

https://pastebin.ubuntu.com/p/FjyTWQChjM/

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: adsys 0.9.2~22.04.2
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
Uname: Linux 6.2.0-1014-aws x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: aws
CloudName: aws
CloudPlatform: ec2
CloudRegion: us-west-2
CloudSubPlatform: metadata (http://169.254.169.254)
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 11:39:06 2024
Ec2AMI: ami-00094f7041bb1b79d
Ec2AMIManifest: (unknown)
Ec2Architecture: x86_64
Ec2AvailabilityZone: us-west-2b
Ec2Imageid: ami-00094f7041bb1b79d
Ec2InstanceType: t3.large
Ec2Instancetype: t3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Ec2Region: us-west-2
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 sssd  2.6.3-1ubuntu3.2
 python3-samba 2:4.15.13+dfsg-0ubuntu1.5
SourcePackage: adsys
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
 [deleted]
modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]

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


** Tags: amd64 apport-bug ec2-images jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2049061

Title:
  adsysctl update with a domain user fails if KRB5CCNAME is not set

Status in adsys package in Ubuntu:
  New

Bug description:
  In an environment where /etc/krb5.conf sets "default_ccache_name =
  FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable
  set, running "adsysctl update" with a AD domain user will fail.

  If you either export the variable with the path to the kerberos ticket
  OR run the command "adsysctl update 
  " it works.

  The adsysctl command should fallback to the default location when
  KRB5CCNAME is not defined or have a mechanism to query klist and find
  the Kerberos tickets location.

  Given that adsys can't find Kerberos tickets when `klist` does. It
  seems like a feature parity issue, granted, an edge case.

  Here is an example of a reproducer:

  https://pastebin.ubuntu.com/p/FjyTWQChjM/

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: adsys 0.9.2~22.04.2
  ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-aws 6.2.16
  Uname: Linux 6.2.0-1014-aws x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: aws
  CloudName: aws
  CloudPlatform: ec2
  CloudRegion: us-west-2
  CloudSubPlatform: metadata (http://169.254.169.254)
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 11:39:06 2024
  Ec2AMI: ami-00094f7041bb1b79d
  Ec2AMIManifest: (unknown)
  Ec2Architecture: x86_64
  Ec2AvailabilityZone: us-west-2b
  Ec2Imageid: ami-00094f7041bb1b79d
  Ec2InstanceType: t3.large
  Ec2Instancetype: t3.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Ec2Region: us-west-2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   sssd  2.6.3-1ubuntu3.2
   python3-samba 2:4.15.13+dfsg-0ubuntu1.5
  SourcePackage: adsys
  UpgradeStatus: No upgrade log present (probably fresh install)
  
modified.conffile..etc.polkit-1.localauthority.conf.d.99-adsys-privilege-enforcement.conf:
 [deleted]
  modified.conffile..etc.sudoers.d.99-adsys-privilege-enforcement: [deleted]

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


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

[Desktop-packages] [Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales

[Fabio M. Panico]

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

I was on 18.04 and that was not an issue for me.

Using US intl. alt. keyboard I could always get ç (cedilha).

Now that I've upgrade to 23.04, this problem came back.

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

Title:
  libgtk2 immodules has cedilla disabled in en locales

Status in gnome-control-center:
  Confirmed
Status in GTK+:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Invalid
Status in gnome-control-center package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: libgtk2.0-0

  philsf@philsf-laptop:~$ lsb_release -rd
  Description:  Ubuntu 8.04
  Release:  8.04

  philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0
  libgtk2.0-0:
Installed: 2.12.9-3ubuntu3

  One can't use dead keys to input a c+cedilla in en_US (probably other
  en_* locales). I had this on Gutsy. Now in Hardy, I thought I should
  report, since it's annoying, and the fix is documented.

  Steps to reproduce: 
  - enable deadkeys
  - Open gnome-terminal (or firefox) and enter ' + c 

  What you should get: ç
  What you do get: ć 

  Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ):

  
  Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and 
include ":en" in the cedilla line

  6c6
  < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa" 
  ---
  > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/228077/+subscriptions


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

[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths

[Fabio Augusto Miranda Martins]

I've tested this in Lunar and Mantic.

TL;DR: In Lunar I hit the exact same issue as in Kinetic. After
installing adsys, I'm no longer able to login using a domain user. On
Mantic, it works fine and I'm able to login even after installing adsys.
On  the other hand, both Lunar and Mantic have the same issue with the
kerberos keytab / credential cache missing the service principal for
ldap/ec2amaz-hg2r0q8.fabio-rg@fabio-rg.com.

Details:

- Lunar: https://pastebin.ubuntu.com/p/mg7xXzM79N/
- Mantic: https://pastebin.ubuntu.com/p/bfGhnCdkjJ/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2020834

Title:
  Properly convert DNS names with '-' characters to valid dbus object
  paths

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Focal:
  Fix Committed
Status in adsys source package in Jammy:
  Fix Committed
Status in adsys source package in Kinetic:
  Confirmed

Bug description:
  [Impact]

  It is common that domain names contain the '-' character, as in "test-
  example.com", and adsys versions 0.9.2 and below cannot parse these
  correctly, leading to the error:

  ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error
  from server: error while updating policy: can't get policies for
  "test-example.com": failed to retrieve offline state from SSSD: dbus:
  invalid message: invalid path name

  when attempting to run adsys on a system attached to "test-
  example.com" Active Directory.

  Currently, 0.9.2 only changes '.' into '_2e', and this would change
  all special characters to use their hexadecimal representations,
  notably '-' becomes '_2d'.

  There is plans from Foundations + Desktop to SRU 0.12.0 back to at
  least Jammy, documented in bug 2020682 which depends on golang 1.20 to
  be included in the jammy archive, documented in bug 2020658. However,
  this fixup is required with high priority while the 0.12.0 release is
  being prepared, and the SRU will hopefully bridge a few weeks between
  SRU release to release of 0.12.0.

  [Testcase]

  Start a Windows Server VM, 2022 will be fine, and create an Active
  Directory with the domain "test-example.com".

  Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the
  domain.

  Try to enable adsys:

  $ sudo apt install adsys
  $ adsysctl update
  ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from 
server: error while updating policy: can't get policies for "test-example.com": 
failed to retrieve offline state from SSSD: dbus: invalid message: invalid path 
name

  There are test packages in the below ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test

  If you install the test package and retry to join the domain, it will
  succeed.

  [Where problems could occur]

  We are changing how domain names are being parsed and converted to
  valid dbus object path names. Domain names can only contain [0-9],
  [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its
  hexadecimal representation of '_2d', there should be limited scope of
  regressions.

  However, if a regression were to occur, then users may not be able to
  use adsys to apply group policy restrictions, and could run into
  issues accessing files, shares and networks.

  As mentioned in the impact section, this will be a temporary fix to
  0.9.2 while 0.12.0 is being prepared to be released into the archive,
  which contains the full fix and testsuite coverage. This SRU should
  hopefully be short lived.

  [Other Info]

  The upstream merge request is:

  https://github.com/ubuntu/adsys/pull/498

  This was fixed in 0.10.0 by the commit:

  commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4
  Author: Didier Roche 
  Date:   Tue Nov 15 11:10:51 2022 +0100
  Subject: Fix special characters in domain conversion to dbus object path
  Link: 
https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4

  Now, there were some additional commits that added testsuite coverage:

  commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540
  Author: Didier Roche 
  Date:   Tue Nov 15 11:13:03 2022 +0100
  Subject: Refresh golden file now that we properly handle the path.
  Link: 
https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540

  commit 4571e39cd724a973270a586d2b18f653f0007de9
  Author: Didier Roche 
  Date:   Tue Nov 15 11:14:35 2022 +0100
  Subject: Use a better case to assert on ServerURL() failure being ignored.
  Link: 
https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9

  commit fdca6e462c26e1cbecdb8386f43515c1947d423d
  Author: Didier Roche 
  Date:   Tue Nov 15 11:16:21 2022 +0100
  Subject: Add a separate case for special characters in domain name.
  Link: 
https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d

  These comm

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

I just tested Ubuntu 22.04 and I can confirm it fixes the issue.

First, used 22.04 with the current mutter version available in jammy-
updates:

user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 
gir1.2-mutter-10
[sudo] password for user1: 
mutter-common:
  Installed: 42.9-0ubuntu1
  Candidate: 42.9-0ubuntu1
  Version table:
 *** 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
libmutter-10-0:
  Installed: 42.9-0ubuntu1
  Candidate: 42.9-0ubuntu1
  Version table:
 *** 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
gir1.2-mutter-10:
  Installed: 42.9-0ubuntu1
  Candidate: 42.9-0ubuntu1
  Version table:
 *** 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

And I do hit the error when trying to revert after changing the scale:

Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use linear monitor 
configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
Jul 24 17:03:38 U-20CG3JVH1ALS3 gnome-shell[3048]: Xlib:  extension "DPMS" 
missing on display ":1".

Then, I upgraded to package from -proposed:

user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 
gir1.2-mutter-10
[sudo] password for user1: 
mutter-common:
  Installed: 42.9-0ubuntu4
  Candidate: 42.9-0ubuntu4
  Version table:
 *** 42.9-0ubuntu4 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
libmutter-10-0:
  Installed: 42.9-0ubuntu4
  Candidate: 42.9-0ubuntu4
  Version table:
 *** 42.9-0ubuntu4 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
gir1.2-mutter-10:
  Installed: 42.9-0ubuntu4
  Candidate: 42.9-0ubuntu4
  Version table:
 *** 42.9-0ubuntu4 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

And now the error is no longer logged and I can successfully revert:


Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: 
Scalig CRTC 59 at 1.00 failed
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on 
crtc 61 to 1.00, error id 2
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: 
Scalig CRTC 61 at 1.00 failed
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on 
crtc 63 to 1.00, error id 2
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: 
Scalig CRTC 63 at 1.00 failed
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on 
crtc 65 to 1.00, error id 2
Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: 
Scalig CRTC 65 at 1.00 failed

 Scalig CRTC 65 at 1.00 failed

(The errors above can be ignored for now as their are a known problem
with Xdcv, which is further explained in comment #16)

Marking as verification-done


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Hi,

Thank you for the package in -proposed.

I just tested Ubuntu 22.04 and I can confirm it fixes the issue.

First, used 22.04 with the current mutter version available in jammy-
updates:

user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0 
gir1.2-mutter-10
mutter-common:
  Installed: 42.9-0ubuntu1
  Candidate: 42.9-0ubuntu1
  Version table:
 *** 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
libmutter-10-0:
  Installed: 42.9-0ubuntu1
  Candidate: 42.9-0ubuntu1
  Version table:
 *** 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
gir1.2-mutter-10:
  Installed: 42.9-0ubuntu1
  Candidate: 42.9-0ubuntu1
  Version table:
 *** 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

And I do hit the error when trying to revert after changing the scale:

Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Failed to use linear monitor 
configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
Jul 18 09:40:39 U-2RVWD6LKXR3GE gnome-shell[3186]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
Jul 18 09:40:40 U-2RVWD6LKXR3GE gnome-shell[3186]: Xlib:  extension "DPMS" 
missing on display ":1".


Then, I upgraded to package from -proposed:

user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0 
gir1.2-mutter-10
[sudo] password for user0: 
mutter-common:
  Installed: 42.9-0ubuntu3
  Candidate: 42.9-0ubuntu3
  Version table:
 *** 42.9-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
libmutter-10-0:
  Installed: 42.9-0ubuntu3
  Candidate: 42.9-0ubuntu3
  Version table:
 *** 42.9-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
gir1.2-mutter-10:
  Installed: 42.9-0ubuntu3
  Candidate: 42.9-0ubuntu3
  Version table:
 *** 42.9-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 42.9-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

And now the error is no longer logged and I can successfully revert:

Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: 
Scalig CRTC 59 at 1.00 failed
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on 
crtc 61 to 1.00, error id 2
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: 
Scalig CRTC 61 at 1.00 failed
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on 
crtc 63 to 1.00, error id 2
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: 
Scalig CRTC 63 at 1.00 failed
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Impossible to set scaling on 
crtc 65 to 1.00, error id 2
Jul 18 09:44:35 U-2RVWD6LKXR3GE gnome-shell[3199]: Window manager warning: 
Scalig CRTC 65 at 1.00 failed

(The errors above can be ignored for now as their are a known problem
with Xdcv, which is further explained in comment #16)

Marking as verification-done

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

OK, thanks for the information. The one I had tested was 42.9-0ubuntu2
with Jammy. I'll test again when 42.9-0ubuntu3 is available in
-proposed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Kinetic:
  Fix Released
Status in mutter source package in Lunar:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  When running GNOME on the Xdcv X11 server, changing the display scale
  in Settings and then clicking 'Revert Settings' instead of 'Keep
  Changes' does not revert the settings.

  [ Test Plan ]

  Very complicated; see comment #8.

  [ Where problems could occur ]

  In the list of available graphics modes in Xorg sessions on jammy only
  (an equivalent fix already exists in later Ubuntu releases).

  [ Original Description ]

   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change the 
Scale in the Gnome Display settings, if you click on a different scale (i.e. 
changing from 100% to 200%) and hitting apply, it will bring up a prompt asking 
if you want to keep or revert the changes and there will be a timer of 20 
seconds. If you try to revert the changes (either by letting the timer expire 
or by clicking the "revert" button), we will hit one of the following two 
behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

I've tested the mutter packages from -proposed in an AWS Workspace:

https://pastebin.ubuntu.com/p/9Yvgfs7yZr/

And I'm able to successfully change the scale to 200% and then revert
the setting.

The following messages are logged when changing to 200%:

https://pastebin.ubuntu.com/p/Y5QdXSqcsW/

And then when you try to revert:

https://pastebin.ubuntu.com/p/cYP7JKryx9/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed
Status in mutter source package in Kinetic:
  Fix Released
Status in mutter source package in Lunar:
  Fix Released
Status in mutter source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  When running GNOME on the Xdcv X11 server, changing the display scale
  in Settings and then clicking 'Revert Settings' instead of 'Keep
  Changes' does not revert the settings.

  [ Test Plan ]

  Very complicated; see comment #8.

  [ Where problems could occur ]

  In the list of available graphics modes in Xorg sessions on jammy only
  (an equivalent fix already exists in later Ubuntu releases).

  [ Original Description ]

   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change the 
Scale in the Gnome Display settings, if you click on a different scale (i.e. 
changing from 100% to 200%) and hitting apply, it will bring up a prompt asking 
if you want to keep or revert the changes and there will be a timer of 20 
seconds. If you try to revert the changes (either by letting the timer expire 
or by clicking the "revert" button), we will hit one of the following two 
behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 

[Desktop-packages] [Bug 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths

[Fabio Augusto Miranda Martins]

I've tested Focal and it works well with adsys from -proposed:

https://pastebin.ubuntu.com/p/6RBcBpZq2T/

And also does Jammy:

https://pastebin.ubuntu.com/p/pqvgSkkmcQ/

I'm having issues with Kinetic. When I install adsys, I'm no longer able
to login to the instance, I'm getting the following errors when trying
to login:

https://pastebin.ubuntu.com/p/hh9SHB3ZXx/

It works if I purge the adsys package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2020834

Title:
  Properly convert DNS names with '-' characters to valid dbus object
  paths

Status in adsys package in Ubuntu:
  Fix Released
Status in adsys source package in Focal:
  Fix Committed
Status in adsys source package in Jammy:
  Fix Committed
Status in adsys source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  It is common that domain names contain the '-' character, as in "test-
  example.com", and adsys versions 0.9.2 and below cannot parse these
  correctly, leading to the error:

  ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error
  from server: error while updating policy: can't get policies for
  "test-example.com": failed to retrieve offline state from SSSD: dbus:
  invalid message: invalid path name

  when attempting to run adsys on a system attached to "test-
  example.com" Active Directory.

  Currently, 0.9.2 only changes '.' into '_2e', and this would change
  all special characters to use their hexadecimal representations,
  notably '-' becomes '_2d'.

  There is plans from Foundations + Desktop to SRU 0.12.0 back to at
  least Jammy, documented in bug 2020682 which depends on golang 1.20 to
  be included in the jammy archive, documented in bug 2020658. However,
  this fixup is required with high priority while the 0.12.0 release is
  being prepared, and the SRU will hopefully bridge a few weeks between
  SRU release to release of 0.12.0.

  [Testcase]

  Start a Windows Server VM, 2022 will be fine, and create an Active
  Directory with the domain "test-example.com".

  Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the
  domain.

  Try to enable adsys:

  $ sudo apt install adsys
  $ adsysctl update
  ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from 
server: error while updating policy: can't get policies for "test-example.com": 
failed to retrieve offline state from SSSD: dbus: invalid message: invalid path 
name

  There are test packages in the below ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test

  If you install the test package and retry to join the domain, it will
  succeed.

  [Where problems could occur]

  We are changing how domain names are being parsed and converted to
  valid dbus object path names. Domain names can only contain [0-9],
  [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its
  hexadecimal representation of '_2d', there should be limited scope of
  regressions.

  However, if a regression were to occur, then users may not be able to
  use adsys to apply group policy restrictions, and could run into
  issues accessing files, shares and networks.

  As mentioned in the impact section, this will be a temporary fix to
  0.9.2 while 0.12.0 is being prepared to be released into the archive,
  which contains the full fix and testsuite coverage. This SRU should
  hopefully be short lived.

  [Other Info]

  The upstream merge request is:

  https://github.com/ubuntu/adsys/pull/498

  This was fixed in 0.10.0 by the commit:

  commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4
  Author: Didier Roche 
  Date:   Tue Nov 15 11:10:51 2022 +0100
  Subject: Fix special characters in domain conversion to dbus object path
  Link: 
https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4

  Now, there were some additional commits that added testsuite coverage:

  commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540
  Author: Didier Roche 
  Date:   Tue Nov 15 11:13:03 2022 +0100
  Subject: Refresh golden file now that we properly handle the path.
  Link: 
https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540

  commit 4571e39cd724a973270a586d2b18f653f0007de9
  Author: Didier Roche 
  Date:   Tue Nov 15 11:14:35 2022 +0100
  Subject: Use a better case to assert on ServerURL() failure being ignored.
  Link: 
https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9

  commit fdca6e462c26e1cbecdb8386f43515c1947d423d
  Author: Didier Roche 
  Date:   Tue Nov 15 11:16:21 2022 +0100
  Subject: Add a separate case for special characters in domain name.
  Link: 
https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d

  These commits are not compatible with 0.9.2 due to testsuite harnesses
  and frameworks and test data files not being added until 0.10.0, and
  adding such commits is numerous, and contains too 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Thank you very much for the great job narrowing this, Daniel!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".

  
  I'm unable to reproduce the problem if I manually install ubuntu-desktop and 
use the Nice DCV Server (as used by Workspaces) by following the steps from 
(using the xorg-x11-drv-dummy):

  https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-
  installing-linux.html

  One relevant difference is that Workspaces uses a custom X11 server
  /usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the
  following process being started:

  /usr/bin/Xdcv -output 800x600+0+0 -output 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Daniel,

Regarding 3 (the blank screen issue when enabling a monitor): I can
confirm that the issue happens when you're using Workspaces client
5.9.0.4129 (Windows client version) and no longer happens (even with
Xdcv + Gnome) in 5.10.0.4196.

And, by checking the client release notes [1]:

"Resolved black screen issue when using multiple monitors with Ubuntu
WorkSpaces"

[1] https://docs.aws.amazon.com/workspaces/latest/userguide/amazon-
workspaces-windows-client.html#windows-release-notes

Regards,
Fabio Martins

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS"

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Ignacio, if Xdcv ever wants to support Fractional Scaling, I believe you
will also need to look at the details shared by Daniel in his comment
#16. Otherwise, even if we fix the zero hz issue, you will be able to
change/revert scale, but will also need to make sure fractional scaling
is disabled.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".

  
  I'm unable to reproduce the problem if I manually install ubuntu-desktop and 
use the Nice DCV Server (as used by Workspaces) by following the steps from 
(using the xorg-x11-drv-dummy):

  https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-
  

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Daniel,

A few items to make sure I'm on the same page:

1. So, IIUC, you're saying that the "final fix" should be the vv5
package, which contains the fix to the zero hz bug (loosening mutter to
accept zero-Hz, as this is the bogus refresh rate being reported by
Xdcv) + the caveat for AWS to either fix Xdcv or never try to enable
Fractional scaling in the instance (details in your comment#16), is that
so?

2. Regarding your comment on bug 1857392 and bug 2007742 being present,
iiuc they do not have a noticeable impact (other than spamming the log).

3. Also, I need to mention that I went ahead and tried once more the vv5
package on a AWS Workspace, and I can no longer reproduce the blank
screen. Now I see these logs [1] and the scale does get reverted from
200% to 100%.

https://pastebin.ubuntu.com/p/JpVsjbQzsQ/

4. If 1 above is correct, then where (if anywhere) we are going to
investigate the situation where vv5 causes the other monitors to get
automatically enabled?

Regards,
Fabio Martins

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Hi Daniel,

Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.

Also, I tested "xrandr --output VNC-output-1 --auto" to enable another
monitor using Budgie and Xfce (I believe none of them use mutter), and I
can't reproduce the "blank screen". It doesn't really do anything, but
also doesn't reproduce the blank screen issue.

This is what I see in Xfce:

https://pastebin.ubuntu.com/p/BNs9KJqbHz/

And Budgie:

https://pastebin.ubuntu.com/p/pKTGzJb8bN/

My previous suggestion (patch with zero hz fix + no fractional scaling)
was because I thought vv1 was also exposed to the issue you mentioned on
comment #19 ("fractional scaling patch is trying to implement the revert
using fractional scaling"), but I guess not, and it still fails with the
"Invalid mode 800x600 (-nan)" errors, which is the zero hz issue, and
led us to vv2 and then vv4.

So, the current situation is that either with vv4 (zero hz patch + no
fractional scaling) OR vv5 with fractional scaling disabled (zero hz
patch included) we get to the situation where the extra monitors are
automatically enabled and the resolution is changed to 800x600:

https://pastebin.ubuntu.com/p/k822YMHM5v/

And IIUC this is what needs to be investigated next.

And no need to apologize if not able to respond this daily, completely
understandable and you're already doing a lot for this bug. Thank you
very very much for that!

I'll also be OoO for the next couple of days, back on Monday anyway.

Cheers,
Fabio Martins

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (2

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

> Try logging into a non-GNOME Xorg session on Workspaces
> if you can. Then use the 'xrandr' command to set a mode
> to turn on one of the unused virtual monitors. If that
> causes the DCV client to go blank then we have proven 
> it's not mutter's fault.

I did test that with a Cinnamon session and confirmed it. I basically
did:

xrandr --output VNC-output-1 --auto

and it immediately goes to a blank screen


OK, so saying out loud my understanding of this issue so far, so as to check 
it's correct. The problems are:

- Fractional scaling is supported in RandR 1.3 or newer
- Xdcv reports its RandR version is 1.6, but when you try to use fraction 
scaling it errors (error id 2)
- The corruption bug 1924689 may be caused by the fractional scaling patch (or 
a side effect of the "error id 2"?)
- Xdcv is reporting a bogus refresh rate
- There's a "config history" issue identified by Mustafa in comments #26 and #30

What we've been doing now to try to narrow it down is:

A - The "Zero Hz" fix is basically loosening mutter to accept zero-Hz, as this 
is the bogus refresh rate being reported by Xdcv
B - vv4 fix = no fractional scaling + "zero Hz" fix
C - vv5 fix = re-adds fractional scaling + "zero Hz" fix

And out of it, we've confirmed in local VM / Workspaces tests that

1 - Without fractional scaling patch (vv4) / with fractional scaling disabled, 
we can't reproduce the "Failed to restore previous configuration: Invalid mode" 
/ "Impossible to set scaling on crtc" errors
2 - The "Zero Hz" fix causes a side-effect of enabling the unused monitors (tbd 
if this is a bug)
2a. If you manually disable 3 monitors (keeping only one) and then try to apply 
/ revert 200% scale, it errors [1] and sets resolution back to 800x600
3 - When enabling unused monitors in Workspaces, we get a blank screen (which 
I've confirmed through cinnamon / xrandr that it must be a problem with the 
Workspaces client when enabling a monitor)

For the "zero Hz" problem, if I understand correctly, it is a bogus
issue without a noticeable impact in usage. On the other hand,  due to
the "zero Hz" fix introducing problems 2 and 2a above, I'm skeptical on
validating that avoiding fractional scaling fixes our issue (item 1
above).

If the "zero hz" issue is really just bogus, should we try a "vv6" build
completely disabling fractional scaling for the Xdcv use case (on apply
and revert), but not including the "zero hz" fix? This way we would be
able to validate item 1 above (even if we see the zero hz bogus
messages, which we can ignore for now). If this succeeds, we can
investigate the item 3 above separately, so we can then re-introduce the
"zero hz" fix.


[1] https://pastebin.ubuntu.com/p/Xtyfvb3CV2/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Although Mustafa says he's not well-versed, he's way smarter than me :)
So his comment#26 seems to be much more relevant than what I have to
say, but I'd like to reply to Daniel's comment#24/25 anyway:

I saw the details you mentioned on comment #16, and I also have
fractional scaling turned off. By "having it off" I'm assuming this [1]
is enough, right?

Also, I noticed that by previous pasteboard wasn't too clear in showing
the problem when I use 42.5-0ubuntu1vv5. I want  to clarify that I get a
screen as if I had 3 monitors side by side, but all in the same "client
monitor". If you try to maximize the application, it picks one of the
"screens" and maximizes to it, as we can see here [2].

Even without changing the fractional scale or scale setting, just by
having the 42.5-0ubuntu1vv5 packages installed, I get this "triple
monitor in 1" situation when I boot my VM. I had to reinstall the
original packages from our archives in order to fix this. Also, I just
want to make sure you're aware that these are the *mutter* packages that
I have installed:

ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter
ii  gir1.2-mutter-10:amd64  42.5-0ubuntu1   amd64GObject 
introspection data for Mutter
ii  libmutter-10-0:amd6442.5-0ubuntu1   amd64window manager 
library from the Mutter window manager
ii  mutter-common   42.5-0ubuntu1   all  shared files for 
the Mutter window manager


i.e. Just want to make clear that I don't have the "mutter" package installed, 
but the ones above.

Back to your comment, iiuc, the "Impossible to set scaling on crtc 65 to
1.00, error id 2" means that we're trying to use some incomplete
RandR implementation in Xdcv. Isn't it the fractional scaling, that was
effectively removed from your 42.5-0ubuntu1vv5 package? In this case,
doesn't the errors showing up means that we're still trying to use
something that isn't properly implemented in Xdcv?

Just for my own information, what's the difference between the vv5 and
vv4 builds?

Tested with vv4 in a VM:

ubuntu@jammy-dcv:~$ sudo dpkg -l | grep mutter
ii  gir1.2-mutter-10:amd64 42.5-0ubuntu1vv4  amd64GObject 
introspection data for Mutter
ii  libmutter-10-0:amd64   42.5-0ubuntu1vv4  amd64window manager 
library from the Mutter window manager
ii  mutter-common  42.5-0ubuntu1vv4  all  shared files for 
the Mutter window manager


As soon as I installed it in my VM, I got that "triple monitor" situation 
again, and then I realized it's really just what you had described, that it 
automatically enables these other monitors. I can disable them and get back to 
1 single monitor. With vv4, I can apply the scale 200% [3] and then revert it, 
but then it changes my resolution to 800x600.

After realizing that, I went back to the vv5 package and re-tested and I
notice it's the same behavior as in vv4. After installing it
automatically enables all 4 monitors, I have to manually disable them
and keep just 1. Then I test the scale to 200% + revert and it does
revert, but also changes my resolution to 800x600.

I can't really test that in Workspaces, because when it enables the
extra monitors, I'm no longer able to access the Workspace with the AWS
Workspaces client. If I try to change the scale in Workspaces, I believe
it tries to enable the other monitors, and then all I get is a blank
screen.

And here's the output of "xrandr --verbose" from the VM [5] and the
Workspace [6]


[1] https://pasteboard.co/qEbvvwijUW2F.png
[2] https://pasteboard.co/K9Oh9nZ8wqNk.png
[3] https://pastebin.ubuntu.com/p/xkcFScZv5c/
[4] https://pastebin.ubuntu.com/p/mVwWt4Rzsr/
[5] https://pastebin.ubuntu.com/p/JC4PXwdv55/
[6] https://pastebin.ubuntu.com/p/S5bXz975Nn/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Hi Daniel,

Thanks again.

Tested 42.5-0ubuntu1vv5

When I apply the 200% scale:

https://pastebin.ubuntu.com/p/MfS9vpT6KB/

When I revert it:

https://pastebin.ubuntu.com/p/SHtvrXyPkY/

And then I get this situation (possibly due to what you mentioned on the
settings app attempting to enable the 4 monitors):

https://pasteboard.co/kLUbb5XWlwAQ.png

The tests above were in a qemu VM in my laptop + DCV. I also tested it
in an AWS Workspace and I believe the situation is similar. When I
change scale to 200%:

https://pastebin.ubuntu.com/p/DgkB3rngvj/

When I revert it:

https://pastebin.ubuntu.com/p/H4nJC4MmKW/

And the screen in the Workspaces client gets all blank and there's no
place to click. Even if I try to resize the client screen (which would
force Xdcv to change the resolution) I can't get back to the workspace.
Only way to fix it is to close and reopen the client.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  In Progress

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

I was getting some inconsistent and confusing results on my tests, so I
decided to start from scratch with a fresh VM (qemu) and also a fresh
Workspace (AWS).

In a freshly installed Jammy VM (on qemu, not AWS), out of the box we
have factional scaling disabled, so I tried changing scale to 200% and I
do hit the error (but the scale DOES change):

https://pastebin.ubuntu.com/p/yVwnmqbTTJ/

When I try to revert, I hit the error again and gnome freezes:

https://pastebin.ubuntu.com/p/nYpqJDmr5x/

I then upgraded the packages in the PPA:

sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade

Rebooted the VM

When I still hit the error both when trying to change the scale to 200%
(still does change it, though):

https://pastebin.ubuntu.com/p/V7MmKCjc4W/

And also when trying to revert it (gnome freezes):

https://pastebin.ubuntu.com/p/dbWZFQGr9t/

Package versions:

https://pastebin.ubuntu.com/p/c4WsgPVnxr/

Also did the same tests with a fresh Workspace:

Tested the very same thing in a Workspace:

Out of the box fractional scaling is disabled, so I tried changing scale
to 200% and I hit the error (but it does change):

https://pastebin.ubuntu.com/p/gSZ5rfm7vF/

When I try to revert, I hit the error and then it causes the problem
reported in https://launchpad.net/bugs/1924689:

https://pastebin.ubuntu.com/p/NHY62YvxCG/

(So both Workspaces and local VM hit the same problem, but when
reverting Workspaces will hit LP#1924689 and the local VM will freeze
gnome)

I then rebooted the Workspace without upgrading any package and tried
the same steps again, and I still have the same problem.

I then upgraded the packages in the PPA:

sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade

Rebooted the Workspace, and I still hit the error both when trying to
change the scale to 200% (still does change it, though):

https://pastebin.ubuntu.com/p/977wzx6sxW/

And when I try to revert:

https://pastebin.ubuntu.com/p/D2VZv2J7QV/

Packages:

https://pastebin.ubuntu.com/p/mDKy4wWyWZ/


So, unless I'm missing something, apparently the same problem happens with 
fractional scaling disabled and also with the packages from the PPA.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  New

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 

[Desktop-packages] [Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails

[Fabio Augusto Miranda Martins]

Thanks for the investigation Daniel.

Indeed my inability to change the scale with the first patch was due to
low resolution in my client machine.

Interesting enough, I tried reproducing this in a Local VM with Xdcv
(with just regular mutter packages, straight from our archives, no PPA),
and I'm unable to reproduce the problem when I disable fractional
scaling. I'm able to change to 200% and then revert properly.

Given that I'm unable to reproduce there, I went back to an AWS
Workspace and installed your new 42.5-0ubuntu1vv2 package and I'm still
able to reproduce the problem when reverting it:

May 31 20:17:42 U-3JQHCWI1WR5QW geoclue[2660]: Service not used for 60 seconds. 
Shutting down..
May 31 20:17:42 U-3JQHCWI1WR5QW systemd[1]: geoclue.service: Deactivated 
successfully.
May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Failed to use linear monitor 
configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
May 31 20:17:43 U-3JQHCWI1WR5QW gnome-shell[3188]: Xlib:  extension "DPMS" 
missing on display ":1".
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-0' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-1' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-2' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-3' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-0' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-1' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-2' does not exist
May 31 20:17:43 U-3JQHCWI1WR5QW gsd-color[3358]: could not find device: 
property match 'XRANDR_name'='VNC-output-3' does not exist

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Xdcv: Changing display scale setting and reverting it fails

Status in mutter package in Ubuntu:
  New

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 

[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages

[Fabio Augusto Miranda Martins]

I also tested Daniel's mutter package with:

sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade 

And rebooted the Workspace just in case.

I know Mustafa mentioned he was still able to reproduce the issue. In my
case, I wasn't but on the other hand, I can't do the action that would
allow me to reproduce it.

When I go to display settings, I don't have an option to change the
scale, but I do have the option to enable "Fractional Scaling", but if I
enable it, I don't have an apply button to enable it, so this never gets
enabled and doesn't get to a situation where I can change/revert the
scale to see if I would be able to reproduce the issue or not.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Changing display scale setting and reverting it, causes gnome-shell to
  error with "Failed to restore previous configuration" and other error
  messages

Status in mutter package in Ubuntu:
  New

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 

[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages

[Fabio Augusto Miranda Martins]

Hi Daniel,

I'm not with the SEG team and I would need assistance from someone
building that and providing the debs or a ppa. I've also subscribed
Mustafa, from SEG, to this bug, as he's assisting me investigating this
issue.

Regards,
Fabio Martins

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782

Title:
  Changing display scale setting and reverting it, causes gnome-shell to
  error with "Failed to restore previous configuration" and other error
  messages

Status in mutter package in Ubuntu:
  New

Bug description:
  In Amazon Workspaces running Ubuntu 22.04, when attempting to change
  the Scale in the Gnome Display settings, if you click on a different
  scale (i.e. changing from 100% to 200%) and hitting apply, it will
  bring up a prompt asking if you want to keep or revert the changes and
  there will be a timer of 20 seconds. If you try to revert the changes
  (either by letting the timer expire or by clicking the "revert"
  button), we will hit one of the following two behaviors:

  1 - The setting won't revert and will keep scaled

  2 - gnome-shell will show some error messages in syslog and the
  display will be "corrupted", where the only window you are able to
  click is the display setting and if you try to drag it, it will leave
  a "blur" throughout the window (per discussions, this seems to be
  https://launchpad.net/bugs/1924689)

  For both situations, changing the display resolution (i.e. going into
  and out of full screen in the workspaces client) will fix the issue

  When hitting situation 1, syslog shows:

  May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
  previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
  'unknown unknown'

  
  When hitting situation 2, syslog shows:

  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
  May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: 
monitor is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

  Sometimes the stack trace isn't shown, but the symptom is the same:

  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored 
monitor configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown 
unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
  May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling 
on crtc 59 to 1.00, error id 2
  May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".

  
  I'm unable to reproduce the problem if I manually install ubuntu-desktop and 
use the Nice DCV Server (as used by Workspaces) by following the st

[Desktop-packages] [Bug 2020782] Re: Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages

[Fabio Augusto Miranda Martins]

Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell
42.5-0ubuntu1:


fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common
[sudo] password for fabiomirmar: 
mutter-common:
  Installed: 42.5-0ubuntu1
  Candidate: 42.5-0ubuntu1
  Version table:
 *** 42.5-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages
fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy gnome-shell
gnome-shell:
  Installed: 42.5-0ubuntu1
  Candidate: 42.5-0ubuntu1
  Version table:
 *** 42.5-0ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
100 /var/lib/dpkg/status
 42.0-2ubuntu1 500
500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages


And I have the same issue.

When I apply the scale change I see:

May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: 
vte-spawn-11c0b6cb-a094-4eee-9cbf-7a694348f00a.scope: Consumed 1.272s CPU time.
May 25 13:30:21 U-1JSKZM4R9U78P systemd[2514]: gnome-terminal-server.service: 
Consumed 1.231s CPU time.
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Impossible to set scaling on 
crtc 59 to 0.615385, error id 2
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Scalig CRTC 59 at 0.615385 failed
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib:  extension "DPMS" 
missing on display ":1".
May 25 13:30:25 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor, 
using scale 1
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Xlib:  extension "DPMS" 
missing on display ":1".
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Missing logical monitor, 
using scale 1
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Spurious 
clutter_actor_allocate called for actor 
0x55a6ef3a4ba0/[:0x55a6ef3a4ba0]
 which isn't a descendent of the stage!
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-0' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-1' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-2' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-3' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-0' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-1' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-2' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gsd-color[2980]: could not find device: 
property match 'XRANDR_name'='VNC-output-3' does not exist
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views 
actor [:0x55a6ee826330] is on because it needs an 
allocation.
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views 
actor [:0x55a6f04896e0] is on because it needs an 
allocation.
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views 
actor [:0x55a6f048ca30] is on because it needs an 
allocation.
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
May 25 13:30:26 U-1JSKZM4R9U78P gnome-shell[2862]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: Can't update stage views 
actor [:0x55a6ee826330] is on because it needs an 
allocation.
May 25 13:30:27 U-1JSKZM4R9U78P gnome-shell[2862]: 

[Desktop-packages] [Bug 2020782] [NEW] Changing display scale setting and reverting it, causes gnome-shell to error with "Failed to restore previous configuration" and other error messages

[Fabio Augusto Miranda Martins]

Public bug reported:

In Amazon Workspaces running Ubuntu 22.04, when attempting to change the
Scale in the Gnome Display settings, if you click on a different scale
(i.e. changing from 100% to 200%) and hitting apply, it will bring up a
prompt asking if you want to keep or revert the changes and there will
be a timer of 20 seconds. If you try to revert the changes (either by
letting the timer expire or by clicking the "revert" button), we will
hit one of the following two behaviors:

1 - The setting won't revert and will keep scaled

2 - gnome-shell will show some error messages in syslog and the display
will be "corrupted", where the only window you are able to click is the
display setting and if you try to drag it, it will leave a "blur"
throughout the window (per discussions, this seems to be
https://launchpad.net/bugs/1924689)

For both situations, changing the display resolution (i.e. going into
and out of full screen in the workspaces client) will fix the issue

When hitting situation 1, syslog shows:

May 17 17:33:10 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore
previous configuration: Invalid mode 1920x1080 (19.958942) for monitor
'unknown unknown'


When hitting situation 2, syslog shows:

May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor 
configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: Object St.Label 
(0x557090d07de0), has been already disposed — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: == Stack trace for context 
0x557090bee180 ==
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #0   557093f00e68 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:1349 
(2cdac32b2e20 @ 105)
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #1   557093f00dd8 i   
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/dash.js:42 
(2cdac32a5d80 @ 27)
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: #2   557093f00d58 i   
resource:///org/gnome/shell/ui/dash.js:545 (20c3e0d20970 @ 24)
May 17 17:31:24 U-1AZMIM8SIPZ6I gnome-shell[3030]: JS ERROR: TypeError: monitor 
is 
null#012_updateWorkAreaBox@resource:///org/gnome/shell/ui/overviewControls.js:58:26#012_init/<@resource:///org/gnome/shell/ui/overviewControls.js:51:45

Sometimes the stack trace isn't shown, but the symptom is the same:

May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to restore previous 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use stored monitor 
configuration: Invalid mode 1920x984 (19.895834) for monitor 'unknown unknown'
May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use linear monitor 
configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Failed to use fallback 
monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown'
May 17 18:31:39 U-1AZMIM8SIPZ6I gnome-shell[3030]: Impossible to set scaling on 
crtc 59 to 1.00, error id 2
May 17 18:31:40 U-1AZMIM8SIPZ6I gnome-shell[3030]: Xlib:  extension "DPMS" 
missing on display ":1".


I'm unable to reproduce the problem if I manually install ubuntu-desktop and 
use the Nice DCV Server (as used by Workspaces) by following the steps from 
(using the xorg-x11-drv-dummy):

https://docs.aws.amazon.com/dcv/latest/adminguide/setting-up-installing-
linux.html

One relevant difference is that Workspaces uses a custom X11 server
/usr/bin/Xdcv, instead of /usr/lib/xorg/Xorg, and they have the
following process being started:

/usr/bin/Xdcv -output 800x600+0+0 -output 800x600+800+0 -output
800x600+1600+0 -output 800x600+2400+0 -enabledoutputs 1 vt2 -displayfd 3
-auth /run/user/541001128/gdm/Xauthority -nolisten tcp -background none
-noreset -keeptty -novtswitch -verbose 3

I'm also unable to reproduce the problem using xrdp + Xorg.

While discussing this with the desktop crew, it was mentioned that we see the 
same problems in
Xorg. And to a much lesser extent some issues in Wayland too when changing 
scales.

[Desktop-packages] [Bug 2019751] Re: Shell startup animation may not complete on early resolution changes

[Fabio Augusto Miranda Martins]

@Daniel,

My understanding is that bug 2019751 is the same as bug 1989170, but
public. Since the fix was not released to Jammy, bug 2019751 aims to
address that (although your question might be targeted to Lunar, since I
see bug 1989170 was released to Kinetic.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2019751

Title:
  Shell startup animation may not complete on early resolution changes

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-ubuntu-dock source package in Jammy:
  Fix Committed
Status in gnome-shell-extension-ubuntu-dock source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell startup animation may not complete during startup, leading
  to a non-functional GNOME shell because the workarea could be clipped
  or input events are ignored.

  [ Test case ]

  1. Run this script: https://gitlab.gnome.org/3v1n0/gnome-shell/-/snippets/5749
  2. It's expected to launch a gnome-shell nested instance and perform monitor 
changes
  3. The shell should animate to the final state and everything should be 
usable:
     - Clicking in shell widgets should work
     - No area is hidden or clipped

  [ Regression potential ]

  GNOME Shell may not start properly, input events are ignored and/or
  the desktop area is clipped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2019751/+subscriptions


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

[Desktop-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04

[fabio andres pino gutierrez]

My error is quite annoying to, already the hotspot work on the SO, the
activated the wifi and detect the wifi, but when my cellphone connected
to the hotspot assigned a public ip, for been exactly assigned by
default the DHCP the ip 10.42.0.189 with a mask subred 255.255.255.0,
but the computer than is working like service DHCP already had
192.168.1.56, i'm undestand if this hotspot is working like a bridge
appliance, but, this time didnt is the case, because the default router
has the 192.168.1.254, so the subred mask of the segment of the red is
from 192.168.1.0 - 192.168.1.255 wtf, why assign me a public IP,
jajajaj, i will send the evidence.

** Attachment added: "hotspot problem2.png"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5644473/+files/hotspot%20problem2.png

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

Title:
  My machine has Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+subscriptions


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

[Desktop-packages] [Bug 1988676] [NEW] package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: il sottoprocesso nuovo pacchetto firefox script pre-installation ha restituito lo stato

[Fabio Martini]

Public bug reported:

package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade:
il sottoprocesso nuovo pacchetto firefox script pre-installation ha
restituito lo stato di errore 1

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 104.0+build3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
Uname: Linux 5.4.0-125-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fabio  1727 F pulseaudio
BuildID: 20220818191623
CasperMD5CheckResult: unknown
Channel: Unavailable
Date: Sun Sep  4 15:38:58 2022
ErrorMessage: il sottoprocesso nuovo pacchetto firefox script pre-installation 
ha restituito lo stato di errore 1
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-12-24 (2445 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IpRoute:
 default via 192.168.1.201 dev wlan0 proto dhcp metric 600 
 169.254.0.0/16 dev wlan0 scope link metric 1000 
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.100 metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.7
RunningIncompatibleAddons: False
SourcePackage: firefox
Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: 
il sottoprocesso nuovo pacchetto firefox script pre-installation ha restituito 
lo stato di errore 1
UpgradeStatus: Upgraded to jammy on 2022-09-04 (0 days ago)
dmi.bios.date: 07/27/2011
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: BA52_CP
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd07/27/2011:svnAcer:pnTravelMate5744Z:pvrV1.04:rvnAcer:rnBA52_CP:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: TravelMate 5744Z
dmi.product.sku: Calpella_CRB
dmi.product.version: V1.04
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-package jammy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1988676

Title:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: il sottoprocesso nuovo pacchetto firefox script pre-
  installation ha restituito lo stato di errore 1

Status in firefox package in Ubuntu:
  New

Bug description:
  package firefox 104.0+build3-0ubuntu0.20.04.1 failed to
  install/upgrade: il sottoprocesso nuovo pacchetto firefox script pre-
  installation ha restituito lo stato di errore 1

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: firefox 104.0+build3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-125.141-generic 5.4.195
  Uname: Linux 5.4.0-125-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fabio  1727 F pulseaudio
  BuildID: 20220818191623
  CasperMD5CheckResult: unknown
  Channel: Unavailable
  Date: Sun Sep  4 15:38:58 2022
  ErrorMessage: il sottoprocesso nuovo pacchetto firefox script 
pre-installation ha restituito lo stato di errore 1
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-12-24 (2445 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 192.168.1.201 dev wlan0 proto dhcp metric 600 
   169.254.0.0/16 dev wlan0 scope link metric 1000 
   192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.100 metric 600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.7
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to 
install/upgrade: il sottoprocesso nuovo pacchetto firefox script 

[Desktop-packages] [Bug 1931312] [NEW] i386 version of libpipewire-0.3 for Ubuntu Focal 20.04

[Fabio C. Barrionuevo]

Public bug reported:


Hi, I updated the packages today and one of them was Steam.
When trying to open Steam, it is reported missing to install 32-bit version of 
libpipewire-0.3.so.0


luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam 
Running Steam on focal 20.04 64-bit
STEAM_RUNTIME is disabled by the user
Error: You are missing the following 32-bit libraries, and Steam may not run:
libpipewire-0.3.so.0

I did a brief search and saw that there is no 32bit version of pipewire
0.3 release.

https://packages.ubuntu.com/search?arch=i386=pipewire


luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386
[sudo] senha para luzfcb: 
Lendo listas de pacotes... Pronto
Construindo árvore de dependências   
Lendo informação de estado... Pronto
E: Impossível encontrar o pacote libpipewire-0.3-0:i386
E: Couldn't find any package by glob 'libpipewire-0.3-0'
E: Não foi possível encontrar o pacote através da expressão regular 
'libpipewire-0.3-0'


Are there any plans to fix this and make life for the few people still
trying to play games using Linux less difficult?

Yes or no, thanks for your hard work.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/1931312

Title:
  i386 version of libpipewire-0.3 for Ubuntu Focal 20.04

Status in pipewire package in Ubuntu:
  New

Bug description:
  
  Hi, I updated the packages today and one of them was Steam.
  When trying to open Steam, it is reported missing to install 32-bit version 
of libpipewire-0.3.so.0

  
  luzfcb@fabio-pc:~ $ STEAM_RUNTIME=0 steam 
  Running Steam on focal 20.04 64-bit
  STEAM_RUNTIME is disabled by the user
  Error: You are missing the following 32-bit libraries, and Steam may not run:
  libpipewire-0.3.so.0

  I did a brief search and saw that there is no 32bit version of
  pipewire 0.3 release.

  https://packages.ubuntu.com/search?arch=i386=pipewire

  
  luzfcb@fabio-pc:~ $ sudo apt-get install libpipewire-0.3-0:i386
  [sudo] senha para luzfcb: 
  Lendo listas de pacotes... Pronto
  Construindo árvore de dependências   
  Lendo informação de estado... Pronto
  E: Impossível encontrar o pacote libpipewire-0.3-0:i386
  E: Couldn't find any package by glob 'libpipewire-0.3-0'
  E: Não foi possível encontrar o pacote através da expressão regular 
'libpipewire-0.3-0'


  
  Are there any plans to fix this and make life for the few people still trying 
to play games using Linux less difficult?

  Yes or no, thanks for your hard work.

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

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

[Desktop-packages] [Bug 1918874] Re: Application icons superposed to open windows

[Fabio Colombo]

Same problem here!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1918874

Title:
  Application icons superposed to open windows

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Click on 'Show Applications' the icons of the applications appear but the 
windows of the applications does not disappear so the icons are hidden.
  problem happens with both sessions Xorg and Wayland after last updates
  see attached picture

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nautilus 1:3.38.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 12 07:36:41 2021
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'initial-size' b'(1288, 663)'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2021-02-28 (11 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210228)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince3.39.2-1
   file-roller   3.38.0-1
   nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
   nautilus-share0.7.3-2ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918874/+subscriptions

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

[Desktop-packages] [Bug 1903593] [NEW] rhythmbox-metadata assert failure: rhythmbox-metadata: ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.

[Fabio Marconi]

Public bug reported:

Nothing to add, the player worked correctly.
B.R. & thanks

ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: rhythmbox 3.4.4-1ubuntu3.2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu51
Architecture: amd64
AssertionMessage: rhythmbox-metadata: ../nouveau/pushbuf.c:723: 
nouveau_pushbuf_data: Assertion `kref' failed.
CasperMD5CheckResult: skip
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov  9 22:04:33 2020
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
InstallationDate: Installed on 2016-10-30 (1471 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
Signal: 6
SourcePackage: rhythmbox
StacktraceTop:
 __assert_fail_base (fmt=0x7fdf7311a458 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7fdf61e47068 "kref", file=0x7fdf61e47052 
"../nouveau/pushbuf.c", line=723, function=) at assert.c:92
 __GI___assert_fail (assertion=0x7fdf61e47068 "kref", file=0x7fdf61e47052 
"../nouveau/pushbuf.c", line=723, function=0x7fdf61e471a0 
"nouveau_pushbuf_data") at assert.c:101
 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 nouveau_pushbuf_data () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
 () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
Title: rhythmbox-metadata assert failure: rhythmbox-metadata: 
../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo
separator:

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


** Tags: amd64 apport-crash hirsute third-party-packages

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1903593/+attachment/5432754/+files/CoreDump.gz

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1903593

Title:
  rhythmbox-metadata assert failure: rhythmbox-metadata:
  ../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref'
  failed.

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Nothing to add, the player worked correctly.
  B.R. & thanks

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: rhythmbox 3.4.4-1ubuntu3.2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  AssertionMessage: rhythmbox-metadata: ../nouveau/pushbuf.c:723: 
nouveau_pushbuf_data: Assertion `kref' failed.
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 22:04:33 2020
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2016-10-30 (1471 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  Signal: 6
  SourcePackage: rhythmbox
  StacktraceTop:
   __assert_fail_base (fmt=0x7fdf7311a458 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7fdf61e47068 "kref", file=0x7fdf61e47052 
"../nouveau/pushbuf.c", line=723, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7fdf61e47068 "kref", file=0x7fdf61e47052 
"../nouveau/pushbuf.c", line=723, function=0x7fdf61e471a0 
"nouveau_pushbuf_data") at assert.c:101
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   nouveau_pushbuf_data () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
   () at /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
  Title: rhythmbox-metadata assert failure: rhythmbox-metadata: 
../nouveau/pushbuf.c:723: nouveau_pushbuf_data: Assertion `kref' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd netdev plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

[Fabio B]

Ubuntu 19.10, mutter-3.34.3-1ubuntu1~19.10.1 and still crash sometimes
with IntelliJ

--
apr 17 16:40:45 delphy gnome-shell[2612]: **
apr 17 16:40:45 delphy gnome-shell[2612]: 
mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should 
be NULL
apr 17 16:40:45 delphy gnome-shell[2612]: Bail out! 
mutter:ERROR:../src/core/window.c:4851:set_workspace_state: 'workspace' should 
be NULL
apr 17 16:40:45 delphy gnome-shell[2612]: GNOME Shell crashed with signal 6
apr 17 16:40:45 delphy gnome-shell[2612]: == Stack trace for context 
0x56084b40d3b0 ==
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
apr 17 16:40:45 delphy systemd[2342]: gnome-shell-x11.service: Scheduled 
restart job, restart counter is at 1.
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session 
(session: ubuntu).
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session (session: 
ubuntu).
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME X11 Session.
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME X11 Session.
apr 17 16:40:45 delphy systemd[2342]: Stopped target GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Stopping GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Stopped GNOME Shell on X11.
apr 17 16:40:45 delphy systemd[2342]: Starting GNOME Shell on X11...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1845281

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [ Description ]

  Intellij and other java apps can cause GNOME shell to crash

  [ Test case ]

  1) Run this test case:
 https://gitlab.gnome.org/3v1n0/mutter/snippets/956
  2) Windows should appear and close correctly while
 Gnome shell must not crash

  [ Regression potential ]

  Parent-child relationship on some windows might be broken.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

[Fabio B]

I recently reported the issue to jetbrains  
https://youtrack.jetbrains.com/issue/IDEA-233737
(with a screencast)

All packages: mutter, mutter-common, gir1.2-mutter-5 and libmutter-5-50
are at version 3.34.1+git20191107-1ubuntu1~19.10.1


journalctl log 
---
feb 25 12:20:29 delphy gnome-shell[9183]: **
feb 25 12:20:29 delphy gnome-shell[9183]: 
mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should 
not be reached
feb 25 12:20:29 delphy gnome-shell[9183]: Bail out! 
mutter:ERROR:../src/core/window.c:5513:meta_window_get_workspaces: code should 
not be reached
feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 
0x55de5b4f1540 ==
feb 25 12:20:29 delphy gnome-shell[9183]: GNOME Shell crashed with signal 6
feb 25 12:20:29 delphy gnome-shell[9183]: == Stack trace for context 
0x55de5b4f1540 ==


Also attached the gdb.txt file produced with these instructions
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-shell

Hope it helps


** Attachment added: "gdb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845281/+attachment/5330843/+files/gdb.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1845281

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  Intellij and other java apps can cause GNOME shell to crash

  [ Test case ]

  1) Run this test case:
 https://gitlab.gnome.org/3v1n0/mutter/snippets/956
  2) Windows should appear and close correctly while
 Gnome shell must not crash

  [ Regression potential ]

  Parent-child relationship on some windows might be broken.

  ---

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1789656] Re: Complete system freeze happening sporadically when running chromium

[Fabio Rotondo]

This is the journal just before freeze. It does not seem to be referred
to Chrome

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+attachment/5311974/+files/journal.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1789656

Title:
  Complete system freeze happening sporadically when running chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This context is in syslog before complete system freeze, repeated a few times 
(attached file).
  Aug 29 15:43:41  chromium-browser.desktop[5003]: 
[5003:5017:0829/154341.786374:ERROR:service_manager_context.cc(250)] Attempting 
to run unsupported native service: 
/usr/lib/chromium-browser/chrome_renderer.service

  It happens sporadic but only after the start of chromium-browser loading 
about 20 tabs and moving from one to another.
  Complete system freeze, no console, no REISUB works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 68.0.3440.106-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLUoHABUUAQOANR54Cu6Ro1RMmSYPUFS/74BxT4EAgUCBgJUAlQ+zAAEBAjqAGHE4LUBYLEUAEyshAAAeAjqA0HI4LUAQLEWAEyshAAAe/QAYSxpRFwAKICAgICAg/ABTTUZYMjQ5MEhECiAgAYoCAxzxS5MEBRQDEhAfICEiIwkHB2cDDAAQALgtAR2A0HIcFiAQLCWAEyshAACeAR2AGHEcFiBYLCUAEyshAACeAR0AclHQHiBuKFUAEyshAAAejArQkCBAMSAMQFUAEyshAAAejArQiiDgLRAQPpYAEyshAAAezg==
   modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 
1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 
1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 
720x576 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Aug 29 16:01:30 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2012-02-05 (2397 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  Load-Avg-1min: 2.18
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (15 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-01-25T17:18:56.251795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions

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

[Desktop-packages] [Bug 1789656] Re: Complete system freeze happening sporadically when running chromium

[Fabio Rotondo]

Hello,

I am using X11, as for:

fabio@fabio-office:~$ env | grep x11
XDG_SESSION_TYPE=x11


I don't know how to use Wayland, but I will look how to.

I will post the journal as soon as the problem appears again

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1789656

Title:
  Complete system freeze happening sporadically when running chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This context is in syslog before complete system freeze, repeated a few times 
(attached file).
  Aug 29 15:43:41  chromium-browser.desktop[5003]: 
[5003:5017:0829/154341.786374:ERROR:service_manager_context.cc(250)] Attempting 
to run unsupported native service: 
/usr/lib/chromium-browser/chrome_renderer.service

  It happens sporadic but only after the start of chromium-browser loading 
about 20 tabs and moving from one to another.
  Complete system freeze, no console, no REISUB works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 68.0.3440.106-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLUoHABUUAQOANR54Cu6Ro1RMmSYPUFS/74BxT4EAgUCBgJUAlQ+zAAEBAjqAGHE4LUBYLEUAEyshAAAeAjqA0HI4LUAQLEWAEyshAAAe/QAYSxpRFwAKICAgICAg/ABTTUZYMjQ5MEhECiAgAYoCAxzxS5MEBRQDEhAfICEiIwkHB2cDDAAQALgtAR2A0HIcFiAQLCWAEyshAACeAR2AGHEcFiBYLCUAEyshAACeAR0AclHQHiBuKFUAEyshAAAejArQkCBAMSAMQFUAEyshAAAejArQiiDgLRAQPpYAEyshAAAezg==
   modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 
1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 
1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 
720x576 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Aug 29 16:01:30 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2012-02-05 (2397 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  Load-Avg-1min: 2.18
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (15 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-01-25T17:18:56.251795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions

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

[Desktop-packages] [Bug 1789656] Re: Complete system freeze happening sporadically when running chromium

[Fabio Rotondo]

UPDATE: it seems just to freeze mouse and keyboard input, since I am
able to see desktop notifications and other stuff going on.

UPDATE2: it does not only affect the Chromium browser, but also Electron
(or similar) applications that use the same technology.

Since the system doesn't actually freeze completely, I could be able to dump 
information / logs.
Please, give me some command lines you want me to run on my system to further 
investigate.

Thanks

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1789656

Title:
  Complete system freeze happening sporadically when running chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This context is in syslog before complete system freeze, repeated a few times 
(attached file).
  Aug 29 15:43:41  chromium-browser.desktop[5003]: 
[5003:5017:0829/154341.786374:ERROR:service_manager_context.cc(250)] Attempting 
to run unsupported native service: 
/usr/lib/chromium-browser/chrome_renderer.service

  It happens sporadic but only after the start of chromium-browser loading 
about 20 tabs and moving from one to another.
  Complete system freeze, no console, no REISUB works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 68.0.3440.106-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLUoHABUUAQOANR54Cu6Ro1RMmSYPUFS/74BxT4EAgUCBgJUAlQ+zAAEBAjqAGHE4LUBYLEUAEyshAAAeAjqA0HI4LUAQLEWAEyshAAAe/QAYSxpRFwAKICAgICAg/ABTTUZYMjQ5MEhECiAgAYoCAxzxS5MEBRQDEhAfICEiIwkHB2cDDAAQALgtAR2A0HIcFiAQLCWAEyshAACeAR2AGHEcFiBYLCUAEyshAACeAR0AclHQHiBuKFUAEyshAAAejArQkCBAMSAMQFUAEyshAAAejArQiiDgLRAQPpYAEyshAAAezg==
   modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 
1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 
1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 
720x576 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Aug 29 16:01:30 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2012-02-05 (2397 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  Load-Avg-1min: 2.18
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (15 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-01-25T17:18:56.251795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions

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

[Desktop-packages] [Bug 1789656] Re: Complete system freeze happening sporadically when running chromium

[Fabio Rotondo]

It happens to me too. Same problem. Related to Chrome or Chromium.

I can add that, if I use ssh to the freezed machine, SSH is active and 
everything works.
I tried to restart X11, even with "runlevel 3" and then "runlevel 5", but once 
it has frozen, the GUI never comes up again.

If I use Firefox, it never happens.
I suspect it has something to do with NVidia drivers, but I don't know how to 
check.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1789656

Title:
  Complete system freeze happening sporadically when running chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  This context is in syslog before complete system freeze, repeated a few times 
(attached file).
  Aug 29 15:43:41  chromium-browser.desktop[5003]: 
[5003:5017:0829/154341.786374:ERROR:service_manager_context.cc(250)] Attempting 
to run unsupported native service: 
/usr/lib/chromium-browser/chrome_renderer.service

  It happens sporadic but only after the start of chromium-browser loading 
about 20 tabs and moving from one to another.
  Complete system freeze, no console, no REISUB works.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 68.0.3440.106-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DVI-I-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLUoHABUUAQOANR54Cu6Ro1RMmSYPUFS/74BxT4EAgUCBgJUAlQ+zAAEBAjqAGHE4LUBYLEUAEyshAAAeAjqA0HI4LUAQLEWAEyshAAAe/QAYSxpRFwAKICAgICAg/ABTTUZYMjQ5MEhECiAgAYoCAxzxS5MEBRQDEhAfICEiIwkHB2cDDAAQALgtAR2A0HIcFiAQLCWAEyshAACeAR2AGHEcFiBYLCUAEyshAACeAR0AclHQHiBuKFUAEyshAAAejArQkCBAMSAMQFUAEyshAAAejArQiiDgLRAQPpYAEyshAAAezg==
   modes: 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 
1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1280x1024 
1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 
1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 
720x576 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  Date: Wed Aug 29 16:01:30 2018
  Desktop-Session:
   'ubuntu'
   '/etc/xdg/xdg-ubuntu:/etc/xdg'
   
'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2012-02-05 (2397 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  Load-Avg-1min: 2.18
  Load-Processes-Running-Percent:   0.1%
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=b3e26f93-613b-48e8-96d7-9c8854fe670c ro
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (15 days ago)
  dmi.bios.date: 07/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0305
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QLD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0305:bd07/30/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.default.chromium-browser: [deleted]
  mtime.conffile..etc.chromium-browser.default: 2017-01-25T17:18:56.251795

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1789656/+subscriptions

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

[Desktop-packages] [Bug 1797734] Re: slow calculator startup

[Fabio Olaechea]

Hi, Ubuntu 18.04.3 LTS running on SSD laptop with 16GB ram and i7 cpu
here, i can confirm that startup was very slow and was solved doing:

$ snap remove gnome-calculator
$ sudo apt-get install gnome-calculator


Before the "snap remove" startup time was as minimum 10 secs, now is 1 sec or 
less.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1797734

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions

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

[Desktop-packages] [Bug 1815444] [NEW] Xorg crashed with SIGABRT in OsAbort()

[Fabio Tenorio de Carvalho]

Public bug reported:

Release: Ubuntu 16.04 LTS

Package: xserver-xorg-core-hwe-16.04 2:1.19.6-1ubuntu4.1~16.04.2

Archicteture:amd64

/usr/lib/xorg/Xorg:6:/lib/x86_64-linux-
gnu/libc-2.23.so+35428:/lib/x86_64-linux-
gnu/libc-2.23.so+3702a:/usr/lib/xorg/Xorg+1b891a:/usr/lib/xorg/Xorg+1be513:/usr/lib/xorg/Xorg+1bf32d:/usr/lib/xorgXorg+8b260/usr/lib/xorg/Xorg+990e0:/usr/lib/xorg/Xorg+582d6:/lib/x86_64
-linux-gnu/libc-2.23.so+20830:/usr/lib/xorg/Xorg+42449

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Mon Feb 11 08:44:05 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 broadcom-sta, 6.30.223.271, 4.15.0-42-generic, x86_64: installed
 broadcom-sta, 6.30.223.271, 4.15.0-43-generic, x86_64: installed
 broadcom-sta, 6.30.223.271, 4.15.0-45-generic, x86_64: installed
 broadcom-sta, 6.30.223.271, 4.4.0-142-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Haswell-ULT Integrated Graphics Controller 
[104d:90be]
InstallationDate: Installed on 2017-06-26 (594 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Sony Corporation SVF15325CBB
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=10884db2-b372-43f6-9549-0e72c5ee1169 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R1080DB
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR1080DB:bd09/19/2014:svnSonyCorporation:pnSVF15325CBB:pvrC800KAXM:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: SVF1532
dmi.product.name: SVF15325CBB
dmi.product.version: C800KAXM
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Feb 11 08:23:25 2019
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1815444

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg package in Ubuntu:
  New

Bug description:
  Release: Ubuntu 16.04 LTS

  Package: xserver-xorg-core-hwe-16.04 2:1.19.6-1ubuntu4.1~16.04.2

  Archicteture:amd64

  /usr/lib/xorg/Xorg:6:/lib/x86_64-linux-
  gnu/libc-2.23.so+35428:/lib/x86_64-linux-
  
gnu/libc-2.23.so+3702a:/usr/lib/xorg/Xorg+1b891a:/usr/lib/xorg/Xorg+1be513:/usr/lib/xorg/Xorg+1bf32d:/usr/lib/xorgXorg+8b260/usr/lib/xorg/Xorg+990e0:/usr/lib/xorg/Xorg+582d6:/lib/x86_64
  -linux-gnu/libc-2.23.so+20830:/usr/lib/xorg/Xorg+42449

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Feb 11 08:44:05 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  

[Desktop-packages] [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed

[Fabio Lallo]

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

Linux Mint 19.1 Cinnamon

Plugin installation failed
error: Python gobject/dbus may be not installed
error: Plug-in install failed.


**

$ hp-plugin

HP Linux Imaging and Printing System (ver. 3.19.1)
Plugin Download and Install Utility ver. 2.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

HP Linux Imaging and Printing System (ver. 3.19.1)
Plugin Download and Install Utility ver. 2.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Checking for network connection...
Downloading plug-in from:
Receiving digital keys: /usr/bin/gpg --homedir /home/fabio/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
Creating directory plugin_tmp
Verifying archive integrity... All good.
Uncompressing HPLIP 3.19.1 Plugin Self Extracting 
Archive..

HP Linux Imaging and Printing System (ver. 3.19.1)
Plugin Installer ver. 3.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Plug-in version: 3.19.1
Installed HPLIP version: 3.19.1
Number of files to install: 64

Plugin installation failed
error: Python gobject/dbus may be not installed
error: Plug-in install failed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1430561

Title:
  hp-plugin crashes with error: Python gobject/dbus may be not installed

Status in HPLIP:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure an HP LaserJet P1102w, when running hp-plugin
  I get errors and can not proceed:

  nessita@miro:~$ hp-plugin
  error: Unable to locate models.dat file

  HP Linux Imaging and Printing System (ver. 3.15.2)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
  Error importing HPLIP modules.  Is HPLIP installed?
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.
  nessita@miro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 19:23:41 2015
  InstallationDate: Installed on 2014-11-30 (100 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet
  MachineType: LENOVO 3249CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET61WW (1.31 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed

[Fabio Lallo]

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

~$ hp-plugin

HP Linux Imaging and Printing System (ver. 3.19.1)
Plugin Download and Install Utility ver. 2.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.


HP Linux Imaging and Printing System (ver. 3.19.1)
Plugin Download and Install Utility ver. 2.1

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Checking for network connection...
Downloading plug-in from: 
Receiving digital keys: /usr/bin/gpg --homedir /home/fabio/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 
0x4ABA2F66DBD5A95894910E0673D770CDA59047B9
Creating directory plugin_tmp
Verifying archive integrity... All good.
Uncompressing HPLIP 3.19.1 Plugin Self Extracting 
Archive..

HP Linux Imaging and Printing System (ver. 3.19.1)
Plugin Installer ver. 3.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Plug-in version: 3.19.1
Installed HPLIP version: 3.19.1
Number of files to install: 64

Plugin installation failed
error: Python gobject/dbus may be not installed
error: Plug-in install failed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1430561

Title:
  hp-plugin crashes with error: Python gobject/dbus may be not installed

Status in HPLIP:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure an HP LaserJet P1102w, when running hp-plugin
  I get errors and can not proceed:

  nessita@miro:~$ hp-plugin
  error: Unable to locate models.dat file

  HP Linux Imaging and Printing System (ver. 3.15.2)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
  Error importing HPLIP modules.  Is HPLIP installed?
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.
  nessita@miro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 19:23:41 2015
  InstallationDate: Installed on 2014-11-30 (100 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet
  MachineType: LENOVO 3249CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET61WW (1.31 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1790482] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] No sound at all

[fabio di bartolo]

Public bug reported:

i can't listen any Sound from the speakers. 
if i use headphones i don't have any problem to hear music or anything, but 
without i can't neither choose the option speaker.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dibo   1094 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  1 18:13:45 2018
InstallationDate: Installed on 2018-09-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   dibo   1094 F...m pulseaudio
 /dev/snd/controlC0:  dibo   1094 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [X550CC, Realtek ALC270, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i can't listen any Sound from the speakers. 
  if i use headphones i don't have any problem to hear music or anything, but 
without i can't neither choose the option speaker.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dibo   1094 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  1 18:13:45 2018
  InstallationDate: Installed on 2018-09-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dibo   1094 F...m pulseaudio
   /dev/snd/controlC0:  dibo   1094 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1790328] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] No sound at all

[fabio di bartolo]

Public bug reported:

Hello, i tried to reinstall Ubuntu thinking was something easy to solve but 
nothing. the problem persist.
in also i did different try with different guides but i didnt manage since im 
new on linux and tried to fix it without result.

the problem is: 
 only headphones are showed on the list of outpout and the speakers, after 
using the command alsamixer -D hw:PCH i tried to increase the volume on the 
speakers, but nothing is changing.

what do i suppose to do

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dibo   1094 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep  1 18:13:45 2018
InstallationDate: Installed on 2018-09-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   dibo   1094 F...m pulseaudio
 /dev/snd/controlC0:  dibo   1094 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [X550CC, Realtek ALC270, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello, i tried to reinstall Ubuntu thinking was something easy to solve but 
nothing. the problem persist.
  in also i did different try with different guides but i didnt manage since im 
new on linux and tried to fix it without result.

  the problem is: 
   only headphones are showed on the list of outpout and the speakers, after 
using the command alsamixer -D hw:PCH i tried to increase the volume on the 
speakers, but nothing is changing.

  what do i suppose to do

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dibo   1094 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep  1 18:13:45 2018
  InstallationDate: Installed on 2018-09-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dibo   1094 F...m pulseaudio
   /dev/snd/controlC0:  dibo   1094 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Fabio Chino]

Update: I tested on Wayland and the problem persists.

I also discovered that, if I move the mouse and wait at least 1 second
before I press the button, the click is always computed. Just in case, I
also monitored the processor load and the issue happens even when the
processor is idle.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

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

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Fabio Chino]

Until I performed the last update on 2018-08-16, I was not experiencing
this issue. Now I started to experience random mouse clicks misses with
no apparent pattern, making the usage very annoying but not impossible.

Usually I misses the first clicks right after I move the mouse to the
desired position. Usually the first few clicks after I stop moving are
ignored but if I insist pressing it, it is eventually computed. The
mouse over events are working properly because links on the browser and
button highlights change as expected so it appears that only the clicks
are affected.

The problem always happens when I switch applications using the mouse
(the first click never works). The same happens when I activate a
context menu.

The only relevant package installed that day was linux-
modules-4.15.0-32-generic but a few days earlier, gdm3 was also
upgraded.

I'm using bionic X64 with XOrg using RX480 with amdgpu-pro drivers and
Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

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

[Desktop-packages] [Bug 1783527] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] Playback problem

[fabio di bartolo]

Public bug reported:

Hello,
i can't hear any sound neither from the test.
the audio isn't working, and, i tried to configure the speakers but linux 
doesn't recognize the speakers of the laptop, infect, checking the settings,i 
can see only headphones listed and not speakers or any other option.
]what can i do?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vecio  1250 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 25 09:50:13 2018
InstallationDate: Installed on 2018-07-24 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: None of the above
Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.212
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [X550CC, Realtek ALC270, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello,
  i can't hear any sound neither from the test.
  the audio isn't working, and, i tried to configure the speakers but linux 
doesn't recognize the speakers of the laptop, infect, checking the settings,i 
can see only headphones listed and not speakers or any other option.
  ]what can i do?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vecio  1250 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 25 09:50:13 2018
  InstallationDate: Installed on 2018-07-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X550CC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1773147] [NEW] nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build

[fabio braga moraes]

Public bug reported:

thats it!

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: nvidia-340 340.106-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
DKMSKernelVersion: 4.15.0-22-generic
Date: Wed May 23 22:59:04 2018
DuplicateSignature: dkms:nvidia-340:340.106-0ubuntu3:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
InstallationDate: Installed on 2018-05-05 (18 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageVersion: 340.106-0ubuntu3
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1773147

Title:
  nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  thats it!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-22-generic
  Date: Wed May 23 22:59:04 2018
  DuplicateSignature: dkms:nvidia-340:340.106-0ubuntu3:cc: error: unrecognized 
command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2018-05-05 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageVersion: 340.106-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.106-0ubuntu3: nvidia-340 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1773147/+subscriptions

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

[Desktop-packages] [Bug 1750416] [NEW] libsane1 crash when I switch from wine branch (devel, stable, staging)

[Fabio Di Giorgio]

Public bug reported:

1) Ubuntu 17.10
2) libsane1 1.0.27-1~experimental2ubuntu2.1
3) regular install
4) crashes on configure libsane1:386

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Feb 19 19:07:51 2018
ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" 
(condiviso), diverso da altre istanze del pacchetto libsane1:i386
InstallationDate: Installed on 2017-10-20 (122 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" 
(condiviso), diverso da altre istanze del pacchetto libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1750416

Title:
  libsane1 crash when I switch from wine branch (devel, stable, staging)

Status in sane-backends package in Ubuntu:
  New

Bug description:
  1) Ubuntu 17.10
  2) libsane1 1.0.27-1~experimental2ubuntu2.1
  3) regular install
  4) crashes on configure libsane1:386

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 19 19:07:51 2018
  ErrorMessage: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" 
(condiviso), diverso da altre istanze del pacchetto libsane1:i386
  InstallationDate: Installed on 2017-10-20 (122 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: tentata sovrascrittura di "/lib/udev/hwdb.d/20-sane.hwdb" 
(condiviso), diverso da altre istanze del pacchetto libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1750416/+subscriptions

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

[Desktop-packages] [Bug 683725] Re: When I format an usb key, after remount it opens the empty device twice.

[Fabio Augusto Miranda Martins]

Thank you for filing this bug. I tried to reproduce it in Xenial, but it
seems this behavior is no longer happening and very likely is already
fixed, so I'm closing this bug as invalid. This is also a duplicate of
686780.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/683725

Title:
  When I format an usb key, after remount it opens the empty device
  twice.

Status in One Hundred Papercuts:
  Confirmed
Status in nautilus package in Ubuntu:
  Invalid
Status in parted package in Ubuntu:
  Invalid

Bug description:
  When I plug an usb device and I format it through right click format, after 
the task is done, it remounts the device and open the empty device in nautilus 
twice. 
  It should open only once.
  It could not open at all because if we want to use the usb key to run "create 
a startup disk" it is no use and if we need to put files in it, we only have to 
double click the icon on the desktop to open the device.

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

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

[Desktop-packages] [Bug 686780] Re: USB format opens two nautilus windows

[Fabio Augusto Miranda Martins]

Thank you for filing this bug. I tried to reproduce it in Xenial, but it
seems this behavior is no longer happening and very likely is already
fixed, so I'm closing this bug as invalid. This is also a duplicate of
683725.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/686780

Title:
  USB format opens two nautilus windows

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: parted

  Sorry that i reported this to parted, i don't know even if this is "parted" 
related.
  This is a general error which is present for a long time. When you format USB 
(the one that displays in desktop) with Right Click , Format, after format it 
opens two nautilus windows.

  Sorry if this is duplicate but i couldn't find it.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: parted 2.2-5ubuntu5.1
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  Architecture: amd64
  Date: Tue Dec  7 23:05:36 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: parted

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

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

[Desktop-packages] [Bug 334806] Re: nautilus disappear desktop icons and freeze open folders on jaunty

[Fabio Augusto Miranda Martins]

We are closing this bug report as it is related to a no longer supported
version of Ubuntu + Kernel + Nautilus and this issue has not been
observed in any recent and supported releases.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/334806

Title:
  nautilus disappear desktop icons and freeze open folders on jaunty

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: nautilus

  This happens a few seconds after startup. When I kill de process the problem 
appears again 3-5 seconds after nautilus reboot.
  When I open nautilus for the terminal I get:
  "
  franciscocosta@franciscocosta-desktop:~$ nautilus

  (nautilus:9651): Unique-DBus-WARNING **: Error while sending message:
  Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nautilus:9651): Unique-DBus-WARNING **: Error while sending message: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.
  "

  I'm using the latest x64 Jaunty

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: fglrx
  Package: nautilus 1:2.25.91-0ubuntu1
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  SourcePackage: nautilus
  Uname: Linux 2.6.28-7-generic x86_64

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

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

[Desktop-packages] [Bug 1746353] Re: Evince cannot open file from Firefox (beta), failed to load libnss3.so

[Fabio Duran Verdugo]

It's a firefox issues, and this is fix now in the last version.

Look at https://bugzilla.mozilla.org/show_bug.cgi?id=1434033

** Bug watch added: Mozilla Bugzilla #1434033
   https://bugzilla.mozilla.org/show_bug.cgi?id=1434033

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

** Changed in: ubuntu
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1746353

Title:
  Evince cannot open file from Firefox (beta), failed to load libnss3.so

Status in Ubuntu:
  Fix Released

Bug description:
  Whenever I try to open a PDF file from the Firefox download manager, I
  get the following error:

  Failed to load backend for 'application/pdf': libnss3.so: failed to
  map segment from shared object.

  This only happens from Firefox Developer edition (same as beta), which
  I have running from my home directory. So this is probably somehow an
  issue with that, but I don't know how to debug it. I don't know why
  it's different from running Evince from nautilus, or just starting it
  directly, or even from Firefox stable, which is fine. But I suppose
  there might also be an issue with Evince if it's crashing when
  launched in this way.

  I would appreciate any help in debugging this matter. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Awesome GNOME
  Date: Tue Jan 30 13:12:05 2018
  InstallationDate: Installed on 2013-11-24 (1528 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-30 (92 days ago)

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

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

[Desktop-packages] [Bug 1744576] [NEW] package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Fabio Marconi]

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

Public bug reported:

Daily upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Sun Jan 21 17:50:41 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental3ubuntu1
 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-PWJxaq/09-libsane1_1.0.27-1~experimental3ubuntu1_i386.deb 
(--unpack):
  trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2016-10-30 (447 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.19.0.4ubuntu1
 apt  1.6~alpha5
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: Upgraded to bionic on 2018-01-08 (13 days ago)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check package-conflict

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1744576

Title:
  package libsane1 1.0.27-1~experimental3ubuntu1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Daily upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sun Jan 21 17:50:41 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental3ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PWJxaq/09-libsane1_1.0.27-1~experimental3ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-30 (447 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to bionic on 2018-01-08 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1744576/+subscriptions

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

[Desktop-packages] [Bug 856210] Fw: many cool stuff

[Fabio Rossi]

Have you already seen all that cool stuff  ? I'm sure you're  going  to
love it ! Check it out
http://www.samtekintl.com/bjwgx.php?UE84NTYyMTBAYnVHUy5sYVVOY2hwYWQubmV0

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/856210

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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

[Desktop-packages] [Bug 856210] Re: wow! some of my thoughts

[Fabio Rossi]

Dear,


I just wished to give out some  of my thoughts, please read  them here 
http://www.sujiapartment.com/will.php?UE84NTYyMTBAYnVncy5sYXVuY2hwYWQubmV0

FBIO ROSSI


From: Bug 856210 [mailto:856...@bugs.launchpad.net]
Sent: Tuesday, October 31, 2017 4:51 PM
To: ross...@inwind.it
Subject: You hate Thierry Henry

Stunning  photos... yes.

Tree growth connected with celestial movement and astral  cycles... no.


Can tree growth be affected  by our sun, the moon,  and possibly power lines?  
Yes.

Can a distant star affect a tree?   Not much (sure, there is some
light).

Do  *astral cycles* affect trees?  Fuck no...  what  a bunch of  hog
wash.


Money quote from  the posted article that lets you know it is nothing  but  
bullshit...

*I believe energies  inside the earth are transmuted and transmitted
into the cosmos  by the trees, so the  trees are like antennas,  senders
and receivers of earth  energies and stellar energies.*

Jeebus fuck - what a  load  of nonsense.


Sent from Mail for Windows 10

** Attachment added: "6B76F4F3398AE5E2.jpg"
   
https://bugs.launchpad.net/bugs/856210/+attachment/5001411/+files/6B76F4F3398AE5E2.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/856210

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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

[Desktop-packages] [Bug 1706936] Re: Wrong version of libgles1-mesa in Xenial-updates

[Fabio Ticconi]

I don't have a VLC ppa. I don't really understand what the problem is
here, but if it's not Ubuntu-related I'll figure something out. Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1706936

Title:
  Wrong version of libgles1-mesa in Xenial-updates

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Xenial-updates has the following packages:

  - libgles1-mesa (12.0.6-0ubuntu0.16.04.1)
  - libglapi-mesa (17.0.7-0ubuntu0.16.04.1)

  The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1),
  but libglapi-mesa has a higher version and so there's a conflict.

  I've had to remove libgles1-mesa for now, to avoid the conflict.

  I have Linux Mint 18.1 but I believe it affects anyone using xenial-
  updates.

  Source links I used to verify it's a xenial-updates problem:

  https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa
  https://packages.ubuntu.com/xenial-updates/libglapi-mesa

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

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

[Desktop-packages] [Bug 1706936] [NEW] Wrong version of libgles1-mesa in Xenial-updates

[Fabio Ticconi]

Public bug reported:

Xenial-updates has the following packages:

- libgles1-mesa (12.0.6-0ubuntu0.16.04.1)
- libglapi-mesa (17.0.7-0ubuntu0.16.04.1)

The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1), but
libglapi-mesa has a higher version and so there's a conflict.

I've had to remove libgles1-mesa for now, to avoid the conflict.

I have Linux Mint 18.1 but I believe it affects anyone using xenial-
updates.

Source links I used to verify it's a xenial-updates problem:

https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa
https://packages.ubuntu.com/xenial-updates/libglapi-mesa

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1706936

Title:
  Wrong version of libgles1-mesa in Xenial-updates

Status in mesa package in Ubuntu:
  New

Bug description:
  Xenial-updates has the following packages:

  - libgles1-mesa (12.0.6-0ubuntu0.16.04.1)
  - libglapi-mesa (17.0.7-0ubuntu0.16.04.1)

  The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1),
  but libglapi-mesa has a higher version and so there's a conflict.

  I've had to remove libgles1-mesa for now, to avoid the conflict.

  I have Linux Mint 18.1 but I believe it affects anyone using xenial-
  updates.

  Source links I used to verify it's a xenial-updates problem:

  https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa
  https://packages.ubuntu.com/xenial-updates/libglapi-mesa

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

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

[Desktop-packages] [Bug 856210] Re: Horizontal Scrollbar in kde dont work (default theme)

[Fabio Rossi]

** Attachment added: "1C56AF79EB02B80A2BF9A0354A651D34.jpg"
   
https://bugs.launchpad.net/bugs/856210/+attachment/4917298/+files/1C56AF79EB02B80A2BF9A0354A651D34.jpg

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/856210

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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

[Desktop-packages] [Bug 856210] Re: Strangers Come Together to Help Man With Down Syndrome Rebuild His Movie Collection After Fire

[Fabio Rossi]

Dear friend!


When a raging wildfire destroyed Mark Orsillo’s home and prized movie 
collection, strangers from http://sparktuition.com/bitex.php?7a7b


Yours faithfully, FBIO ROSSI


From: Bug 856210 [mailto:856...@bugs.launchpad.net]
Sent: Wednesday, July 19, 2017 12:51 AM
To: ross...@inwind.it
Subject: What's a water ramp?

This  comment needs  to  be higher up. I've  been  in Japan for a  few
years  and it's the country I've made my home. I always heard stories
about the  work/school life of people here but finally coming here  and
seeing it was mind-boggling. I don't like  the stereotypes to  be spread
further but things like overtime work,  drinking with coworkers and
after  school activities (e.g. cram school, club activities, etc.) are
ridiculous. Moderation is not a word  many Japanese people are familiar
with.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/856210

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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

[Desktop-packages] [Bug 1704637] [NEW] package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[fabio campanile]

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

Public bug reported:

I received this error message during the upgrade to 17.04

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: cracklib-runtime 2.9.2-3
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.4
Architecture: amd64
Date: Sun Jul 16 11:11:15 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-01-21 (176 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: cracklib2
Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to zesty on 2017-07-16 (0 days ago)

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


** Tags: amd64 apport-package zesty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cracklib2 in Ubuntu.
https://bugs.launchpad.net/bugs/1704637

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cracklib2 package in Ubuntu:
  New

Bug description:
  I received this error message during the upgrade to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.4
  Architecture: amd64
  Date: Sun Jul 16 11:11:15 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-01-21 (176 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-07-16 (0 days ago)

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

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

[Desktop-packages] [Bug 1650325] Re: Make Link missing from right click menu

[Fabio M. Panico]

I appreciate the effort in providing a solution to this problem.

But, as I came to know, the "make link" is not really missing from
Nautilus, but just disable by default.

All it takes is getting into Nautilus Preferences > Behavior (tab) and
check the box for "Link Creation".  After that, "create link" option
comes back to contextual menu.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1650325

Title:
  Make Link missing from right click menu

Status in gedit package in Ubuntu:
  New

Bug description:
  In Ubuntu 16.10, the "Make Link" command is missing from the right
  click Nautilus menu.

  Please attribute this bug to the correct module, gedit was used to
  trigger the ubuntu-bug process.

  Thanks.

  more info at: https://answers.launchpad.net/ubuntu/+question/404047

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 15 11:12:01 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-09 (159 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1643429] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[fabio]

Public bug reported:

x

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
Uname: Linux 4.4.0-49-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Sun Nov 20 10:13:29 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-04-15 (585 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: HP-Pavilion FL398AA-ABZ m9461it
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-27 (85 days ago)
dmi.bios.date: 09/05/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.30
dmi.board.name: Benicia
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.30:bd09/05/2008:svnHP-Pavilion:pnFL398AA-ABZm9461it:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: FL398AA-ABZ m9461it
dmi.sys.vendor: HP-Pavilion
modified.conffile..etc.default.cups:
 # Cups configure options
 
 # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
 # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
 # LOAD_LP_MODULE=yes
mtime.conffile..etc.default.cups: 2015-04-17T00:15:58.864658

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


** Tags: amd64 apport-package need-duplicate-check xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1643429

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  New

Bug description:
  x

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30
  Uname: Linux 4.4.0-49-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun Nov 20 10:13:29 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-04-15 (585 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: HP-Pavilion FL398AA-ABZ m9461it
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic 
root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-27 (85 days ago)
  dmi.bios.date: 09/05/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.30
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.30:bd09/05/2008:svnHP-Pavilion:pnFL398AA-ABZm9461it:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: FL398AA-ABZ m9461it
  dmi.sys.vendor: HP-Pavilion
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2015-04-17T00:15:58.864658

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

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

[Desktop-packages] [Bug 1633162] Re: Files application throws an error 'Oops! Something went wrong' when clicked on 'Recents'

[Fabio B]

This bug affects me as well, anyway the "recent files" works inside
modal windows while opening/selecting files

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633162

Title:
  Files application throws an error 'Oops! Something went wrong' when
  clicked on 'Recents'

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  The application crashes every time I click on 'Recent' with this
  message in a pop-up window:

  "Unhandled error message: Message recipient disconnected from message
  bus without replying."

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 13 22:34:57 2016
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'enable-interactive-search' b'false'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+476+24'"
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[Fabio Marconi]

Raising importance cuz isn't only aesthetic issue but it affect
usability

** Changed in: gedit (Ubuntu)
   Importance: Low => Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1620806

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1635998] Re: Transparent window

[Fabio Marconi]

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

** This bug has been marked a duplicate of bug 1620806
   gedit edit window  is transparent when using Ambiance and Radiance themes

** Attachment removed: "Screenshot from 2016-10-23 19-49-09.png"
   
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1635998/+attachment/4765944/+files/Screenshot%20from%202016-10-23%2019-49-09.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1635998

Title:
  Transparent window

Status in gedit package in Ubuntu:
  New

Bug description:
  Hallo
  I just noticed that as soon as I type something the window background becomes 
transparent even if gedit still working and focused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.22.0-1ubuntu1
  Uname: Linux 4.8.4-040804-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 23 19:51:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-22 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1635998] [NEW] Transparent window

[Fabio Marconi]

Public bug reported:

Hallo
I just noticed that as soon as I type something the window background becomes 
transparent even if gedit still working and focused

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: gedit 3.22.0-1ubuntu1
Uname: Linux 4.8.4-040804-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 23 19:51:33 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-22 (1 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

** Attachment added: "Screenshot from 2016-10-23 19-49-09.png"
   
https://bugs.launchpad.net/bugs/1635998/+attachment/4765944/+files/Screenshot%20from%202016-10-23%2019-49-09.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1635998

Title:
  Transparent window

Status in gedit package in Ubuntu:
  New

Bug description:
  Hallo
  I just noticed that as soon as I type something the window background becomes 
transparent even if gedit still working and focused

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.22.0-1ubuntu1
  Uname: Linux 4.8.4-040804-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 23 19:51:33 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-22 (1 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1631787] Re: Ubuntu ship by default Amazon launcher

[Fabio Marconi]

Confirmed on Italian Television

** Tags added: rls-y-incoming yakkety

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webapps-applications in Ubuntu.
https://bugs.launchpad.net/bugs/1631787

Title:
  Ubuntu ship by default Amazon launcher

Status in webapps-applications package in Ubuntu:
  Confirmed

Bug description:
  How many times encountered, Amazon requires its workers to too high pace of 
work, proving to not to be humanity for others. Please stop this shame.
  Man is not a machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1631787/+subscriptions

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

[Desktop-packages] [Bug 1631787] [NEW] Ubuntu ship by default Amazon launcher

[Fabio Marconi]

Public bug reported:

How many times encountered, Amazon requires its workers to too high pace of 
work, proving to not to be humanity for others. Please stop this shame.
Man is not a machine.

** Affects: webapps-applications (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: rls-y-incoming yakkety

** Package changed: pulseaudio (Ubuntu) => webapps-applications (Ubuntu)

** Changed in: webapps-applications (Ubuntu)
   Importance: Undecided => High

** Changed in: webapps-applications (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1631787

Title:
  Ubuntu ship by default Amazon launcher

Status in webapps-applications package in Ubuntu:
  Confirmed

Bug description:
  How many times encountered, Amazon requires its workers to too high pace of 
work, proving to not to be humanity for others. Please stop this shame.
  Man is not a machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1631787/+subscriptions

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

[Desktop-packages] [Bug 1631782] [NEW] Volume and Mic controls grayed out and not working

[Fabio Marconi]

Public bug reported:

Hallo
testing Yakkety 08-10 buld on live session i have the controls of the volume 
locked and not working as shown in the attached screenshot. Even in sound 
setting I can-t set the desired volume, anyway it play sounds correctly.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: pulseaudio 1:9.0-2ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
Uname: Linux 4.8.0-21-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CasperVersion: 1.379
CurrentDesktop: Unity
Date: Sun Oct  9 17:53:10 2016
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: H55M-S2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55M-S2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug rls-y-incoming yakkety

** Attachment added: "Screenshot from 2016-10-09 17-52-04.png"
   
https://bugs.launchpad.net/bugs/1631782/+attachment/4758293/+files/Screenshot%20from%202016-10-09%2017-52-04.png

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1631782

Title:
  Volume and Mic controls grayed out and not working

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hallo
  testing Yakkety 08-10 buld on live session i have the controls of the volume 
locked and not working as shown in the attached screenshot. Even in sound 
setting I can-t set the desired volume, anyway it play sounds correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.379
  CurrentDesktop: Unity
  Date: Sun Oct  9 17:53:10 2016
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: H55M-S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55M-S2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1629088] Re: [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial

[Fabio Marconi]

retenjin_EXT_EXT is home wifi
VodafoneMobileWifi is the mobile modem

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

Title:
  [Yakkety] WIFI disconnections, fail in reconnection introduced from
  Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hallo
  Wily with latest mainline kernel works great so I assume this issue is not 
related to linux.
  Starting from Xenial I cannot (or sometimes I can for few times and for few 
minutes) connect to my wireless, even the mobile modem frequently disconnect 
with problem reconnecting back.
  Even now I cannot reconnect to my mobile modem so I have to use the usb wire 
to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 29 19:02:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s1  proto static  metric 600 
   169.254.0.0/16 dev wlp4s1  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s1  proto kernel  scope link  src 192.168.0.110  
metric 600
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   
 
   wlp4s1  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
VodafoneMobileWiFi-CC8463  31bb378f-071e-49d9-96f5-600b2c1b511a  
/org/freedesktop/NetworkManager/ActiveConnection/15 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+subscriptions

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

[Desktop-packages] [Bug 1629088] Re: [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial

[Fabio Marconi]

** Summary changed:

- [Yakkety] Disconnections, fail in reconnection introduced from Xenial
+ [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial

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

Title:
  [Yakkety] WIFI disconnections, fail in reconnection introduced from
  Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hallo
  Wily with latest mainline kernel works great so I assume this issue is not 
related to linux.
  Starting from Xenial I cannot (or sometimes I can for few times and for few 
minutes) connect to my wireless, even the mobile modem frequently disconnect 
with problem reconnecting back.
  Even now I cannot reconnect to my mobile modem so I have to use the usb wire 
to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 29 19:02:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s1  proto static  metric 600 
   169.254.0.0/16 dev wlp4s1  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s1  proto kernel  scope link  src 192.168.0.110  
metric 600
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   
 
   wlp4s1  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
VodafoneMobileWiFi-CC8463  31bb378f-071e-49d9-96f5-600b2c1b511a  
/org/freedesktop/NetworkManager/ActiveConnection/15 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+subscriptions

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

[Desktop-packages] [Bug 1629088] [NEW] [Yakkety] Disconnections, fail in reconnection introduced from Xenial

[Fabio Marconi]

Public bug reported:

Hallo
Wily with latest mainline kernel works great so I assume this issue is not 
related to linux.
Starting from Xenial I cannot (or sometimes I can for few times and for few 
minutes) connect to my wireless, even the mobile modem frequently disconnect 
with problem reconnecting back.
Even now I cannot reconnect to my mobile modem so I have to use the usb wire to 
it.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CasperVersion: 1.378
CurrentDesktop: Unity:Unity7
Date: Thu Sep 29 19:02:44 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.0.1 dev wlp4s1  proto static  metric 600 
 169.254.0.0/16 dev wlp4s1  scope link  metric 1000 
 192.168.0.0/24 dev wlp4s1  proto kernel  scope link  src 192.168.0.110  metric 
600
LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   
 
 wlp4s1  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
VodafoneMobileWiFi-CC8463  31bb378f-071e-49d9-96f5-600b2c1b511a  
/org/freedesktop/NetworkManager/ActiveConnection/15 
 enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
  ----  

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --   
  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug regression-release xenial yakkety

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Tags added: regression-release xenial

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

Title:
  [Yakkety] Disconnections, fail in reconnection introduced from Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hallo
  Wily with latest mainline kernel works great so I assume this issue is not 
related to linux.
  Starting from Xenial I cannot (or sometimes I can for few times and for few 
minutes) connect to my wireless, even the mobile modem frequently disconnect 
with problem reconnecting back.
  Even now I cannot reconnect to my mobile modem so I have to use the usb wire 
to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 29 19:02:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s1  proto static  metric 600 
   169.254.0.0/16 dev wlp4s1  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s1  proto kernel  scope link  src 192.168.0.110  
metric 600
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   
 
   wlp4s1  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
VodafoneMobileWiFi-CC8463  31bb378f-071e-49d9-96f5-600b2c1b511a  
/org/freedesktop/NetworkManager/ActiveConnection/15 
   enp3s0  ethernet  unavailable  

[Desktop-packages] [Bug 1629088] Re: [Yakkety] Disconnections, fail in reconnection introduced from Xenial

[Fabio Marconi]

Attaching some logs with fail in reconnection during this report

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+attachment/4751312/+files/syslog

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

Title:
  [Yakkety] Disconnections, fail in reconnection introduced from Xenial

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hallo
  Wily with latest mainline kernel works great so I assume this issue is not 
related to linux.
  Starting from Xenial I cannot (or sometimes I can for few times and for few 
minutes) connect to my wireless, even the mobile modem frequently disconnect 
with problem reconnecting back.
  Even now I cannot reconnect to my mobile modem so I have to use the usb wire 
to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.378
  CurrentDesktop: Unity:Unity7
  Date: Thu Sep 29 19:02:44 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.0.1 dev wlp4s1  proto static  metric 600 
   169.254.0.0/16 dev wlp4s1  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s1  proto kernel  scope link  src 192.168.0.110  
metric 600
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION CON-UUID  CON-PATH   
 
   wlp4s1  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
VodafoneMobileWiFi-CC8463  31bb378f-071e-49d9-96f5-600b2c1b511a  
/org/freedesktop/NetworkManager/ActiveConnection/15 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
----
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+subscriptions

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

[Desktop-packages] [Bug 1623126] Re: Application icons don't follow the theme

[Fabio]

No, the same behaviour happens on Yakkety.. I tried it with the Paper
icon theme

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1623126

Title:
  Application icons don't follow the theme

Status in gnome-software package in Ubuntu:
  Won't Fix

Bug description:
  Icons of applications within the store are fixed and don't follow the
  theme chosen by the user. This makes the icons ugly and out of place
  when using any icon theme different from the default.

  Expected:
  Icons of common applications to follow the custom icon theme chosen by the 
user.

  What happens:
  Icons are displayed according to the default theme (ubuntu-mono-*).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1623126/+subscriptions

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

[Desktop-packages] [Bug 1623126] Re: Application icons don't follow the theme

[Fabio]

I don't know how it works, but couldn't it load icons from the app names
like launchers do?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1623126

Title:
  Application icons don't follow the theme

Status in gnome-software package in Ubuntu:
  Won't Fix

Bug description:
  Icons of applications within the store are fixed and don't follow the
  theme chosen by the user. This makes the icons ugly and out of place
  when using any icon theme different from the default.

  Expected:
  Icons of common applications to follow the custom icon theme chosen by the 
user.

  What happens:
  Icons are displayed according to the default theme (ubuntu-mono-*).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1623126/+subscriptions

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

[Desktop-packages] [Bug 856210] Re: giornata folle

[Fabio Rossi]

Caro,


Ho avuto una giornata folle ieri e ho voluto condividere la storia con voi,  si 
può trovare  qui 

Grazie per la tua considerazione,FBIO ROSSI

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/856210

Title:
  Horizontal Scrollbar in kde dont work (default theme)

Status in LibreOffice:
  Fix Released
Status in oxygen transparent:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Oneiric:
  Fix Released
Status in libreoffice source package in Precise:
  Fix Released

Bug description:
  When using libreoffice in kunbuntu 11.10 beta, the horizontal
  scrollbar seems too large and cannot be moved (see screenshot in
  attachement). I've seen this bug in calc and impress.

  Thanks for your help !

  WORKAROUND: remove libreoffice-kde  (but you lose KDE integration -
  but it becomes useable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/856210/+subscriptions

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

[Desktop-packages] [Bug 1623126] [NEW] Application icons don't follow the theme

[Fabio]

Public bug reported:

Icons of applications within the store are fixed and don't follow the
theme chosen by the user. This makes the icons ugly and out of place
when using any icon theme different from the default.

Expected:
Icons of common applications to follow the custom icon theme chosen by the user.

What happens:
Icons are displayed according to the default theme (ubuntu-mono-*).

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1623126

Title:
  Application icons don't follow the theme

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Icons of applications within the store are fixed and don't follow the
  theme chosen by the user. This makes the icons ugly and out of place
  when using any icon theme different from the default.

  Expected:
  Icons of common applications to follow the custom icon theme chosen by the 
user.

  What happens:
  Icons are displayed according to the default theme (ubuntu-mono-*).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1623126/+subscriptions

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

[Desktop-packages] [Bug 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze

[Fabio]

** Description changed:

  I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89
  from Additional Drivers application then reboot, it shows black screen,
  no login window, I even can't use ctrl+alt+F2 to switch to text mode,
  then I reboot and go to recovery mode, use 'prime-select intel' to
  switch to intel GPU and reboot, everything is fine, but as soon as I
  switch to nvidia GPU, still same issue.
  
  OS: Ubuntu 14.04 64bit
  Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600
  Desktop: Unity
  Kernel: 3.13.0
  CPU: Intel® Core™ i7-4700MQ
  
- Thanks!
+ Temporary workaround:
+ close the lid and open it back
+ 
http://askubuntu.com/questions/762329/black-screen-on-boot-screen-reappears-after-closing-and-opening-lid
+ 
+ Possible temporary fix:
+ see 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/comments/15

** Summary changed:

- ubuntu 14.04 after install nvidia binary driver  331.89  black screen and 
freeze
+ black/blank screen and freeze at startup after installing nvidia driver (with 
hybrid graphic card)

** Description changed:

  I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89
  from Additional Drivers application then reboot, it shows black screen,
  no login window, I even can't use ctrl+alt+F2 to switch to text mode,
  then I reboot and go to recovery mode, use 'prime-select intel' to
  switch to intel GPU and reboot, everything is fine, but as soon as I
  switch to nvidia GPU, still same issue.
  
  OS: Ubuntu 14.04 64bit
  Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600
  Desktop: Unity
  Kernel: 3.13.0
  CPU: Intel® Core™ i7-4700MQ
  
- Temporary workaround:
+ Temporary workaround (intel session):
+ Reboot to recovery mode, mount the filesystem and run
+ `prime-select intel`. Than reboot.
+ 
+ Temporary workaround (nvidia session):
  close the lid and open it back
  
http://askubuntu.com/questions/762329/black-screen-on-boot-screen-reappears-after-closing-and-opening-lid
  
  Possible temporary fix:
  see 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/comments/15

** Tags added: nvidia-361

** Description changed:

  I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89
  from Additional Drivers application then reboot, it shows black screen,
  no login window, I even can't use ctrl+alt+F2 to switch to text mode,
  then I reboot and go to recovery mode, use 'prime-select intel' to
  switch to intel GPU and reboot, everything is fine, but as soon as I
  switch to nvidia GPU, still same issue.
  
  OS: Ubuntu 14.04 64bit
  Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600
  Desktop: Unity
  Kernel: 3.13.0
  CPU: Intel® Core™ i7-4700MQ
  
+ --
+ 
  Temporary workaround (intel session):
  Reboot to recovery mode, mount the filesystem and run
  `prime-select intel`. Than reboot.
  
  Temporary workaround (nvidia session):
  close the lid and open it back
  
http://askubuntu.com/questions/762329/black-screen-on-boot-screen-reappears-after-closing-and-opening-lid
  
  Possible temporary fix:
  see 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/comments/15

** Description changed:

  I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89
  from Additional Drivers application then reboot, it shows black screen,
  no login window, I even can't use ctrl+alt+F2 to switch to text mode,
  then I reboot and go to recovery mode, use 'prime-select intel' to
  switch to intel GPU and reboot, everything is fine, but as soon as I
  switch to nvidia GPU, still same issue.
  
  OS: Ubuntu 14.04 64bit
  Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600
  Desktop: Unity
  Kernel: 3.13.0
  CPU: Intel® Core™ i7-4700MQ
  
  --
  
  Temporary workaround (intel session):
  Reboot to recovery mode, mount the filesystem and run
  `prime-select intel`. Than reboot.
  
  Temporary workaround (nvidia session):
  close the lid and open it back
  
http://askubuntu.com/questions/762329/black-screen-on-boot-screen-reappears-after-closing-and-opening-lid
  
  Possible temporary fix:
- see 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/comments/15
+ see 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/comments/18

** Also affects: ubuntu-drivers-common
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-drivers-common

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
https://bugs.launchpad.net/bugs/1362848

Title:
  black/blank screen and freeze at startup after installing nvidia
 

[Desktop-packages] [Bug 1580472] Re: No visible cursor after logging in

[Fabio]

I'm not sure I can use the nvidia card without the nvidia drivers as
it's an optimus card. With just nouveau installed it works fine,
anyaway.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Only when using the nvidia drivers, after logging in, the cursor is
  not drawn on the screen. I can see its effects while moving the mouse
  or touchpad, as items on the panel gets highlighted, or my unity panel
  becomes visible. I can even click on them and everything else works.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again through lightdm. This works 
most of the time.

  ---
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
     Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1580472] Re: No visible cursor after logging in

[Fabio]

No, to my memory I just experienced this using the nvidia drivers and
when enabling the nvidia card (I have an hybrid optimus card)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] ProcEnviron.txt

[Fabio]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704711/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] nvidia-settings.txt

[Fabio]

apport information

** Attachment added: "nvidia-settings.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704720/+files/nvidia-settings.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Desktop-packages] [Bug 1580472] Xrandr.txt

[Fabio]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1580472/+attachment/4704719/+files/Xrandr.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] GconfCompiz.txt

[Fabio]

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704703/+files/GconfCompiz.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] DpkgLog.txt

[Fabio]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704702/+files/DpkgLog.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] Lspci.txt

[Fabio]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1580472/+attachment/4704707/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] xdpyinfo.txt

[Fabio]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704721/+files/xdpyinfo.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] Dependencies.txt

[Fabio]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704701/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] XorgLog.txt

[Fabio]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704717/+files/XorgLog.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] XorgLogOld.txt

[Fabio]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704718/+files/XorgLogOld.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] XorgConf.txt

[Fabio]

apport information

** Attachment added: "XorgConf.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704716/+files/XorgConf.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] UnitySupportTest.txt

[Fabio]

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704715/+files/UnitySupportTest.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Desktop-packages] [Bug 1580472] UdevDb.txt

[Fabio]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1580472/+attachment/4704714/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] ProcModules.txt

[Fabio]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704713/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] ProcInterrupts.txt

[Fabio]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704712/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Desktop-packages] [Bug 1580472] ProcCpuinfo.txt

[Fabio]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704710/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] NvidiaBugReportLog.txt

[Fabio]

apport information

** Attachment added: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704709/+files/NvidiaBugReportLog.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Desktop-packages] [Bug 1580472] MonitorsUser.xml.txt

[Fabio]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704708/+files/MonitorsUser.xml.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Desktop-packages] [Bug 1580472] LightdmLog.txt

[Fabio]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704706/+files/LightdmLog.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: 

[Desktop-packages] [Bug 1580472] LightdmDisplayLog.txt

[Fabio]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704705/+files/LightdmDisplayLog.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  

[Desktop-packages] [Bug 1580472] JournalErrors.txt

[Fabio]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1580472/+attachment/4704704/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580472

Title:
  No visible cursor after logging in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After logging in, the cursor is not drawn on the screen.

  I can see it's effects while moving the mouse or touchpad, as items on
  the panel gets highlighted, or my unity panel becomes visible. I can
  even click on them and everything else just works, but I have to
  figure the cursor position.

  Workaround:
  Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server:
  sudo service lightdm restart. Now log in again trough lightdm and cross your 
fingers, as it doesn't always work, but most of the times does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  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: Wed May 11 08:53:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-21 (416 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: nvidia-graphics-drivers-361
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted]
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:178d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d]
  InstallationDate: Installed on 2016-06-24 (27 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.303
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: