[Desktop-packages] [Bug 1656532] Re: package flashplugin-installer 24.0.0.194ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before att

[Launchpad Bug Tracker]

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

** Changed in: flashplugin-nonfree (Ubuntu)
   Status: New => Confirmed

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

Title:
  package flashplugin-installer 24.0.0.194ubuntu0.16.04.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  none

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: flashplugin-installer 24.0.0.194ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Fri Jan 13 15:25:21 2017
  DuplicateSignature:
   package:flashplugin-installer:24.0.0.194ubuntu0.16.04.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package flashplugin-installer (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-11-29 (46 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-installer 24.0.0.194ubuntu0.16.04.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1656532/+subscriptions

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

[Desktop-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu

[Chris Cheney]

reply #48

Yes packaged version in main archive, using Ubuntu Mate 17.10 now and
its still not showing the photos mount in Caja (like nautilus). I can
see the Documents mount though.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

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

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

[Desktop-packages] [Bug 1720551] Re: Evince show this text when I try to open a PDF: Failed to load backend for 'application/pdf': libtiff.so.5

[Launchpad Bug Tracker]

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

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

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

Title:
  Evince show this text when I try to open a PDF: Failed to load backend
  for 'application/pdf': libtiff.so.5

Status in evince package in Ubuntu:
  Expired

Bug description:
  Recently I notice I can't open any PDF. I've tried with Okular, Evince
  and Quick PDF View. All of them mark an error as I try to open any
  PDF.

  Evince show this text when I try to open a PDF: Failed to load backend
  for 'application/pdf': libtiff.so.5

  I'm using Ubuntu 16.04 LTS in 32 bits

  I've already checked that libtiff5 is installed.

  f: /usr/lib/i386-linux-gnu/libtiff.so.5
  Drwxr-xr-x root  root  / 
  drwxr-xr-x root  root   usr 
  drwxr-xr-x root  root   lib 
  drwxr-xr-x root  root   i386-linux-gnu 
  srwxrw-r-T 138742031 1300990212 libtiff.so.5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Sep 30 10:26:10 2017
  InstallationDate: Installed on 2015-05-26 (857 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738515] [NEW] [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at all after plugging in headphones

[Paul Williams]

Public bug reported:

Sound worked before, but after plugging in headphones, sound does not work 
through either headphones or internal speakers. Sound continues not to work 
after unplugging headphones.
I tried:
1. killall pulseaudio; rm -r ~/.config/pulse/* ; rm -r ~/.pulse*
2. wait 10 seconds 
3. reboot

Then sound worked in internal speakers, but when I plugged in
headphones, I got the same result. I tested the sound using "Test
Speakers" in Settings, and by playing youtube videos in Firefox.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
 /dev/snd/controlC0:  paul   1374 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 22:15:26 2017
InstallationDate: Installed on 2017-12-08 (7 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
 /dev/snd/controlC0:  gdm1055 F pulseaudio
  paul   1374 F pulseaudio
Symptom_Jack: Black Speaker, Internal
Symptom_Type: No sound at all
Title: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 0WVDX2
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd08/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at
  all after plugging in headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound worked before, but after plugging in headphones, sound does not work 
through either headphones or internal speakers. Sound continues not to work 
after unplugging headphones.
  I tried:
  1. killall pulseaudio; rm -r ~/.config/pulse/* ; rm -r ~/.pulse*
  2. wait 10 seconds 
  3. reboot

  Then sound worked in internal speakers, but when I plugged in
  headphones, I got the same result. I tested the sound using "Test
  Speakers" in Settings, and by playing youtube videos in Firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
   /dev/snd/controlC0:  paul   1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 22:15:26 2017
  InstallationDate: Installed on 2017-12-08 (7 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   paul   1374 F...m pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
paul   1374 F pulseaudio
  Symptom_Jack: Black Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 5510, Realtek ALC3266, Black Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0WVDX2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd08/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0WVDX2:rvrA03:cvnDellInc.:ct9:cvr:
  dmi.product.family: 

[Desktop-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[José Manuel]

I experienced this bug too. #2 fixes the problem but also removes
plasma-pa. When plasma-pa is reinstalled it breaks pulseaudio again.

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1089131] Re: Stat errors on locked (but excluded) files

[Patricio]

Is this updated going to be released for 16.04?

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

Title:
  Stat errors on locked (but excluded) files

Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in duplicity source package in Zesty:
  Fix Released

Bug description:
  Each time that I backup using duplicity (duply, actually) I receive
  errors about files that are locked, even though these files are in my
  exclude list.

  I understand that this is a known bug:
  http://lists.gnu.org/archive/html/duplicity-talk/2012-10/msg00020.html
  https://answers.launchpad.net/duplicity/+question/169980

  I would quite like to get rid of these errors, as they are confusing.
  Note that, while these are counted in the "Errors" number of the
  backup statistics, they do not seem to change the return value of
  duplicity and do not therefore affect the ability to use check_call
  from another Python script.

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

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

[Desktop-packages] [Bug 1710370] Re: Cheese crashes on launch in Ubuntu 17.10 if no camera device is present

[Gunnar Hjalmarsson]

This may be a long shot, but I encountered another problem on 17.10 with
cheese: It starts with the message "There was an error playing video
from the webcam".

Upgrading to version 1.12.6-1 of the libv4l-0 and libv4lconvert0
packages (currently in bionic) fixed that problem. If you want to test,
they are available in this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/v4l-utils

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

Title:
  Cheese crashes on launch in Ubuntu 17.10 if no camera device is
  present

Status in Cheese:
  Confirmed
Status in cheese package in Ubuntu:
  Triaged

Bug description:
  Cheese crashes on launch in Ubuntu 17.10 if the computer does not have
  any camera device connected.

  
  (cheese:3620): cheese-CRITICAL **: cheese_camera_device_get_name: assertion 
'CHEESE_IS_CAMERA_DEVICE (device)' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_new_string: assertion
  'string != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value
  != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_schema_key_type_check:
  assertion 'value != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_get_type_string: assertion
  'value != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_set_value: key
  'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of
  type '(null)' was given

  (cheese:3620): GLib-CRITICAL **: g_variant_unref: assertion 'value !=
  NULL' failed

  ** (cheese:3620): CRITICAL **:
  cheese_preferences_dialog_setup_resolutions_for_device: assertion
  'device != NULL' failed

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

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

[Desktop-packages] [Bug 1738503] [NEW] Cannot Install SNAPS from Gnome-Software Bionic

[Stephen Allen]

Public bug reported:

Error captured in attached Screengrab. I don't recall making any
changes, how would I fix this locally?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.26.3-2ubuntu1
ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
Uname: Linux 4.14.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 15 18:36:40 2017
InstallationDate: Installed on 2017-09-25 (81 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.26.3-2ubuntu1
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.26.3-2ubuntu1
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic gnome-software wayland-session

** Attachment added: "Screengrab of error message when attempting to install 
from Snap-store"
   
https://bugs.launchpad.net/bugs/1738503/+attachment/5023244/+files/Screenshot-20171215183531-1126x844.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/1738503

Title:
  Cannot Install SNAPS from Gnome-Software Bionic

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Error captured in attached Screengrab. I don't recall making any
  changes, how would I fix this locally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 15 18:36:40 2017
  InstallationDate: Installed on 2017-09-25 (81 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.26.3-2ubuntu1
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  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/1738503/+subscriptions

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

[Desktop-packages] [Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subpr

[Adam Williamson]

BTW, for your Apport folks - I'm currently unpicking rather a mess
caused by our equivalent tool (abrt) considering many crashes that run
through a particular codepath in GNOME Shell as duplicates when they are
not in fact duplicates at all. See
https://bugzilla.redhat.com/show_bug.cgi?id=1509086 for more details on
that. You might wanna check if the same thing is affecting Apport in any
way.

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

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

Title:
  gnome-shell crashed with SIGTRAP in object_instance_finalize from
  js::Class::doFinalize ["Finalizing proxy for an object that's
  scheduled to be unrooted: Gio.Subprocess\n"]

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  Logged in with one new user, switched to login under another account.
  Was logged in for a few moments then got kicked out - session crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct  2 10:39:27 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-08-02 (60 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1720768] Re: gnome-shell crashed with SIGTRAP in object_instance_finalize from js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be unrooted: Gio.Subpr

[Adam Williamson]

We have several reports of the same crash message ("Finalizing proxy for
an object that's scheduled to be unrooted: Gio.Subprocess") in Fedora:

https://bugzilla.redhat.com/show_bug.cgi?id=1466948
https://bugzilla.redhat.com/show_bug.cgi?id=1517479
https://bugzilla.redhat.com/show_bug.cgi?id=1514732
https://bugzilla.redhat.com/show_bug.cgi?id=1522921
https://bugzilla.redhat.com/show_bug.cgi?id=1523323

at least. Not sure if they all have the same underlying cause. One
report mentions the Easy Screen Cast extension, and also claims to have
solved the problem by disabling pipewire.service .

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

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

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

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

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

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

Title:
  gnome-shell crashed with SIGTRAP in object_instance_finalize from
  js::Class::doFinalize ["Finalizing proxy for an object that's
  scheduled to be unrooted: Gio.Subprocess\n"]

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  Logged in with one new user, switched to login under another account.
  Was logged in for a few moments then got kicked out - session crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Oct  2 10:39:27 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2017-08-02 (60 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 799546] Re: RE: Case: 8737174858

[Stefano Dall'Agata]

U.S.  Department of Justice
Federal Bureau  of Investigation
Internet Crime Investigation  Center/Cyber  Division
FBI  - Minneapolis  Suite 3213
115 Washington Avenue,  North
MN 55375
Telephone: (888) 348-1766
Fax: (888) 348-1766

November 16, 2017

RE: Case #:  8777174342

The IPregistered on your name was  referred to our ICC Center (IC3)  
multiple times as  being a  possible victim of federal cyber crime.
We believe that your IP address was used to commit several computer  crimes. 
This investigation covers the  time period from  September  4, 2017 to the 
present  date.
We   appreciate  your immediate  assistance  . Please contact  us immediately , 
 at phone number listed above.

Respectfully, Sam Harris
Internet Crime Investigation Center
Minneapolis  Suite 3119
114  Washington Avenue, East
MN 55693
Telephone: (888) 348-1766
Fax: (888) 348-1766


-

Les informations contenues dans ce site sont à titre d'actualité
seulement . L'information est touffue par US et bien que nous nous
efforcions de maintenir les déclarations habitué et correctes , nous ne
faisons aucune notion ou garantie d'aucune sorte , expresse ou inexprimé
, sur l'exhaustivité , l'exactitude , la permanence , la pertinence ou
la délai de validité du site ou les déclarations , kits , prestations ou
graphismes associés textes dans le contenu du site Web à quelque but que
ce soit . Toute cession que vous accordez à ces précisions est donc
parcimonieusement à toutes vos risques et périls .

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

Title:
  Unable to find CD Metadata from the net when I insert an audio CD to
  import

Status in banshee package in Ubuntu:
  Expired

Bug description:
  Binary package hint: banshee

  When I put in an audio CD to ripp the music to MP3, Banshee fails to
  find the metadata for the CD, which makes importing a CD big pain.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: banshee 2.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  Architecture: amd64
  Date: Sun Jun 19 18:52:23 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 242533] Re: weather applet beaufort scale should use descriptions and not numbers.

[Bug Watch Updater]

** Changed in: libgweather
   Status: New => Won't Fix

** Changed in: libgweather
   Importance: Medium => Wishlist

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

Title:
  weather applet beaufort scale should use descriptions and not numbers.

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

Bug description:
  Binary package hint: gnome-applets

  The weather applet, when set to use the Beaufort scale, should at least have 
an option to present descriptions instead of numbers.  Descriptions may be 
found at http://en.wikipedia.org/wiki/Beaufort_scale#The_modern_scale (accessed 
June 23, 2008, permalink:
  http://en.wikipedia.org/w/index.php?title=Beaufort_scale=220195075): 
look in the table under the "Description" column.  
  To reproduce:
  1. set the weather applet to use the Beaufort scale: right click on it and 
choose preferences, from there set the wind speed unit
  2. view the weather (you may have to hit update to see it using the Beaufort 
scale).
  This is a wishlist bug/enhancement

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

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

[Desktop-packages] [Bug 1723376] Re: Disk read / Disk write are backwards in the Processes page

[Bug Watch Updater]

** Changed in: gnome-system-monitor
   Status: Confirmed => Fix Released

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

Title:
  Disk read / Disk write are backwards in the Processes page

Status in Gnome System Monitor:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  Disk read / Disk write are backwards in the Processes page of gnome-
  system-monitor.

  For a process that is only reading from disk it shows values under
  "Disk write". And for a process that is only writing to disk, it shows
  values under "Disk read".

  Running iotop or monitoring /proc/PID/io shows no such bug anywhere
  else. Only in gnome-system-monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-system-monitor 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 13 17:30:30 2017
  InstallationDate: Installed on 2017-05-03 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.

[Scott Moser]

This bug is believed to be fixed in curtin in 17.1. If this is still a
problem for you, please make a comment and set the state back to New

Thank you.

** Changed in: curtin
   Status: Fix Committed => Fix Released

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

Title:
  ping does not work as a normal user on trusty tarball cloud images.

Status in curtin:
  Fix Released
Status in MAAS:
  Fix Released
Status in curtin package in Ubuntu:
  Fix Released
Status in iputils package in Ubuntu:
  Fix Released
Status in maas package in Ubuntu:
  Fix Released
Status in tar package in Ubuntu:
  Fix Released
Status in tar source package in Precise:
  Confirmed
Status in maas source package in Saucy:
  Won't Fix
Status in tar source package in Saucy:
  Won't Fix
Status in curtin source package in Trusty:
  Fix Released
Status in maas source package in Trusty:
  Fix Released
Status in tar source package in Trusty:
  Fix Released
Status in maas source package in Vivid:
  Won't Fix
Status in maas source package in Wily:
  Fix Released

Bug description:
  With trusty, /bin/ping relies on having extended attributes and kernel
  capabilities to gain the cap_net_raw+p capability. This allows
  removing the suid bit.

  However, the tarball cloud images do not preserve the extended
  attributes, and thus /bin/ping does not work on a system derived from
  them.

  Summary of problem per package:
   * lxc: ubuntu cloud template needs to extract
   * download template needs to extract with xattr flags
   * server side download creation tools need xattr flags
   * [unconfirmed] tarball caches need creation and extraction with xattr flags
   * tar: need the '--xattr' and '--acl' flags backported
   * maas: uec2roottgz needs to use xattr/acl flags
   * curtin: extraction needs to use xattr/acl flags.
   * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags

  Related Bugs:
   * bug 1382632: horizon insecure key file permissions
   * bug 1386237: tar strange behavior with --acl and xattr
   * bug 1313550: ping broken (xattrs lost in tar extraction)

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

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

[Desktop-packages] [Bug 1738487] [NEW] Shell crashes with JS ERROR: TypeError: monitor is null

[Laura Dietz]

Public bug reported:

Periodically when I suspend my computer and resume it I find that my
session is gone. The following is logged in the journal after such an
event,

Dec 15 16:20:35 jam gnome-shell[1501]: JS ERROR: TypeError: monitor is null
   
BoxPointer<._reposition@resource:///org/gnome/shell/ui/boxpointer.js:507:13
   
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
   
BoxPointer<._allocate@resource:///org/gnome/shell/ui/boxpointer.js:234:13
   
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
   
LayoutManager<._init/<@resource:///org/gnome/shell/ui/layout.js:208:33
Dec 15 16:20:36 jam org.gnome.Shell.desktop[1501]: == Stack trace for context 
0x564daca8d000 ==

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 16:29:40 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Iris Graphics 540 [1028:06dc]
InstallationDate: Installed on 2017-11-24 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Latitude E7470
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.13.0-18-generic.efi.signed 
root=UUID=68384484-a30e-4aa4-990d-3727f8967b40 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.5
dmi.board.name: 0YDW8F
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.5:bd07/11/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0YDW8F:rvrA03:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

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

Title:
  Shell crashes with JS ERROR: TypeError: monitor is null

Status in xorg package in Ubuntu:
  New

Bug description:
  Periodically when I suspend my computer and resume it I find that my
  session is gone. The following is logged in the journal after such an
  event,

  Dec 15 16:20:35 jam gnome-shell[1501]: JS ERROR: TypeError: monitor is null
 
BoxPointer<._reposition@resource:///org/gnome/shell/ui/boxpointer.js:507:13
 
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
 
BoxPointer<._allocate@resource:///org/gnome/shell/ui/boxpointer.js:234:13
 
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
 
LayoutManager<._init/<@resource:///org/gnome/shell/ui/layout.js:208:33
  Dec 15 16:20:36 jam org.gnome.Shell.desktop[1501]: == Stack trace for context 
0x564daca8d000 ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 16:29:40 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[NoOne]

Now, if someone could ever fix that bug, I would be free of any
annoyance in Ubuntu. :-)

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724105

Let's hope for 18.04.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

[Sergio Callegari]

Don't know what I did, but finally I have succeeded disabling the
display of the driverless network printers.

Right before systemd reported cups-browsed as stopped.

Can it be the case that you need /both/ the process stopped /and/ the
BrowseRemoteProtocols in its conf file set to none /at the same time/
plus a restart of the desktop environment?

In case, I would change the bug title to "please document how to disable
the display of the driverless network printers" in the print dialog. It
can be a handy feature in places with just a couple of printers of
different brands, but in some environments it needs to be off.

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
  CurrentDesktop: KDE
  Date: Fri Dec 15 16:22:07 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1463 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Notebook W740SU
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1738479] [NEW] libimobile device doesn't see device and device reboots when I'm disconnecting it from computer device doesn't see device, device reboots when I'm disconnecting

[Evgeny]

Public bug reported:

Hi.

My computer: 
(Lubuntu):
evg@evg-Parallels-Virtual-Platform:$ uname -a
Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP 
Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
(Ubuntu):
Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 
2017 i686 i686 i686 GNU/Linux

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken

I've successfully installed all libs from this document
https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc .
And device isn't visible when I'm trying to pair it using idevicepair
pair command, but it appears in all connected device list.

evg@evg-Parallels-Virtual-Platform:$ lsusb
Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1
Bus 001 Device 002: ID 203a:fff9
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
evg@evg-Parallels-Virtual-Platform:$ idevicepair pair
No device found, is it plugged in?
I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on Ubuntu 
(16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my ipad 
reboots when I disconnecting it from computer.

video with reboot (Reboot appears only on Ubuntu, not Lubuntu):
https://youtu.be/8expDYVAW4o

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

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

Title:
  libimobile device doesn't see device and device reboots when I'm
  disconnecting it from computer device doesn't see device, device
  reboots when I'm disconnecting it from computer

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Hi.

  My computer: 
  (Lubuntu):
  evg@evg-Parallels-Virtual-Platform:$ uname -a
  Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP 
Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
  (Ubuntu):
  Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 
2017 i686 i686 i686 GNU/Linux

  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken

  I've successfully installed all libs from this document
  https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc
  . And device isn't visible when I'm trying to pair it using
  idevicepair pair command, but it appears in all connected device list.

  evg@evg-Parallels-Virtual-Platform:$ lsusb
  Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1
  Bus 001 Device 002: ID 203a:fff9
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  evg@evg-Parallels-Virtual-Platform:$ idevicepair pair
  No device found, is it plugged in?
  I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on 
Ubuntu (16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my 
ipad reboots when I disconnecting it from computer.

  video with reboot (Reboot appears only on Ubuntu, not Lubuntu):
  https://youtu.be/8expDYVAW4o

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

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

[Desktop-packages] [Bug 1430068] Re: Unable to launch gnome-system-monitor

[Mitchell Nahikian]

This has happened twice to me. The first time required a full re-image of my 
machine to fix it.
Then it randomly happened again today. The only thing I can associate with it 
was very high CPU/RAM usage (~100% on most of 32 cores and most if not all of 
swap space) when building with gcc72.
Ubuntu 14.04

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

Title:
  Unable to launch gnome-system-monitor

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

Bug description:
  When you have too many open files, you can't launch gnome-system-
  monitor:

   $ gnome-system-monitor

  (gnome-system-monitor:23720): glibmm-CRITICAL **: 
  unhandled exception (type Glib::Error) in signal handler:
  domain: g-io-error-quark
  code  : 0
  what  : Unable to find default local directory monitor type

  
  (gnome-system-monitor:23720): Gtk-CRITICAL **: gtk_window_present_with_time: 
assertion 'GTK_IS_WINDOW (window)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-system-monitor 3.8.2.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 09:32:12 2015
  InstallationDate: Installed on 2014-06-26 (255 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (133 days ago)

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

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

[Desktop-packages] [Bug 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu

[Jesse Glick]

I think I have tracked this down to irccloud.com, an app offering web
access to IRC channels once you are logged in. I had that site open in a
tab, among others, and saw `gnome-keyring-daemon` acting up. Closed
`chromium` and `gnome-keyring-daemon` stopped working. Restarted
`chromium` with the same tabs—daemon started working again. I tried
restarting with progressively fewer tabs open, and it was restarting
with irccloud.com closed that caused the problem to cease. Conversely,
opening a tab with irccloud.com again causes the daemon to work. Not
sure what about that site specifically would trigger a bug like this;
GMail, etc. do not.

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

Title:
  chrome-browser makes gnome-keyring-daemon use 100% cpu

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 13.04, when starting the chromium browser, the
  gnome-keyring-daemon runs at full CPU load and the chromium-browser
  has no access to the stored passwords.

  The issue seems to be known
  (https://code.google.com/p/chromium/issues/detail?id=98601). I'm
  personally a bit surprised that Ubuntu 13.04 was released with such a
  serious problem.

  The frequently proposed workaround (e.g.
  https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4)
  doesn't work because (a) there is no .gnome2/keyrings any more and (b)
  it's rather inresponsible to store your passwords unencryted.

  I found that killing gnome-keyring-server several times eventually gives you 
a working system.
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnl   18759 F pulseaudio
  CRDA:
   country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140
  InstallationDate: Installed on 2010-11-10 (900 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD)
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice 
wireshark
  WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group 
rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP]
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.20
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU9326SJY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6730b (GB990EA#ABD)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

Thank *you*, NoOne, both for reporting the issue and for confirming the
fix.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[William Ivanski]

Workaround in #4 works for me, but only for the computer-integrated
speaker. Integrated microphone and also headsets don't work any more.

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1733162] Re: Epiphany creates an empty "OpenGL Renderer" window entry in the dock for every video embedded in a webpage.

[Launchpad Bug Tracker]

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

** Changed in: epiphany-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  Epiphany creates an empty "OpenGL Renderer" window entry in the dock
  for every video embedded in a webpage.

Status in epiphany-browser package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 17.10, Epiphany (GNOME Web) creates an empty "OpenGL
  Renderer" window entry in the dock for every video embedded in a
  webpage.

  I wasn't sure where to report this. Probably an issue that could be
  fixed by blacklisting this by name from creating an entry on the dock?

  Testing is pretty easy. Open a youtube video and notice the empty
  window entry on the dock. Or (even better) scroll down a page with
  multiple videos and notice that a new "OpenGL Renderer" entry is
  created on the dock for each one. This is really aggravating with
  Facebook.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.1-1ubuntu1
  Uname: Linux 4.14.0-041400-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 02:09:20 2017
  InstallationDate: Installed on 2017-11-08 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[NoOne]

@Thanks Gunnar, it worked like you said.

Can confirm that the fix works !

Finally!  Very happy.  :-)

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

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

[Apport retracing service]

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

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 #1706097, 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/1738468/+attachment/5023144/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** 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 gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1738468

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  The error occurred when I connected the Samsung GT I9082L to the USB
  port.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.34.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 16:16:08 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2017-11-12 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.18 
/org/gtk/gvfs/exec_spaw/11
  SegvAnalysis:
   Segfault happened at: 0x7fe7b14ca5a9:mov0x18(%rax),%rax
   PC (0x7fe7b14ca5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones

[Adam Hulin]

I'm also affected of this issue.

I found this partial(?) solution to this on github:
https://gist.github.com/kevinlekiller/f533f4d1f7318a7cf81a

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   20842 F pulseaudio
   /dev/snd/controlC0:  michael   20842 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
   /dev/snd/controlC1:  michael   20842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 11 22:50:15 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
  Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2404 F pulseaudio
   /dev/snd/controlC2:  michael2404 F pulseaudio
   /dev/snd/controlC1:  michael2404 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875
  InstallationDate: Installed on 2014-10-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1380046] Re: [AV200 - Xonar STX, playback] Loud pop when switching to headphones

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [AV200 - Xonar STX, playback] Loud pop when switching to headphones

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

Bug description:
  When switching the port to either headphone ports from the speaker
  port there is a loud pop in the headphones. When I am playing music
  through the speakers at 100% volume and then switch, I can hear the
  music at a very loud volume through the headphones for a fraction of a
  second before dropping to the proper headphones volume which is much
  lower. Even if I mute the output before switching ports there is still
  a pop although not nearly as loud.

  I believe this is a driver issue (oxygen/virtuoso). The Essense STX
  uses a relay to switch between the speaker and headphones ports. I am
  guessing the the power for the speaker (line out) port is much higher
  than that used for the headphones port and the drivers need to mute
  the sound at a hardware level before switching to elmininate the pop.
  On Windows when switching to and from speaker and headphones port the
  output would be muted for almost a second as the port was switched so
  there was no pop. On Ubuntu there is no delay when switching ports. I
  have looked at the driver source code and there is an anti_pop_delay
  of 800 milliseconds used on the Xonar init method. I think this same
  delay should probably be added when switching to the headphone ports.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  michael   20842 F pulseaudio
   /dev/snd/controlC0:  michael   20842 F pulseaudio
   /dev/snd/pcmC0D0p:   michael   20842 F...m pulseaudio
   /dev/snd/controlC1:  michael   20842 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 11 22:50:15 2014
  InstallationDate: Installed on 2014-10-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:STX successful
  Symptom_Card: HD Webcam C910 - USB Device 0x46d:0x821
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2404 F pulseaudio
   /dev/snd/controlC2:  michael2404 F pulseaudio
   /dev/snd/controlC1:  michael2404 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=89201542-3d78-4588-9f0f-3725c7c22875
  InstallationDate: Installed on 2014-10-07 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=fbc05121-3d98-42ce-8073-986171e4b73f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:
   
  Tags:  trusty trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm 

[Desktop-packages] [Bug 1738450] Re: cant gey latest firefox to update

[Leonidas S. Barbosa]

Hi Thomas!

Did you already try: sudo apt-get update && sudo apt-upgrade or apt-get
install firerox?

** Information type changed from Private Security to Public

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

Title:
  cant gey latest firefox to update

Status in firefox package in Ubuntu:
  New

Bug description:
  am running 54. version need to make latest version work

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic i686
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.8.0-59-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomas 1268 F pulseaudio
  BuildID: 20170612122239
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe938000 irq 27'
 Mixer name : 'Realtek ALC888'
 Components : 'HDA:10ec0888,14627438,0011'
 Controls  : 23
 Simple ctrls  : 11
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Fri Dec 15 11:06:32 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 2017-08-15 (121 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.1)
  IpRoute:
   default via 10.0.0.1 dev wls33  proto static  metric 600 
   10.0.0.0/24 dev wls33  proto kernel  scope link  src 10.0.0.21  metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122239 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2009
  dmi.bios.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.bios.version: 1.0B
  dmi.board.name: MS-7438
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 100
  dmi.chassis.type: 4
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.modalias: 
dmi:bvnMICRO-STARINTERNATIONALCO.,LTD:bvr1.0B:bd04/17/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-6638:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7438:rvr100:cvnMICRO-STARINTERNATIONALCO.,LTD:ct4:cvr:
  dmi.product.name: MS-6638
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD

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

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

[Desktop-packages] [Bug 1738338] Re: Have unity-session recommend gtk3-nocsd

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-session - 3.26.1-0ubuntu8

---
gnome-session (3.26.1-0ubuntu8) bionic; urgency=medium

  * Have unity-session recommend gtk3-nocsd. (LP: #1738338)

 -- Khurshid Alam   Fri, 15 Dec 2017
11:46:26 +0530

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

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

Title:
  Have unity-session recommend gtk3-nocsd

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu patches Gnome apps to use tradition titlebar and menubar (in
  some apps) so that it can work well under Unity (Specially for LIM).

  But Unity is not the default desktop anymore. And Desktop Team goals
  is to reduce the Ubuntu-specific patches they are carrying. So in
  future they are likely to be dropped. But then it will create problem
  for Unity.

  One simple solution is to use gtk3-nocsd. gtk3-nocsd will
  automatically force all applications to use traditional titlebar.

  See discussion here: https://community.ubuntu.com/t/removal-of-
  headerbar-patches-and-impact-on-unity/1456

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

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

[Desktop-packages] [Bug 1738457] [NEW] package oneconf install oneconf-query but documentation is missing

[Mikko Rantalainen]

Public bug reported:

$ dpkg -L oneconf
...
/usr/bin/oneconf-query

$ man oneconf-query
No manual entry for oneconf-query
See 'man 7 undocumented' for help when manual pages are not available.

$ man 7 undocumented
No manual entry for undocumented in section 7

If command oneconf-query is installed in default PATH, I would expect it
to be documented. Otherwise I would expect it to be located only in
/usr/share/oneconf/oneconf-query to be used by other programs but never
by humans.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: oneconf 0.3.9
ProcVersionSignature: Ubuntu 4.13.0-19.22~16.04.1-lowlatency 4.13.13
Uname: Linux 4.13.0-19-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Dec 15 19:36:36 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2009-10-08 (2990 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20091008)
PackageArchitecture: all
SourcePackage: oneconf
UpgradeStatus: Upgraded to xenial on 2016-11-14 (396 days ago)

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


** Tags: amd64 apport-bug xenial

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/oneconf/+bug/1738457/+attachment/5023128/+files/JournalErrors.txt

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

Title:
  package oneconf install oneconf-query but documentation is missing

Status in oneconf package in Ubuntu:
  New

Bug description:
  $ dpkg -L oneconf
  ...
  /usr/bin/oneconf-query

  $ man oneconf-query
  No manual entry for oneconf-query
  See 'man 7 undocumented' for help when manual pages are not available.

  $ man 7 undocumented
  No manual entry for undocumented in section 7

  If command oneconf-query is installed in default PATH, I would expect
  it to be documented. Otherwise I would expect it to be located only in
  /usr/share/oneconf/oneconf-query to be used by other programs but
  never by humans.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: oneconf 0.3.9
  ProcVersionSignature: Ubuntu 4.13.0-19.22~16.04.1-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Dec 15 19:36:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2009-10-08 (2990 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20091008)
  PackageArchitecture: all
  SourcePackage: oneconf
  UpgradeStatus: Upgraded to xenial on 2016-11-14 (396 days ago)

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

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

[Desktop-packages] [Bug 1683990] Re: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all. Resets to mute. No 'Play Sound Through' options

[Clare]

the bug is fixed! today I have sound. I would close this if I could see
how.

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

Title:
  [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all.
  Resets to mute. No 'Play Sound Through' options

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Edit 11-Dec-2017

  attached screenshot showing how there are no 'Play sound through' Output 
Options in the Sound Settings. Also, AlsaMixer indicates that the speaker keeps 
getting reset to mute after each re-start.
  -

  Edit 05-Nov-2017
  note that when I run pulseaudio (verbose) at the command line it says that 
the daemon is running but that pa_pid_file_create() failed

  and when I ran gnome-control-center at the command line recently I
  saw:

  (gnome-control-center:8955): sound-cc-panel-WARNING **: No devices in
  the tree, so cannot set the active output

  (gnome-control-center:8955): Gvc-WARNING **: Couldn't match the
  portless stream (with card) - 'Built-in Audio Analog Stereo' is it an
  input ? -> 1, streams card id -> 0

  (gnome-control-center:8955): Gvc-CRITICAL **:
  gvc_mixer_ui_device_get_id: assertion 'GVC_IS_MIXER_UI_DEVICE
  (device)' failed

  (gnome-control-center:8955): sound-cc-panel-WARNING **:
  on_control_active_input_update - tried to fetch an input of id 0 but
  got nothing

  -original text of bug--

  I have had no sound since original (fairly recent) purchase. I
  purchased online from Dell.

  Sound preferences were originally showing in upper right hand corner
  of the screen, but the sliders for changing volume were grayed out,
  and choosing sound test had no audible or visual result.

  Now sound preferences are not showing in upper right corner at all,
  and system preferences --> sound no longer shows 'sound test' as an
  option.

  I tried to fix original problem myself by killing then re-starting pulseaudio
  No effect. Also I tried commands

  apt-get purge pulseaudio
  and then later
  apt-get install pulseaudio

  it seemed to be after that when the sound preferences stopped showing
  in upper right corner, but I also did a general ubuntu update at the
  same time (and there is still a restart required for update for
  'Latitude E5X60 System Update' 68614)

  Release: Ubuntu 16.04.2 LTS
  Package: N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clare  2105 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 18 22:44:33 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2017-01-05 (104 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  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:  clare  2105 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Precision 3510, Realtek ALC3235, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2017-02-10 (67 days ago)
  dmi.bios.date: 08/26/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.4
  dmi.board.name: 0FFPFD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.4:bd08/26/2016:svnDellInc.:pnPrecision3510:pvr:rvnDellInc.:rn0FFPFD:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 3510
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1716986] Re: Unity session entry in lightdm has a white circle logo

[Walter Garcia-Fontes]

@ventrical, it's:
/usr/share/unity-greeter/unknown_badge.png

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

Title:
  Unity session entry in lightdm has a white circle logo

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 from 17.04, and switching back to lightdm
  from gdm3 to be able to start the Unity 7 desktop, the entry in the
  login screen for Unity 7 has a white circle as a logo (the Ubuntu logo
  is now assigned to the default Gnome option). A logo should be created
  to distinguish the Unity 7 desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unity-session 3.25.90-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Sep 13 19:31:07 2017
  InstallationDate: Installed on 2015-10-17 (696 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to artful on 2017-09-12 (1 days ago)

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

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

[Desktop-packages] [Bug 1728045] Re: Please restore battery time remaining to top bar!

[Charles Beer]

Has there been any resolution to this?  Or is one underway?  When I go
to the link for the bug link mentioned here (#540373), the last comment
or update of any kind I see is from 2009...

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

Title:
  Please restore battery time remaining to top bar!

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu 17.04 and earlier, I was able to display the amount of
  battery life remaining AS TIME in the top bar of my screen.

  Now all I'm able to display, in 17.10, is the battery percentage.

  Frankly, I don't give a flying fig about battery percentage, and I'm
  not sure most other people do either. What I care about is how much
  time I have left to work on my laptop before it's out of power.

  If you want to display _both_ the percentage and the time remaining,
  or allow the user to choose which to display, that would be great. But
  just taking away the eminently useful time remaining and replacing it
  with the much less useful percentage is annoying and should be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 27 09:13:40 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-05-19 (160 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-20 (6 days ago)

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

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

[Desktop-packages] [Bug 1738448] Re: gnome-online-accounts should recommend dleyna-server for Media Server support

[Jeremy Bicha]

** Description changed:

- Because dleyna-server is in universe, Ubuntu's gnome-online-accounts
- cannot recommend it like the Debian package does. I have pushed a hack
- to Debian to allow us to sync gnome-online-accounts and for the
- dependencies to be handled correctly.
+ Because dleyna-server is in universe, Ubuntu's gnome-online-accounts cannot 
recommend it like the Debian package does. I have pushed a hack to Debian to 
allow us to sync gnome-online-accounts and for the dependencies to be handled 
correctly.
+ 
https://anonscm.debian.org/git/pkg-gnome/gnome-online-accounts.git/commit/?id=e544639
  
  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.
  
  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.
  
  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.
  
  Or we could try to get dleyna-server in to Ubuntu main.

** Tags added: artful bionic gnome-17.10

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

Title:
  gnome-online-accounts should recommend dleyna-server for Media Server
  support

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Because dleyna-server is in universe, Ubuntu's gnome-online-accounts cannot 
recommend it like the Debian package does. I have pushed a hack to Debian to 
allow us to sync gnome-online-accounts and for the dependencies to be handled 
correctly.
  
https://anonscm.debian.org/git/pkg-gnome/gnome-online-accounts.git/commit/?id=e544639

  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.

  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.

  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.

  Or we could try to get dleyna-server in to Ubuntu main.

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

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

[Desktop-packages] [Bug 1716986] Re: Unity session entry in lightdm has a white circle logo

[Khurshid Alam]

** Tags added: bionic unity

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

Title:
  Unity session entry in lightdm has a white circle logo

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10 from 17.04, and switching back to lightdm
  from gdm3 to be able to start the Unity 7 desktop, the entry in the
  login screen for Unity 7 has a white circle as a logo (the Ubuntu logo
  is now assigned to the default Gnome option). A logo should be created
  to distinguish the Unity 7 desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: unity-session 3.25.90-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Sep 13 19:31:07 2017
  InstallationDate: Installed on 2015-10-17 (696 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to artful on 2017-09-12 (1 days ago)

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

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

[Desktop-packages] [Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort()

[Bug Watch Updater]

Launchpad has imported 17 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1511681.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-11-09T20:49:38+00:00 Michael wrote:

Version-Release number of selected component:
xorg-x11-server-Xwayland-1.19.3-4.fc26

Additional info:
reporter:   libreport-2.9.1
backtrace_rating: 4
cmdline:/home/mcatanzaro/Projects/GNOME/install/bin/Xwayland :1 
-rootless -terminate -core -listen 4 -listen 5 -displayfd 6
crash_function: xwl_read_events
executable: /usr/bin/Xwayland
journald_cursor: 
s=ca44c691f28b4a3fa6affd95ab5151f5;i=1b36b7;b=1bb81d6006b3438f9124fe2aa5b58740;m=a0fe9fcbc;t=55ce29a097191;x=9b45217435b11c67
kernel: 4.13.9-200.fc26.x86_64
rootdir:/
runlevel:   N 5
type:   CCpp
uid:1000

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/0


On 2017-11-09T20:49:46+00:00 Michael wrote:

Created attachment 1350099
File: backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/1


On 2017-11-09T20:49:47+00:00 Michael wrote:

Created attachment 1350100
File: cgroup

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/2


On 2017-11-09T20:49:48+00:00 Michael wrote:

Created attachment 1350101
File: core_backtrace

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/3


On 2017-11-09T20:49:49+00:00 Michael wrote:

Created attachment 1350102
File: cpuinfo

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/4


On 2017-11-09T20:49:50+00:00 Michael wrote:

Created attachment 1350103
File: dso_list

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/5


On 2017-11-09T20:49:51+00:00 Michael wrote:

Created attachment 1350104
File: environ

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/6


On 2017-11-09T20:49:52+00:00 Michael wrote:

Created attachment 1350105
File: limits

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/7


On 2017-11-09T20:49:53+00:00 Michael wrote:

Created attachment 1350106
File: maps

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/8


On 2017-11-09T20:49:55+00:00 Michael wrote:

Created attachment 1350107
File: open_fds

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/9


On 2017-11-09T20:49:56+00:00 Michael wrote:

Created attachment 1350108
File: proc_pid_status

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/10


On 2017-11-09T20:49:57+00:00 Michael wrote:

Created attachment 1350109
File: var_log_messages

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/11


On 2017-11-10T09:26:11+00:00 Olivier wrote:

Same as bug 1510078, this is a abort() because Xwayland (Wayland client)
cannot read events from the Wayland compositor (gnome-shell.mutter,
presumably) which is most likely a crash in gnome-shell/mutter in the
first place.

xwl_read_events() aborts in two cases, either it fails to read the
events (wl_display_read_events) or it fails to dispatch the events
(wl_display_dispatch_pending), in both cases it's a communication issue
with the Wayland compositor.

Can you quickly check in the logs at the time of the crash if gnome-
shell/mutter had crashed or failed to start (I've seen this happening as
well at startup, gnome-shell starts, spawns Xwayland, then fails, and
Xwayland aborts in xwl_read_events())

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1731911/comments/12


On 2017-11-18T06:51:36+00:00 Justin wrote:

I am also experiencing 

[Desktop-packages] [Bug 512467] Re: Devhelp has no copy/paste context menu on right-click

[Bug Watch Updater]

** Changed in: devhelp
   Status: Confirmed => Fix Released

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

Title:
  Devhelp has no copy/paste context menu on right-click

Status in Gnome DevHelp:
  Fix Released
Status in devhelp package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: devhelp

  Devhelp doesn't have a right-click popup to copy/cut//paste.

  Personally I naever use the menu for this, occasioanlly use
  ^C and the like, but most often use the right-click popup.

  bjd

  ProblemType: Bug
  Architecture: amd64
  Date: Mon Jan 25 21:01:33 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/devhelp
  NonfreeKernelModules: nvidia
  Package: devhelp 0.23-4
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: devhelp
  Uname: Linux 2.6.31-17-generic x86_64

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

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

[Desktop-packages] [Bug 1738338] Re: Have unity-session recommend gtk3-nocsd

[Khurshid Alam]

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

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

Title:
  Have unity-session recommend gtk3-nocsd

Status in gnome-session package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu patches Gnome apps to use tradition titlebar and menubar (in
  some apps) so that it can work well under Unity (Specially for LIM).

  But Unity is not the default desktop anymore. And Desktop Team goals
  is to reduce the Ubuntu-specific patches they are carrying. So in
  future they are likely to be dropped. But then it will create problem
  for Unity.

  One simple solution is to use gtk3-nocsd. gtk3-nocsd will
  automatically force all applications to use traditional titlebar.

  See discussion here: https://community.ubuntu.com/t/removal-of-
  headerbar-patches-and-impact-on-unity/1456

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

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

[Desktop-packages] [Bug 1738448] [NEW] gnome-online-accounts should recommend dleyna-server for Media Server support

[Jeremy Bicha]

Public bug reported:

Because dleyna-server is in universe, Ubuntu's gnome-online-accounts
cannot recommend it like the Debian package does. I have pushed a hack
to Debian to allow us to sync gnome-online-accounts and for the
dependencies to be handled correctly.

I am filing this as an informational bug since this issue will now be
less visible than if there was a persistent diff with Debian.

I think this will make the Media Server option in Settings > Online
Accounts not work, but I don't have a Media Server here to test right
now. This issue affects Ubuntu 17.10 and newer.

Ideally, the Media Server account type should be hidden if it doesn't
work, or modified to allow a user to easily install dleyna-server via
PackageKit.

Or we could try to get dleyna-server in to Ubuntu main.

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

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

Title:
  gnome-online-accounts should recommend dleyna-server for Media Server
  support

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Because dleyna-server is in universe, Ubuntu's gnome-online-accounts
  cannot recommend it like the Debian package does. I have pushed a hack
  to Debian to allow us to sync gnome-online-accounts and for the
  dependencies to be handled correctly.

  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.

  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.

  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.

  Or we could try to get dleyna-server in to Ubuntu main.

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

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

[Desktop-packages] [Bug 1738432] Re: Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

[Till Kamppeter]

Do you actually have no cups-browsed process running at all?
In which print dialogs do the driverless extra printers appear? Of which 
applications?
Please also run the commands

avahi-browse -v -t -r --all
lpstat -e
lpstat -v

and post the output here.


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

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
  CurrentDesktop: KDE
  Date: Fri Dec 15 16:22:07 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1463 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Notebook W740SU
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Desktop-packages] [Bug 1738442] [NEW] When installing a printer, the process gets stuck at "Loading drivers database..."

[Zaszuś]

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

Public bug reported:

When installing a printer, the process gets indefinitely stuck at
"Loading drivers database..."

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-control-center 1:3.18.2-1ubuntu6
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 15 17:22:04 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-09-29 (76 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** This bug has been marked a duplicate of bug 1721704
   Printer settings stuck on loading drivers database

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

Title:
  When installing a printer, the process gets stuck at "Loading drivers
  database..."

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

Bug description:
  When installing a printer, the process gets indefinitely stuck at
  "Loading drivers database..."

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Dec 15 17:22:04 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-09-29 (76 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1691479] Re: can't send message

[acastano]

Same problem here

NS_ERROR_NOT_IMPLEMENTED: Component returned failure code: 0x80004001 
(NS_ERROR_NOT_IMPLEMENTED) [nsIMsgCompose.expandMailingLists]  
MsgComposeCommands.js:4466
An error occurred executing the cmd_sendButton command: [Exception... 
"Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) 
[nsIMsgCompose.expandMailingLists]"  nsresult: "0x80004001 
(NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame :: 
chrome://messenger/content/messengercompose/MsgComposeCommands.js :: 
expandRecipients :: line 4466"  data: no]

Thunderbird 52.5.0 (64 bits)

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

Title:
  can't send message

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After last thunderbird update, I am not able to send a message from 
Thunderbird.
  I press the send button and nothing happens (I haven't noticed any debug log).
  The same happens with the ctrl+enter combination.
  I have tried to run Thunderbird in the safe mode (all add-ons disabled) and 
the issue is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: thunderbird 1:52.1.1+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: openafs
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  afiergol   5023 F pulseaudio
   /dev/snd/controlC1:  afiergol   5023 F pulseaudio
  BuildID: 20170510140118
  Channel: Unavailable
  CurrentDesktop: Unity:Unity7
  Date: Wed May 17 11:38:11 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   Enigmail - {847b3a00-7ab1-11d4-8f02-006008948af5}
   Lightning - {e2fda1a4-762b-4020-b5ad-a41df1933103}
   English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
   Polski Language Pack - langpack...@thunderbird.mozilla.org
   Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-04-02 (775 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PrefSources:
   prefs.js
   
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
   [Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
   
[Profile]/extensions/{a62ef8ec-5fdc-40c2-873c-223b8a6925cc}/defaults/preferences/preferences.js
   
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
  Profiles: Profile0 (Default) - LastVersion=52.1.1/20170510140118 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (28 days ago)
  dmi.bios.date: 04/25/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M70 Ver. 01.15
  dmi.board.name: 2253
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 03.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3009CD10002:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ZBook 15 G2
  dmi.product.version: A3009CD10002
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 269243] Re: pdf documents with japanes fonts do not show some characters

[Ondra Žižka]

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

** Also affects: poppler (CentOS)
   Importance: Undecided
   Status: New

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

Title:
  pdf documents with japanes fonts do not show some characters

Status in evince package in Ubuntu:
  Confirmed
Status in poppler package in CentOS:
  New

Bug description:
  Binary package hint: evince

  do not show japanes pdf files

  ProblemType: Bug
  Architecture: i386
  Date: Thu Sep 11 22:17:31 2008
  DistroRelease: Ubuntu 8.04
  ExecutablePath: /usr/bin/evince
  Package: evince 2.22.2-0ubuntu1
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  Uname: Linux 2.6.24-19-generic i686

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

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

[Desktop-packages] [Bug 1738207] Re: chromium with flash 28.0.0.126 + NVIDIA driver 384.90 crash and disable kwin_x11 compositing

[spear]

idk -- the Xid error occus thru chromium so I will change it back to
chromium ...

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

Title:
  chromium with flash 28.0.0.126 + NVIDIA driver 384.90 crash and
  disable kwin_x11 compositing

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  [ 3148.947708] traps: chromium-browse[11854] trap int3 ip:55a0ce34c40c 
sp:7ffc09cb41a0 error:0
  [ 3148.947715]  in chromium-browser[55a0cbefa000+8009000]
  [ 3149.160567] nvidia-modeset: Freed GPU:0 
(GPU-5999a249-a531-ac0e-b829-7818a72e5543) @ PCI::0c:00.0
  [ 3149.907851] nvidia-modeset: Allocated GPU:0 
(GPU-5999a249-a531-ac0e-b829-7818a72e5543) @ PCI::0c:00.0
  [ 3183.135074] NVRM: GPU at PCI::0c:00: 
GPU-5999a249-a531-ac0e-b829-7818a72e5543
  [ 3183.135076] NVRM: GPU Board Serial Number:
  [ 3183.135079] NVRM: Xid (PCI::0c:00): 31, Ch 0020, engmask 0101, 
intr 1000

  Zotac GeForce GTX 1070 AMP! Extreme Edition
  Xid: 31 => memory page fault ... does not occur in Firefox - only in chromium 
since upgrade to flash 28.0.0.126
  breaks compositing - need to log out and may break other GL dependant apps 
but for me it doesnt - just kwin_x11 cant composite anymore neither via GUI nor 
DBUS commands - even it says openGLisBroken is false and it can composite it 
doesnt toggle/activate compositing.
  Only way to get compositing back in this session is running "kwin_x11 
--replace &> /dev/null &" and thats not very intuitive for every user.

  lsb_release -rd
  Description:Ubuntu 17.04 # NOTE Kubuntu
  Release:17.04

  KDE Plasma Version: 5.10.5
  KDE Frameworks Version: 5.38.0
  Qt Version: 5.7.1
  Kernel Version: 4.10.0-42-generic
  OS Type: 64-bit

  Hardware
  Processors: 16 x AMD Ryzen 7 1700x Eight-Core Processor
  Memory: 31,4 GiB of RAM

  apt-cache policy chromium-browser
  chromium-browser:
    Installed: 63.0.3239.84-0ubuntu0.17.04.1
    Candidate: 63.0.3239.84-0ubuntu0.17.04.1
    Version table:
   *** 63.0.3239.84-0ubuntu0.17.04.1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   57.0.2987.98-0ubuntu1.1348 500
  500 http://at.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

  apt-cache policy flashplugin-installer
  flashplugin-installer:
    Installed: 28.0.0.126ubuntu0.17.04.1
    Candidate: 28.0.0.126ubuntu0.17.04.1
    Version table:
   *** 28.0.0.126ubuntu0.17.04.1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty-updates/multiverse 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/multiverse amd64 
Packages
  100 /var/lib/dpkg/status
   25.0.0.148ubuntu1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty/multiverse amd64 
Packages

  apt-cache policy pepperflashplugin-nonfree
  pepperflashplugin-nonfree:
    Installed: 1.8.3+nmu1ubuntu1
    Candidate: 1.8.3+nmu1ubuntu1
    Version table:
   *** 1.8.3+nmu1ubuntu1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty/multiverse amd64 
Packages
  100 /var/lib/dpkg/status

  apt-cache policy kwin
  kwin:
    Installed: 4:5.10.5-0ubuntu1~ubuntu17.04~ppa1
    Candidate: 4:5.10.5-0ubuntu1~ubuntu17.04~ppa1
    Version table:
   *** 4:5.10.5-0ubuntu1~ubuntu17.04~ppa1 500
  500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
amd64 Packages
  500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
i386 Packages
  100 /var/lib/dpkg/status
   4:5.9.5-0ubuntu0.1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
  500 http://at.archive.ubuntu.com/ubuntu zesty-updates/universe i386 
Packages
   4:5.9.5-0ubuntu0.1~ubuntu17.04~ppa1 500
  500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
amd64 Packages
  500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
i386 Packages
   4:5.9.4-0ubuntu1 500
  500 http://at.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
  500 http://at.archive.ubuntu.com/ubuntu zesty/universe i386 Packages

  apt-cache policy nvidia-384
  nvidia-384:
    Installed: 384.90-0ubuntu0.17.04.2
    Candidate: 384.90-0ubuntu0.17.04.2
    Version table:
   *** 384.90-0ubuntu0.17.04.2 500
  500 http://at.archive.ubuntu.com/ubuntu zesty-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   384.90-0ubuntu0.17.04.1 500
  500 http://security.ubuntu.com/ubuntu zesty-security/restricted amd64 
Packages

  So chromium didn't update its flash player from 27.0.0.130 so but Firefox did 
.. got frustrated and reinstalled chromium and pepperflash-nonfree which 
actually upgraded the version but now 

[Desktop-packages] [Bug 1738432] [NEW] Regression, poor user experience, print dialogs garbled by unidentifiable driverless printers

[Sergio Callegari]

Public bug reported:

Recently, my print dialogs have started to include network discoverd
printers in addition to those configured in cups even if the cups-
browsed service is disabled and the BrowseRemoteProtocols option is set
to none.

There does not seem to be any way to disable this behavior apart from
disabling avahi or its ability to talk to dbus, which causes side
effects on the system.

Yet, in some environments this behavior is a definite regression over
the old one and leads to an extremely poor user experience.

On some networks:

- The print dialogs takes 3-10 sec to open which is a huge amount of
time for an action that is expected to be instantaneous and for which
there is no visual feedback.

- The print dialog contains many tens of printer entries, all identified
by weird hex strings that cannot be related to any useful location, that
do not help identifying which entry corresponds to which printer and
that only mess up the list making it hard to find the printers that are
actually useful.

For instance, suppose that you work at some office that has recently
purchased a batch of new printers all the same model. In the print
dialog you may get many entries like:

HP_Laserjet_Pro_Mxxxdw_21ACF2

which only vary in the final hex string. How is one suppose to know what
is where?

Please make it possible to disable this driverless printer madness.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libcups2 2.2.4-7ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CupsErrorLog: E [15/Dec/2017:12:41:45 +0100] [Client 6] Returning IPP 
client-error-bad-request for Create-Printer-Subscriptions (/) from localhost
CurrentDesktop: KDE
Date: Fri Dec 15 16:22:07 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1463 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Notebook W740SU
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to artful on 2017-10-26 (50 days ago)
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W740SU
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

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

Title:
  Regression, poor user experience, print dialogs garbled by
  unidentifiable driverless printers

Status in cups package in Ubuntu:
  New

Bug description:
  Recently, my print dialogs have started to include network discoverd
  printers in addition to those configured in cups even if the cups-
  browsed service is disabled and the BrowseRemoteProtocols option is
  set to none.

  There does not seem to be any way to disable this behavior apart from
  disabling avahi or its ability to talk to dbus, which causes side
  effects on the system.

  Yet, in some environments this behavior is a definite regression over
  the old one and leads to an extremely poor user experience.

  On some networks:

  - The print dialogs takes 3-10 sec to open which is a huge amount of
  time for an action that is expected to be instantaneous and for which
  there is no visual feedback.

  - The print dialog contains many tens of printer entries, all
  identified by weird hex strings that cannot be related to any useful
  location, that do not help identifying which entry corresponds to
  which printer and that only mess up the list making it hard to find
  the printers that are actually useful.

  For instance, suppose that you work at some office that has recently
  purchased a batch of new printers all the same model. In the print
  dialog you may get many entries like:

  HP_Laserjet_Pro_Mxxxdw_21ACF2

  which only vary in the final hex string. How is one suppose to know
  what is where?

  Please make it possible to disable this driverless printer madness.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libcups2 2.2.4-7ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CupsErrorLog: E 

[Desktop-packages] [Bug 1738207] [NEW] chromium with flash 28.0.0.126 + NVIDIA driver 384.90 crash and disable kwin_x11 compositing

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[ 3148.947708] traps: chromium-browse[11854] trap int3 ip:55a0ce34c40c 
sp:7ffc09cb41a0 error:0
[ 3148.947715]  in chromium-browser[55a0cbefa000+8009000]
[ 3149.160567] nvidia-modeset: Freed GPU:0 
(GPU-5999a249-a531-ac0e-b829-7818a72e5543) @ PCI::0c:00.0
[ 3149.907851] nvidia-modeset: Allocated GPU:0 
(GPU-5999a249-a531-ac0e-b829-7818a72e5543) @ PCI::0c:00.0
[ 3183.135074] NVRM: GPU at PCI::0c:00: 
GPU-5999a249-a531-ac0e-b829-7818a72e5543
[ 3183.135076] NVRM: GPU Board Serial Number:
[ 3183.135079] NVRM: Xid (PCI::0c:00): 31, Ch 0020, engmask 0101, 
intr 1000

Zotac GeForce GTX 1070 AMP! Extreme Edition
Xid: 31 => memory page fault ... does not occur in Firefox - only in chromium 
since upgrade to flash 28.0.0.126
breaks compositing - need to log out and may break other GL dependant apps but 
for me it doesnt - just kwin_x11 cant composite anymore neither via GUI nor 
DBUS commands - even it says openGLisBroken is false and it can composite it 
doesnt toggle/activate compositing.
Only way to get compositing back in this session is running "kwin_x11 --replace 
&> /dev/null &" and thats not very intuitive for every user.

lsb_release -rd
Description:Ubuntu 17.04 # NOTE Kubuntu
Release:17.04

KDE Plasma Version: 5.10.5
KDE Frameworks Version: 5.38.0
Qt Version: 5.7.1
Kernel Version: 4.10.0-42-generic
OS Type: 64-bit

Hardware
Processors: 16 x AMD Ryzen 7 1700x Eight-Core Processor
Memory: 31,4 GiB of RAM

apt-cache policy chromium-browser
chromium-browser:
  Installed: 63.0.3239.84-0ubuntu0.17.04.1
  Candidate: 63.0.3239.84-0ubuntu0.17.04.1
  Version table:
 *** 63.0.3239.84-0ubuntu0.17.04.1 500
500 http://at.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 57.0.2987.98-0ubuntu1.1348 500
500 http://at.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages

apt-cache policy flashplugin-installer
flashplugin-installer:
  Installed: 28.0.0.126ubuntu0.17.04.1
  Candidate: 28.0.0.126ubuntu0.17.04.1
  Version table:
 *** 28.0.0.126ubuntu0.17.04.1 500
500 http://at.archive.ubuntu.com/ubuntu zesty-updates/multiverse amd64 
Packages
500 http://security.ubuntu.com/ubuntu zesty-security/multiverse amd64 
Packages
100 /var/lib/dpkg/status
 25.0.0.148ubuntu1 500
500 http://at.archive.ubuntu.com/ubuntu zesty/multiverse amd64 Packages

apt-cache policy pepperflashplugin-nonfree
pepperflashplugin-nonfree:
  Installed: 1.8.3+nmu1ubuntu1
  Candidate: 1.8.3+nmu1ubuntu1
  Version table:
 *** 1.8.3+nmu1ubuntu1 500
500 http://at.archive.ubuntu.com/ubuntu zesty/multiverse amd64 Packages
100 /var/lib/dpkg/status

apt-cache policy kwin
kwin:
  Installed: 4:5.10.5-0ubuntu1~ubuntu17.04~ppa1
  Candidate: 4:5.10.5-0ubuntu1~ubuntu17.04~ppa1
  Version table:
 *** 4:5.10.5-0ubuntu1~ubuntu17.04~ppa1 500
500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
amd64 Packages
500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
i386 Packages
100 /var/lib/dpkg/status
 4:5.9.5-0ubuntu0.1 500
500 http://at.archive.ubuntu.com/ubuntu zesty-updates/universe amd64 
Packages
500 http://at.archive.ubuntu.com/ubuntu zesty-updates/universe i386 
Packages
 4:5.9.5-0ubuntu0.1~ubuntu17.04~ppa1 500
500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
amd64 Packages
500 http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu zesty/main 
i386 Packages
 4:5.9.4-0ubuntu1 500
500 http://at.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages
500 http://at.archive.ubuntu.com/ubuntu zesty/universe i386 Packages

apt-cache policy nvidia-384
nvidia-384:
  Installed: 384.90-0ubuntu0.17.04.2
  Candidate: 384.90-0ubuntu0.17.04.2
  Version table:
 *** 384.90-0ubuntu0.17.04.2 500
500 http://at.archive.ubuntu.com/ubuntu zesty-updates/restricted amd64 
Packages
100 /var/lib/dpkg/status
 384.90-0ubuntu0.17.04.1 500
500 http://security.ubuntu.com/ubuntu zesty-security/restricted amd64 
Packages

So chromium didn't update its flash player from 27.0.0.130 so but Firefox did 
.. got frustrated and reinstalled chromium and pepperflash-nonfree which 
actually upgraded the version but now when launching Chromium - the GPU has a 
memory page fault ...
So KWin Compositing is unusable after launching chromium now - I need to logout 
or shoot down X11 to get compositing back (I am on a Ryzen System and had this 
problem before with a different driver) - I wished everything would finally 
work and compositing stayed on. Only way to get compositing back in this 
session is running "kwin_x11 --replace &> /dev/null &" and thats not very 
intuitive for every user.

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

[Didier Raboud]

It's fine to have root as member of the lpadmin group. BUT… it's not
fine to have cups-pk-helper run as root and allow unauthorized users (in
CUPS' eyes) cancel other user's jobs.

This should be fixed in cups-pk-helper through making it interact with
CUPS using the requesting user's user. This would ensure that CUPS's
authorizations are respected.

I don't want to see a situation where "any GNOME user" accesses "cups-
pk-helper which runs as root" and can then "manipulate CUPS as if it
were a member of lpadmin".

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

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

[Desktop-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work

[Till Kamppeter]

shemgp, unfortunately, your newest patch still does not solve the
problem for me.

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete
Status in cups-pk-helper package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

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

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

[Desktop-packages] [Bug 1696305] Re: High CPU usage in gnome-shell just redrawing the screen (Firefox is running)

[monomakh]

Switch off the second monitor solve high CPU usage for me

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

Title:
  High CPU usage in gnome-shell just redrawing the screen (Firefox is
  running)

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

Bug description:
  Even when doing nothing at all, gnome-shell uses around 70% CPU.

  ```
  inxi -t cm
  Processes: CPU: % used - top 5 active
 1: cpu: 68.6% command: gnome-shell pid: 1399
 2: cpu: 50.4% command: Xwayland pid: 1405
 3: cpu: 19.7% command: firefox pid: 3684
 4: cpu: 2.4% command: gnome-shell pid: 1859
 5: cpu: 1.5% command: gnome-tweak-tool (started by: python) pid: 
13603
 Memory: MB / % used - Used/Total: 2350.1/11897.0MB - top 5 active
 1: mem: 1033.63MB (8.6%) command: firefox pid: 3684
 2: mem: 317.59MB (2.6%) command: gnome-shell pid: 1859
 3: mem: 267.55MB (2.2%) command: gnome-software pid: 2058
 4: mem: 111.25MB (0.9%) command: Xorg pid: 1506
 5: mem: 90.90MB (0.7%) command: nautilus-desktop pid: 2055
  ```

  It's also strange that Xwayland is active as I did choose the "normal" gnome 
session upon signin.
  ```
  echo $XDG_SESSION_TYPE
  x11
  ```

  While searching I found a recent problem with AMD GPUs, but I'm using an 
Intel GPU
  ```
  glxinfo 
  name of display: :0
  display: :0  screen: 0
  direct rendering: Yes
  server glx vendor string: SGI
  server glx version string: 1.4
  server glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, 
  GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, 
  GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, 
  GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_texture_from_pixmap, 
  GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, 
  GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, 
  GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, 
  GLX_SGI_make_current_read, GLX_SGI_swap_control
  client glx vendor string: Mesa Project and SGI
  client glx version string: 1.4
  client glx extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  GLX version: 1.4
  GLX extensions:
  GLX_ARB_create_context, GLX_ARB_create_context_profile, 
  GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, 
  GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, 
  GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, 
  GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, 
  GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, 
  GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
  GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, 
  GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
  GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, 
  GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, 
  GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, 
  GLX_SGI_swap_control, GLX_SGI_video_sync
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel Open Source Technology Center (0x8086)
  Device: Mesa DRI Intel(R) Haswell Mobile  (0xa16)
  Version: 17.1.0
  Accelerated: yes
  Video memory: 1536MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.5
  Max compat profile version: 3.0
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.1
  OpenGL vendor string: Intel Open Source Technology Center
  OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
  OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.1.0
  OpenGL core profile shading language version string: 4.50
  OpenGL core profile context flags: (none)
  OpenGL core 

[Desktop-packages] [Bug 1731888] Re: right-click menu on the terminal gets broken when terminal window is maximized

[LuisC]

It happens to me too.

I noticed that it happens when I maximize the gnome-terminal window, but
not always: right now, I have another gnome-terminal, maximized, with 3
tabs, and the right-click (contextual) menu works well.

I also noticed that, when maximized and "demaximized" again, the right-
click menu shows with more space than needed (as shown in the
attachment).

** Attachment added: "Menu with big borders"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1731888/+attachment/5023017/+files/mnu.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/1731888

Title:
  right-click menu on the terminal gets broken when terminal window is
  maximized

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  Not sure if this bug was introduced by the upgrade from 17.04 to 17.10, as I 
am rarely using the terminal in maximized mode.
  Issue can be reproduced - happens each time, even after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 13 12:26:05 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-10 (33 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-10-20 (24 days ago)

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

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

[Desktop-packages] [Bug 1738419] Re: package libreoffice-common (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/lib/libreoffice/share/template/common/presnt/L

[Pietro Scarioni]

non capisco

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  impossibile copiare i dati estratti per
  "./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in
  "/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-
  new": fine del file o dello stream inattesa

Status in libreoffice package in Ubuntu:
  New

Bug description:
  ho cliccato applica in gestore pacchetti ed ha fatto tutto lui

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  Date: Fri Dec 15 14:23:59 2017
  ErrorMessage: impossibile copiare i dati estratti per 
"./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in 
"/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-new": 
fine del file o dello stream inattesa
  InstallationDate: Installed on 2017-11-07 (37 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
impossibile copiare i dati estratti per 
"./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in 
"/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-new": 
fine del file o dello stream inattesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738419] [NEW] package libreoffice-common (not installed) failed to install/upgrade: impossibile copiare i dati estratti per "./usr/lib/libreoffice/share/template/common/presnt

[Pietro Scarioni]

Public bug reported:

ho cliccato applica in gestore pacchetti ed ha fatto tutto lui

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libreoffice-common (not installed)
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic i686
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
Date: Fri Dec 15 14:23:59 2017
ErrorMessage: impossibile copiare i dati estratti per 
"./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in 
"/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-new": 
fine del file o dello stream inattesa
InstallationDate: Installed on 2017-11-07 (37 days ago)
InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: libreoffice
Title: package libreoffice-common (not installed) failed to install/upgrade: 
impossibile copiare i dati estratti per 
"./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in 
"/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-new": 
fine del file o dello stream inattesa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 zesty

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  impossibile copiare i dati estratti per
  "./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in
  "/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-
  new": fine del file o dello stream inattesa

Status in libreoffice package in Ubuntu:
  New

Bug description:
  ho cliccato applica in gestore pacchetti ed ha fatto tutto lui

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic i686
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  Date: Fri Dec 15 14:23:59 2017
  ErrorMessage: impossibile copiare i dati estratti per 
"./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in 
"/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-new": 
fine del file o dello stream inattesa
  InstallationDate: Installed on 2017-11-07 (37 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
impossibile copiare i dati estratti per 
"./usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp" in 
"/usr/lib/libreoffice/share/template/common/presnt/LushGreen.otp.dpkg-new": 
fine del file o dello stream inattesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738413] [NEW] speedlink LUCIDS keyboards ctrl alt keys recognised as shift key

[Lakner Máté]

Public bug reported:

Each keys in space row - except for space - recognised as shift key. In
GRUB it works perfectly fine, dual booted windows recognises them well.
The correct type of the keyboard is Speedlink SL-6432-BK-HU, hungarian
layout. Please, provide proper driver. Thank you.

Description:Ubuntu 16.04.3 LTS
Release:16.04

Package - Default provided

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Dec 15 14:17:28 2017
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+2297+202'"
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2017-08-16 (120 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  speedlink LUCIDS keyboards ctrl alt keys recognised as shift key

Status in nautilus package in Ubuntu:
  New

Bug description:
  Each keys in space row - except for space - recognised as shift key.
  In GRUB it works perfectly fine, dual booted windows recognises them
  well. The correct type of the keyboard is Speedlink SL-6432-BK-HU,
  hungarian layout. Please, provide proper driver. Thank you.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Package - Default provided

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Dec 15 14:17:28 2017
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+2297+202'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2017-08-16 (120 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738410] Re: baobab

[Launchpad Bug Tracker]

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

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

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

Title:
  baobab

Status in baobab package in Ubuntu:
  Confirmed

Bug description:
  Application icon shown in Lubuntu 17.10, e.g. with Alt+Tab, is of too
  low resolution. I can easily count the pixels, is something of 16, 22,
  24, 32 or in between pixels in width and height.

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

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

[Desktop-packages] [Bug 1738410] [NEW] baobab

[Pander]

Public bug reported:

Application icon shown in Lubuntu 17.10, e.g. with Alt+Tab, is of too
low resolution. I can easily count the pixels, is something of 16, 22,
24, 32 or in between pixels in width and height.

** Affects: baobab (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: artful

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

Title:
  baobab

Status in baobab package in Ubuntu:
  Confirmed

Bug description:
  Application icon shown in Lubuntu 17.10, e.g. with Alt+Tab, is of too
  low resolution. I can easily count the pixels, is something of 16, 22,
  24, 32 or in between pixels in width and height.

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

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

[Desktop-packages] [Bug 1733136] Re: wayland session in Ubuntu 18.04 chooses LLVMpipe software driver on hybrid graphics system

[Timo Aaltonen]

the archive version of libegl1 does _not_ depend on libglvnd0, so I
don't know where you got it from..

bionic will migrate to it once nvidia is ready, maybe in january

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

Title:
  wayland session in Ubuntu 18.04 chooses LLVMpipe software driver on
  hybrid graphics system

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I upgraded to 18.04 and I no longer get an option to run a wayland
  session (17.10 offered both the default ubuntu wayland session and
  xorg on this laptop).

  gnome-shell runs under the llvmpipe driver. (Unity used to run when I
  first upgraded, but now gnome-shell is the only option because the gdm
  login screen offers no login options.)

  The upgrade did force me to remove bumblebee and nvidia, but
  afterwards I manually reinstalled bumblebee and nvidia-387 and reset
  to using intel via prime-select (installing nvidia changes some of the
  symlinks so that gnome-shell no longer boots, but "sudo prime-select
  intel" fixes this).

  The nvidia-387 modules are blacklisted in /etc/modprobe.d, and
  bumblebee isn't reporting any errors - bbswitch reports that the
  nvidia card is off, so I don't think it's an issue with hybrid
  graphics. (primusrun does work, as well.)

  Attached are the mutter logs that I generated via the environment
  variables mentioned in
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583 comment
  #20. I suspect that the culprit is hinted at in this message:

  Window manager warning: Failed to create renderer: Failed to initialize 
renderer: Missing extensio
  n for GBM renderer: EGL_KHR_platform_gbm, Missing EGL extensions required for 
EGLDevice renderer:
  EGL_EXT_device_base

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

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

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

[Desktop-packages] [Bug 1733136] Re: wayland session in Ubuntu 18.04 chooses LLVMpipe software driver on hybrid graphics system

[Timo Aaltonen]

in any case, this is not a bug but something messed up in your
installation

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

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

Title:
  wayland session in Ubuntu 18.04 chooses LLVMpipe software driver on
  hybrid graphics system

Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I upgraded to 18.04 and I no longer get an option to run a wayland
  session (17.10 offered both the default ubuntu wayland session and
  xorg on this laptop).

  gnome-shell runs under the llvmpipe driver. (Unity used to run when I
  first upgraded, but now gnome-shell is the only option because the gdm
  login screen offers no login options.)

  The upgrade did force me to remove bumblebee and nvidia, but
  afterwards I manually reinstalled bumblebee and nvidia-387 and reset
  to using intel via prime-select (installing nvidia changes some of the
  symlinks so that gnome-shell no longer boots, but "sudo prime-select
  intel" fixes this).

  The nvidia-387 modules are blacklisted in /etc/modprobe.d, and
  bumblebee isn't reporting any errors - bbswitch reports that the
  nvidia card is off, so I don't think it's an issue with hybrid
  graphics. (primusrun does work, as well.)

  Attached are the mutter logs that I generated via the environment
  variables mentioned in
  https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583 comment
  #20. I suspect that the culprit is hinted at in this message:

  Window manager warning: Failed to create renderer: Failed to initialize 
renderer: Missing extensio
  n for GBM renderer: EGL_KHR_platform_gbm, Missing EGL extensions required for 
EGLDevice renderer:
  EGL_EXT_device_base

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

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

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

[Desktop-packages] [Bug 1572244] Re: Kubuntu requires that the WiFi password be entered twice before WiFi can be used

[Waz]

I was about to pass an exam, a powerpoint presentation, so the examiner
spelled me the wifi password and after pressing ok an other windows ask
for the wifi password! Quite embarrassing...

Is it a Kubuntu bug or Kde one ?

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

Title:
  Kubuntu requires that the WiFi password be entered twice before WiFi
  can be used

Status in network-manager package in Ubuntu:
  Confirmed
Status in plasma-nm package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics

[Cico Zhang]

I am using XPS 13 9360, it happens often that the login session goes
without wayland.

Here is the log I got from running journalctl /usr/bin/gnome-shell


Dec 15 12:45:45 cico-XPS-13-9360 gnome-shell[883]: Failed to apply DRM plane 
transform 0: Permission denied
Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: (EE)
Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: Fatal server 
error:
Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: (EE) wl_drm@4: 
error 0: authenicate failed
Dec 15 12:45:45 cico-XPS-13-9360 org.gnome.Shell.desktop[883]: (EE)
Dec 15 12:45:46 cico-XPS-13-9360 gnome-shell[883]: X Wayland crashed; aborting
Dec 15 12:45:47 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: 
[resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property 
"MetaStage"
Dec 15 12:45:47 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: 
[resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property 
"MetaWindowGroup"
Dec 15 12:45:47 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: 
[resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to 
undefined property "MetaDBusDisplayConfig
Dec 15 12:45:48 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: 
[resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property 
"CallyActor"
Dec 15 12:45:48 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: 
[resource:///org/gnome/gjs/modules/tweener/tweener.js 540]: reference to 
undefined property "isSpecialProperty"
Dec 15 12:45:48 cico-XPS-13-9360 gnome-shell[1030]: Error looking up 
permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.impl.portal.Per
Dec 15 12:45:48 cico-XPS-13-9360 org.gnome.Shell.desktop[1030]: Window manager 
warning: "XF86RFKill" is not a valid accelerator
Dec 15 12:45:49 cico-XPS-13-9360 gnome-shell[1030]: JS WARNING: 
[resource:///org/gnome/shell/ui/layout.js 29]: reference to undefined property 
"MetaWindowX11"
Dec 15 12:46:02 cico-XPS-13-9360 gnome-shell[1809]: Failed to read monitors 
config file '/home/cico/.config/monitors.xml': Logical monitor scales must be 
identical
Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: 
[resource:///org/gnome/shell/ui/main.js 315]: reference to undefined property 
"MetaStage"
Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: 
[resource:///org/gnome/shell/ui/layout.js 221]: reference to undefined property 
"MetaWindowGroup"
Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: 
[resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to 
undefined property "MetaDBusDisplayConfig
Dec 15 12:46:03 cico-XPS-13-9360 gnome-shell[1809]: JS WARNING: 
[resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property 
"CallyActor"

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

Title:
  gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid
  graphics

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

Bug description:
  I've just upgraded to Ubuntu 17.10 and switched the login manager from
  sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The
  /usr/share/xsessions folder indeed only contains the -xorg -related
  sessions:

  $ ls -la /usr/share/xsessions
  total 36
  drwxr-xr-x   2 root root  4096 okt 18 16:00 .
  drwxr-xr-x 427 root root 20480 okt 18 15:56 ..
  -rw-r--r--   1 root root   201 okt 13 12:56 gnome-xorg.desktop
  -rw-r--r--   1 root root  2354 aug 23 16:39 plasma.desktop
  -rw-r--r--   1 root root   262 okt 13 12:56 ubuntu-xorg.desktop

  How can I enable the ubuntu-wayland session please?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.26.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 18 16:37:47 2017
  InstallationDate: Installed on 2016-09-05 (408 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-10-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1723370] Re: Processes % CPU column is inaccurate (only ever an integer multiple of the number of CPUs)

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-system-monitor - 3.26.0-1ubuntu1

---
gnome-system-monitor (3.26.0-1ubuntu1) bionic; urgency=medium

  * debian/patches/git-fix-lp1723370.patch:
backport commit to fix inaccurate %CPU values in the Processes table
(LP: #1723370)

 -- Daniel van Vugt   Wed, 13 Dec 2017
16:42:47 +0800

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs)

Status in Gnome System Monitor:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs).

  So for example on my desktop with 8 CPU threads, the Processes tab
  only ever shows a process is using either 0%, 8%, 16%, 24%, 32%

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-system-monitor 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 13 17:18:24 2017
  InstallationDate: Installed on 2017-05-03 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1567742] Re: Cann't login to last.fm

[rithik g]

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

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

Title:
  Cann't login to last.fm

Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  I just cant login to last.fm account. The web says "Token expired. Please 
return to Rhythmbox and try again."
  Ubuntu 16.04

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

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

[Desktop-packages] [Bug 1365870] Re: Too little visual feedback during import

[rithik g]

please file a bug upstream at

https://bugzilla.gnome.org/enter_bug.cgi?product=rhythmbox

with all relevant information.

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

Title:
  Too little visual feedback during import

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  if I pick a directory in ubuntu for importing into the collection,
  there is too little UI feedback, sometimes just the import box/count
  remain dimmed; I would need feedback "no music in folder" or "all
  music already in library" or "there were errors, check import errors
  list".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep  5 09:09:18 2014
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (6 days ago)

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

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

[Desktop-packages] [Bug 1696231] Re: amdgpu needed blacklisting of radeon module

[MasterCATZ]

how can I get radeon and amdgpu to play nice with each other ? 
or better yet not use amdgpu and still be able to use opencl

I have a A10-5800K APU and R9 290

Ubuntu 16.04 / amdgpu-pro-17.40-492261



lspci -nnk | grep -i vga -A3 | grep 'in use'
Kernel driver in use: radeon
Kernel driver in use: amdgpu


amdgpu_device_initialize: DRM version is 2.50.0 but this driver is only 
compatible with 3.x.x.

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

Title:
  amdgpu needed blacklisting of radeon module

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I have installed a new Radeon card alongside the old one:
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Baffin [Polaris11] (rev cf)
  03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV730 PRO [Radeon HD 4650]

  Booted Ubuntu, and the console just froze when switching to graphics mode. I 
was not able to switch consoles with ctrl+alt+f1/ctrl+alt+f2, despite having 
NAutoVTs=6 in /etc/systemd/logind.conf.
  I could login via SSH, but all I could see is that X wasn't able to find any 
screens, but without any clues why:
  [11.142] (EE) No devices detected.

  Finally when running X -configure as root I got the following helpful log 
message before crashing:
  amdgpu_device_initialize: DRM version is 2.49.0 but this driver is only 
compatible with 3.x.x.

  After some searching I found that I should blacklist the radeon module
  to get the amdgpu module working, and indeed adding this file fixed
  it:

  /etc/modprobe.d/blacklist-radeon.conf 
  # cannot load  both amdgpu and radeon
  blacklist radeon

  Then: sudo update-initramfs -u -k all

  Another workaround is to remove the old graphics card, that made
  booting work again.

  I think there is a bug here though: X shouldn't crash: it should be
  able to use at least one of the two graphics card drivers, and the
  text console should still be operational even if it failed to
  initialize graphical mode, so that the user can log in, investigate
  and fix things from a local console, instead of relying on fixing
  things over SSH.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Jun  5 20:44:06 2017
  ExecutablePath: /usr/lib/xorg/Xorg
  ExecutableTimestamp: 1490632988
  InstallationDate: Installed on 2017-03-25 (71 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1)
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcCwd: /
  ProcEnviron: PATH=(custom, no user)
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x556cb5e47590, argc=11, argv=0x7ffca36148c8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffca36148b8) at ../csu/libc-start.c:291
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1600606] Re: Totem is missing the playlist. Please reintroduce it.

[Luís de Sousa]

Totem is hopelessly broken, this application is no longer up to the
standards Ubuntu has grown us used to.

The best solution is to install a fork of a functional Totem version like 
xplayer:
https://launchpad.net/~embrosyn/+archive/ubuntu/xapps

Cheers.

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

Title:
  Totem is missing the playlist. Please reintroduce it.

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 16.04 Totem is no longer displays the video
  playlist in the side panel. As in previous Ubuntu releases, the side
  panel is disabled by default, but in this release the View menu is
  missing the Sidebar item in this later release.

  The Sibedar item should restored to the View menu.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 10 16:06:21 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-05 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1738386] [NEW] [N501VW, Realtek ALC668, Black Headphone Out, Right] Underruns, dropouts or crackling sound

[Etienneo]

Public bug reported:


1. This bug happens everytime my computer wake up from sleep: a loud crackling 
noise can be heard from headphones but not from laptop speakers
2. It disappears after reboot and audio works perfectly both through laptop 
speakers and headphones
3. Bringing the output volume to 0 doesn't make the crackling sound disappear
4. Bringing microphone volume to 0 doesn't make the crackling sound disappear
5. This bug was not present in the previous version of Ubuntu used on this 
computer ie. 17.04.

Additionnaly, headphones contain a built-in microphone.

```lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
```

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   etienne5390 F...m pulseaudio
 /dev/snd/controlC0:  etienne5390 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec 15 10:44:27 2017
InstallationDate: Installed on 2017-05-22 (206 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
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_Jack: Black Headphone Out, Right
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Underruns, dropouts 
or crackling sound
UpgradeStatus: Upgraded to artful on 2017-11-26 (18 days ago)
dmi.bios.date: 11/28/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
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.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N501VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  [N501VW, Realtek ALC668, Black Headphone Out, Right] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  
  1. This bug happens everytime my computer wake up from sleep: a loud 
crackling noise can be heard from headphones but not from laptop speakers
  2. It disappears after reboot and audio works perfectly both through laptop 
speakers and headphones
  3. Bringing the output volume to 0 doesn't make the crackling sound disappear
  4. Bringing microphone volume to 0 doesn't make the crackling sound disappear
  5. This bug was not present in the previous version of Ubuntu used on this 
computer ie. 17.04.

  Additionnaly, headphones contain a built-in microphone.

  ```lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   etienne5390 F...m pulseaudio
   /dev/snd/controlC0:  etienne5390 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 15 10:44:27 2017
  InstallationDate: Installed on 2017-05-22 (206 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  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_Jack: Black Headphone Out, Right
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Underruns, 
dropouts or crackling sound
  UpgradeStatus: Upgraded to artful on 2017-11-26 (18 days ago)
  dmi.bios.date: 11/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.
  

[Desktop-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[Shaheed Haque]

The workaround in #4 works-for-me.

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

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

[Jens Forker]

update to my entry #47:
installed ubuntu 18.04 daily build from Dec 11, 2017 on the Lenovo IdeaPad/Yoga 
2 13 with touch screen. For one day everything went fine except one single 
appearance of the on screen keyboard (osk). On the second day the osk got 
crazy, appearing that frequently that working with the mouse or touch screen 
was practically impossible. But the cursor didn't jump (to lower left corner) 
as it did with 17.04 and 17.10.
The osk sometimes flickered really fast giving the impression of being turned 
on/off at least 10x/second - without me touching anything on the laptop!
Then I applied the fix provided by https://askubuntu.com/users/750621/keringar 
(Thank you!!) and now I can use the laptop again.
Testing continues

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

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

Bug description:
  Impact
  ==
  I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is 
disabled in System Preferences > Universal Access.  This didn't happen in any 
previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based.

  Test Case
  =
  0. Find a laptop with a touch screen that works.
  1. Settings > Universal Access > Typing > Screen Keyboard = OFF
  2. Touch the screen.

  Regression Potential
  

  Workaround
  ==
  https://extensions.gnome.org/extension/1326/block-caribou/

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

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

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

@NoOne: No need to mess with priority settings. Instead of running

sudo apt upgrade

run

sudo apt install gir1.2-gweather-3.0 libgweather-3-6 libgweather-common

and then disable -proposed again.

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  In Progress
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Committed
Status in libgweather source package in Zesty:
  Fix Committed
Status in libgweather source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

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

[Apport retracing service]

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

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 #1706097, 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/1738377/+attachment/5022915/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** 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 gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1738377

Title:
  gvfsd-mtp crashed with SIGSEGV

Status in gvfs package in Ubuntu:
  New

Bug description:
  Eventually Happens when I plug in my android phone

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gvfs-backends 1.34.1-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Dec 15 08:20:00 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-mtp
  InstallationDate: Installed on 2014-08-13 (1219 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/4
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7efd2772f5a9:mov0x18(%rax),%rax
   PC (0x7efd2772f5a9) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gvfsd-mtp crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1045790] Re: Rendering error on OCAL website

[Sebastien Bacher]

** Changed in: librsvg (Ubuntu)
   Status: New => Triaged

** Changed in: librsvg (Ubuntu)
   Importance: Undecided => High

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

Title:
  Rendering error on OCAL website

Status in librsvg:
  Expired
Status in openclipart:
  Invalid
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  I uploaded an SVG that is a map of the UK and Ireland
  http://openclipart.org/detail/171939/uk-and-ireland-by-
  hellocatfood-171939 It was generated in Inkscape and then cleaned up
  using SVG Cleaner

  In Inkscape, GIMP and the Firefox SVG preview it displays correctly,
  but on OCAL it looks very weird!

  Steps to reproduce:
  Download the original SVG 
https://bugs.launchpad.net/librsvg/+bug/1045790/+attachment/3302221/+files/uk-ireland-vector_original.svg
  Download and install SVG Cleaner https://github.com/RazrFalcon/SVGCleaner/
  Run SVG Cleaner on the folder containing the SVG
  Look at the thumbnail preview on programs that use librsvg (Open Clip Art 
Library, Nautilus)

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

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

[Desktop-packages] [Bug 1737993] Re: Gnome-shell segfault and returns to login screen

[Thibault Roche]

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

Thanks for the input and for your help.

It seems to lead me to bug 1714989, so I'll check things there.

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

Title:
  Gnome-shell segfault and returns to login screen

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Since my upgrade to ubuntu 17.10 (and therefore usage of gnome-shell
  instead of unity), I have regular crashes of gnome-shell where I
  return to the login screen. I don't have a reproduction scenario, it
  appears to happen at random times, sometimes multiple times a day when
  some other days everything is fine.

  Everytime, I have this line in my kern.log : 
  Dec 13 15:48:23 plw-fr-troche kernel: [22168.253619] gnome-shell[16768]: 
segfault at 7fdafa227114 ip 7fdbb5943bb1 sp 7ffdc85c7d80 error 7 in 
libst-1.0.so[7fdbb5925000+4b000]

  The segfault always refers to libst.

  I work as a developer and tend to use some applications that take
  quite a lot of memory.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 13 15:49:10 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-08-24 (476 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-03 (40 days ago)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-08-24 (477 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-11-03 (40 days ago)
  UserGroups: adm lpadmin sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1710370] Re: Cheese crashes on launch in Ubuntu 17.10 if no camera device is present

[Sebastien Bacher]

** Changed in: cheese (Ubuntu)
   Importance: Undecided => High

** Changed in: cheese (Ubuntu)
   Status: New => Triaged

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

Title:
  Cheese crashes on launch in Ubuntu 17.10 if no camera device is
  present

Status in Cheese:
  Confirmed
Status in cheese package in Ubuntu:
  Triaged

Bug description:
  Cheese crashes on launch in Ubuntu 17.10 if the computer does not have
  any camera device connected.

  
  (cheese:3620): cheese-CRITICAL **: cheese_camera_device_get_name: assertion 
'CHEESE_IS_CAMERA_DEVICE (device)' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_new_string: assertion
  'string != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_ref_sink: assertion 'value
  != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_schema_key_type_check:
  assertion 'value != NULL' failed

  (cheese:3620): GLib-CRITICAL **: g_variant_get_type_string: assertion
  'value != NULL' failed

  (cheese:3620): GLib-GIO-CRITICAL **: g_settings_set_value: key
  'camera' in 'org.gnome.Cheese' expects type 's', but a GVariant of
  type '(null)' was given

  (cheese:3620): GLib-CRITICAL **: g_variant_unref: assertion 'value !=
  NULL' failed

  ** (cheese:3620): CRITICAL **:
  cheese_preferences_dialog_setup_resolutions_for_device: assertion
  'device != NULL' failed

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

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

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

[Sebastien Bacher]

The new libgphoto2 which includes the fix has been uploaded to the current serie
https://launchpad.net/ubuntu/+source/libgphoto2/2.5.16-1

That fix is probably worth a SRU for 17.10 as well if somebody wants to
work on that (https://wiki.ubuntu.com/StableReleaseUpdates)

** Package changed: gphoto2 (Ubuntu) => libgphoto2 (Ubuntu)

** Changed in: libgphoto2 (Ubuntu)
   Importance: Undecided => High

** Changed in: libgphoto2 (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: shotwell (Ubuntu)
   Importance: Undecided => High

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

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

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

Status in libgphoto2 package in Ubuntu:
  Fix Committed
Status in shotwell package in Ubuntu:
  Invalid

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

  lsusb gives:

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

  dmesg gives:

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: shotwell 0.26.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  9 21:36:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-03 (494 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago)

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

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

[Desktop-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile

[Sebastien Bacher]

thanks Daniel, let's see what the feedback is after the new version
lands

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Bluetooth speaker used the HSP/HFP profile by default rather than the
  higher-quality A2DP profile

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Kubuntu 17.04
  Bluetooth device: 
https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1
 (itentifies itself as "C6")

  The above Bluetooth speaker paired and started streaming audio
  perfectly in Kubuntu 17.04. But the audio quality was poor, because
  the default audio profile was the low-quality HSP/HFP one. When I
  switched it to the A2DP profile, it sounded perfect again.

  Can we make A2DP the default playback profile for Bluetooth audio
  devices?

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

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

[Desktop-packages] [Bug 1723370] Re: Processes % CPU column is inaccurate (only ever an integer multiple of the number of CPUs)

[Sebastien Bacher]

Thanks Daniel, I renamed the patch to prefix it with git- since it has
been commited upstream (it helps to know what's the status of the patch
when doing the next update) and uploaded

** Changed in: gnome-system-monitor (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs)

Status in Gnome System Monitor:
  Fix Released
Status in gnome-system-monitor package in Ubuntu:
  Fix Committed

Bug description:
  Processes % CPU column is inaccurate (only ever an integer multiple of
  the number of CPUs).

  So for example on my desktop with 8 CPU threads, the Processes tab
  only ever shows a process is using either 0%, 8%, 16%, 24%, 32%

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-system-monitor 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 13 17:18:24 2017
  InstallationDate: Installed on 2017-05-03 (163 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Omk]

I have this same issue on Dell XPS 13.
Mouse pointer jumps intermittently to the lower left corner. When typing, the 
cursor occasionally jumps to the middle of the sentence. And occasionally the 
mouse pointer just freezes, and does not move at all using the trackpad, unless 
I simultaneously click and hold down the button, while dragging the pointer 
around with the trackpad. Sometimes Alt+TAB to another program may revive the 
mouse, and at others, have to close the lid, suspend and awake to re-activate 
the mouse. Very annoying, making the laptop practically unusable.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  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: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Desktop-packages] [Bug 1516531] Re: Fullscreen Freeze.

[Martin]

My system was always freezing when I was using chrome or chromium in
fullscreen (F11). After disabling "unredirect windows" with ccsm, it
seems to be fixed.

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

Title:
  Fullscreen Freeze.

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Related?:
  
http://askubuntu.com/questions/692405/ubuntu-15-10-unity-freezes-after-escaping-full-screen-video
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622

  I've been having cases of unusual screen behavior, particularly when Kodi 16 
is being used (maybe it's just a Kodi thing).
  There have been times before when coming out of fullscreen video using either 
Chrome or Kodi would drop me to a console screen with no input.
  I think I would be able to kill the gnome session in tty1.

  Now, after a bios upgrade as well as the latest display manager and kernel 
update, Kodi has frozen in fullscreen a couple of times and yet audio will 
still play from Kodi.
  I created the bug report in tty1.

  I've also been noticing that if I pause a Kodi video, other non-Kodi 
applications may not update their window content.
  For example, I may be in a webpage in Chrome and I try to mousewheel scroll, 
yet not see the scrolling effect. Or I will click on a different tab and the 
window doesn't show the switch. BUT, if I continue playing the Kodi video, 
Chrome will update it's screen, and if I switch back to the tab I scrolled, the 
scroll will have already occurred.

  I will say that I have at least not had a fullscreen GUI crash me out
  to console.

  Another peculiarity is when booting Ubuntu, I used to be able to press ESC to 
view the kernel/system booting output, but now it just shows a black screen 
with a cursor.
  The downside to that in 15.04 was I'd lose my mouse cursor when the GUI login 
screen came up.

  Let me know what other output you'd like (or whatever test you'd like me to 
try) "when" it happens again.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:041e]
  InstallationDate: Installed on 2015-10-28 (26 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash elevator=cfq 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 07/27/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H97M-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97M-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  

[Desktop-packages] [Bug 469481] Re: Rhythmbox visualizations appear frozen

[rithik g]

visualizer plugin has been removed in rhythmbox 3.4.2

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

Title:
  Rhythmbox visualizations appear frozen

Status in Rhythmbox:
  Expired
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  Visualizations appear to -start- in Ubuntu 9.10's version of
  Rhythmbox, but on my system they only get as far as a single frame and
  don't display any more than that. Rhythmbox itself does not appear to
  be crashing as visualizations can be turned back off and on again, but
  they'll never actually appear in motion. This was not an issue on the
  same system running 9.04.

  ProblemType: Bug
  Architecture: i386
  Date: Sun Nov  1 17:31:42 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/rhythmbox
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.12.5-0ubuntu4
  ProcEnviron:
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-14-generic i686

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

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

[Desktop-packages] [Bug 534553] Re: Rhythmbox visualization freezes when one song finishes and another of the same format starts

[rithik g]

visualizer plugin has been removed in rhythmbox 3.4.2

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

Title:
  Rhythmbox visualization freezes when one song finishes and another of
  the same format starts

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  Rhythm boxes visualization freezes after playing one song.

  To reproduce:
  1. Open rhythmbox and add at least 2 songs to the play queue (some of the 
tests will need four or five).
  2. Turn on the visualization.
  3. Wait for the first song to finish playing (or even skip to close to the 
end).
  4. Notice that the visualization freezes, even though the second song has 
started.
  5. Click the visualization button on and off and notice the visualization is 
still frozen, but changes every time you cycle the visualization button.
  6. Clear the play queue and start a song (if one doesn't start automatically).
  7. Notice that the visualization runs faster than normal.
  8. Close rhythmbox.

  9. Repeat steps 1-3, except press the next button right before the end of the 
first song and notice that visualization doesn't freeze when the next (second) 
song starts. At the end of this next song, notice the visualization doesn't 
freeze on the third or any subsequent songs, except between albums.
  10. Close rhythmbox.

  11. Repeat steps 1-5, stopping with the visualization enabled.
  12. Click next.
  13. Notice the visualization unfreezes (and of course, you are taken to the 
next song), and that no subsequent song changes cause the visualization to 
freeze, except between albums.

  ProblemType: Bug
  Architecture: amd64
  CheckboxSubmission: a869e808e24f1cd12a0b9ddfb6a9e84b
  CheckboxSystem: fd6c484c0b5d20a2f1cd036ef0f63975
  Date: Mon Mar  8 09:58:58 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: nvidia
  Package: rhythmbox 0.12.5-0ubuntu5.2
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/zsh
   LANG=en_US.UTF-8
   LC_CTYPE=C
  ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
  SourcePackage: rhythmbox
  Uname: Linux 2.6.31-20-generic x86_64

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

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

[Desktop-packages] [Bug 619000] Re: fullscreen visualization freezes when seeking in a song

[rithik g]

visualizer plugin has been removed in rhythmbox 3.4.2

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

Title:
  fullscreen visualization freezes when seeking in a song

Status in Rhythmbox:
  New
Status in rhythmbox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  Turn on visualization on Rhythmbox while a song is playing, then make
  it fullscreen, click the disable button, skip to another part of the
  song, and turn visualization back on. The visualization is frozen and
  the song stops playing until the disable button is clicked. This
  doesn't seem to happen when visualization is not in fullscreen.

  Ubuntu 10.10
  Rhythmbox 0.13.1

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

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