date:20180502

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Lists lack zebra-striping

Status in GTK+:
  Expired
Status in light-themes:
  Fix Released
Status in Ubuntu theme:
  Fix Released
Status in light-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  We had it before and was taken out in Precise. We need this back. It
  makes apps like Rhythmbox much easier to handle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/945430/+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-02 Thread Sum Sim

I have a kinda similar problem on xubuntu 18.04. And had that problem on
xubuntu 16.04.

After I type the password, there is only desktop wallpaper and mouse
pointer (it moves). Then I press Ctr-Alt-Del and go back to password
screen again (screen resolution changes to low), then I enter password
and suddenly all works, everything is upsie-daisy.

I believe it somehow connected to nvidia drivers. Under nvidia-384 it
problem doesn't existed, but on nvidia-390 and 396 it does.

-- 
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:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  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 1768723] Re: package postgresql-common 190 failed to install/upgrade: installed postgresql-common package post-installation script subprocess returned error exit status 1

2018-05-02 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package postgresql-common 190 failed to install/upgrade: installed
  postgresql-common package post-installation script subprocess returned
  error exit status 1

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  The error occurred on first boot after upgrade from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: postgresql-common 190
  ProcVersionSignature: Ubuntu 4.13.0-40.45-generic 4.13.16
  Uname: Linux 4.13.0-40-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 05:39:07 2018
  ErrorMessage: installed postgresql-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-11-02 (1277 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  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: postgresql-common
  Title: package postgresql-common 190 failed to install/upgrade: installed 
postgresql-common package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1768723/+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 1768723] [NEW] package postgresql-common 190 failed to install/upgrade: installed postgresql-common package post-installation script subprocess returned error exit status 1

2018-05-02 Thread Chris

Public bug reported:

The error occurred on first boot after upgrade from 17.10 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: postgresql-common 190
ProcVersionSignature: Ubuntu 4.13.0-40.45-generic 4.13.16
Uname: Linux 4.13.0-40-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Thu May  3 05:39:07 2018
ErrorMessage: installed postgresql-common package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2014-11-02 (1277 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
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: postgresql-common
Title: package postgresql-common 190 failed to install/upgrade: installed 
postgresql-common package post-installation script subprocess returned error 
exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package postgresql-common 190 failed to install/upgrade: installed
  postgresql-common package post-installation script subprocess returned
  error exit status 1

Status in postgresql-common package in Ubuntu:
  New

Bug description:
  The error occurred on first boot after upgrade from 17.10 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: postgresql-common 190
  ProcVersionSignature: Ubuntu 4.13.0-40.45-generic 4.13.16
  Uname: Linux 4.13.0-40-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 05:39:07 2018
  ErrorMessage: installed postgresql-common package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-11-02 (1277 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  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: postgresql-common
  Title: package postgresql-common 190 failed to install/upgrade: installed 
postgresql-common package post-installation script subprocess returned error 
exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1768723/+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 1704765] Re: can't drag file from desktop to folder window on Artful

** Changed in: nautilus
   Status: Confirmed => Expired

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

Title:
  can't drag file from desktop to folder window on Artful

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  I'm running Ubuntu 17.10 (Artful).  If I create a text file on my
  desktop and then attempt to drag it into a Nautilus folder window, it
  fails: when I release the mouse cursor over the folder window nothing
  happens and the file is not moved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1704765/+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 1629251] Re: Some app-indicators not showing menus

[Expired for unity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: unity (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Some app-indicators not showing menus

Status in appmenu-qt package in Ubuntu:
  Expired
Status in gnome-session package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Impact
  ==
  In Ubuntu 16.10 the menus of the Dropbox and hplip app-indicators are not 
working. I attach a video of the problem.

  Test Case
  =
  sudo apt install hplip-gui
  Log out
  Log in (to Unity)
  Click the hp indicator in the top left of the screen.
  Does it show items or is it blank?

  appmenu-qt 0.2.7+14.04.20140305-0ubuntu2  is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Fri Sep 30 11:44:26 2016
  DistUpgraded: 2016-09-01 11:00:51,009 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-11-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-15-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-16-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to yakkety on 2016-09-01 (29 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 08:45:37 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1629251/+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 1629251] Re: Some app-indicators not showing menus

[Expired for appmenu-qt (Ubuntu) because there has been no activity for
60 days.]

** Changed in: appmenu-qt (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Some app-indicators not showing menus

Status in appmenu-qt package in Ubuntu:
  Expired
Status in gnome-session package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Impact
  ==
  In Ubuntu 16.10 the menus of the Dropbox and hplip app-indicators are not 
working. I attach a video of the problem.

  Test Case
  =
  sudo apt install hplip-gui
  Log out
  Log in (to Unity)
  Click the hp indicator in the top left of the screen.
  Does it show items or is it blank?

  appmenu-qt 0.2.7+14.04.20140305-0ubuntu2  is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Fri Sep 30 11:44:26 2016
  DistUpgraded: 2016-09-01 11:00:51,009 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-11-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-15-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-16-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to yakkety on 2016-09-01 (29 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 08:45:37 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1629251/+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 1629251] Re: Some app-indicators not showing menus

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

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

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

Title:
  Some app-indicators not showing menus

Status in appmenu-qt package in Ubuntu:
  Expired
Status in gnome-session package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  Impact
  ==
  In Ubuntu 16.10 the menus of the Dropbox and hplip app-indicators are not 
working. I attach a video of the problem.

  Test Case
  =
  sudo apt install hplip-gui
  Log out
  Log in (to Unity)
  Click the hp indicator in the top left of the screen.
  Does it show items or is it blank?

  appmenu-qt 0.2.7+14.04.20140305-0ubuntu2  is installed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity 7.5.0+16.10.20160906.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.3-0ubuntu7
  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:Unity7
  Date: Fri Sep 30 11:44:26 2016
  DistUpgraded: 2016-09-01 11:00:51,009 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: yakkety
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.6, 4.4.0-9136-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-11-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-15-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-16-generic, x86_64: installed
   virtualbox, 5.1.6, 4.8.0-17-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire [FirePro W5100] [1002:6649] 
(prog-if 00 [VGA controller])
     Subsystem: Dell Bonaire [FirePro W5100] [1028:230c]
  InstallationDate: Installed on 2015-10-17 (348 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Precision Tower 7810
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic 
root=UUID=63c3c29d-24d9-4ecb-8511-3f2291792bc5 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to yakkety on 2016-09-01 (29 days ago)
  dmi.bios.date: 04/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0GWHMW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd04/14/2015:svnDellInc.:pnPrecisionTower7810:pvr01:rvnDellInc.:rn0GWHMW:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 7810
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Thu Sep 29 08:45:37 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1629251/+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 883138] Re: Dim file extensions

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Dim file extensions

Status in GTK+:
  Expired
Status in Nautilus:
  Confirmed
Status in Wine:
  New
Status in enlightenment package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in lesstif2 package in Ubuntu:
  New
Status in mono package in Ubuntu:
  New
Status in nautilus package in Ubuntu:
  Triaged
Status in qt4-x11 package in Ubuntu:
  Opinion
Status in tcltk-defaults package in Ubuntu:
  New
Status in wine package in Ubuntu:
  Incomplete

Bug description:
  Many web browsers have now began dimming less relevant parts of the URL, such 
as the protocol, subdomain, path, and query string.
  I propose we have an option/setting/feature that does the same Nautilus and 
Gtk file dialogs. Dim the the file extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/883138/+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 1742398] Re: package pulseaudio-module-x11 1:8.0-0ubuntu3.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

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

** This bug has been marked a duplicate of bug 1669654
   package pulseaudio 1:8.0-0ubuntu3.2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration

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

Title:
  package pulseaudio-module-x11 1:8.0-0ubuntu3.7 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi , Can someone please help with that bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-x11 1:8.0-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashr3f 1749 F pulseaudio
  Date: Wed Jan 10 09:41:07 2018
  DuplicateSignature:
   package:pulseaudio-module-x11:1:8.0-0ubuntu3.7
   Setting up libpulse-mainloop-glib0:i386 (1:8.0-0ubuntu3.7) ...
   dpkg: error processing package pulseaudio-module-x11 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-09-30 (101 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: pulseaudio
  Title: package pulseaudio-module-x11 1:8.0-0ubuntu3.7 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742398/+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 1669654] Re: package pulseaudio 1:8.0-0ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

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

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

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

Title:
  package pulseaudio failed to install/upgrade: package is in a very bad
  inconsistent state; you should  reinstall it before attempting
  configuration

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulse audio has crashed completely , not able to delete as well as
  reinstall

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aayush 1608 F pulseaudio
  Date: Fri Mar  3 06:24:50 2017
  DuplicateSignature:
   package:pulseaudio:1:8.0-0ubuntu3.2
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package linux-image-4.4.0-36-generic (--configure):
package linux-image-4.4.0-36-generic is not ready for configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-01-16 (411 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: pulseaudio
  Title: package pulseaudio 1:8.0-0ubuntu3.2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0220DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF15213SNW:pvrC10K0BT6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF15213SNW
  dmi.product.version: C10K0BT6
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1669654/+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 1669654] Re: package pulseaudio failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

** Summary changed:

- package pulseaudio 1:8.0-0ubuntu3.2 failed to install/upgrade: package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
+ package pulseaudio failed to install/upgrade: package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration

** Tags added: artful

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

Title:
  package pulseaudio failed to install/upgrade: package is in a very bad
  inconsistent state; you should  reinstall it before attempting
  configuration

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulse audio has crashed completely , not able to delete as well as
  reinstall

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aayush 1608 F pulseaudio
  Date: Fri Mar  3 06:24:50 2017
  DuplicateSignature:
   package:pulseaudio:1:8.0-0ubuntu3.2
   Processing triggers for gconf2 (3.2.6-3ubuntu6) ...
   dpkg: error processing package linux-image-4.4.0-36-generic (--configure):
package linux-image-4.4.0-36-generic is not ready for configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-01-16 (411 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: pulseaudio
  Title: package pulseaudio 1:8.0-0ubuntu3.2 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0220DA
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0220DA:bd11/18/2013:svnSonyCorporation:pnSVF15213SNW:pvrC10K0BT6:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVF15213SNW
  dmi.product.version: C10K0BT6
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1669654/+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 1768712] Re: package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade: パッケージが非常に矛盾した状態に陥りました。設定を試みる前に再インストールすべきです。

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

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 1669654, 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 1669654
   package pulseaudio failed to install/upgrade: package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration

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

Title:
  package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade:
  パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  it happens when install gimp.
  thank you

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio-utils 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1223 F pulseaudio
tosikato   1566 F pulseaudio
  Date: Thu May  3 12:20:14 2018
  ErrorMessage: パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。
  InstallationDate: Installed on 2017-11-23 (160 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64(20171024.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: pulseaudio
  Title: package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade: 
パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768712/+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 1768712] [NEW] package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade: パッケージが非常に矛盾した状態に陥りました。設定を試みる前に再インストールすべきです。

2018-05-02 Thread tako surume

Public bug reported:

it happens when install gimp.
thank you

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: pulseaudio-utils 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1223 F pulseaudio
  tosikato   1566 F pulseaudio
Date: Thu May  3 12:20:14 2018
ErrorMessage: パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。
InstallationDate: Installed on 2017-11-23 (160 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64(20171024.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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: pulseaudio
Title: package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade: 
パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A14
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.

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

Title:
  package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade:
  パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  it happens when install gimp.
  thank you

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio-utils 1:10.0-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1223 F pulseaudio
tosikato   1566 F pulseaudio
  Date: Thu May  3 12:20:14 2018
  ErrorMessage: パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。
  InstallationDate: Installed on 2017-11-23 (160 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64(20171024.1)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: pulseaudio
  Title: package pulseaudio-utils 1:10.0-2ubuntu3.1 failed to install/upgrade: 
パッケージが非常に矛盾した状態に陥りました。設定を試みる 前に再インストールすべきです。
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0G848F
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/07/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768712/+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 1725779] Re: Gnome network manager cannot find authentication binary

2018-05-02 Thread Alex R

** No longer affects: network-manager-openvpn (Ubuntu)

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

Title:
  Gnome network manager cannot find authentication binary

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

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/1725779/+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 1767878] Re: /usr/bin/gnome-software:11:_int_free:GI_libc_free:g_free:array_free:snapd_client_finalize

The stack trace is hinting that something is going wrong in the read
buffer in snapd-glib. Could be inside snapd-glib itself or external
corruption. Nothing stands out, but the code is relatively complex...

** Changed in: gnome-software (Ubuntu)
   Status: New => In Progress

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

Title:
  /usr/bin/gnome-
  software:11:_int_free:__GI___libc_free:g_free:array_free:snapd_client_finalize

Status in gnome-software package in Ubuntu:
  In Progress

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1767878/+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 1768567] Re: Mouse not click after clean install ubuntub18.04

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1768567

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: bionic noclick

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

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

Title:
  Mouse not click after clean install ubuntub18.04

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  After upgrade from 17.10 to 18.04 mouse not accept click. Do a clean
  install. Firs works well but after update the bug start again. Mouse
  work im login screen. I tried in waylan and xorg and is the same. Acer
  aspire f15  intel graphics 520. Core I5-6200u

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768567/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: ubiquity (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: ubiquity (Ubuntu)
   Status: Triaged => In Progress

** Changed in: ubiquity (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in OEM Priority Project:
  Triaged
Status in glib2.0 package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  In Progress
Status in glib2.0 source package in Bionic:
  Invalid
Status in ubiquity source package in Bionic:
  In Progress

Bug description:
  The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
  it was working some weeks/months ago, so this is a recent regression.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1751252/+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 1723403] Re: Gedit doesn't Gain Focus Upon Opening a File in Nautilus

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Gedit doesn't Gain Focus Upon Opening a File in Nautilus

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  If you already have one tab open in gedit, and then minimize gedit, if
  you double click on another file in nautilus, gedit should regain
  focus, but it does not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 13 06:26:01 2017
  InstallationDate: Installed on 2017-10-13 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1723403/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

** Tags added: a2dp bionic mic

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 785479] Re: gtkcalendar emitting incorrect day_selected signal

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  gtkcalendar emitting incorrect day_selected signal

Status in GTK+:
  Expired
Status in wxWidgets:
  Unknown
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When clicking (or selecting via keyboard) on the days surrounding a
  month in the gtk calendar widget, the widget emits two day_selected
  events.

  The first, with an incorrect date, is emitted by
  calendar_set_month_prev & next functions.. the second emitted
  correctly from calendar_select_and_focus_day.

  When calendar_set_month_prev & next is called by the
  calendar_main_button_press and gtk_calendar_key_press, this first
  signal needs to be blocked. (calendar_set_month_prev & next are also
  called, but correctly from the month back and forward buttons)

  When changing from a month with more days (with one of those days
  selected) to a following month with less days, the first signal
  emitted in this case contains an invalid date.

  You can verify this behaviour in the gtk calendar sample. For example
  click may 31st, then click on June 1st in the surrounding days.

  I submitted a patch upstream (for the svn version) on this issue.  A fix 
along these lines could be used in gtk+2.0
  https://bugzilla.gnome.org/show_bug.cgi?id=106161

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libgtk2.0-0 2.24.4-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri May 20 10:33:52 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=
   LC_MESSAGES=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to natty on 2011-04-19 (30 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/785479/+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 30749] Re: Tabs disappear in core Gnome applications

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Tabs disappear in core Gnome applications

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  When opening more than a few tabs in Gnome applications like Gedit,
  Epiphany etc, earlier tabs suddenly disappear with no warning and
  almost without trace. All that is seen are two tiny arrows beside the
  tabs which allows the user to scroll the tab list to reach the other
  tabs.

  When this happens the first few times it's a very confusing, and also
  scary and upsetting experience - "where did my important tab go?" "Did
  I save?" "Please, please, please be in my history".

  After finding out what actually happens, and at least understanding
  it, it is just incredibly annoying and unusable. The huge advantages
  that tabs offer are totally lost: instant overview and one-click
  access. Without those, might as well use separate windows like
  Internet Explorer or Notepad, although they only get as inaccessible
  after their windows have grouped on the task list.

  Almost all other tabbed systems shrink their tabs when needing to, and
  it works great for them. A few expand into multiple rows instead.

  I thought long and hard before filing this bug, because this is a
  sensitive question apparently - common opinion is that this is a
  50/50-issue, some love this, others hate it. Personally I've mostly
  seen hate, and I deeply, strongly feel that this must be addressed one
  way or the other, so here goes.

  Summary on current behaviour:

  * It is scary, surprising and confusing
  * It takes away the instant overview of tabs
  * It takes away the instant access of tabs

  I suggest that:

  * GtkNotebook gets another mode of operation, where tabs shrink instead of 
disappear when space becomes scarce. 
  * If use open an incredible amount of tabs, it's ok to disappear them though, 
we can't do magic and there's just so many pixels.
  * Old mode of operation is also kept, and a global preference for the whole 
Gnome desktop switches all GtkNotebooks to either behaviour for all using 
applications.
  * Default is changed to Resize, because:
- That is what any tab savvy user is used to
- That doesn't scare by making things disappear suddenly
- It's better usability with instant overview and access
  * Nice to have: multiple row tabs as third option.

  So, you heard me right. I propose to add extra options to Gnome. =) I
  think it's warranted though. If it's such a 50/50 issue, there can
  hardly be a good default. The current behaviour is scary and
  unintiuitive, but have a loyal following. Those should be able to
  retain their experience, just like there is spatial and non-spatial
  Nautilus.

  For a more humorous rant on this frustration, I wrote this post a
  little while back: http://ubuntuforums.org/showthread.php?t=124068 =)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/30749/+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 1768509] Re: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all

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

A fix is on the way. Please see bug 1767784.

** This bug has been marked a duplicate of bug 1767784
   [regression] output device not recognized anymore since update 
1:8.0-0ubuntu3.9

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

Title:
  [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I know it was working before with LTS 16.04. Also the sound card is
  shown as dummy when I have tried several times to upload the software
  i  have seen two different sound cards.

  Could you help me fix this?

  18/04 LTS upgraded fresh, no updates

  vincenzo@inspiron530:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  vincenzo@inspiron530:~$ 

  i thought it would find the card automatically. it seems not to have
  the right card or be misconfigured.

  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
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincenzo949 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 12:33:58 2018
  InstallationDate: Installed on 2018-05-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincenzo949 F pulseaudio
  Symptom_Jack: Black Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 530, Realtek ALC888, Black Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.15
  dmi.board.name: 0K216C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768509/+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 1768532] Re: Popup behind the dock

Is your dock set to auto-hide?

If yes, then the dock should be moving out the way.

If no, then nautilus-desktop should be placing that popup in the clearly
defined desktop work area (that does not include under the dock).

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

** Summary changed:

- Popup behind the dock
+ Nautilus-desktop popup behind the ubuntu-dock

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

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

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

Title:
  Nautilus-desktop popup behind the ubuntu-dock

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.04 with Gnome Shell

  Steps to reproduce:
  1. Create a folder on the desktop
  2. Press F2 to change the folder's name

  Expected result:
  The popup where you can write new name is not obstructed by the dock

  What happens instead:
  The popup where you can write new name is partially covered by the dock

  Screenshot attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1768532/+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 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics

Resolution limits are almost always imposed by the motherboard/system
manufacturer. Not the software or CPU/GPU manufacturer. In the case of
your system there are some interesting notes:

---
"*This DisplayPort only supports DP to D-Sub dongles. DP to HDMI dongles and DP
to DVI dongles are not supported.
To power up three monitors, please connect your monitors to 2 x HDMI and 1 x DP
ports or 2 x HDMI and 1 x D-Sub ports via a DP to D-Sub dongle.
HDMI 1 (4K/2K@30Hz) / HDMI 2 (4K/2K@30Hz)
Supports DisplayPort 1.1a with max. resolution up to 4K x 2K (4096x2304) @ 30Hz"
---
[https://www.asrock.com/nettop/Intel/Beebox%20Series/index.asp#Specification]

So it appears the machine has some hardware limits that are relevant
here:

"DP to HDMI dongles and DP to DVI dongles are not supported."
so make sure you're not using converters or converter cables.

"HDMI 1 (4K/2K@30Hz) / HDMI 2 (4K/2K@30Hz)"
so 2560x1440x60Hz is not supported over HDMI. 1920x1080x60Hz is the highest
resolution those HDMI ports can do at full frame rate (presumably 60Hz).
Although if you're OK with stuttering then you might be able to select
2560x1440x30Hz.

"Supports DisplayPort 1.1a with max. resolution up to 4K x 2K (4096x2304) @
30Hz"
Sounds like it should support 2560x1440x60Hz but only if you're using a cable
that is DisplayPort at both ends, because "DP to HDMI dongles and DP to DVI
dongles are not supported".

This is a problem I'm familiar with... A lot of low-power (but modern
CPU) systems are made with graphics connectors that don't allow you to
use the full resolution the GPU is capable of.

Your best bet sounds like trying more cables that are DisplayPort at
both ends.

See also:
https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video
https://en.wikipedia.org/wiki/DisplayPort#Resolution_and_refresh_frequency_limits_for_DisplayPort

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

Title:
Lubuntu: X11 freezing/low resolution on N3150 intel graphics

Status in xorg-server package in Ubuntu:
Incomplete

Bug description:
Hi,
I just installed a fresh 18.04 on an ASRock beebox N3150 machine.

The regular ubuntu desktop installer hanged after entering X11 mode,
machine froze.

I then used Lubuntu alternate installer with the console based
installation, which worked without any problem.

But after rebooting the system again hung after the graphical login
prompt.

I then changed the boot options in /etc/default/grub to give the
kernel the options nosplash nomodeset and to leave the system in
console mode (I had similar experiences with former ubuntu versions on
that machine where X11 did not start when the mode had been set by
console.)

Now X11 works, but comes up in vesa mode (1024x768) only.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
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
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Mon Apr 30 12:25:09 2018
InstallationDate: Installed on 2018-04-30 (0 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+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 1765504] Re: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

2018-05-02 Thread Chenwei

I am faced the same problem when I try to upgrade from 17.10 to 18.04,
but after running the following commands, libp11-kit-gnome-keyring
installed successfully, and my computer boot OK. So far, it is OK.

sudo apt-get remove --purge libp11-kit-gnome-keyring
sudo apt-get install libp11-kit-gnome-keyring
sudo dpkg --configure -a

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

Title:
  package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  error while upgrade!

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  Date: Thu Apr 19 14:58:45 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-0ubuntu3
   libgcc1 1:8-20180414-1ubuntu2
   multiarch-support 2.27-0ubuntu3
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  InstallationDate: Installed on 2014-05-28 (1422 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1765504/+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 1756092] Re: Screen freeze for some time when unlocking

Your bug 1759849 was definitely a duplicate of bug 1748450, so the
remaining problem here must be a different bug...

Please goto comment #26 :)

** This bug is no longer a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Screen freeze for some time when unlocking

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When trying to unlock the machine, sometimes the screen freezes entirely 
(including mouse and keyboard input) for a long time either right away or after 
submitting the password.
  The freeze lasts for 10-20s, and sometimes the display goes into suspend.

  I've seen this behavior on both my computers, both fresh 18.04
  installs.

  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: GNOME
  Date: Thu Mar 15 15:09:26 2018
  InstallationDate: Installed on 2018-02-25 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-01-11 (66 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Tags:  bionic wayland-session
  Uname: Linux 4.15.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+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 1767953] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from g_hash_table_lookup_node()

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

I'm not so sure this is a duplicate.

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  g_hash_table_lookup_node()

Status in gnome-shell package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767953/+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 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

Note that if the workarounds at the top of this bug don't work for you
then you're subscribed to the wrong bug. In that case, please open a new
one.

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

Title:
  Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on
  a desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1749975] Re: Flickering screen with ultra-wide monitor in Wayland mode

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

** Changed in: gdm3 (Ubuntu)
   Status: New => 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/1749975

Title:
  Flickering screen with ultra-wide monitor in Wayland mode

Status in gdm3 package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  1. leave computer until gnome-shell blanks the screen (monitor goes to sleep)
  2. clear GDM screen by swiping up.

  There is a video flicker now when I interact with computer.
  Usually small, but can cover many different UI elements.

  This does not happen if I use the X backend instead of wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 16 16:07:12 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['workspace-g...@mathematical.coffee.gmail.com', 
'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
   b'org.gnome.shell' b'enable-hot-corners' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 
'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'"
  InstallationDate: Installed on 2018-01-05 (42 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2018-01-05 (42 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1749975/+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 1768678] Re: regional settings are far too restrictive

2018-05-02 Thread Jeremy Bicha

As a workaround, why don't you try Canada (English) ?
It uses the US Letter paper size, metric measurement, and the date format is at 
least closer to what you were wanting.

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

Title:
  regional settings are far too restrictive

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

Bug description:
  Settings --> Region & Language --> Formats

  Allows me to select the country, not set the actual format.us
  I live in the US, so this means that I am stuck with

  date: mm/dd/
  time: HH:MM:SS AM/PM
  date:  the weird format which somehow starts with week and ends with 
am/pm
  numbers: 123,456,789.00
  measurements: imperial
  paper: us letter

  basically, since all paper is always "letter", no other country selection 
will work for me.
  however, I don't see why I have to be stuck with the US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units - not "imperial") 
and "infix" date/time formats.

  I could set date and time formats to ISO 8601 for the last 10 years at least, 
and still can do it on Mac.
  This appears to be a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 18:41:18 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768678/+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 26439] Re: Editors crash scrolling file with long lines

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Editors crash scrolling file with long lines

Status in Bluefish:
  Invalid
Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  I have experienced this problem with Gedit (standard Ubuntu 5.10 installation)
  and with Bluefish 1.04 (compiled on my dual opteron), so it might be a gtk 
problem.

  A file with long lines - e.g.:-

  http://www.psr.keele.ac.uk/area/uk/ge59/maj.htm

  will cause the editors to crash if you try to scroll down the document by
  dragging the scroll bar down with the mouse.

  In the terminal, Bluefish gives:-
  (bluefish:15351): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file:
  assertion `filename != NULL' failed

  (bluefish:15351): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file:
  assertion `filename != NULL' failed the dir_icon and unknown_icon items
  in the config file are invalid The application 'bluefish' lost its
  connection to the display :0.0; most likely the X server was shut down
  or you killed/destroyed the application.

  While Gedit gives:-
  The program 'gedit' received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadLength (poly request too large or internal Xlib
  length erro'. (Details: serial 30590 error_code 16 request_code 1
  minor_code 0) (Note to programmers: normally, X errors are reported
  asynchronously; that is, you will receive the error a while after
  causing it. To debug your program, run it with the --sync command line
 option to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error()
  function.) Terminated

  I'm using 2.6.12-9-amd64-k8-smp, Ubuntu 5.10, gtk 2.8.6-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluefish/+bug/26439/+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 1766758] Re: Gnome software can uninstall some programs but not others

2018-05-02 Thread Ken T

So, I've freshly installed the release version of Xubuntu 18.04 and
applied updates, and now Gnome-Mines uninstalls as expected.

However, the "SGT Puzzles Collection" which came bundled with Xubuntu
still refuses to uninstall properly. Gnome Software says it's removed,
yet that cluster of games still appears on the XFCE menu and is
launchable.

Cheers,
Ken.
***

** Attachment added: "SGT games collection still seen on XFCE menu but removed 
according to Gnome Software.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1766758/+attachment/5132547/+files/SGT%20games%20collection%20still%20seen%20on%20XFCE%20menu%20but%20removed%20according%20to%20Gnome%20Software.png

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

Title:
  Gnome software can uninstall some programs but not others

Status in gnome-software package in Ubuntu:
  New

Bug description:
  As seen in Gnome Software 3.28.1 within a daily build of Xubuntu 18.04
  i386 downloaded 12hrs ago.

  I used the Gnome Software GUI to uninstall the games bundled with
  Xubuntu (Gnome Sudoku, Mines, and the cluster of games grouped as "SGT
  Puzzles Collection". Gnome Sudoku was uninstalled as expected, but
  both Mines and the puzzles collection disappeared from the "installed"
  list within Software while still remaining in the XFCE main menu and
  are still launchable. See attached screenshot.

  This is a different bug to the one listed as Bug #1563322, as that one
  refers to externally-sourced programs.

  Thanks,
  Ken.
  ***
  --- 
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: i386
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (0 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180424)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  Package: gnome-software 3.28.1-0ubuntu4
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-19-generic i686
  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-software/+bug/1766758/+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 1750146] Re: Xbox (One) Wireless Controller won't connect

2018-05-02 Thread Jeb E.

I've tried on Ubuntu 18.04 LTS and I'm still getting the same issues.

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

Title:
  Xbox (One) Wireless Controller won't connect

Status in gnome-control-center:
  Confirmed
Status in Linux:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Xbox One Wireless Controllers (Model 1708) refuse to connect via bluetooth 
with Ubuntu 17.10 in the gnome-control-center.
  Placing the controller into pairing mode makes it visible on the Bluetooth 
Devices list and the device pairs, but does not make the full connection needed 
to pull the controller out of pairing mode.

  This renders my controller unusable with my Ubuntu PC unless I want to
  resort to using the wire (microUSB).

  Please fix. See the attached system information below.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-lowlatency 4.13.13
  Uname: Linux 4.13.0-32-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 17 09:26:14 2018
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1750146/+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 1768684] [NEW] Please remove gnome-icon-theme-symbolic

2018-05-02 Thread Jeremy Bicha

Public bug reported:

gnome-icon-theme-symbolic was removed from Debian in December. It has
been replaced by adwaita-icon-theme. Therefore, please remove it from
Ubuntu Cosmic also.

** Affects: gnome-icon-theme-symbolic (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: cosmic

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

Title:
  Please remove gnome-icon-theme-symbolic

Status in gnome-icon-theme-symbolic package in Ubuntu:
  New

Bug description:
  gnome-icon-theme-symbolic was removed from Debian in December. It has
  been replaced by adwaita-icon-theme. Therefore, please remove it from
  Ubuntu Cosmic also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme-symbolic/+bug/1768684/+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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Middle-click titlebar actions (like maximizing vertically) don't work
  in Wayland sessions

Status in GTK+:
  Expired
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  In Gnome Tweak Tool you can configure vertical maximizing for:
    Windows > Titlebar Actions > Middle-Click
  However this feature seems to get ignored in Wayland sessions (it just 
maximizes fully instead). It only works correctly in Xorg Gnome sessions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Thu Jun 15 14:46:04 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2017-05-03 (43 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1698083/+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 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-xenial

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1768678] Re: regional settings are far too restrictive

2018-05-02 Thread sds

** Description changed:

  Settings --> Region & Language --> Formats
  
- Allows me to select the country, not set the actual format.us 
- I live in the US, so this means that I am stuck with 
+ Allows me to select the country, not set the actual format.us
+ I live in the US, so this means that I am stuck with
  
  date: mm/dd/
  time: HH:MM:SS AM/PM
- date:  the imbecilic format which somehow starts with week and ends with 
am/pm
+ date:  the weird format which somehow starts with week and ends with 
am/pm
  numbers: 123,456,789.00
  measurements: imperial
  paper: us letter
  
  basically, since all paper is always "letter", no other country selection 
will work for me.
- however, I don't see why I have to be stuck with the crazy US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units which are 
___NOT___ "imperial" in any way!) and date/time formats that make no sense 
(although, apparently, used by many here).
+ however, I don't see why I have to be stuck with the US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units - not "imperial") 
and "infix" date/time formats.
  
- This is 2018.
- I could set date and time formats to ISO 8601 for the last 10 years at least.
- What happened that you decided to take that away all of a sudden?!
+ I could set date and time formats to ISO 8601 for the last 10 years at least, 
and still can do it on Mac.
+ This appears to be a regression.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 18:41:18 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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

Title:
  regional settings are far too restrictive

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

Bug description:
  Settings --> Region & Language --> Formats

  Allows me to select the country, not set the actual format.us
  I live in the US, so this means that I am stuck with

  date: mm/dd/
  time: HH:MM:SS AM/PM
  date:  the weird format which somehow starts with week and ends with 
am/pm
  numbers: 123,456,789.00
  measurements: imperial
  paper: us letter

  basically, since all paper is always "letter", no other country selection 
will work for me.
  however, I don't see why I have to be stuck with the US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units - not "imperial") 
and "infix" date/time formats.

  I could set date and time formats to ISO 8601 for the last 10 years at least, 
and still can do it on Mac.
  This appears to be a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 18:41:18 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768678/+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 1767445] Re: Uninstalled snaps show most recent channel version, not version to be installed by default

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: Triaged => Fix Committed

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1767445] Re: Incorrect metadata shown for snaps

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Summary changed:

- Incorrect metadata shown for snaps
+ Uninstalled snaps show most recent channel version, not version to be 
installed by default

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Fix Committed

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1768679] [NEW] Bookmark behaviour does not handle directory links

2018-05-02 Thread David LaPointe

Public bug reported:

Nautilus bookmarks fail silently for all links (whether they are
directory links or file links). After dragging the item to the link area
nothing happens.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 20:08:58 2018
ExecutablePath: /usr/bin/nautilus
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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

Title:
  Bookmark behaviour does not handle directory links

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus bookmarks fail silently for all links (whether they are
  directory links or file links). After dragging the item to the link
  area nothing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 20:08:58 2018
  ExecutablePath: /usr/bin/nautilus
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768679/+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 1767445] Re: Incorrect metadata shown for snaps

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

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

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

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

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

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu Cosmic)
   Status: New => Triaged

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

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Triaged

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1719985] Re: flatpak software is not shown in gnome-software

2018-05-02 Thread Andrew Hayzen

The gnome-software-plugin-flatpak was known to have issues in 3.26,
would you be able to try again with Ubuntu 18.04 + gnome-software 3.28 ?

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

Title:
  flatpak software is not shown in gnome-software

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I installed gnome-software-plugin-flatpak which install flatpak and a
  few other packaged.

  After a reboot I opened gnome-software and at the top of the app under
  the headerbar I saw "Sorry, something went wrong" popup.

  I couldnt find any flatpaks shown in the software center.

  Is there something else we need to-do to get flatpaks working in
  17.10?

  Subsequently I can confirm that I can install flatpaks via the command
  line though using the flathub command line webpage.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Wed Sep 27 20:17:46 2017
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 
(20170926)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.0-0ubuntu2
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu2
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1719985/+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 1767445] Re: Incorrect metadata shown for snaps

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu-bionic

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

Title:
  Uninstalled snaps show most recent channel version, not version to be
  installed by default

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Fix Committed
Status in gnome-software source package in Cosmic:
  Triaged

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1767445] Re: Incorrect metadata shown for snaps

Is there any other data apart from the version?

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

Title:
  Incorrect metadata shown for snaps

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Bionic:
  Triaged
Status in gnome-software source package in Cosmic:
  Triaged

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages

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

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

** Changed in: gnome-software (Ubuntu)
   Status: Confirmed => Fix Released

** No longer affects: gnome-software (Ubuntu Bionic)

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

Title:
  "Got unknown content type text/html" error viewing flatpack packages

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Artful:
  New

Bug description:
  Whenever I view a Flatpak package in gnome-software, an in-app
  notification appears saying:

  > Sorry, something went wrong
  > Got unknown content type text/html from reviews.ubuntu.com

  Since this is modal, I then need to dismiss it before being able to do
  anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct  4 01:31:10 2017
  InstallationDate: Installed on 2015-07-22 (804 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snapN/A
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1721049/+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 1768678] [NEW] regional settings are far too restrictive

2018-05-02 Thread sds

Public bug reported:

Settings --> Region & Language --> Formats

Allows me to select the country, not set the actual format.us 
I live in the US, so this means that I am stuck with 

date: mm/dd/
time: HH:MM:SS AM/PM
date:  the imbecilic format which somehow starts with week and ends with 
am/pm
numbers: 123,456,789.00
measurements: imperial
paper: us letter

basically, since all paper is always "letter", no other country selection will 
work for me.
however, I don't see why I have to be stuck with the crazy US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units which are 
___NOT___ "imperial" in any way!) and date/time formats that make no sense 
(although, apparently, used by many here).

This is 2018.
I could set date and time formats to ISO 8601 for the last 10 years at least.
What happened that you decided to take that away all of a sudden?!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May  2 18:41:18 2018
ExecutablePath: /usr/bin/gnome-control-center
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

** Affects: gnome-control-center (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 gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1768678

Title:
  regional settings are far too restrictive

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

Bug description:
  Settings --> Region & Language --> Formats

  Allows me to select the country, not set the actual format.us 
  I live in the US, so this means that I am stuck with 

  date: mm/dd/
  time: HH:MM:SS AM/PM
  date:  the imbecilic format which somehow starts with week and ends with 
am/pm
  numbers: 123,456,789.00
  measurements: imperial
  paper: us letter

  basically, since all paper is always "letter", no other country selection 
will work for me.
  however, I don't see why I have to be stuck with the crazy US customary units 
(https://en.wikipedia.org/wiki/United_States_customary_units which are 
___NOT___ "imperial" in any way!) and date/time formats that make no sense 
(although, apparently, used by many here).

  This is 2018.
  I could set date and time formats to ISO 8601 for the last 10 years at least.
  What happened that you decided to take that away all of a sudden?!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
  Uname: Linux 4.15.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  2 18:41:18 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768678/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-02 Thread James Kent

Reiterating the above experiences regarding the Dell XPS 9560.  Black
screen with nvidia drivers.  Cannot workaround this issue unless I
remove the drivers.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 662051] Re: CR-LFs get duplicated whenever they fall on READ_CHUNK_SIZE boundaries

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

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

Title:
  CR-LFs get duplicated whenever they fall on READ_CHUNK_SIZE boundaries

Status in gedit:
  Expired
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  Gedit massively screws up files whose lines are terminated by CR-LF
  (i.e., Windows-style newlines, or 0D 0A in hex). It reads in a file in
  8192-byte chunks, and then if a CR-LF combo happens to fall on a
  boundary so that the CR is on one side and the LF is on the other,
  then Gedit translates BOTH of them into a newline. The net effect is
  that quite a few newlines get randomly duplicated here and there in
  any reasonably long file with Windows-style newlines when you load it.

  Time to find a new text editor. I've already wasted several minutes
  too many discovering Gedit's design flaws and creating a pointless
  account here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/662051/+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 1265418] Re: Gtk3 bookmark can't be removed if it points to a file

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Gtk3 bookmark can't be removed if it points to a file

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  In the file requestor of Gtk3 you can drag files and directories to
  the sidebar to create bookmarks. If the user drags a file here the
  bookmark can never be deleted because the option is disabled.

  To reproduce:

  1. Open a Gtk3 application such as firefox, gedit etc.
  2. Open the File Open requester.
  3. Drag a file to the bookmarks.
  4. Right click on the file bookmark.

  Expected result: Should be able to click on "Remove" to remove the
  bookmark.

  Actual result: The remove option is always disabled.

  Workaround: Edit ~/.config/gtk-3.0/bookmarks and delete the bookmark
  line.

  Also affects trusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk-3-0 3.8.6-0ubuntu3.1
  Uname: Linux 3.11.0-031100-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan  2 02:49:04 2014
  InstallationDate: Installed on 2013-08-27 (127 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  MarkForUpload: True
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1265418/+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 966697] Re: Transparent panel has themed widgets

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Transparent panel has themed widgets

Status in GTK+:
  Expired
Status in gnome-panel package in Ubuntu:
  Confirmed

Bug description:
  GTK+ 3.4 has introduced a bug with transparent panels.  Specifically,
  upstream gtk+ commit 7603e6e4 breaks setting the "background-image"
  style property to a cairo pattern.  This is the method that gnome-
  panel uses to simulate transparent backgrounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/966697/+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 1716409] Re: Unable to install flatpakref on Ubuntu artful

2018-05-02 Thread Andrew Hayzen

@Ad2, Are you using flatpak version 0.11.4 or 0.11.5 from the PPA ?
There was a regression which I found and reported here
https://github.com/flatpak/flatpak/issues/1632 where flatpakref's could
crash gnome-software. It has since been fixed and released in 0.11.6.

** Bug watch added: github.com/flatpak/flatpak/issues #1632
   https://github.com/flatpak/flatpak/issues/1632

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

Title:
  Unable to install flatpakref on Ubuntu artful

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  I saw a news article with a link to install a flatpak.

  http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4

  I clicked the link expecting to be able to install the flatpak, but
  the experience appears broken. I'm on an up to date Artful install

  What I did was:-

  Click on http://www.omgubuntu.co.uk/2017/09/download-pithos-pandora-app-1-4
  Click the flathub link:- 
https://flathub.org/repo/appstream/io.github.Pithos.flatpakref
  This downloaded the flatpakref file.
  I clicked the file in my browser, nothing happened

  I then tried finding the file in nautilus and double clicked it.
  GNOME Software launched and presented an error "Don't know how to handle 
'file:///home/alan/Downloads/io.github.Pithos.flatpakref' (see screenshot).

  If I search for pithos in GNOME Software I am able to find the older
  version from the deb repo, but not the newer version from flathub.

  Do we not support flatpak/flathub out of the box? Or is my system
  uniquely hosed?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716409/+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 1731581] Re: Context menus do not appear for Gtk text areas upon right-click

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  Context menus do not appear for Gtk text areas upon right-click

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When right-clicking on Gtk text areas (such as an editable text area
  or a text entry field), a context menu does not appear.  The pop-up
  context menu typically lists options such as copy, paste, etc.

  EXAMPLES

  Examples of applications that are impacted include:
  1. Gedit Text Area
  2. Nautlus (editable address bar)
  3. Google Chrome URL bar
  4. GtkHash (text entry fields)

  Interestingly the text areas of some other applications do show pop-up 
context menu when right-clicked:
  1. Libre Office Writer
  2. Web pages in Google Chrome that require text entry (such as this web page)

  RECREATING ISSUE

  I do not have a consistent way to recreate this issue (yet). When I
  first log in, the right-click context menus work fine.  After some
  time of usage, the right-click context menus no longer appear.  If I
  use the computer long enough (over an hour) without rebooting, this
  issue always appears.

  This issue seems to only affect widgets that require text entry.
  However, there is one exception I have noticed: the tabs in Google
  Chrome stop showing pop-up context menus at the same time as this
  issues manifests itself for the rest of gnome-shell applications with
  text areas.

  
  OTHER CONTEXT MENUS

  Context menus for other widgets do appear upon right-click, as
  expected, and work fine.  For example, the context menu for window
  title bars appear when right-clicking on them.  The context menu for
  folders and files in Nautilus also appear when right-clicking on them.

  
  SYSTEM INFORMATION

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy gnome-shell
  gnome-shell:
Installed: 3.26.1-0ubuntu5
Candidate: 3.26.1-0ubuntu5
Version table:
   *** 3.26.1-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 10 18:39:00 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 
'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 
'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 
'ubuntu-d...@ubuntu.com', 
'user-th...@gnome-shell-extensions.gcampax.github.com', 
'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-11-08 (2 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1731581/+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 1733334] Re: ATK doesn't list all children for GtkNotebook when tab contains more than label

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  ATK doesn't list all children for GtkNotebook when tab contains more
  than label

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When gtknotebook have got a tab page that contains something more than
  label we can't access those elements in accerciser.

  For example create a GtkNotebook and put a Bo that contains label and
  an image into the tab page, then observe the hierarchy in the
  accercisser. Those elements won't be show and what's worse if the
  image is used to close the tab, there will be no way to do this.

  more info can be found here:
  https://bugzilla.gnome.org/show_bug.cgi?id=790496

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/174/+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 1721049] Re: "Got unknown content type text/html" error viewing flatpack packages

2018-05-02 Thread Andrew Hayzen

This bug has been fixed with gnome-sofware 3.28, which is found in
Ubuntu 18.04 (bionic).

I don't have permission to nominate this bug for the series artful so
don't want to close this myself, is someone with permission able to set
gnome-software (ubuntu) as fixed released and nominate this for artful?

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

Title:
  "Got unknown content type text/html" error viewing flatpack packages

Status in GNOME Software:
  Expired
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Whenever I view a Flatpak package in gnome-software, an in-app
  notification appears saying:

  > Sorry, something went wrong
  > Got unknown content type text/html from reviews.ubuntu.com

  Since this is modal, I then need to dismiss it before being able to do
  anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Oct  4 01:31:10 2017
  InstallationDate: Installed on 2015-07-22 (804 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.0-0ubuntu3
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snapN/A
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1721049/+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 1767618] Re: system Brightness & Lock app ignores file permissions

On Wed, May 02, 2018 at 07:07:51AM -, steve gooberman-hill wrote:
> I'm agreed that this is the way the system permissions work. But, did you
> see the comment I added to the bug report?

Hi Steve, indeed I did.

> Further investigation shows that file ownership is also ignored
> If I change the ownership and permissions of the file, then they are
> ignored by the Brightness & Lock app
> 
> eve@steve-laptop:~$ ls -l ~/.config/dconf/user
> -rw-r--r-- 1 steve eve 15965 Apr 28 10:37 /home/eve/.config/dconf/user
> 
> ==> Alter lock settings using "Brightness & Lock" app
> 
> eve@steve-laptop:~$ ls -l ~/.config/dconf/user
> -rw-rw-r-- 1 eve eve 15965 Apr 28 11:13 /home/eve/.config/dconf/user
> 
> 
> Eve is no longer the file owner, but is in the group (and she is not in the
> sudo group), so I don't believe that any process she is running should be
> able to change the file permissions and ownership. So I am guessing that
> the screen locking process is either not run by the user, or it is running
> with elevated privileges, which enable it to overwrite the file with a
> different privilege set.

Eve owns the directory /home/eve/.config/dconf/. Thus a process running
as Eve can unlink() any file in this directory regardless of who owns
the file or what permissions are on the file. Then it creates a new
file with any contents -- as you've seen here.

> However, I am not convinced that the existing behaviour is desirable -
> because the screen locking process appears not to check the file
> permissions and ownership, and uses it's elevated privilege status to
> overwrite them.

The screen locking mechanism does not have elevated privileges. It just
runs as her. The assumption is she's the one who wants to protect her
session when she walks away momentarily.

> PS. FWIW Eve is thankfully not interested in Unix system hacking. Social
> engineering on her parents seems a better way to get increased access to
> funny cat videos :-)

Such a pity, I've heard there's a world-wide shortfall of roughly a
million information security professionals. Practicing how to bypass
access controls on childhood computers is a time-honoured traditional
education for the field.

Of course social engineering is also a useful skill. :)

Thanks Steve

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

Title:
  system Brightness & Lock app ignores file permissions

Status in gnome-screensaver package in Ubuntu:
  Won't Fix

Bug description:
  The "Brightness & Lock" app in "System Settings" is ignoring file
  permissions.

  As a sudoo group user, I wish to restrict another user's ability to
  change their user settings (particularly the screen lock settings), so
  they can't switch the lock off

  (I want to restrict my daughter's access to the laptop, so I control
  the password to her account - but she has worked out that she can turn
  the screen lock off)

  Using sudo privileges I can change the file permissions on her
  dconf/user settings

  steve@steve-laptop:/home/eve$ sudo chmod ug-w ~eve/.config/dconf/user
  steve@steve-laptop:/home/eve$ sudo ls -l ~eve/.config/dconf/user
  -r--r--r-- 1 eve eve 15965 Apr 28 10:34 /home/eve/.config/dconf/user

  If I then switch to her account, and use the system settings
  "Brighness & Lock" app to switch the lock off. I then check the file
  permissions on her dconf/user account, and find

  eve@steve-laptop:/home/eve$ sudo ls -l ~eve/.config/dconf/user
  -rw-rw-r-- 1 eve eve 15965 Apr 28 10:37 /home/eve/.config/dconf/user

  I don't believe that any user should have permission to overwrite this
  file if it has read-only permissions

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-screensaver 3.6.1-7ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 28 10:49:12 2018
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to xenial on 2016-10-18 (556 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1767618/+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 1768494] Re: Screen lock doesn't cover the whole screen

** Information type changed from Private Security to Public Security

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

Title:
  Screen lock doesn't cover the whole screen

Status in gnome-screensaver package in Ubuntu:
  New

Bug description:
  I noticed a rather alarming bug today.

  Got a Lenovo T470P with dock and two 1440p screens.
  The laptop is 1440p but I chose 1080p as scaling didn't want to play along.

  To reproduce:
  1. Have the laptop unlocked without the dock.
  2. Lock and/or hibernate, close the lid.
  3. Connect to the dock.
  4. Power on the laptop trough dock.
  5. The connected screens to the dock should light up with the login screen, 
however.. The secondary screen is only covered about 1/4, guessing the same 
scale as 1080p.

  I could open files, browse the web and cause damage trough this
  method.

  It also works if I lock my laptop on the dock, and someone undocks it
  and opens the lid, then does step 2-5 again.

  I saw a "confirmed" bug from 2014, but felt that this needed to be
  brought up, again.

  
  Running 18.04 LTS
  gnome-screensaver on 3.6.1-ubuntu3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screensaver 3.6.1-8ubuntu3
  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: Wed May  2 12:39:19 2018
  InstallationDate: Installed on 2018-03-19 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1768494/+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 1641867] Re: GtkMenu: Submenu navigation triangle doesn't work

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  GtkMenu: Submenu navigation triangle doesn't work

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  The navigation triangle code for keeping a submenu open when the mouse
  is moving diagonally toward it is broken due to incorrect rounding.

  This was reported upstream at:
  https://bugzilla.gnome.org/show_bug.cgi?id=710388

  The attached patch (also submitted upstream) rounds the cursor
  location when calculating the navigation triangle bounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1641867/+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 1767542] Re: Turning off WiFi enables Airplane mode

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

** Changed in: gnome-control-center
   Importance: Unknown => High

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

Title:
  Turning off WiFi enables Airplane mode

Status in gnome-control-center:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-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: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+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 1767445] Re: Incorrect metadata shown for snaps

Removing snapd-glib as that just reflects whatever snapd tells it.
Adding snapd as it gets to decide what this field contains.

** No longer affects: snapd-glib (Ubuntu)

** Also affects: snapd
   Importance: Undecided
   Status: New

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

Title:
  Incorrect metadata shown for snaps

Status in snapd:
  New
Status in Snap Store:
  New
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Ubuntu Software, when showing metadata about a snap package, is most
  of the time, likely to get information which is misleading, since it
  shows info from the *most recently* uploaded snap, regardless of which
  channel the snap was uploaded to.

  An example of this is to search for blender, and see that the version
  shows the edge channel - 2.80-4de142e0b7b and not the stable channel -
  2.79.

  After actually installing the application, the correct metadata is
  shown.

  See https://forum.snapcraft.io/t/unexpected-revision-information-
  exposed-in-some-situations/5163 for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software-plugin-snap 3.28.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 17:33:07 2018
  InstallationDate: Installed on 2015-07-04 (1028 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to bionic on 2018-03-15 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1767445/+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 778054] Salut!

2018-05-02 Thread Nenad

voulez avoir fille ce soir?


cliquez ici

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

Title:
  Packages shouldn't depend on the transitional package python-gobject

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in desktopcouch package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in gnome-utils package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Invalid
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in wine1.4 package in Ubuntu:
  Invalid
Status in zeitgeist package in Ubuntu:
  Fix Released
Status in aptdaemon source package in Trusty:
  Fix Released
Status in eglibc source package in Trusty:
  Won't Fix
Status in libreoffice source package in Trusty:
  Fix Released
Status in system-config-printer source package in Trusty:
  Fix Released
Status in zeitgeist source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  python-zeitgeist depends on python-gobject, which means python-gobject
  cannot be removed from the system. python-gobject is a transitional
  package, and packages should be updated to no longer depend on it.

  [Test Case]

  * Install python-zeitgeist, and verify that python-gobject is not
  installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing python-zeitgeist.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

  ---

  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-02 Thread Milan Pultar

Hi. I am new to this forum. I have recently bought Dell XPS 15 9560 with
GTX 1050 graphic card. I am trying Ubuntu 18.04, but I can't find any
working nvidia driver. From ppa I tried 384, 390 as well as 396, each
installation results in black screen. If I uninstall nvidia driver,
laptop boots normally. I also tried the proprietary driver from Nvidia
website, which didn't work as well. I also tried to switch using nvidia-
prime after installation, which broke Ubuntu and I had to reinstall the
system. So... are there any fixes coming? I don't have xorg.conf file so
deleting it is not an option.

I did not imagine this hardware has so bad support on Linux. Did anybody
have good experience with older Ubuntu and GTX 1050? I don't want to
give up and agree this issue is NOT FIXED.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768603] Re: All review score averages are 5 Stars - 1 Star reviews show as 5 Star

I suspect this is a themeing issue - they show as one star reviews in
Ubuntu desktop 18.04 LTS.

** Attachment added: "Screenshot from 2018-05-03 10-31-14.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768603/+attachment/5132500/+files/Screenshot%20from%202018-05-03%2010-31-14.png

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

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

Title:
  All review score averages are 5 Stars - 1 Star reviews show as 5 Star

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  OS:  Ubuntu Studio 18.04 Bionic Beaver

  (Comes with:
  DE - XFCE4
  Version of application: 3.28.1-0ubuntu4)


  Looking in the Gnome Software application, all applications with any
  ratings show as 5-star.  One-star reviews show as 5-star in the
  reviews section.

  An easy example to demonstrate this issue is to look at the entry for
  WINE.

  5 Star Reviews (x24)
  4 Star Reviews (x9)
  3 Star Reviews (x5)
  2 Star Reviews (x11)
  1 Star Reviews (x45)

  Overall average - 5 Stars.

  Scrolling down to read individual reviews shows five stars for
  obviously negative reviews:

  (5 Star Rating)
  Title:  Doesn't work

  (5 Star Rating)
  Title:  Garbage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768603/+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 1767715] Re: Laptop does not suspend after lid is closed on nvidia drivers

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

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

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

Title:
  Laptop does not suspend after lid is closed on nvidia drivers

Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  System: Ubuntu 18.04 fresh install
  HW: Macbook Pro Retina 15"

  Settings in Tweak: Suspend on Lid closed

  The machine does not suspend after lid is closed

  syslog: ---
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:34 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:35 mbpr15a gnome-shell[1460]: _st_paint_shadow_with_opacity: 
assertion 'shadow_pipeline != NULL' failed

  ...
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 21:46:37 2018
  InstallationDate: Installed on 2018-04-28 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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/1767715/+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 990377] Re: lock icon in User Accounts is at best confusing

2018-05-02 Thread Dan Kortschak

One of my hobbies is to shout into the void; bugs are my favourite.

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

Title:
  lock icon in User Accounts is at best confusing

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  This is a UI issue.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  The lock/unlock button in User Accounts goes against the normal use of
  a lock to indicate the locked state, instead meaning the action of
  locking. This makes the icon confusing. A better approach would be to
  use the commonly used convention, and not have the lock in the button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/990377/+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 1768610] Re: No acceleration after upgrading to 18.04: gnome-session-check-accelerated incorrectly picks llvmpipe

2018-05-02 Thread Martin D. Weinberg

I have figured out the problem: the installer removed nux-tools, left
over from unity, but did not purge it.  This left a start up script in
/etc/X11/Xsession.d which interfered with gnome.  Purged that and the
problem was gone.

So this is a dependency bug in the nux-tools package (or perhaps some
mistakenly identified changed file which turned into evil cruft).  Sigh.
Took me a long time to find this.

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

Title:
  No acceleration after upgrading to 18.04: gnome-session-check-
  accelerated incorrectly picks llvmpipe

Status in gnome-session package in Ubuntu:
  New

Bug description:
  After an upgrade from 17.10 to 18.04, I noticed that all gnome windows
  animations were gone.  After some digging, it seems that gnome-session
  incorrectly assumes that my graphics has no acceleration, when in fact
  it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics
  (i915 driver).

  I've tried this with and without the xserver-xorg-video-intel package
  (a.k.a. Intel driver) with the same behavior.

  The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
  256 bits)  however the system should have DRM 2.0 capability.

  GL checks (e.g. glxinfo, glxgears produce the expected output from a
  working DRM system).

  mesa-utils and mesa-utils-extra are both installed.

  I can't find a work around.  Perhaps there is something wrong with my
  install/upgrade?

  Everything else works fine, although the graphical transitions are no
  longer smooth.  But it would be nice to restore the expected behavior.

  I have attached the log of 'journalctl -b0'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.1-0ubuntu2
  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: Wed May  2 13:06:00 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (739 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1768610/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-05-02 Thread ausiasbcn

Hi, I have the same problem on my Lenovo Y700,
I tried different solutions but the subwoofer doesn't works.

Please,Please,Please, let me know what a kind of test or information you
need to fix the problem.

Thank you.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 990377] Re: lock icon in User Accounts is at best confusing

** Changed in: gnome-control-center
   Status: Confirmed => 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/990377

Title:
  lock icon in User Accounts is at best confusing

Status in gnome-control-center:
  Expired
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  This is a UI issue.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  The lock/unlock button in User Accounts goes against the normal use of
  a lock to indicate the locked state, instead meaning the action of
  locking. This makes the icon confusing. A better approach would be to
  use the commonly used convention, and not have the lock in the button.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/990377/+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 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu
  /graphics-drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+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 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2018-05-02 Thread azanaz

This bug has been affecting me since around 2012 or so, when I was using
Arch linux (still installed btw). Same graphics chip as OP's. Upgraded
ubuntu MATE to 18.04 a week ago, and today the freeze happened again.
This time, I intentionally wanted to test if it was fixed, and found out
that it still was not. It is random as OP said, but easily reproducible
by launching any application involving accelerated 3D. So today I wanted
to turn on the 3D spectrum in VLC, and the screen became garbage like on
the pic below :

https://i.stack.imgur.com/FEaIj.jpg

And since it was VLC, I also heard the looping short bit of my music that was 
playing when my system froze.
So no screenshot possible, the only way out is the reset button.
I can confirm this never happened when I used the proprietary driver.

This is not a production machine, so I'm willing to test possible fixes if 
needed.
Will post my lspci output tomorrow, +whatever else is needed.

Thanks.

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu
  /graphics-drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue

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

** Changed in: im-config (Ubuntu)
   Status: New => Confirmed

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue

Status in im-config package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
  suffer from a graphics issue where parts of their windows hold parts
  of wallpaper or other windows' contents as background.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 09:12:31 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1760818/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-02 Thread Donjan Rodic

Upgraded 17.10 -> 18.04, Thinkpad X460p with GeForce 940MX.
No issues before (even both prime AND bumblebee worked).
Exhaustively tried combinations of blacklisting modules, nvidia.modeset kernel 
lines and reinstalls of both default and ppa 390/396 drivers.
The system will not boot past the filesystem check with nvidia drivers (and 
prime/bumblebee can't load them either), which renders the GPU unusable.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

2018-05-02 Thread Apport retracing service

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1767116
   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

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

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

Bug description:
  During the time i used Xubuntu 16.04, trying to install NVidia 390.48
  it didn't allow me to use Cuda on Quadro cards, then i installed a new
  card GTX750Ti (Gigabyte) it did have the same issues, but downgrading
  to nvidia-384 on additional drivers, it did run OK. Today i did
  reinstalled the new Xubuntu 18.04 and it showed just nvidia-390,
  nvidia-340 and no cuda for nvidia-390.

  Changing to nvidia-340 it keeps mw warning that system crashed, and
  there's no more Nvidia-384. Of course i do not have Cuda yet for GTX
  750 ti, but i also do not have cuda for Quadro card too.

  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: Wed May  2 23:05:05 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.106-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
  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 2018-05-02 (0 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 (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: 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/1768665/+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 1768665] [NEW] 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-com

2018-05-02 Thread Ardit Dashaj

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

Public bug reported:

During the time i used Xubuntu 16.04, trying to install NVidia 390.48 it
didn't allow me to use Cuda on Quadro cards, then i installed a new card
GTX750Ti (Gigabyte) it did have the same issues, but downgrading to
nvidia-384 on additional drivers, it did run OK. Today i did reinstalled
the new Xubuntu 18.04 and it showed just nvidia-390, nvidia-340 and no
cuda for nvidia-390.

Changing to nvidia-340 it keeps mw warning that system crashed, and
there's no more Nvidia-384. Of course i do not have Cuda yet for GTX 750
ti, but i also do not have cuda for Quadro card too.

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: Wed May  2 23:05:05 2018
DuplicateSignature:
 package:nvidia-340:(not installed)
 Unpacking nvidia-340 (340.106-0ubuntu3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
  trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
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 2018-05-02 (0 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 (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: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

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

Bug description:
  During the time i used Xubuntu 16.04, trying to install NVidia 390.48
  it didn't allow me to use Cuda on Quadro cards, then i installed a new
  card GTX750Ti (Gigabyte) it did have the same issues, but downgrading
  to nvidia-384 on additional drivers, it did run OK. Today i did
  reinstalled the new Xubuntu 18.04 and it showed just nvidia-390,
  nvidia-340 and no cuda for nvidia-390.

  Changing to nvidia-340 it keeps mw warning that system crashed, and
  there's no more Nvidia-384. Of course i do not have Cuda yet for GTX
  750 ti, but i also do not have cuda for Quadro card too.

  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: Wed May  2 23:05:05 2018
  DuplicateSignature:
   package:nvidia-340:(not installed)
   Unpacking nvidia-340 (340.106-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/nvidia-340_340.106-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in 
package nvidia-kernel-common-390 390.48-0ubuntu3
  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 2018-05-02 (0 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 (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: 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/1768665/+subscriptions

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

[Desktop-packages] [Bug 1768661] [NEW] can't make WIFI work

2018-05-02 Thread Richard Schneider

Public bug reported:

I can't make the WIfFI operate Compact Presario V2000

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed May  2 17:05:59 2018
DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: ndiswrapper, 1.59: added
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:3091]
InstallationDate: Installed on 2018-05-01 (1 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
Lsusb:
 Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Presario V2000 (EP377UA#ABA)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=3698752e-32a7-443e-959d-c4578e3e85a3 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2018-05-01 (1 days ago)
dmi.bios.date: 01/02/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.name: 3097
dmi.board.vendor: Quanta
dmi.board.version: 47.0F
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd01/02/2006:svnHewlett-Packard:pnPresarioV2000(EP377UA#ABA):pvrRev1:rvnQuanta:rn3097:rvr47.0F:cvnQuanta:ct10:cvrN/A:
dmi.product.name: Presario V2000 (EP377UA#ABA)
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed May  2 12:26:46 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  can't make WIFI work

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't make the WIfFI operate Compact Presario V2000

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May  2 17:05:59 2018
  DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.59: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3091]
  InstallationDate: Installed on 2018-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID

[Desktop-packages] [Bug 437309] Re: Ability: start typing item to select in drop-down menu

** Changed in: libgtk
   Status: Confirmed => Expired

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

Title:
  Ability: start typing item to select in drop-down menu

Status in One Hundred Papercuts:
  Invalid
Status in LibGTK:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  For example: during the Ubuntu installation when the time-zone selection 
window appearing or when I would like to change keyboard layout in the 
installed system, I can't select e.g.: Hungary by type "H" (it should jump to 
the first line starting with "H" when I press it), I only can select the 
country manually and it's very annoying when the list is very long.
  It's a very old missing feature in gnome. KDE, MAC, and Windows already have 
for ages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/437309/+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 608787] Re: GtkFileChooserButton uses previously selected path when choosing an unmounted device

** Changed in: gtk
   Status: Confirmed => Expired

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

Title:
  GtkFileChooserButton uses previously selected path when choosing an
  unmounted device

Status in GTK+:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Overview:
  While the FileChooserButton is not expanded (the FileChooserDialog is not
  shown, just the list in the ComboBox) and the user selects a unmounted device,
  the previously selected paths is automatically assumed.

  Steps to reproduce:
  1) Open gnome-search-tool (or similar tool which uses GtkFileChooserButton)
  2) Select a valid path like the home folder
  3) Select an unmounted device
  4) Press the search button

  Actual result:
  The search is made in the previously selected path (eg. Home folder).
  No warnings or errors are reported about the unmounted device.
  Using the widget from PyGTK I've checked that no signals are fired if the user
  choose an unmounted device and get_uri reports the previous path.

  Expected result:
  The chooser should warn or deny to choose an unmounted device.
  Some signals should inform the developer that an invalid path was selected OR
  BOTH get_uri and get_filename should return the correct unmounted path AND all
  signals should be fired to let the developer to decide if such path is
  valid/mounted.

  Build Date & Platform:
  Tested with:
  GTK 2.14.4 from OpenSuse 11.1
  GTK 2.16.1 from Ubuntu 9.04
  GTK 2.18.3 from Ubuntu 9.10
  GTK 2.20.1 from Debian sid
  GTK 2.21.2 from Ubuntu 10.10 alpha 2

  Additional information:
  This bug is not strictly related to gnome-search-tool, it's reproducible with
  every app that uses GtkFileChooserButton.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/608787/+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 1718238] Re: Giant terminal icon is blocking out the Terminal window buttons

2018-05-02 Thread Simone Bordet

I am on 18.04, and I see the smaller 48x48 icon as reported in 1765704
and by xprop.

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

Title:
  Giant terminal icon is blocking out the Terminal window buttons

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Invalid

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/23

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170918-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 19 12:47:51 2017
  InstallationDate: Installed on 2017-09-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  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/1718238/+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 1726753] Yannick TROCHET

2018-05-02 Thread Trochet Yannick

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

Salut à toi

Comment vas-tu ? J'espère bien ? Mon tel n'est pas en service.

J'ai besoin de solliciter ta faveur.


Garanti
sans virus. www.avast.com

<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

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

Title:
  Après  le démarrage de la session, et au bout de 30 secondes environ,
  un message apparaît signalant qu'une erreur s'est produite. D'autre
  part le clavier numérique ne fonctionne pas.

Status in nautilus package in Ubuntu:
  New

Bug description:
  Il m'est difficile d'en dire plus. Sauf que je constate que ces bogues 
arrivent après la mise à niveau de Ubuntu 17.04 vers Ubuntu 17.10.
  trochet@trochet-ubuntu16:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  Quel est le package utilisé juste après l'ouverture de session, étant donné 
que je n'ai rien ouvert?
  What you expected to happen? J'aimerais pouvoir continuer dans ma session.
  What happened instead? Sans etre dérangé par des messages d'erreur.
  Je viens aussi de voir que l'accent grave du verbe etre ne s'affiche pas.
  Avec la version précédente (Ubuntu 16.04 et 17.04) mon clavier (version 
Français-variante) fonctionnait parfaitement.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 08:43:15 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  InstallationDate: Installed on 2015-10-07 (747 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: nautilus-desktop
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/i386-linux-gnu/libX11.so.6
   XPending () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libgdk-3.so.0
  Title: nautilus-desktop crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to artful on 2017-10-22 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726753/+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 1767542] Re: Turning off WiFi enables Airplane mode

2018-05-02 Thread Slavic Dragovtev

I'm not sure what that meant. Could you rephrase? Note that the issue is
that the user turns OFF Wi-Fi, but the system turns ON Airplane mode.

An analogy would be one wants to flush the toilet, but the computer
turns off the lights, instead. Perhaps some of the goals are
accomplished either way, but it's definitely not a good user experience.

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

Title:
  Turning off WiFi enables Airplane mode

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  Turning off the WiFi from the top right control enables Airplane mode
  (see screenshots). Also after turning off airplane mode, the Wi-Fi is
  not turned back on, rather the Bluetooth is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.1-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: Fri Apr 27 17:46:34 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+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 1768597] Re: package filemanager-actions missing

2018-05-02 Thread Brian Murray

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

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

Title:
  package filemanager-actions missing

Status in nautilus package in Ubuntu:
  New

Bug description:

  nautilus-actions was deprecated in favour of filemanager-actions.

  But 18.04 repositories do not have either of the packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768597/+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 1768597] [NEW] package filemanager-actions missing

You have been subscribed to a public bug:


nautilus-actions was deprecated in favour of filemanager-actions.

But 18.04 repositories do not have either of the packages.

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


** Tags: bot-comment
-- 
package filemanager-actions missing
https://bugs.launchpad.net/bugs/1768597
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nautilus 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

[Desktop-packages] [Bug 1768653] Re: chromium 66 FTBFS on armhf

2018-05-02 Thread Olivier Tilloy

This appears similar to the build errors in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=761193.

Those were initially addressed by disabling exception handling on armhf
(https://anonscm.debian.org/viewvc/pkg-llvm/libcxx/trunk/debian/patches
/disable-arm-excep-handling.diff) and later with a patch that supposedly
implements exception handling on armhf
(https://anonscm.debian.org/viewvc/pkg-llvm/libcxx/trunk/debian/patches
/libcxxabi-arm-ehabi-fix.patch, not forwarded upstream).

** Bug watch added: Debian Bug tracker #761193
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761193

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

Title:
  chromium 66 FTBFS on armhf

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:21: 
error: unknown type name '_Unwind_Control_Block'
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
  ^
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:62: 
error: member reference base type 'void' is not a structure or union
  
static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
   ^ ~
  ../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:434:71: 
error: no member named 'barrier_cache' in '_Unwind_Exception'
  return 
reinterpret_cast(exception_header->unwindHeader.barrier_cache.bitpattern[0]);
 ~~ ^

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1768653/+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 1768653] [NEW] chromium 66 FTBFS on armhf

2018-05-02 Thread Olivier Tilloy

Public bug reported:

FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:21: 
error: unknown type name '_Unwind_Control_Block'

static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
^
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:284:62: 
error: member reference base type 'void' is not a structure or union

static_cast<_Unwind_Control_Block*>(unwind_exception)->barrier_cache.bitpattern[0]);
 ^ ~
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp:434:71: 
error: no member named 'barrier_cache' in '_Unwind_Exception'
return 
reinterpret_cast(exception_header->unwindHeader.barrier_cache.bitpattern[0]);
   ~~ ^

** Affects: chromium-browser (Ubuntu)
 Importance: High
 Assignee: Olivier Tilloy (osomon)
 Status: In Progress

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => High

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Status: New => In Progress

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

Title:
  chromium 66 FTBFS on armhf

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  FAILED: ../../../../../usr/bin/clang++-4.0 -MMD -MF 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o.d 
-DLIBCXXABI_SILENT_TERMINATE -DV8_DEPRECATION_WARNINGS -DUSE_UDEV -DUSE_AURA=1 
-DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC -DFULL_SAFE_BROWSING 
-DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DOFFICIAL_BUILD -DCHROMIUM_BUILD 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS 
-D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -I../.. -Igen -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe 
-pthread -fcolor-diagnostics -no-canonical-prefixes 
--target=arm-linux-gnueabihf -march=armv7-a -mfloat-abi=hard 
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -O2 -fno-ident -fdata-sections 
-ffunction-sections -fno-omit-frame-pointer -gdwarf-3 -g1 -fvisibility=hidden 
-Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wall 
-Wno-unused-variable -Wno-missing-field-initializers -Wno-unused-parameter 
-Wno-c++11-narrowing -Wno-covered-switch-default 
-Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override 
-Wno-undefined-var-template -Wno-nonportable-include-path 
-Wno-address-of-packed-member -Wno-user-defined-warnings -fstrict-aliasing 
-fPIC -std=gnu++14 -nostdinc++ 
-isystem../../buildtools/third_party/libc++/trunk/include 
-isystem../../buildtools/third_party/libc++abi/trunk/include 
-fvisibility-inlines-hidden -fexceptions -frtti -c 
../../buildtools/third_party/libc++abi/trunk/src/cxa_exception.cpp -o 
obj/buildtools/third_party/libc++abi/libc++abi/cxa_exception.o

[Desktop-packages] [Bug 1683359] Re: 17.04 rdesktop crash

2018-05-02 Thread RH

I have just upgraded to Ubuntu 18.04 with rdesktop 1.8.3-2build1 and it
does the same thing. The old (v1.8.3) version still works fine.

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

Title:
  17.04 rdesktop crash

Status in rdesktop package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  After upgrading to 17.04 rdesktop crashes while connecting to windows
  2003:

  
  dm@dm:~$ LANG=C rdesktop -g 1024x758 elk
  Failed to negotiate protocol, retrying with plain RDP.
  Ошибка сегментирования (стек памяти сброшен на диск)
  dm@dm:~$ 

  
  Previous version , i.e. from 16.10 works just fine though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rdesktop/+bug/1683359/+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 1768638] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

2018-05-02 Thread Brian Murray

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

** This bug has been marked a duplicate of bug 1768541
   package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: 
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Problems on "Mise à niveau" to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 20:51:37 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-T4PeWt/0613-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  InstallationDate: Installed on 2013-01-01 (1947 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768638/+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 1767122] Re: duplicity Errors 199 at end backup

2018-05-02 Thread Kenneth Loafman

** Also affects: duplicity
   Importance: Undecided
   Status: New

** Changed in: duplicity
   Status: New => Incomplete

** Changed in: duplicity
   Importance: Undecided => Medium

** Changed in: duplicity
 Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)

** Changed in: duplicity
Milestone: None => 0.7.18

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

Title:
  duplicity Errors 199 at end backup

Status in Déjà Dup:
  New
Status in Duplicity:
  Incomplete
Status in Python:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Hello,

  I use duplicity to backup my file. However. I get always this message
  at end backup with Error 199

  --[ Backup Statistics ]--
  StartTime 1524741993.34 (Thu Apr 26 13:26:33 2018)
  EndTime 1524746175.96 (Thu Apr 26 14:36:15 2018)
  ElapsedTime 4182.62 (1 hour 9 minutes 42.62 seconds)
  SourceFiles 3821570
  SourceFileSize 191576839080 (178 GB)
  NewFiles 2088902
  NewFileSize 19156070 (178 GB)
  DeletedFiles 3
  ChangedFiles 54
  ChangedFileSize 1834439 (1.75 MB)
  ChangedDeltaSize 0 (0 bytes)
  DeltaEntries 2088959
  RawDeltaSize 0 (0 bytes)
  TotalDestinationSizeChange 0 (0 bytes)
  Errors 199lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  
  Step to reproduce :
  1. Configure duplicity
  2. Run a bakup.
  Result
  3. At end backup, you should get Error 199
  -
  uname -r
  4.15.0-20-generic

  My configuration :

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  
  apt-cache policy duplicity 
  duplicity:
Installed: 0.7.17-0ubuntu1
Candidate: 0.7.17-0ubuntu1
Version table:
   *** 0.7.17-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy python
  python:
Installed: 2.7.15~rc1-1
Candidate: 2.7.15~rc1-1
Version table:
   *** 2.7.15~rc1-1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Could you help me please to fix this issues ?

  
  Thanks by advance for your support

  
  Best regards

  Battant

  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: Thu Apr 26 15:58:41 2018
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1767122/+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 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

2018-05-02 Thread Shomz

I've removed the problematic library and was able to finish the
installation/upgrade with no issues.

# apt remove libp11-kit-gnome-keyring

The keyring seems fine as well. Still not sure if this is the way to go.

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  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  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+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 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

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

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

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  installation of this package failed, upgrading from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  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  2 01:39:47 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-keyring (3.28.0.2-1ubuntu1) over (3.20.1-1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-PlRQuy/0830-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768541/+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 1768624] Re: duplicity Errors 192 at end backup

2018-05-02 Thread Kenneth Loafman

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

** This bug has been marked a duplicate of bug 1767122
   duplicity Errors 199 at end backup

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

Title:
  duplicity Errors 192 at end backup

Status in Déjà Dup:
  New
Status in Python:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Hello,

  At end the backup, I get this error

  Could you explain me and help me to fix this issus

  Best regards

  Battant

  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: Wed May  2 20:02:36 2018
  InstallationDate: Installed on 2018-04-29 (3 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/deja-dup/+bug/1768624/+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 1768638] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable w

2018-05-02 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Problems on "Mise à niveau" to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 20:51:37 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-T4PeWt/0613-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  InstallationDate: Installed on 2013-01-01 (1947 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768638/+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 1768638] [NEW] package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable

2018-05-02 Thread Frédérico Hermenegildo

Public bug reported:

Problems on "Mise à niveau" to 17.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed May  2 20:51:37 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DuplicateSignature:
 package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
 Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-T4PeWt/0613-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
  libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
InstallationDate: Installed on 2013-01-01 (1947 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
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: gnome-keyring
Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Problems on "Mise à niveau" to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libp11-kit-gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed May  2 20:51:37 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libp11-kit-gnome-keyring:3.20.1-1ubuntu1
   Unpacking gnome-initial-setup (3.28.0-2ubuntu6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-T4PeWt/0613-libp11-kit-gnome-keyring_3.28.0.2-1ubuntu1_all.deb
 (--unpack):
libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not 
co-installable with libp11-kit-gnome-keyring which has multiple installed 
instances
  ErrorMessage: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) 
is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  InstallationDate: Installed on 2013-01-01 (1947 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  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: gnome-keyring
  Title: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to 
install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: 
no) is not co-installable with libp11-kit-gnome-keyring which has multiple 
installed instances
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1768638/+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 1768637] [NEW] /etc/modprobe.d is not a file

Public bug reported:

Hello, I noticed the following entries in my journal after upgrading to
18.04 LTS from 16.04 LTS:

May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
May 02 12:06:31 hunt gpu-manager[1112]: /etc/modprobe.d is not a file
May 02 12:06:31 hunt gpu-manager[1112]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
May 02 12:06:31 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:31 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1170]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1170]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1254]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1254]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
May 02 12:06:32 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:32 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1316]: /etc/modprobe.d is not a file
May 02 12:06:32 hunt gpu-manager[1316]: Error: can't open 
/lib/modules/4.15.0-20-generic/updates/dkms
May 02 12:06:33 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:33 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=gpu-manager comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Start request repeated 
too quickly.
May 02 12:06:33 hunt systemd[1]: gpu-manager.service: Failed with result 
'start-limit-hit'.


The referenced dkms path does not exist:

sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/dkms
ls: cannot access '/lib/modules/4.15.0-20-generic/updates/dkms': No such file 
or directory
sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/updates/
ls: cannot access '/lib/modules/4.15.0-20-generic/updates/': No such file or 
directory
sarnold@hunt:~$ ls -l /lib/modules/4.15.0-20-generic/
total 5292
lrwxrwxrwx  1 root root  40 Apr 23 21:56 build -> 
/usr/src/linux-headers-4.15.0-20-generic
drwxr-xr-x  2 root root4096 Apr 23 21:56 initrd
drwxr-xr-x 15 root root4096 May  1 18:23 kernel
-rw-r--r--  1 root root 1253762 May  1 18:36 modules.alias
-rw-r--r--  1 root root 1235639 May  1 18:36 modules.alias.bin
-rw-r--r--  1 root root7594 Apr 23 21:56 modules.builtin
-rw-r--r--  1 root root9600 May  1 18:36 modules.builtin.bin
-rw-r--r--  1 root root  552117 May  1 18:36 modules.dep
-rw-r--r--  1 root root  780401 May  1 18:36 modules.dep.bin
-rw-r--r--  1 root root 317 May  1 18:36 modules.devname
-rw-r--r--  1 root root  206162 Apr 23 21:56 modules.order
-rw-r--r--  1 root root 515 May  1 18:36 modules.softdep
-rw-r--r--  1 root root  589679 May  1 18:36 modules.symbols
-rw-r--r--  1 root root  719498 May  1 18:36 modules.symbols.bin
drwxr-xr-x  3 root root4096 May  1 18:23 vdso
sarnold@hunt:~$ find /lib/modules/4.15.0-20-generic/ -name dkms
sarnold@hunt:~$ 


Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-drivers-common 1:0.5.2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux

[Desktop-packages] [Bug 1725779] Re: Gnome network manager cannot find authentication binary

2018-05-02 Thread Alex R

Ubuntu 18.04

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

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

Title:
  Gnome network manager cannot find authentication binary

Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  Confirmed
Status in network-manager-ssh package in Ubuntu:
  Confirmed

Bug description:
  From logs:

  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7424] audit: 
op="connection-activate" uuid="71868b90-3a57-4fee-9933-bf7c9b22d44d" 
name="Library" pid=2510 uid=1000 result="success"
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7473] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Started the VPN service, PID 6934
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7518] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Saw the service appear; activating connection
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V gnome-shell[2510]: Invalid VPN service type (cannot find 
authentication binary)
  Oct 21 13:54:03 V NetworkManager[5935]:  [1508608443.7698] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 Failed to request VPN secrets #3: No agents were available for t
  his request.
  Oct 21 13:54:03 V NetworkManager[5935]:   [1508608443.7708] 
vpn-connection[0x55e8f7b612f0,71868b90-3a57-4fee-9933-bf7c9b22d44d,"Library",0]:
 VPN plugin: state changed: stopped (6)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-pptp-gnome 1.2.4-4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 21 14:07:06 2017
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager-pptp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1725779/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2

2018-05-02 Thread Veli-Jussi Raitila

Deceivingly similar issue, and one that I also encountered, in Fedora
here: https://ask.fedoraproject.org/en/question/120258/macbook-touchpad-
becomes-unresponsive/

And a fix here:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-abb147f32e

It would be nice to have this resolved as it pretty much renders Ubuntu
unusable in affected Macbooks. The issue is reproducible on the 18.04
“LiveCD”.

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

Title:
  'Apple touchpad bcm5974' is temporarily unresponsive after a few
  seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after
  upgrading to 18.04 Beta 2

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Report created by following 
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected
  Let me know if anything is wrong or if I can give more info

  Touchpad worked perfectly in Ubuntu 17.10 when using one and two
  fingers clicks, two finger scrolling, and tapping. (I don't know if
  multitouch worked, but IIRC it did in the past with Unity)

  After upgrading to Bionic Beaver it frequently becomes unresponsive,
  during which I can neither move the mouse cursor or scroll. I can
  repro it most of the time, even directly after rebooting, but not in
  100% of tries. Sometimes, without anything obvious happening (e.g., no
  reboot or logging out), the problem may not occur for an hour or two
  and I cannot repro it on purpose. Then after a while it is back.
  Checking the CPU when it occurs does not show high load. Also repro on
  gdm screen and logging in as a different user account and with a an
  alternative non-gnome-shell session.

  There seem to be two slightly different kinds of unresponsiveness, one
  provoked by one-finger movement, the other provoked by two-finger
  scrolling:

  One-finger movement:

  Triggered by:
  Giving continuous input to touchpad for a second or two. E.g., move one 
finger in a small circle. After 1-3 circles the touchpad becomes unresponsive. 
(Making long straight left-right movements also tends to trigger it, but less 
clearly)

  Results in:
  Stays unresponsive until the finger is lifted from and lowered on touchpad 
again. However, lifting+lowering only restores responsiveness briefly, then it 
stops again. Waiting a few seconds makes it work again, like for two-finger 
scrolling.

  Two-finger scrolling:

  Scroll up and down a few times. Does not seem to matter what the
  application is.

  Results in:
  Scrolling stops after a few movements. Lifting and re-lowering both fingers 
does not seem to make it go again, but it works after waiting a few seconds. 
However scrolling is jumpy most of the time and rarely as smooth as it was in 
17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-input-synaptics (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  BootLog:
   Gave up waiting for suspend/resume device
   /dev/sda4: clean, 1015626/39428096 files, 55279634/157701376 blocks
   Gave up waiting for suspend/resume device
   /dev/sda4: clean, 1026169/39428096 files, 54683366/157701376 blocks
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 12:07:31 2018
  DistUpgraded: 2018-04-08 10:29:35,542 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-15 (2037 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: Apple Inc. MacBookPro5,4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=1f4ef214-a70d-44ac-8515-2d4234f32e38 ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: Upgraded to bionic on 2018-04-08 (7 days ago)
  dmi.bios.date: 06/15/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP53.88Z.00AC.B03.0906151647
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22587A1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro5,4
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22587A1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,4:pvr1.0:rvnAppleInc.:rnMac-F22587A1:rvrMacBookPro5,4:cvnAppleInc.:ct10:cvrMac-F22587A1:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro5,4
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

[Desktop-packages] [Bug 1768634] [NEW] /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected

Public bug reported:

Hello, I noticed the following error messages in my journal after an
upgrade to 18.04 LTS from 16.04 LTS:

The failsafeXServer lines show errors -- the rest is for context:

May 02 12:06:35 hunt systemd[1]: Reached target Multi-User System.
May 02 12:06:35 hunt systemd[1]: Starting Update UTMP about System Runlevel 
Changes...
May 02 12:06:35 hunt systemd[1]: Reached target Graphical failsafe fallback.
May 02 12:06:35 hunt audit[1656]: SYSTEM_RUNLEVEL pid=1656 uid=0 
auid=4294967295 ses=4294967295 msg='old-level=N new-level=3 
comm="systemd-update-utmp" exe="/lib/systemd/systemd-update-utmp" hostname=? 
addr=? terminal=? res=success'
May 02 12:06:35 hunt systemd[1]: Started Update UTMP about System Runlevel 
Changes.
May 02 12:06:35 hunt set-cpufreq[796]: Setting powersave scheduler for all CPUs
May 02 12:06:35 hunt systemd[1]: Startup finished in 4.007s (kernel) + 6.827s 
(userspace) = 10.834s.
May 02 12:06:35 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" 
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 02 12:06:35 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" 
exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 02 12:06:35 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=ondemand comm="systemd" exe="/lib/systemd/systemd" 
hostname=? addr=? terminal=? res=success'
May 02 12:06:35 hunt systemd[1]: Reloading OpenBSD Secure Shell server.
May 02 12:06:35 hunt failsafeXServer[1103]: expr: non-integer argument
May 02 12:06:35 hunt failsafeXServer[1103]: 
/usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected
May 02 12:06:35 hunt failsafeXServer[1103]: xinit 
/usr/share/xdiagnose/failsafeXinit /etc/X11/xorg.conf.failsafe  -- /usr/bin/X  
-br -once -config /etc/X11/xorg.conf.failsafe -logfile 
/var/log/Xorg.failsafe.log
May 02 12:06:35 hunt systemd[1]: Reloaded OpenBSD Secure Shell server.
May 02 12:06:35 hunt sshd[1528]: Received SIGHUP; restarting.
May 02 12:06:35 hunt sshd[1528]: Server listening on 0.0.0.0 port 22.
May 02 12:06:35 hunt sshd[1528]: Server listening on :: port 22.
May 02 12:06:35 hunt nm-dispatcher[1042]: req:6 'connectivity-change': start 
running ordered scripts...
May 02 12:06:35 hunt failsafeXServer[1103]: X.Org X Server 1.19.6
May 02 12:06:35 hunt failsafeXServer[1103]: Release Date: 2017-12-20
May 02 12:06:35 hunt failsafeXServer[1103]: X Protocol Version 11, Revision 0
May 02 12:06:35 hunt failsafeXServer[1103]: Build Operating System: Linux 
4.4.0-119-generic x86_64 Ubuntu
May 02 12:06:35 hunt failsafeXServer[1103]: Current Operating System: Linux 
hunt 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64
May 02 12:06:35 hunt failsafeXServer[1103]: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256
May 02 12:06:35 hunt failsafeXServer[1103]: Build Date: 13 April 2018  
08:07:36PM
May 02 12:06:35 hunt failsafeXServer[1103]: xorg-server 2:1.19.6-1ubuntu4 (For 
technical support please see http://www.ubuntu.com/support)
May 02 12:06:35 hunt failsafeXServer[1103]: Current version of pixman: 0.34.0
May 02 12:06:35 hunt failsafeXServer[1103]: Before reporting problems, 
check http://wiki.x.org
May 02 12:06:35 hunt failsafeXServer[1103]: to make sure that you have 
the latest version.
May 02 12:06:35 hunt failsafeXServer[1103]: Markers: (--) probed, (**) from 
config file, (==) default setting,
May 02 12:06:35 hunt failsafeXServer[1103]: (++) from command line, 
(!!) notice, (II) informational,
May 02 12:06:35 hunt failsafeXServer[1103]: (WW) warning, (EE) error, 
(NI) not implemented, (??) unknown.
May 02 12:06:35 hunt failsafeXServer[1103]: (++) Log file: 
"/var/log/Xorg.failsafe.log", Time: Wed May  2 12:06:35 2018
May 02 12:06:35 hunt failsafeXServer[1103]: (++) Using config file: 
"/etc/X11/xorg.conf.failsafe"
May 02 12:06:35 hunt failsafeXServer[1103]: (==) Using system config directory 
"/usr/share/X11/xorg.conf.d"
May 02 12:06:36 hunt avahi-daemon[854]: Service "Squid deb proxy on hunt" 
(/services/squid-deb-proxy.service) successfully established.
May 02 12:06:36 hunt dbus-daemon[1716]: [session uid=0 pid=1714] AppArmor D-Bus 
mediation is enabled
May 02 12:06:36 hunt dbus-daemon[1716]: [session uid=0 pid=1714] Activating 
service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=1706 comm="zenity 
--warning --text The system is runn" label="unconfined")
May 02 12:06:36 hunt dbus-daemon[1716]: [session uid=0 pid=1714] Successfully 
activated service 'org.a11y.Bus'
May 02 12:06:36 hunt org.a11y.Bus[1716]: dbus-daemon[1723]: Activating service 
name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=1706

[Desktop-packages] [Bug 1768633] [NEW] desktop or window fallen over after standby

2018-05-02 Thread Stefan Helmert

Public bug reported:

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

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


** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial

** Attachment added: "window fallen over"
   
https://bugs.launchpad.net/bugs/1768633/+attachment/5132367/+files/Bildschirmfoto%20vom%202018-05-02%2012-36-57.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:
  New

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

[Desktop-packages] [Bug 1767715] Re: Laptop does not suspend after lid is closed on nvidia drivers

2018-05-02 Thread Meowsus

I'm not using the Nvidia drivers and am experiencing the same issue.

➜  ~ sudo lshw -c video
[sudo] password for meowsus: 
  *-display 
   description: VGA compatible controller
   product: Crystal Well Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 08
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:50 memory:a000-a03f memory:9000-9fff 
ioport:1000(size=64) memory:c-d


For what it's worth here are my inhibitors:

➜  ~ systemd-inhibit --list
 Who: gdm (UID 121/gdm, PID 1524/gsd-power)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: ModemManager (UID 0/root, PID 1039/ModemManager)
What: sleep
 Why: ModemManager needs to reset devices
Mode: delay

 Who: gdm (UID 121/gdm, PID 1520/gsd-media-keys)
What: sleep
 Why: GNOME handling keypresses
Mode: delay

 Who: GNOME Shell (UID 1000/meowsus, PID 2563/gnome-shell)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: NetworkManager (UID 0/root, PID 1082/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: meowsus (UID 1000/meowsus, PID 2729/gsd-media-keys)
What: sleep
 Why: GNOME handling keypresses
Mode: delay

 Who: gdm (UID 121/gdm, PID 1520/gsd-media-keys)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

 Who: UPower (UID 0/root, PID 1349/upowerd)
What: sleep
 Why: Pause device polling
Mode: delay

 Who: meowsus (UID 1000/meowsus, PID 2678/gsd-power)
What: sleep
 Why: GNOME needs to lock the screen
Mode: delay

 Who: meowsus (UID 1000/meowsus, PID 2729/gsd-media-keys)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: GNOME handling keypresses
Mode: block

10 inhibitors listed.

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

Title:
  Laptop does not suspend after lid is closed on nvidia drivers

Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  System: Ubuntu 18.04 fresh install
  HW: Macbook Pro Retina 15"

  Settings in Tweak: Suspend on Lid closed

  The machine does not suspend after lid is closed

  syslog: ---
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:18 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:19 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:22 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:26 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html
 for details
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: (EE) event7  - 
bcm5974: kernel bug: Touch jump detected and discarded.
  Apr 28 21:42:27 mbpr15a /usr/lib/gdm3/gdm-x-session[2063]: See 
https://wayland.freedesktop.org/libinput/doc/1.10.4/touchpad_jumping_cursor.html

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened