date:20180527

[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gdm greeter does not allow non-US characters (like euro character €)
  when typing password

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

Bug description:
  In latest Artful (2017-09-08 daily), gdm does not allow to enter the
  euro character (€) when typing the password (be it with the real
  keyboard or with the visual on screen keyboard).

  Steps to reproduce:
  1. on the gdm login screen, try to type € in the password field
  2. the input is ignored (not big dot is added)
  3. if your password contains a € symbol (which is allowed, incliding during 
installation with ubiquity), you cannot login anymore...

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

Manfred Steiner:

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

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

To use your table to further clarify:

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773484] Re: Login screen not moved to used monitor

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

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773484] Re: Login screen not moved to used monitor

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

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-05-27 Thread Sum Sim

When are you gonna fix this bug? It says "Fix committed", but the bug is
still exist. I can't login to my Xubuntu like a month already!

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1766137/+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 1691032] Re: Some PCs still turn off the backlight by zero brightness even when the maximum brightness level is less than 100

2018-05-27 Thread Yuan-Chen Cheng

** Changed in: oem-priority/xenial
   Status: New => Triaged

** Changed in: oem-priority/xenial
   Importance: High => Medium

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

Title:
  Some PCs still turn off the backlight by zero brightness even when the
  maximum brightness level is less than 100

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in Unity Settings Daemon:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  Need to have fix in Bionic, better to have it in xenial.

  The minimum brightness of the laptop screen panel may not be realistic
  sometimes especially when having a problematic screen panel.

  For example, Dell Precision 5720 AIO only has 9 levels in
  /sys/class/backlight/intel_backlight/max_brightness because the wrong
  settings in VBIOS. It is an all-in-one desktop PC and there is no
  brightness hotkey to control the backlight. When we set 0 to
  /sys/class/backlight/intel_backlight/brightness, it turns off the
  panel's backlight and there is no way to brightness up the backlight
  again so we can only avoid using 0 as the minimum backlight level.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1691032/+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 1773597] Re: USB flash drive won't mount

2018-05-27 Thread Roy Kimbrell

After a reboot, inserted encrypted USB flash drive (32G Lexar). Waited
about 15 minutes and the request for the password was displayed. I
entered the password, but nothing happened. Waited five minutes - then
rebooted with the drive still inserted. It was not recognized (by
Nautilus) upon completion of the reboot. Removed and inserted and it was
eventually recognized, but no window asking for a password showed until
I opened the "file cabinet" and clicked on the drive listed on the left.
A request for password then appeared. I entered the password and was
able to open the drive. However after about ten minutes, I could not
open any files - a lock icon appeared on the file icon. Removed the USB
flash drive and rebooted.

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

Title:
  USB flash drive won't mount

Status in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1

  Ubuntu version: Ubuntu 18.04 LTS, software is up to date

  Steps to create problem:

  1. Reboot
  2. Insert USB flash drive

  USB flash drive does not appear on desktop or in Nautilus file window

  dmesg | tail

  [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
  [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c
  [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 1435.685765] usb 2-1.3: Product: USB Flash Drive
  [ 1435.685766] usb 2-1.3: Manufacturer: Lexar
  [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF

  lsusb

  Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card
  Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
  Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
  Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. 
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 0c45:640f Microdia 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1773597/+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 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

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

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2 [error: implicit declaration of function
  ‘init_timer’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+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 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

** Summary changed:

- nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 
4.15.0-1.2
+ nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 
4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

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

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

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2 [error: implicit declaration of function
  ‘init_timer’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/amd64/n/nvidia-graphics-drivers-304/20171212_030744_5105c@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/n/nvidia-graphics-drivers-304/20171212_014232_5105c@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+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 1773518] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build

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

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


** This bug has been marked a duplicate of bug 1737750
   nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 
4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

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

Title:
  nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed
  to build

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

Bug description:
  it occurred when i updated my kernel headers and image to 4.10.42

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.104-0ubuntu3
  Uname: Linux 4.10.0-42-generic SMP x86_64

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.104-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Είναι κατάλογος: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.104  Thu Sep 14 17:13:13 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog: /dev/sda1: clean, 299125/7331840 files, 2066528/29304931 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.15.0-15-generic
  Date: Sat May 26 12:36:00 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-42-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-127-generic, x86_64: installed
   nvidia-340, 340.104, 4.10.0-42-generic, x86_64: installed
   nvidia-340, 340.104, 4.4.0-127-generic, x86_64: installed
  DuplicateSignature: 
dkms:nvidia-340:340.104-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-340/340.104/build/nv.c:2407:5:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK106 [GeForce GTX 660] [1043:8423]
  InstallationDate: Installed on 2018-05-21 (4 days ago)
  InstallationMedia: Ubuntu4Kitchen 16.04.2 amd64 "Ubuntu4Kitchen"
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD P35 Platinum(MS-7345)
  PackageVersion: 340.104-0ubuntu0.16.04.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=e4843b8c-6d2a-40cd-9a8f-8d05ed3be539 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P35 Platinum(MS-7345)
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd12/30/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnP35Platinum(MS-7345):pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnP35Platinum(MS-7345):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: P35 Platinum(MS-7345)
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs:

[Desktop-packages] [Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

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

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

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

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

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

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

** Tags added: nouveau

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

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

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

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

  See bugs here:

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

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

-- 
Mailing list: https://launchpad.net/~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 1773549] Re: Pulse audio does not remember default sink

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

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

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  Triaged

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

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

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

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

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

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

  But this doesn't have any effect at all.

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

Yes, I am aware of the mouse pointer being less efficient in Wayland
sessions. That's covered by bug 1690719.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1734887] Re: No caps lock indicator on login screen

Upstreams:
https://gitlab.gnome.org/GNOME/gdm/issues/326
https://bugzilla.gnome.org/show_bug.cgi?id=762881

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

** Bug watch added: GNOME Bug Tracker #762881
   https://bugzilla.gnome.org/show_bug.cgi?id=762881

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=762881
   Importance: Unknown
   Status: Unknown

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Changed in: unity-greeter (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No caps lock indicator on login screen

Status in GNOME Shell:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  Expected results: Pressing the Caps Lock key should cause an indicator
  to appear on the login screen.

  Actual results: Pressing the Caps Lock key does not cause the login
  screen to change in any way.

  Reproducing:

  1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Lock key, see no 
indicator. (gdm3 3.26.1-3ubuntu3)
  2. Install Fedora 27 Workstation ISO and log in, press Caps Lock key, see an 
indicator. (gdm-3.26.2.1-1.fc27.x86_64)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  Uname: Linux 4.14.2-041402-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Nov 28 08:24:31 2017
  InstallationDate: Installed on 2017-11-05 (22 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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/gnome-shell/+bug/1734887/+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 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

Thanks. That explains a lot. I think gnome-shell is presently too slow
to be able to handle 1080p on a Celeron 847. But we are working on a
bunch of different optimizations that should help in future.

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1773597] Re: USB flash drive won't mount

2018-05-27 Thread Roy Kimbrell

Tried ...

 apt-get install --reinstall nautilus
 
No change. Still cannot mount USB flash drives.

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

Title:
  USB flash drive won't mount

Status in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1

  Ubuntu version: Ubuntu 18.04 LTS, software is up to date

  Steps to create problem:

  1. Reboot
  2. Insert USB flash drive

  USB flash drive does not appear on desktop or in Nautilus file window

  dmesg | tail

  [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
  [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c
  [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 1435.685765] usb 2-1.3: Product: USB Flash Drive
  [ 1435.685766] usb 2-1.3: Manufacturer: Lexar
  [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF

  lsusb

  Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card
  Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
  Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
  Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. 
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 0c45:640f Microdia 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

2018-05-27 Thread pavel kkkko

Private bug reported:

/

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

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


** Tags: amd64 apport-package bionic

** Information type changed from Public to Private

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

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

Status in libxml2 package in Ubuntu:
  New

Bug description:
  /

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

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

-- 
Mailing list: https://launchpad.net/~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 1773597] Re: USB flash drive won't mount

2018-05-27 Thread Roy Kimbrell

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

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

Title:
  USB flash drive won't mount

Status in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  New

Bug description:
  [0.00] Linux version 4.15.0-22-generic (buildd@lgw01-amd64-013) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #24-Ubuntu SMP Wed May 16 12:15:17 UTC 
2018 (Ubuntu 4.15.0-22.24-generic 4.15.17)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=870f1d77-345c-44b2-99e6-79adea07159c ro quiet splash vt.handoff=1

  Ubuntu version: Ubuntu 18.04 LTS, software is up to date

  Steps to create problem:

  1. Reboot
  2. Insert USB flash drive

  USB flash drive does not appear on desktop or in Nautilus file window

  dmesg | tail

  [ 1435.463032] usb 2-1.3: new high-speed USB device number 8 using ehci-pci
  [ 1435.685760] usb 2-1.3: New USB device found, idVendor=05dc, idProduct=c75c
  [ 1435.685763] usb 2-1.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 1435.685765] usb 2-1.3: Product: USB Flash Drive
  [ 1435.685766] usb 2-1.3: Manufacturer: Lexar
  [ 1435.685767] usb 2-1.3: SerialNumber: D2036779FCE9EDC016EF

  lsusb

  Bus 002 Device 007: ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth 
Mini-card
  Bus 002 Device 006: ID 413c:8158 Dell Computer Corp. Integrated Touchpad / 
Trackstick
  Bus 002 Device 005: ID 413c:8157 Dell Computer Corp. Integrated Keyboard
  Bus 002 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
  Bus 002 Device 008: ID 05dc:c75c Lexar Media, Inc. 
  Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 003: ID 0c45:640f Microdia 
  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1773597/+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 113338] Re: Cannot close a tab in Gedit by middle clicking the tab bar

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

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

Title:
  Cannot close a tab in Gedit by middle clicking the tab bar

Status in gedit:
  New
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  See title. This is in 7.04 final. It is inconsistent with Firefox's
  behavior.

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

2018-05-27 Thread DSHR

Syslog output from non working kernel with failed probe message:

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

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

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

Status in alsa-driver package in Ubuntu:
  New

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

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

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

  PX Headphones are on the newest firmware level.

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

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

2018-05-27 Thread remi

Public bug reported:

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

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

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


** Tags: amd64 apport-bug bionic

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

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

Status in alsa-driver package in Ubuntu:
  New

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

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

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

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

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

2018-05-27 Thread DSHR

Public bug reported:

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

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

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

PX Headphones are on the newest firmware level.

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

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


** Tags: amd64 apport-bug bionic

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

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

Status in alsa-driver package in Ubuntu:
  New

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

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

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

  PX Headphones are on the newest firmware level.

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

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

Manfred Steiner:

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

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1306849] Re: Printing error

2018-05-27 Thread Tom Stover

Experiencing this same Brother printer problem with Ubuntu 18.04
download in late May, 2018

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

Title:
  Printing error

Status in foomatic-db package in Ubuntu:
  Confirmed

Bug description:
  I get the message ERROR NAME; stackunderflow COMMAND; pop OPERAND
  STACK; when I try to print from Firefox or anything that has a picture
  as part of the file.  I am running saucy on an AMD64 system. so far I
  have tried deleting the printer and setting it up again. No change.
  Ubuntu 13.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/1306849/+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 1770269] Re: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 139

Hello, I was experiencing something similar. I'd like to request some
data from you; seems we might have duplicate bugs, so I'm trying to
narrowing if they all are reporting the same failures, and I have a
potential fix for it.

Please, try to rebuild the packages by running (as root): 
"/usr/lib/dkms/dkms_autoinstaller start "
For example: "/usr/lib/dkms/dkms_autoinstaller start 4.15.0-21-generic"

After that, collect the build log and attach it here. It's present usually at:
"/var/lib/dkms/nvidia-340//build/make.log"

Thanks,


Guilherme

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

Title:
  package nvidia-340 340.106-0ubuntu3 failed to install/upgrade:
  installed nvidia-340 package post-installation script subprocess
  returned error exit status 139

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

Bug description:
  Can't install NVIDIA proprietary driver - no obvious symptoms, just
  failed.

  Virgin install of xubuntu 18.04 + updates.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  9 22:02:19 2018
  ErrorMessage: installed nvidia-340 package post-installation script 
subprocess returned error exit status 139
  InstallationDate: Installed on 2018-05-08 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: 
installed nvidia-340 package post-installation script subprocess returned error 
exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1770269/+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 1770497] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo

Hello, I was experiencing something similar. I'd like to request some
data from you; seems we might have duplicate bugs, so I'm trying to
narrowing if they all are reporting the same failures, and I have a
potential fix for it.

Please, try to rebuild the packages by running (as root): 
"/usr/lib/dkms/dkms_autoinstaller start "
For example: "/usr/lib/dkms/dkms_autoinstaller start 4.15.0-21-generic"

After that, collect the build log and attach it here. It's present usually at:
"/var/lib/dkms/nvidia-340//build/make.log"

Thanks,


Guilherme

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: trying
  to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in
  package nvidia-kernel-common-390 390.48-0ubuntu3

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

Bug description:
  I really need for the 304 Driver to be supported in 18.04. This is the
  only driver that does not crash my system. I have tried 390 and 340
  both have their problems.

  thanks

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May 10 16:39:13 2018
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2017-11-22 (169 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: trying 
to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package 
nvidia-kernel-common-390 390.48-0ubuntu3
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1770497/+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 1771108] Re: package nvidia-340 (not installed) failed to install/upgrade: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете nvidia-kernel-

Hello, I was experiencing something similar. I'd like to request some
data from you; seems we might have duplicate bugs, so I'm trying to
narrowing if they all are reporting the same failures, and I have a
potential fix for it.

Please, try to rebuild the packages by running (as root): 
"/usr/lib/dkms/dkms_autoinstaller start "
For example: "/usr/lib/dkms/dkms_autoinstaller start 4.15.0-21-generic"

After that, collect the build log and attach it here. It's present usually at:
"/var/lib/dkms/nvidia-340//build/make.log"

Thanks,


Guilherme

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

Title:
  package nvidia-340 (not installed) failed to install/upgrade: попытка
  перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется
  в пакете nvidia-kernel-common-390 390.48-0ubuntu3

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

Bug description:
  Dunno.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-340 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Mon May 14 15:14:26 2018
  ErrorMessage: попытка перезаписать «/lib/udev/rules.d/71-nvidia.rules», 
который уже имеется в пакете nvidia-kernel-common-390 390.48-0ubuntu3
  InstallationDate: Installed on 2018-05-05 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 (not installed) failed to install/upgrade: попытка 
перезаписать «/lib/udev/rules.d/71-nvidia.rules», который уже имеется в пакете 
nvidia-kernel-common-390 390.48-0ubuntu3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1771108/+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 1771413] Re: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: new nvidia-340 package pre-installation script subprocess returned error exit status 1

Hello, I was experiencing something similar. I'd like to request some
data from you; seems we might have duplicate bugs, so I'm trying to
narrowing if they all are reporting the same failures, and I have a
potential fix for it.

Please, try to rebuild the packages by running (as root): 
"/usr/lib/dkms/dkms_autoinstaller start "
For example: "/usr/lib/dkms/dkms_autoinstaller start 4.15.0-21-generic"

After that, collect the build log and attach it here. It's present usually at:
"/var/lib/dkms/nvidia-340//build/make.log"

Thanks,


Guilherme

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

Title:
  package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: new
  nvidia-340 package pre-installation script subprocess returned error
  exit status 1

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

Bug description:
  I was doing daily updates when the error came up.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: nvidia-340 340.106-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  Date: Tue May 15 12:08:02 2018
  ErrorMessage: new nvidia-340 package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-10-21 (205 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha0ubuntu1
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-340 340.106-0ubuntu3 failed to install/upgrade: new 
nvidia-340 package pre-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Title:
  symbol conflicts in libtimezonemap1

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1760144] Re: Wrong size of icon, if launcher put on desktop

2018-05-27 Thread nmaxx

It's now improved in 18.04 with Firefox version 60.0.1+build2-0ubuntu0.18.04.1.
Dragging the FF icon from the menu to the Desktop now creates a correctly sized
icon.
However, in "Preferred Applications" the icon is still a bit too large.
See attached ff.png.

** Attachment added: "ff.png"

https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760144/+attachment/5145292/+files/ff.png

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

Title:
Wrong size of icon, if launcher put on desktop

Status in firefox package in Ubuntu:
Confirmed

Bug description:
Hi,

as off Firefox 59, if a launcher is put on desktop, its icon size is
too large.

The culprit may be a missing icons folder ?

Testing on a liveUSB of Ubuntu 16.04.1 here I get :
https://postimg.org/image/6t98217zt/
left window is the liveUSB, right window is my actual 16.04 installation.

Right after upgrading FF to newer version, I get :
https://postimg.org/image/cu6wz42bt/
left window is still the liveUSB.
« icons » folder disappeared while upgrading FF
and then instantly icon get much larger on desktop.

It's not unity related : see
https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https
://ubuntu-mate.community/t/firefox-v59-has-a-ridiculously-large-
static-desktop-icon/16205/3 or https://forum.ubuntu-
fr.org/viewtopic.php?id=2023636

The workarounds provided by those topics are not reliable fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760144/+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 1720630] Re: Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1

2018-05-27 Thread bing

+1

*Please* preserve choice for the user, and make the full selection of
backend choices visible.

UI design can direct casual users to the friendly backends while
preserving convenient choices for experienced users who often have
specific needs.  Options that are unnecessarily limited on the
proprietary OSes is exactly what has driven many users to Linux!

Thanks for the very useful info, and the excellent package.

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

Title:
  Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I am currently testing out Ubuntu 17.10 and I noticed that Deja Dup
  (version 36.1-0ubuntu1) no longer supports S3 backups. I have already
  installed the packages python-boto python-cloudfiles but the "Amazon
  S3" option is missing from the Storage location tab.

  Using dconfig editor, I can see the S3 records created under
  /org/gnome/deja-dup/s3. The same installation works fine on Ubuntu
  16.04. Any thoughts?

  
  lsb_release -d
  Description:  Ubuntu Artful Aardvark (development branch)

  dpkg-query -W deja-dup duplicity
  deja-dup  36.1-0ubuntu1
  duplicity 

  gsettings list-recursively org.gnome.DejaDup
  org.gnome.DejaDup last-restore ''
  org.gnome.DejaDup periodic false
  org.gnome.DejaDup periodic-period 7
  org.gnome.DejaDup full-backup-period 90
  org.gnome.DejaDup backend 'remote'
  org.gnome.DejaDup last-run ''
  org.gnome.DejaDup nag-check ''
  org.gnome.DejaDup prompt-check '2017-10-01T10:29:53.542958Z'
  org.gnome.DejaDup root-prompt true
  org.gnome.DejaDup include-list ['$HOME']
  org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
  org.gnome.DejaDup last-backup ''
  org.gnome.DejaDup allow-metered false
  org.gnome.DejaDup delete-after 0
  org.gnome.DejaDup.Rackspace username ''
  org.gnome.DejaDup.Rackspace container 'ubuntu'
  org.gnome.DejaDup.S3 id ''
  org.gnome.DejaDup.S3 bucket ''
  org.gnome.DejaDup.S3 folder 'ubuntu'
  org.gnome.DejaDup.OpenStack authurl ''
  org.gnome.DejaDup.OpenStack tenant ''
  org.gnome.DejaDup.OpenStack username ''
  org.gnome.DejaDup.OpenStack container 'ubuntu'
  org.gnome.DejaDup.GCS id ''
  org.gnome.DejaDup.GCS bucket ''
  org.gnome.DejaDup.GCS folder 'ubuntu'
  org.gnome.DejaDup.Local folder 'ubuntu'
  org.gnome.DejaDup.Remote uri ''
  org.gnome.DejaDup.Remote folder 'ubuntu'
  org.gnome.DejaDup.Drive uuid ''
  org.gnome.DejaDup.Drive icon ''
  org.gnome.DejaDup.Drive folder '$HOSTNAME'
  org.gnome.DejaDup.Drive name ''
  org.gnome.DejaDup.GOA id ''
  org.gnome.DejaDup.GOA folder 'ubuntu'
  org.gnome.DejaDup.GOA type 'owncloud'
  org.gnome.DejaDup.File short-name ''
  org.gnome.DejaDup.File type 'normal'
  org.gnome.DejaDup.File migrated true
  org.gnome.DejaDup.File name ''
  org.gnome.DejaDup.File path ''
  org.gnome.DejaDup.File uuid ''
  org.gnome.DejaDup.File icon ''
  org.gnome.DejaDup.File relpath @ay []

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

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

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773662] [NEW] Fingerprint login not available

You have been subscribed to a public bug:

I have fprintd installed on 18.04. I have enrolled my fingerprint. It
does not offer fingerprint login when I sudo. This was working on 16.04.

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

-- 
Fingerprint login not available
https://bugs.launchpad.net/bugs/1773662
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to fprintd in Ubuntu.

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

Re: [Desktop-packages] [Bug 1708922] Re: uvcvideo module does not work with Dell XPS 12 webcam

2018-05-27 Thread emk2203

Ok, I will do that.

Reinhard Tartler  schrieb am Do., 12. Apr. 2018,
23:29:

> If you can, please file a separate bug for uvcvideo with a stacktrace. Then
> please link those bugs
>
> The easiest way is probably by using apport on the crash file, I guess.
>
> On Thu, Apr 12, 2018, 17:21 emk2203 <1708...@bugs.launchpad.net> wrote:
>
> > Original reporter here. I am willing to assist wherever I can, but I
> > reported chiefly because I cannot debug or investigate of my own.
> >
> > Regarding the cheese issue, the exact same issue arises when just using
> > uvcvideo, so it is definitely something passed on from the driver.
> >
> > 2018-04-12 15:52 GMT+02:00 Reinhard Tartler :
> >
> > > Looking at the stacktrace, this is coming from /usr/bin/cheese. Even
> > > with bad input from the driver (which seems like a valid issue to
> > > investigate and improve) - an error message is preferable to a SIGFPE
> as
> > > seen in the initial report.
> > >
> > > ** Also affects: linux via
> > >https://trac.ffmpeg.org/ticket/4795
> > >Importance: Unknown
> > >Status: Unknown
> > >
> > > ** No longer affects: linux
> > >
> > > ** Changed in: ffmpeg (Ubuntu)
> > >Importance: Undecided => Low
> > >
> > > ** Also affects: cheese (Ubuntu)
> > >Importance: Undecided
> > >Status: New
> > >
> > > ** Changed in: cheese (Ubuntu)
> > >Importance: Undecided => Medium
> > >
> > > ** Changed in: cheese (Ubuntu)
> > >Status: New => Confirmed
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1708922
> > >
> > > Title:
> > >   uvcvideo module does not work with Dell XPS 12 webcam
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/
> > > 1708922/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are a member of MOTU
> > Media Team, which is subscribed to ffmpeg in Ubuntu.
> > https://bugs.launchpad.net/bugs/1708922
> >
> > Title:
> >   uvcvideo module does not work with Dell XPS 12 webcam
> >
> > To manage notifications about this bug go to:
> >
> >
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1708922/+subscriptions
> >
> > Launchpad-Notification-Type: bug
> > Launchpad-Bug: distribution=ubuntu; sourcepackage=cheese; component=main;
> > status=Confirmed; importance=Medium; assignee=None;
> > Launchpad-Bug: distribution=ubuntu; sourcepackage=ffmpeg;
> > component=universe; status=Incomplete; importance=Low; assignee=None;
> > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> > status=Incomplete; importance=Medium; assignee=None;
> > Launchpad-Bug-Tags: amd64 apport-crash artful gstreamer-error
> > Launchpad-Bug-Information-Type: Public
> > Launchpad-Bug-Private: no
> > Launchpad-Bug-Security-Vulnerability: no
> > Launchpad-Bug-Commenters: apport emk2203 janitor jcowgill kaihengfeng
> > siretart ubuntu-kernel-bot
> > Launchpad-Bug-Reporter: emk2203 (emk2203)
> > Launchpad-Bug-Modifier: emk2203 (emk2203)
> > Launchpad-Message-Rationale: Subscriber (ffmpeg in Ubuntu) @motumedia
> > Launchpad-Message-For: motumedia
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1708922
>
> Title:
>   uvcvideo module does not work with Dell XPS 12 webcam
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1708922/+subscriptions
>

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

Title:
  uvcvideo module does not work with Dell XPS 12 webcam

Status in cheese package in Ubuntu:
  Confirmed
Status in ffmpeg package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  uvcvideo: Found UVC 1.00 device Integrated Webcam (0bda:5716) from
  Dell XPS 12 laptop (9Q33 version) does not work properly for several
  versions of the kernel now.

  guvcview nor cheese both show the issue, so it's the uvcvideo driver.
  Starting at 640x480 and higher resolutions, parts of lower half of
  video flickers / don't show image.

  Error messages:
  V4L2_CORE: (jpeg decoder) error while decoding frame
  V4L2_CORE: (jpeg decoder) Ignoring empty buffer
  V4L2_CORE: Error - Couldn't decode frame

  VLC seems to use another driver AND DOES NOT SHOW issue.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cheese 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Aug  6 12:15:28 2017
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2017-04-01 (127 days ago)
  InstallationMedia: Ubuntu 17.04

[Desktop-packages] [Bug 1773662] Re: Fingerprint login not available

2018-05-27 Thread nmaxx

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

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

Title:
  Fingerprint login not available

Status in fprintd package in Ubuntu:
  New

Bug description:
  I have fprintd installed on 18.04. I have enrolled my fingerprint. It
  does not offer fingerprint login when I sudo. This was working on
  16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1773662/+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 1773674] Re: cups-pk-helper-mechanism crashed with signal 5

2018-05-27 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1290533
   cups-pk-helper-mechanism crashed with signal 5 in g_variant_new_va()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  cups-pk-helper-mechanism crashed with signal 5

Status in cups-pk-helper package in Ubuntu:
  New

Bug description:
  no more information at this moment

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: cups-pk-helper 0.2.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17
  Uname: Linux 4.15.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  Date: Sun May 27 13:27:16 2018
  ExecutablePath: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism
  InstallationDate: Installed on 2018-04-13 (44 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180413)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism
  ProcEnviron:
   
  Signal: 5
  SourcePackage: cups-pk-helper
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new_va () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_variant_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-pk-helper-mechanism crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1773674/+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 901147] Re: No timeout in gedit when connection is lost

** Changed in: gedit
   Status: Confirmed => Won't Fix

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

Title:
  No timeout in gedit when connection is lost

Status in gedit:
  Won't Fix
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  If connection is lost when editing a document in gedit that is on a
  remote sftp/ssh server, gedit gets stuck in an endless loop when
  trying to save the document. It will also fail even if the connection
  is reestablished

  To reproduce:
  1. Open Nautilus and connect through it to your SFTP/SSH server
  2. Open a .txt document with gedit and do some changes
  3. Close connection to simulate a lost network situation
  4. Reconnect to your SFTP/SSH server
  5. Try to save the document in gedit. Gedit will now get stuck in a never 
ending loop trying to save the document and will need to be killed manually

  Expected:
  5. Gedit will eventually timeout if it can't find the location.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gedit 3.2.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Uname: Linux 3.0.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Wed Dec  7 10:54:16 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to oneiric on 2011-11-01 (35 days ago)

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

2018-05-27 Thread David Ward

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

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

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

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

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

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

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

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

Bug description:
  Binary package hint: opensc

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

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

  Expected result:

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

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

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773665] [NEW] gdm-x-session crash: glamor_composite_largepixmap_region: Assertion `0' failed.

2018-05-27 Thread Hans Deragon

Public bug reported:

Whenever as root in a terminal, I start 'gvim', the whole windows system
crashes and the user find himself on the gdm login screen.  Windowing
session has been lost.

It only occurs with gvim. I tried xterm, terminator and gthumb as root
and these graphical application do not cause the crash.

Ubuntu 18.04 Bionic Beaver, all packages up to date as of 2018-05-27
11:26:45 EDT.

Following is the trace found under /var/log/syslog:

May 27 10:43:45 demloka gnome-shell[21426]: g_array_unref: assertion 'array' 
failed
May 27 10:43:45 demloka gnome-shell[21426]: message repeated 2 times: [ 
g_array_unref: assertion 'array' failed]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Xorg: 
../../../../glamor/glamor_largepixmap.c:1449: 
glamor_composite_largepixmap_region: Assertion `0' failed.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Backtrace:
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 0: 
/usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5619d46e58ad]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 1: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x1bc649) [0x5619d46e9649]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 2: 
/lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4c99632000+0x12890) [0x7f4c99644890]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 3: 
/lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) [0x7f4c9927fe97]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 4: 
/lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) [0x7f4c99281801]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 5: 
/lib/x86_64-linux-gnu/libc.so.6 (0x7f4c99241000+0x3039a) [0x7f4c9927139a]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 6: 
/lib/x86_64-linux-gnu/libc.so.6 (0x7f4c99241000+0x30412) [0x7f4c99271412]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (0x7f4c95ec3000+0x21e21) [0x7f4c95ee4e21]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 8: 
/usr/lib/xorg/modules/libglamoregl.so (0x7f4c95ec3000+0x16362) [0x7f4c95ed9362]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 9: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x13d896) [0x5619d466a896]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 10: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x13312c) [0x5619d466012c]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 11: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x52e98) [0x5619d457fe98]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 12: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x56ee0) [0x5619d4583ee0]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 13: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f4c99262b97]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 14: 
/usr/lib/xorg/Xorg (_start+0x2a) [0x5619d456db8a]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Fatal server error:
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Caught signal 
6 (Aborted). Server aborting
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Please consult the 
The X.Org Foundation support
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: #011 at 
http://wiki.x.org
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]:  for help.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Please also 
check the log file at "/home/hans/.local/share/xorg/Xorg.0.log" for additional 
information.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Server 
terminated with error (1). Closing log file.
May 27 10:43:49 demloka update-notifier[22815]: update-notifier: Fatal IO error 
11 (Resource temporarily unavailable) on X server :0.

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

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

Title:
  gdm-x-session crash:  glamor_composite_largepixmap_region: Assertion
  `0' failed.

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Whenever as root in a terminal, I start 'gvim', the whole windows
  system crashes and the user find himself on the gdm login screen.
  Windowing session has been lost.

  It only occurs with gvim. I tried xterm, terminator and gthumb as root
  and these graphical

[Desktop-packages] [Bug 1770720] Re: network-manager-openvpn is not working on ubuntu 18.04

2018-05-27 Thread David Ing

The status at https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/1772066 have moved to "confirmed".

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

Title:
  network-manager-openvpn is not working on ubuntu 18.04

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

Bug description:
  I'm using Ubuntu 18.04.

  I installed network-manager-openvpn and as a dependency openvpn and
  network-manager-openvpn-gnome.

  I restarted NetworkManager with systemctl restart NetworkManager

  I'm able to add new openvpn connexion trough .ovpn files but when I
  click to ON to my openvpn server network-manager is doing nothing, its
  not trying to connect to the openvpn server.

  I think there is a bug there.

  I'm open to any further questions or informations devs will need

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1770720/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2018-05-27 Thread Peter Bennett

@luca.mg
I tried what you suggested, and rebooted, but the scanner is still not found by 
scanimage -L

@Ken Wright
The network must be OK, because I can scan if I run under chroot in the same 
installation.

$Peterpall
I do not have gufw, or any firewall. the ports all should be open, and it does 
work under chroot so I don't think it is a network problem.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  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/1728012/+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 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

2018-05-27 Thread Bump

It should be installed somehow.

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

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

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

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

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

  See bugs here:

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

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

-- 
Mailing list: https://launchpad.net/~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 1773651] [NEW] xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

2018-05-27 Thread Bump

Public bug reported:

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

See bugs here:

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

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

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

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

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

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

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

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

** Summary changed:

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

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

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

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

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

  See bugs here:

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

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

-- 
Mailing list: https://launchpad.net/~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 1768633] Re: desktop or window fallen over after standby

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

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

Title:
  desktop or window fallen over after standby

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1734887] Re: No caps lock indicator on login screen

2018-05-27 Thread Metta Crawler

gdm version 3.28.0-0ubuntu1

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

Title:
  No caps lock indicator on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Expected results: Pressing the Caps Lock key should cause an indicator
  to appear on the login screen.

  Actual results: Pressing the Caps Lock key does not cause the login
  screen to change in any way.

  Reproducing:

  1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Lock key, see no 
indicator. (gdm3 3.26.1-3ubuntu3)
  2. Install Fedora 27 Workstation ISO and log in, press Caps Lock key, see an 
indicator. (gdm-3.26.2.1-1.fc27.x86_64)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  Uname: Linux 4.14.2-041402-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Nov 28 08:24:31 2017
  InstallationDate: Installed on 2017-11-05 (22 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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/+source/gdm3/+bug/1734887/+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 1734887] Re: No caps lock indicator on login screen

2018-05-27 Thread Metta Crawler

18.04 GDM login screen now displays an exclamation mark as a caps lock 
indicator.
The older GDM used a different icon but this is sufficient for me.
It is my opinion that this issue has been resolved.

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

Title:
  No caps lock indicator on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed

Bug description:
  Expected results: Pressing the Caps Lock key should cause an indicator
  to appear on the login screen.

  Actual results: Pressing the Caps Lock key does not cause the login
  screen to change in any way.

  Reproducing:

  1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Lock key, see no 
indicator. (gdm3 3.26.1-3ubuntu3)
  2. Install Fedora 27 Workstation ISO and log in, press Caps Lock key, see an 
indicator. (gdm-3.26.2.1-1.fc27.x86_64)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu3
  Uname: Linux 4.14.2-041402-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Nov 28 08:24:31 2017
  InstallationDate: Installed on 2017-11-05 (22 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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/+source/gdm3/+bug/1734887/+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 1766103] Re: bionic: VPN not working at all

2018-05-27 Thread canti

Also I cannot do vpn connections after upgrade to bionic from 17.10.

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

Title:
  bionic: VPN not working at all

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

Bug description:
  VPN is completely busted on bionic-desktop (4/21/2018).  In 17.10 my
  VPN was still working, "only" had to do a `killall nm-applet; nohup
  nm-applet &` to get the password prompt to show up.  In bionic, at
  least that portion now works without work-around.  However, I can't
  establish my VPN to my workplace at all.

  My VPN configuration in /etc/NetworkManager/system-connections/Test
  seems rather basic:

  [connection]
  id=Test
  uuid=ae916f15-2e8d-46b0-92d3-c2dece212c40
  type=vpn
  autoconnect=false
  permissions=user:thomas:;

  [vpn]
  domain=XX.XXX
  gateway=vpn.XX.XXX
  password-flags=2
  refuse-chap=yes
  refuse-eap=yes
  refuse-pap=yes
  require-mppe=yes
  user=Y
  service-type=org.freedesktop.NetworkManager.pptp

  [ipv4]
  dns=10.11.11.11;
  dns-search=
  method=auto
  never-default=true
  route1=10.11.0.0/16,10.11.31.31

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=ignore

  Here's the logs from syslog:

  Apr 22 10:29:18 thomas-bionic NetworkManager[507]:   [1524414558.0300] 
audit: op="connection-activate" uuid="ae916f15-2e8d-46b0-92d3-c2dece212c40" 
name="Test" pid=1141 uid=1000 result="success"
  Apr 22 10:29:18 thomas-bionic gnome-shell[781]: JS ERROR: TypeError: item is 
undefined#012setActiveConnections/<@resource:///org/gnome/shell/ui/status/network.js:1518:17#012setActiveConnections@resource:///org/gnome/shell/ui/status/network.js:1515:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
  Apr 22 10:29:18 thomas-bionic NetworkManager[507]:   [1524414558.0445] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
Started the VPN service, PID 2601
  Apr 22 10:29:18 thomas-bionic NetworkManager[507]:   [1524414558.0631] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
Saw the service appear; activating connection
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.2896] 
settings-connection[0x55588511f440,ae916f15-2e8d-46b0-92d3-c2dece212c40]: 
write: successfully updated (keyfile: update 
/etc/NetworkManager/system-connections/Test 
(ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test")), connection was modified in the 
process
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3008] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
VPN connection: (ConnectInteractive) reply received
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3095] 
vpn-connection[0x555885252640,ae916f15-2e8d-46b0-92d3-c2dece212c40,"Test",0]: 
VPN plugin: state changed: starting (3)
  Apr 22 10:29:21 thomas-bionic pppd[2613]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Apr 22 10:29:21 thomas-bionic pppd[2613]: pppd 2.4.7 started by root, uid 0
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3358] 
manager: (ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/5)
  Apr 22 10:29:21 thomas-bionic pppd[2613]: Using interface ppp0
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Using interface ppp0
  Apr 22 10:29:21 thomas-bionic pppd[2613]: Connect: ppp0 <--> /dev/pts/0
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]: Connect: ppp0 <--> 
/dev/pts/0
  Apr 22 10:29:21 thomas-bionic pptp[2620]: nm-pptp-service-2601 
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
  Apr 22 10:29:21 thomas-bionic systemd-udevd[2617]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3610] 
devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  Apr 22 10:29:21 thomas-bionic NetworkManager[507]:   [1524414561.3613] 
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown 
configuration found.
  Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 
log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
  Apr 22 10:29:21 thomas-bionic pptp[2632]: nm-pptp-service-2601 
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
  Apr 22 10:29:22 thomas-bionic pptp[2632]: nm-pptp-service-2601 
log[ctrlp_rep:pptp_ctrl.c:259]: Sent control packet type is

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

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1762122] Re: drm_kms_helper.edid_firmware not working anymore on Ubuntu 18.04

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

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

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

Title:
  drm_kms_helper.edid_firmware not working anymore on Ubuntu 18.04

Status in xorg package in Ubuntu:
  Confirmed

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

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

2018-05-27 Thread Kabeer Vohra

Can also confirm bug, when logging in from a reboot, it works fine but
when I show text after locking and unlocking (using windows key + L to
lock) and I show text, it seems that the first 3 letters of my password
are lowercase even though I was holding shift. I can also confirm that
backspacing them all (using ctrl + backspace) and retyping the password
without attempting to log in with the incorrect password works fine.

I am using Gnome 3 on Ubuntu 18.04

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed
Status in gnome-shell package in Fedora:
  Fix Released

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/240

  Ubuntu 18.04 login screen rejects a valid password on first attempt.
  Always works on the second attempt..

  This seems to be a new problem, just started today.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 11:16:17 2018
  InstallationDate: Installed on 2017-12-12 (127 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gdm3
  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/1765261/+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 1773484] Re: Login screen not moved to used monitor

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

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

Title:
  Login screen not moved to used monitor

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1068605] Re: List of session type does not fit on screen with many window managers installed

2018-05-27 Thread kenn

I have the same issue on Ubuntu 16.04.4. They won't fix it.

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

Title:
  List of session type does not fit on screen with many window managers
  installed

Status in unity-greeter package in Ubuntu:
  Triaged

Bug description:
  Please see the attached screenshot. The system has many window
  managers installed because it is a public lab machine with a many
  users that have different preferences. In order to change the session,
  one is supposed to confirm his selection by pressing the button at the
  bottem. However, the button hardly fits on the screen, in fact, one
  has to guess the purpose of the lowest button.

  On option would be to have the list of managers in a scroll box.

  ---
  Desired resolution:

  - Vertically middle align the desktop environment switcher with the
  back button when there are more than 6 desktop environments in the
  menu.

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

2018-05-27 Thread Stefan Helmert

tried now nvidia 396.24, got simmilar problems

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

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

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

Title:
  desktop or window fallen over after standby

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773637] [NEW] Distribution upgrade to 18.04: used nvidia display driver is commented out

2018-05-27 Thread Yoshee

Public bug reported:

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

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

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

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

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


** Tags: amd64 apport-bug bionic ubuntu

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

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

Status in xorg package in Ubuntu:
  New

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

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

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

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

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

2018-05-27 Thread Alfred Krohmer

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

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

Title:
Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
Triaged

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

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

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

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

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

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

But this doesn't have any effect at all.

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

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

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

[Desktop-packages] [Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

2018-05-27 Thread Yuri

Resolution: 1920 X 1080 (16:9), with a refresh rate of 60,00 Hz, I use
an HDMI connection:

yuri@DS47:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 509mm x 286mm
   1920x1080 60.00*+  50.0059.94  
   1920x1080i60.0050.0050.0059.94  
   1600x1200 60.00  
   1680x1050 59.88  
   1400x1050 59.95  
   1280x1024 75.0260.02  
   1440x900  74.9859.90  
   1280x960  60.00  
   1360x768  60.02  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   75.0072.8166.6760.0059.94  
   720x400   70.08  
DP-2 disconnected (normal left inverted right x axis y axis)

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1773634] [NEW] Nutilus can't delete folders on samba share

2018-05-27 Thread Vonschutter

Public bug reported:

When deleting folders (only) on a samba share, the folders re appear
after view/refresh. They were never deleted even though initially the
folders seemed to be. Same share, same credentials, are able to delete
the folders successfully from windows and older versions of Ubuntu.

Bug is resolved upstream it seems: 
https://bugzilla.gnome.org/show_bug.cgi?id=792147

Please implement.

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

Title:
  Nutilus can't delete folders on samba share

Status in gvfs package in Ubuntu:
  New

Bug description:
  When deleting folders (only) on a samba share, the folders re appear
  after view/refresh. They were never deleted even though initially the
  folders seemed to be. Same share, same credentials, are able to delete
  the folders successfully from windows and older versions of Ubuntu.

  Bug is resolved upstream it seems: 
  https://bugzilla.gnome.org/show_bug.cgi?id=792147

  Please implement.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773634/+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 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

I mean the performance is mostly the same.

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

Not actually. But mouse pointer moves are not smooth in Wayland session.
So I guess that counts.

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1773516] Re: [Lenovo Yoga 300-11IBY] Right click not working

2018-05-27 Thread Timo Aaltonen

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

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

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

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

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773575] Re: dual vga

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

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

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

Title:
  dual vga

Status in xorg package in Ubuntu:
  Invalid

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

Do you find any significant difference in performance between Xorg and
Wayland sessions?

Is this bug the same?

** Tags added: radeon

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

Sure. Here is it.


00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 
08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Host Bridge/DRAM Registers
Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
Subsystem: Lenovo Skylake GT2 [HD Graphics 520]
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller
Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
Subsystem: Lenovo Sunrise Point-LP Thermal subsystem
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
Subsystem: Lenovo Sunrise Point-LP CSME HECI
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
Subsystem: Lenovo Sunrise Point-LP SATA Controller [AHCI mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
Subsystem: Lenovo Sunrise Point-LP LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
Subsystem: Lenovo Sunrise Point-LP PMC
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
Subsystem: Lenovo Sunrise Point-LP SMBus
Kernel modules: i2c_i801
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 15)
Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
Kernel driver in use: r8169
Kernel modules: r8169
02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus 
Bluetooth (rev 99)
Subsystem: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT 
[Radeon HD 8670A/8670M/8690M / R5 M330 / M430] (rev 83)
Subsystem: Lenovo Radeon R5 M330
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 421239]

2018-05-27 Thread eddie latham

http://original.moxieyogafitness.com
Edward Latham

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

Title:
  updates failed http://:8080/:invalid host name

Status in epiphany-browser package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: epiphany-browser

  updates for ubuntu failed and any thing i try to down load
  http;//;8080/;Ivalid host name it also my be effecting internet video
  & audio

  ProblemType: Bug
  Architecture: i386
  Date: Sat Aug 29 16:11:56 2009
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/epiphany-gecko
  Package: epiphany-gecko 2.22.2-0ubuntu0.8.04.5
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  Uname: Linux 2.6.24-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/421239/+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 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

Thanks.

Can you please also run 'lspci -k' and send us the output?

** Summary changed:

- High CPU usage by gnome-shell. 
+ High CPU usage by gnome-shell when using Google Chrome

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1770929] Re: backup fails on ubuntu 18.4

2018-05-27 Thread Ahmad Amr

Failed with an unknown error.

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1523, in do_backup
incremental_backup(sig_chain)
  File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
  File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
return self.__run_synchronously(fn, params)
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
ret = fn(*params)
  File "/usr/bin/duplicity", line 453, in 
vol_num: put(tdp, dest_filename, vol_num),
  File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

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

Title:
  backup fails on ubuntu 18.4

Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1770929/+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 1770929] Re: backup fails on ubuntu 18.4

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

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

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

Title:
  backup fails on ubuntu 18.4

Status in duplicity package in Ubuntu:
  Confirmed

Bug description:
  backup worked under Ubuntu 17.10
  It also worked on Ubuntu 18.4 before last week's update (run on Friday 11.5)
  my drive is encrypted
  this is the error message in the error frame
  Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1393, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1523, in do_backup
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
  globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
  (tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
  return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
  ret = fn(*params)
File "/usr/bin/duplicity", line 453, in 
  vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
  backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
  % (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
  return ufn(unicode(e).encode('utf-8'))
   UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 37: 
ordinal not in range(128)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: duplicity 0.7.17-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 13 09:55:00 2018
  InstallationDate: Installed on 2018-05-01 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1770929/+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 1773528] Re: High CPU usage by gnome-shell.

Google Chrome Version 66.0.3359.181 (Official Build) (64-bit). 
By [CPU usage] in my previous letter I refer to CPU usage of gnome-shell.

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

Title:
  High CPU usage by gnome-shell.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1773628] [NEW] package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 127

2018-05-27 Thread Sklyarov Yurii

Public bug reported:

memcached

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: cups-browsed 1.17.9-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
AptOrdering:
 firefox:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CupsErrorLog:
 
Date: Sun May 27 10:55:56 2018
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 127
Lpstat: device for Canon-G3000: 
cnijbe2://Canon/?port=net=84-BA-3B-5E-63-D7
MachineType: Hewlett-Packard HP ProBook 430 G2
Papersize: a4
PpdFiles: Canon-G3000: Canon G3000 series Ver.5.30
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic 
root=UUID=94718cde-02bd-40cb-baab-db57e87057a5 ro quiet splash vt.handoff=7
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: cups-filters
Title: package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 127
UpgradeStatus: Upgraded to artful on 2018-03-05 (82 days ago)
dmi.bios.date: 09/26/2016
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M73 Ver. 01.42
dmi.board.name: 2246
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 59.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.42:bd09/26/2016:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion59.23:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 430 G2
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard

** Affects: cups-filters (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  127

Status in cups-filters package in Ubuntu:
  New

Bug description:
  memcached

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: cups-browsed 1.17.9-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun May 27 10:55:56 2018
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 127
  Lpstat: device for Canon-G3000: 
cnijbe2://Canon/?port=net=84-BA-3B-5E-63-D7
  MachineType: Hewlett-Packard HP ProBook 430 G2
  Papersize: a4
  PpdFiles: Canon-G3000: Canon G3000 series Ver.5.30
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic 
root=UUID=94718cde-02bd-40cb-baab-db57e87057a5 ro quiet splash vt.handoff=7
  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: cups-filters
  Title: package cups-browsed 1.17.9-0ubuntu1.1 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 127
  UpgradeStatus: Upgraded to artful on 2018-03-05 (82 days ago)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M73 Ver. 01.42
  dmi.board.name: 2246
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 59.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM73Ver.01.42:bd09/26/2016:svnHewlett-Packard:pnHPProBook430G2:pvrA3008CD10003:rvnHewlett-Packard:rn2246:rvrKBCVersion59.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 430 G2
  dmi.product.version: A3008CD10003
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1773628/+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 1773528] Re: High CPU usage by gnome-shell.

When "playing videos on youtube", what browser (and version) are you
using?

Remember to focus on the CPU usage of the gnome-shell process only.

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

Title:
  High CPU usage by gnome-shell.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1773528] Re: High CPU usage by gnome-shell.

I've noticed that playing videos on youtube affects it the most. The bigger is 
resolution the higher is CPU usage. But it's 
also high while using WebStorm or VmWare.

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

Title:
  High CPU usage by gnome-shell.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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

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

2018-05-27 Thread mustafa

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

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

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

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

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

 https://trello.com/c/aI3BX3ax

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

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

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  Triaged

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

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

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

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

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

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

  But this doesn't have any effect at all.

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

Does anyone feel like logging a new bug for the regression in
3.28.0-0ubuntu1.1/3.28.0-0ubuntu2 ?

It's a real bug now, since 3.28.0-0ubuntu2 was released in cosmic.

** Description changed:

  [ Description ]
  
  Due to a refcounting bug, a GDBusConnection was getting disposed when it
- was still required. The symptom of this was that you couldn't log in if
- you'd got your password wrong.
+ was still required. The symptom of this was that you couldn't log in on
+ the second attempt if you'd got your password wrong on the first
+ attempt.
  
  [ Test case ]
  
  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password
  
  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.
  
  [ Fix ]
  
  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-
  
  The GdmClient has a shared GDBusConnection for its operations. The first
  time  someone calls for it, it is created and stored in the object's
  private structure. Subsequent calls return *a new reference* to this
  same object. It turned out that the asynchronous method to get the
  connection was accidentally unreferencing its object before giving it to
  the caller if it was returning an already-existing connection.
  
  For this to work properly, we need to nullify the pointer we stored when
  the connection goes away, so we know when to make a new one. There were
  some cases where we didn't add the weak references required to do that.
  Those are also fixed.
  
  [ Regression potential ]
  
  Now we share connections more than we did before. We also more carefully
  track when to clear our object. If we got this wrong, we might end up
  leaking the connection or dropping it in even more cases.
  
  [ Original report ]
  
- 
- WORKAROUND: After typing an incorrect password, click Cancel, then click your 
name, then enter your password again.
+ WORKAROUND: After typing an incorrect password, click Cancel, then click
+ your name, then enter your password again.
  
  ---
  
  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable menu
  in the top right. If I enter it correctly the first time, there is no
  problem.
  
  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.
  
  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [ Description ]
  
  Due to a refcounting bug, a GDBusConnection was getting disposed when it
  was still required. The symptom of this was that you couldn't log in on
  the second attempt if you'd got your password wrong on the first
- attempt.
+ attempt. All you'd see is a blank purple screen and mouse pointer only.
  
  [ Test case ]
  
  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password
  
  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.
  
  [ Fix ]
  
  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-
  
  The GdmClient has a shared GDBusConnection for its operations. The first
  time  someone calls for it, it is created and stored in the object's
  private structure. Subsequent calls return *a new reference* to this
  same object. It turned out that the asynchronous method to get the
  connection was accidentally unreferencing its object before giving it to
  the caller if it was returning an already-existing connection.
  
  For this to work properly, we need to nullify the pointer we stored when
  the connection goes away, so we know when to make a new one. There were
  some cases where we didn't add the weak references required to do that.
  Those are also fixed.
  
  [ Regression potential ]
  
  Now we share connections more than we did before. We also more carefully

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

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

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

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


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

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

Title:
  Pulse audio does not remember default sink

Status in pulseaudio package in Ubuntu:
  Triaged

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

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

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

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

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

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

  But this doesn't have any effect at all.

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1773502] Re: High CPU usage in gnome-shell & Xorg when using Firefox

Nevermind, it's obvious you're using Xorg sessions.

At what resolution though? Please just run 'xrandr' and send us the
output.

** Summary changed:

- High CPU usage in gnome-shell & Xorg when using Firefox
+ High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's 
Resources tab

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1773528] Re: High CPU usage by gnome-shell.

What specific app do you find triggers gnome-shell's high CPU usage?

** Tags added: performance

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

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

Title:
  High CPU usage by gnome-shell.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Usually 40% or more CPU usage. May be related to AMD GPU. Problem
  disappears while using XFCE.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 16:59:28 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-28 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1773528/+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 1773502] Re: High CPU usage in gnome-shell & Xorg when using Firefox

Oooh... that makes sense now, thanks.

The problem you are seeing is with mutter/gnome-shell being inefficient
at frequently-updating software rendered windows. This is a known
problem, but until now we only knew of Eclipse triggering it (bug
1756508), and the older pre-Quantum versions of Firefox (bug 1696305).

What you are seeing is a known performance problem, but you have
discovered a great test case for it in the Resources tab. So thanks.

As I suspected, this is not a problem with the new Firefox at all (which
is hardware rendered). It's a problem with gnome-system-monitor, or any
frequently-redrawing software rendered (e.g. Gnome) app.

I only have two more questions: What is your display resolution, and are
you using Wayland or Xorg? Both of these can be answered by running
'xrandr' and sending us the output.

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   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"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1773541] Re: Entering wrong password once on login causes startup to hang on purple screen

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

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


** This bug has been marked a duplicate of bug 1766137
   [regression] Password accepted but login fails (blank purple screen and 
mouse pointer only)

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

Title:
  Entering wrong password once on login causes startup to hang on purple
  screen

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Hi folks,

  Running Ubuntu 18.04 LTS (dual boot with Windows 10 Pro) on Dell XPS
  15 9570, lshw below.

  Steps to reproduce:

  1. Turn on computer
  2. Select Ubuntu from GRUB menu
  3. Wait for login screen
  4. User list appears, click on user
  5. Enter incorrect password
  6. Wait for prompt to enter password again
  7. Enter correct password

  Now screen will hang.

  lshw:

  xps15
  description: Notebook
  product: XPS 15 9575 (080D)
  vendor: Dell Inc.
  serial: FZVMTN2
  width: 64 bits
  capabilities: smbios-3.1 dmi-3.1 smp vsyscall32
  configuration: boot=normal chassis=notebook family=XPS sku=080D 
uuid=44454C4C-5A00-1056-804D-C6C04F544E32
*-core
 description: Motherboard
 product: 0C32VW
 vendor: Dell Inc.
 physical id: 0
 version: A00
 serial: /FZVMTN2/CNCMK0085I0053/
   *-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: 1.0.7
date: 03/16/2018
size: 64KiB
capacity: 15MiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd 
int13floppynec int13floppy1200 int13floppy720 int13floppy2880 int5printscreen 
int9keyboard int14serial int17printer acpi usb smartbattery 
biosbootspecification netboot uefi
   *-memory
description: System Memory
physical id: 3c
slot: System board or motherboard
size: 16GiB
  *-bank
   description: Row of chips DDR4 Synchronous Unbuffered 
(Unregistered) 2400 MHz (0.4 ns)
   product: HMAA51S6AMR6N-UH
   vendor: SK Hynix
   physical id: 0
   slot: Motherboard
   size: 16GiB
   width: 64 bits
   clock: 2400MHz (0.4ns)
   *-cache:0
description: L1 cache
physical id: 3f
slot: L1 Cache
size: 256KiB
capacity: 256KiB
capabilities: synchronous internal write-back unified
configuration: level=1
   *-cache:1
description: L2 cache
physical id: 40
slot: L2 Cache
size: 1MiB
capacity: 1MiB
capabilities: synchronous internal write-back unified
configuration: level=2
   *-cache:2
description: L3 cache
physical id: 41
slot: L3 Cache
size: 8MiB
capacity: 8MiB
capabilities: synchronous internal write-back unified
configuration: level=3
   *-cpu
description: CPU
product: Intel(R) Core(TM) i7-8705G CPU @ 3.10GHz
vendor: Intel Corp.
physical id: 42
bus info: cpu@0
version: Intel(R) Core(TM) i7-8705G CPU @ 3.10GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 3885MHz
capacity: 4100MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp 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 pbe syscall nx pdpe1gb rdtscp constant_tsc art arch_perfmon pebs bts 
rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni 
pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti tpr_shadow vnmi 
flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx 
rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves ibpb ibrs 
stibp dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp cpufreq
configuration: cores=4 enabledcores=4 threads=8
   *-pci
description: Host bridge

[Desktop-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2018-05-27 Thread Apport retracing service

** Tags added: cosmic

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1559650/+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 1773622] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2018-05-27 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1559650
   gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This is on kernel 4.17.0-041700rc6-generic x86_64.
  Got it directly after boot.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.28.1-0ubuntu2
  Uname: Linux 4.17.0-041700rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun May 27 08:17:00 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-05-15 (376 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f8fe339713e <___vsnprintf_chk+126>: movb   
$0x0,(%r12)
   PC (0x7f8fe339713e) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f8fd2eefae5 "%s%s", args=args@entry=0x7f8f93d54d00) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: Upgraded to cosmic on 2018-04-29 (27 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773622/+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 993106] Re: Provide a way to do on-demand wifi scanning from applet

2018-05-27 Thread William Poetra Yoga

Hi, may I know what's the status of this bug? Any chance we will be
seeing it implemented? Sorry for asking, but I also would love this
feature.

And maybe (probably) I can contribute some patches, will they be
accepted?

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

Title:
  Provide a way to do on-demand wifi scanning from applet

Status in network-manager-applet package in Ubuntu:
  Triaged

Bug description:
  If im connected to one router and i set up another then refresh button is 
needed couse otherwise i
  a.) Need to wait
  b.) Need to disable enable Wireless. And this in cases when connection still 
needed isnt acceptable.

  Slution
  2x clicking on wifi icon refreshes or on clikck witch opens menu- while menu 
open it refreshes. Showing identification "Refreshing" and that wireless to 
witch is it still connected.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: network-manager-gnome 0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-41.88-generic 2.6.32.59+drm33.24
  Uname: Linux 2.6.32-41-generic i686
  Architecture: i386
  Date: Wed May  2 10:53:27 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 
(20100429.4)
  IpRoute:
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.27  
metric 2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   default via 192.168.43.1 dev wlan0  proto static
  Keyfiles: Error: [Errno 2] No such file or directory
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager-applet

  Brainstorm entry about this:
  http://www.brainstorm.ubuntu.com/idea/8326/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/993106/+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 1770731] Re: [nvidia] multimonitor display artifacts

... and then let us know the URL of the new bug.

** Summary changed:

- [nvidia] multimonitor display artifacts
+ [nvidia] multimonitor ghostly flickering display artifacts

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

Title:
  [nvidia] multimonitor ghostly flickering display artifacts

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

Bug description:
  On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome
  shell 3.28.1.

  I have a 3 monitor setup. When I open a terminal in the middle window and 
some other window, like nautilus on the left, and quickly drag the nautilus 
window to the right, covering the terminal, and back without releasing the 
mouse, a flickering ghost of the window remains on the terminal for about a 
minute or so.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2018-05-10 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770731/+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 1770731] Re: [nvidia] multimonitor display artifacts

Flickering ghost images may be caused by gnome-shell's damage tracking
losing track of where things have been drawn, and it then uses buffer
age information incorrectly, leaving junk in only one of the buffers
(out of 2 or 3). So every second or third frame contains pixels that
shouldn't be there, 20 or 30 times per second. I think the best way to
work around it is to drag a window over the flickering area.

Also, please report this bug to the Gnome developers here:
https://gitlab.gnome.org/GNOME/mutter/issues

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

Title:
  [nvidia] multimonitor ghostly flickering display artifacts

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

Bug description:
  On Ubuntu 18.04, running nvidia-390 driver (on a GTX 1080), and gnome
  shell 3.28.1.

  I have a 3 monitor setup. When I open a terminal in the middle window and 
some other window, like nautilus on the left, and quickly drag the nautilus 
window to the right, covering the terminal, and back without releasing the 
mouse, a flickering ghost of the window remains on the terminal for about a 
minute or so.
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-format' b"'12h'"
  InstallationDate: Installed on 2018-05-10 (15 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

mustafa:

1) Regarding crash files, you would not want to attach them, as they may
contain sensitive information you don't want to reveal publicly.

Instead, one may report them in a privacy respectful way via a terminal:
ubuntu-bug /var/crash/FILENAME.crash

where FILENAME is the name of the crash file.

2) It is advised to immediately back up your data (config files, list of
what apps you have installed, etc.), so that in the event of a disaster
(hardware failure, OS stops working entirely, etc.) you may perform a
clean install and bring the OS back to the desired state. Stating "i do
not want to lose my server configuration and reinstall Ubuntu and all
the configuration and apps that i used" doesn't mean you won't have to
do it. This is a matter of how prepared are you if you must.

3) Post the results of the following terminal command:
history

4) To confirm a WORKAROUND, if you install the package gnome-session-
flashback and login to GNOME (Metacity), does this allow you to use the
GUI again?

** Attachment removed: 
"_usr_lib_x86_64-linux-gnu_unity_compiz-config-profile-setter.1000_copy.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773575/+attachment/5145036/+files/_usr_lib_x86_64-linux-gnu_unity_compiz-config-profile-setter.1000_copy.crash

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

Title:
  dual vga

Status in xorg package in Ubuntu:
  Incomplete

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

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

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

-- 
Mailing list: https://launchpad.net/~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 1755800] Re: Greeter/lockscreen fails to authenicate in an endless loop. Repeated "No space left on device" errors and strange swap file configuration

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Greeter/lockscreen fails to authenicate in an endless loop. Repeated
  "No space left on device" errors and strange swap file configuration

Status in gdm3 package in Ubuntu:
  Fix Released

Bug description:
  After a recent install of the 18.04 (why is a separate story), I
  notice that after some number of successful screen locks, I become
  locked out of the desktop with an authentication failure.  During
  those unsuccessful attempts to log in, syslog shows:

  Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"21"
  Mar 13 22:46:04 magpie kernel: [83554.367969] rfkill: input handler enabled
  Mar 13 22:46:04 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event2  - 
Power B
  utton: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"25"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event4  - 
Video B
  us: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"27"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event1  - 
Sleep B
  utton: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"24"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event17 - 
Integra
  ted Camera: Integrated C: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"29"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event3  - AT 
Tran
  slated Set 2 keyboard: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"28"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event5  - 
SynPS/2 Synaptics TouchPad: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"30"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event6  - 
TPPS/2 IBM TrackPoint: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (**) Option "fd" 
"62"
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) event7  - 
ThinkPad Extra Buttons: device removed
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:81
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:68
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 226:0
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:71
  Mar 13 22:46:05 magpie /usr/lib/gdm3/gdm-x-session[1340]: (II) 
systemd-logind: got pause for 13:66

  one new line for each attempted log in.  This is occurring once or
  twice a day.  Sometimes, it works again.  Last time, I needed to
  reboot.

  Since this is a fresh install, albeit with my desktop files being
  restored via CrashPlan (which could be part of the problem?), I
  thought that this warranted a report.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  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: ubuntu:GNOME
  Date: Wed Mar 14 07:58:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-03-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1755800/+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

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

2018-05-27 Thread mustafa

i tried all the possibilities that i found online even to install invidia
because they told me that there might help installing some important files.
now it  doesn't allow me to use the GUI i can use only command line. i
tried many ways to restore the original drivers but i could not restore
them. in windows there is something called soft system reset which
reinstall the system basic files and drivers which i could not find it on
ubuntu, because i do not want to lose my server configuration and reinstall
Ubuntu and all the configuration and apps that i used.
so if there is any future from the command line to restore the drivers or
the basic files of the system without damaging my web server it would be
helpful please.
it might not be a bug but i can see it as bug because i tried to remove the
new installed drivers and though i can not use the gui and it gives me
error when i try to login with my user and pass.

Could you please advise what you did
precisely, in a keyboard click-for-click fashion? concerning this question
i can not give you an answer because i tried many things and now i can not
remember them . i tired to install amd drivers and intel and something from
invidia and then tried to remove them all but the gui still give me error
when i try to login .

in my crash i can find the following / in the attachment/ i could not
understand all the things inside the crash file

thanks for the great job that you and the team doing and i hope that you
can help me to solve this problem.

greetings

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

> mustafa, thank you for reporting this and helping make Ubuntu better.
>
> 1) Regarding your Bug Description:
> >"i tried to update the drivers in one way or another..."
>
> This is not enough information. Could you please advise what you did
> precisely, in a keyboard click-for-click fashion?
>
> 2) Are there any crash files in the /var/crash folder?
>
> 3) As per your logs, you install unsupported software (PPA) and have
> installed the nvidia proprietary drivers when you don't have a nvidia
> card installed. Hence, after removing all PPAs and the nvidia drivers,
> and rebooting does this allow you to use the GUI?
>
> ** Tags added: latest-bios-a14
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1773575
>
> Title:
>   dual vga
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   i have a laptop dell which has two vga one from intel and the other
>   one is amd. i tried to update the drivers in one way or another every
>   thing stoped and i can not use the gui anymore
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
>   Uname: Linux 4.13.0-43-generic x86_64
>   .tmp.unity_support_test.1:
>
>   ApportVersion: 2.20.1-0ubuntu2.17
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Sat May 26 22:00:13 2018
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
>Intel Corporation 3rd Gen Core processor Graphics Controller
> [8086:0166] (rev 09) (prog-if 00 [VGA controller])
>  Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:05b8]
>Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M]
> [1002:6601] (rev ff) (prog-if ff)
>   InstallationDate: Installed on 2018-01-10 (136 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
>   MachineType: Dell Inc. Inspiron 5521
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   Xrandr: Screen 0: minimum 0 x 0, current 3600 x 1080, maximum 4096 x 4096
>   dmi.bios.date: 07/31/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A14
>   dmi.board.name: 0C46Y8
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: A14
>   dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/31/2015:svnDellInc.:
> pnInspiron5521:pvrA14:rvnDellInc.:rn0C46Y8:rvrA00:cvnDellInc.:ct8:cvrA14:
>   dmi.product.family: 103C_5335KV
>   dmi.product.name: Inspiron 5521
>   dmi.product.version: A14
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.83-1~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri

[Desktop-packages] [Bug 481620] Re: Syntax highlighting: inconsistent when in 'sql' text highlight mode