date:20171109

** Changed in: scowl (Debian)
   Status: Unknown => Fix Released

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  Won't Fix
Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix
Status in scowl package in Ubuntu:
  Fix Released
Status in hunspell-en-us package in Debian:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  Won't Fix
Status in scowl package in Debian:
  Fix Released

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions

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

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-11-09 Thread luca.mg

Hi Staedtler, I knew You were right, but I gave it a try; too bad
Brother sold a linux supported product while in fact they give no
support, and not a good after sale service for a 10 months old product.

This is (in short) the debugging output:

'sane-find-scanner' output
-- snip 
found USB scanner (vendor=0x04f9 [Brother], product=0x035d [MFC-1910W]) at 
libusb:002:006
-- snip 

'scanimage -L'

[sanei_debug] Setting debug level of dll to 255.
[dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.27
[dll] sane_init/read_dlld: attempting to open directory `./dll.d'
[dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d'
[dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d'
[dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/iscan
[dll] sane_init/read_config: reading dll.d/iscan
[dll] add_backend: adding backend `epkowa'
[dll] sane_init/read_dlld: done.
[dll] sane_init/read_config: reading dll.conf
[dll] add_backend: adding backend `net'
[dll] add_backend: adding backend `abaton'
[dll] add_backend: adding backend `agfafocus'
[dll] add_backend: adding backend `apple'
[dll] add_backend: adding backend `avision'
[dll] add_backend: adding backend `artec'
[dll] add_backend: adding backend `artec_eplus48u'
[dll] add_backend: adding backend `as6e'
[dll] add_backend: adding backend `bh'
[dll] add_backend: adding backend `canon'
[dll] add_backend: adding backend `canon630u'
[dll] add_backend: adding backend `canon_dr'
[dll] add_backend: adding backend `cardscan'
[dll] add_backend: adding backend `coolscan'
[dll] add_backend: adding backend `coolscan3'
[dll] add_backend: adding backend `dell1600n_net'
[dll] add_backend: adding backend `dmc'
[dll] add_backend: adding backend `epkowa'
[dll] add_backend: `epkowa' is already there
-- snip 
-- plenty of lines here, no brother backend though; backends are 
listed in aphabetical order, copy-pasted the text up to 'epkowa', which is the 
Epson Perfection 4490 Photo scanner (unplugged), since it is one of the 
scanners that do not work without tinkering with the backend location

[dll] sane_get_devices
-- snip 
-- plenty of text here too, no brother backend found and loaded, I 
include the Epson Perfection lines 

[dll] load: searching backend `epkowa' in `/usr/lib/x86_64-linux-gnu/sane'
[dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-epkowa.so.1'
[dll] load: dlopen()ing `/usr/lib/x86_64-linux-gnu/sane/libsane-epkowa.so.1'
[dll] init: initializing backend `epkowa'
[dll] init: backend `epkowa' is version 1.0.213
-- snip 
[dll] sane_get_devices: found 0 devices

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).
[dll] sane_exit: exiting
[dll] sane_exit: calling backend `xerox_mfp's exit function
-- snip 
-- plenty of text again, no brother backend, I include the Epson 
Perfection lines. It's in reverse alphabetical order, except for the net backend

[dll] sane_exit: calling backend `epkowa's exit function
[dll] sane_exit: calling backend `dmc's exit function
[dll] sane_exit: calling backend `dell1600n_net's exit function
[dll] sane_exit: calling backend `coolscan3's exit function
[dll] sane_exit: calling backend `coolscan's exit function
[dll] sane_exit: calling backend `cardscan's exit function
[dll] sane_exit: calling backend `canon_dr's exit function
[dll] sane_exit: calling backend `canon630u's exit function
[dll] sane_exit: calling backend `canon's exit function
[dll] sane_exit: calling backend `bh's exit function
[dll] sane_exit: calling backend `artec_eplus48u's exit function
[dll] sane_exit: calling backend `artec's exit function
[dll] sane_exit: calling backend `avision's exit function
[dll] sane_exit: calling backend `apple's exit function
[dll] sane_exit: calling backend `agfafocus's exit function
[dll] sane_exit: calling backend `abaton's exit function
[dll] sane_exit: calling backend `net's exit function
[dll] sane_exit: finished

'xsane' does not see the scanner; and now 'sudo sane-find-scanner'

-- snip 
found USB scanner (vendor=0x04f9 [Brother], product=0x035d [MFC-1910W]) at 
libusb:002:006
-- snip 

'sudo scanimage -L' gave no output except the "No scanners were
identified" message; I realized debug was off, and ran 'sudo export
SANE_DEBUG_DLL=255' which gave "command not found"

the following is the output after 'su root', 'SANE_DEBUG_DLL=255', and 
'sane-find-scanner'
-- snip 
found USB scanner (vendor=0x04f9 [Brother], product=0x035d [MFC-1910W]) at 
libusb:002:006
-- snip

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

2017-11-09 Thread Ross Gammon

** Changed in: ubuntustudio-meta (Ubuntu)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  Fix Committed
Status in lubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in ubuntustudio-meta package in Ubuntu:
  Fix Committed

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Desktop-packages] [Bug 1723117] Re: Desktop icons goes under the Dock, if the Dock is set to auto-hide.

I believe this is a feature and not a bug. Most people using auto-hide
do so because they want to use their full desktop width, which includes
putting icons on the left edge of the desktop. So for many/most users of
auto-hide the current behaviour is probably best.

Workaround: You also have the option of simply moving your icons to a
place where they are never covered.

P.S. The desktop and its icons are rendered by 'nautilus-desktop' from
the 'nautilus' source package.

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

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

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

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

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Desktop icons goes under the Dock, if the Dock is set to auto-hide.

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

Bug description:
  This bug is found in Artful.

  Desktop icons goes under the Dock, if the Dock is set to auto-hide.

  Either the Dock should auto-hide on the Desktop as well, or the
  Desktop Icons should leave a margin with the same size of the Dock.

  This happen both horizontal and vertical Dock positions.

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

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

[Desktop-packages] [Bug 1731397] [NEW] Cant find video driver for Acer Aspire One GZ5

2017-11-09 Thread Candido Pichardo

Public bug reported:

What i exptected to happen:
Install Lubuntu 17.10 and have no problems with video drivers

What happened instead:
Freshly installed Lubuntu 17.10 has problems with video drivers. Especifying 
nomodeset makes it usable but it's not optimal and the max resolution i'm 
getting is 800x600. 

Whenever I install Lubuntu and try to get to the desktop, there is an
about 80% of the screen that is black, and the remaining 20% is normal.
I don't know if it is because of the driver, but

sudo apt-get install xserver-xorg-video-intel
[sudo] password for freddy: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
xserver-xorg-video-intel is already the newest version 
(2:2.99.917+git20170309-0ubuntu1).
xserver-xorg-video-intel set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

This tells me that supposedly the driver is installed.

This is the output of lscpci -v that shows the part of the video
chipset:

freddy@freddy-PC:~$ sudo lspci -v
00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller 
Hub (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Memory 
Controller Hub
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=09 

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Mobile 945GSE Express Integrated 
Graphics Controller
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at 5848 (32-bit, non-prefetchable) [size=512K]
I/O ports at 60c0 [size=8]
Memory at 4000 (32-bit, prefetchable) [size=256M]
Memory at 5850 (32-bit, non-prefetchable) [size=256K]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Kernel modules: i915, intelfb

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller (rev 03)
Subsystem: Acer Incorporated [ALI] Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller
Flags: bus master, fast devsel, latency 0
Memory at 5840 (32-bit, non-prefetchable) [size=512K]
Capabilities: [d0] Power Management version 2

I just want my video to work ok. I installed the Intel microcode
propietary driver and it doesnt seem to work either. I have to hard
power down the pc because the reboot button that i can see in the 20% of
the screen that is viewable doesnt work at all. I'm using the latest
lubuntu, 17.10.

freddy@freddy-PC:~$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10


freddy@freddy-PC:~$ apt-cache policy xorg
xorg:
  Installed: (none)
  Candidate: 1:7.7+19ubuntu3
  Version table:
 1:7.7+19ubuntu3 500
500 http://archive.ubuntu.com/ubuntu artful/main i386 Packages

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic i686
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: i386
CurrentDesktop: LXDE
Date: Fri Nov 10 01:16:59 2017
InstallationDate: Installed on 2017-11-10 (0 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug artful i386

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

Title:
  Cant find video driver for Acer Aspire One GZ5

Status in xorg package in Ubuntu:
  New

Bug description:
  What i exptected to happen:
  Install Lubuntu 17.10 and have no problems with video drivers

  What happened instead:
  Freshly installed Lubuntu 17.10 has problems with video drivers. Especifying 
nomodeset makes it usable but it's not optimal and the max resolution i'm 
getting is 800x600. 

  Whenever I install Lubuntu and try to get to the desktop, there is an
  about 80% of the screen that is black, and the remaining 20% is
  normal. I don't know if it is because of the driver, but

  sudo apt-get install xserver-xorg-video-intel
  [sudo] password for freddy: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  xserver-xorg-video-intel is already the newest version 
(2:2.99.917+git20170309-0ubuntu1).
  xserver-xorg-video-intel set to manually installed.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  This tells me that supposedly the driver is installed.

  This is the output of lscpci -v that shows the part of the video

[Desktop-packages] [Bug 1728791] Re: [SRU] pulseaudio-droid module crashes on start

2017-11-09 Thread bhushan

@jr : Sorry to bother you again, but can you re-upload with this patch
instead of previous one? Also, do I have to change the version given
1:8.0-0ubuntu3.5 is already uploaded to xenial-proposed? If so let me
know.

** Patch added: "fix-lp-1728791-proper.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+attachment/5006771/+files/fix-lp-1728791-proper.debdiff

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

Title:
  [SRU] pulseaudio-droid module crashes on start

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4

  [Impact]

   * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) 
from using the pulseaudio-modules-droid on android devices.
   * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates 
enabled.
   * Last 3 releases of pulseaudio included multiple patches which modified 
behavior of pulsecore library but required changes were not made in 
pulseaudio-module-droid.
   * This results in crash in pulseaudio-modules-droid

  
  #0  init_profile (u=0x59528) at modules/droid/module-droid-card.c:370
  #1  module_droid_card_22_LTX_pa__init (m=0x3c3f8) at 
modules/droid/module-droid-card.c:923
  #2  0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 
"module-droid-card-22", argument=0x0) at pulsecore/module.c:180
  #3  0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, 
fail=0x3c1f4) at pulsecore/cli-command.c:439
  #4  0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at 
pulsecore/cli-command.c:2134
  #5  0xf76f6fc8 in pa_cli_command_execute_line (c=, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155
  #6  0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module 
module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153
  #7  0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at 
pulsecore/ioline.c:269
  #8  do_read (l=0x3c208) at pulsecore/ioline.c:337
  #9  do_work (l=0x3c208) at pulsecore/ioline.c:386
  #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655
  #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898
  #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, 
retval=0xfffef1c4) at pulse/mainloop.c:929
  #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, 
retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944
  #14 0x000158ca in main (argc=, argv=) at 
daemon/main.c:1152

  
  [Test Case]

   * Start pulseaudio
   * From another session run pacmd
   * In prompt type load-module module-droid-discover
   * On ubuntu touch devices, it will crash at startup

  [Regression Potential]

   * There is no regression potential for other parts of pulseaudio
  components.

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

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

[Desktop-packages] [Bug 1731392] [NEW] package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-09 Thread alejandro hurtado chacñama

Public bug reported:

this problem always appears when starting the operating system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: inkscape 0.91-7ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Nov  8 11:06:18 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-02-17 (265 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: inkscape
Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in inkscape package in Ubuntu:
  New

Bug description:
  this problem always appears when starting the operating system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: inkscape 0.91-7ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  8 11:06:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-17 (265 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: inkscape
  Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731392] Re: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-09 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 inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1731392

Title:
  package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in inkscape package in Ubuntu:
  New

Bug description:
  this problem always appears when starting the operating system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: inkscape 0.91-7ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Nov  8 11:06:18 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-02-17 (265 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: inkscape
  Title: package inkscape 0.91-7ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728791] Re: [SRU] pulseaudio-droid module crashes on start

2017-11-09 Thread bhushan

Ah crap. I did just realize I had uploaded a totally wrong patch, meh I
will upload proper patch in bit.. (basically patch which was in diff was
wrong then what I reported earlier)

** Tags removed: verification-needed-xenial
** Tags added: verification-faileed-xenial

** Tags removed: verification-faileed-xenial
** Tags added: verification-failed-xenial

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

Title:
  [SRU] pulseaudio-droid module crashes on start

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4

  [Impact]

   * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) 
from using the pulseaudio-modules-droid on android devices.
   * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates 
enabled.
   * Last 3 releases of pulseaudio included multiple patches which modified 
behavior of pulsecore library but required changes were not made in 
pulseaudio-module-droid.
   * This results in crash in pulseaudio-modules-droid

  
  #0  init_profile (u=0x59528) at modules/droid/module-droid-card.c:370
  #1  module_droid_card_22_LTX_pa__init (m=0x3c3f8) at 
modules/droid/module-droid-card.c:923
  #2  0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 
"module-droid-card-22", argument=0x0) at pulsecore/module.c:180
  #3  0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, 
fail=0x3c1f4) at pulsecore/cli-command.c:439
  #4  0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at 
pulsecore/cli-command.c:2134
  #5  0xf76f6fc8 in pa_cli_command_execute_line (c=, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155
  #6  0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module 
module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153
  #7  0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at 
pulsecore/ioline.c:269
  #8  do_read (l=0x3c208) at pulsecore/ioline.c:337
  #9  do_work (l=0x3c208) at pulsecore/ioline.c:386
  #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655
  #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898
  #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, 
retval=0xfffef1c4) at pulse/mainloop.c:929
  #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, 
retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944
  #14 0x000158ca in main (argc=, argv=) at 
daemon/main.c:1152

  
  [Test Case]

   * Start pulseaudio
   * From another session run pacmd
   * In prompt type load-module module-droid-discover
   * On ubuntu touch devices, it will crash at startup

  [Regression Potential]

   * There is no regression potential for other parts of pulseaudio
  components.

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

-- 
Mailing list: https://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 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2017-11-09 Thread michael deer

Im running android jelly bean on a coolpad quatro 2. No problems so far.
The error was generated automatically and affected nothing on my system.
Not that i could tell anyway

On Thu, Nov 9, 2017 at 11:06 PM, Rakesh 
wrote:

> Hello everyone,
>
> I am facing this bug, I am not able to mount my android device.
> Is there any quick fix for this like restarting gvfsd-mtp?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1725871).
> https://bugs.launchpad.net/bugs/1706097
>
> Title:
>   gvfsd-mtp crashed with SIGSEGV
>
> Status in gvfs package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I get this every day when I have connected my Android phone for
>   charging its battery.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 17.10
>   Package: gvfs-backends 1.32.1-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
>   Uname: Linux 4.11.0-10-generic x86_64
>   ApportVersion: 2.20.6-0ubuntu4
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: GNOME
>   Date: Mon Jul 24 11:29:55 2017
>   ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
>   InstallationDate: Installed on 2015-04-30 (816 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6
> /org/gtk/gvfs/exec_spaw/8
>   ProcEnviron:
>LANG=en_US.UTF-8
>LANGUAGE=en_US
>PATH=(custom, user)
>SHELL=/bin/bash
>XDG_RUNTIME_DIR=
>   SegvAnalysis:
>Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
>PC (0x7fea768b6cc9) ok
>source "0x18(%rax)" (0x0018) not located in a known VMA region
> (needed readable region)!
>destination "%rax" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gvfs
>   StacktraceTop:
>() at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>() at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>   Title: gvfsd-mtp crashed with SIGSEGV
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare
> sudo wireshark
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1706097/+subscriptions
>

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I get this every day when I have connected my Android phone for
  charging its battery.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:29:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (816 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
   PC (0x7fea768b6cc9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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

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

[Desktop-packages] [Bug 1706097] Re: gvfsd-mtp crashed with SIGSEGV

2017-11-09 Thread Rakesh

Hello everyone,

I am facing this bug, I am not able to mount my android device.
Is there any quick fix for this like restarting gvfsd-mtp?

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

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I get this every day when I have connected my Android phone for
  charging its battery.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.32.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Mon Jul 24 11:29:55 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2015-04-30 (816 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.6 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fea768b6cc9:mov0x18(%rax),%rax
   PC (0x7fea768b6cc9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo 
wireshark

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

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

[Desktop-packages] [Bug 1731273] Re: Super + L (Ubuntu 17.10) - Lock screen does not work

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

** Tags added: lock

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

Title:
  Super + L (Ubuntu 17.10) - Lock screen does not work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 installed. Upgraded from 17.04.
  GDM as login manager active. 
  Gnome Session on wayland in use.
  Tried to press Super + L but without any affect. All other shortcuts and keys 
are working.

  Gnome Session on X11 without any issues. Super + L is working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  Uname: Linux 4.13.0-041300-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 12:24:38 2017
  InstallationDate: Installed on 2017-04-15 (207 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-20 (20 days ago)

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2017-11-09 Thread Hui Wang

Upgraded the pulseaudio from -proposed, and verified the dock analog
audio (lineout + speaker) worked well.

changed  verification-needed-xenial to  verification-done-xenial

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

** Changed in: hwe-next
   Status: In Progress => Fix Committed

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

-- 
Mailing list: https://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 1686189] Re: External monitor connecting problem on Intel graphics card

2017-11-09 Thread Kai-Heng Feng

> On 9 Nov 2017, at 6:04 PM, Giacomo Orlandi <1686...@bugs.launchpad.net> wrote:
> 
> @Kai-Heng I'm running that now it seems to be working well:
> $ uname -a
> Linux giacomo-awin-latitude 4.4.0-100-generic #123-Ubuntu SMP Thu Nov 2 
> 10:16:13 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> 
> 
> I see many changes in the changelog, what's the patch that fixed it?

This one:
- drm/dp/mst: save vcpi with payloads

Kai-Heng

> 
> -- 
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1686189
> 
> Title:
>  External monitor connecting problem on Intel graphics card
> 
> Status in linux package in Ubuntu:
>  Confirmed
> Status in xorg package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  I am facing a problem with Intel Graphics driver. I have external
>  monitor and in display settings the second monitor is detecting but
>  it's not working, so could you email me a solution.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.04
>  Package: xorg 1:7.7+13ubuntu3
>  Uname: Linux 4.4.25-040425-generic x86_64
>  .tmp.unity_support_test.0:
> 
>  ApportVersion: 2.20.1-0ubuntu2.5
>  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: Tue Apr 25 21:45:16 2017
>  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
>  DistroCodename: xenial
>  DistroVariant: ubuntu
>  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
>  GraphicsCard:
>   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
> (rev 09) (prog-if 00 [VGA controller])
> Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
>  InstallationDate: Installed on 2017-04-25 (0 days ago)
>  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 
> (20160803)
>  MachineType: Dell Inc. Inspiron 3537
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
> root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
>  SourcePackage: xorg
>  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
>  dmi.bios.date: 04/30/2014
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: A08
>  dmi.board.name: 03JPPR
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: A00
>  dmi.chassis.type: 8
>  dmi.chassis.vendor: Dell Inc.
>  dmi.chassis.version: A08
>  dmi.modalias: 
> dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
>  dmi.product.name: Inspiron 3537
>  dmi.product.version: A08
>  dmi.sys.vendor: Dell Inc.
>  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>  version.ia32-libs: ia32-libs N/A
>  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
>  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
>  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
>  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
>  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
>  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20160325-1ubuntu1.2
>  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
> 1:1.0.12-1build2
>  xserver.bootTime: Tue Apr 25 21:37:24 2017
>  xserver.configfile: default
>  xserver.errors:
> 
>  xserver.logfile: /var/log/Xorg.0.log
>  xserver.outputs:
>   product id   17900 
>   vendor AUO
>  xserver.version: 2:1.18.4-0ubuntu0.2
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Tue Apr 25 21:45:16 2017
  DistUpgraded:

[Desktop-packages] [Bug 1652436] Re: nvidia-367 367.57-0ubuntu0.14.04.1: nvidia-367 kernel module failed to build [error: #error kmem_cache_create() conftest failed!]

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

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

** Summary changed:

- nvidia-367 367.57-0ubuntu0.14.04.1: nvidia-367 kernel module failed to build 
[error: #error kmem_cache_create() conftest failed!]
+ nvidia-* kernel module failed to build [error: #error kmem_cache_create() 
conftest failed!]

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

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

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

Title:
  nvidia-* kernel module failed to build [error: #error
  kmem_cache_create() conftest failed!]

Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-367 367.57-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.13.0-105.152-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-105-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-106-generic
  Date: Sat Dec 24 16:25:22 2016
  DuplicateSignature: 
dkms:nvidia-367:367.57-0ubuntu0.14.04.1:/var/lib/dkms/nvidia-367/367.57/build/conftest/functions.h:13:2:
 error: #error kmem_cache_create() conftest failed!
  InstallationDate: Installed on 2015-02-14 (679 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageVersion: 367.57-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.14.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1505409] Re: gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from _XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to xwayland lost"]

Nicolás,

Yes please. In particular please try to report crashes using the crash files 
left in /var/crash/ using this command:
  ubuntu-bug /var/crash/YOURFILE.crash
or if that fails then:
  apport-cli /var/crash/YOURFILE.crash

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

Title:
  gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from
  _XEventsQueued() from XPending() from gdk_check_xpending()
  ["Connection to xwayland lost"]

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

Bug description:
  https://errors.ubuntu.com/problem/d0252e2b465152efea2511e72f1e31681e2b2742

  ---

  Occurred during start-up, before I did anything special...

  1 Ubuntu Wily Werewolf (development branch) 15.10
  2 3.16.3-1ubuntu6
  3&4 not applicable

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: gnome-shell 3.16.3-1ubuntu6
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 12 19:22:07 2015
  DisplayManager: gdm
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2015-10-08 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   SHELL=/bin/false
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () 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: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2017-11-09 Thread Hui Wang

@Daniel,

OK, will do it today.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1567427] Re: gnome-shell crashes when touchscreen is touched

** Tags added: touch

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

Title:
  gnome-shell crashes when touchscreen is touched

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 16.04 with gnome-shell, the gnome-shell would crash every
  time I touch the touchscreen of my laptop (ASUS-S400CA). Sometimes the
  session would just restart, but when I touch again the whole session
  would just crash and drive me back to gdm.

  There are related log line in journald says:

  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (II) XKB: 
generating xkmfile /tmp/server-3D32AD876081C702D9B5501C336C5CB154F5C8D2.xkm
  4月 07 20:38:14 ubuntu-s400ca kernel: gnome-shell[15211]: segfault at c ip 
7f2ad1ae9f87 sp 7ffc96f9e6b0 error 4 in 
libcaribou.so.0.0.0[7f2ad1ae+1e000]
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: syntax 
error: line 1 of stdin
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: Errors 
encountered in stdin; not compiled.
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) Error 
compiling keymap (server-3D32AD876081C702D9B5501C336C5CB154F5C8D2)
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) XKB: 
Couldn't compile keymap
  4月 07 20:38:15 ubuntu-s400ca polkitd(authority=local)[874]: Unregistered 
Authentication Agent for unix-session:6 (system bus name :1.360, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale zh_CN.UTF-8) 
(disconnected from bus)
  4月 07 20:38:15 ubuntu-s400ca gnome-session[15129]: 
gnome-session-binary[15129]: WARNING: Application 'gnome-shell.desktop' killed 
by signal 11

  You may find the full log in the attached files generated by ubuntu-
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Thu Apr  7 20:41:10 2016
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1567427] Re: gnome-shell crashes when touchscreen is touched

Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a ".crash" file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the 
crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 
'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is 
the crash you would like to report. If you get an error that you aren't allowed 
to access this report you will have to file it with 'sudo ubuntu-bug 
/var/crash/_my_crash_report.crash'.

When the crash report has been uploaded to a new bug, please mention
that new bug's ID here.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => 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/1567427

Title:
  gnome-shell crashes when touchscreen is touched

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  In Ubuntu 16.04 with gnome-shell, the gnome-shell would crash every
  time I touch the touchscreen of my laptop (ASUS-S400CA). Sometimes the
  session would just restart, but when I touch again the whole session
  would just crash and drive me back to gdm.

  There are related log line in journald says:

  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (II) XKB: 
generating xkmfile /tmp/server-3D32AD876081C702D9B5501C336C5CB154F5C8D2.xkm
  4月 07 20:38:14 ubuntu-s400ca kernel: gnome-shell[15211]: segfault at c ip 
7f2ad1ae9f87 sp 7ffc96f9e6b0 error 4 in 
libcaribou.so.0.0.0[7f2ad1ae+1e000]
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: syntax 
error: line 1 of stdin
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: Errors 
encountered in stdin; not compiled.
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) Error 
compiling keymap (server-3D32AD876081C702D9B5501C336C5CB154F5C8D2)
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) XKB: 
Couldn't compile keymap
  4月 07 20:38:15 ubuntu-s400ca polkitd(authority=local)[874]: Unregistered 
Authentication Agent for unix-session:6 (system bus name :1.360, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale zh_CN.UTF-8) 
(disconnected from bus)
  4月 07 20:38:15 ubuntu-s400ca gnome-session[15129]: 
gnome-session-binary[15129]: WARNING: Application 'gnome-shell.desktop' killed 
by signal 11

  You may find the full log in the attached files generated by ubuntu-
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Thu Apr  7 20:41:10 2016
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

@hui.wang,

Please test: https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.5
And then update the above tag 
(https://wiki.ubuntu.com/StableReleaseUpdates#Verification)

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1730543] Re: In gnome-shell, unlocking screen before suspend completes means no password is required on resume

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

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 1532508, 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 1532508
   Screen shown briefly after opening closed laptop lid, before even unlocking

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

Title:
  In gnome-shell, unlocking screen before suspend completes means no
  password is required on resume

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sometimes it can take gnome-shell a few seconds after the lock screen
  appears before suspend completes. If during this time you enter your
  password and unlock gnome-shell, upon resume there is no lock screen.
  Obviously this is a security issue, because your data is available to
  whoever resumes the PC.

  To do this, you have to manually suspend the machine (eg by locking
  the screen and then pressing the suspend icon). I often have to do
  this of another bug whereby gnome-shell doesn't always suspend when
  you close the laptop lid if there is an external monitor connected
  (often it just switches to using the external monitor as primary when
  you close the lid).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  Uname: Linux 4.14.0-rc8-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  7 08:59:31 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-16 (82 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-08-17 (82 days ago)

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

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

[Desktop-packages] [Bug 1729887] Re: Drag-and-drop to desktop not possible without copying the file under wayland

** Tags added: dnd

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

Title:
  Drag-and-drop to desktop not possible without copying the file under
  wayland

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  since my upgrade to Ubuntu Desktop 17.10 all files moved with drag-
  and-drop from any folder to my desktop are copied but not moved.

  Using strg+x and strg+v works. When i open the desktop as a folder
  usual drag-and-drop from different folders do work without copying the
  files.

  This is wayland related. Ubuntu Desktop 17.10 with Xorg performs like
  before and allows normal drag-and-drop from folders to the desktop.

  
  (I reported the issue before at https://askubuntu.com/questions/972533/)

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

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

[Desktop-packages] [Bug 1730625] Re: Dragging and dropping files into MPV doesn't work in Wayland sessions

** Tags added: wayland

** Tags added: wayland-session

** Tags added: dnd

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

Title:
  Dragging and dropping files into MPV doesn't work in Wayland sessions

Status in gnome-shell package in Ubuntu:
  New
Status in mpv package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Dragging and dropping files into MPV doesn't work in Wayland sessions.
  Only Xorg sessions.

  I have no idea right now if this is an MPV, Wayland protocol or Gnome
  Shell issue.

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

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

[Desktop-packages] [Bug 1731378] Re: wifi settings unable to connect or show visible networks after laptop closes and then opens

2017-11-09 Thread Colin Watson

** Project changed: launchpad => network-manager (Ubuntu)

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

Title:
  wifi settings unable to connect or show visible networks after laptop
  closes and then opens

Status in network-manager package in Ubuntu:
  New

Bug description:
  I recently upgraded to 17.10 and have been having problems connecting
  to wifi. Wifi Settings shows no available networks and says
  Unavailabel - 802.1x Supplicant Failed. If I attempt to turn off wifi
  and turn back on, it will not connect at all and I have to either
  restart or open a terminal and do a network restart. It's been
  frustrating. I'm relatively new to Linux and for what I use it for,
  it's much better than Windows. Thanks for the help.

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

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

[Desktop-packages] [Bug 1728791] Re: [SRU] pulseaudio-droid module crashes on start

bhushan,

Please test the proposed package and then change the above tag
(https://wiki.ubuntu.com/StableReleaseUpdates#Verification).

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

Title:
  [SRU] pulseaudio-droid module crashes on start

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4

  [Impact]

   * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) 
from using the pulseaudio-modules-droid on android devices.
   * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates 
enabled.
   * Last 3 releases of pulseaudio included multiple patches which modified 
behavior of pulsecore library but required changes were not made in 
pulseaudio-module-droid.
   * This results in crash in pulseaudio-modules-droid

  
  #0  init_profile (u=0x59528) at modules/droid/module-droid-card.c:370
  #1  module_droid_card_22_LTX_pa__init (m=0x3c3f8) at 
modules/droid/module-droid-card.c:923
  #2  0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 
"module-droid-card-22", argument=0x0) at pulsecore/module.c:180
  #3  0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, 
fail=0x3c1f4) at pulsecore/cli-command.c:439
  #4  0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at 
pulsecore/cli-command.c:2134
  #5  0xf76f6fc8 in pa_cli_command_execute_line (c=, 
s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, 
fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155
  #6  0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module 
module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153
  #7  0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at 
pulsecore/ioline.c:269
  #8  do_read (l=0x3c208) at pulsecore/ioline.c:337
  #9  do_work (l=0x3c208) at pulsecore/ioline.c:386
  #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655
  #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898
  #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, 
retval=0xfffef1c4) at pulse/mainloop.c:929
  #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, 
retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944
  #14 0x000158ca in main (argc=, argv=) at 
daemon/main.c:1152

  
  [Test Case]

   * Start pulseaudio
   * From another session run pacmd
   * In prompt type load-module module-droid-discover
   * On ubuntu touch devices, it will crash at startup

  [Regression Potential]

   * There is no regression potential for other parts of pulseaudio
  components.

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

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

[Desktop-packages] [Bug 1731378] [NEW] wifi settings unable to connect or show visible networks after laptop closes and then opens

You have been subscribed to a public bug:

I recently upgraded to 17.10 and have been having problems connecting to
wifi. Wifi Settings shows no available networks and says Unavailabel -
802.1x Supplicant Failed. If I attempt to turn off wifi and turn back
on, it will not connect at all and I have to either restart or open a
terminal and do a network restart. It's been frustrating. I'm relatively
new to Linux and for what I use it for, it's much better than Windows.
Thanks for the help.

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

-- 
wifi settings unable to connect or show visible networks after laptop closes 
and then opens
https://bugs.launchpad.net/bugs/1731378
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager 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 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions

** Tags added: session

** Tags removed: session
** Tags added: wayland-session

-- 
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+:
  Confirmed
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 1717155] Re: Xwayland refresh rate reported by xrandr is incorrect

** Tags added: wayland

** Tags added: wayland-session

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

Title:
  Xwayland refresh rate reported by xrandr is incorrect

Status in wayland:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xwayland refresh rate reported by 'xrandr' is incorrect:

1920x1200   59.88*+

  Actually my hardware runs at 59.95Hz, as confirmed by 'weston-info'.

  If Xwayland is reporting the wrong frequency to apps via Xrandr then
  apps and toolkits implementing frame clocks (i.e. not synchronously
  tied to swap buffers) may animate at the wrong frequency, causing some
  stuttering and skipped frames.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.3-1ubuntu6
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Thu Sep 14 11:40:31 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[8086:041a] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v3 Processor Integrated Graphics Controller 
[17aa:30a1]
  InstallationDate: Installed on 2017-05-03 (133 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  MachineType: LENOVO 30AJS05700
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed 
root=UUID=1446940d-616b-4f78-926f-05ddb67580b8 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FBKTB6AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50519 PRO
  dmi.chassis.type: 7
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 30AJS05700
  dmi.product.version: ThinkStation P300
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jul 31 16:27:11 2017
  xserver.configfile: default
  xserver.errors:
   modeset(G0): eglGetDisplay() failed
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

** Tags added: wayland

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  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: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731273] Re: Super + L (Ubuntu 17.10) - Lock screen does not work

** Tags added: wayland

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

Title:
  Super + L (Ubuntu 17.10) - Lock screen does not work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 installed. Upgraded from 17.04.
  GDM as login manager active. 
  Gnome Session on wayland in use.
  Tried to press Super + L but without any affect. All other shortcuts and keys 
are working.

  Gnome Session on X11 without any issues. Super + L is working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  Uname: Linux 4.13.0-041300-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 12:24:38 2017
  InstallationDate: Installed on 2017-04-15 (207 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-20 (20 days ago)

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

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

** Changed in: lubuntu-meta (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  Fix Committed
Status in lubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in ubuntustudio-meta package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Desktop-packages] [Bug 1702082] Re: /usr/bin/nautilus:ERROR:nautilus-bookmark.c:351:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->details->file))

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

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

Title:
  /usr/bin/nautilus:ERROR:nautilus-
  bookmark.c:351:nautilus_bookmark_connect_file: assertion failed:
  (!nautilus_file_is_gone (bookmark->details->file))

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.20.4-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bf809b6dff6ba5f9da90cc650449a4b862e1d00f 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1731376] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: intentando sobreescribir el compartido `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto

2017-11-09 Thread huertacjavier

Public bug reported:

bug when I tried to install wine

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Thu Nov  9 19:51:12 2017
ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
InstallationDate: Installed on 2017-10-31 (9 days ago)
InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
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
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: intentando sobreescribir el compartido
  `/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias
  del paquetes libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  bug when I tried to install wine

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Thu Nov  9 19:51:12 2017
  ErrorMessage: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  InstallationDate: Installed on 2017-10-31 (9 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  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
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/lib/udev/hwdb.d/20-sane.hwdb', que es distinto de otras instancias del 
paquetes libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1581151] Re: Time to drop 69-language-selector-zh-??.conf?

I have uploaded related changes to
/etc/fonts/conf.avail/30-cjk-aliases.conf:

http://launchpadlibrarian.net/345170169/language-
selector_0.182_0.183.diff.gz

Would appreciate if someone for respective language, who understands the
meaning of those aliases, could review the changes.

** Changed in: language-selector (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  Time to drop 69-language-selector-zh-??.conf?

Status in language-selector package in Ubuntu:
  Fix Committed

Bug description:
  With the transition to Noto Sans CJK as default font for Chinese, we
  have established a fontconfig configuration for rendering Chinese
  under an *English* locale via these three files:

  /etc/fonts/conf.avail/64-language-selector-prefer.conf

  /etc/fonts/conf.avail/65-fonts-arphic-ukai.conf

  /etc/fonts/conf.avail/65-fonts-arphic-uming.conf

  (I questioned the need for the two latter in bug #1560548, but I think
  we'd better consider the need for the 69-language-selector-zh-??.conf
  files first.)

  So, if I have understood the feedback from Chinese users correctly,
  both Chinese and Japanese are properly rendered under an English
  locale in Ubuntu 16.04.

  It's my belief that what's happening if you switch to a Chinese locale
  is that one of the 69-language-selector-zh-??.conf files is enabled,
  and Japanese is no longer properly rendered while there is no
  improvement in rendering Chinese.

  If I'm right, I think we should drop 69-language-selector-zh-??.conf.
  Did I miss anything?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581151/+subscriptions

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

I have uploaded related changes to
/etc/fonts/conf.avail/30-cjk-aliases.conf:

http://launchpadlibrarian.net/345170169/language-
selector_0.182_0.183.diff.gz

Would appreciate if someone for respective language, who understands the
meaning of those aliases, could review the changes.

** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  Fix Committed
Status in lubuntu-meta package in Ubuntu:
  Fix Committed
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in ubuntustudio-meta package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

2017-11-09 Thread John

Thorsten - you can workaround a few different ways. For me, it's a pain
because I move from a proxy-only to a non-proxy environment as I move my
workstation around.

Workarounds:
1. set the http_proxy, https_proxy, ftp_proxy environment variables in root's 
environment, reboot.

2. prefix any apt command with the variables,ie

sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt update
sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt upgrade
sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt install 
[package]

Hope that helps. Proxy issues have been appearing on and off in Ubuntu
for a long time (9.x). They usually get sorted out eventually.

etc

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

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

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-budgie-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: lubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntukylin-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntustudio-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => In Progress

** Changed in: lubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: ubuntu-budgie-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-budgie-meta (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: ubuntukylin-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntukylin-meta (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: ubuntustudio-meta (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntustudio-meta (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress
Status in lubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in ubuntustudio-meta package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Desktop-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

** Branch linked: lp:~gunnarhj/ubuntu-seeds/lubuntu.bionic_drop-nanum

** Branch linked: lp:~gunnarhj/ubuntu-seeds/platform.bionic_drop-takao-
nanum

** Branch linked: lp:~gunnarhj/ubuntu-seeds/ubuntu.bionic_drop-takao-
nanum

** Branch linked: lp:~gunnarhj/ubuntu-seeds/ubuntu-budgie.bionic_drop-
takao-nanum

** Branch linked: lp:~gunnarhj/ubuntu-seeds/ubuntukylin.bionic_drop-
takao-nanum

** Branch linked: lp:~gunnarhj/ubuntu-seeds/ubuntustudio.bionic_drop-
takao

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress
Status in lubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntu-budgie-meta package in Ubuntu:
  In Progress
Status in ubuntu-meta package in Ubuntu:
  In Progress
Status in ubuntukylin-meta package in Ubuntu:
  In Progress
Status in ubuntustudio-meta package in Ubuntu:
  In Progress

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+subscriptions

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

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2017-11-09 Thread WinEunuchs2Unix

Confirm this occurs with Dell AW17R3. Skylake i7 6700HQ with HM170
chipset and HD530 internal graphics controlling built in display and
external Thunderbolt 3 to display port to HDMI adapter sound works good.

Discrete GPU is GTX 970M and on built-in HDMI port is hard wired to it
(Optimus not supported). Here there is no sound and pavucontrol hangs
can't even display configuration properly. Additional problem of about
40 pixels underscanning with both Nouveau and nVidia drivers.

Windows 10 works perfectly in all departments except when resuming from
an overnight suspend nVidia HDMI might have to be hot-plugged to fix
screeching sound.

Added NVMe Samsung Pro 960 M.2 SSD card meaning in Linux kernel hot
plugging had to be deactivated due to known bug so solutions recommended
above in that area will not work.

Many thanks to previous poster for possible solution which I will
hopefully have time to try in a couple weeks.

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

Title:
HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
Confirmed
Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
Hi,

not sure if this is an alsa or nvidia/nouveau bug.
HDMI audio output doesn't appear in sound settings output panel.
Audio works well on internal speakers, but it seems there is no way to make
it output to hdmi...

The laptop has optimus NVIDIA+Intel.
The behaviour is the same with nouveau or nvidia proprietary driver.

Please let me know if further testing is required

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam2295 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission
denied
Date: Sun Oct 5 17:05:35 2014
InstallationDate: Installed on 2014-04-21 (166 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1694329] Re: oversized "characters" when Noto Color Emoji font is used on a page

2017-11-09 Thread Václav Haisman

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1694329/+attachment/4885854/+files/JournalErrors.txt

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-lowlatency N/A
   linux-backports-modules-4.10.0-21-lowlatency  N/A
   linux-firmware1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790XTA-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-790XTA-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1694329] Re: oversized "characters" when Noto Color Emoji font is used on a page

** Changed in: firefox
   Status: Unknown => New

** Changed in: firefox
   Importance: Unknown => Medium

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in Mozilla Firefox:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-lowlatency N/A
   linux-backports-modules-4.10.0-21-lowlatency  N/A
   linux-firmware1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790XTA-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-790XTA-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

** Changed in: gnome-desktop
   Status: Unknown => Confirmed

** Changed in: gnome-desktop
   Importance: Unknown => Medium

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Confirmed
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1731354] [NEW] No response to scroll events on left navigation panel

2017-11-09 Thread jeremy-list

Public bug reported:

To replicate: (only confirmed with touchpad: I don't currently have a mouse to 
test it)
Position the mouse cursor over the navigation panel on the left hand side of a 
nautilus window, and attempt to scroll up or down.

Expected results:
The left panel should scroll up or down as appropriate for the scroll event.

Actual results:
None.

ProblemType: Bug
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 x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 10 12:14:21 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-15 (86 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: nautilus
UpgradeStatus: Upgraded to artful on 2017-09-14 (56 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  No response to scroll events on left navigation panel

Status in nautilus package in Ubuntu:
  New

Bug description:
  To replicate: (only confirmed with touchpad: I don't currently have a mouse 
to test it)
  Position the mouse cursor over the navigation panel on the left hand side of 
a nautilus window, and attempt to scroll up or down.

  Expected results:
  The left panel should scroll up or down as appropriate for the scroll event.

  Actual results:
  None.

  ProblemType: Bug
  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 x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 10 12:14:21 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-08-15 (86 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-09-14 (56 days ago)

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

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

[Desktop-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack

2017-11-09 Thread Brian Murray

The regression potential here is insufficient, additionally the version
of libclc in xenial would be greater than the one in artful so it not
blowing up there doesn't seem relevant.

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Incomplete
Status in libdrm source package in Xenial:
  New
Status in llvm-toolchain-5.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  artful hasn't blown up

  [Other information]

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

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

[Desktop-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack

2017-11-09 Thread Brian Murray

After cleaning up the bug description please also upload newer versions
of libclc to Zesty and Artful.

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

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Incomplete
Status in libdrm source package in Xenial:
  New
Status in llvm-toolchain-5.0 source package in Xenial:
  New
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  artful hasn't blown up

  [Other information]

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

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

[Desktop-packages] [Bug 1567427] Re: gnome-shell crashes when touchscreen is touched

2017-11-09 Thread Fox

Anytime I have a video playing, or my laptop has been on a while, if I
touch the screen all my programs close and I get logged out.

Trying to turn off the screen via XINPUT does not work, disabling the
touchscreen does NOTHING now that ubuntu runs on wayland.

Running Ubuntu 17 right now

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

Title:
  gnome-shell crashes when touchscreen is touched

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04 with gnome-shell, the gnome-shell would crash every
  time I touch the touchscreen of my laptop (ASUS-S400CA). Sometimes the
  session would just restart, but when I touch again the whole session
  would just crash and drive me back to gdm.

  There are related log line in journald says:

  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (II) XKB: 
generating xkmfile /tmp/server-3D32AD876081C702D9B5501C336C5CB154F5C8D2.xkm
  4月 07 20:38:14 ubuntu-s400ca kernel: gnome-shell[15211]: segfault at c ip 
7f2ad1ae9f87 sp 7ffc96f9e6b0 error 4 in 
libcaribou.so.0.0.0[7f2ad1ae+1e000]
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: syntax 
error: line 1 of stdin
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: Errors 
encountered in stdin; not compiled.
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) Error 
compiling keymap (server-3D32AD876081C702D9B5501C336C5CB154F5C8D2)
  4月 07 20:38:14 ubuntu-s400ca /usr/lib/gdm3/gdm-x-session[14967]: (EE) XKB: 
Couldn't compile keymap
  4月 07 20:38:15 ubuntu-s400ca polkitd(authority=local)[874]: Unregistered 
Authentication Agent for unix-session:6 (system bus name :1.360, object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale zh_CN.UTF-8) 
(disconnected from bus)
  4月 07 20:38:15 ubuntu-s400ca gnome-session[15129]: 
gnome-session-binary[15129]: WARNING: Application 'gnome-shell.desktop' killed 
by signal 11

  You may find the full log in the attached files generated by ubuntu-
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Thu Apr  7 20:41:10 2016
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1694329] Re: oversized "characters" when Noto Color Emoji font is used on a page

2017-11-09 Thread Laurent Bigonville

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

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1416018
   Importance: Unknown
   Status: Unknown

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

Title:
  oversized "characters" when Noto Color Emoji font is used on a page

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  I am seeing oversized emoji characters. See a duck in attached
  screenshot. This duck is from Noto Color Emoji font. In previous
  releases of Firefox it worked fine. It also works fine on Firefox for
  Windows. You can test it yourself if you have the font by visiting
  this URL:
  http://chat.stackexchange.com/transcript/message/37722474#37722474

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-lowlatency 4.10.0-21.23
  ProcVersionSignature: Ubuntu 4.10.0-21.23-lowlatency 4.10.11
  Uname: Linux 4.10.0-21-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 29 22:07:30 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=cf2fd7df-da6e-4e8b-876e-c91fa967ae41
  InstallationDate: Installed on 2011-11-13 (2024 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-790XTA-UD4
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-lowlatency 
root=UUID=503b3cdd-770e-4354-bf3d-c917a2ebe292 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw elevator=cfq nomdmonddf nomdmonisw nomdmonddf nomdmonisw
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-21-lowlatency N/A
   linux-backports-modules-4.10.0-21-lowlatency  N/A
   linux-firmware1.164.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (43 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-790XTA-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd12/03/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XTA-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XTA-UD4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-790XTA-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1730672] Re: Proxy settings not applied system-wide, are not used by Software Update or apt

2017-11-09 Thread Thorsten Greeb

Importance: Low? Are you sure?

In environments where Internet access is only possible via proxy

- Ubuntu Software: Not working
- Software Updater: Not working
- Automatic install of security updates: Not working
- Install Languages (Language Support): Not working
- ...

I find this quite critical!

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

Title:
  Proxy settings not applied system-wide, are not used by Software
  Update or apt

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

Bug description:
  The Network Proxy settings available under Settings/Network are not applied 
system wide. Unlike 16.x, there is no "apply system wide" setting. Setting a 
proxy here:
  - does not modify /etc/environment
  - does not set root's http_proxy, https_proxy, ftp_proxy environment 
variables 

  This means that apt and Software Updates do not receive the proxy
  settings, and package checks/updates/installs fail.

  
  workaround:

  sudo http_proxy='http://[username]:[password]@[webproxy]:[port]' apt
  update

  etc

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

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

[Desktop-packages] [Bug 1729377] Re: AMD r7 250 wrong detection

2017-11-09 Thread Timo Aaltonen

[40.915] (==) Matched radeon as autoconfigured driver 0
[40.915] (==) Matched ati as autoconfigured driver 1
[40.915] (==) Matched ati as autoconfigured driver 2
[40.915] (==) Matched modesetting as autoconfigured driver 3
[40.915] (==) Matched fbdev as autoconfigured driver 4
[40.915] (==) Matched vesa as autoconfigured driver 5

as you can see it doesn't even list ati as the first, it'll always use
radeon if it's available. So with xserver autoconfig radeon is loaded
first. No problem there.

[40.998] (--) RADEON(0): Chipset: "VERDE" (ChipID = 0x682b)
OpenGL renderer string: AMD CAPE VERDE (DRM 2.50.0 / 4.13.0-16-generic, LLVM 
5.0.0)

these look normal and should have proper hardware acceleration with
this.

The card is probably actually R7 250X which uses a Cape Verde GPU:
https://en.wikipedia.org/wiki/AMD_Radeon_Rx_200_series

closing as there's no bug

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

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

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

Title:
  AMD r7 250 wrong detection

Status in mesa package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  My AMD R7 250 GPU is being wrongly detected in Ubuntu as a Radeon HD
  8830M. This results in the wrong detection of drivers. The result is a
  wrongly installed driver and very poor performance. This bug has been
  affecting me since Ubuntu 16.10, and still affects me in Ubuntu 17.10.

  brad@brad-ubuntu:~$ lspci | grep 'VGA compatible controller'
  02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Venus LE [Radeon HD 8830M] (rev 87)
  brad@brad-ubuntu:~$ lsmod | grep -i 'radeon'
  radeon   1470464  9
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper
  brad@brad-ubuntu:~$ lsmod | grep -i 'amdgpu'
  amdgpu   2007040  0
  i2c_algo_bit   16384  2 amdgpu,radeon
  ttm94208  2 amdgpu,radeon
  drm_kms_helper167936  2 amdgpu,radeon
  drm   356352  9 amdgpu,radeon,ttm,drm_kms_helper

  Ubuntu installs by autodetection: xserver-xorg-video-ati. The proper
  driver is, xserver-xorg-video-radeon.

  However even after proper installation of the new driver. Ubuntu still
  reports that I am using a mobile graphics card, instead of a desktop
  graphics card.

  Ubuntu reports: llvmpipe (LLVM 5.0, 128 bits) with the radeon driver. And 
CAPE VERDE with the ati driver. Its a "OLAND" or "southern island" card.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2017-10-21 23:44:08,256 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroRelease: Ubuntu 17.10
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-23 (71 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: MSI MS-7721
  Package: xorg 1:7.7+19ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d9298166-bfea-422f-990f-71ef38407fa5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful ubuntu
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-22 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/10/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A68HM-E33 V2 (MS-7721)
  dmi.board.vendor: MSI
  dmi.board.version: 9.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 9.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.4:bd08/10/2016:svnMSI:pnMS-7721:pvr9.0:rvnMSI:rnA68HM-E33V2(MS-7721):rvr9.0:cvnMSI:ct3:cvr9.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7721
  dmi.product.version: 9.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing

[Desktop-packages] [Bug 1731314] Re: In Gnome Shell Most of Ibus input method are not available to the user

Once one installs an input method using `apt install`, it is possible to:
* activate it manually using `ibus engine `. (use `ibus list-engine` for 
the list of );
* configure it using `ibus-setup`.

The method that you c

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

Title:
  In Gnome Shell Most of Ibus input method are not available to the user

Status in ibus package in Ubuntu:
  New

Bug description:
  Most of Ibus input methods are not available in Gnome Shell (Ubuntu
  17.10) X11 and Wayland.

  For instance, there is no way to use chewing, even if the ibus-chewing 
package is installed.
  The same for ibus-zhuyin.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 19:20:28 2017
  InstallationDate: Installed on 2017-10-22 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731314] Re: In Gnome Shell Most of Ibus input method are not available to the user

The methods that you configure or activate manually are not reflected in
the top bar menu, nor in the Region & Language parameter panel.

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

Title:
  In Gnome Shell Most of Ibus input method are not available to the user

Status in ibus package in Ubuntu:
  New

Bug description:
  Most of Ibus input methods are not available in Gnome Shell (Ubuntu
  17.10) X11 and Wayland.

  For instance, there is no way to use chewing, even if the ibus-chewing 
package is installed.
  The same for ibus-zhuyin.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 19:20:28 2017
  InstallationDate: Installed on 2017-10-22 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731341] [NEW] Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"

2017-11-09 Thread Aaron Whitehouse

Public bug reported:

I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since 
upgrading to 17.10, I receive an error whenever I try to import photos:
Unable to fetch previews from the camera: Unspecified error (-1)

lsusb gives:

Bus 001 Device 010: ID 04cb:02c8 Fuji Photo Film Co., Ltd

dmesg gives:

[  585.129167] usb 1-2: new high-speed USB device number 10 using xhci_hcd
[  585.269979] usb 1-2: New USB device found, idVendor=04cb, idProduct=02c8
[  585.269980] usb 1-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
[  585.269981] usb 1-2: Product: USB PTP Camera
[  585.269981] usb 1-2: SerialNumber: 59353130303416092266F93011BFE6

This looks like the same issue reported in Ask Ubuntu (with no answer) here:
https://askubuntu.com/questions/972613/usb-ptp-camera-no-longer-working-after-upgrade-to-17-10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: shotwell 0.26.3-1ubuntu1
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.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 21:36:30 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-03 (494 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: shotwell
UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the
  camera: Unspecified error (-1)"

Status in shotwell package in Ubuntu:
  New

Bug description:
  I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since 
upgrading to 17.10, I receive an error whenever I try to import photos:
  Unable to fetch previews from the camera: Unspecified error (-1)

  lsusb gives:

  Bus 001 Device 010: ID 04cb:02c8 Fuji Photo Film Co., Ltd

  dmesg gives:

  [  585.129167] usb 1-2: new high-speed USB device number 10 using xhci_hcd
  [  585.269979] usb 1-2: New USB device found, idVendor=04cb, 
idProduct=02c8
  [  585.269980] usb 1-2: New USB device strings: Mfr=0, Product=2, 
SerialNumber=3
  [  585.269981] usb 1-2: Product: USB PTP Camera
  [  585.269981] usb 1-2: SerialNumber: 59353130303416092266F93011BFE6

  This looks like the same issue reported in Ask Ubuntu (with no answer) here:
  
https://askubuntu.com/questions/972613/usb-ptp-camera-no-longer-working-after-upgrade-to-17-10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  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.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 21:36:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-03 (494 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago)

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

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

[Desktop-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses

2017-11-09 Thread Hashem Nasarat

Here's how you fix the issue:

This is a bug that's fixed in upstream NetworkManager. That said, the
various GUI tools which write the NetworkManager config files haven't
been updated to ensure that DNS leaks are prevented when using vpn
connections.

To prevent system dns from appearing and being used in /etc/resolv.conf
when using a VPN, edit your  vpn configuration (i.e. the file in
/etc/NetworkManager/system-connections/) so it's something
like this:

[ipv4]
dns=;
ignore-auto-dns=true
method=auto
dns-priority=-1

the negative dns-priority means only this dns server will be used.
Then reload the config file:
sudo nmcli c reload 

and toggle the vpn.

/etc/resolv.conf should now only include the one dns ip address defined
in the config file.

References:
https://developer.gnome.org/NetworkManager/stable/settings-ipv4.html
https://bugzilla.gnome.org/show_bug.cgi?id=758772

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

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

Title:
  network manager openvpn dns push data not updating system DNS
  addresses

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

Bug description:
  [Triage Notes]

  Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions.
  Please see wall of text on comment 50 for a long excuse.

  [Original Description]

  When IPv4 Method is set to Automatic VPN, DNS address recieved from
  OpenVPN server do not update resolv.conf.

  This can be achieved when using a standard openvpn config file by
  adding the lines:

  script-security 2
  up /etc/openvpn/update-resolv-conf
  down /etc/openvpn/update-resolv-conf

  In Network-manager there seems to be no option to run connection
  specific scripts and the DNS data from the server is ignored.

  Ubuntu 13.04
  Network-manager 0.9.8.0-0ubuntu6

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

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

[Desktop-packages] [Bug 1706452] Re: Gtk error when I try to open and isntall a new font

2017-11-09 Thread John Bales

jbales@bales:~/myfonts$ sudo gnome-font-viewer Snell-Roundhand-Script.ttf
[sudo] password for jbales: 
No protocol specified
Unable to init server: Could not connect: Connection refused

(gnome-font-viewer:19642): Gtk-WARNING **: cannot open display: :0

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

Title:
  Gtk error when I try to open and isntall a new font

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  When I did doble-click on top of a font the font viewer is not open.

  When I run from the console the command `gnome-font-viewer in-mono.otf` it 
shows this error:
  ⇒  gnome-font-viewer in-mono.otf 

  (gnome-font-viewer:3639): GLib-GObject-WARNING **: invalid (NULL)
  pointer instance

  (gnome-font-viewer:3639): GLib-GObject-CRITICAL **:
  g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)'
  failed

  (gnome-font-viewer:3639): Gtk-CRITICAL **: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  [1]3639 segmentation fault (core dumped)  gnome-font-viewer in-mono.otf

  If I try with sudo throws this other error:
  ⇒  sudo gnome-font-viewer in-mono.otf
  No protocol specified
  Unable to init server: Could not connect: Connection refused

  (gnome-font-viewer:3609): Gtk-WARNING **: cannot open display: :0

  I tried with different kind of fonts (ttf, otf ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-font-viewer 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 25 23:19:53 2017
  InstallationDate: Installed on 2017-07-25 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1706452] Re: Gtk error when I try to open and isntall a new font

2017-11-09 Thread worksk historya general Antonio Mainardi

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

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

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

Title:
  Gtk error when I try to open and isntall a new font

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  When I did doble-click on top of a font the font viewer is not open.

  When I run from the console the command `gnome-font-viewer in-mono.otf` it 
shows this error:
  ⇒  gnome-font-viewer in-mono.otf 

  (gnome-font-viewer:3639): GLib-GObject-WARNING **: invalid (NULL)
  pointer instance

  (gnome-font-viewer:3639): GLib-GObject-CRITICAL **:
  g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)'
  failed

  (gnome-font-viewer:3639): Gtk-CRITICAL **: gtk_widget_get_scale_factor: 
assertion 'GTK_IS_WIDGET (widget)' failed
  [1]3639 segmentation fault (core dumped)  gnome-font-viewer in-mono.otf

  If I try with sudo throws this other error:
  ⇒  sudo gnome-font-viewer in-mono.otf
  No protocol specified
  Unable to init server: Could not connect: Connection refused

  (gnome-font-viewer:3609): Gtk-WARNING **: cannot open display: :0

  I tried with different kind of fonts (ttf, otf ...)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-font-viewer 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 25 23:19:53 2017
  InstallationDate: Installed on 2017-07-25 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1077335] ☑omg! wow, that's so awesome

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

Dear,

Just found something really  wonderful,  you might be  thinking about
that products  too, check it out
http://www.ozesnaps.com/assessment.php?UE8xMDc3MzM1QGJ1Z3MubGF1bmNocGFkLm5ldA--

Yours faithfully, ntonio Mainardi


From: Bug 1077335 [mailto:1077...@bugs.launchpad.net]
Sent: Thursday, November 09, 2017 2:21 PM
To: antonio.maina...@libero.it
Subject: Good win for us

CinciJ, you are ignoring the  point.   The hypothetical was an  "all
other things being equal, the  gun is a lot more  dangerous than the
knife" assertion.

Following your logic, if one guy was armed  with a  mosquito but it was
going  to give me malaria, and the other guy had a sherman tank  but the
turret  was stuck pointing in  the wrong direction, you would conclude
that a mosquito is more dangerous  than a  sherman tank.


Sent from Mail for Windows 10

** Attachment added: "C66C8CB997D7A24C.jpg"
   
https://bugs.launchpad.net/bugs/1077335/+attachment/5006652/+files/C66C8CB997D7A24C.jpg

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

Title:
  fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed
  to build

Status in fglrx-installer-updates package in Ubuntu:
  New

Bug description:
  ...Installing ATI post-release drivers

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: fglrx-updates 2:8.982-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
  Uname: Linux 3.2.0-33-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  DKMSKernelVersion: 3.2.0-33-generic
  Date: Sat Nov 10 12:50:49 2012
  MarkForUpload: True
  PackageVersion: 2:8.982-0ubuntu0.1
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1077335/+subscriptions

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

2017-11-09 Thread Kenneth Loafman

This will work when duplicity is run from DejaDup, not when it is run
from the console or from cron.

The system wide solution above will work for all situations.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2017-11-09 Thread Kenneth Loafman

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

** This bug has been marked a duplicate of bug 1720159
   Cannot allocate memory with large manifest file since 0.7.03

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

Title:
  MemoryError while verifying backup

Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

2017-11-09 Thread Timo Aaltonen

After the package has been reviewed and accepted to enter -proposed
it'll usually take 7 days before an update is allowed to enter -updates,
assuming it was verified to fix the issue during that period.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

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

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1724933] Re: I can't adjust display brightness

2017-11-09 Thread nata

Thanks Neil! This method works fine. I hope someday somebody will fix
it. In any case, I'll leave it here:

Step 1: Fire a terminal (Obviously)

Step 2: Finding the correct module.

Run the following command:
$ ls /sys/class/backlight/
This should list down two modules:
acpi_video0 and intel_backlight
We need to know which module is exactly controlling the brightness.

Run the below command: (You need to be root)

# tee /sys/class/backlight/acpi_video0/brightness <<< 5
If nothing happens, then intel_backlight is the one handling the brightness 
settings.

Step 3: Modifying the bootloader.

Next step is modifying the file /etc/default/grub.

(Why modify /etc/default/grub and not /boot/grub/grub.cfg)

# nano /etc/default/grub

Insert the below four lines:

GRUB_CMDLINE_LINUX="acpi_backlight=none"
GRUB_CMDLINE_LINUX="acpi_backlight=video"
GRUB_CMDLINE_LINUX="acpi_backlight=vendor"
GRUB_CMDLINE_LINUX="acpi_backlight=native"
After that save and close the file. (Root access needed)

Run (as root):

# update-grub
Step 4: Reboot your system.

Step 5: Verification

After reboot, fire the terminal one last time and

Run the following command:
$ ls /sys/class/backlight/
12
Voila acpi_video0 is gone!
Check the fn+Brightness keys or change the brightness via the applet. 
Brightness controls should work just fine.

Additional info: https://wiki.archlinux.org/index.php/Backlight

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

Title:
  I can't adjust display brightness

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I
  can't adjust display brightness. when I press F2|F3 keys icon
  brightness appears, the controller moves but the brightness doesn't
  change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 22:14:51 2017
  DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:3388]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M 
XT] [1002:6740] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-06-18 (123 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3388
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124471610100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1731314] Re: In Gnome Shell Most of Ibus input method are not available to the user

** Description changed:

  Most of Ibus input methods are not available in Gnome Shell (Ubuntu
  17.10) X11 and Wayland.
  
- For instance, there is no way to use chewing, even if the ibus-chewing
- package is installed.
+ For instance, there is no way to use chewing, even if the ibus-chewing 
package is installed.
+ The same for ibus-zhuyin.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 19:20:28 2017
  InstallationDate: Installed on 2017-10-22 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  In Gnome Shell Most of Ibus input method are not available to the user

Status in ibus package in Ubuntu:
  New

Bug description:
  Most of Ibus input methods are not available in Gnome Shell (Ubuntu
  17.10) X11 and Wayland.

  For instance, there is no way to use chewing, even if the ibus-chewing 
package is installed.
  The same for ibus-zhuyin.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 19:20:28 2017
  InstallationDate: Installed on 2017-10-22 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731053] Re: Update gnome-shell to 3.26.2

** Description changed:

  Impact
  ==
  gnome-shell has released a new stable bugfix release.
  
  https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26
  
  We had already cherry-picked two fixes:
  - fix_reset_initial_focus.patch
  - git_layout-unset-when-headless.patch
  
  We are also adding a fix for LP: #1712798
  
  Test Case
  =
  After installing this update, please restart your computer.
  
  Verify that the default Ubuntu 17.10 desktop still works as well as it
  did before.
  
  Also log in to the "vanilla" GNOME session to verify that it works (you
  may need to install gnome-session and restart first).
  
  Optionally, you can go through some of the fixed bugs to verify the bug
  and the fix.
  
  Regression Potential
  
- GNOME Shell is also used for the login screen so it is really important that
+ GNOME Shell is also used for the login screen so it is really important that 
updates don't break!
  
  This is a much smaller update than 3.26.1 (in terms of commits and lines
  of code changed).
  
  GNOME 3.26 distros will be shipping this update.
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

** Description changed:

  Impact
  ==
  gnome-shell has released a new stable bugfix release.
  
  https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26
  
  We had already cherry-picked two fixes:
  - fix_reset_initial_focus.patch
  - git_layout-unset-when-headless.patch
  
  We are also adding a fix for LP: #1712798
  
  Test Case
  =
  After installing this update, please restart your computer.
  
  Verify that the default Ubuntu 17.10 desktop still works as well as it
  did before.
  
  Also log in to the "vanilla" GNOME session to verify that it works (you
  may need to install gnome-session and restart first).
  
  Optionally, you can go through some of the fixed bugs to verify the bug
  and the fix.
  
  Regression Potential
  
- GNOME Shell is also used for the login screen so it is really important that 
updates don't break!
+ GNOME Shell is also used for the login screen so it is really important that 
updates don't break it.
  
  This is a much smaller update than 3.26.1 (in terms of commits and lines
- of code changed).
+ of code changed) so it seems pretty unlikely to cause that kind of
+ breakage.
  
  GNOME 3.26 distros will be shipping this update.
  
  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

Title:
  Update gnome-shell to 3.26.2

Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in gnome-shell source package in Artful:
  In Progress

Bug description:
  Impact
  ==
  gnome-shell has released a new stable bugfix release.

  https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26
  https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26

  We had already cherry-picked two fixes:
  - fix_reset_initial_focus.patch
  - git_layout-unset-when-headless.patch

  We are also adding a fix for LP: #1712798

  Test Case
  =
  After installing this update, please restart your computer.

  Verify that the default Ubuntu 17.10 desktop still works as well as it
  did before.

  Also log in to the "vanilla" GNOME session to verify that it works
  (you may need to install gnome-session and restart first).

  Optionally, you can go through some of the fixed bugs to verify the
  bug and the fix.

  Regression Potential
  
  GNOME Shell is also used for the login screen so it is really important that 
updates don't break it.

  This is a much smaller update than 3.26.1 (in terms of commits and
  lines of code changed) so it seems pretty unlikely to cause that kind
  of breakage.

  GNOME 3.26 distros will be shipping this update.

  There is a micro-release exception for GNOME:
  https://wiki.ubuntu.com/StableReleaseUpdates#GNOME

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

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

[Desktop-packages] [Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors

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

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

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Unknown
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

2017-11-09 Thread themroc

I have exactly the same Problem like User Orange Shiang-Yuan Kao
(orange-kao) wrote on 2017-03-22 in Comment #10 in duplicate Bug 1671606
since upgrading to

Kubuntu 17.10

https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1671606/comments/10

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Desktop-packages] [Bug 1731318] [NEW] NVIDIA systems will not suspend with lid close and no external monitors

2017-11-09 Thread Jeremy Soller

Public bug reported:

With the NVIDIA driver, nvidia-384, the system will not sleep when the
lid is closed due to gnome_rr_output_is_builtin_display incorrectly
returning false. I have linked to an upstream bug, which also has
patches fixing the issue.

** Affects: gnome-desktop
 Importance: Unknown
 Status: Unknown

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

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

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

** Description changed:

  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
- returning false
+ returning false. I have linked to an upstream bug, which also has
+ potential fixes for the issue.

** Summary changed:

- NVIDIA systems will not suspend with lid close and no external montiors
+ NVIDIA systems will not suspend with lid close and no external monitors

** Description changed:

  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
- potential fixes for the issue.
+ patches fixing the issue.

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

Title:
  NVIDIA systems will not suspend with lid close and no external
  monitors

Status in gnome-desktop:
  Unknown
Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  With the NVIDIA driver, nvidia-384, the system will not sleep when the
  lid is closed due to gnome_rr_output_is_builtin_display incorrectly
  returning false. I have linked to an upstream bug, which also has
  patches fixing the issue.

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

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

[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

2017-11-09 Thread Pierre-Loup Griffais

When should we expect the baseline mesa-vulkan-drivers to get that patch
for all users of the regular repository? Just so our support agents know
what to tell affected Ubuntu users.

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  In Progress
Status in mesa source package in Xenial:
  New
Status in mesa source package in Artful:
  New

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

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

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

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

[Desktop-packages] [Bug 1718869] Re: Migrate to hunspell-en-us in libreoffice-dictionaries

Nothing to do with hunspell-en-us (Ubuntu), then.

** Changed in: hunspell-en-us (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Migrate to hunspell-en-us in libreoffice-dictionaries

Status in hunspell-en-us package in Ubuntu:
  Won't Fix
Status in libreoffice-dictionaries package in Ubuntu:
  Won't Fix
Status in scowl package in Ubuntu:
  Fix Released
Status in hunspell-en-us package in Debian:
  Fix Released
Status in libreoffice-dictionaries package in Debian:
  Won't Fix
Status in scowl package in Debian:
  Unknown

Bug description:
  libreoffice-dictionaries upstream ships hunspell-en-us, which is
  properly maintained and is newer than the one currently in Debian and
  Ubuntu (20070829-6ubuntu3). Please consider migrating to the one in
  libreoffice-dictionaries. The other English variants (British,
  Australian and others) are already provided by libreoffice-
  dictionaries and are more up-to-date than the US variant.

  Debian bugs:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874519
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795159

  Inside the source of libreoffice-dictionaries in Debian, I can find en_US.aff 
and en_US.dic but there is not a built package for them.
  
https://sources.debian.net/src/libreoffice-dictionaries/1:5.2.5-1/dictionaries/en/

  See this README from the Libreoffice/dictionaries git,
  https://cgit.freedesktop.org/libreoffice/dictionaries/tree/en/README_en_US.txt

  It seems that this is now dead,
  https://sourceforge.net/projects/hunspell/files/Spelling%20dictionaries/en_US/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hunspell-en-us 20070829-6ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 09:43:32 2017
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  PackageArchitecture: all
  SourcePackage: hunspell-en-us
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hunspell-en-us/+bug/1718869/+subscriptions

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

[Desktop-packages] [Bug 1731273] Re: Super + L (Ubuntu 17.10) - Lock screen does not work

2017-11-09 Thread Paul White

** Package changed: evince (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Super + L (Ubuntu 17.10) - Lock screen does not work

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 installed. Upgraded from 17.04.
  GDM as login manager active. 
  Gnome Session on wayland in use.
  Tried to press Super + L but without any affect. All other shortcuts and keys 
are working.

  Gnome Session on X11 without any issues. Super + L is working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  Uname: Linux 4.13.0-041300-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 12:24:38 2017
  InstallationDate: Installed on 2017-04-15 (207 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-20 (20 days ago)

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

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

[Desktop-packages] [Bug 1731314] [NEW] In Gnome Shell Most of Ibus input method are not available to the user

Public bug reported:

Most of Ibus input methods are not available in Gnome Shell (Ubuntu
17.10) X11 and Wayland.

For instance, there is no way to use chewing, even if the ibus-chewing
package is installed.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ibus 1.5.14-2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 19:20:28 2017
InstallationDate: Installed on 2017-10-22 (18 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  In Gnome Shell Most of Ibus input method are not available to the user

Status in ibus package in Ubuntu:
  New

Bug description:
  Most of Ibus input methods are not available in Gnome Shell (Ubuntu
  17.10) X11 and Wayland.

  For instance, there is no way to use chewing, even if the ibus-chewing
  package is installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 19:20:28 2017
  InstallationDate: Installed on 2017-10-22 (18 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729910] Re: lp ignores ~/.cups/lpoptions in 17.10

2017-11-09 Thread Brian Murray

Hello Gabriel, or anyone else affected,

Accepted cups into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/cups/2.2.4-7ubuntu3 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cups (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  lp ignores ~/.cups/lpoptions in 17.10

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * During some refactoring done to cupsGetNamedDest function used in
  many different parts of the code a regression has been introduced
  causing the per-user default printer setting (in ~/.cups/lpoptions) to
  be ignored.

  This bug has been introduced in Artful due to the refactoring. Earlier
  releases are fine, similarly this bug is fixed upstream for Bionic.

  [Test Case]

   1. Make sure at least 2 printers are set up in cups.
   2. Set one of them as global default.
   3. Create a user default setting (~/.cups/lpoptions) with the other printer 
set as default:
  Default other_printer
   4. Run lpstat -d.

  Expected result:
  User default printer is displayed.

  Actual result:
  Global default printer is displayed.

  [Regression Potential]

   * The regression potential is minial, as this is a very simple bugfix and is 
already included in the latest (2.2.5+) releases of cups (including Bionic).
   * The only setups affected may be those depending (possibly unintentionally) 
on the incorrect behavior. Their users may observe default printer change.

  [Other Info]

   * Original bug description

  LP ignores the settings defined in ~/cups/lpoptions in artful

  Steps to reproduce:

  1) Define a default print in lpoptions that differs from one in 
/etc/cups/printers.conf
  2) Execute lpstat -d
  3) Above will output default defined in prints.conf instead of 
~/cups/lpoptions

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

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

[Desktop-packages] [Bug 1731310] [NEW] nautilus doesn't align icons properly when name is long

2017-11-09 Thread fcole90

Public bug reported:

Nautilus icons with long text are not aligned properly to the grid

ProblemType: Bug
DistroRelease: Ubuntu 18.04
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 x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 19:28:36 2017
InstallationDate: Installed on 2017-08-21 (80 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic regression-proposed

** Attachment added: "Screenshot from 2017-11-09 19-28-19.png"
   
https://bugs.launchpad.net/bugs/1731310/+attachment/5006621/+files/Screenshot%20from%202017-11-09%2019-28-19.png

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

Title:
  nautilus doesn't align icons properly when name is long

Status in nautilus package in Ubuntu:
  New

Bug description:
  Nautilus icons with long text are not aligned properly to the grid

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  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 x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 19:28:36 2017
  InstallationDate: Installed on 2017-08-21 (80 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 735496] ✈I've found something interesting

2017-11-09 Thread Robert Cotterman

Greetings!

Look at that cool products! I've just found it on the  internet and it
reminded me of you. Please take a  peek
http://www.ngocacr.com/constraint.php?UE83MzU0OTZAYnVncy5sYXVuY2hwYWQubmV0

Sent from a prehistoric stone tablet, Kayla Nolan


From: Bug 735496 [mailto:735...@bugs.launchpad.net]
Sent: Thursday, November 09, 2017 11:26 AM
To: robertc1...@yahoo.com
Subject: An eggsellent idea

So many Americans talking about how much they love the healthcare they
get outside  of the country.

It's such a shame that many Americans are fighting this change.  I have
lived in four different countries,  and America is the worst for
healthcare. No one should  have their care depend on their ability to
pay.


Sent from Mail for Windows 10

** Attachment added: "BBE715F880D501E4.jpg"
   
https://bugs.launchpad.net/bugs/735496/+attachment/5006618/+files/BBE715F880D501E4.jpg

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

Title:
  package monodoc-webkit-manual 0.3-2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in webkit-sharp package in Ubuntu:
  New

Bug description:
  i don't know anything about this, the machine just asked me to file
  this report

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: monodoc-webkit-manual 0.3-2
  ProcVersionSignature: Ubuntu 2.6.32-29.58-generic-pae 2.6.32.28+drm33.13
  Uname: Linux 2.6.32-29-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Mar 14 20:23:04 2011
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: webkit-sharp
  Title: package monodoc-webkit-manual 0.3-2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webkit-sharp/+bug/735496/+subscriptions

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2017-11-09 Thread Zaszuś

Right, thanks Michael. I missed that part.

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1686623] Re: Gnome terminal window shrink on exit focus with wayland

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

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

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

Title:
  Gnome terminal window shrink on exit focus with wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Gnome terminal window shrink each time the window is unfocused. It
  only happen with Wayland.

  Workaround:
  Maximize the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 27 14:10:17 2017
  EcryptfsInUse: Yes
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to zesty on 2017-03-28 (29 days ago)

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

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

[Desktop-packages] [Bug 1686623] Re: Gnome terminal window shrink on exit focus with wayland

2017-11-09 Thread atomic

Same issue here, whether I'm on a phisical machine or a VM.

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

Title:
  Gnome terminal window shrink on exit focus with wayland

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Gnome terminal window shrink each time the window is unfocused. It
  only happen with Wayland.

  Workaround:
  Maximize the terminal window.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-terminal 3.20.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 27 14:10:17 2017
  EcryptfsInUse: Yes
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to zesty on 2017-03-28 (29 days ago)

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

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

[Desktop-packages] [Bug 1710373] Re: Desktop shortcut missing for Vino GUI in Ubuntu 17.10

I think this is at least in part a duplicate of bug 1730612.

I don't expect for vino itself to gain Wayland support but for vino to
be replaced by gnome-remote-desktop.

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

Title:
  Desktop shortcut missing for Vino GUI in Ubuntu 17.10

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

Bug description:
  There is not any possibility for an end user to configure screen
  sharing via VNC in Ubuntu 17.10. The "Desktop sharing" shortcut cannot
  be found in the GNOME Shell Overview and is also missing in the
  Sharing section of the GNOME Control Center.

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

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

[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time

** Changed in: mutter
   Status: Unknown => Fix Released

** Changed in: mutter
   Importance: Unknown => Medium

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Unknown
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16,

[Desktop-packages] [Bug 1731296] [NEW] GNOME Software app not shown as "Ubuntu Software" in Unity 17.10

Public bug reported:

Test Case
=
Install Ubuntu 17.10.
sudo apt install unity
Restart your computer.
On the login screen, click your name then click the gear button and select 
Unity. Log in.
In the Launcher on the left side of the screen, GNOME Software is shown but not 
Ubuntu Software

Background Info
===
There is an interesting per-desktop override feature. The primary .desktop is 
installed as /usr/share/applications/org.gnome.Software.desktop . That .desktop 
file can be overriden for the ubuntu desktop by shipping 
/usr/share/applications/Ubuntu/org.gnome.Software.desktop or for the gnome 
desktop by shipping /usr/share/applications/gnome/org.gnome.Software.desktop.

Until now, this override was only done for the Ubuntu session (which in
17.10 is no longer Unity).

Proposal #1
===
Have the ubuntu-software packaging install the override .desktop to 
/usr/share/unity/applications/ too.

Proposal #2
===
Have the ubuntu-software packaging install the override .desktop to 
/usr/share/FOO/applications/ where FOO is every desktop session in Ubuntu. Then 
it's up to users and flavors whether they want the Ubuntu or GNOME branding 
based on whether they install the ubuntu-software package.

Proposal #3
===
Rework the packaging to install the Ubuntu Software .desktop to 
/usr/share/applications/
Install the GNOME Software .desktop to /usr/share/gnome/applications/ so that 
GNOME (as in the vanilla GNOME session) alone gets the GNOME branding.

In this case, the ubuntu-software package is not needed any more (after
a transitional period for upgrades).

The question is whether there is any reason why someone not using
vanilla GNOME would want the GNOME branding instead of the Ubuntu
branding.

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

** Description changed:

  Test Case
  =
  Install Ubuntu 17.10.
  sudo apt install unity
  Restart your computer.
  On the login screen, click your name then click the gear button and select 
Unity. Log in.
  In the Launcher on the left side of the screen, GNOME Software is shown but 
not Ubuntu Software
  
  Background Info
  ===
  There is an interesting per-desktop override feature. The primary .desktop is 
installed as /usr/share/applications/org.gnome.Software.desktop . That .desktop 
file can be overriden for the ubuntu desktop by shipping 
/usr/share/applications/Ubuntu/org.gnome.Software.desktop or for the gnome 
desktop by shipping /usr/share/applications/gnome/org.gnome.Software.desktop.
  
  Until now, this override was only done for the Ubuntu session (which in
  17.10 is no longer Unity).
  
  Proposal #1
  ===
  Have the ubuntu-software packaging install the override .desktop to 
/usr/share/unity/applications/ too.
  
  Proposal #2
  ===
  Have the ubuntu-software packaging install the override .desktop to 
/usr/share/FOO/applications/ where FOO is every desktop session in Ubuntu. Then 
it's up to users and flavors whether they want the Ubuntu or GNOME branding 
based on whether they install the ubuntu-software package.
  
  Proposal #3
  ===
  Rework the packaging to install the Ubuntu Software .desktop to 
/usr/share/applications/
  Install the GNOME Software .desktop to /usr/share/gnome/applications/ so that 
GNOME (as in the vanilla GNOME session) alone gets the GNOME branding.
+ 
+ In this case, the ubuntu-software package is not needed any more (after
+ a transitional period for upgrades).
+ 
+ The question is whether there is any reason why someone not using
+ vanilla GNOME would want the GNOME branding instead of the Ubuntu
+ branding.

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

Title:
  GNOME Software app not shown as "Ubuntu Software" in Unity 17.10

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Test Case
  =
  Install Ubuntu 17.10.
  sudo apt install unity
  Restart your computer.
  On the login screen, click your name then click the gear button and select 
Unity. Log in.
  In the Launcher on the left side of the screen, GNOME Software is shown but 
not Ubuntu Software

  Background Info
  ===
  There is an interesting per-desktop override feature. The primary .desktop is 
installed as /usr/share/applications/org.gnome.Software.desktop . That .desktop 
file can be overriden for the ubuntu desktop by shipping 
/usr/share/applications/Ubuntu/org.gnome.Software.desktop or for the gnome 
desktop by shipping /usr/share/applications/gnome/org.gnome.Software.desktop.

  Until now, this override was only done for the Ubuntu session (which
  in 17.10 is no longer Unity).

  Proposal #1
  ===
  Have the ubuntu-software packaging install the override .desktop to 
/usr/share/unity/applications/ too.

  Proposal #2
  ===
  Have the ubuntu-software

[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Fix Released => Invalid

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

Title:
  Gnome web urlbar very slow to show typed input

Status in GTK+:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Artful:
  Invalid
Status in mutter source package in Artful:
  Fix Committed
Status in gtk+3.0 package in Debian:
  Fix Released

Bug description:
  Impact
  ==
  It is very difficult to use the address bar in Epiphany on GNOME on Wayland 
because after a few characters, the address bar field stops redrawing. (This 
apparently was triggered by mutter 3.26?)

  Test Case
  =
  sudo apt install epiphany-browser
  Open the Web app
  Type a URL into the address bar. Type a lng URL.
  You should see all the characters you type into the address bar.

  Regression Potential
  ===
  To fix this issue, an optimization commit applied earlier in 3.26 development 
was reverted. This fix is part of mutter 3.26.2 (LP: #1730097).

  Other Info
  ==
  The first SRU gtk+3.0 3.22.24-0ubuntu2 caused a regression seen in totem and 
so was reverted in both gtk upstream and in the next SRU 3.22.25-0ubuntu0.1

  Instead, this is being fixed in mutter.

  Original Bug Report
  ===
  First two characters typed in urlbar show immediately, other characters take 
up to 30 seconds to appear, or url will appear in full once enter key is 
pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1729104] Re: loading Ubuntu from restart libsane didn't load

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

** Changed in: sane-backends (Ubuntu)
   Status: New => Confirmed

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

Title:
  loading Ubuntu from restart libsane didn't load

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  from reboot
  says can't load libsane

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 30 19:48:01 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8cdJP1/11-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-23 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

2017-11-09 Thread Seth Forshee

This and other errors are related to lacking the cfg80211 module, which
we do not build for s390. However we did not build it in artful either,
and we currently have the same version of network-manager in artful and
bionic, so it's odd that the tests are failing in bionic and not in
artful.

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

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

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

[Desktop-packages] [Bug 1731283] [NEW] network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

2017-11-09 Thread Seth Forshee

Public bug reported:

Testing failed on:
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

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

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

[Desktop-packages] [Bug 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

2017-11-09 Thread Seth Forshee

autopkgtest [13:37:31]: test wpa-dhclient: [---
modprobe: FATAL: Module cfg80211 not found in directory 
/lib/modules/4.14.0-6-generic
ERROR

==
ERROR: setUpClass (__main__.T)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest.J2UcbH/build.Dbb/network-manager-1.8.4/debian/tests/network_test_base.py",
 line 47, in setUpClass
subprocess.check_call(['modprobe', 'cfg80211'])
  File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['modprobe', 'cfg80211']' returned 
non-zero exit status 1.

--
Ran 0 tests in 0.002s

FAILED (errors=1)
autopkgtest [13:37:32]: test wpa-dhclient: ---]

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

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

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

[Desktop-packages] [Bug 1731276] Re: package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already installed and conf

2017-11-09 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1731276

Title:
  package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
  failed to install/upgrade: package chromium-codecs-ffmpeg-extra is
  already installed and configured

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  after new install and adding ubuntu-restricted-extras, on login this
  error was displayed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Thu Nov  9 01:04:21 2017
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:62.0.3202.75-0ubuntu0.16.04.1313
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package chromium-codecs-ffmpeg-extra is already installed and 
configured
  InstallationDate: Installed on 2017-11-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 
failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already 
installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1710931] Re: Ctrl+N shortcut does not work when desktop has focus

2017-11-09 Thread Tuomo Sipola

Affects me, thanks for upstreaming it.

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

Title:
  Ctrl+N shortcut does not work when desktop has focus

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

Bug description:
  When a Nautilus window is open, Ctrl+N opens a new window that shows
  the same folder as the focused Nautilus window.

  However, when the desktop is focused, the shortcut doesn't work -
  instead I see an error that x-nautilus-desktop:// is not supported.

  This functionality was previously reported as working in #307229.

  This is on Ubuntu 17.10 Artful Aardvark (fully patched as of today)
  with GNOME Files 3.24.2.1.

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

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

[Desktop-packages] [Bug 1731276] Re: package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already installed and conf

2017-11-09 Thread dino99

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

** Package changed: chromium-browser (Ubuntu) => dpkg (Ubuntu)

** This bug has been marked a duplicate of bug 545790
   package PACKAGE failed to install/upgrade: error writing to '': Success

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

Title:
  package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
  failed to install/upgrade: package chromium-codecs-ffmpeg-extra is
  already installed and configured

Status in dpkg package in Ubuntu:
  New

Bug description:
  after new install and adding ubuntu-restricted-extras, on login this
  error was displayed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Thu Nov  9 01:04:21 2017
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:62.0.3202.75-0ubuntu0.16.04.1313
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package chromium-codecs-ffmpeg-extra is already installed and 
configured
  InstallationDate: Installed on 2017-11-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 
failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already 
installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1731276] [NEW] package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already installed and co

2017-11-09 Thread Zabasd

Public bug reported:

after new install and adding ubuntu-restricted-extras, on login this
error was displayed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Thu Nov  9 01:04:21 2017
DuplicateSignature:
 package:chromium-codecs-ffmpeg-extra:62.0.3202.75-0ubuntu0.16.04.1313
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
  package chromium-codecs-ffmpeg-extra is already installed and configured
ErrorMessage: package chromium-codecs-ffmpeg-extra is already installed and 
configured
InstallationDate: Installed on 2017-11-09 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: chromium-browser
Title: package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 
failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already 
installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
  failed to install/upgrade: package chromium-codecs-ffmpeg-extra is
  already installed and configured

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  after new install and adding ubuntu-restricted-extras, on login this
  error was displayed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Thu Nov  9 01:04:21 2017
  DuplicateSignature:
   package:chromium-codecs-ffmpeg-extra:62.0.3202.75-0ubuntu0.16.04.1313
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package chromium-codecs-ffmpeg-extra (--configure):
package chromium-codecs-ffmpeg-extra is already installed and configured
  ErrorMessage: package chromium-codecs-ffmpeg-extra is already installed and 
configured
  InstallationDate: Installed on 2017-11-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 62.0.3202.75-0ubuntu0.16.04.1313 
failed to install/upgrade: package chromium-codecs-ffmpeg-extra is already 
installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1694004] Re: [RFE] Add pidgin-otr to Pidgin Addons in GNOME Software

Already fixed in Fedora and probably other distributions.

** Tags added: bionic

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

Title:
  [RFE] Add pidgin-otr to Pidgin Addons in GNOME Software

Status in pidgin package in Ubuntu:
  New
Status in pidgin-otr package in Ubuntu:
  New

Bug description:
  Please consider adding the pidgin-otr plugin to Pidgin Addons in GNOME
  Software. It would make installing this plugin a lot easier for end-
  users. Currently, there is only a SIPE plugin in the list.

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

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

[Desktop-packages] [Bug 1725362] Re: Network icon shows question mark after connected to wifi, not wifi radio strength icon

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

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

Title:
  Network icon shows question mark after connected to wifi, not wifi
  radio strength icon

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  BEHAVIOR
  After I successfully connect to a wifi network, the network icon in the 
system tray (at the top-right) shows a question mark over the radio strength 
symbol (even though the Internet connect is working fine). After about 3-5 
minutes, it disappears and the radio symbol shows the signal strength.

  EXPECTED BEHAVIOR
  For the question mark to not be showing if the connection is successful and 
there is valid Internet access, I suppose.

  BUG DISCOVERED USING
  Ubuntu 17.10
  GNOME 3.26.1
  Xorg 1.19.5
  Nvidia 384.90 proprietary driver
  Linux kernel 4.13.0-16-generic
  Panda USB wireless N wifi adapater, connected to a 5.0ghz linksys wireless 
router (E2500)

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

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

[Desktop-packages] [Bug 1731273] [NEW] Super + L (Ubuntu 17.10) - Lock screen does not work

2017-11-09 Thread Support

Public bug reported:

Ubuntu 17.10 installed. Upgraded from 17.04.
GDM as login manager active. 
Gnome Session on wayland in use.
Tried to press Super + L but without any affect. All other shortcuts and keys 
are working.

Gnome Session on X11 without any issues. Super + L is working.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
Uname: Linux 4.13.0-041300-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  9 12:24:38 2017
InstallationDate: Installed on 2017-04-15 (207 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-10-20 (20 days ago)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Super + L (Ubuntu 17.10) - Lock screen does not work

Status in evince package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10 installed. Upgraded from 17.04.
  GDM as login manager active. 
  Gnome Session on wayland in use.
  Tried to press Super + L but without any affect. All other shortcuts and keys 
are working.

  Gnome Session on X11 without any issues. Super + L is working.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  Uname: Linux 4.13.0-041300-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 12:24:38 2017
  InstallationDate: Installed on 2017-04-15 (207 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-20 (20 days ago)

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

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

[Desktop-packages] [Bug 1491787] Re: Gnome's Activities Overview search is always in English, regardless of the system language

** Tags added: 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/1491787

Title:
  Gnome's Activities Overview search is always in English, regardless of
  the system language

Status in Ubuntu GNOME:
  New
Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hey,

  I'm referring to this issue on AskUbuntu:
  http://askubuntu.com/questions/600656/change-language-of-the-gnome-
  shell-overview

  On my Ubuntu Gnome 15.04 system all entries from the gnome-control-
  center are shown in English in the Gnome-Shell overview (see
  screenshot in the above mentioned link), even though my system
  language is German. The entries in the gnome-control-center itself are
  however in German.

  Is this due to a bug or missing translations?

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

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

[Desktop-packages] [Bug 1710370] Re: Cheese crashes on launch in Ubuntu 17.10 if no camera device is present

** Tags added: bionic

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

Title:
  Cheese crashes on launch in Ubuntu 17.10 if no camera device is
  present

Status in cheese package in Ubuntu:
  New

Bug description:
  Cheese crashes on launch in Ubuntu 17.10 if the computer does not have
  any camera device connected.

  
  (cheese:3620): cheese-CRITICAL **: cheese_camera_device_get_name: assertion 
'CHEESE_IS_CAMERA_DEVICE (device)' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_new_string: assertion
  'string != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value
  != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_schema_key_type_check:
  assertion 'value != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_get_type_string: assertion
  'value != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_set_value: key
  'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of
  type '(null)' was given

  (cheese:3620): GLib-CRITICAL **: g_variant_unref: assertion 'value !=
  NULL' failed

  ** (cheese:3620): CRITICAL **:
  cheese_preferences_dialog_setup_resolutions_for_device: assertion
  'device != NULL' failed

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

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

[Desktop-packages] [Bug 1710373] Re: Desktop shortcut missing for Vino GUI in Ubuntu 17.10

** Tags added: bionic

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

Title:
  Desktop shortcut missing for Vino GUI in Ubuntu 17.10

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

Bug description:
  There is not any possibility for an end user to configure screen
  sharing via VNC in Ubuntu 17.10. The "Desktop sharing" shortcut cannot
  be found in the GNOME Shell Overview and is also missing in the
  Sharing section of the GNOME Control Center.

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

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

[Desktop-packages] [Bug 1719691] Re: Featured subcategory missing on Ubuntu 17.10

** Tags added: 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/1719691

Title:
  Featured subcategory missing on Ubuntu 17.10

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The "Featured" subcategory in GNOME Software is missing in every
  category except Graphics & Photography on my Ubuntu 17.10
  installation. I use non-english (Czech) system, but I believe this
  issue is not related to the system language.

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

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

[Desktop-packages] [Bug 1721359] Re: Simple Scan translations are not synced with upstream

** Tags added: bionic

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

Title:
  Simple Scan translations are not synced with upstream

Status in Ubuntu Translations:
  New
Status in simple-scan package in Ubuntu:
  New

Bug description:
  Czech and probably many other translations are incomplete even though
  they are translated in upstream.

  For example the Czech one:
  Launchpad - 
https://translations.launchpad.net/ubuntu/artful/+source/simple-scan/+pots/simple-scan/cs/+details
 (last update: January 2016; 62 strings untranslated)
  Upstream - https://github.com/GNOME/simple-scan/blob/master/po/cs.po (last 
update: two months ago; fully translated)

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

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

[Desktop-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

** Tags added: 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/1552792

Title:
  gnome software leaves dependencies installed

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Using gnome software to install an application - removal of that
  package leaves behind dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  
  sudo apt-get autoremove 
  [sudo] password for wolf: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  
  After cleaning up and then reinstalling with gnome software, followed by the 
removal

  sudo apt-get autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  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
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1552792/+subscriptions

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

[Desktop-packages] [Bug 1564570] Re: Gnome Software catalog entry missing for Steam except on i386