[Desktop-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

[Leo Didier]

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

Same for me, the upgrade went horribly also wrong...

But i could get everything on track again from the terminal with a complete 
update and upgrade the missing packages.
Did not have to do install systemd-resolved as i already had the latest 
installed.

Then in Ubuntu 24 desktop i had troubles with long minutes hanging on a grey 
screen, firefox freeze at start up and other desktop freezes..
A snap store refresh did the job with 'sudo snap refresh snap-store' and 
everything is working fine now !

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2058193] [NEW] Support Synaptics fingerprint device with ID [06CB:0106]

[Leo Lin]

Public bug reported:

The ID [06CB:0106] is included in
https://salsa.debian.org/debian/libfprint/-/commit/427139f347c576e08d6656142ba39d06c7be2b15

[Impact]

 * Support Synaptics [06CB:0106] fingerprint component.

[Test Plan]

 * Find a machine with this fingerprint device

 * Launch `settings` and enable `Fingerprint Login`

 * Enroll finger and then logout

 * Login system with enrolled finger

[Where problems could occur]

 * If the vendor uses the same ID for other devices, the new device may
not work properly.

** Affects: oem-priority
 Importance: Critical
 Assignee: Leo Lin (0xff07)
 Status: New

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


** Tags: oem-priority originate-from-2057729 stella

** Tags added: oem-priority originate-from-2057729 stella

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

** Changed in: oem-priority
 Assignee: (unassigned) => Leo Lin (0xff07)

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

Title:
  Support Synaptics fingerprint device with ID [06CB:0106]

Status in OEM Priority Project:
  New
Status in libfprint package in Ubuntu:
  New

Bug description:
  The ID [06CB:0106] is included in
  
https://salsa.debian.org/debian/libfprint/-/commit/427139f347c576e08d6656142ba39d06c7be2b15

  [Impact]

   * Support Synaptics [06CB:0106] fingerprint component.

  [Test Plan]

   * Find a machine with this fingerprint device

   * Launch `settings` and enable `Fingerprint Login`

   * Enroll finger and then logout

   * Login system with enrolled finger

  [Where problems could occur]

   * If the vendor uses the same ID for other devices, the new device
  may not work properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2058193/+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 1982477] [NEW] UI does not work with Linux version 5.15.0-41

[Leo Kotschenreuther]

Public bug reported:

After upgrading my Linux kernel to version 5.15.0-41, I am no longer
able to get into the UI. After booting and unlocking the disk I end up
on a black screen with a blinking underscore in the top left corner.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Jul 21 12:14:04 2022
InstallationDate: Installed on 2021-12-03 (229 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcEnviron:
 TERM=linux
 SHELL=/usr/bin/zsh
 PATH=(custom, user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904

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


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  UI does not work with Linux version 5.15.0-41

Status in gdm3 package in Ubuntu:
  New

Bug description:
  After upgrading my Linux kernel to version 5.15.0-41, I am no longer
  able to get into the UI. After booting and unlocking the disk I end up
  on a black screen with a blinking underscore in the top left corner.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Uname: Linux 5.15.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul 21 12:14:04 2022
  InstallationDate: Installed on 2021-12-03 (229 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  ProcEnviron:
   TERM=linux
   SHELL=/usr/bin/zsh
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2022-07-21T11:41:09.164904

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1982477/+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 1967488] [NEW] Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver)

[Leo]

Public bug reported:

Hi
I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the 
Chromium browser (stable snap package), only see a black window. If I switch 
from Wayland to Xorg, everything is normal again.

I tried to delete the profile folder , but I have the same result.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: chromium snap wayland xorg

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

Title:
  Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi
  I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the 
Chromium browser (stable snap package), only see a black window. If I switch 
from Wayland to Xorg, everything is normal again.

  I tried to delete the profile folder , but I have the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 1948723] Re: /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma? raise Exceptions.LayoutFile

[Leo Chen]

Got same error when install Unity on Ubuntu Server 20.04 LTS 32-bit for
Raspberry Pi.

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

Title:
  /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447:
  SyntaxWarning: 'str' object is not callable; perhaps you missed a
  comma?   raise Exceptions.LayoutFileError("Unrecognized modifier %s
  in" \

Status in Onboard:
  New
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install or reinstall Onboard with

  sudo apt-get install --reinstall onboard onboard-common onboard-
  data

  Expected results:
  * no warnings

  Actual results:
  * the following warning is shown -

  ```
  $ sudo apt-get install --reinstall onboard onboard-common onboard-data 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  0 upgraded, 0 newly installed, 3 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 5 217 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-common 
all 1.4.1-5build4 [595 kB]
  Get:2 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard amd64 
1.4.1-5build4 [380 kB]
  Get:3 http://archive.ubuntu.com/ubuntu jammy/universe amd64 onboard-data all 
1.4.1-5build4 [4 242 kB]
  Fetched 5 217 kB in 2s (2 938 kB/s)   
  (Reading database ... 243599 files and directories currently installed.)
  Preparing to unpack .../onboard-common_1.4.1-5build4_all.deb ...
  Unpacking onboard-common (1.4.1-5build4) over (1.4.1-5build4) ...
  Preparing to unpack .../onboard_1.4.1-5build4_amd64.deb ...
  Unpacking onboard (1.4.1-5build4) over (1.4.1-5build4) ...
  Preparing to unpack .../onboard-data_1.4.1-5build4_all.deb ...
  Unpacking onboard-data (1.4.1-5build4) over (1.4.1-5build4) ...
  Setting up onboard-common (1.4.1-5build4) ...
  Setting up onboard (1.4.1-5build4) ...
  /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 
'str' object is not callable; perhaps you missed a comma?
raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
  Processing triggers for mailcap (3.70ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.5+21.10.20210710-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for desktop-file-utils (0.26-1ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.17-2) ...
  Processing triggers for gnome-menus (3.36.0-1ubuntu2) ...
  Processing triggers for libglib2.0-0:amd64 (2.68.4-1ubuntu1) ...
  Processing triggers for man-db (2.9.4-2build1) ...
  Setting up onboard-data (1.4.1-5build4) ...

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: onboard 1.4.1-5build4
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Oct 26 01:08:47 2021
  InstallationDate: Installed on 2021-10-24 (1 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211024)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1948723/+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 1934882] Re: package has invalid Support Legacyheader

[Leo]

So the Support Legacyheader was a red herring.

Debugging the ubuntu-drivers python showed that
ubuntu-drivers install
calls the following:
apt-get install -o DPkg::options::=--force-confnew -y nvidia-driver-460 
linux-modules-nvidia-460-generic

when run manually this gives the output:
Preparing to unpack .../libnvidia-gl-460_460.84-0ubuntu0.21.04.1_amd64.deb ...
diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340
dpkg-divert: error: mismatch on package
  when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by 
libnvidia-gl-460'
  found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to 
/usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340'
dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-gl-460_460.84-0ubuntu0.21.04.1_amd64.deb 
(--unpack):
 new libnvidia-gl-460:amd64 package pre-installation script subprocess returned 
error exit status 2
Selecting previously unselected package libnvidia-ifr1-460:amd64.
Preparing to unpack .../libnvidia-ifr1-460_460.84-0ubuntu0.21.04.1_amd64.deb ...
Unpacking libnvidia-ifr1-460:amd64 (460.84-0ubuntu0.21.04.1) ...
Selecting previously unselected package linux-modules-nvidia-460-generic.
Preparing to unpack .../linux-modules-nvidia-460-generic_5.11.0-24.25_amd64.deb 
...
Unpacking linux-modules-nvidia-460-generic (5.11.0-24.25) ...
Selecting previously unselected package nvidia-driver-460.
Preparing to unpack .../nvidia-driver-460_460.84-0ubuntu0.21.04.1_amd64.deb ...
Unpacking nvidia-driver-460 (460.84-0ubuntu0.21.04.1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libnvidia-gl-460_460.84-0ubuntu0.21.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

So perhaps something did get cleaned up correctly in the upgrade?
Searching for this error led me to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1768050 where the suggested fix for running dpkg-divert
--remove, resulted in ubuntu-drivers install running successfully.

Not sure why this output didn't show up when I initially call ubuntu-
drivers from the cmd line. Perhaps because the GUI had already called it
and now apt was unhappy there was no output, just a non-zero return
code?

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

Title:
  package has invalid Support Legacyheader

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Having recently upgraded 20.10 -> 21.04 it is no longer possible to install 
the nvidia drivers. Running: ubuntu-drivers devices
  Outputs:
  WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support 
Legacyheader, cannot determine support level
  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1184sv1458sd3603bc03sc00i00
  vendor   : NVIDIA Corporation
  model: GK104 [GeForce GTX 770]
  driver   : nvidia-driver-460 - distro non-free recommended
  driver   : nvidia-driver-450-server - distro non-free
  driver   : nvidia-driver-465 - distro non-free
  driver   : nvidia-driver-460-server - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-418-server - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  Running: ubuntu-drivers install nvidia-driver-460
  Outputs:
  WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support 
Legacyheader, cannot determine support level
  No drivers found for installation.

  I've tried:
  apt-get remove --purge "nvidia*" libnvidia-ifr1-460
  and then re-doing the ubuntu-drivers commands. But that doesn't make a 
difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-drivers-common 1:0.9.0~0.21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
  Uname: Linux 5.11.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Jul  7 11:01:07 2021
  InstallationDate: Installed on 2017-05-13 (1515 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to hirsute on 2021-07-04 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1934882/+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 1934882] [NEW] package has invalid Support Legacyheader

[Leo]

Public bug reported:

Having recently upgraded 20.10 -> 21.04 it is no longer possible to install the 
nvidia drivers. Running: ubuntu-drivers devices
Outputs:
WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support 
Legacyheader, cannot determine support level
== /sys/devices/pci:00/:00:01.0/:01:00.0 ==
modalias : pci:v10DEd1184sv1458sd3603bc03sc00i00
vendor   : NVIDIA Corporation
model: GK104 [GeForce GTX 770]
driver   : nvidia-driver-460 - distro non-free recommended
driver   : nvidia-driver-450-server - distro non-free
driver   : nvidia-driver-465 - distro non-free
driver   : nvidia-driver-460-server - distro non-free
driver   : nvidia-driver-390 - distro non-free
driver   : nvidia-driver-418-server - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

Running: ubuntu-drivers install nvidia-driver-460
Outputs:
WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support 
Legacyheader, cannot determine support level
No drivers found for installation.

I've tried:
apt-get remove --purge "nvidia*" libnvidia-ifr1-460
and then re-doing the ubuntu-drivers commands. But that doesn't make a 
difference.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubuntu-drivers-common 1:0.9.0~0.21.04.1
ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
Uname: Linux 5.11.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Wed Jul  7 11:01:07 2021
InstallationDate: Installed on 2017-05-13 (1515 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: ubuntu-drivers-common
UpgradeStatus: Upgraded to hirsute on 2021-07-04 (2 days ago)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute package-from-proposed

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

Title:
  package has invalid Support Legacyheader

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  Having recently upgraded 20.10 -> 21.04 it is no longer possible to install 
the nvidia drivers. Running: ubuntu-drivers devices
  Outputs:
  WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support 
Legacyheader, cannot determine support level
  == /sys/devices/pci:00/:00:01.0/:01:00.0 ==
  modalias : pci:v10DEd1184sv1458sd3603bc03sc00i00
  vendor   : NVIDIA Corporation
  model: GK104 [GeForce GTX 770]
  driver   : nvidia-driver-460 - distro non-free recommended
  driver   : nvidia-driver-450-server - distro non-free
  driver   : nvidia-driver-465 - distro non-free
  driver   : nvidia-driver-460-server - distro non-free
  driver   : nvidia-driver-390 - distro non-free
  driver   : nvidia-driver-418-server - distro non-free
  driver   : xserver-xorg-video-nouveau - distro free builtin

  Running: ubuntu-drivers install nvidia-driver-460
  Outputs:
  WARNING:root:_pkg_get_support nvidia-driver-390: package has invalid Support 
Legacyheader, cannot determine support level
  No drivers found for installation.

  I've tried:
  apt-get remove --purge "nvidia*" libnvidia-ifr1-460
  and then re-doing the ubuntu-drivers commands. But that doesn't make a 
difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-drivers-common 1:0.9.0~0.21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22
  Uname: Linux 5.11.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Jul  7 11:01:07 2021
  InstallationDate: Installed on 2017-05-13 (1515 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to hirsute on 2021-07-04 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1934882/+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 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

[Leo]

It's strange , 1 hour after the message that the bug was resolved, I
updated my system, but the package was not updated.

I updated again just a moment ago, and now everything is fine. Thank you
very much!

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

Title:
  Window focus/clicking/moving failures for Xorg sessions in
  3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1

[Leo]

In my case is not resolved and I have my system updated.

I came from this bug, and my problem is exactly the showed by Paul Goins
in his video:

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918273/+attachment/5475163/+files/simplescreenrecorder-2021-03-09_08.18.31.mkv

** Attachment added: "my mutter version"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+attachment/5475367/+files/Captura%20de%20pantalla%20de%202021-03-10%2012-36-23.png

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

Title:
  Window focus/clicking/moving failures for Xorg sessions in
  3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

[Leo]

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

** Description changed:

  Hello
  
  I'm trying to move the windows pulling it with the mouse, but is not
- possible. I need to use the righ click of the mouse on the border and
- select "Move"
+ possible. I need to use the righ click of the mouse on the upper border
+ and select "Move"

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

Title:
  I can't move the windows on Ubuntu 21.04

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the upper
  border and select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918273/+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 1918273] Re: I can't move the windows on Ubuntu 21.04

[Leo]

I'm not sure what the package associated with the problem might be, but
it's something related to window management.

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

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

Title:
  I can't move the windows on Ubuntu 21.04

Status in mutter package in Ubuntu:
  New

Bug description:
  Hello

  I'm trying to move the windows pulling it with the mouse, but is not
  possible. I need to use the righ click of the mouse on the border and
  select "Move"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918273/+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 1915207] Re: [critical for usability] complete crash/bug of fonts and icons on ubutntu thinkpad extreme 4K2021

[leo]

Another tasty capture :

** Attachment added: "new bug also.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1915207/+attachment/5462049/+files/new%20bug%20also.png

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

Title:
  [critical for usability] complete crash/bug of fonts and icons on
  ubutntu thinkpad extreme 4K2021

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  On lenevo thinkpad extme gen 2 with nvidia graphics and ubuntu 20.04.2

  All the menus text and the logging screen text is messed up and shows "whit 
noise" instead of the letters. The letters disapeard and the screen is left 
complitly unusable. I can not see where to click anymore because the "logout" 
"login" and "reboot" is also messed up. Clearly a big big prolem to me and my 
girlfriend on a 2600 euros machine.
  The problems appears on it's own after clean install so so problem is not on 
my ide. I did not mess anything up, because I just did an easy install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1915207/+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 1915207] [NEW] [critical for usability] complete crash/bug of fonts and icons on ubutntu thinkpad extreme 4K2021

[leo]

Public bug reported:

On lenevo thinkpad extme gen 2 with nvidia graphics and ubuntu 20.04.2

All the menus text and the logging screen text is messed up and shows "whit 
noise" instead of the letters. The letters disapeard and the screen is left 
complitly unusable. I can not see where to click anymore because the "logout" 
"login" and "reboot" is also messed up. Clearly a big big prolem to me and my 
girlfriend on a 2600 euros machine.
The problems appears on it's own after clean install so so problem is not on my 
ide. I did not mess anything up, because I just did an easy install.

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


** Tags: content driver glitch graphic ui warning

** Attachment added: "new bug.png"
   
https://bugs.launchpad.net/bugs/1915207/+attachment/5462048/+files/new%20bug.png

** Description changed:

  On lenevo thinkpad extme gen 2 with nvidia graphics and ubuntu 20.04.2
  
- All the menu abr text and the logging screen text is messed up and shows 
"whit noise" instead of the letters. The letters disapeard and the screen is 
left complitly unusable. I can not see where to click anymore because the 
"logout" "login" and "reboot" is also messed up. Clearly a big big prolem to me 
and my girlfriend on a 2600 euros machine. 
+ All the menus text and the logging screen text is messed up and shows "whit 
noise" instead of the letters. The letters disapeard and the screen is left 
complitly unusable. I can not see where to click anymore because the "logout" 
"login" and "reboot" is also messed up. Clearly a big big prolem to me and my 
girlfriend on a 2600 euros machine.
  The problems appears on it's own after clean install so so problem is not on 
my ide. I did not mess anything up, because I just did an easy install.

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

Title:
  [critical for usability] complete crash/bug of fonts and icons on
  ubutntu thinkpad extreme 4K2021

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  On lenevo thinkpad extme gen 2 with nvidia graphics and ubuntu 20.04.2

  All the menus text and the logging screen text is messed up and shows "whit 
noise" instead of the letters. The letters disapeard and the screen is left 
complitly unusable. I can not see where to click anymore because the "logout" 
"login" and "reboot" is also messed up. Clearly a big big prolem to me and my 
girlfriend on a 2600 euros machine.
  The problems appears on it's own after clean install so so problem is not on 
my ide. I did not mess anything up, because I just did an easy install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1915207/+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 1914187] [NEW] terminal interact too slow. Do many '/usr/bin/gnome-shell's affect to the problem?

[Leo Seo]

Public bug reported:

Terminal interaction takes too much time compared to the previous.
Not just on local device, but also with server connection

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb  2 16:47:33 2021
DisplayManager: lightdm
GsettingsChanges:
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
InstallationDate: Installed on 2020-07-17 (200 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  terminal interact too slow. Do many '/usr/bin/gnome-shell's affect to
  the problem?

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Terminal interaction takes too much time compared to the previous.
  Not just on local device, but also with server connection

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  2 16:47:33 2021
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  InstallationDate: Installed on 2020-07-17 (200 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914187/+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 1905717] Re: HDMI audio unusable after update to 13.99.1-1ubuntu3.8

[Leo Alekseyev]

After doing killall pulseaudio the sound seems back to normal. Marking
this as invalid until I collect more data.

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

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

Title:
  HDMI audio unusable after update to 13.99.1-1ubuntu3.8

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After a recent update of pulseaudio and related packages to
  13.99.1-1ubuntu3.8 on Ubuntu 20.04.1 LTS, audio via HDMI output became
  crackling and distorted, rendering my monitor speakers unusable. This
  is particularly frustrating because I cannot seem to roll back the
  update without uninstalling a good chunk of gnome(!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905717/+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 1905717] [NEW] HDMI audio unusable after update to 13.99.1-1ubuntu3.8

[Leo Alekseyev]

Public bug reported:

After a recent update of pulseaudio and related packages to
13.99.1-1ubuntu3.8 on Ubuntu 20.04.1 LTS, audio via HDMI output became
crackling and distorted, rendering my monitor speakers unusable. This is
particularly frustrating because I cannot seem to roll back the update
without uninstalling a good chunk of gnome(!)

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

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

Title:
  HDMI audio unusable after update to 13.99.1-1ubuntu3.8

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After a recent update of pulseaudio and related packages to
  13.99.1-1ubuntu3.8 on Ubuntu 20.04.1 LTS, audio via HDMI output became
  crackling and distorted, rendering my monitor speakers unusable. This
  is particularly frustrating because I cannot seem to roll back the
  update without uninstalling a good chunk of gnome(!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905717/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

[Leo Ramakersuca]

Daniel I successfully ran the dpkg process as you illustrated but it
then failed to boot, so now I must manually selected the 5.4 version in
order to get to this boot. Is there a way to reverse that?

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

[Leo Ramakersuca]

I found the information, at section 3.4 of the manual
https://dlcdnets.asus.com/pub/ASUS/LCD%20Monitors/PB287/PB287Q_English.pdf
where VESA / IBM Modes Support Timing (DP/HDMI) reaches 4k but CEA-861
Formats Supported Timing (HDMI/MHL) only reach 1920

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

[Leo Ramakersuca]

Regarding HDMI version the spec which I gave a link to claims;
True Resolution : 3840x2160 at 60Hz (DisplayPort) ,3840x2160 at 30Hz (HDMI) 

Some while ago I was researching this issue and found a specification
page on the ASUS website which showed two formats for declaring the
frame rate, one extended only to the 1920 value while the other went to
the full 4K. From this I deduced that perhaps windows uses one report
format while linux uses the other. I cannot locate that page now, it may
have been taken down.

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: i915 does not expose vendor-specific extended HDMI timings/modes

[Leo Ramakersuca]

Thanks for your work

I just bought and tried a new 4K hdmi cable, with no change. I noticed
that the monitor has TWO inputs, HDMI and HDMI/MHL (it had been plugged
into HDMI) but switching this to HDMI/MHL gave no result.

I am using MATE but the same issue occurs in several flavours of Ubuntu
that I have tried.

I dont know how to try the new kernel at 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/ as you requested. If I 
attempt to ask Gdebi to load the 
linux-image-unsigned-5.8.0-050800-generic_5.8.0-050800.202008022230_amd64.deb 
package from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/ it 
fails with unmet dependencies. 

kernel-modes.txt is attached

** Attachment added: "kernel-modes.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890418/+attachment/5399129/+files/kernel-modes.txt

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

Title:
  i915 does not expose vendor-specific extended HDMI timings/modes

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k

[Leo Ramakersuca]

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399093/+files/lspcik.txt

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

Title:
  External monitor will not display to 4k

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k

[Leo Ramakersuca]

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399094/+files/xrandr.txt

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

Title:
  External monitor will not display to 4k

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k

[Leo Ramakersuca]

Done. Thanks

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

Title:
  External monitor will not display to 4k

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] Re: External monitor will not display to 4k

[Leo Ramakersuca]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+attachment/5399092/+files/journal.txt

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

Title:
  External monitor will not display to 4k

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1890418] [NEW] External monitor will not display to 4k

[Leo Ramakersuca]

Public bug reported:

I have a Toshiba radius 11 laptop which has a 4 k native screen. I have
connected an Asus PB287Q 28" external monitor (https://www.asus.com/us
/Commercial-Monitors/PB287Q/specifications/) over HDMI which displays
the full 4K resolution when running under windows10 but will only reach
a maximum resolution of 1920x1080 under ubuntu 20.04, same hardware just
dual booting. Under Monitor Preferences this monitor is detected as an
"Ancor Communications inc 28" and the monitor preferences provides a
number of resolution steps up to 1920. If I issue "xrandr --addmode
HDMI-1 3840x2160" this resolution is added to the monitor preferences
pick list but attempting to apply it results in "the selected
configuration for displays could not ..." message

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

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

Title:
  External monitor will not display to 4k

Status in mutter package in Ubuntu:
  New

Bug description:
  I have a Toshiba radius 11 laptop which has a 4 k native screen. I
  have connected an Asus PB287Q 28" external monitor
  (https://www.asus.com/us/Commercial-Monitors/PB287Q/specifications/)
  over HDMI which displays the full 4K resolution when running under
  windows10 but will only reach a maximum resolution of 1920x1080 under
  ubuntu 20.04, same hardware just dual booting. Under Monitor
  Preferences this monitor is detected as an "Ancor Communications inc
  28" and the monitor preferences provides a number of resolution steps
  up to 1920. If I issue "xrandr --addmode HDMI-1 3840x2160" this
  resolution is added to the monitor preferences pick list but
  attempting to apply it results in "the selected configuration for
  displays could not ..." message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890418/+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 1882237] Re: Libre Office doesn't start at all (wrong library version)

[Leo Cacciari]

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

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882237/+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 1882237] Re: Libre Office doesn't start at all (wrong library version)

[Leo Cacciari]

Ok, I'm certified stupid and I'm sorry to have bothered people with
better things to do. It turns out, using lddtree, that what actually
depended on libicu version 63 was my personal copy of libboost-locale
that I keep, together with other boost library, in /usr/local for
development purposes. What I did was forgetting to re-compile the
libraries after update.

Please, update the status of this report to PIBKAC

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882237/+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 1882237] Re: Libre Office doesn't start at all (wrong library version)

[Leo Cacciari]

@hellsworth I tried your suggestion, but it didn't solve the problem: it
still complains that it can find the 63 version of libicui18n

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1882237/+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 1882237] [NEW] Libre Office doesn't start at all (wrong library version)

[Leo Cacciari]

Public bug reported:

I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

hobbit:~ $ lowriter
/usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: 
libicui18n.so.63: cannot open shared object file: No such file or directory

Now, the libicu is (obviously) installed, but the installed version is
66, not 63. Version 66, BTW, is the one listed as dependency for the
libre office package.

I do not exactly know when libreoffice stopped working after the update
to focal, as I do not use it extensively

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Jun  5 12:49:19 2020
InstallationDate: Installed on 2019-02-09 (481 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "output of ldd /usr/lib/libreoffice/program/soffice.bin"
   
https://bugs.launchpad.net/bugs/1882237/+attachment/5380662/+files/soffice.ldd

** Description changed:

- I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a 
- file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message: 
+ I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
+ file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:
  
- hobbit:~ $ lowriter 
+ hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory
  
  Now, the libicu is (obviously) installed, but the installed version is
- 66, not 63.
+ 66, not 63. Version 66, BTW, is the one listed as dependency for the
+ libre office package.
  
  I do not exactly know when libreoffice stopped working after the update
  to focal, as I do not use it extensively
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

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

Title:
  Libre Office doesn't start at all (wrong library version)

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm unable to start any of the libre office collection (writer, calc, etc). 
When trying to open a
  file the system goes busy for a little while (as shown by the pointer) then 
nothing happens. If I try from the menu nothing happens at all. Finally, if I 
try starting the component from the command line I get the following error 
message:

  hobbit:~ $ lowriter
  /usr/lib/libreoffice/program/soffice.bin: error while loading shared 
libraries: libicui18n.so.63: cannot open shared object file: No such file or 
directory

  Now, the libicu is (obviously) installed, but the installed version is
  66, not 63. Version 66, BTW, is the one listed as dependency for the
  libre office package.

  I do not exactly know when libreoffice stopped working after the
  update to focal, as I do not use it extensively

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Jun  5 12:49:19 2020
  InstallationDate: Installed on 2019-02-09 (481 days ago)
  InstallationMedia: Xubuntu 

[Desktop-packages] [Bug 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED

[Leo]

** Bug watch added: github.com/KhronosGroup/Vulkan-Tools/issues #403
   https://github.com/KhronosGroup/Vulkan-Tools/issues/403

** Also affects: mesa via
   https://github.com/KhronosGroup/Vulkan-Tools/issues/403
   Importance: Unknown
   Status: Unknown

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

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
  
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

  $ vkcube
  vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
  Аварийный останов (стек памяти сброшен на диск)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Apr 27 22:47:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-E
  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.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1875483/+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 1875483] Re: vulkan failed with ERROR_INITIALIZATION_FAILED

[Leo]

Got the same outputs:

vulkaninfo
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

vkcube
vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.

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

Title:
  vulkan failed with ERROR_INITIALIZATION_FAILED

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  1.The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  2. The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Установлен: 20.0.4-2ubuntu1
Кандидат:   20.0.4-2ubuntu1
Таблица версий:
   *** 20.0.4-2ubuntu1 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. What you expected to happen

  run vulkaninfo
  run vkcube

  4. What happened instead

  $ vulkaninfo
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_radeon.so: 
wrong ELF class: ELFCLASS32
  ERROR: [Loader Message] Code 0 : /usr/lib/i386-linux-gnu/libvulkan_intel.so: 
wrong ELF class: ELFCLASS32
  
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/vulkaninfo/vulkaninfo.h:477:
 failed with ERROR_INITIALIZATION_FAILED

  $ vkcube
  vkcube: 
/build/vulkan-tools-KEbD_A/vulkan-tools-1.2.131.1+dfsg1/cube/cube.c:3173: 
demo_init_vk: Assertion `!err' failed.
  Аварийный останов (стек памяти сброшен на диск)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vulkan-drivers 20.0.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Apr 27 22:47:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7560D] [1043:8526]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Oland XT [Radeon HD 8670 / R7 
250/350] [1458:226e]
  InstallationDate: Installed on 2020-04-23 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=24f6821a-8923-45d6-ad53-4f5250d5064a ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1801
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-E
  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.:bvr1801:bd12/14/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875483/+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 1878152] [NEW] no sound out of headphones

[Leo Cacciari]

Public bug reported:

Since upgrading to 20.04, when plugging an headphone with integrated
microphone in my Dell Vostro15 the system makes a display of changing
sounds settings (i.e. a volume bar is showed with the headphones sound
level) but no sound is coming out either from the headphones or the
system speakers.

Opening the audio mixer settings, I can see that the selected output
device is "Headphones (plugged in)" (the other displayed alternative
being "Speakers (plugged in)". The selected input device is "Microphone
(plugged in)" and there are two other alternatives: "Headset Microphone
(plugged in)" and "Internal Microphone (plugged in)".

If I change the setting for the *input* device from "Microphone" to
"Headset Microphone" sound magically starts coming out of the
headphones.

It may or may not be useful to remark that if I unplug the settings for output 
device changes to "Speakers (plugged in)" while the "Headphones" alternative is 
now correctly marked as unplugged and sound comes out of the speakers as 
expected. The situation for the input device, however, is slightly surprising:
 - If I changed the settings as described above the settings stay the same, 
i.e. "Headset microphone (plugged in)"
 - If I let the input device unchanged (i.e. "Microphone (plugged in)", it 
switches back to "Internal Microphone (plugged in)" while the "Microphone" 
device has its status reported as "unplugged".
In both cases, the input device "Headphone microphone" keeps the "plugged in" 
status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hobbit 1935 F pulseaudio
 /dev/snd/pcmC0D0c:   hobbit 1935 F...m pulseaudio
 /dev/snd/pcmC0D0p:   hobbit 1935 F...m pulseaudio
CasperMD5CheckResult: skip
Date: Tue May 12 08:52:12 2020
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2019-02-09 (457 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to focal on 2020-05-08 (3 days ago)
dmi.bios.date: 09/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0XT0D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd09/11/2017:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0XT0D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5568
dmi.product.sku: 0786
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

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

Title:
  no sound out of headphones

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrading to 20.04, when plugging an headphone with integrated
  microphone in my Dell Vostro15 the system makes a display of changing
  sounds settings (i.e. a volume bar is showed with the headphones sound
  level) but no sound is coming out either from the headphones or the
  system speakers.

  Opening the audio mixer settings, I can see that the selected output
  device is "Headphones (plugged in)" (the other displayed alternative
  being "Speakers (plugged in)". The selected input device is
  "Microphone (plugged in)" and there are two other alternatives:
  "Headset Microphone (plugged in)" and "Internal Microphone (plugged
  in)".

  If I change the setting for the *input* device from "Microphone" to
  "Headset Microphone" sound magically starts coming out of the
  headphones.

  It may or may not be useful to remark that if I unplug the settings for 
output device changes to "Speakers (plugged in)" while the "Headphones" 
alternative is now correctly marked as unplugged and sound comes out of the 
speakers as expected. The situation for the input device, however, is slightly 
surprising:
   - If I changed the settings as described above the settings stay the same, 
i.e. "Headset microphone (plugged in)"
   - If I let the input device unchanged (i.e. "Microphone (plugged in)", it 
switches back to "Internal Microphone (plugged in)" while the "Microphone" 
device has its status reported as "unplugged".
  In both cases, the input device "Headphone microphone" keeps the "plugged in" 
status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hobbit 1935 F pulseaudio
   

[Desktop-packages] [Bug 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session

[Leo]

The problem happens over dash-to-panel dropdowns.
See video:
https://yadi.sk/i/b5_2307WlAYRhQ

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

Title:
  Mouse cursor lagging (or freezing) when moving over system tray when
  wayland session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Cursor lagging when using wayland session. It happens on edge of something 
new, for example:
  - between clock menu and keyboard langugge
  - between app window and left launch panel

  Xorg session has no mouse lagging over this edges.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwayland-client0 1.18.0-1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 23:10:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600]
  InstallationDate: Installed on 2020-04-26 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 03PS.M505.20110929.LEO
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 305U1A/305U1A
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 03PS
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 305U1A
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 03PS
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876516/+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 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session

[Leo]

There was a video how it looks like.
https://github.com/home-sweet-gnome/dash-to-panel/issues/561

https://youtu.be/5g-_y9s1YaA

** Bug watch added: github.com/home-sweet-gnome/dash-to-panel/issues #561
   https://github.com/home-sweet-gnome/dash-to-panel/issues/561

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

Title:
  Mouse cursor lagging (or freezing) when moving over system tray when
  wayland session

Status in wayland package in Ubuntu:
  New

Bug description:
  Cursor lagging when using wayland session. It happens on edge of something 
new, for example:
  - between clock menu and keyboard langugge
  - between app window and left launch panel

  Xorg session has no mouse lagging over this edges.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwayland-client0 1.18.0-1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 23:10:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600]
  InstallationDate: Installed on 2020-04-26 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 03PS.M505.20110929.LEO
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 305U1A/305U1A
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 03PS
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 305U1A
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 03PS
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1876516/+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 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session

[Leo]

** Summary changed:

- Mouse cursor lagging (or freezing) when moving over system tray
+ Mouse cursor lagging (or freezing) when moving over system tray when wayland 
session

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

Title:
  Mouse cursor lagging (or freezing) when moving over system tray when
  wayland session

Status in wayland package in Ubuntu:
  New

Bug description:
  Cursor lagging when using wayland session. It happens on edge of something 
new, for example:
  - between clock menu and keyboard langugge
  - between app window and left launch panel

  Xorg session has no mouse lagging over this edges.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwayland-client0 1.18.0-1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 23:10:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600]
  InstallationDate: Installed on 2020-04-26 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 03PS.M505.20110929.LEO
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 305U1A/305U1A
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 03PS
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 305U1A
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 03PS
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1876516/+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 1876516] [NEW] Mouse cursor lagging (or freezing) when moving over system tray when wayland session

[Leo]

Public bug reported:

Cursor lagging when using wayland session. It happens on edge of something new, 
for example:
- between clock menu and keyboard langugge
- between app window and left launch panel

Xorg session has no mouse lagging over this edges.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libwayland-client0 1.18.0-1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  2 23:10:15 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600]
InstallationDate: Installed on 2020-04-26 (6 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
MonitorsUser.xml:
 
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7
SourcePackage: wayland
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 03PS.M505.20110929.LEO
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 305U1A/305U1A
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 03PS
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 305U1A
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 03PS
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu wayland-session

** Summary changed:

- mouse cursor lagging (or freezing) when moving over system tray
+ Mouse cursor lagging (or freezing) when moving over system tray

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

Title:
  Mouse cursor lagging (or freezing) when moving over system tray when
  wayland session

Status in wayland package in Ubuntu:
  New

Bug description:
  Cursor lagging when using wayland session. It happens on edge of something 
new, for example:
  - between clock menu and keyboard langugge
  - between app window and left launch panel

  Xorg session has no mouse lagging over this edges.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libwayland-client0 1.18.0-1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  2 23:10:15 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] 
(prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600]
  InstallationDate: Installed on 2020-04-26 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A
  MonitorsUser.xml:
   
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeSt

[Desktop-packages] [Bug 1875800] [NEW] Cannot choose which display dock shows on

[Leo S.]

Public bug reported:

I have two monitors both connected to one graphics card. Dock is showing
on both of them. I would like it to show only on the right side of the
left monitor.

I go to "Settings > Appearance > Dock > Show on".
I select the left monitor from the menu.
I expect the dock to disappear from the right monitor and show on the left.
Instead the dock stays on both monitors.

To be spesific what seems to happen is that selecting other option, eg.
AOC 27", from the menu makes the dock flash but the selection goes to
"All displays". Then if I select AOC 27" again the selection goes to
that but now the dock doesn't flash and it stays on both monitors.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 09:31:59 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-04-28 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Cannot choose which display dock shows on

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have two monitors both connected to one graphics card. Dock is
  showing on both of them. I would like it to show only on the right
  side of the left monitor.

  I go to "Settings > Appearance > Dock > Show on".
  I select the left monitor from the menu.
  I expect the dock to disappear from the right monitor and show on the left.
  Instead the dock stays on both monitors.

  To be spesific what seems to happen is that selecting other option,
  eg. AOC 27", from the menu makes the dock flash but the selection goes
  to "All displays". Then if I select AOC 27" again the selection goes
  to that but now the dock doesn't flash and it stays on both monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 29 09:31:59 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1875800/+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 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted

[Leo Wandersleb]

The most annoying part about this bug is that it leaves the user
guessing what's going on. I did not know if it is an issue with local or
remote system. Speculating that deleting excluded folders might be
triggering the issue etc.

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

Title:
  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted

Status in Déjà Dup:
  Triaged
Status in deja-dup package in Ubuntu:
  Triaged
Status in deja-dup package in Mandriva:
  New

Bug description:
  I've got my system set up with off-site backup over sftp. This works
  fine but the problem is that while deja-dup is gathering files and
  calculating the backup delta the connection to the server times out.
  This means that it's not available when deja-dup actually tries to
  push files to the server and results in this error message:

  Giving up after 5 attempts. Error: g-io-error-quark: The specified
  location is not mounted (16)

  By sitting in the file manager and jumping between folders the
  connection can be kept alive but that's rather annoying and requires
  my presence. Would really like to see deja-dup actually trying to set
  up the connection again instead.

  
  Using:
  Manjaro 16.06.1
  deja-dup 34.2-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1600299/+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 390001] Leo here

[Leo Petroski]

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

Title:
  Gnome visual effects not retained after reboot

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: yelp

  All of the settings specified in the gnome-appearance-properties
  applet are forgotten when a reboot occurs. This affects all of the
  windows transitions, mouse cursor sizes and colors, etc. Setting the
  values to the desired choices appears to take effect in the current
  session and all changes look fine. However on reboot, all settings
  return to the (presumable) defaults and none of the prior
  customization is retained. This occurs on version 9.04 (Jaunty) of
  UbuntuStudio.

  System details:

  System information report, generated by Sysinfo: 6/20/2009 4:03:26 PM
  http://sourceforge.net/projects/gsysinfo

  SYSTEM INFORMATION
Running Ubuntu Linux, the 5.0 release.
GNOME: 2.26.1 (Ubuntu 2009-05-06)
Kernel version: 2.6.28-3-rt (#12-Ubuntu SMP PREEMPT RT Fri Apr 17 
10:09:11 UTC 2009)
GCC: 4.3.3 (i486-linux-gnu)
Xorg: unknown (09 April 2009  02:10:02AM) (09 April 2009  02:10:02AM)
Hostname: esocid
Uptime: 0 days 2 h 20 min

  CPU INFORMATION
GenuineIntel, Intel(R) Pentium(R) 4 CPU 1300MHz
Number of CPUs: 1
CPU clock currently at 17000.000 MHz with 256 KB cache
Numbering: family(15) model(0) stepping(7)
Bogomips: 2594.02
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up pebs bts

  MEMORY INFORMATION
Total memory: 745 MB
Total swap: 2212 MB

  STORAGE INFORMATION
SCSI device -  scsi0
Vendor:  ATA  
Model:  WDC WD2500JB-00G 
SCSI device -  scsi0
Vendor:  ATA  
Model:  ST3160815A   
SCSI device -  scsi1
Vendor:  HL-DT-ST 
Model:  DVD-RAM GSA-H55L 
SCSI device -  scsi1
Vendor:  HL-DT-ST 
Model:  DVDRAM GSA-4163B 

  HARDWARE INFORMATION
  MOTHERBOARD
Host bridge
Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (MCH) 
(rev 02)
PCI bridge(s)
Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev 02)
Intel Corporation 82801 PCI Bridge (rev 02)
Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev 02)
Intel Corporation 82801 PCI Bridge (rev 02)
USB controller(s)
Intel Corporation 82801BA/BAM USB Controller #1 (rev 02)
Intel Corporation 82801BA/BAM USB Controller #1 (rev 02)
Intel Corporation 82801BA/BAM USB Controller #1 (rev 02)
Intel Corporation 82801BA/BAM USB Controller #1 (rev 02)
ISA bridge
Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
IDE interface
Intel Corporation 82801BA IDE U100 Controller (rev 02) (prog-if 
80 [Master])
Subsystem: Gateway 2000 Device 0063

  GRAPHIC CARD
VGA controller
ATI Technologies Inc Radeon R100 QD [Radeon 7200]
Subsystem: ATI Technologies Inc Device 0538

  SOUND CARD
Multimedia controller
Creative Labs SB Live! EMU10k1 (rev 07)
Subsystem: Creative Labs Device 8032

  NETWORK
Ethernet controller
National Semiconductor Corporation DP83815 (MacPhyter) Ethernet 
Controller
Subsystem: Netgear Device f311

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/bin/yelp
  Package: yelp 2.25.1-0ubuntu5
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: yelp
  Uname: Linux 2.6.28-3-rt i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/390001/+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 1801540]

[leo]

I was wondering about this as well. It looks like not everyone have the
exact same issue. For example, I have problems with sound input only
while other people reported sound problem with output as well.

I tried to gather and resume the reports given until now. I hope I
didn't made a mistake. The values "Yes", "No" and '"Same"' in the
"Input" and "Output" columns means "Does have the issue", "Does not have
the issue" and 'Reported "the same problem"' respectively.

Reporter   Input  Output Codec Motherboard
== =  == = 
icebalm[...]   YesNo ALC1220   ASUS CROSSHAIR VI HERO
Malte zu Klampen   "Same" "Same" ? ASUS PRIME X370-PRO
Luke Ricciolo  Yes"Same" ALC1220   ASUS CROSSHAIR VI HERO
Frédéric Pierret   "Same" "Same" ALC1220   ASROCK X370 GAMING K4
thomasg"Same" "Same" ALC1220   ASUS PRIME X370-PRO
Artem Hluvchynskyi ?  YesALC1220   ASROCK X370 GAMING K4
henk717[...]   YesNo ALC1220   MSI X370 Gaming Pro Carbon
aeder.redea[...]   YesNo ALC1220   ASUS ROG STRIX X470-F GAMING
Sebastian Hofmann  ?  YesALC1220   ASUS ROG STRIX X370-F GAMING
Luca   "Same" "Same" ALC892?
Axel   "Same" "Same" ? Gigabyte X470 AORUS
Parker H   "Same" "Same" ? Taichi X370
Marten "Same" "Same" ALC1220   Gigabyte GA-AX370-Gaming K3
evilphish[...] YesNo ALC1220   ASUS ROG CROSSHAIR VI HERO WiFi
Tomasz Pieczerak   YesNo ALC1220   Gigabyte B450 AORUS PRO
ben.schaaf[...]YesNo ALC887-VD ASUS PRIME B350-Plus
spychodelics[...]  "Same" "Same" ALC1220   ASUS PRIME X470-PRO
Anders ?  ?  ? ASUS PRIME X370-PRO
Rafael Rossi   YesYesALC1220   ASUS ROG STRIX X470-F GAMING
daxcore[...]   "Same" "Same" ALC1220   Micro-Star MEG X399 CREATION MS-7B92
wtravisjones[...]  "Same" "Same" ALC1220   ASRock B450 Gaming-ITX/ac
ZigZag "Same" "Same" ? ASUS ROG Strix B450-F
George Gibbs   "Same" "Same" ? ASUS ROG CROSSHAIR VI HERO
Marco  "Same" "Same" ALC892Gigabyte B450 AORUS ELITE
Benjamin Cheng Yes?  ? ASUS PRIME X470-PRO
Jon"Same" YesALC1220   MSI B450 Carbon Pro Gaming AC
Léo El AmriYesNo ALC1220   ASRock B450 Gaming-ITX/ac

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

[leo]

Frédéric Pierret was the first here to identify a possible origin for
the problem. And Marco did preliminary work on this. The "jcs way" looks
promising to me, but surely it requires a lot of work. I'm joining you
on the fact that we might never get help from Realtek on this, but I
don't think we should disregard community's effort :)

On my side, I also have a Realtek ALC1220 codec
Codec: Realtek ALC1220
Vendor Id: 0x10ec1220
Subsystem Id: 0x18492220
Revision Id: 0x100101
equipped on an ASRock B450 Gaming-ITX/ac motherboard ("AMD Promontory B450" 
chipset).
The sound coming out the green jack is OK.
The sound recorded from the microphone plugged on the pink jack is crackling.
I'm running Linux 4.19.44.

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 1808557] [NEW] package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

[Leo Germeys]

Public bug reported:

the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing 
instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. 
As a result I had to restart installation for updates several times.
Such disfunctioning occured a number of times before with the gui, so I was 
using apt instead, but as it was stated that the gui would be improved, I gave 
it a try.
It showed a large number of errors. Moreover it does not show any progress of 
what is going on during install of updates.  
In the small window it was stated that libnm-glib-vpn1:i386 would be in total 
bad shape so it should be removed and reinstalled. This is now done. But that 
seems only the result of  an instability occuring lately quite often with 
Ubuntu, starting with some larger uodate a couple of months ago. 
I know this is not a very precise description. I will now clean up the system 
starting with verifying all packages. The instability will probably remain 
though. 
In the process the gui was also updated and seems now to be functioning, so the 
version is now 
ubuntu-software 3.20.5-0ubuntu0 i386 . 
There are similar issues of being outphased  with libreoffice, evince and 
probably some more which we seldom use.
The common link between these errors is that contact with X is temporarily lost 
while free memory is low.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
Uname: Linux 4.4.0-140-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Fri Dec 14 15:49:36 2018
DuplicateSignature:
 package:libnm-glib-vpn1:i386:1.2.6-0ubuntu0.16.04.3
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
 dpkg: error processing package libnm-glib-vpn1:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-08-25 (476 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.103  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2017-08-25 (476 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
dlink-5C98  af76c1cc-4c5d-4991-af25-a2fdfd7a5b5c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: apport-package i386 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/1808557

Title:
  package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in network-manager package in Ubuntu:
  New

Bug description:
  the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing 
instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. 
As a result I had to restart installation for updates several times.
  Such disfunctioning occured a number of times before with the gui, so I was 
using apt instead, but as it was stated that the gui would be improved, I gave 
it a try.
  It showed a large number of errors. Moreover it does not show any progress of 
what is going on during install of updates.  
  In the 

[Desktop-packages] [Bug 1793441] [NEW] After blank screen I have to switch ctrl alt f2 ctrl alt f1 to get screen not blank again

[Leo Treasure]

Public bug reported:

After blank screen I have to switch ctrl alt f2 ctrl alt f1 to get
screen not blank again

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.18.5-041805-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 20 13:52:38 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 amdgpu, 18.30-641594, 4.15.0-34-generic, x86_64: installed
 amdgpu, 18.30-641594, 4.15.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] (rev 
c0) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 
64] [1002:6b76]
InstallationDate: Installed on 2018-04-27 (145 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.5-041805-generic 
root=UUID=9620a532-c2fe-49a3-8d3f-40e6c3b60bb0 ro quiet splash 
usbcore.autosuspend=-1 pci=noaer vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/10/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F10
dmi.board.asset.tag: Default string
dmi.board.name: X399 AORUS Gaming 7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF10:bd07/10/2018:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X399 AORUS Gaming 7
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  After blank screen I have to switch ctrl alt f2 ctrl alt f1 to get
  screen not blank again

Status in xorg package in Ubuntu:
  New

Bug description:
  After blank screen I have to switch ctrl alt f2 ctrl alt f1 to get
  screen not blank again

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.18.5-041805-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 20 13:52:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 18.30-641594, 4.15.0-34-generic, x86_64: installed
   amdgpu, 18.30-641594, 4.15.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX 
Vega 64] [1002:6b76]
  InstallationDate: Installed on 2018-04-27 (145 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.5-041805-generic 
root=UUID=9620a532-c2fe-49a3-8d3f-40e6c3b60bb0 ro quiet splash 
usbcore.autosuspend=-1 pci=noaer vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F10
  dmi.board.asset.tag: Default string
  

[Desktop-packages] [Bug 1764005] Re: Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu, Kubuntu

[Bryce Leo]

Broken again with kernel 4.15.0.22.23.

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

Title:
  Black-screen on boot with nvidia 390 for Budgie, MATE, Xubuntu,
  Kubuntu

Status in nvidia-prime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from Ubuntu Budgie 17.10 to 18.04.  After the plymouth splash
  left with a black screen.

  Purged all the nivdia-* packages and rebooted - graphical logon and
  logged in ok with nouveau.

  Tried software & updates to reinstall the nvidia 390 drivers.
  Rebooted.  Left at black screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nvidia-driver-390 390.48-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sat Apr 14 21:42:04 2018
  InstallationDate: Installed on 2016-11-26 (503 days ago)
  InstallationMedia: budgie-remix 16.10 "Budgie-remix" -  amd64 (20161013)
  SourcePackage: nvidia-graphics-drivers-390
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1764005/+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 1763924] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from o

[Leo]

Public bug reported:

while installing wine in the end i got this

 Errors were encountered while processing:
 
/tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Im using Lubantu 17.10 x64
1 gb RAM
Intel Pentium 4-2 core 3.20 MHz 3.20 MHz

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sat Apr 14 13:04:05 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental2ubuntu2.1
 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_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 2018-03-10 (34 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
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: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful 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/1763924

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 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:
  while installing wine in the end i got this

   Errors were encountered while processing:
   
/tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Im using Lubantu 17.10 x64
  1 gb RAM
  Intel Pentium 4-2 core 3.20 MHz 3.20 MHz

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Apr 14 13:04:05 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Qbn4VG/135-libsane1_1.0.27-1~experimental2ubuntu2.1_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 2018-03-10 (34 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  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: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package 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/1763924/+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 1754458] Re: nm-applet symbol not displayed on mate (18.04)

[Leo]

Hi,
This problem also affect other applications like shutter (it also appears if 
launched by root).
Thanks

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

Title:
  nm-applet symbol not displayed on mate (18.04)

Status in mate-desktop package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: 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.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-desktop/+bug/1754458/+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 1751954] Re: disabling wi-fi in power management options disables the wi-fi

[Leo Arias]

Oh, yes, very bad design :) Thanks for the info and the link Jeremy!

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

Title:
  disabling wi-fi in power management options disables the wi-fi

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  In the gnome-control-center, in the power section, there is a checkbox
  that says:

  Wi-Fi
  Turn off Wi-Fi to save power

  I have it checked, so after a few minutes without using my computer,
  the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked
  this box, but it disables my wi-fi immediately.

  So, it's obviously wrong to disable the wi-fi when I click that
  checkbox. And I don't seem to have a way to keep my wi-fi enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 18:27:16 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-04 (145 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=eo
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1751954/+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 1751954] Re: disabling wi-fi in power management options disables the wi-fi

[Leo Arias]

Same bug reported for redhat:
https://bugzilla.redhat.com/show_bug.cgi?id=1495433

** Bug watch added: Red Hat Bugzilla #1495433
   https://bugzilla.redhat.com/show_bug.cgi?id=1495433

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

Title:
  disabling wi-fi in power management options disables the wi-fi

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  In the gnome-control-center, in the power section, there is a checkbox
  that says:

  Wi-Fi
  Turn off Wi-Fi to save power

  I have it checked, so after a few minutes without using my computer,
  the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked
  this box, but it disables my wi-fi immediately.

  So, it's obviously wrong to disable the wi-fi when I click that
  checkbox. And I don't seem to have a way to keep my wi-fi enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 18:27:16 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-04 (145 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=eo
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1751954/+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 1751954] [NEW] disabling wi-fi in power management options disables the wi-fi

[Leo Arias]

Public bug reported:

In the gnome-control-center, in the power section, there is a checkbox
that says:

Wi-Fi
Turn off Wi-Fi to save power

I have it checked, so after a few minutes without using my computer, the
wi-fi is disabled. I want to keep my wi-fi working, so I unchecked this
box, but it disables my wi-fi immediately.

So, it's obviously wrong to disable the wi-fi when I click that
checkbox. And I don't seem to have a way to keep my wi-fi enabled.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.26.2-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 18:27:16 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-04 (145 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=eo
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago)

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


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

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

Title:
  disabling wi-fi in power management options disables the wi-fi

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  In the gnome-control-center, in the power section, there is a checkbox
  that says:

  Wi-Fi
  Turn off Wi-Fi to save power

  I have it checked, so after a few minutes without using my computer,
  the wi-fi is disabled. I want to keep my wi-fi working, so I unchecked
  this box, but it disables my wi-fi immediately.

  So, it's obviously wrong to disable the wi-fi when I click that
  checkbox. And I don't seem to have a way to keep my wi-fi enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 18:27:16 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-04 (145 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=eo
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (101 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1751954/+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 1743767] Re: Mouse click does not work

[Leo Treasure]

** Description changed:

  moving mouse is fine, clicking does nothing. Just upgraded some packages
  in 17.10
+ 
+ in the /var/log/Xorg.0.log:
+ 
+ config/udev: Adding input device Logitech G Pro Gaming Mouse 
(/dev/input/mouse0)
+ no input driver specified , ignoring this device
+ 
+ I wrote that out as I can't copy paste without clicking.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.15.0-041500rc3-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 20:35:20 2018
  DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
-Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
+  Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
+    Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
  InstallationDate: Installed on 2017-10-17 (92 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-18 (30 days ago)
  dmi.bios.date: 09/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3d
  dmi.board.asset.tag: Default string
  dmi.board.name: X399 AORUS Gaming 7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3d:bd09/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X399 AORUS Gaming 7
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.89+git1801121720.fd9bcb7~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
1:17.4~git180112172800.0eb30d8~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 
1:17.4~git180112172800.0eb30d8~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.10.99+git1801121842.1fe8ca7~a~padoka0
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1801121840.26f5406~a~padoka0
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Mouse click does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  moving mouse is fine, clicking does nothing. Just upgraded some
  packages in 17.10

  in the /var/log/Xorg.0.log:

  config/udev: Adding input device Logitech G Pro Gaming Mouse 
(/dev/input/mouse0)
  no input driver specified , ignoring this device

  I wrote that out as I can't copy paste without clicking.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.15.0-041500rc3-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 20:35:20 2018
  DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
  InstallationDate: Installed on 2017-10-17 (92 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash 

[Desktop-packages] [Bug 1743767] [NEW] Mouse click does not work

[Leo Treasure]

Public bug reported:

moving mouse is fine, clicking does nothing. Just upgraded some packages
in 17.10

in the /var/log/Xorg.0.log:

config/udev: Adding input device Logitech G Pro Gaming Mouse (/dev/input/mouse0)
no input driver specified , ignoring this device

I wrote that out as I can't copy paste without clicking.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
Uname: Linux 4.15.0-041500rc3-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 17 20:35:20 2018
DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] (rev 
c0) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
InstallationDate: Installed on 2017-10-17 (92 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2017-12-18 (30 days ago)
dmi.bios.date: 09/06/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3d
dmi.board.asset.tag: Default string
dmi.board.name: X399 AORUS Gaming 7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3d:bd09/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnX399AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX399AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: X399 AORUS Gaming 7
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.89+git1801121720.fd9bcb7~a~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 
1:17.4~git180112172800.0eb30d8~a~padoka0
version.libgl1-mesa-glx: libgl1-mesa-glx 
1:17.4~git180112172800.0eb30d8~a~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.10.99+git1801121842.1fe8ca7~a~padoka0
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1801121840.26f5406~a~padoka0
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful third-party-packages ubuntu wayland-session

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

Title:
  Mouse click does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  moving mouse is fine, clicking does nothing. Just upgraded some
  packages in 17.10

  in the /var/log/Xorg.0.log:

  config/udev: Adding input device Logitech G Pro Gaming Mouse 
(/dev/input/mouse0)
  no input driver specified , ignoring this device

  I wrote that out as I can't copy paste without clicking.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.15.0-041500rc3-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 17 20:35:20 2018
  DistUpgraded: 2017-12-18 13:27:58,717 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] [1002:687f] 
(rev c0) (prog-if 00 [VGA controller])
     Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega [Radeon RX Vega] 
[1002:6b76]
  InstallationDate: Installed on 2017-10-17 (92 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. X399 AORUS Gaming 7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc3-generic 
root=UUID=ffe04907-dda5-48e8-b717-b9a5fb224907 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2017-12-18 (30 days ago)
  dmi.bios.date: 09/06/2017
  dmi.bios.vendor: American Megatrends 

[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Gerard]

Proposed update fixed the issue, thanks.

product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation

$ apt policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 17.2.4-0ubuntu1~16.04.4
  Candidate: 17.2.4-0ubuntu1~16.04.4
  Version table:
 *** 17.2.4-0ubuntu1~16.04.4 400
400 http://fr.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 17.2.4-0ubuntu1~16.04.2 500
500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
 11.2.0-1ubuntu2 500
500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

I did not realize that the -dev packages were also updated and in the
proposed repository.  I understood from a post above that everything
would be pulled in when the libgl1-mesa-dri package was updated.  I did
look for -dev updates but I could not find a way to see any of the
packages themselves on archive.ubuntu.com

Everything installs with no dependency issues now although working the
mesa based graphics hard can still cause some problems, but no more than
on other systems built before 1/4/2018.

Thanks, LP

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

Already tried that:

***
sudo apt -f install libegl1-mesa-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libegl1-mesa-dev : Depends: libegl1-mesa (= 17.2.4-0ubuntu1~16.04.2) but 
17.2.4-0ubuntu1~16.04.3 is to be installed
Depends: libwayland-egl1-mesa (= 17.2.4-0ubuntu1~16.04.2) 
but 17.2.4-0ubuntu1~16.04.3 is to be installed
E: Unable to correct problems, you have held broken packages.
***

Trying with aptitude to get a solution gives:

***
The following actions will resolve these dependencies:

 Downgrade the following packages:  
1) libegl1-mesa [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16.04.2 (x
2) libgbm1 [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16.04.2 (xenial
3) libgl1-mesa-dri [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16.04.2
4) libwayland-egl1-mesa [17.2.4-0ubuntu1~16.04.3 (now) -> 17.2.4-0ubuntu1~16
***

The solution is to downgrade the 4 packages that fixed the graphics
problem!

So, the proposed fix is somehow incomplete.

LeoP

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

proposed did not fix

The compiz issue is resolved but the fix breaks other dependencies and
software (ROS for example)

Just upgrading libgl1-mesa-dri from ...16.04.2 to ...16.04.3 gives
dependency errors when installing other packages such as libegl1-mesa-
dev:

The following packages have unmet dependencies:
 libegl1-mesa-dev : Depends: libegl1-mesa (= 17.2.4-0ubuntu1~16.04.2) but 
17.2.4-0ubuntu1~16.04.3 is to be installed
Depends: libwayland-egl1-mesa (= 17.2.4-0ubuntu1~16.04.2) 
but 17.2.4-0ubuntu1~16.04.3 is to be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

It appears that the mirror I contact to still has not synced.  How do I
use "archive.ubuntu.com" ?

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Leo Pilachowski]

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

Thanks.  I saw that and that the comment on the "fix" was entered 8
minutes after my post above. But, I see there may be dependency problems
installing that fix.

LP

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  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: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Leo Pilachowski]

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

There appear to be two ppa locations to get the fix for 16.04 i386:

ppa: paulo-miguel-dias / pkppa

ppa:tjaalton/ppa

Please tell us again how to get and try out the possible fix.  I am
experienced but new to Ubuntu but need to get a older system up and
running asap on 16.04.

Leo

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  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: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net

[Desktop-packages] [Bug 1547297] Re: No auto login in Ubuntu GNOME Xenial

[Leo]

I have the same problem in Ubuntu 17.10. I configure in settings my user
to autologon in system but it don't works. If I type in a console:

cat /etc/gdm3/custom.conf | grep Auto

I have this:

AutomaticLoginEnable=True
AutomaticLogin=leo

I think that it's correct, but It don't login into my gnome xorg session

** Changed in: gdm3 (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  No auto login in Ubuntu GNOME Xenial

Status in Ubuntu GNOME:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in sddm package in Ubuntu:
  Confirmed

Bug description:
  Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto
  login during installation, but once the installation was complete and
  I booted into Ubuntu GNOME I was asked for my password. I looked in
  the user UI and auto login was set to off, so I unlocked it, selected
  auto login = on, clicked on lock again, and rebooted but was once
  again asked for my password and the user UI once again showed auto
  login = off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gdm3 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Feb 18 20:26:14 2016
  InstallationDate: Installed on 2016-02-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+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 1281580] Re: glib-compile-schemas doesn't compile relocatable schemas

[Leo Jiménez]

I have the same problem compiling relocatable schemas on override files
on Ubuntu MATE 16.04.

Manual configuration with 'gsettings set ...' work correctly.

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

Title:
  glib-compile-schemas doesn't compile relocatable schemas

Status in GLib:
  Confirmed
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Dear Developers,

  I am using the Ubuntu 14.04 development release with the GNOME Shell 3.10 
and, because my wife is using this system as well, I defined some settings in a 
gschema.override file.
  Everything is working right, except applying settings related to custom 
key-bindings.

  I added following lines my gschema.override file:
  [org.gnome.settings-daemon.plugins.media-keys]
  www='w'
  email='e'
  custom-keybindings = 
['/org/gnome/settings-daemon/plugins/media-keys/custom-keybinding/custom0']

  
[org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/]
  name = 'Launch Gedit'
  command = 'gedit'
  binding = 'g'

  I put my gschema.override file in the '/usr/share/glib-2.0/schemas' 
directory. After I added these lines, I ran 'glib-compile-schemas 
/usr/share/glib2.0/schemas' and no error was reported.
  For testing purposes I created a new user, logged out, and logged in with the 
new user. In the best case, the custom key-binding were applied automatically, 
but this has not happened. Other defined key-bindings were applied correctly.
  In the gnome-control-center's key-bindings tab, the table containing  custom 
shortcuts is empty, containing one row with empty columns.

  Running 'gsettings list-recursively org.gnome.settings-daemon.plugins
  .media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins
  /media-keys/custom-keybindings/custom0/' shows, the name, command, and
  binding key pairs contain empty ('') values.

  If I manually run following commands, the custom key-binding is created 
correctly:
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 name "Launch Gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 command "gedit"
  gsettings set 
org.gnome.settings-daemon.plugins.media-keys.custom-keybinding:/org/gnome/settings-daemon/plugins/media-keys/custom-keybindings/custom0/
 binding "g"

  Am I doing anything wrong when I want to add a custom key-bindings in
  my schema file, or  is 'glib-compile-schemas' really not applying this
  part from the schema file?

  Attila

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libglib2.0-bin 2.39.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.13.2-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 18 13:58:37 2014
  InstallationDate: Installed on 2013-12-13 (67 days ago)
  InstallationMedia: BeLin 3.02 i386
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1281580/+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 1700649] [NEW] MTP device fails to mount

[Leo]

Public bug reported:

In 17.04 thunar/gvfs is no longer able to access my phone over USB. (This 
worked fine in 16.10 with the same phone/android version.)
On connecting the phone the device shows up in Thunar and double clicking it 
shows the two folders (Internal Shared Storage and SD Card), however another 
window immediately pops up saying:
Failed to mount "E5823"
Unable to open MTP device '[usb:003,048]'
The phone will then pop up the dialog asking how to use the USD connection 
(charging or transfer files) like when initially connected. Choosing Transfer 
causes the device to show up again in Thunar, but the same thing happens again 
if trying to access it.

The output of dmesg shows lots of lines like:
usbfs: process 13035 (events) did not claim interface 0 before use
and a few lines like:
usbfs: process 12893 (pool) did not claim interface 0 before use
where the process id changes every time I reconnect the device.

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

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

Title:
  MTP device fails to mount

Status in gvfs package in Ubuntu:
  New

Bug description:
  In 17.04 thunar/gvfs is no longer able to access my phone over USB. (This 
worked fine in 16.10 with the same phone/android version.)
  On connecting the phone the device shows up in Thunar and double clicking it 
shows the two folders (Internal Shared Storage and SD Card), however another 
window immediately pops up saying:
  Failed to mount "E5823"
  Unable to open MTP device '[usb:003,048]'
  The phone will then pop up the dialog asking how to use the USD connection 
(charging or transfer files) like when initially connected. Choosing Transfer 
causes the device to show up again in Thunar, but the same thing happens again 
if trying to access it.

  The output of dmesg shows lots of lines like:
  usbfs: process 13035 (events) did not claim interface 0 before use
  and a few lines like:
  usbfs: process 12893 (pool) did not claim interface 0 before use
  where the process id changes every time I reconnect the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1700649/+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 1700571] [NEW] package thunderbird 1:52.1.1+build1-0ubuntu0.16.04.1 failed to install/upgrade: 套件 thunderbird 還無法設定 不能設定（目前狀態 `half-installed'）

[Leo Hsieh]

Public bug reported:

I don't know.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: thunderbird 1:52.1.1+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 thunderbird: Configure
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  leo1719 F pulseaudio
 /dev/snd/pcmC1D0p:   leo1719 F...m pulseaudio
 /dev/snd/controlC1:  leo1719 F pulseaudio
BuildID: 2017051014
Channel: Unavailable
Date: Mon Jun 26 16:55:53 2017
DpkgTerminalLog:
 dpkg: error processing package thunderbird (--configure):
  套件 thunderbird 還無法設定
  不能設定（目前狀態 `half-installed'）
ErrorMessage: 套件 thunderbird 還無法設定  不能設定（目前狀態 `half-installed'）
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-06-17 (9 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
IpRoute:
 default via 172.20.10.1 dev wlo1  proto static  metric 600 
 169.254.0.0/16 dev wlo1  scope link  metric 1000 
 172.20.10.0/28 dev wlo1  proto kernel  scope link  src 172.20.10.3  metric 600
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird 1:52.1.1+build1-0ubuntu0.16.04.1 failed to 
install/upgrade: 套件 thunderbird 還無法設定  不能設定（目前狀態 `half-installed'）
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M71 Ver. 01.01
dmi.board.name: 2216
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 96.52
dmi.chassis.asset.tag: 73436S20Y0
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM71Ver.01.01:bd12/03/2014:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009CD18002:rvnHewlett-Packard:rn2216:rvrKBCVersion96.52:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 840 G2
dmi.product.version: A3009CD18002
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package xenial

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

Title:
  package thunderbird 1:52.1.1+build1-0ubuntu0.16.04.1 failed to
  install/upgrade: 套件 thunderbird 還無法設定  不能設定（目前狀態 `half-installed'）

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I don't know.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   thunderbird: Configure
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leo1719 F pulseaudio
   /dev/snd/pcmC1D0p:   leo1719 F...m pulseaudio
   /dev/snd/controlC1:  leo1719 F pulseaudio
  BuildID: 2017051014
  Channel: Unavailable
  Date: Mon Jun 26 16:55:53 2017
  DpkgTerminalLog:
   dpkg: error processing package thunderbird (--configure):
套件 thunderbird 還無法設定
不能設定（目前狀態 `half-installed'）
  ErrorMessage: 套件 thunderbird 還無法設定  不能設定（目前狀態 `half-installed'）
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-06-17 (9 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  IpRoute:
   default via 172.20.10.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   172.20.10.0/28 dev wlo1  proto kernel  scope link  src 172.20.10.3  metric 
600
  NoProfiles: True
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird 1:52.1.1+build1-0ubuntu0.16.04.1 failed to 
install/upgrade: 套件 thunderbird 還無法設定  不能設定（目前狀態 `half-installed'）
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M71 Ver. 01.01
  dmi.board.name: 2216
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.52
  dmi.chassis.a

[Desktop-packages] [Bug 1495276] Re: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed.

[Leo Milano]

I guess this is obvious. But this bug still happens in Xenial.


lmilano@grisell:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"


lmilano@grisell:~$ dpkg -l |grep cups-client
ii  cups-client   2.1.3-4   
 amd64Common UNIX Printing System(tm) - client programs 
(SysV)


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

Title:
  cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free:
  Assertion `*_head == _item' failed.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  This crash just appeared during startup.
  Lots of CUPS updates and errors lately.
   Printer and scanner have worked mostly one way or the other using different 
apps.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: cups-daemon 2.1.0-1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AssertionMessage: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion 
`*_head == _item' failed.
  CrashCounter: 1
  Date: Sat Sep 12 22:57:48 2015
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2015-01-29 (226 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat:
   device for Brother-DCP-7065DN: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for Brother-DCP-7065DN-2: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for david@david-Lenovo-H535: 
dnssd://Brother%20DCP-7065DN._pdl-datastream._tcp.local/
   device for PDF: cups-pdf:/
  MachineType: LENOVO 10117
  Papersize: letter
  PpdFiles:
   david@david-Lenovo-H535: Brother DCP-7065DN, using brlaser v3
   PDF: Generic CUPS-PDF Printer
   Brother-DCP-7065DN-2: Brother DCP-7065DN, using brlaser v3
   Brother-DCP-7065DN: Brother DCP-7065DN, using brlaser v3
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  ProcEnviron:
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=94709fac-8bfa-41bf-8d29-24abdd9f77cc ro drm.debug=0xe plymouth:debug
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __assert_fail_base (fmt=0x7fed6ded1028 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fed6e80d132 "*_head == _item", 
file=file@entry=0x7fed6e80d117 "entrygroup.c", line=line@entry=245, 
function=function@entry=0x7fed6e80d3b0 "avahi_entry_group_free") at assert.c:92
   __GI___assert_fail (assertion=0x7fed6e80d132 "*_head == _item", 
file=0x7fed6e80d117 "entrygroup.c", line=245, function=0x7fed6e80d3b0 
"avahi_entry_group_free") at assert.c:101
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
  Title: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: 
Assertion `*_head == _item' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT31AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO
  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: 2014-04-16T18:25:57

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1495276/+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 1675445] Re: Cannot login to install snaps

[Leo Arias]

I tested this in a clean xenial vm up-to-date and could install and play
ohmygiraffe. There was an apport crash which I submitted, but it didn't
seem to affect the installation.

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

Title:
  Cannot login to install snaps

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I'm unable to login to gnome software on an up to date 16.04 system (a
  clean brand new dell xps laptop which has been dist-upgraded to latest
  packages in xenial)

  Currently have version 3.20.1+git20170208.0.a34b091-0ubuntu1~xenial1
  installed.

  When I try to login it just claims my password is wrong. This sounds
  like bug 1616943 which is apparently fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1675445/+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 1555567] Re: [snaps] License information from the store not available

[Leo Arias]

** Changed in: snapd-glib
   Status: In Progress => Confirmed

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

Title:
  [snaps] License information from the store not available

Status in snapd-glib:
  Confirmed
Status in Snappy:
  Confirmed
Status in Software Center Agent:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  While the store (and its API) has a field to specify the app's
  license, it seems to be ignored somewhere in its way to the client.

  As an example, ubuntu-calculator-app.ubuntucoredev has GPL3 set as its
  license in the store, yet in GNOME Software is tagged as "non-free"
  when listed in a search. Clicking on the package details in GNOME
  Software, the license type is shown as "Unknown"

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd-glib/+bug/167/+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 1555567] Re: [snaps] License information from the store not available

[Leo Arias]

Hey Robert, any progress here?

Harald's post became popular today:
https://apachelog.wordpress.com/2017/01/30/kde-applications-in-ubuntu-
snap-store/

Sadly, it has a prominent picture of this bug too :)

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

Title:
  [snaps] License information from the store not available

Status in snapd-glib:
  In Progress
Status in Snappy:
  Confirmed
Status in Software Center Agent:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  While the store (and its API) has a field to specify the app's
  license, it seems to be ignored somewhere in its way to the client.

  As an example, ubuntu-calculator-app.ubuntucoredev has GPL3 set as its
  license in the store, yet in GNOME Software is tagged as "non-free"
  when listed in a search. Clicking on the package details in GNOME
  Software, the license type is shown as "Unknown"

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd-glib/+bug/167/+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 1637606] [NEW] package liblirc-client0 0.9.4c-1 failed to install/upgrade: provo anstataŭigi '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', kiu ankaŭ estas en la pako liblirc

[Leo Arias]

Public bug reported:

I restarted my zesty machine, and this report popped up.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: liblirc-client0 0.9.4c-1
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Tue Oct 25 17:35:59 2016
Dependencies:
 gcc-6-base 6.2.0-8ubuntu1
 libc6 2.24-3ubuntu1
 libgcc1 1:6.2.0-8ubuntu1
ErrorMessage: provo anstataŭigi 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', kiu ankaŭ estas en la pako 
liblircclient0:amd64 0.9.0-0ubuntu6
InstallationDate: Installed on 2016-06-03 (147 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160525)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: lirc
Title: package liblirc-client0 0.9.4c-1 failed to install/upgrade: provo 
anstataŭigi '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', kiu ankaŭ estas en 
la pako liblircclient0:amd64 0.9.0-0ubuntu6
UpgradeStatus: Upgraded to zesty on 2016-10-23 (4 days ago)

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

Title:
  package liblirc-client0 0.9.4c-1 failed to install/upgrade: provo
  anstataŭigi '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', kiu ankaŭ
  estas en la pako liblircclient0:amd64 0.9.0-0ubuntu6

Status in lirc package in Ubuntu:
  New

Bug description:
  I restarted my zesty machine, and this report popped up.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblirc-client0 0.9.4c-1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 25 17:35:59 2016
  Dependencies:
   gcc-6-base 6.2.0-8ubuntu1
   libc6 2.24-3ubuntu1
   libgcc1 1:6.2.0-8ubuntu1
  ErrorMessage: provo anstataŭigi 
'/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', kiu ankaŭ estas en la pako 
liblircclient0:amd64 0.9.0-0ubuntu6
  InstallationDate: Installed on 2016-06-03 (147 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160525)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: lirc
  Title: package liblirc-client0 0.9.4c-1 failed to install/upgrade: provo 
anstataŭigi '/usr/lib/x86_64-linux-gnu/liblirc_client.so.0', kiu ankaŭ estas en 
la pako liblircclient0:amd64 0.9.0-0ubuntu6
  UpgradeStatus: Upgraded to zesty on 2016-10-23 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1637606/+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 1625877] Re: VLC screen always on top

[Leo Lee]

Christopher M. Penalver
Sorry about that, I test again with 16.10(daily build)
and 14.04 with same hardware.
everything work normally.

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

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC

  the interface disappeared while minimum VLC (video playing)
  video screen remains only

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  Reference:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 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 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1191
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877/+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 1165382] Re: No sound output/input to Plantronics .Audio 478 USB

[Leo Yuriev]

UPDATE: working after disabling the Intel HD on motherboard, seem bug in
Pulseaudio UI.

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

Title:
  No sound output/input to Plantronics .Audio 478 USB

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Plantronics .Audio 478 USB works well with Ubuntu 12.04.
  Ubuntu 13.04 beta2 has option for sound output to it but really sound outputs 
to standart laptop speakers.
  There is no Plantronics .Audio 478 in input devices list and sound input not 
work from it.

  lsusb:
  Bus 003 Device 004: ID 047f:c011 Plantronics, Inc.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu4b2
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 4416 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3483 F pulseaudio
    ubuntu 4416 F pulseaudio
   /dev/snd/pcmC0D0c:   ubuntu 3483 F...m pulseaudio
  CasperVersion: 1.330
  Date: Sat Apr  6 11:57:20 2013
  ExecutablePath: /usr/bin/pulseaudio
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5110
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1165382/+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 1165382] Re: No sound output/input to Plantronics .Audio 478 USB

[Leo Yuriev]

16.04, now sound is ok, but no input from microphone.

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

Title:
  No sound output/input to Plantronics .Audio 478 USB

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Plantronics .Audio 478 USB works well with Ubuntu 12.04.
  Ubuntu 13.04 beta2 has option for sound output to it but really sound outputs 
to standart laptop speakers.
  There is no Plantronics .Audio 478 in input devices list and sound input not 
work from it.

  lsusb:
  Bus 003 Device 004: ID 047f:c011 Plantronics, Inc.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu4b2
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 4416 F pulseaudio
   /dev/snd/controlC0:  ubuntu 3483 F pulseaudio
    ubuntu 4416 F pulseaudio
   /dev/snd/pcmC0D0c:   ubuntu 3483 F...m pulseaudio
  CasperVersion: 1.330
  Date: Sat Apr  6 11:57:20 2013
  ExecutablePath: /usr/bin/pulseaudio
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5110
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1165382/+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 1625877] Re: VLC screen always on top

[Leo Lee]

I test this on Yakkety Yak in VirtualBox, works normally.
Maybe it's resolved.

Last version of Ubuntu I used is 14.04.
I remembered vlc works normally, but not the same computer.

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

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC

  the interface disappeared while minimum VLC (video playing)
  video screen remains only

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  Reference:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 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 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1191
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877/+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 1537053] Re: vlc screen always on top, buggly.

[Leo Lee]

Thanks, Christopher.
here is the new report
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877

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

Title:
  vlc screen always on top, buggly.

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I don't know  whether it's due to 15.10 or due to my laptop being a very new 
model "Asus Zenbook 305CA".
  The screen is always on top. Even if it is minimized.
  The gif below takes may some ten seconds to load.
  http://imgur.com/N3AZkiH

  And in addition, the video quality is sensibly worse than it should
  be, compared to Totem video player which functions properly.

  vlc revision 2.2.1-0-ga425c42
  ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053/+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 1625877] Re: VLC screen always on top

[Leo Lee]

** Description changed:

  After new installed VLC on 16.04
- The screen always only while playing video with VLC
+ The video screen always on top only while playing with VLC
  
- The title bar and the bottom bar will disappear while minimum VLC
+ the interface disappeared while minimum VLC (video playing)
+ video screen remains only
  
  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"
  
  in Preference > Video > Display
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
-Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
+  Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
+    Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
  InstallationDate: Installed on 2016-09-01 (19 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 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd 
-  Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
-  Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd
+  Bus 001 Device 004: ID 8087:0a2b Intel Corp.
+  Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: SY Series
  dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: SY Series
  dmi.product.version: Not Applicable
  dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 20 22:21:24 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id1191 
-  vendor LGD
+  product id1191
+  vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2.3

** Description changed:

  After new installed VLC on 16.04
  The video screen always on top only while playing with VLC
  
  the interface disappeared while minimum VLC (video playing)
  video screen remains only
  
  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"
  
  in Preference > Video > Display
+ 
+ Reference:
+ 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1625877] [NEW] VLC screen always on top

[Leo Lee]

Public bug reported:

After new installed VLC on 16.04
The screen always only while playing video with VLC

The title bar and the bottom bar will disappear while minimum VLC

but the situation is fixed after canceled the option
"Accelerated video output(Overlay)"

in Preference > Video > Display

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Sep 21 09:23:57 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588]
InstallationDate: Installed on 2016-09-01 (19 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 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd 
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: COPELION INTERNATIONAL CO., LTD. SY Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed 
root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: SY Series
dmi.board.vendor: COPELION INTERNATIONAL CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: SY Series
dmi.product.version: Not Applicable
dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Sep 20 22:21:24 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1191 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 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/1625877

Title:
  VLC screen always on top

Status in xorg package in Ubuntu:
  New

Bug description:
  After new installed VLC on 16.04
  The screen always only while playing video with VLC

  The title bar and the bottom bar will disappear while minimum VLC

  but the situation is fixed after canceled the option
  "Accelerated video output(Overlay)"

  in Preference > Video > Display

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 21 09:23:57 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake 

[Desktop-packages] [Bug 1537053] Re: vlc screen always on top, buggly.

[Leo Lee]

I have the same problem on my laptop with 16.04
CPU i5-6600
GPU HD 530

but the situation is fixed after canceled the option
"Accelerated video output(Overlay)"

in Preference > Video > Display

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

Title:
  vlc screen always on top, buggly.

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I don't know  whether it's due to 15.10 or due to my laptop being a very new 
model "Asus Zenbook 305CA".
  The screen is always on top. Even if it is minimized.
  The gif below takes may some ten seconds to load.
  http://imgur.com/N3AZkiH

  And in addition, the video quality is sensibly worse than it should
  be, compared to Totem video player which functions properly.

  vlc revision 2.2.1-0-ga425c42
  ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053/+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 1622394] [NEW] vlc playback flicker and has delays

[Leo Kalovyrnas]

Public bug reported:

Your system is providing 3D via software rendering rather than hardware
rendering.  This is a compatibility mode which should display 3D
graphics properly but the performance may be very poor.  If the problem
you're reporting is related to graphics performance, your real question
may be why X didn't use hardware acceleration for your system.

ubuntu 16.04 LTS 
Intel® Core™2 CPU 6420 @ 2.13GHz × 2 
Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Sep 11 22:19:56 2016
DistUpgraded: 2016-09-11 12:24:34,299 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cedar [Radeon HD 
5000/6000/7350/8350 Series] [174b:e164]
InstallationDate: Installed on 2012-12-11 (1370 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=150153c9-a663-4cf4-b335-3e170c2f4845 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-09-11 (0 days ago)
dmi.bios.date: 07/03/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-VM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0901:bd07/03/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-VM:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Sep 11 21:01:07 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Microsoft Wireless Optical Desktop® 2.10 KEYBOARD, id 8
 inputMicrosoft Microsoft Wireless Optical Desktop® 2.10 KEYBOARD, id 9
 input2.4G wireless Mouse  MOUSE, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 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/1622394

Title:
  vlc playback flicker and has delays

Status in xorg package in Ubuntu:
  New

Bug description:
  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  ubuntu 16.04 LTS 
  Intel® Core™2 CPU 6420 @ 2.13GHz × 2 
  Gallium 0.4 on llvmpipe (LLVM 3.8, 128 bits)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 

[Desktop-packages] [Bug 1574586] Re: Not able to rate/review snaps

[Leo Arias]

** Changed in: snappy
   Status: New => Confirmed

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

Title:
  Not able to rate/review snaps

Status in Snappy:
  Confirmed
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Snaps are not able to be rated/reviewed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1574586/+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 1577316] Re: LibreOffice Base Crash when i try to connect to mysql

[Leo Gaggl]

Is there a work-around for this issue ?

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

Title:
  LibreOffice Base Crash when i try to connect to mysql

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to my mysql database via libreoffice base , this
  one closes it without providing crash report.

  
  lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  apt-cache policy libreoffice-base
  libreoffice-base:
Installé : 1:5.1.2-0ubuntu1
Candidat : 1:5.1.2-0ubuntu1
   
  apt-cache policy libreoffice-mysql-connector 
  libreoffice-mysql-connector:
Installé : 1.0.2+LibO5.1.2-0ubuntu1
Candidat : 1.0.2+LibO5.1.2-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1577316/+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 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.

[Leo Iz]

#34 fixed the problem. Thank you Ryan Lux!

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

Title:
  Shows "Chromium isn't your default browser" since 15.10.

Status in Chromium Browser:
  New
Status in chromium-browser package in Ubuntu:
  In Progress
Status in google-chrome package in Ubuntu:
  Confirmed
Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  Since the 15.10.  upgrade Chromium shows on every launch "Chromium
  isn't your default browser", even when i select "Set as default" or
  "Don't ask again".

  Chromium is set as default application for "Web" at System Settings ->
  Details -> Default Applications.

  Version 45.0.2454.101 Ubuntu 15.10 (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1509139/+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 1547994] [NEW] package libreoffice-report-builder (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Leo Moseley]

Public bug reported:

There is no conclusive pointer to a reason for the crash.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libreoffice-report-builder (not installed)
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sat Feb 20 12:18:53 2016
DuplicateSignature: package:libreoffice-report-builder:(not 
installed):dependency problems - leaving triggers unprocessed
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2016-02-20 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: libreoffice
Title: package libreoffice-report-builder (not installed) failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package wily

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

Title:
  package libreoffice-report-builder (not installed) failed to
  install/upgrade: dependency problems - leaving triggers unprocessed

Status in libreoffice package in Ubuntu:
  New

Bug description:
  There is no conclusive pointer to a reason for the crash.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libreoffice-report-builder (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sat Feb 20 12:18:53 2016
  DuplicateSignature: package:libreoffice-report-builder:(not 
installed):dependency problems - leaving triggers unprocessed
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-02-20 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: libreoffice
  Title: package libreoffice-report-builder (not installed) failed to 
install/upgrade: dependency problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1547994/+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 1504698] Re: NetworkManager crashes after reboot

[Leo Milano]

Just a quick note.This problem persists after the official release of
15.10.

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+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 1504698] Re: NetworkManager crashes after reboot

[Leo Milano]

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

An automatic comment stating that this bug is a duplicate has been
added, but the allegedely original bug doesn't seem to exist.

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+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 1504698] [NEW] NetworkManager crashes after reboot

[Leo Milano]

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

Public bug reported:

I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
boot, NetworkManager crashes and I get the popup to send a bug report
for a NM crash. There is no network, either. Restarting the
NetworkManager service from a terminal fixes the issue ... until next
reboot :)

~$ sudo service NetworkManager restart

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
Uname: Linux 4.2.0-15-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Oct  9 16:39:39 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 10.0.0.1 dev wlan0  proto static  metric 600 
 10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
nmcli-dev:
 DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
 wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  -- 
   ---- 

 lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  -- 
   ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-crash wily

** Information type changed from Private to Public

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage 

[Desktop-packages] [Bug 1504698] Re: NetworkManager crashes after reboot

[Leo Milano]

** This bug is no longer a duplicate of private bug 1500399

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

Title:
  NetworkManager crashes after reboot

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my HP Chromebook 14  from 15.04 to 15.10 beta. After cold
  boot, NetworkManager crashes and I get the popup to send a bug report
  for a NM crash. There is no network, either. Restarting the
  NetworkManager service from a terminal fixes the issue ... until next
  reboot :)

  ~$ sudo service NetworkManager restart

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Oct  9 16:39:39 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 600 
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.38  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   wlan0wifi  connected /org/freedesktop/NetworkManager/Devices/2  
MilanoFamily  fbced2d1-aa52-4d01-81dd-9f56594e0911  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   ttyUSB0  gsm   disconnected  /org/freedesktop/NetworkManager/Devices/3  
------  
   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
------
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+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 1471563] Re: I can't type messages in the chat function when installing thunderbird-locale-zh-hant.

[Leo]

** Changed in: thunderbird (Ubuntu)
 Assignee: Leo (x50908) = (unassigned)

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

Title:
  I can't type messages in the chat function when installing
  thunderbird-locale-zh-hant.

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I use chat function to send messages to my facebook friends in the
  Windows thunderbird version very well. However, I do the same thing in
  the Linux Ubuntu, and it can be a nightmare! There's no space to type
  the messages!

  After asking for the Ubuntu community, I think this is a bug.

  ※The most important thing is, this bug only appear when you install the 
language pack thunderbird-locale-zh-hant!
  ※There is no problem when installing other language pack.

  The release of Ubuntu : unspecified
  The version of the package : unspecified

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1471563/+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 1471563] [NEW] I can't type messages in the chat function when installing thunderbird-locale-zh-hant.

[Leo]

Public bug reported:

I use chat function to send messages to my facebook friends in the
Windows thunderbird version very well. However, I do the same thing in
the Linux Ubuntu, and it can be a nightmare! There's no space to type
the messages!

After asking for the Ubuntu community, I think this is a bug.

※The most important thing is, this bug only appear when you install the 
language pack thunderbird-locale-zh-hant!
※There is no problem when installing other language pack.

The release of Ubuntu : unspecified
The version of the package : unspecified

** Affects: thunderbird (Ubuntu)
 Importance: Undecided
 Assignee: Leo (x50908)
 Status: New


** Tags: languagepack traditionalchinese

** Attachment added: There's no space to type the messages!
   
https://bugs.launchpad.net/bugs/1471563/+attachment/4424595/+files/2015-02-16-19-58-00-d33393.png

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) = Leo (x50908)

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

Title:
  I can't type messages in the chat function when installing
  thunderbird-locale-zh-hant.

Status in thunderbird package in Ubuntu:
  New

Bug description:
  I use chat function to send messages to my facebook friends in the
  Windows thunderbird version very well. However, I do the same thing in
  the Linux Ubuntu, and it can be a nightmare! There's no space to type
  the messages!

  After asking for the Ubuntu community, I think this is a bug.

  ※The most important thing is, this bug only appear when you install the 
language pack thunderbird-locale-zh-hant!
  ※There is no problem when installing other language pack.

  The release of Ubuntu : unspecified
  The version of the package : unspecified

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1471563/+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 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90

[Leo Francisco]

I'm also experiencing this. Quite frustrating.


I'm on 15.04 and GNOME 3.16 with the gnome3-team and gnome3-staging PPA's.


Only thing to add this message in terminal every time I hit the non functional 
brightness keys:

(gnome-settings-daemon:13855): media-keys-plugin-WARNING **: No existing
D-Bus connection trying to handle power keys

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

Title:
  Media, brightness and volume keys don't work with GNOME 3.15.90

Status in GNOME Shell:
  Incomplete
Status in Ubuntu GNOME:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu 15.04 Vivid to use GNOME 3.15.90 (by using
  gnome3-team/gnome3, gnome3-team/gnome3-staging ppas) media, brightness
  and volume keys from my laptop keyboard stop to work after working
  some time in a session or after suspending the computer.

  If I restart my computer media keys work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.15.90-0ubuntu1~vivid1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  3 23:07:33 2015
  InstallationDate: Installed on 2014-10-22 (132 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140923)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1427877/+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 1422004] Re: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'

[Leo Milano]

Thank you, Till, I was looking for the proper place to change the tag :)

Cheers,
Leo

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

Title:
  pkservice.py crashed with AttributeError in __init__(): 'module'
  object has no attribute 'MainLoop'

Status in HP Linux Imaging and Printing:
  Fix Committed
Status in hplip package in Ubuntu:
  Fix Released
Status in hplip source package in Vivid:
  Fix Committed

Bug description:
  If an HP printer needs HPLIP with HP's proprietary plug-in (firmware
  files for printers, proprietary driver code pieces for printing and/or
  scanning) the automatically initiated installation of the plug-in
  fails and causes crash reports, leading to crash report pop-ups and
  non-working printing and scanning functionality. The problem is caused
  by the switchover from Python2 to Python3 in Vivid, especially also
  that the Python3 executable is named python3 and not python.

  If the crash happens shortly before shutdown or reboot the pop-up can
  appear right after log-in.

  [Impact]

  All Vivid users who use a printer or multi-function device which needs
  HP's proprietary plug-in get crash pop-ups and their devices will not
  completely work or not work at all.

  [Test Case]

  Connect an HP printer or multi-function device which needs the plug-in
  (for which models see this bug report and the numerous duplicates) and
  set it up. As soon as the plug-in gets downloaded and installed, crash
  reports pop up, and the devices functionality which needs the plug-in
  will not work as plug-in installation does not complete.

  The proposed package solves the problem.

  To test without having an appropriate printer, simply run the command

  hp-plugin

  in a terminal window. With the current package it will fail as
  mentioned, with the proposed package plug-in installation will
  succeed.

  [Regression Potential]

  Very low. The patch is trivial and it affects only users who need the
  plug-in. All users of other HP printers or non-HP printers are not
  affected.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: hplip-data 3.15.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog: E [14/Feb/2015:19:56:52 +0100] Unable to open listen socket for 
address [v1.::1]:631 - Cannot assign requested address.
  Date: Sat Feb 14 05:59:51 2015
  ExecutablePath: /usr/share/hplip/pkservice.py
  InstallationDate: Installed on 2014-05-08 (282 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.4
  Lpstat:
   device for HP-Deskjet-1000-J110-series: 
usb://HP/Deskjet%201000%20J110%20series?serial=CN33A18VXG05YD
   device for PDF: cups-pdf:/
  MachineType: Acer Aspire 5943G
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   HP-Deskjet-1000-J110-series: HP Deskjet 1000 j110 Series, hpcups 3.15.2
   PDF: Generic CUPS-PDF Printer
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-pkservice
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=e9be64c9-5b7e-438a-ac82-6b89bf946a86 ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/bin/hp-pkservice']
  SourcePackage: hplip
  Title: pkservice.py crashed with AttributeError in __init__(): 'module' 
object has no attribute 'MainLoop'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 10/21/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5943G
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 5943G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1422004/+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 1422004] Re: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'

[Leo Milano]

Hi

I enabled 'proposed' vivid updates, installed hplip 3.15.2-0ubuntu4.1 ,
and I could successfully run the hp-plugin component. As far as my local
machine goes, the package fixes the issue.

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

Title:
  pkservice.py crashed with AttributeError in __init__(): 'module'
  object has no attribute 'MainLoop'

Status in HP Linux Imaging and Printing:
  Fix Committed
Status in hplip package in Ubuntu:
  Fix Released
Status in hplip source package in Vivid:
  Fix Committed

Bug description:
  If an HP printer needs HPLIP with HP's proprietary plug-in (firmware
  files for printers, proprietary driver code pieces for printing and/or
  scanning) the automatically initiated installation of the plug-in
  fails and causes crash reports, leading to crash report pop-ups and
  non-working printing and scanning functionality. The problem is caused
  by the switchover from Python2 to Python3 in Vivid, especially also
  that the Python3 executable is named python3 and not python.

  If the crash happens shortly before shutdown or reboot the pop-up can
  appear right after log-in.

  [Impact]

  All Vivid users who use a printer or multi-function device which needs
  HP's proprietary plug-in get crash pop-ups and their devices will not
  completely work or not work at all.

  [Test Case]

  Connect an HP printer or multi-function device which needs the plug-in
  (for which models see this bug report and the numerous duplicates) and
  set it up. As soon as the plug-in gets downloaded and installed, crash
  reports pop up, and the devices functionality which needs the plug-in
  will not work as plug-in installation does not complete.

  The proposed package solves the problem.

  To test without having an appropriate printer, simply run the command

  hp-plugin

  in a terminal window. With the current package it will fail as
  mentioned, with the proposed package plug-in installation will
  succeed.

  [Regression Potential]

  Very low. The patch is trivial and it affects only users who need the
  plug-in. All users of other HP printers or non-HP printers are not
  affected.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: hplip-data 3.15.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
  Uname: Linux 3.16.0-22-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog: E [14/Feb/2015:19:56:52 +0100] Unable to open listen socket for 
address [v1.::1]:631 - Cannot assign requested address.
  Date: Sat Feb 14 05:59:51 2015
  ExecutablePath: /usr/share/hplip/pkservice.py
  InstallationDate: Installed on 2014-05-08 (282 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.4
  Lpstat:
   device for HP-Deskjet-1000-J110-series: 
usb://HP/Deskjet%201000%20J110%20series?serial=CN33A18VXG05YD
   device for PDF: cups-pdf:/
  MachineType: Acer Aspire 5943G
  PackageArchitecture: all
  Papersize: a4
  PpdFiles:
   HP-Deskjet-1000-J110-series: HP Deskjet 1000 j110 Series, hpcups 3.15.2
   PDF: Generic CUPS-PDF Printer
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-pkservice
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-22-generic 
root=UUID=e9be64c9-5b7e-438a-ac82-6b89bf946a86 ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/bin/hp-pkservice']
  SourcePackage: hplip
  Title: pkservice.py crashed with AttributeError in __init__(): 'module' 
object has no attribute 'MainLoop'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 10/21/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5943G
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.15
  dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15:
  dmi.product.name: Aspire 5943G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1422004/+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 1448794] [NEW] hp-plugin needs /usr/bin/python to point to python3*

[Leo Milano]

Public bug reported:

After upgrading to Vivid, my HP LaserJet M1212nf MFP would not work
anymore, and trying to install the binary driver, as prompted by the
HPLIP utility would fail. After fiddling for a good hour, I realized
that the utility was failing to load the python modules for hplip:


$ gksu hp-plugin

[ ... ]

Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
Error importing HPLIP modules.  Is HPLIP installed?


I changed to /usr/bin, and noticed that python was a symlink to
python2.7; I temporarily made it be a symlink to python3.4, and I
managed to install the proprietary plugin for my printer. However, other
software would crash, so I reverted to have the symlink pointing to the
old python2.7 location.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: hplip 3.15.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-15.15-lowlatency 3.19.3
Uname: Linux 3.19.0-15-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 26 16:13:19 2015
Lpstat:
 device for HP_COLOR_LaserJet: hp:/net/HP_LaserJet_200_color_M251nw?zc=NPI6A3827
 device for HP_LaserJet_Professional_M1212nf_MFP: 
hp:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ4316YPR1a
MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
Papersize: letter
PpdFiles:
 HP_COLOR_LaserJet: HP LaserJet 200 color M251 Postscript (recommended)
 HP_LaserJet_Professional_M1212nf_MFP: HP LaserJet Professional m1212nf MFP, 
hpcups 3.15.2, requires proprietary plugin
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-lowlatency 
root=UUID=edc6b677-0e99-4da6-83b8-12f019053f9f ro quiet splash vt.handoff=7
SourcePackage: hplip
UpgradeStatus: Upgraded to vivid on 2014-04-12 (378 days ago)
dmi.bios.date: 08/12/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-D3HP-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: Z87-D3HP
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  hp-plugin needs /usr/bin/python to point to python3*

Status in hplip package in Ubuntu:
  New

Bug description:
  After upgrading to Vivid, my HP LaserJet M1212nf MFP would not work
  anymore, and trying to install the binary driver, as prompted by the
  HPLIP utility would fail. After fiddling for a good hour, I realized
  that the utility was failing to load the python modules for hplip:

  
  $ gksu hp-plugin

  [ ... ]

  Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
  Error importing HPLIP modules.  Is HPLIP installed?
  

  I changed to /usr/bin, and noticed that python was a symlink to
  python2.7; I temporarily made it be a symlink to python3.4, and I
  managed to install the proprietary plugin for my printer. However,
  other software would crash, so I reverted to have the symlink pointing
  to the old python2.7 location.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-15.15-lowlatency 3.19.3
  Uname: Linux 3.19.0-15-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 16:13:19 2015
  Lpstat:
   device for HP_COLOR_LaserJet: 
hp:/net/HP_LaserJet_200_color_M251nw?zc=NPI6A3827
   device for HP_LaserJet_Professional_M1212nf_MFP: 
hp:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ4316YPR1a
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  Papersize: letter
  PpdFiles:
   HP_COLOR_LaserJet: HP LaserJet 200 color M251 Postscript (recommended)
   HP_LaserJet_Professional_M1212nf_MFP: HP LaserJet Professional m1212nf MFP, 
hpcups 3.15.2, requires proprietary plugin
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-lowlatency 
root=UUID=edc6b677-0e99-4da6-83b8-12f019053f9f ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to vivid on 2014-04-12 (378 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  

Re: [Desktop-packages] [Bug 1437692] Re: cups-browsed crashed with SIGABRT in __GI_____strtof_l_internal()

[Leo Milano]

Yes, indeed, the crashes are not happening anymore, sorry, I should have
updated this.
On Apr 13, 2015 9:11 AM, Till Kamppeter 1437...@bugs.launchpad.net
wrote:

 Most probably fixed in cups-browsed 1.0.67-0ubuntu2. Please update and
 re-open this bug if you still have problems.

 ** Information type changed from Private to Public

 ** Changed in: cups-filters (Ubuntu)
Status: New = Fix Released

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1437692

 Title:
   cups-browsed crashed with SIGABRT in __GI_strtof_l_internal()

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1437692/+subscriptions


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

Title:
  cups-browsed crashed with SIGABRT in __GI_strtof_l_internal()

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  Cups seems to be crashing as I reboot the machine, using the latest
  development Vivid packages.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-lowlatency 3.19.2
  Uname: Linux 3.19.0-9-lowlatency x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Mar 20 21:18:28 2015
  ExecutablePath: /usr/sbin/cups-browsed
  Lpstat:
   device for HP_COLOR_LaserJet: 
ipps://grisell.local:631/printers/HP_COLOR_LaserJet
   device for HP_LaserJet_Conectada_a_Grisell: 
ipps://grisell.local:631/printers/HP_LaserJet_Conectada_a_Grisell
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Papersize: letter
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-lowlatency 
root=UUID=0b932d1f-e9f1-43b9-9031-506b5e14f40b ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __GI_strtof_l_internal (nptr=0x305 error: Cannot access memory at 
address 0x305, endptr=0x305, group=6, loc=0x3066653138303230) at strtod_l.c:644
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? ()
   ?? ()
   ?? ()
  Title: cups-browsed crashed with SIGABRT in __GI_strtof_l_internal()
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A68HM-H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd12/02/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A68HM-H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1437692/+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 1441893] Re: Can't connect to my wi-fi: authentication timed out

[Leo Arias]

** Description changed:

  I can't connect to my wi-fi with my laptop.
  
  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out
  
  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
-   *-network   
-description: Ethernet interface
-product: Ethernet Connection I217-V
-vendor: Intel Corporation
-physical id: 19
-bus info: pci@:00:19.0
-logical name: eth0
-version: 05
-serial: 00:90:f5:f8:ef:86
-size: 1Gbit/s
-capacity: 1Gbit/s
-width: 32 bits
-clock: 33MHz
-capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
-configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
-resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
-   *-network
-description: Wireless interface
-product: Wireless 3160
-vendor: Intel Corporation
-physical id: 0
-bus info: pci@:03:00.0
-logical name: wlan0
-version: 83
-serial: a0:88:69:39:ae:d6
-width: 64 bits
-clock: 33MHz
-capabilities: bus_master cap_list ethernet physical wireless
-configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
-resources: irq:32 memory:f7c0-f7c01fff
+   *-network
+    description: Ethernet interface
+    product: Ethernet Connection I217-V
+    vendor: Intel Corporation
+    physical id: 19
+    bus info: pci@:00:19.0
+    logical name: eth0
+    version: 05
+    serial: 00:90:f5:f8:ef:86
+    size: 1Gbit/s
+    capacity: 1Gbit/s
+    width: 32 bits
+    clock: 33MHz
+    capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
+    configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
+    resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
+   *-network
+    description: Wireless interface
+    product: Wireless 3160
+    vendor: Intel Corporation
+    physical id: 0
+    bus info: pci@:03:00.0
+    logical name: wlan0
+    version: 83
+    serial: a0:88:69:39:ae:d6
+    width: 64 bits
+    clock: 33MHz
+    capabilities: bus_master cap_list ethernet physical wireless
+    configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
+    resources: irq:32 memory:f7c0-f7c01fff
  
  Attached is the full syslog.
- This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working. 
- Recently I changed the network from N to G, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
+ This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
+ Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.
  
  I'm connecting to the same network using the same password with my other
  machine.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
  IpRoute:
-  default via 192.168.2.1 dev eth0  proto static  metric 1024 
-  169.254.0.0/16 dev eth0  scope link  metric 1000 
-  192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
+  default via 192.168.2.1 dev eth0  proto static  metric 1024
+  169.254.0.0/16 dev eth0  scope link  metric 1000
+  

[Desktop-packages] [Bug 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out

[Leo Arias]

I could connect to the G network on utopic, so this is a regression.

** Summary changed:

- Can't connect to my wi-fi N network: authentication timed out
+ Can't connect to my wi-fi N network on vivid: authentication timed out

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

Title:
  Can't connect to my wi-fi N network on vivid: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1441893/+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 1441893] Re: Can't connect to my wi-fi N network on vivid: authentication timed out

[Leo Arias]

sorry, scratch that last comment. It should have been:

I could connect to the N network on utopic, so this is a regression.

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

Title:
  Can't connect to my wi-fi N network on vivid: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1441893/+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 1441893] Re: Can't connect to my wi-fi N network: authentication timed out

[Leo Arias]

I switched the network back to G, and I can connect.

** Summary changed:

- Can't connect to my wi-fi: authentication timed out
+ Can't connect to my wi-fi N network: authentication timed out

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

Title:
  Can't connect to my wi-fi N network: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
    *-network
     description: Ethernet interface
     product: Ethernet Connection I217-V
     vendor: Intel Corporation
     physical id: 19
     bus info: pci@:00:19.0
     logical name: eth0
     version: 05
     serial: 00:90:f5:f8:ef:86
     size: 1Gbit/s
     capacity: 1Gbit/s
     width: 32 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
     resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
    *-network
     description: Wireless interface
     product: Wireless 3160
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:03:00.0
     logical name: wlan0
     version: 83
     serial: a0:88:69:39:ae:d6
     width: 64 bits
     clock: 33MHz
     capabilities: bus_master cap_list ethernet physical wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
     resources: irq:32 memory:f7c0-f7c01fff

  Attached is the full syslog.
  This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working.
  Recently I changed the network from G to N, and recently did an upgrade to 
the latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
  I've just tested with a daily vivid live USB, and the same problem happened.

  I'm connecting to the same network using the same password with my
  other machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.356
  CurrentDesktop: Unity
  Date: Wed Apr  8 22:20:03 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static  metric 1024
   169.254.0.0/16 dev eth0  scope link  metric 1000
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2
   wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1441893/+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 1441893] [NEW] Can't connect to my wi-fi: authentication timed out

[Leo Arias]

Public bug reported:

I can't connect to my wi-fi with my laptop.

I get this error message in the syslog.
Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

ubuntu@ubuntu:~$ lshw -c network
WARNING: you should run this program as super-user.
  *-network   
   description: Ethernet interface
   product: Ethernet Connection I217-V
   vendor: Intel Corporation
   physical id: 19
   bus info: pci@:00:19.0
   logical name: eth0
   version: 05
   serial: 00:90:f5:f8:ef:86
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 32 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 
100bt 100bt-fd 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=e1000e 
driverversion=2.3.2-k duplex=full firmware=0.12-3 ip=192.168.2.208 latency=0 
link=yes multicast=yes port=twisted pair speed=1Gbit/s
   resources: irq:29 memory:f7e0-f7e1 memory:f7e3d000-f7e3dfff 
ioport:f080(size=32)
  *-network
   description: Wireless interface
   product: Wireless 3160
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlan0
   version: 83
   serial: a0:88:69:39:ae:d6
   width: 64 bits
   clock: 33MHz
   capabilities: bus_master cap_list ethernet physical wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=3.19.0-10-generic firmware=25.15.12.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11abgn
   resources: irq:32 memory:f7c0-f7c01fff

Attached is the full syslog.
This machine has been working more or less ok on vivid for at least three 
months. Sometimes it refused to connect to the wi-fi, but after a restart it 
started working. 
Recently I changed the network from N to G, and recently did an upgrade to the 
latest vivid. I had some problems booting, so I also recently fully removed 
upstart. It boots fine with systemd, and everything else seem to be working.
I've just tested with a daily vivid live USB, and the same problem happened.

I'm connecting to the same network using the same password with my other
machine.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu11
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CasperVersion: 1.356
CurrentDesktop: Unity
Date: Wed Apr  8 22:20:03 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.2.1 dev eth0  proto static  metric 1024 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.208
LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 eth0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Wired connection 1  cf5cb021-0df1-4f13-b74c-c3e9c6749a30  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 wlan0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  --  
----
 
 lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  --  
----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug vivid

** Attachment added: syslog
   https://bugs.launchpad.net/bugs/1441893/+attachment/4369887/+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/1441893

Title:
  Can't connect to my wi-fi: authentication timed out

Status in network-manager package in Ubuntu:
  New

Bug description:
  I can't connect to my wi-fi with my laptop.

  I get this error message in the syslog.
  Apr  8 22:25:35 ubuntu kernel: [  793.89] wlan0: authentication with 
10:bf:48:e5:d1:b8 timed out

  ubuntu@ubuntu:~$ lshw -c network
  WARNING: you should run this program as super-user.
*-network   
 description: Ethernet interface
 product: Ethernet Connection I217-V
 

[Desktop-packages] [Bug 399466] Re: Creating image checksum message not informative anough

[Leo Z]

Message is still the same in xubuntu 14.04.2 using brasero.
It is misleading. I cancelled the process and the disc came out just as fine.

** Attachment added: Screenshot of the message (in spanish)
   
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/399466/+attachment/4361407/+files/Screenshot%20-%20300315%20-%2019%3A15%3A02.png

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

Title:
  Creating image checksum message not informative anough

Status in brasero package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: brasero

  brasero 2.26.1-0ubuntu1
  Ubuntu 9.04

  I burned an ISO file to a DVD+RW.

  After burning there was a step labeled Creating image checksum.
  This is not very clear (unless you are an experienced brasero user).

  As I understand, it is reading back the disc content to verify the
  burn was without errors.

  The message should be changed to be more clear.

  Users care what is done (verification), not how it is done (by
  computing and comparing a checksum - I guess).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/399466/+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 1435631] [NEW] Diagnose

[Leo Villanueva]

Public bug reported:

error reports during diagnose

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Mar 24 08:53:25 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3a02]
   Subsystem: Lenovo Device [17aa:3a02]
InstallationDate: Installed on 2015-03-21 (2 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 (20150218.1)
MachineType: LENOVO Lenovo 3000 G430
ProcEnviron:
 LANGUAGE=en_PH:en
 PATH=(custom, no user)
 LANG=en_PH.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=fcd1e9c0-69eb-4fbd-a159-dcfe476bcff8 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/04/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 0ECN57WW
dmi.board.name: LE6
dmi.board.vendor: Lenovo
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: 
dmi:bvnLENOVO:bvr0ECN57WW:bd03/04/2009:svnLENOVO:pnLenovo3000G430:pvrRev1.0:rvnLenovo:rnLE6:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: Lenovo 3000 G430
dmi.product.version: Rev 1.0
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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: Tue Mar 24 07:40:00 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1409 
 vendor BOE
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  Diagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  error reports during diagnose

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Mar 24 08:53:25 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3a02]
 Subsystem: Lenovo Device [17aa:3a02]
  InstallationDate: Installed on 2015-03-21 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 
(20150218.1)
  MachineType: LENOVO Lenovo 3000 G430
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=fcd1e9c0-69eb-4fbd-a159-dcfe476bcff8 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0ECN57WW
  dmi.board.name: LE6
  dmi.board.vendor: Lenovo
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr0ECN57WW:bd03/04/2009:svnLENOVO:pnLenovo3000G430:pvrRev1.0:rvnLenovo:rnLE6:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: Lenovo 3000 G430
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 

[Desktop-packages] [Bug 1435631] Re: Diagnose

[Leo Villanueva]

Getting to know Ubuntu.As a first time user I am confident enough that
Ubuntu OS will teach me a lot about computing .Patience is the key word
here.Not that easy but in due time I will get the hang of it.Thanks a
lot guys for giving this out for free..

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

Title:
  Diagnose

Status in xorg package in Ubuntu:
  New

Bug description:
  error reports during diagnose

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Mar 24 08:53:25 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3a02]
 Subsystem: Lenovo Device [17aa:3a02]
  InstallationDate: Installed on 2015-03-21 (2 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release i386 
(20150218.1)
  MachineType: LENOVO Lenovo 3000 G430
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=fcd1e9c0-69eb-4fbd-a159-dcfe476bcff8 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0ECN57WW
  dmi.board.name: LE6
  dmi.board.vendor: Lenovo
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr0ECN57WW:bd03/04/2009:svnLENOVO:pnLenovo3000G430:pvrRev1.0:rvnLenovo:rnLE6:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: Lenovo 3000 G430
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  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: Tue Mar 24 07:40:00 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1409 
   vendor BOE
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1435631/+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 562423] Re: gnome-keyring-manager interferes with the VNC server

[Leo]

Hit this issue today trying to enable vino from a remote ssh terminal. Took me 
half a day to figure out that the server side popped up the keyring window 
causing TightVnc client to hang during authentication.
Sad :(

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

Title:
  gnome-keyring-manager interferes with the VNC server

Status in GNOME Remote Desktop:
  New
Status in vino package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: vino

  Actual configuration

  PC A : Ubuntu Lucid Lynx (upgraded from an updated 09.10) with distant 
desktop enabled
  PC B : Another OS with vncviewer

  After the first start of PC A, if I launch vncviewer on PC B with
  correct login/password to view the PC A desktop, vncviewer waits for
  the connection acceptation. I have to go to the PC A and enter my user
  password in the gnome-keyring-manager window that appeared after the
  first connect attempt of PC B. After password acceptation, PC B
  vncviewer is able to connect/disconnect without any problems.

  Why vncserver needs my user password to know it's own password ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/vino/+bug/562423/+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