date:20170823

Debug log requested by upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=786561

** Attachment added: "totemdebug.log.xz"
   
https://bugs.launchpad.net/ubuntu/+source/clutter-gst-3.0/+bug/1698282/+attachment/4937819/+files/totemdebug.log.xz

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

Title:
  Totem uses dramatically higher CPU than any other video player

Status in Totem:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  Totem uses dramatically higher CPU than any other video player.

  Example 1: software playback under Gnome Shell Wayland:

  totem: 120% (but drops to 80% in Unity7)
  mplayer: 40%
  vlc: 40%
  [all are using ffmpeg for decoding]

  Example 2: hardware-accelerated playback under Gnome Shell Xorg:

  totem: 11%
  gst-play-1.0: 3%
  [both are using gstreamer-vaapi for decoding]

  Since the decoding libraries are theoretically the same it sounds like
  totem's performance problems might be in its rendering path.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  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 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

2017-08-23 Thread Robert Ancell

This is how this patch looks like installing a classically confined
snap. Note that the warning is only visible if your screen is tall
enough, otherwise you would have to scroll down to see it.

** Attachment added: "Screenshot from 2017-08-24 16-44-45.png"

https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1690280/+attachment/4937818/+files/Screenshot%20from%202017-08-24%2016-44-45.png

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

Title:
Classic confined snaps don't install

Status in GNOME Software:
Confirmed
Status in gnome-software package in Ubuntu:
In Progress

Bug description:
[Impact]
Apps that use classic confinement show up in search results but don't install.

[Test Case]
1. Open GNOME Software
2. Search for a classic snap, e.g. "atom"
3. Install snap

Expected result:
Either:
a) Snap is installed
b) Snap is not installed and error given
c) Snap is installed but user needs to provide some sort of confirmation
since it is not confined.

Observed result:
Snap is not installed, no error given.

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

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

[Desktop-packages] [Bug 1245745] Re: Loading larger folders with images takes a lot of time

2017-08-23 Thread Bug Watch Updater

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

Title:
  Loading larger folders with images takes a lot of time

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

Bug description:
  I have lots of pictures on my computer and they are taken on digital camera. 
It makes them 1-6 MB each, and it is common to have 300-500 files in one 
folder. But using Nautilus to navigate there is a huge error, until I can do 
anything in that folder, it takes more than a minute. The file list does not 
appear instantly, but files appear as they get a thumbnail.
  See the attached screen recording, in my case it took more than 1 minute and 
10 seconds to be able to do anything in that folder. It is a blocking bug.

  And thumbs do not have a standard size, like a square, they are shows
  upper/lower depending on the portrait/landscape type of picture.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: nautilus 1:3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Oct 29 05:52:43 2013
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'840x550+49+189'"
  InstallationDate: Installed on 2013-10-19 (10 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711482] Re: Firefox shows white screen of death

2017-08-23 Thread shemgp

The fix gfx.xrender.enabled=true doesn't work for in Xenial but works in
Artful.

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

Title:
  Firefox shows white screen of death

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox 55 & 56 shows white screen of death (no contents, just white
  screen) after a while of being used in Ubuntu GNOME.  To show the bug
  more quickly try refreshing gnome-shell (ALT-F2 r) while Firefox is
  opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   shemgp24833 F...m pulseaudio
   /dev/snd/controlC2:  shemgp24833 F pulseaudio
   /dev/snd/controlC1:  shemgp24833 F pulseaudio
   /dev/snd/controlC0:  shemgp24833 F pulseaudio
  BuildID: 20170816210634
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Aug 18 09:55:10 2017
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so 
(browser-plugin-freshplayer-pepperflash)
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  MostRecentCrashID: bp-c408a251-b0e4-488d-a7a6-6676b1170814
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=55.0.2/20170816210634 (In use)
   Profile1 - LastVersion=44.0a2/20151214004008 (Out of date)
  RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 
0.3.6-1~webupd8~xenial6
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V11.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68MA-ED55 (MS-7676)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV11.1:bd01/09/2013:svnMSI:pnMS-7676:pvr2.0:rvnMSI:rnZ68MA-ED55(MS-7676):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7676
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

2017-08-23 Thread Eric Carroll

1. apt-get install dbus-user-session
2. reboot
3. confirm flatpak not installed: 
emc@emc-office:~$ which flatpak

4. Check reverse dependancies and ensure there is nothing dependant on
it

emc@emc-office:~$ apt-rdepends --reverse dbus-user-session
Reading package lists... Done
Building dependency tree   
Reading state information... Done
dbus-user-session
  Reverse Depends: razer-daemon (1.1.15-0ubuntu1)
razer-daemon
  Reverse Depends: polychromatic (>= 0.3.10-xenial)
polychromatic
emc@emc-office:~$ sudo apt-get remove --purge razer-daemon polychromatic 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package 'polychromatic' is not installed, so not removed
Package 'razer-daemon' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

5. Check Passwords and Keys

Login section is missing

6. start chrome

emc@emc-office:~$ /opt/google/chrome/chrome 
[4151:4181:0823/233754.144116:ERROR:nss_util.cc(802)] After loading Root Certs, 
loaded==false: NSS error code: -8018
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[4151:4151:0823/233844.494199:ERROR:background_mode_manager_aura.cc(13)] Not 
implemented reached in virtual void 
BackgroundModeManager::EnableLaunchOnStartup(bool)
Gkr-Message: secret service operation failed: Did not receive a reply. Possible 
causes include: the remote application did not send a reply, the message bus 
security policy blocked the reply, the reply timeout expired, or the network 
connection was broken.
[4151:4176:0823/233909.532194:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-103397427961759974994

7. Remove dbus-user-session, reboot and confirm problem resolved

Yep.

So I think this is clear that adding/deleting dbus-user-session induces
seahorse to not unlock, cause undetermined, which then sets off failures
for anyone using keys.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1656790] Re: print-notifications: Don't show error for job in progress

2017-08-23 Thread kolya

I think this is actually bug in system-config-printer package that is
used by ubuntu mate to control printers.

** Also affects: system-config-printer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  print-notifications: Don't show error for job in progress

Status in ubuntu-mate:
  New
Status in mate-settings-daemon package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  Running Ubuntu MATE 16.04.1 LTS

  Every single time I print something, I get an error notification.

  Unfortunly, I'm running a Norwegian desktop, so this will be a
  translation of what I suppose the notification says on an English
  desktop:

  Printer error
  Printer 'NAME':'cups-waiting-for-job-completed'

  
  It is a bit annoying, but it disappears after a couple of seconds, when the 
print job is done.

  
  After a bit of Googling, I found this is a known error from earlier, with 
gnome-settings-daemon. I guess the fix never have been included in 
mate-settings-daemon ?

  
  This is the bug in Red Hat for the same problem:
  https://bugzilla.redhat.com/show_bug.cgi?id=1207154

  This is the patch for gnome-settings-daemon from May 20 2015 :
  https://mail.gnome.org/archives/commits-list/2015-May/msg03447.html

  
  The 'cups-waiting-for-job-completed' is a notification in Cups, which should 
not be ignored by gnome-settings-daemon.

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

2017-08-23 Thread Eric Carroll

Jeremy,

razer-daemon committer identifies they are expressing a package
dependency correctly, and if installing dbus-user-session causes chrome
to break, that's not a driver/package problem. They have a point.
https://github.com/terrycain/razer-drivers/issues/358

I would like to say that I am happy to gather data on this and debug it,
if someone would help me understand where to look. If this was a kernel
issue I would be beavering away, but this is gnome, and as far as I can
tell dbus-user-session is systemd transition related, so I am less
clueful.

Let me run an experiment. I will install dbus-user-session by itself. If
this causes gnome-keyring not to unlock and thus chrome to fail, would
we have consensus there is a problem here that has nothing to do with
other packages that drag in dbus-user-session?


** Bug watch added: github.com/terrycain/razer-drivers/issues #358
   https://github.com/terrycain/razer-drivers/issues/358

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  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/1689825/+subscriptions

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

[Desktop-packages] [Bug 1712719] [NEW] PCI/internal sound card not detected

2017-08-23 Thread FRANCISCO GUAJARDO

Public bug reported:

hi i did the update and i lost the sound i have checked the mute the
volume and did a test on the right and left speakers and nothing i also
tried the troubleshooting on the help menu and i can't find the driver
for the sound

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Wed Aug 23 21:47:03 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-chestersmill-trusty-amd64-20150428-4
InstallationDate: Installed on 2016-10-01 (326 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150428-09:25
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: FCBYT10H.86A.0024.2015.0522.1757
dmi.board.name: STCK1A8LFC
dmi.board.vendor: Intel Corporation
dmi.board.version: H67494-302
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrFCBYT10H.86A.0024.2015.0522.1757:bd05/22/2015:svnIntelCorporation:pnSTCK1A8LFC:pvrH85499-100:rvnIntelCorporation:rnSTCK1A8LFC:rvrH67494-302:cvnIntelCorporation:ct3:cvr1.0:
dmi.product.name: STCK1A8LFC
dmi.product.version: H85499-100
dmi.sys.vendor: Intel Corporation

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


** Tags: amd64 apport-bug trusty

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  hi i did the update and i lost the sound i have checked the mute the
  volume and did a test on the right and left speakers and nothing i
  also tried the troubleshooting on the help menu and i can't find the
  driver for the sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Aug 23 21:47:03 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-chestersmill-trusty-amd64-20150428-4
  InstallationDate: Installed on 2016-10-01 (326 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150428-09:25
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: FCBYT10H.86A.0024.2015.0522.1757
  dmi.board.name: STCK1A8LFC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H67494-302
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrFCBYT10H.86A.0024.2015.0522.1757:bd05/22/2015:svnIntelCorporation:pnSTCK1A8LFC:pvrH85499-100:rvnIntelCorporation:rnSTCK1A8LFC:rvrH67494-302:cvnIntelCorporation:ct3:cvr1.0:
  dmi.product.name: STCK1A8LFC
  dmi.product.version: H85499-100
  dmi.sys.vendor: Intel Corporation

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

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

[Desktop-packages] [Bug 869793] Re: Nautilus is very slow when opening folders with many files

2017-08-23 Thread Bug Watch Updater

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

Title:
  Nautilus is very slow when opening folders with many files

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

Bug description:
  Opening folders with many files takes a long time with Nautilus, to the point 
it becomes unusable for folders with more than 5K files. 
  I've measured the time it takes for folders with different amount of files to 
open with Nautilus and Gnome Commander. It is ~6 times faster with GC on 
average. In folders with ~20K files, it takes 30s with nautilus versus 6! with 
GC. 

  With Nautilus
  ~3500 files tales 6 seconds
  ~7000 files takes 18 seconds
  ~15000 files takes 22 seconds
  ~2 files takes 30 seconds

  With Gnome Commander
  ~3500 files tales <1 second
  ~7000 files takes 1.5 seconds
  ~15000 files takes 3 seconds
  ~2 files takes 6 seconds

  These are mostly small dicom files (MRI images). I am using a 8 core 3.4Ghz 
and 16Gigs of RAM with Ubuntu 11.04 64-bits.
  Also, of course, things like selecting all files and copying them around is 
absurdly slow and makes nautilus unusable... but that would be another bug 
report (?).

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

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

[Desktop-packages] [Bug 1712664] Re: GNOME Control Center results in GNOME Shell Overview are not translated in Ubuntu 17.10

** Tags added: gnome-17.10

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

Title:
  GNOME Control Center results in GNOME Shell Overview are not
  translated in Ubuntu 17.10

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

Bug description:
  GNOME Control Center results in GNOME Shell Overview are untranslated
  on my non-English Ubuntu 17.10 install even though they are fully
  translated in GNOME Control Center itself. See the attached
  screenshot.

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

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

[Desktop-packages] [Bug 1712529] Re: pulseaudio crashed with SIGABRT in pa_source_output_attach()

** Information type changed from Private to Public

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

Title:
  pulseaudio crashed with SIGABRT in pa_source_output_attach()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Just upgraded packages in 17.10 dev and rebooted and this crash popped
  out.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shemgp15659 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 23 17:02:31 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-09-28 (694 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_source_output_attach () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   pa_source_attach_within_thread () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   ?? () from /usr/lib/pulse-10.0/modules/module-echo-cancel.so
   pa_source_process_msg () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   ?? () from /usr/lib/pulse-10.0/modules/libalsa-util.so
  Title: pulseaudio crashed with SIGABRT in pa_source_output_attach()
  UpgradeStatus: Upgraded to artful on 2017-08-12 (10 days ago)
  UserGroups: adm cdrom dip docker fuse kismet libvirt libvirtd lp lpadmin lxd 
mail mythtv netdev plugdev sambashare sbuild scanner sudo video
  dmi.bios.date: 09/24/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA3WW (2.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA3WW(2.63):bd09/24/2015:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

Yes, I briefly forgot about zesty. We could fix zesty too, but in
hindsight it's probably still a good idea to prioritize xenial first.

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

2017-08-23 Thread Mike Rushton

$ apt rdepends dbus-user-session
dbus-user-session
Reverse Depends:
 |Suggests: dbus
  Depends: anbox-common
 |Suggests: dbus
 |Suggests: dbus

Which I understand is not an official package and in my case, is no
longer installed. The point is, dbus-user-session is an official package
and causes major problems with Ubuntu if it is installed for any reason.
I feel these problems should be fixed in the dbus-user-session package
or in the packages it affects (gnome-keyring) when installed.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  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/1689825/+subscriptions

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

[Desktop-packages] [Bug 1712715] [NEW] Row filter not working for dates

2017-08-23 Thread Lucas Clemente Vella

Public bug reported:

Trying to select rows by year in the first column of the attached file
hides all lines, instead of keeping the lines matching the selected
filter criteria.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libreoffice-calc 1:5.3.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-32.36-lowlatency 4.10.17
Uname: Linux 4.10.0-32-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Aug 23 23:26:09 2017
InstallationDate: Installed on 2015-07-05 (780 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to zesty on 2017-04-30 (115 days ago)

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


** Tags: amd64 apport-bug zesty

** Attachment added: "File triggering the bug"
   
https://bugs.launchpad.net/bugs/1712715/+attachment/4937787/+files/BUG_AUTO_FILTRO.ods

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

Title:
  Row filter not working for dates

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Trying to select rows by year in the first column of the attached file
  hides all lines, instead of keeping the lines matching the selected
  filter criteria.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-calc 1:5.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-lowlatency 4.10.17
  Uname: Linux 4.10.0-32-lowlatency x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Aug 23 23:26:09 2017
  InstallationDate: Installed on 2015-07-05 (780 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to zesty on 2017-04-30 (115 days ago)

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

Mike, what is the output of this command:

apt rdepends dbus-user-session

** Project changed: dbus => meta-gnome3 (Ubuntu)

** No longer affects: meta-gnome3 (Ubuntu)

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  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/1689825/+subscriptions

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

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

** Changed in: meta-gnome3 (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  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/1689825/+subscriptions

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

[Desktop-packages] [Bug 1712714] [NEW] deja-dup autopkgtest failure with meson 0.42

Public bug reported:

deja-dup's autopkgtest now fails with meson 0.42.


autopkgtest [01:28:42]: test check: ---]
checkFAIL stderr: Warning: This executable is deprecated. Use 
"meson test" instead.autopkgtest [01:28:46]: test check:  - - - - - - - - - - 
results - - - - - - - - - -


http://autopkgtest.ubuntu.com/packages/d/deja-dup/artful/armhf

Basically change "mesontest" to "meson test" in debian/tests/check

I'm setting the importance to High because this autopkgtest regression
prevents other packages from migrating to artful.

** Affects: deja-dup (Ubuntu)
 Importance: High
 Status: New

** Description changed:

  deja-dup's autopkgtest now fails with meson 0.42.
  
  
  autopkgtest [01:28:42]: test check: ---]
  checkFAIL stderr: Warning: This executable is deprecated. Use 
"meson test" instead.autopkgtest [01:28:46]: test check:  - - - - - - - - - - 
results - - - - - - - - - -
  
  
+ http://autopkgtest.ubuntu.com/packages/d/deja-dup/artful/armhf
+ 
  Basically change "mesontest" to "meson test" in debian/tests/check
  
  I'm setting the importance to High because this autopkgtest regression
  prevents other packages from migrating to artful.

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

Title:
  deja-dup autopkgtest failure with meson 0.42

Status in deja-dup package in Ubuntu:
  New

Bug description:
  deja-dup's autopkgtest now fails with meson 0.42.

  
  autopkgtest [01:28:42]: test check: ---]
  checkFAIL stderr: Warning: This executable is deprecated. Use 
"meson test" instead.autopkgtest [01:28:46]: test check:  - - - - - - - - - - 
results - - - - - - - - - -
  

  http://autopkgtest.ubuntu.com/packages/d/deja-dup/artful/armhf

  Basically change "mesontest" to "meson test" in debian/tests/check

  I'm setting the importance to High because this autopkgtest regression
  prevents other packages from migrating to artful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1712714/+subscriptions

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

[Desktop-packages] [Bug 1704162] Re: Add on/off switch for network connectivity check

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

** Changed in: network-manager (Ubuntu)
   Status: New => Fix Committed

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: gnome-control-center (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Add on/off switch for network connectivity check

Status in gnome-control-center:
  Confirmed
Status in NetworkManager:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  For Ubuntu 17.10, the Desktop Team would like to enable
  NetworkManager's connectivity check (LP: #997200) to detect captive
  portals. This has been supported by other GNOME distros for a couple
  years. Fedora in particular makes it opt out which we plan to do also
  in Ubuntu.

  This bug is a feature request to add an on/off switch for this
  connectivity check to gnome-control-center. I suggest that it be added
  to the Privacy panel although it might also work in the Network panel.

  I think there are two ways the switch could work. It could either
  write directly to a config file or it could use PackageKit to install
  or uninstall the distro-specific package that contains the
  connectivity config file. The advantage of the separate binary package
  is that it's easy to install or uninstall it for people that don't use
  gnome-control-center.

  See the upstream bug for a bit more details.

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

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

[Desktop-packages] [Bug 1704162] Re: Add on/off switch for network connectivity check

** Branch linked: lp:~ubuntu-desktop/gnome-control-center/ubuntu

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

Title:
  Add on/off switch for network connectivity check

Status in gnome-control-center:
  Confirmed
Status in NetworkManager:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  For Ubuntu 17.10, the Desktop Team would like to enable
  NetworkManager's connectivity check (LP: #997200) to detect captive
  portals. This has been supported by other GNOME distros for a couple
  years. Fedora in particular makes it opt out which we plan to do also
  in Ubuntu.

  This bug is a feature request to add an on/off switch for this
  connectivity check to gnome-control-center. I suggest that it be added
  to the Privacy panel although it might also work in the Network panel.

  I think there are two ways the switch could work. It could either
  write directly to a config file or it could use PackageKit to install
  or uninstall the distro-specific package that contains the
  connectivity config file. The advantage of the separate binary package
  is that it's easy to install or uninstall it for people that don't use
  gnome-control-center.

  See the upstream bug for a bit more details.

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

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

[Desktop-packages] [Bug 1491073] Re: Invalid data message while opening a file

2017-08-23 Thread bladefallcon

I am running Ubuntu 17.04, Transmission 2.94 (14714)
And I am getting this exact problem. Every torrent, I get the error, but each 
one, if I just click close, I can still open the file and download...

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

Title:
  Invalid data message while opening a file

Status in transmission package in Ubuntu:
  Fix Released

Bug description:
  When I open any file in Transmission I get message that file contain
  invalid data, but I can open torrent file anyway when I close the
  message. I think that this is a bug because this happen to every file
  I open.

  transmission-gtk 2.84 (14307)
  Xubuntu 13.04

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

2017-08-23 Thread Mike Rushton

This bug was not only related to Flatpak. I have never
installed/used/heard of Flapak before I filed this bug. Maybe this bug
should be filed against dbus-user-session.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

Eric, please contact the distributor/maintainer for razer-daemon and
polychromatic since those packages are not provided by Ubuntu.

I'm closing this bug since the issue was specific to the Flatpak PPA and
that was resolved there weeks ago.

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

** No longer affects: gdm (Ubuntu)

** No longer affects: lightdm (Ubuntu)

** No longer affects: libgnome-keyring (Ubuntu)

** No longer affects: gnome-keyring (Ubuntu)

** Changed in: dbus (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

Rocko, please file a different bug for that issue.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Triaged
Status in flatpak package in Ubuntu:
  Fix Released

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711545] Re: glib-compile-schemas assert failure: * Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid pointer: 0x0000002601a1d1e0

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

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  glib-compile-schemas assert failure: *** Error in `/usr/lib/x86_64
  -linux-gnu/glib-2.0/glib-compile-schemas': munmap_chunk(): invalid
  pointer: 0x002601a1d1e0 ***

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  Got that crash while upgrading some packages:

  Preparing to unpack .../0-ubuntu-minimal_1.395_amd64.deb ...
  Unpacking ubuntu-minimal (1.395) over (1.394) ...
  Preparing to unpack .../1-ubuntu-standard_1.395_amd64.deb ...
  Unpacking ubuntu-standard (1.395) over (1.394) ...
  Preparing to unpack .../2-gnome-session-bin_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session-bin (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../3-ubuntu-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking ubuntu-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../4-gnome-session_3.24.1-0ubuntu21_amd64.deb ...
  Unpacking gnome-session (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../5-gnome-session-common_3.24.1-0ubuntu21_all.deb ...
  Unpacking gnome-session-common (3.24.1-0ubuntu21) over (3.24.1-0ubuntu20) ...
  Preparing to unpack .../6-ubuntu-settings_17.10.12_all.deb ...
  Unpacking ubuntu-settings (17.10.12) over (17.10.11) ...
  Preparing to unpack .../7-ubuntu-web-launchers_17.10.12_all.deb ...
  Unpacking ubuntu-web-launchers (17.10.12) over (17.10.11) ...
  Processing triggers for gconf2 (3.2.6-4ubuntu1) ...
  Processing triggers for mime-support (3.60ubuntu1) ...
  Setting up ubuntu-web-launchers (17.10.12) ...
  Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
  Setting up ubuntu-settings (17.10.12) ...
  Processing triggers for libglib2.0-0:amd64 (2.53.4-3ubuntu1) ...
  No such key 'enable-hot-corners' in schema 'org.gnome.shell:ubuntu' as 
specified in override file 
'/usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override'; ignoring 
override for this key.
  *** Error in `/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas': 
munmap_chunk(): invalid pointer: 0x002601a1d1e0 ***
  === Backtrace: =
  /lib/x86_64-linux-gnu/libc.so.6(+0x790bb)[0x7fb4dfe8b0bb]
  /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1f8)[0x7fb4dfe98f08]
  /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_strfreev+0x29)[0x7fb4e02423e9]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x3ff6)[0x25ff8c9ff6]
  /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fb4dfe32421]
  /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas(+0x404a)[0x25ff8ca04a]
  === Memory map: 
  25ff8c6000-25ff8d r-xp  08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffacf000-25ffad r--p 9000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  25ffad-25ffad1000 rw-p a000 08:04 523111 
/usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas
  26018a6000-2601b18000 rw-p  00:00 0  
[heap]
  7fb4df48f000-7fb4df4a5000 r-xp  08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df4a5000-7fb4df6a4000 ---p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a4000-7fb4df6a5000 r--p 00015000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a5000-7fb4df6a6000 rw-p 00016000 08:04 522367 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  7fb4df6a6000-7fb4df981000 r--p  08:04 522184 
/usr/lib/locale/locale-archive
  7fb4df981000-7fb4df999000 r-xp  08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4df999000-7fb4dfb99000 ---p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb99000-7fb4dfb9a000 r--p 00018000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9a000-7fb4dfb9b000 rw-p 00019000 08:04 542247 
/lib/x86_64-linux-gnu/libpthread-2.24.so
  7fb4dfb9b000-7fb4dfb9f000 rw-p  00:00 0 
  7fb4dfb9f000-7fb4dfc11000 r-xp  08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfc11000-7fb4dfe1 ---p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe1-7fb4dfe11000 r--p 00071000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe11000-7fb4dfe12000 rw-p 00072000 08:04 523149 
/lib/x86_64-linux-gnu/libpcre.so.3.13.3
  7fb4dfe12000-7fb4dffce000 r-xp  08:04 54 
/lib/x86_64-linux-gnu/libc-2.24.so

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed

2017-08-23 Thread Rocko

I also have this issue in Ubuntu 17.10 (running gdm/gnome-shell).
Uninstalling dbus-user-session isn't really an option, because tons of
apps depend on it.

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

Title:
  gnome-keyring not unlocked on xenial when dbus-user-session is
  installed

Status in D-Bus:
  New
Status in chromium-browser package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Confirmed
Status in flatpak package in Ubuntu:
  Confirmed
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1712708] [NEW] USB Keyboard+SmartPad

2017-08-23 Thread Lorenzo

Public bug reported:

The scroll of touchpad dont work, my touchpad is Synaptics, but the
system recognizes it as USB Keyboard+SmartPad.

More information:

I: Bus=0003 Vendor=04f3 Product=0740 Version=0110
N: Name="USB Keyboard+SmartPad"
P: Phys=usb-:00:1a.0-1.3.1/input1
S: 
Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:04F3:0740.0006/input/input15
U: Uniq=
H: Handlers=kbd mouse2 event10 
B: PROP=0
B: EV=10001f
B: KEY=3007f 0 0 48317aff32d bf56 1f0003 130c130b17c000 
267bfad941dfed 9e16804400 1002
B: REL=1c3
B: ABS=1f01
B: MSC=10

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Aug 23 22:01:58 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e1]
InstallationDate: Installed on 2017-08-23 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=fd28929f-93e7-4355-acd3-2688ff9aba77 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P10AAT.050.140215.dg
dmi.board.asset.tag: No Asset Tag
dmi.board.name: XE700T1C-A01CL
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 8
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP10AAT.050.140215.dg:bd02/15/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP10AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A01CL:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A:
dmi.product.name: 700T1C
dmi.product.version: P10AAT
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Aug 23 21:51:10 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 Wacom ISDv4 EC Pen stylus: Invalid type 'cursor' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'touch' for this device.
 Wacom ISDv4 EC Pen stylus: Invalid type 'pad' for this device.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  USB Keyboard+SmartPad

Status in xorg package in Ubuntu:
  New

Bug description:
  The scroll of touchpad dont work, my touchpad is Synaptics, but the
  system recognizes it as USB Keyboard+SmartPad.

  More information:

  I: Bus=0003 Vendor=04f3 Product=0740 Version=0110
  N: Name="USB Keyboard+SmartPad"
  P: Phys=usb-:00:1a.0-1.3.1/input1
  S: 
Sysfs=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3.1/1-1.3.1:1.1/0003:04F3:0740.0006/input/input15
  U: Uniq=
  H: Handlers=kbd mouse2 event10 
  B: PROP=0
  B: EV=10001f
  B: KEY=3007f 0 0 48317aff32d bf56 1f0003 130c130b17c000 
267bfad941dfed 9e16804400 1002
  B: REL=1c3
  B: ABS=1f01
  B: MSC=10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64

[Desktop-packages] [Bug 1708569] Re: 1st. login fails to create a complete $HOME directory in a ubuntu-wayland (defacto default) session

2017-08-23 Thread Matthias Klumpp

FTR, this is also resolved upstream now :-)

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

Title:
  1st. login fails to create a complete $HOME directory in a ubuntu-
  wayland (defacto default) session

Status in Xdg User Dirs:
  Confirmed
Status in xdg-user-dirs package in Ubuntu:
  Fix Released

Bug description:
  Test case:
  Use latest image (august 2 here
  Install, reboot
  Check contents of home folder

  Seen here:
  $ ls
  Desktop  examples.desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubiquity (not installed)
  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: Thu Aug  3 22:07:38 2017
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
  InstallationDate: Installed on 2017-08-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170802)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-user-dirs/+bug/1708569/+subscriptions

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

[Desktop-packages] [Bug 1706478] Re: Show promoted snap in "Featured" section

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

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

Title:
  Show promoted snap in "Featured" section

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  [Impact]
  The "Featured" banner only shows hard-coded .debs that are available. This 
should show the currently promoted snap.

  [Test Case]
  1. Open GNOME Software
  2. Look at featured section

  Expected result:
  The currently promoted snap is shown.

  Observed result:
  A hard-coded .deb is shown.

  [Regression Potential]
  The change is to use the first snap from the "featured" store section and 
show it here. If there is a screenshot with the name "banner" then this is used 
as the promotion image (and not shown in screenshots).

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

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

[Desktop-packages] [Bug 1705953] Re: Show only snaps in "Editor's Picks"

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

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

Title:
  Show only snaps in "Editor's Picks"

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  [Impact]
  The "Editor's Picks" section currently contains a mix of hard-coded values, 
values based on Ubuntu reviews and snaps from the "featured" snap store 
section. As snaps are the newest and preferred method of installing things in 
Ubuntu it should show only these in the order provided by snapd, falling back 
to the default behaviour if no snaps are found.

  [Test Case]
  1. Open GNOME Software
  2. Look at "Editor's Picks" section

  Expected result:
  This section contains the snaps from the "featured" snap store section in the 
correct order.

  Observed result:
  This section contains a mix of .deb and snaps. Some snaps may not be shown 
due to not being able to fit them all in. The order is random (changes daily).

  [Regression Potential]
  Solution is to add featured snaps last after clearing the existing featured 
apps. GNOME Software was modified to not randomize this list. Some risk of 
breaking related code.

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

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

[Desktop-packages] [Bug 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

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

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

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

[Desktop-packages] [Bug 1568410] Re: Double-clicking .desktop file makes nautilus show bogus file

2017-08-23 Thread Bug Watch Updater

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

Title:
  Double-clicking .desktop file makes nautilus show bogus file

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

Bug description:
  When double-clicking a .desktop file in nautilus, bogus file briefly
  appear and the original .desktop file "jerks" because of that. This
  behaviour is quite annoying. Try unpacking tor browser bundle for
  instance, navigate to tor-browser-en-US directory in nautilus and
  double-click Tor Browser icon (the .desktop file). The file briefly
  appears, marked as no read/write access (the little lock and cross
  icons attached). I could not catch it with screen capture to see what
  it was but you could see it for yourself. I believe that this is a
  temp file. To verify, follow the steps below.

  1. Make sure nautilus is configured to hide hidden files and that you can 
reproduce the bug as has been described to this point
  2. Leave nautilus window open, launch terminal and create a file named 
.HIDDEN in tor-browser-en-US directory (the directory active in nautilus)
  3. Double-click Tor Browser icon once again in nautilus

  Now you should be able to see the file in question and look up its
  properties in nautilus (see attached screen shot)

  4. Return to the terminal and run 'ls -la' command to see that the file isn't 
really present in the directory.
  5. Refresh nautilus window with F5 button to return to normal

  I believe this behaviour in nautilus is wrong but have no idea how to
  fix it. Any idea?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4
  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: Sun Apr 10 00:47:49 2016
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'823x550+457+222'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where']"
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.nautilus.autostart.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2016-02-10T01:22:47.461799

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

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

[Desktop-packages] [Bug 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

2017-08-23 Thread Robert Ancell

I didn't manage to work out why this is happening, but gnome-software
3.25.4 replaced this code with the AsIcon code and it doesn't seem to be
occuring anymore. This change was backporter to 3.22 and 3.20 and should
hopefully fix this issue.

** Changed in: gnome-software (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Zesty)
   Status: New => Fix Committed

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

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

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

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

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

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

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

[Desktop-packages] [Bug 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

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

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

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

[Desktop-packages] [Bug 1706478] Re: Show promoted snap in "Featured" section

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

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

Title:
  Show promoted snap in "Featured" section

Status in gnome-software package in Ubuntu:
  Triaged
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  [Impact]
  The "Featured" banner only shows hard-coded .debs that are available. This 
should show the currently promoted snap.

  [Test Case]
  1. Open GNOME Software
  2. Look at featured section

  Expected result:
  The currently promoted snap is shown.

  Observed result:
  A hard-coded .deb is shown.

  [Regression Potential]
  The change is to use the first snap from the "featured" store section and 
show it here. If there is a screenshot with the name "banner" then this is used 
as the promotion image (and not shown in screenshots).

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

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

[Desktop-packages] [Bug 1708140] Re: /usr/bin/gnome-software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

2017-08-23 Thread Robert Ancell

** Description changed:

- The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.5-0ubuntu0.16.04.5, the problem page at 
https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
- If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ [Impact]
+ errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.
+ 
+ [Test Case]
+ 1. Check errors.ubuntu.com for crash reports in the icon cache code
+ 
+ Expected result:
+ Errors do not occur.
+ 
+ Observed result:
+ Errors occur.
+ 
+ [Regression Potential]
+ Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).
+ 
+ [1]
+ https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

Title:
  /usr/bin/gnome-
  
software:11:gs_plugin_snap_set_app_pixbuf_from_data:load_icon:gs_plugin_refine_app:gs_plugin_loader_run_refine:gs_plugin_loader_search_thread_cb

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  errors.ubuntu.com [1] is showing crashes in the icon caching code. Inspection 
and testing of this code doesn't show any reason why this code path can occur.

  [Test Case]
  1. Check errors.ubuntu.com for crash reports in the icon cache code

  Expected result:
  Errors do not occur.

  Observed result:
  Errors occur.

  [Regression Potential]
  Some risk of introducing new bugs in the icon handling code. The code is 
similar to what has been released into Artful, but needed to be modified to 
work with the older version of gnome-software in Xenial (the Zesty change is 
the same as Artful).

  [1]
  https://errors.ubuntu.com/problem/3a1f24323eae90094dc223360e9f0e56deb5e56d

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

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

[Desktop-packages] [Bug 1663926] Re: Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017

2017-08-23 Thread Mark Bucknell

Anything? is this even remotely on the radar?

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

Title:
  Dell XPS 15 9560 (Nvidia 1050) black screen, Feb 11, 2017

Status in Nvidia:
  New
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  There have been multiple reports that "nvidia-prime select intel" results in 
a black screen on the new Dell XPS 15 (9560, with Nvidia 1050)
  See the following threads:

  1. (initial report). 
  
https://www.reddit.com/r/Ubuntu/comments/5qjq4v/dell_xps_15_kaby_lake_w_nvidia_1050_review_2017/

  2. (lots of confirmations of the same thing)
   
https://www.reddit.com/r/Dell/comments/5rxb5x/any_dell_xps_15_9560_linux_users/ 

  3. (additional confirmation)
  
https://www.reddit.com/r/Dell/comments/5t2b5d/high_cpu_temp_and_fan_usage_for_ubuntu_on_9560/

  4. (reported on Nvidia forums)
  
https://devtalk.nvidia.com/default/topic/991853/complete-freeze-with-nvidia-prime/

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

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

[Desktop-packages] [Bug 1710789] Re: chromium does not open downloaded files

2017-08-23 Thread RCV

Yes, chromium is working correctly. Thank you

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

Title:
  chromium does not open downloaded files

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I have up to date Ubuntu 17.04. Recently, Chromium stoped to open
  downloaded files.

  If i download and open doc file from chromium, in command line i see
  the following message:

  /usr/lib/libreoffice/program/soffice.bin: relocation error:
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol
  mir_display_config_release, version MIR_CLIENT_0.21 not defined in
  file libmirclient.so.9 with link time reference

  If i download pdf file i see the same message with evince instead of
  libreoffice.

  It looks like more general problem, but I still can open files from
  these two applications or using xdg-open.

  I tried to work with new chromium profile, but i get the same message
  no matter what and files cannot be opened.

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

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

[Desktop-packages] [Bug 1712701] Re: Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

2017-08-23 Thread Simon Steinbeiß

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

** Also affects: gtk+3.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872687
   Importance: Unknown
   Status: Unknown

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

Title:
  Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

Status in GTK+:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  This bug affects gtk3 >= 3.22.18.1.

  How to reproduce:
  
  In Xfce, try to open the xfce4-powermanager-plugin and click the 
brightness-slider.
  When dragging the slider, the parent window disappears (loses focus) and the 
slider value is not changed.

  This is a regression within Gtk+ which was introduced in
  
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

  garnacho has provided a patch in the upstream bugreport but so far it
  has not been merged.

  Note that this bug has already been reported in Arch and Debian.

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

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

[Desktop-packages] [Bug 1712701] [NEW] Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

2017-08-23 Thread Simon Steinbeiß

Public bug reported:

This bug affects gtk3 >= 3.22.18.1.

How to reproduce:

In Xfce, try to open the xfce4-powermanager-plugin and click the
brightness-slider.
When dragging the slider, the parent window disappears (loses focus) and the
slider value is not changed.

This is a regression within Gtk+ which was introduced in
https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

garnacho has provided a patch in the upstream bugreport but so far it
has not been merged.

Note that this bug has already been reported in Arch and Debian.

** Affects: gtk
Importance: Unknown
Status: Unknown

** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New

** Affects: gtk+3.0 (Debian)
Importance: Unknown
Status: Unknown

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

** Also affects: gtk via
https://bugzilla.gnome.org/show_bug.cgi?id=786029
Importance: Unknown
Status: Unknown

** Description changed:

This bug affects gtk3 >= 3.22.18.1.

How to reproduce:

In Xfce, try to open the xfce4-powermanager-plugin and click the
brightness-slider.
When dragging the slider, the parent window disappears (loses focus) and the
slider value is not changed.

This is a regression within Gtk+ which was introduced in

https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

garnacho has provided a patch in the upstream bugreport but so far it
has not been merged.
+
+ Note that this bug has already been reported in Arch and Debian.

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

Title:
Clicking on a GtkRange inside a GtkMenuitem makes the parent disappear

Status in GTK+:
Unknown
Status in gtk+3.0 package in Ubuntu:
New
Status in gtk+3.0 package in Debian:
Unknown

Bug description:
This bug affects gtk3 >= 3.22.18.1.

How to reproduce:

In Xfce, try to open the xfce4-powermanager-plugin and click the
brightness-slider.
When dragging the slider, the parent window disappears (loses focus) and the
slider value is not changed.

This is a regression within Gtk+ which was introduced in

https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=9b032073cbcf5aadbeb4b74f0cf662a9fa5f5530

garnacho has provided a patch in the upstream bugreport but so far it
has not been merged.

Note that this bug has already been reported in Arch and Debian.

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

[Desktop-packages] [Bug 1710789] Re: chromium does not open downloaded files

2017-08-23 Thread Olivier Tilloy

> May i test this package now?

Packages available at:

https://launchpad.net/~osomon/+archive/ubuntu/cr-test-
officialbuild/+packages

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

Title:
  chromium does not open downloaded files

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I have up to date Ubuntu 17.04. Recently, Chromium stoped to open
  downloaded files.

  If i download and open doc file from chromium, in command line i see
  the following message:

  /usr/lib/libreoffice/program/soffice.bin: relocation error:
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol
  mir_display_config_release, version MIR_CLIENT_0.21 not defined in
  file libmirclient.so.9 with link time reference

  If i download pdf file i see the same message with evince instead of
  libreoffice.

  It looks like more general problem, but I still can open files from
  these two applications or using xdg-open.

  I tried to work with new chromium profile, but i get the same message
  no matter what and files cannot be opened.

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

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

[Desktop-packages] [Bug 1437502] Re: nautilus lacking 'new document' in context menu on GNOME

2017-08-23 Thread Jeremy Soller

I believe this applies again to Ubuntu 17.10.

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

Title:
  nautilus lacking 'new document' in context menu on GNOME

Status in Ubuntu GNOME:
  Triaged
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  As the title mentions nautilus is provided in its default state and
  there is no 'New Document' in the context menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 27 17:49:01 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-03-27 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1712660] Re: application menu icon in title bar has wrong size

2017-08-23 Thread Philipp

** Description changed:

  gnome-terminal application menu icon in the title bar has the wrong size.
  See screenshot
+ 
+ Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

** No longer affects: light-themes (Ubuntu)

** Also affects: humanity-icon-theme (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

- gnome-terminal application menu icon in the title bar has the wrong size.
+ gnome-terminal application menu icon in the title bar has the wrong size. 
Porbably only affects humanity-icon-theme, works fine with a Ubuntu Gnome and 
the adwaita icon theme.
  See screenshot
  
  Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size. 
Porbably only affects humanity-icon-theme, works fine with a Ubuntu Gnome and 
the adwaita icon theme.
  See screenshot

  Ubuntu 17.10, gnome-temrinal 3.24.2-0ubuntu4

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

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

[Desktop-packages] [Bug 1712663] [NEW] Visioneer RoadWarrior Scanner [Sane]

2017-08-23 Thread Andrew Charnley

Public bug reported:

I just picked up one of these portable scanners, it works well in
Windows.

In Linux and either xsane or simple-scan however it always scans a
completely black page.

Thinking it was a calibration issue I ran:-

SANE_DEBUG_GENESYS=255 scanimage -d genesys --calibrate 2>calibrate.log

Which at first reported it couldn't find the correct sheet. I made one
using:
http://www.fixya.com/support/t17003105-calibration_sheet_visioneer_roadwarrior
and the errors went away

This is resolved. The calibration value "01 e8 00 00 00" is written.
There is still an error in the log but it appears to be OK. I'm unsure
if it's calibration anyhow as it worked OK-ish in Windows (washed out,
but had an image).

Scans are still completely black.

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "calibrate.log"
   
https://bugs.launchpad.net/bugs/1712663/+attachment/4937663/+files/calibrate.log

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

Title:
  Visioneer RoadWarrior Scanner [Sane]

Status in simple-scan package in Ubuntu:
  New

Bug description:
  I just picked up one of these portable scanners, it works well in
  Windows.

  In Linux and either xsane or simple-scan however it always scans a
  completely black page.

  Thinking it was a calibration issue I ran:-

  SANE_DEBUG_GENESYS=255 scanimage -d genesys --calibrate
  2>calibrate.log

  Which at first reported it couldn't find the correct sheet. I made one
  using:
  http://www.fixya.com/support/t17003105-calibration_sheet_visioneer_roadwarrior
  and the errors went away

  This is resolved. The calibration value "01 e8 00 00 00" is written.
  There is still an error in the log but it appears to be OK. I'm unsure
  if it's calibration anyhow as it worked OK-ish in Windows (washed out,
  but had an image).

  Scans are still completely black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1712663/+subscriptions

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

[Desktop-packages] [Bug 1712664] [NEW] GNOME Control Center results in GNOME Shell Overview are not translated in Ubuntu 17.10

2017-08-23 Thread AsciiWolf

Public bug reported:

GNOME Control Center results in GNOME Shell Overview are untranslated on
my non-English Ubuntu 17.10 install even though they are fully
translated in GNOME Control Center itself. See the attached screenshot.

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

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


** Tags: artful l10n

** Attachment added: "gnome-shell_control-center-results.png"
   
https://bugs.launchpad.net/bugs/1712664/+attachment/4937664/+files/gnome-shell_control-center-results.png

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

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

Title:
  GNOME Control Center results in GNOME Shell Overview are not
  translated in Ubuntu 17.10

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

Bug description:
  GNOME Control Center results in GNOME Shell Overview are untranslated
  on my non-English Ubuntu 17.10 install even though they are fully
  translated in GNOME Control Center itself. See the attached
  screenshot.

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

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

[Desktop-packages] [Bug 1712660] Re: application menu icon in title bar has wrong size

2017-08-23 Thread Philipp

** Attachment added: "buttons positioned on the left side"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1712660/+attachment/4937658/+files/left.png

** Also affects: light-themes (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  New
Status in light-themes package in Ubuntu:
  New

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size.
  See screenshot

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

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

[Desktop-packages] [Bug 1712660] [NEW] application menu icon in title bar has wrong size

2017-08-23 Thread Philipp

Public bug reported:

gnome-terminal application menu icon in the title bar has the wrong size.
See screenshot

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

** Affects: light-themes (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "right.png"
   https://bugs.launchpad.net/bugs/1712660/+attachment/4937657/+files/right.png

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

Title:
  application menu icon in title bar has wrong size

Status in gnome-terminal package in Ubuntu:
  New
Status in light-themes package in Ubuntu:
  New

Bug description:
  gnome-terminal application menu icon in the title bar has the wrong size.
  See screenshot

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

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

[Desktop-packages] [Bug 1710789] Re: chromium does not open downloaded files

2017-08-23 Thread RCV

>I have switched builds for the beta branch to is_component_build=false,
so this bug should go away with the next major chromium update (61).

May i test this package now?

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

Title:
  chromium does not open downloaded files

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I have up to date Ubuntu 17.04. Recently, Chromium stoped to open
  downloaded files.

  If i download and open doc file from chromium, in command line i see
  the following message:

  /usr/lib/libreoffice/program/soffice.bin: relocation error:
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol
  mir_display_config_release, version MIR_CLIENT_0.21 not defined in
  file libmirclient.so.9 with link time reference

  If i download pdf file i see the same message with evince instead of
  libreoffice.

  It looks like more general problem, but I still can open files from
  these two applications or using xdg-open.

  I tried to work with new chromium profile, but i get the same message
  no matter what and files cannot be opened.

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

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

[Desktop-packages] [Bug 1712658] [NEW] Rhythmbox is only partially translated in Ubuntu 17.10

2017-08-23 Thread AsciiWolf

Public bug reported:

Rhythmbox is only partially translated in Ubuntu 17.10, at least in my
(Czech) language, even though it is fully translated on Launchpad. See
the attached screenshot.

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


** Tags: artful l10n

** Attachment added: "rhythmbox.png"
   
https://bugs.launchpad.net/bugs/1712658/+attachment/4937656/+files/rhythmbox.png

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

Title:
  Rhythmbox is only partially translated in Ubuntu 17.10

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Rhythmbox is only partially translated in Ubuntu 17.10, at least in my
  (Czech) language, even though it is fully translated on Launchpad. See
  the attached screenshot.

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

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

[Desktop-packages] [Bug 1712571] Re: xwayland does not support wacom tablets

2017-08-23 Thread Timo Aaltonen

no, 1.20.0 will be released maybe around Nov/Dec, so too late

I'll check the patches if I can find my tablet somewhere..

** Changed in: xorg-server (Ubuntu)
   Status: New => Triaged

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  xwayland does not support wacom tablets

Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  When running a session under Wayland, my Wacom tablet does not work
  properly in applications using xwayland (the cursor moves, but
  clicking does not work).

  This is a known issue that apparently has been fixed in xorg-server
  1.20 branch - see the upstream bug at
  https://bugs.freedesktop.org/show_bug.cgi?id=99411 and also
  https://bugzilla.redhat.com/show_bug.cgi?id=1397898.

  Is xorg-server 1.20 likely to be released in time for Artful or can
  the wacom patches be backported for xwayland?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.3-1ubuntu3
  Uname: Linux 4.13.0-041300rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 20:59:41 2017
  DistUpgraded: 2017-08-17 08:53:31,141 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.12.0-11-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-041300rc6-generic, x86_64: installed
   nvidia-384, 384.59, 4.12.0-11-generic, x86_64: installed
   nvidia-384, 384.59, 4.13.0-041300rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-08-16 (7 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.
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-041300rc6-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7
  Renderer: Software
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to artful on 2017-08-17 (6 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  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: Thu Aug 17 08:57:12 2017
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  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/ubuntu/+source/xorg-server/+bug/1712571/+subscriptions

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

2017-08-23 Thread Till Kamppeter

ajgreeny, so it seems that it is fixed for you now. Marking this as
verified.

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

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is to just ignore the
  failure.

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

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

2017-08-23 Thread ajgreeny

This morning at about 10:30 UTC I updated to cups-2.1.3-4ubuntu0.3 on my 64bit 
Xubuntu-16.04 using kernel 4.4.0-92 and it has so far not stopped running.
My /etc/cups/cupsd.conf has the "WebInterface Yes" entry but so far no problems 
at all, though I had no problems with the cups-2.1.3-4ubuntu0.2 version either 
to which I upgradede with a comment on January 26th.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is to just ignore the
  failure.

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

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

** Changed in: cups (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: cups (Ubuntu Xenial)
 Assignee: (unassigned) => Eric Desrochers (slashd)

** Changed in: cups (Ubuntu Xenial)
 Assignee: Eric Desrochers (slashd) => Till Kamppeter (till-kamppeter)

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is to just ignore the
  failure.

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

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

[Desktop-packages] [Bug 1712223] Re: performing dist-upgrade results in open-vm-tools no longer working

2017-08-23 Thread Jean-Baptiste Lallement

Thank you for confirming it is an issue specific to wayland. I'm
retargeting the bug report.

Don't hesitate to file any new bug you may find.

** Package changed: xorg (Ubuntu) => open-vm-tools (Ubuntu)

** Changed in: open-vm-tools (Ubuntu)
   Importance: Undecided => High

** Changed in: open-vm-tools (Ubuntu)
   Status: Incomplete => Confirmed

** Summary changed:

- performing dist-upgrade results in open-vm-tools no longer working
+ open-vm-tools does not work under wayland

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

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

Title:
  open-vm-tools does not work under wayland

Status in open-vm-tools package in Ubuntu:
  Confirmed

Bug description:
  At first I thought this bug was caused with the recent changes in
  open-vm-tools 10.1.10; however, after restoring my VM to the snapshot
  that had 17.04 and re-performing the dist-upgrade with open-vm-tools
  and open-vm-tools-desktop held at 10.1.5 I am experiencing the same
  issue where VMWare Workstation no longer can interact with display
  resolution detection of the host monitor(s). Multiple monitor support
  is also lost in the update process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 17:09:59 2017
  DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components: 
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful': 
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security': 
{'multiverse', 'restricted', 'universe', 'main'}}
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
   virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-11-30 (264 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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 Aug 21 16:27:55 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver:

[Desktop-packages] [Bug 1076880] Re: network speed incorrectly reported in System Monitor using VPN

2017-08-23 Thread David Young

This bug also affects systems with VLAN interfaces. System Monitor will
add the traffic on the VLAN to the traffic on the physical interface,
again doubling the measured traffic.

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

Title:
  network speed incorrectly reported in System Monitor using VPN

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  looks similar to bug #957617

  When using a VPN and monitoring up and download speeds shown in System
  monitor (ubuntu 12.04), then the indicated speeds are much greater
  than they apparently should be. When VPN is stoped and normal
  connection used, then indicate speeds are as expected.

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

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

[Desktop-packages] [Bug 1611037] Re: Geolocation in firefox doesn't work anymore

2017-08-23 Thread Amr Ibrahim

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

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

Title:
  Geolocation in firefox doesn't work anymore

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Since a couple of days (around beginning of August 2016) the
  geolocation in Firefox doesn't work anymore. I _think_ (but not
  entirely sure) this happened already with Firefox 47.

  That seems to affect all the website using the W3C geolocation, but to test, 
go for example to:
  http://benwerd.com/lab/geo.php

  In the popup, accept to share the location, and the text displayed in the 
location is:
  "The page could not get your location."

  My computer is running Ubuntu 16.04, with Firefox
  48.0+build2-0ubuntu0.16.04.1 .

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

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

[Desktop-packages] [Bug 1133477] Re: [SRU] cut-n-paste move files got stuck forever

2017-08-23 Thread Ferux

yes yes YES YES YES!!

Finally fixed on Ubuntu 16.04 with the proposed package.

All credits to Brian and the other persons who finally took this serious
and got it solved.

Thank you!

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

Title:
  [SRU] cut-n-paste move files got stuck forever

Status in caja package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in pcmanfm package in Ubuntu:
  Invalid
Status in caja source package in Xenial:
  Invalid
Status in gvfs source package in Xenial:
  Fix Committed
Status in nautilus source package in Xenial:
  Invalid
Status in pcmanfm source package in Xenial:
  Invalid

Bug description:
  [Impact]
  Without these fixes, copying any more than a few files in several file 
managers including but not limited to Nautilus and Caja either completely 
freezes up the file manager (if this happens with a Cut and Paste, it destroys 
user data by leaving files half moved) or slows it down to a crawl. These bugs 
are not found when using the mv command in the terminal, which will copy the 
files in a couple of seconds at maximum. This is a nightmare for people who 
want to Cut and Paste a lot of files and who need to do it quickly.

  [Test Case]
  Either find some files that you would be OK losing (or have a backup for) or 
create the files yourself. You can run the following command to generate 1024 
empty 1 MB files (do this in an empty directory, where you have at least 1 GB 
of free space), which is a valid way to reproduce this bug:

  i=1 && while [ $i -lt 1025 ]; do dd if=/dev/zero of=$i bs=4k
  iflag=fullblock,count_bytes count=1M; i=$[$i+1]; done

  (Credit to https://stackoverflow.com/a/11779492/4123313 and
  http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_09_02.html - also,
  neither truncate or fallocate are used because the bug cannot be
  reproduced when using those tools, my theory is that with dd it
  actually writes the zeroes, with those tools, they say they wrote the
  zeroes to the filesystems but it seems they actually didn't (something
  along the lines of that), although I could be wrong)

  If you open Nautilus or Caja, and Cut and Paste these 1024 files
  somewhere else, the transfer will slow to a crawl, and in one instance
  where I tried this with 1024 empty 512 MB files, Nautilus actually
  crashed. This is very different to using mv in the terminal before
  doing it in the file manager, which transfers these files flawlessly.

  Once this fix is applied and I recreate these files, the transfer in
  Nautilus and Caja is almost as fast as using mv (I'd say within a
  second), which is what should happen.

  [Breakdown of the patches and the regression potential for each]
  First, I'd like to thank levien for providing the patch links to fix this. 
Without that, it would have been a bit more work to hunt down which patches are 
applicable.

  lp1133477-metadata-use-sequences-instead-of-lists.patch:
  Patch Description: The metabuilder stores files and data in sorted lists. An 
insertion into a sorted list is done in linear time, which highly affects 
efficiency. In order to fix this, use GSequence instead which does insertion 
and deletion in logarithmic time.

  This patch is in here because it helps with a large amount of files.
  Regardless if the files are 1 MB or 10 GB, the sorting of the files to
  be moved/copied is inefficient. This addresses part of the problem by
  making sure large amount of files can be dealt with efficiently. The
  regression potential for this is low, and the only case that I can see
  where a package would regress is a file manager that depends on (not
  100% on this theory but it's a possibility) monitoring the status of
  the list at a given time, and is incompatible with using GSequence. In
  this case, the package would have something peculiar hardcoded, and
  would most likely have an upstream fix that could be backported
  because this fix is in the gvfs release that is already in 17.04 and
  later (so they should have fixed it already). I can't think of a
  package that does this (from what I can tell, it's not sane code if it
  isn't compatible with this change) but if something does regress, it
  should be trivial to fix.

  lp1133477-metadata-use-queues-instead-of-lists.patch:
  Patch Description: Some of the lists used by the metabuilder have items 
appended to them. Appending to a list is done in linear time and this highly 
affects efficiency. In order to fix this, use GQueue which supports appending 
in constant time.

  This patch is extremely similar in function to the last one, but this
  one addresses items appended to a list instead of files and data in
  sorted lists. As such, the regression potential is similar (low)
  because it would involve a package hardcoding some things that are
  incompatible

[Desktop-packages] [Bug 1712223] Re: performing dist-upgrade results in open-vm-tools no longer working

2017-08-23 Thread Jack Peterson

I can confirm that using X11 as you suggested instead of Wayland is a
viable workaround and that both multi-monitor support and resolution re-
scaling work when moving VMWare Workstation around.

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

Title:
  performing dist-upgrade results in open-vm-tools no longer working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  At first I thought this bug was caused with the recent changes in
  open-vm-tools 10.1.10; however, after restoring my VM to the snapshot
  that had 17.04 and re-performing the dist-upgrade with open-vm-tools
  and open-vm-tools-desktop held at 10.1.5 I am experiencing the same
  issue where VMWare Workstation no longer can interact with display
  resolution detection of the host monitor(s). Multiple monitor support
  is also lost in the update process.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 17:09:59 2017
  DistUpgraded: 2017-08-07 09:05:02,559 DEBUG found components: 
{'artful-updates': {'multiverse', 'restricted', 'universe', 'main'}, 'artful': 
{'multiverse', 'restricted', 'universe', 'main'}, 'artful-security': 
{'multiverse', 'restricted', 'universe', 'main'}}
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.26, 4.10.0-30-generic, x86_64: installed
   virtualbox, 5.1.26, 4.12.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2016-11-30 (264 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=dd284488-2aa1-430d-a510-0527b909f561 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-08-07 (14 days ago)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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 Aug 21 16:27:55 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.19.3-1ubuntu1.1
  xserver.video_driver: vmware

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

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

[Desktop-packages] [Bug 1710993] Re: PulseAudio requirement breaks Firefox on ALSA-only systems after 55.0.1 update

2017-08-23 Thread Tiago Pimenta

Let us see how many time it will remain there until they consider it duplicated:
https://bugzilla.mozilla.org/show_bug.cgi?id=1393105

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

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

Title:
  PulseAudio requirement breaks Firefox on ALSA-only systems after
  55.0.1 update

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  I am on Lubuntu, an ALSA-only system, after update Firefox to version
  55.0.1 it started to ask for PulseAudio when playing media.

  Reference: https://i.imgur.com/5gEnaYv.png

  I have initially stated the bug here: https://askubuntu.com/q/946568
  This bug also happened with Firefox 52 and were fixed on 52.0.2, it seems it 
have had returned: 
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1671273

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

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

[Desktop-packages] [Bug 1697112] Re: package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from other instances

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

** Changed in: sni-qt (Ubuntu)
   Status: New => Confirmed

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

Title:
  package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to
  install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf',
  which is different from other instances of package sni-qt:amd64

Status in sni-qt package in Ubuntu:
  Confirmed

Bug description:
  Showed System error while trying to install OS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sni-qt 0.2.7+15.10.20150729-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun  9 19:23:01 2017
  DuplicateSignature:
   package:sni-qt:0.2.7+15.10.20150729-0ubuntu1
   Unpacking sni-qt:amd64 (0.2.7+16.04.20170217.1-0ubuntu1) over 
(0.2.7+15.10.20150729-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/sni-qt_0.2.7+16.04.20170217.1-0ubuntu1_amd64.deb 
(--unpack):
trying to overwrite shared '/etc/xdg/sni-qt.conf', which is different from 
other instances of package sni-qt:amd64
  ErrorMessage: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
  InstallationDate: Installed on 2015-04-02 (799 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: sni-qt
  Title: package sni-qt 0.2.7+15.10.20150729-0ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/etc/xdg/sni-qt.conf', which is 
different from other instances of package sni-qt:amd64
  UpgradeStatus: Upgraded to xenial on 2016-04-29 (406 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sni-qt/+bug/1697112/+subscriptions

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

[Desktop-packages] [Bug 1712607] [NEW] gnome keyring goes awol after a few logout/logins

2017-08-23 Thread Rachel Greenham

Public bug reported:

First symptom noticed: That *sometimes* after logging in, owncloud-
client would fail to connect to the server, after a delay asking instead
for a password with the message something like (sorry don't have it in
front of me) "keyring service unavailable".

Second symptom, on trying to start Google Chrome (Chromium too), it
would fail to sign in to my Google account for sync, with a long delay
on startup while it gives up on that.

This never happens on the first login session since the last boot. It
may not happen on the second, but usually by the third login, it
happens. I'm not certain of the pattern except it seems always to be
fine in the *first* session.

A reboot seemed to be needed to resolve this. But just now I tried
instead from the commandline:

gnome-keyring-daemon -r -f

I'm sure -d would do too, but I wanted to watch it. Sure enough on
trying to relaunch owncloud-client, I am *then* asked for my password to
unlock the keyring as, it says, it didn't get unlocked when I logged in.
Then both owncloud-client and google-chrome are now able to sign in, and
I see associated messages from the gnome-keyring-daemon in the terminal
where I'm running it.

Presumably the daemon is not being reliably relaunched when needed, on
successive logins to the gnome desktop.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 23 16:38:04 2017
InstallationDate: Installed on 2017-07-30 (23 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to artful on 2017-08-22 (1 days ago)

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

Title:
  gnome keyring goes awol after a few logout/logins

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  First symptom noticed: That *sometimes* after logging in, owncloud-
  client would fail to connect to the server, after a delay asking
  instead for a password with the message something like (sorry don't
  have it in front of me) "keyring service unavailable".

  Second symptom, on trying to start Google Chrome (Chromium too), it
  would fail to sign in to my Google account for sync, with a long delay
  on startup while it gives up on that.

  This never happens on the first login session since the last boot. It
  may not happen on the second, but usually by the third login, it
  happens. I'm not certain of the pattern except it seems always to be
  fine in the *first* session.

  A reboot seemed to be needed to resolve this. But just now I tried
  instead from the commandline:

  gnome-keyring-daemon -r -f

  I'm sure -d would do too, but I wanted to watch it. Sure enough on
  trying to relaunch owncloud-client, I am *then* asked for my password
  to unlock the keyring as, it says, it didn't get unlocked when I
  logged in. Then both owncloud-client and google-chrome are now able to
  sign in, and I see associated messages from the gnome-keyring-daemon
  in the terminal where I'm running it.

  Presumably the daemon is not being reliably relaunched when needed, on
  successive logins to the gnome desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 16:38:04 2017
  InstallationDate: Installed on 2017-07-30 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to artful on 2017-08-22 (1 days ago)

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

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

[Desktop-packages] [Bug 1398898] Re: [armhf] segfaults when trying to save a file

2017-08-23 Thread Bryan Quigley

Fixed in Firefox 35 which should be in all releases long ago.

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

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

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

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

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

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

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

Title:
  [armhf] segfaults when trying to save a file

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in firefox source package in Precise:
  Invalid
Status in firefox source package in Trusty:
  Fix Released
Status in firefox source package in Utopic:
  Won't Fix
Status in firefox source package in Vivid:
  Invalid
Status in iceweasel package in Debian:
  Confirmed

Bug description:
  I reproduced by:

  1) starting firefox on an armhf system
  2) browsing to http://us.archive.ubuntu.com
  3) right clicking on the "folder" image, clicking "Save Image As..."
  4) then selecting a folder. 

  ubuntu@hb06-22:/tmp$ firefox

  (process:23506): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
  Gtk-Message: Failed to load module "canberra-gtk-module"

  (firefox:23506): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
  bus: Failed to execute child process "dbus-launch" (No such file or
  directory)

  ### THIS IS WHERE I SELECT SAVE IMAGE AS ###

  
   1417625318797GMPInstallManager.simpleCheckAndInstall INFOLast 
check was: 1417625319 seconds ago, minimum seconds: 86400
  1417625318798 GMPInstallManager._getURL   INFOUsing url: 
https://aus4.mozilla.org/update/3/GMP/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml
  1417625318800 GMPInstallManager._getURL   INFOUsing url (with 
replacement): 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml
  1417625318805 GMPInstallManager.checkForAddonsINFOsending request 
to: 
https://aus4.mozilla.org/update/3/GMP/33.0/20141013200607/Linux_arm-eabi-gcc3/en-US/release/Linux%203.13.0-37-generic%20(GTK%202.24.23)/canonical/1.0/update.xml

  (firefox:23506): Gtk-WARNING **: Attempting to store changes into 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: Failed to create 
file '/home/ubuntu/.local/share/recently-used.xbel.ECJTPX': No such file or 
directory

  (firefox:23506): Gtk-WARNING **: Attempting to set the permissions of 
`/home/ubuntu/.local/share/recently-used.xbel', but failed: No such file or 
directory
  ubuntu@hb06-22:/tmp$

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

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

** Description changed:

  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0
  
  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏
  
  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups
  
  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.
  
  [Impact]
  
  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/ via
  a web browser fails. People get confused as other access to CUPS
  
  [Testcase]
  
  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via
  
  cupsctl WebInterface=Yes
  
  Now you are able to access the web interface via http://localhost:631/.
  Wait for some minutes without accessing CUPS until the CUPS daemon shuts
  down automatically. Try to open the web interface again and it will not
  work.
  
  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.
  
  [Regression Potential]
  
  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.
+ 
+ [Regression in Pending SRU page]
+ 
+ * Regression in autopkgtest for c2esp (armhf): test log
+ 
+ This autopkgtest seems always fails :
+ 
+ http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf
+ 
+ c2esp [xenial/armhf]
+ 
+ Version   TriggersDateDurationResult
+ 27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
+ 27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
+ 27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
+ 27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻
+ 
+ Additionally look at Till comment :
+ https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129
+ 
+ * Regression in autopkgtest for libreoffice (i386): test log
+ 
+ It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772
+ 
+ ... so until this is fixed upstream in the kernel and backported in an
+ ubuntu kernel, I'm afraid the only option is to just ignore the failure.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

** Description changed:

  This concerns only Xenial (16.04)!
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  
  [Regression Potential]
  
  Regression risk is low, the fix mitigate cups failing to stop/restart on
  upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.
  
  [Regression in Pending SRU page]
  
  * Regression in autopkgtest for c2esp (armhf): test log
  
  This autopkgtest seems always fails :
  
  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf
  
  c2esp [xenial/armhf]
  
  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻
  
  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129
  
+ * Regression in autopkgtest for libreoffice (i386): test log
+ 
+ It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
+ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772
+ 
+ ... so until this is fixed upstream in the kernel and backported in an
+ ubuntu kernel, I'm afraid the only option is to just ignore the failure.
+ 
+ 
  [Other Info]
  
  * The patch is joint effort between xnox and slashd.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This concerns only Xenial (16.04)!

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion:

[Desktop-packages] [Bug 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2017-08-23 Thread Ross Gammon

Just an update for my upgrade. I can't remember exactly what happened
now. But I think that I looked into the emacs issue, and then did
something like "apt-get --fix-broken" or "apt-get --fix-missing". And
once the emacs problem was fixed, I could "apt-get upgrade" & "dist-
upgrade" to continue the upgrade, and the upgrade completed fine.

Sorry about the vagueness, but I thought I would report back that it is
no longer a problem for me.

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

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Triaged
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  Fix Released

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1712019] Re: Driverless printing only prints a blank sheet 17.10

2017-08-23 Thread Till Kamppeter

Thank you for the tests.

This means that the odd resolution (4800x1200 dpi) which got put into
the "Normal" setting of the "cupsPrintQuality" option breaks it (as I
assumed yesterday).

You should be able to work around this if the print dialog of the
application offers a "Print Quality" option where you can set "Draft" or
"High".

I have already posted a upstream bug report on CUPS:

https://github.com/apple/cups/issues/5091
The driverless PPD generator chooses resolutions for cupsPrintQuality settings 
badly

Unfortunately, Mike Sweet, the author of CUPS, is currently on vacation,
so it can take some time until he will read this bug report.

Note that the PPD generator in cups-filters is a near 100% copy of the
one of CUPS. I will look into fixing it there and then proposing a patch
to CUPS.

** Bug watch added: github.com/apple/cups/issues #5091
   https://github.com/apple/cups/issues/5091

** Changed in: cups (Ubuntu)
   Status: Incomplete => Triaged

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

** Changed in: cups-filters (Ubuntu)
   Status: New => Triaged

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Triaged
Status in cups-filters package in Ubuntu:
  Triaged

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

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

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

[Desktop-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

2017-08-23 Thread Nirbhay Choubey

I too got stuck in the spiral.

$ sudo dpkg --remove unity-scope-gdrive
$ sudo dpkg --remove account-plugin-google
$ sudo apt-get -f install

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

  SRU information
  ===

  [Impact] It's not possible to install KDE and Unity in co-existence
  because of several file conflicts: many files under
  /usr/share/accounts/{providers,services}/ are provided by both the
  package "kaccounts-providers" and packages build from the "account-
  plugins" source package, for example 'account-plugin-facebook'.

  [Test case] Install both kaccounts-providers and account-plugin-facebook: 
you'll get file conflicts for /usr/share/accounts/services/facebook-im.service 
and /usr/share/accounts/providers/facebook.provider.
  You might get other conflicts as well, but those are due to bug 1565772 (also 
nominated for SRU).

  [Regression potential] Minimal: the changed packages belong to the
  default KDE installation, and have already landed in Yakkety. Things
  appear to be working fine there: account creation is still possible
  under KDE, even after changing the file paths as per this fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

-- 
Mailing list: https://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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-08-23 Thread Steve Langasek

On Wed, Aug 23, 2017 at 02:54:51PM -, Till Kamppeter wrote:
> About the c2esp regressio mentioned in the description (see also below):
> It seems that c2esp never built/worked on arnhf.  I see this also with
> several other printing-related packages (like cups-filters).  So you can
> safely ignore it.

There are widespread failures to upgrade this package.  We are trying to
publish an SRU, which by definition means we are going to be inducing users
to *upgrade the package*.  Regardless of whether the c2esp package works on
armhf, it is built and the autopkgtest did pass in xenial until August of
last year.  This is not going to be ignored without a very specific reason,
and if the c2esp autopkgtest happens to be exposing this same user-affecting
upgrade failure, then there is definitely no reason to ignore it.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This concerns only Xenial (16.04)!

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

  [Regression Potential]

  Regression risk is low, the fix mitigate cups failing to stop/restart
  on upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.

  [Regression in Pending SRU page]

  * Regression in autopkgtest for c2esp (armhf): test log

  This autopkgtest seems always fails :

  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

  c2esp [xenial/armhf]

  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻

  Additionally look at Till comment :
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129

  * Regression in autopkgtest for libreoffice (i386): test log

  It's a known issue, A regression in the kernel, which breaks libreoffice with 
java enabled on i386 :
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772

  ... so until this is fixed upstream in the kernel and backported in an
  ubuntu kernel, I'm afraid the only option is

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

** Description changed:

  This concerns only Xenial (16.04)!
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  
  [Regression Potential]
  
  Regression risk is low, the fix mitigate cups failing to stop/restart on
  upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.
  
  [Regression in Pending SRU page]
  
  * Regression in autopkgtest for c2esp (armhf): test log
  
  This autopkgtest seems to recurrent, meaning that it always fails :
  
  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf
  
  c2esp [xenial/armhf]
  
  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻
  
+ Additionally look at Till comment :
+ https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/comments/129
+ 
  [Other Info]
  
  * The patch is joint effort between xnox and slashd.

** Description changed:

  This concerns only Xenial (16.04)!
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

** Description changed:

  This concerns only Xenial (16.04)!
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  
  [Regression Potential]
  
  Regression risk is low, the fix mitigate cups failing to stop/restart on
  upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.
  
- Regression found in pending SRU page :
+ [Regression in Pending SRU page]
  
  * Regression in autopkgtest for c2esp (armhf): test log
  
- This autopkgtest seems to always fails :
+ This autopkgtest seems to recurrent, meaning that it always fails :
  
  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf
  
  c2esp [xenial/armhf]
  
  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻
  
  [Other Info]
  
- * The patch is a collaboration between xnox and I, slashd.
+ * The patch is joint effort between xnox and slashd.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This concerns only Xenial (16.04)!

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:

  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for

[Desktop-packages] [Bug 1712595] Re: unity-settings-daemon crashed with signal 5 in _XReply() seemingly without user interaction

2017-08-23 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1306436
   unity-settings-daemon crashed with signal 5 in _XReply()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-settings-daemon crashed with signal 5 in _XReply() seemingly
  without user interaction

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  Some background process must have triggered this.  I was using the
  machine and did not notice anything visibly fail.

  There are a number of similar bugs reported with titles starting
  "unity-settings-daemon crashed with signal 5" but none are for 16.04
  and required no user input.  I expect this will ultimately be marked
  as a duplicate of one of them, I cannot work out which one.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-settings-daemon 15.04.1+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 23 15:22:10 2017
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2015-03-12 (894 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd mock plugdev sambashare sudo 
wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1712595/+subscriptions

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

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-08-23 Thread Till Kamppeter

About the c2esp regressio mentioned in the description (see also below):
It seems that c2esp never built/worked on arnhf. I see this also with several 
other printing-related packages (like cups-filters). So you can safely ignore 
it.

--

Regression found in pending SRU page :

* Regression in autopkgtest for c2esp (armhf): test log

This autopkgtest seems to always fails :

http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf

c2esp [xenial/armhf]

** Description changed:

- This is in xenial-proposed, please block release to -updates accordingly
- :)
+ This concerns only Xenial (16.04)!
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
  
  [Regression Potential]
  
  Regression risk is low, the fix mitigate cups failing to stop/restart on
  upgrade. No source code change, just adding a custom pre-removal
  maintainer script in case of upgrade failure.
  
  Regression found in pending SRU page :
  
  * Regression in autopkgtest for c2esp (armhf): test log
  
  This autopkgtest seems to always fails :
  
  http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf
  
  c2esp [xenial/armhf]
  
  Version   TriggersDateDurationResult
  27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
  27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻
  
  [Other Info]
  
  * The patch is a collaboration between xnox and I, slashd.

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

Title:
  package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new
  pre-removal script returned error exit status 1

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed
Status in cups source package in Yakkety:
  Fix Released
Status in cups source package in Zesty:
  Fix Released

Bug description:
  This concerns only Xenial (16.04)!

  [Impact]
  * fail to upgrade

  [testcase]
  Root cause is believed to be reproducible with:

  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs

[Desktop-packages] [Bug 694211] Re: could not initialize the package information

2017-08-23 Thread Bryan Quigley

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

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

Title:
  could not initialize the  package information

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  'E:Malformed line 53 in source list /etc/apt/sources.list (dist
  parse)'

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

-- 
Mailing list: https://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 1712019] Re: Driverless printing only prints a blank sheet 17.10

2017-08-23 Thread Roderic Jones

I have done these tests. a lot of fiddling with the files was necessary
because they all have to be owned by root to work.

The "old" ppd file produces draft, normal and high printouts as you would
expect.

The new PPD file produces draft and high output but normal just ejects a
blank sheet. This has been the problem.

I have tried fiddling with the print settings printing from chrome but I
van not get any mark on the paper.

Printing from libre Office Write is the same but in the print dialog as
well as the two printers "oldppd" and "newppd" show up. If you select
"oldppd" it prints correctly.

Best wishes

Rod Jones

On 22 August 2017 at 19:08, Till Kamppeter <1712...@bugs.launchpad.net>
wrote:

> First, the kernel has no influence to printing results. All the printing
> logic is happening in user space.
>
> Please do the following tests and tell in which cases you get useful
> printouts (and if so, also tell whether there are quality differences,
> the PPD files are ones which you had attached in comment #2, file.pdf is
> an arbitrary PDF file):
>
> lpadmin -p oldppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P
> EPSON-WF-3620-Series17-04.ppd
> lpadmin -p newppd -E -v ipp://EPSON25B56D.local:631/ipp/print -P
> EPSON_WF_3620_series17-10.ppd
>
> lp -d oldppd -o cupsPrintQuality=Draft file.pdf
> lp -d oldppd -o cupsPrintQuality=Normal file.pdf
> lp -d oldppd -o cupsPrintQuality=High file.pdf
>
> lp -d newppd -o cupsPrintQuality=Draft file.pdf
> lp -d newppd -o cupsPrintQuality=Normal file.pdf
> lp -d newppd -o cupsPrintQuality=High file.pdf
>
> For these tests please also follow the instructions of the section "CUPS
> error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1712019
>
> Title:
>   Driverless printing only prints a blank sheet 17.10
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1712019/+subscriptions
>

-- 
Rod Jones

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Driverless printing works perfectly in Ubuntu 17.04 with my Epson WF 3620. 
Scanning is also perfect.
  I have 17.10 on another SSD and driverless printing was working but recent 
updates have broken this. I reinstalled from the Aug 14th daily build and have 
updated it daily but printing still does not work

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

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

[Desktop-packages] [Bug 1710993] Re: PulseAudio requirement breaks Firefox on ALSA-only systems after 55.0.1 update

2017-08-23 Thread Tiago Pimenta

I am begging them to reconsider the decision, I am very sad about it:

https://support.mozilla.org/pt-BR/questions/1172578

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

Title:
  PulseAudio requirement breaks Firefox on ALSA-only systems after
  55.0.1 update

Status in firefox package in Ubuntu:
  In Progress

Bug description:
  I am on Lubuntu, an ALSA-only system, after update Firefox to version
  55.0.1 it started to ask for PulseAudio when playing media.

  Reference: https://i.imgur.com/5gEnaYv.png

  I have initially stated the bug here: https://askubuntu.com/q/946568
  This bug also happened with Firefox 52 and were fixed on 52.0.2, it seems it 
have had returned: 
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1671273

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

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

[Desktop-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

** Description changed:

  This is in xenial-proposed, please block release to -updates accordingly
  :)
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15
  SourcePackage: cups
  Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.
+ 
+ [Regression Potential]
+ 
+ Regression risk is low, the fix mitigate cups failing to stop/restart on
+ upgrade. No source code change, just adding a customer pre-removal
+ maintainer script in case of upgrade failure.
+ 
+ Regression found in pending SRU page :
+ 
+ * Regression in autopkgtest for c2esp (armhf): test log
+ 
+ This autopkgtest seems to always fails :
+ 
+ http://autopkgtest.ubuntu.com/packages/c/c2esp/xenial/armhf
+ 
+ c2esp [xenial/armhf]
+ 
+ Version   TriggersDateDurationResult  
+ 27-2  cups/2.1.3-4ubuntu0.3   2017-08-23 04:07:44 UTC 2h 50m 13s  
faillog   artifacts   ♻
+ 27-2  cups/2.1.3-4ubuntu0.2   2017-08-14 23:31:50 UTC 2h 50m 11s  
faillog   artifacts   ♻
+ 27-2  cups/2.1.3-4ubuntu0.2   2017-07-17 20:17:10 UTC 2h 50m 52s  
faillog   artifacts   ♻
+ 27-2  cups/2.1.3-4ubuntu0.1   2017-01-20 12:00:41 UTC 2h 49m 29s  
faillog   artifacts   ♻
+ 
+ 
+ [Other Info]
+ 
+ * The patch is a collaboration between xnox and I, slashd.

** Description changed:

  This is in xenial-proposed, please block release to -updates accordingly
  :)
  
  [Impact]
  * fail to upgrade
  
  [testcase]
  Root cause is believed to be reproducible with:
  
  #!/bin/bash
  systemctl stop cups.path cups.service
  rm /var/cache/cups/org.cups.cupsd
  systemctl start cups.path
  touch /var/cache/cups/org.cups.cupsd
  sleep 1
  rm /var/cache/cups/org.cups.cupsd
  sleep 1
  systemctl stop cups.service
  echo $?
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
  
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7

[Desktop-packages] [Bug 1710789] Re: chromium does not open downloaded files

2017-08-23 Thread Olivier Tilloy

I have switched builds for the beta branch to is_component_build=false,
so this bug should go away with the next major chromium update (61).

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

Title:
  chromium does not open downloaded files

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  I have up to date Ubuntu 17.04. Recently, Chromium stoped to open
  downloaded files.

  If i download and open doc file from chromium, in command line i see
  the following message:

  /usr/lib/libreoffice/program/soffice.bin: relocation error:
  /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: symbol
  mir_display_config_release, version MIR_CLIENT_0.21 not defined in
  file libmirclient.so.9 with link time reference

  If i download pdf file i see the same message with evince instead of
  libreoffice.

  It looks like more general problem, but I still can open files from
  these two applications or using xdg-open.

  I tried to work with new chromium profile, but i get the same message
  no matter what and files cannot be opened.

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

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

[Desktop-packages] [Bug 1264115] Re: Gedit hangs while searching in large file

2017-08-23 Thread stamster

This is still present in 16.04 LTS. Disable on-key event, instead make
Search button (enter) to start the actual search after user have
finished string input!

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

Title:
  Gedit hangs while searching in large file

Status in gedit:
  Confirmed
Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  When I did a search in Gedit with a large text file (about 101 KB), the 
editor hangs and used high CPU load. 
  When I shut down the application, a dialog box appears: The Window 
"history.log (/var/log/apt) - gedit" is not respondig. This dialog box is 
attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit 3.10.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 25 14:24:16 2013
  InstallationDate: Installed on 2013-12-20 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131220)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1712587] [NEW] Firefox 55 instantly crashes on Google Maps

2017-08-23 Thread Alistair Buxton

Public bug reported:

To reproduce:

1. Go to http://maps.google.co.uk

Result: Firefox instantly crashes.

I tried disabling hardware acceleration. It didn't make any difference.

This crash is 100% reproducible.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  al 2782 F pulseaudio
 /dev/snd/controlC1:  al 2782 F pulseaudio
 /dev/snd/controlC2:  al 2782 F pulseaudio
 /dev/snd/controlC0:  al 2782 F pulseaudio
BuildID: 20170816210634
Channel: Unavailable
CurrentDesktop: XFCE
Date: Wed Aug 23 14:46:26 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2015-07-12 (773 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
IpRoute:
 default via 192.168.0.1 dev enp0s31f6  proto static  metric 100 
 169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 192.168.0.0/24 dev enp0s31f6  proto kernel  scope link  src 192.168.0.5  
metric 100
IwConfig:
 lono wireless extensions.
 
 enp0s31f6  no wireless extensions.
 
 docker0   no wireless extensions.
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-b982df2a-0748-4395-a586-f88c01170823
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816210634 (In use)
RfKill:
 
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs:
 bp-b982df2a-0748-4395-a586-f88c01170823
 bp-93cc1950-6206-4734-99b7-7cfea1170823
 bp-7dec83a1-282b-4c55-9b8f-3f5690170823
 bp-d61de9e9-55ac-4c4d-8f89-867360170823
 bp-f907228f-d818-4d12-8ff5-cef060170823
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: Default string
dmi.board.name: Z170-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd03/24/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug xenial

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

Title:
  Firefox 55 instantly crashes on Google Maps

Status in firefox package in Ubuntu:
  New

Bug description:
  To reproduce:

  1. Go to http://maps.google.co.uk

  Result: Firefox instantly crashes.

  I tried disabling hardware acceleration. It didn't make any
  difference.

  This crash is 100% reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  al 2782 F pulseaudio
   /dev/snd/controlC1:  al 2782 F pulseaudio
   /dev/snd/controlC2:  al 2782 F pulseaudio
   /dev/snd/controlC0:  al 2782 F pulseaudio
  BuildID: 20170816210634
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Wed Aug 23 14:46:26 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-07-12 (773 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6  proto static  metric 100 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src

[Desktop-packages] [Bug 1133477] Re: [SRU] cut-n-paste move files got stuck forever

2017-08-23 Thread Peter Passchier

Ubuntu 16.04.3 here, bug confirmed. With gvfs from proposed, the bug is
fixed.

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

Title:
  [SRU] cut-n-paste move files got stuck forever

Status in caja package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Invalid
Status in pcmanfm package in Ubuntu:
  Invalid
Status in caja source package in Xenial:
  Invalid
Status in gvfs source package in Xenial:
  Fix Committed
Status in nautilus source package in Xenial:
  Invalid
Status in pcmanfm source package in Xenial:
  Invalid

Bug description:
  [Impact]
  Without these fixes, copying any more than a few files in several file 
managers including but not limited to Nautilus and Caja either completely 
freezes up the file manager (if this happens with a Cut and Paste, it destroys 
user data by leaving files half moved) or slows it down to a crawl. These bugs 
are not found when using the mv command in the terminal, which will copy the 
files in a couple of seconds at maximum. This is a nightmare for people who 
want to Cut and Paste a lot of files and who need to do it quickly.

  [Test Case]
  Either find some files that you would be OK losing (or have a backup for) or 
create the files yourself. You can run the following command to generate 1024 
empty 1 MB files (do this in an empty directory, where you have at least 1 GB 
of free space), which is a valid way to reproduce this bug:

  i=1 && while [ $i -lt 1025 ]; do dd if=/dev/zero of=$i bs=4k
  iflag=fullblock,count_bytes count=1M; i=$[$i+1]; done

  (Credit to https://stackoverflow.com/a/11779492/4123313 and
  http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_09_02.html - also,
  neither truncate or fallocate are used because the bug cannot be
  reproduced when using those tools, my theory is that with dd it
  actually writes the zeroes, with those tools, they say they wrote the
  zeroes to the filesystems but it seems they actually didn't (something
  along the lines of that), although I could be wrong)

  If you open Nautilus or Caja, and Cut and Paste these 1024 files
  somewhere else, the transfer will slow to a crawl, and in one instance
  where I tried this with 1024 empty 512 MB files, Nautilus actually
  crashed. This is very different to using mv in the terminal before
  doing it in the file manager, which transfers these files flawlessly.

  Once this fix is applied and I recreate these files, the transfer in
  Nautilus and Caja is almost as fast as using mv (I'd say within a
  second), which is what should happen.

  [Breakdown of the patches and the regression potential for each]
  First, I'd like to thank levien for providing the patch links to fix this. 
Without that, it would have been a bit more work to hunt down which patches are 
applicable.

  lp1133477-metadata-use-sequences-instead-of-lists.patch:
  Patch Description: The metabuilder stores files and data in sorted lists. An 
insertion into a sorted list is done in linear time, which highly affects 
efficiency. In order to fix this, use GSequence instead which does insertion 
and deletion in logarithmic time.

  This patch is in here because it helps with a large amount of files.
  Regardless if the files are 1 MB or 10 GB, the sorting of the files to
  be moved/copied is inefficient. This addresses part of the problem by
  making sure large amount of files can be dealt with efficiently. The
  regression potential for this is low, and the only case that I can see
  where a package would regress is a file manager that depends on (not
  100% on this theory but it's a possibility) monitoring the status of
  the list at a given time, and is incompatible with using GSequence. In
  this case, the package would have something peculiar hardcoded, and
  would most likely have an upstream fix that could be backported
  because this fix is in the gvfs release that is already in 17.04 and
  later (so they should have fixed it already). I can't think of a
  package that does this (from what I can tell, it's not sane code if it
  isn't compatible with this change) but if something does regress, it
  should be trivial to fix.

  lp1133477-metadata-use-queues-instead-of-lists.patch:
  Patch Description: Some of the lists used by the metabuilder have items 
appended to them. Appending to a list is done in linear time and this highly 
affects efficiency. In order to fix this, use GQueue which supports appending 
in constant time.

  This patch is extremely similar in function to the last one, but this
  one addresses items appended to a list instead of files and data in
  sorted lists. As such, the regression potential is similar (low)
  because it would involve a package hardcoding some things that are
  incompatible with GQueue, and would most likely have an upstream fix
  that could be backported because this fix is in

[Desktop-packages] [Bug 1712571] [NEW] xwayland does not support wacom tablets

2017-08-23 Thread Rocko

Public bug reported:

When running a session under Wayland, my Wacom tablet does not work
properly in applications using xwayland (the cursor moves, but clicking
does not work).

This is a known issue that apparently has been fixed in xorg-server 1.20
branch - see the upstream bug at
https://bugs.freedesktop.org/show_bug.cgi?id=99411 and also
https://bugzilla.redhat.com/show_bug.cgi?id=1397898.

Is xorg-server 1.20 likely to be released in time for Artful or can the
wacom patches be backported for xwayland?

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xwayland 2:1.19.3-1ubuntu3
Uname: Linux 4.13.0-041300rc6-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 23 20:59:41 2017
DistUpgraded: 2017-08-17 08:53:31,141 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.12.0-11-generic, x86_64: installed
 bbswitch, 0.8, 4.13.0-041300rc6-generic, x86_64: installed
 nvidia-384, 384.59, 4.12.0-11-generic, x86_64: installed
 nvidia-384, 384.59, 4.13.0-041300rc6-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:07be]
InstallationDate: Installed on 2017-08-16 (7 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.
MachineType: Dell Inc. XPS 15 9560
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-041300rc6-generic 
root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet 
splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7
Renderer: Software
SourcePackage: xorg-server
UpgradeStatus: Upgraded to artful on 2017-08-17 (6 days ago)
dmi.bios.date: 06/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.4
dmi.board.name: 05FFDN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9560
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170720-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.82-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.0~rc4-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.0~rc4-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
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: Thu Aug 17 08:57:12 2017
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu2

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


** Tags: amd64 apport-bug artful reproducible ubuntu

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

Title:
  xwayland does not support wacom tablets

Status in xorg-server package in Ubuntu:
  New

Bug description:
  When running a session under Wayland, my Wacom tablet does not work
  properly in applications using xwayland (the cursor moves, but
  clicking does not work).

  This is a known issue that apparently has been fixed in xorg-server
  1.20 branch - see the upstream bug at
  https://bugs.freedesktop.org/show_bug.cgi?id=99411 and also
  https://bugzilla.redhat.com/show_bug.cgi?id=1397898.

  Is xorg-server 1.20 likely to be released in time for Artful or can
  the wacom patches be backported for xwayland?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xwayland 2:1.19.3-1ubuntu3
  Uname: Linux 4.13.0-041300rc6-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'

[Desktop-packages] [Bug 1710100] Re: XDG_DATA_DIR doesn't include /usr/share/$DESKTOP_SESSION under wayland

2017-08-23 Thread Iain Lane

** Changed in: gnome-session (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

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

Title:
  XDG_DATA_DIR doesn't include /usr/share/$DESKTOP_SESSION under wayland

Status in gnome-session package in Ubuntu:
  In Progress

Bug description:
  That's done by an Xsession.d script under X, we need an equivalent
  under wayland

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

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

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

Is there a fix required for zesty as well?

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

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Desktop-packages] [Bug 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()

Hello MrRomanze, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1539209

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_set_volume_cb() from pa_source_process_msg()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Zesty:
  New
Status in pulseaudio source package in Artful:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
     headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
     older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Original Description]

  Appears randomly.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:7.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   potato12883 F...m pulseaudio
   /dev/snd/controlC0:  potato12883 F pulseaudio
   /dev/snd/controlC1:  potato12883 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 28 22:16:03 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-17 (11 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   LANGUAGE=ru
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so
   ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so
   ?? () from /usr/lib/libpulsecore-7.1.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113

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

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

[Desktop-packages] [Bug 1562817] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_write_volume_cb() from source_set_port_cb() from pa_source_process_msg() from source_proce

Hello TBS, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1562817

Title:
  pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from
  source_write_volume_cb() from source_set_port_cb() from
  pa_source_process_msg() from source_process_msg()

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/3bb5044276ea358334e8e662559a1cbd45240cd9

  ---

  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Find some headphones and/or microphone. Ensure you do not wear the
 headphones during the test as it may be loud.
  2. Set audio output/input volumes to maximum.
  3. Unplug and replug the headphones/microphone.
  4. Check that that pulseaudio process is still running, with a start time
 older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would be 
loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  This error is there when i get back to the computer after a while of
  no use, and at login after restart. haven't seen this error while the
  system is "active"/in use.

  I have been unable to provoke the error to come.

  I'm not sure it is related, but when i plug in a headset, the audio volume 
goes through the roof, and a loud (painfully so) scratching sound is coming 
from the headset until i press Vol+. Vol- does nothing till i have pressed up 
at least once.
  But the bug report thing does not pop up when the sound issue is there.

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  pulseaudio:
    Installed: 1:8.0-0ubuntu2
    Candidate: 1:8.0-0ubuntu2
    Version table:
   *** 1:8.0-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tbs   22776 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Mon Mar 28 12:39:45 2016
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2016-01-14 (73 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
   pa_source_process_msg () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so
   ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so
  Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
  UpgradeStatus: Upgraded to xenial on 2016-03-19 (8 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev root sambashare sudo 
vboxusers
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ETA3WW (2.63 )

[Desktop-packages] [Bug 1672171] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from profile_new_connection() from profile_handler()

Hello bikram, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1672171

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from profile_new_connection()
  from profile_handler() from _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  Bluetooth device keep disconnect and audio output tab is empty

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bikram14994 F pulseaudio
   /dev/snd/controlC0:  bikram14994 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: Unity:Unity7
  Date: Sun Mar 12 21:52:24 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_bluetooth_transport_set_state () from 
/usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /usr/lib/pulse-10.0/modules/libbluez5-util.so
   ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so
  Title: pulseaudio crashed with SIGABRT in pa_bluetooth_transport_set_state()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0Y004V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron3437:pvrNotSpecified:rvnDellInc.:rn0Y004V:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1690028] Re: pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_hand

Hello errors.ubuntu.com, or anyone else affected,

Accepted pulseaudio into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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!

** Also affects: pulseaudio (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-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/1690028

Title:
  pulseaudio crashed with SIGABRT in device_start_waiting_for_profiles()
  from pa_bluetooth_transport_set_state() from
  endpoint_set_configuration() from endpoint_handler() from
  _dbus_object_tree_dispatch_and_unlock()

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  pulseaudio daemon crashes, interrupting sound output/input.

  [Test Case]
  Theoretical test case (crash does not happen for all users):
  1. Get a Bluetooth audio device capable of multiple profiles (e.g. high 
 fidelity A2DP and the lower quality headset profiles).
  2. Pair it with your machine and select the device in sound settings.
  3. Turn the Bluetooth audio device off and on again, making sure it is 
 set to active if not automatically so.
  4. Select the device in sound settings.
  5. Check that that pulseaudio process is still running, with a start 
 time older than when you began this test case.

  [Regression Potential]
  Low. This SRU affects the pulseaudio daemon only so the worst case would 
  be loss of sound output/input. The same patches have been released to
  17.10 for a month already and zero regressions of the crashes have
  occurred worldwide since then.

  [Other Info]
  Debdiff patch is attached to the most prolific bug 1539209.

  [Original Description]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:10.0-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/5a76b9eca937daf6dc05fd32a35fa50e58ccf8f5 
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/pulseaudio/+bug/1690028/+subscriptions

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

[Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11

2017-08-23 Thread Timo Jyrinki

A fix might be coming in some months' time to the upstream kernel.

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

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

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Desktop-packages] [Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04

2017-08-23 Thread Ivo Straka

For reference, a couple of users have been experiencing the same issue
on HP ProLiant MicroServer Gen8, which use Matrox MGA G200EH, the
original culprit that caused the module mgag200 to be excluded from the
kernel years ago.

https://community.hpe.com/t5/ProLiant-Servers-Netservers/HP-ProLiant-
Gen8-with-Ubuntu-16-and-no-monitor-using-iLO-remote/m-p/6972709

In the linked topic, I put together a step-by-step walkthrough through
installing the mgag200 module for Ubuntu or Ubuntu-based distros like
Mint. Some users might find it helpful.

Unfortunately, only one novice user tried this on HP Gen8 and apparently
it did not work. I am not sure whether the mgag200 module just does not
work with G200EH yet or whether there was some mistake made in the
approach either by me or the user. It would be very helpful for someone
to test this with this specific chip and report in more detail.

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

Title:
  matrox g200eR2 is unclaimed in 14.04

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  On a certified Dell PowerEdge T620 server
  (http://www.ubuntu.com/certification/hardware/201207-11426/)

  The matrox video card is not recognised:
  lspci | grep VGA
  0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2

  lshw -C display
*-display UNCLAIMED 
 description: VGA compatible controller
 product: G200eR2
 vendor: Matrox Electronics Systems Ltd.
 physical id: 0
 bus info: pci@:0a:00.0
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: pm vga_controller bus_master cap_list
 configuration: latency=64 maxlatency=32 mingnt=16
 resources: memory:d800-d8ff memory:deffc000-deff 
memory:de00-de7f

  Thus xserver is not hardver accelerated.

  Also /dev/dri and /dev/dri/card0 is missing.

  kernel module mga is not loaded, although if i manually load by modprobe it 
works fine
  modprobe mga
  lsmod | grep mga
  mga40811  0 
  drm   302817  1 mga

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

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

[Desktop-packages] [Bug 1712544] [NEW] New release 384.69

2017-08-23 Thread Cristian Aravena Romero

Public bug reported:

Hello,

http://www.nvidia.com/Download/driverResults.aspx/123103/en-us

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-current (not installed)
Uname: Linux 4.13.0-041300rc6-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Aug 23 08:25:26 2017
InstallationDate: Installed on 2017-07-05 (48 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: nvidia-graphics-drivers-304
UpgradeStatus: Upgraded to artful on 2017-07-05 (48 days ago)

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


** Tags: amd64 apport-bug artful upgrade-software-version

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

Title:
  New release 384.69

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

Bug description:
  Hello,

  http://www.nvidia.com/Download/driverResults.aspx/123103/en-us

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nvidia-current (not installed)
  Uname: Linux 4.13.0-041300rc6-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug 23 08:25:26 2017
  InstallationDate: Installed on 2017-07-05 (48 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nvidia-graphics-drivers-304
  UpgradeStatus: Upgraded to artful on 2017-07-05 (48 days ago)

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

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

[Desktop-packages] [Bug 1703110] Re: notes doesn't delete only if empty

2017-08-23 Thread Alberts Muktupāvels

Roland, that is different bug. Text selection works, but there are
problems with colours... If I remember correctly then selection colour
is same as sticky notes background.

I have fixed this in gnome-applets and fix will be available in 3.26
release. Unfortunately I think that this fix is not something that I
would backport to older releases as there might be new regressions that
I have not noticed.

Commits that should fix this:
https://git.gnome.org/browse/gnome-applets/commit/?id=141d03c861e988b680d93c445c43cf6d528cf02d
https://git.gnome.org/browse/gnome-applets/commit/?id=a48212eb3af54d64b75eeadfe29f84d66074c76a

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

Title:
  notes doesn't delete only if empty

Status in gnome-applets package in Ubuntu:
  Fix Released
Status in gnome-applets source package in Zesty:
  Fix Released

Bug description:
  [Impact]

  Unnesessary work for the user as he is forced to clear the note from
  text in order to delete it. It makes it more difficult that selecting
  text isn't possible with mouse.

  [Test Case]

  - Write anything in a note
  - Try to select text in a note
  - Try to delete it with 'x' or with 'delete notes' menu item

  [Proposed Fix]

  The fix is a backport of three upstream commits:
  - https://git.gnome.org/browse/gnome-applets/commit/?id=85041d6567c78b4a 
“sticky-notes: make sure that notes are really saved”
  - https://git.gnome.org/browse/gnome-applets/commit/?id=0c4e0c4fed0c61bf 
“sticky-notes: fix path to resource file for delete dialog”
  - https://git.gnome.org/browse/gnome-applets/commit/?id=e189ba213c0f8db8
  “sticky-notes: fix text selection”

  [Regression Potential]

  The fix definitely improves the Sticky Notes applet because without
  ability to save notes that applet is mostly unusable. It does not
  touch other applets so no regression expected there.

  [Other Info]

  System configuration:

   roland@roland-Lenovo-ideapad-110-15I
  `:+ss+:`   

    -+ssyy+- OS: Ubuntu 17.04 x86_64
  .ossdMMMNyo.   Model: 80T7 Lenovo ideapad 
110-15IBR
     /ssshdmmNNmmyNhss/  Kernel: 4.10.0-26-generic
    +shmydMMMNy+ Uptime: 4 hours, 45 mins
   /hNMMMyhhhmNMMMNh/Packages: 2360
  .dMMMNhsshNMMMd.   Shell: bash 4.4.7
  +hhhyNMMNyyNMMMysss+   Resolution: 1366x768
  ossyNMMMNyMMhsshmmmhssso   DE: GNOME-Flashback:GNOME
  ossyNMMMNyMMhsshmmmhssso   WM: Compiz
  +hhhyNMMNyyNMMMysss+   WM Theme: Adwaita
  .dMMMNhsshNMMMd.   Theme: Adwaita [GTK2/3]
   /hNMMMyhhhdNMMMNh/Icons: Ubuntu-mono-light [GTK2/3]
    +sdmydy+ Terminal: gnome-terminal
     /ssshdmmyNhss/  CPU: Intel Pentium N3710 (4) @ 
2.5GH
  .ossdMMMNyo.   GPU: Intel HD Graphics 405
    -+syyy+- Memory: 1674MiB / 3862MiB
  `:+ss+:`
  .-/+oooo+/-.

  Stickynotes version: 3.22.0

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

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

[Desktop-packages] [Bug 1712524] Re: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all

2017-08-23 Thread Naeil ZOUEIDI

Hello, Thanks for filing the bug, could you please attach a verbose log
for PluseAudio: https://wiki.ubuntu.com/PulseAudio/Log

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

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

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No sounds work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asgeir 1383 F pulseaudio
asgeir 4491 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Aug 23 11:51:02 2017
  InstallationDate: Installed on 2017-08-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asgeir 1383 F pulseaudio
asgeir 4491 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UA
  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.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX430UA
  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/1712524/+subscriptions

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

[Desktop-packages] [Bug 1712524] Re: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all

2017-08-23 Thread Asgeir Nilsen

I did someting, and it works now! :)

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

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

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No sounds work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asgeir 1383 F pulseaudio
asgeir 4491 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Aug 23 11:51:02 2017
  InstallationDate: Installed on 2017-08-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asgeir 1383 F pulseaudio
asgeir 4491 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UA
  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.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX430UA
  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/1712524/+subscriptions

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

[Desktop-packages] [Bug 1712528] Re: GNOME Software is slow to start up on first launch

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

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

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

Title:
  GNOME Software is slow to start up on first launch

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On an up to date Ubuntu Artful system with nothing running, GNOME
  Software takes between 15 and 20 seconds to be usable. This feels
  incredibly slow.

  I timed it on my laptop and recorded it here:-
  https://www.youtube.com/watch?v=gxvn_RyJ46o

  I had nothing else running. Laptop is an i7 with 8GB RAM and SSD for
  storage. I would expect G-S to launch a lot quicker on this setup.
  Especially given launch speed was one of the reasons users were given
  as to why we switched away from the previous Ubuntu Software Center to
  G-S in the first place.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.24.3-0ubuntu7
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 10:53:50 2017
  InstallationDate: Installed on 2017-08-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.24.3-0ubuntu7
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1711482] Re: Firefox shows white screen of death

2017-08-23 Thread shemgp

Fix: go to about:config and enable gfx.xrender.enabled

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

Title:
  Firefox shows white screen of death

Status in firefox package in Ubuntu:
  New

Bug description:
  Firefox 55 & 56 shows white screen of death (no contents, just white
  screen) after a while of being used in Ubuntu GNOME.  To show the bug
  more quickly try refreshing gnome-shell (ALT-F2 r) while Firefox is
  opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 55.0.2+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC2D0p:   shemgp24833 F...m pulseaudio
   /dev/snd/controlC2:  shemgp24833 F pulseaudio
   /dev/snd/controlC1:  shemgp24833 F pulseaudio
   /dev/snd/controlC0:  shemgp24833 F pulseaudio
  BuildID: 20170816210634
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Fri Aug 18 09:55:10 2017
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePlugins: Shockwave Flash - 
/usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so 
(browser-plugin-freshplayer-pepperflash)
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  MostRecentCrashID: bp-c408a251-b0e4-488d-a7a6-6676b1170814
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=55.0.2/20170816210634 (In use)
   Profile1 - LastVersion=44.0a2/20151214004008 (Out of date)
  RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 
0.3.6-1~webupd8~xenial6
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V11.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68MA-ED55 (MS-7676)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV11.1:bd01/09/2013:svnMSI:pnMS-7676:pvr2.0:rvnMSI:rnZ68MA-ED55(MS-7676):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7676
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1712528] [NEW] GNOME Software is slow to start up on first launch

2017-08-23 Thread Alan Pope  濾

Public bug reported:

On an up to date Ubuntu Artful system with nothing running, GNOME
Software takes between 15 and 20 seconds to be usable. This feels
incredibly slow.

I timed it on my laptop and recorded it here:-
https://www.youtube.com/watch?v=gxvn_RyJ46o

I had nothing else running. Laptop is an i7 with 8GB RAM and SSD for
storage. I would expect G-S to launch a lot quicker on this setup.
Especially given launch speed was one of the reasons users were given as
to why we switched away from the previous Ubuntu Software Center to G-S
in the first place.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-software 3.24.3-0ubuntu7
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 23 10:53:50 2017
InstallationDate: Installed on 2017-08-02 (20 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.24.3-0ubuntu7
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  GNOME Software is slow to start up on first launch

Status in gnome-software package in Ubuntu:
  New

Bug description:
  On an up to date Ubuntu Artful system with nothing running, GNOME
  Software takes between 15 and 20 seconds to be usable. This feels
  incredibly slow.

  I timed it on my laptop and recorded it here:-
  https://www.youtube.com/watch?v=gxvn_RyJ46o

  I had nothing else running. Laptop is an i7 with 8GB RAM and SSD for
  storage. I would expect G-S to launch a lot quicker on this setup.
  Especially given launch speed was one of the reasons users were given
  as to why we switched away from the previous Ubuntu Software Center to
  G-S in the first place.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.24.3-0ubuntu7
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 23 10:53:50 2017
  InstallationDate: Installed on 2017-08-02 (20 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.24.3-0ubuntu7
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2017-08-23 Thread Asgeir Nilsen

Public bug reported:

No sounds work

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  asgeir 1383 F pulseaudio
  asgeir 4491 F alsamixer
CurrentDesktop: Unity
Date: Wed Aug 23 11:51:02 2017
InstallationDate: Installed on 2017-08-17 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  asgeir 1383 F pulseaudio
  asgeir 4491 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX430UA.201
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX430UA
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.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX430UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

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

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

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sounds work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asgeir 1383 F pulseaudio
asgeir 4491 F alsamixer
  CurrentDesktop: Unity
  Date: Wed Aug 23 11:51:02 2017
  InstallationDate: Installed on 2017-08-17 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asgeir 1383 F pulseaudio
asgeir 4491 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UA
  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.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX430UA
  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/1712524/+subscriptions

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

[Desktop-packages] [Bug 1712520] [NEW] [17.04][gnome] screen hanged after meld launched via terminal was put to sleep by C-z: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed

2017-08-23 Thread Dmitrii Shcherbakov

Public bug reported:

Surprisingly, when I launched meld as a difftool and later suspended it
my session got frozen: my mouse was moving but clicks and keyboard
presses did not have any effect, there was an empty rectangle on my
screen on top of one of the windows. The only thing I could do was to
switch to a different VT and take a look at what's going on.


Actions:

git difftool master tests/basic_deployment.py

This message is displayed because 'diff.tool' is not configured.
See 'git difftool --tool-help' or 'git help config' for more details.
'git difftool' will now attempt to use one of the following tools:
meld opendiff kdiff3 tkdiff xxdiff kompare gvimdiff diffuse diffmerge ecmerge 
p4merge araxis bc codecompare emerge vimdiff

Viewing (1/1): 'tests/basic_deployment.py'
Launch 'meld' [Y/n]? y
^Z
[1]  + 16839 suspended  git difftool master tests/basic_deployment.py


lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty


dpkg -l 'gnome-session'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   
  ArchitectureDescription
+++-=-===-===-
ii  gnome-session 3.24.0-0ubuntu1   
  amd64   GNOME Session Manager - GNOME 3 
session


➜  ~ dpkg -l 'libgtk*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version   
  ArchitectureDescription
+++-=-===-===-
ii  libgtk-3-0:amd64  3.22.11-0ubuntu3  
  amd64   GTK+ graphical user interface library
ii  libgtk-3-bin  3.22.11-0ubuntu3  
  amd64   programs for the GTK+ graphical user 
interface library
ii  libgtk-3-common   3.22.11-0ubuntu3  
  all common files for the GTK+ graphical 
user interface library
un  libgtk-vnc-1.0-0  
(no description available)
ii  libgtk-vnc-2.0-0:amd640.6.0-3   
  amd64   VNC viewer widget for GTK+3 (runtime 
libraries)
ii  libgtk2-perl  2:1.2499-1
  amd64   Perl interface to the 2.x series of 
the Gimp Toolkit library
un  libgtk2-perl-doc  
(no description available)
ii  libgtk2.0-0:amd64 2.24.31-1ubuntu1.1
  amd64   GTK+ graphical user interface library
ii  libgtk2.0-bin 2.24.31-1ubuntu1.1
  amd64   programs for the GTK+ graphical user 
interface library
ii  libgtk2.0-common  2.24.31-1ubuntu1.1
  all common files for the GTK+ graphical 
user interface library
ii  libgtkglext1:amd641.2.0-6   
  amd64   OpenGL Extension to GTK+ (shared 
libraries)
un  libgtkmm-2.4-1c2a 
(no description available)
ii  libgtkmm-2.4-1v5:amd641:2.24.5-1
  amd64   C++ wrappers for GTK+ (shared 
libraries)
un  libgtkmm-3.0-1
(no description available)
ii  libgtkmm-3.0-1v5:amd643.22.0-1  
  amd64   C++ wrappers for GTK+ (shared 
libraries)
ii  libgtksourceview-3.0-1:amd64  3.24.0-0ubuntu1   
  amd64   shared libraries for the GTK+ syntax 
highlighting widget
ii

[Desktop-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

2017-08-23 Thread Colin Law

I can confirm that for me removing /etc/resolv.conf and replacing it
with a link to stub-resolv.conf using

sudo ln -s /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

and rebooting (probably I could just have restarted the appropriate
service) restores DNS functionality.

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

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Confirmed
Status in netcfg package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Desktop-packages] [Bug 982307] Re: unity shows sometimes the desktop on desktop unlock dialog