[Desktop-packages] [Bug 1660353] Re: thumbnails disappear when scrolling in thumbnails pane

[Václav Haisman]

I still see this with Evince 3.24.0 on Zesty.

** Tags added: zesty

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

Title:
  thumbnails disappear when scrolling in thumbnails pane

Status in Evince:
  Fix Released
Status in evince package in Ubuntu:
  Triaged

Bug description:
  1. open a many-page (at least 15 pages) document
  2. open the thumbnails pane
  3. click on a thumbnail
  4. scroll up and down until the thumbnails (including outlines disappear)

  Obviously, we expect for the thumbnails to stay visible.  To make then
  visible again, move the pointer to the main document window, and then
  back to the thumbnails. Each one will reappear as you move the pointer
  over it.

  This is not the same as bug 1369028 as evince does not hang.
  This is not the same as bug 1629633, as there is still a thumbnail border for 
that document, and under no circumstances will the thumbnail appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 30 15:36:40 2017
  InstallationDate: Installed on 2014-10-13 (840 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: evince
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (108 days ago)

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

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

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

[Simon Quigley]

This honestly is an awful bug that I really really want to see fixed.

I'll play with some fixes.

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

** Changed in: gvfs (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: gvfs (Ubuntu)
   Status: New => In Progress

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

Title:
  cut-n-paste move files got stuck forever

Status in caja package in Ubuntu:
  New
Status in gvfs package in Ubuntu:
  In Progress
Status in nautilus package in Ubuntu:
  Incomplete
Status in pcmanfm package in Ubuntu:
  Incomplete

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

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

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

[Desktop-packages] [Bug 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gedit edit window  is transparent when using Ambiance and Radiance
  themes

Status in gedit package in Ubuntu:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Expired

Bug description:
  In a freshly booted and fully updated Ubuntu 16.10 the edit window of
  gedit is transparent using the *Classic* colour scheme. Other colour
  schemes seem to work as intended.

  The text of loaded files shows against the desktop wallpaper but when
  no files are loaded gedit displays its edit window or pane as it
  should do.

  To clarify this bug is only apparent when a file is loaded.

  I don't know when this started as I don't normally used gedit to edit
  files. I haven't found any other application affected by this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gedit 3.20.2-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep  6 21:01:35 2016
  InstallationDate: Installed on 2016-03-11 (179 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Karl Schindler]

old and still not fixed:
(SWT:7981): GLib-CRITICAL **: Source ID 383 was not found when attempting to 
remove it

Ubuntu 16.10 kernel 4.11.8-041108-generic

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

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

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

[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

[Andrew Bumbarger]

** Changed in: gnome-software (Ubuntu)
 Assignee: Joo Heung Lee (jooheunglee) => Andrew Bumbarger (andrewbumbarger)

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

Title:
  Cannot install Debian files outside of the repositories

Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  https://www.google.com/chrome/
  https://itch.io/app

  b. Open the .deb with gnome-software
  gnome-software --local-filename=itch_23.2.1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  Click Install and verify that the app is installed.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1672424/+subscriptions

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

[Desktop-packages] [Bug 397412] Re: brasero fails when burning DVD

[Paweł]

Same bug here. Also, brasero is leaving behind a lot of temporary files
after session is closed with this error:

j ~ ❯❯❯ ls /tmp | grep brasero
brasero-session.log
brasero_tmp_22JU4Y
brasero_tmp_55ZT4Y.md5
brasero_tmp_7FJH4Y
brasero_tmp_9L2R4Y.bin
brasero_tmp_A4JU4Y
brasero_tmp_E3JU4Y
brasero_tmp_EJLI4Y.bin
brasero_tmp_FU0S4Y
brasero_tmp_GT0S4Y
brasero_tmp_I25P4Y.bin
brasero_tmp_IW0S4Y.bin
brasero_tmp_OGJH4Y
brasero_tmp_QMLI4Y
brasero_tmp_STBJ4Y.md5
brasero_tmp_TFJH4Y
brasero_tmp_W6LJ4Y
brasero_tmp_WMLI4Y
brasero_tmp_X6XU4Y
brasero_tmp_XU0S4Y
brasero_tmp_ZVLI4Y

** Attachment added: "Log with the error"
   
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/397412/+attachment/4926860/+files/brasero-session.log

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

Title:
  brasero fails when burning DVD

Status in brasero package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: brasero wodim

  brasero 2.26.1 on ubuntu 9.04 jaunty, all updates applied as of July
  09, 2009.

  DVD ISO images, both DVD-Video and DVD-ROM images, fail to burn, data
  discs created in brasero also fail. A sample brasero log follows, in
  this instance the image was of a 4.1Gb DVD-Video. I have been living
  with this problem since upgrading from ubuntu 8.10 (in which brasero
  worked fine).

  I dual-boot with Windows XP and the same image writes ok using Nero on
  the same hardware, using media from the same spindle.

  ---brasero log start---
  Checking session consistency (brasero_burn_check_session_consistency 
burn.c:1905)
  BraseroBurnURI called brasero_job_get_action
  BraseroBurnURI called brasero_job_get_action
  BraseroBurnURI called brasero_job_set_output_size_for_current_track
  BraseroBurnURI stopping
  BraseroBurnURI called brasero_job_get_action
  BraseroBurnURI called brasero_job_get_session_output_size
  BraseroBurnURI output set (IMAGE) image = /tmp/brasero_tmp_PBU5WU.bin toc = 
none
  BraseroBurnURI called brasero_job_get_action
  BraseroBurnURI called brasero_job_get_current_track
  BraseroBurnURI called brasero_job_get_input_type
  BraseroBurnURI no burn:// URI found
  BraseroBurnURI stopping
  BraseroWodim called brasero_job_get_action
  BraseroWodim getting varg
  BraseroWodim called brasero_job_get_action
  BraseroWodim got varg:
  BraseroWodim deactivating
  BraseroWodim called brasero_job_get_action
  BraseroWodim getting varg
  BraseroWodim called brasero_job_get_action
  BraseroWodim called brasero_job_get_device
  BraseroWodim called brasero_job_get_flags
  BraseroWodim called brasero_job_get_speed
  BraseroWodim called brasero_job_get_flags
  BraseroWodim called brasero_job_get_input_type
  BraseroWodim called brasero_job_get_fd_in
  BraseroWodim called brasero_job_get_current_track
  BraseroWodim called brasero_job_set_current_action
  BraseroWodim got varg:
wodim
-v
dev=/dev/sr0
speed=8
driveropts=burnfree
-dao
fs=16m
-data
-nopad
/home/noel/Desktop/dvd.iso
  BraseroWodim Launching command
  BraseroWodim called brasero_job_get_fd_out
  BraseroWodim stderr: wodim: Operation not permitted. Warning: Cannot raise 
RLIMIT_MEMLOCK limits.scsidev: '/dev/sr0'
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: devname: '/dev/sr0'
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: scsibus: -2 target: -2 lun: -2
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Linux sg driver version: 3.5.27
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Wodim version: 1.1.9
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: SCSI buffer size: 64512
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: Beginning DMA speed test. Set CDR_NODMATEST environment 
variable if device
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stderr: communication breaks or freezes immediately after that.
  BraseroWodim called brasero_job_get_flags
  BraseroWodim stdout: TOC Type: 1 = CD-ROM
  BraseroWodim stdout: Driveropts: 'burnfree'
  BraseroWodim stdout: Device type: Removable CD-ROM
  BraseroWodim stdout: Version: 5
  BraseroWodim stdout: Response Format: 2
  BraseroWodim stdout: Capabilities   : 
  BraseroWodim stdout: Vendor_info: 'PIONEER '
  BraseroWodim stdout: Identification : 'DVD-RW  DVR-217 '
  BraseroWodim stdout: Revision   : '1.05'
  BraseroWodim stdout: Device seems to be: Generic mmc2 DVD-R/DVD-RW.
  BraseroWodim stdout: Current: 0x0011 (DVD-R sequential recording)
  BraseroWodim stdout: Profile: 0x002B (DVD+R/DL) 
  BraseroWodim stdout: Profile: 0x001B (DVD+R) 
  BraseroWodim stdout: Profile: 0x001A (DVD+RW) 
  BraseroWodim stdout: Profile: 0x0016 (DVD-R/DL layer jump recording) 
  BraseroWodim stdout: Profile: 0x0015 (DVD-R/DL sequential recording) 
  BraseroWodim stdout: Profile: 

[Desktop-packages] [Bug 1468786] Re: libgrip FTBFS with newer GTK

[Bug Watch Updater]

** Changed in: libgrip (Debian)
   Status: Confirmed => Fix Released

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

Title:
  libgrip FTBFS with newer GTK

Status in libgrip:
  Fix Committed
Status in libgrip package in Ubuntu:
  Fix Released
Status in libgrip package in Debian:
  Fix Released

Bug description:
  The package fails to build:
  gesture.c: In function ‘create_window’:
  gesture.c:219:3: error: ‘gtk_widget_override_background_color’ is deprecated 
(declared at
  /usr/include/gtk-3.0/gtk/gtkwidget.h:1157) [-Werror=deprecated-declarations]
 gtk_widget_override_background_color (app->da, GTK_STATE_NORMAL, );
 ^
  cc1: all warnings being treated as errors

  An alternative build log:
  https://reproducible.debian.net/rb-pkg/unstable/amd64/libgrip.html

   affects libgrip
   assignee bregma
   status inprogress
   importance medium

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

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

[Desktop-packages] [Bug 1599874] Re: no rear sound creative sound blaster Z ssid: 1102:0023

[aidanjt]

I'm having the same problem with PCI ID 1102:0012 & sub ID 1102:0010.
It's a SB Z OEM (no fancy shroud).

** Attachment added: "alsainfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1599874/+attachment/4926853/+files/alsainfo.txt

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

Title:
   no rear sound creative sound blaster Z ssid: 1102:0023

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  it's long standing bug we can't use Z series cards properly on linux 
  only front panel work 
  rest of ports are not working

  I extracted latest firmware from windows driver but no luck 
  here are extra details from windows and freebsd drivers both are works fine

  freebsd pin configs;
  hdaa0: Patched pins configuration:
  hdaa0: nid   0xas seq device   conn  jackloccolor   misc
  hdaa0: 11 410140f0 15 0  Line-out  None  1/8 Rear   Green   0 DISA
  hdaa0: 12 014520f0 15 0  SPDIF-out Jack  Optical Rear   Grey0
  hdaa0: 13 010170f0 15 0  Line-out  Jack  1/8 Rear   Yellow  0
  hdaa0: 14 01c510f0 15 0  SPDIF-in  Jack  Optical Rear   Black   0
  hdaa0: 15 412000f0 15 0  HeadphonesNone  Unknown Rear   Unknown 0 DISA
  hdaa0: 16 022140f0 15 0  HeadphonesJack  1/8 Front  Green   0
  hdaa0: 17 418120f0 15 0  Line-in   None  1/8 Rear   Grey0 DISA
  hdaa0: 18 01a190f0 15 0  Mic   Jack  1/8 Rear   Pink0
  hdaa0: 19 50d000f0 15 0  Digital-inNone  Unknown Internal   Unknown 0 DISA
  hdaa0: 24 50f0 15 0  Line-out  None  Unknown Internal   Unknown 0 DISA

  pin configs from windows driver
  NID: 11
  Node: 0x0b
  Pin: 0x410140f0
  Verb 00B71CF0 00B71D40 00B71E01 00B71F41 

  NID: 12
  Node: 0x0c
  Pin: 0x014520f0
  Verb 00C71CF0 00C71D20 00C71E45 00C71F01 

  NID: 13
  Node: 0x0d
  Pin: 0x010171f0
  Verb 00D71CF0 00D71D71 00D71E01 00D71F01 

  NID: 14
  Node: 0x0e
  Pin: 0x01c510f0
  Verb 00E71CF0 00E71D10 00E71EC5 00E71F01 

  NID: 15
  Node: 0x0f
  Pin: 0x412000f0
  Verb 00F71CF0 00F71D00 00F71E20 00F71F41 

  NID: 16
  Node: 0x10
  Pin: 0x022140f0
  Verb 01071CF0 01071D40 01071E21 01071F02 

  NID: 17
  Node: 0x11
  Pin: 0x418120f0
  Verb 01171CF0 01171D20 01171E81 01171F41 

  NID: 18
  Node:0x12
  Pin:0x01a190f0
  Verb 01271CF0 01271D90 01271EA1 01271F01 

  NID: 19
  Node:0x13
  Pin:0x50d000f0
  Verb 01371CF0 01371D00 01371ED0 01371F50 

  NID: 24
  Node:0x18
  Pin:0x50f0
  Verb 01871CF0 01871D00 01871E00 01871F50

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  olci   1701 F pulseaudio
   /dev/snd/controlC0:  olci   1701 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  7 16:48:52 2016
  InstallationDate: Installed on 2016-06-25 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.12
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 7 (MS-7916)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd02/16/2016:svnMSI:pnMS-7916:pvr1.0:rvnMSI:rnZ97GAMING7(MS-7916):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7916
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

[aidanjt]

I'm having the same problem with PCI ID 1102:0012 & sub ID 1102:0010.
It's a SB Z OEM (no fancy shroud).

** Attachment added: "alsainfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1166529/+attachment/4926854/+files/alsainfo.txt

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 1708528] Re: Chrome web apps added to desktop are missing icons

[Daniel van Vugt]

The desktop icons actually aren't part of gnome-shell. It's nautilus-
desktop, which may also go away in future releases (!) It's also an
X11-only app so depends on Xwayland (!)

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

** Tags added: gnome-17.10

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

Title:
  Chrome web apps added to desktop are missing icons

Status in nautilus package in Ubuntu:
  New

Bug description:
  In Google chrome (and chromium from the archive) it's possible to add
  a desktop icon (like a webapp) via kebab menu -> more tools -> Add to
  desktop.

  This adds a launcher on the desktop and to the menu. On other desktops
  (such as Unity) this works as expected.

  On an up to date Ubuntu Artful the icon on the desktop launcher is
  missing. The icon in the launcher is fine however.

  This video demonstrates it:-
  https://www.youtube.com/watch?v=SbZwh8zshAI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 20:02:01 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['clock-overr...@gnomeshell.kryogenix.org']"
   b'org.gnome.shell' b'command-history' b"['gnome-control-center']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-08-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1708528] [NEW] Chrome web apps added to desktop are missing icons

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In Google chrome (and chromium from the archive) it's possible to add a
desktop icon (like a webapp) via kebab menu -> more tools -> Add to
desktop.

This adds a launcher on the desktop and to the menu. On other desktops
(such as Unity) this works as expected.

On an up to date Ubuntu Artful the icon on the desktop launcher is
missing. The icon in the launcher is fine however.

This video demonstrates it:- https://www.youtube.com/watch?v=SbZwh8zshAI

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug  3 20:02:01 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' 
b"['clock-overr...@gnomeshell.kryogenix.org']"
 b'org.gnome.shell' b'command-history' b"['gnome-control-center']"
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-08-02 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session
-- 
Chrome web apps added to desktop are missing icons
https://bugs.launchpad.net/bugs/1708528
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nautilus in Ubuntu.

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

[Desktop-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: 

[Desktop-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: 

[Desktop-packages] [Bug 1708562] Re: Xorg crashed with SIGABRT in OsAbort()

[Apport retracing service]

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

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 #1543192, 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/1708562/+attachment/4926812/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort() ["no screens found"]

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1708562

Title:
  Xorg crashed with SIGABRT in OsAbort()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is a somewhat flaky hybrid system (the hardware is fine, but the
  Ubuntu hybrid detection & setup fails and I need to manually write an
  xorg.conf)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: xserver-xorg-core 2:1.19.3-1ubuntu2
  ProcVersionSignature: Ubuntu 
4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic 4.11.3
  Uname: Linux 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Thu Aug  3 19:42:05 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
   bbswitch, 0.8, 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic, x86_64: 
installed
   nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic, 
x86_64: installed
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
   NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev ff) 
(prog-if ff)
  MachineType: System76 Oryx Pro
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/125/gdm/Xauthority -background none -noreset -keeptty -verbose 7 -core
  ProcEnviron:
   
  ProcKernelCmdLine: 
BOOT_IMAGE=/vmlinuz-4.11.3+bcachefs.git20170608.87a9a6efd0ab-1-generic 
root=UUID=912b1771-d5ce-4e19-955b-f60f617ef8ad ro fbcon=map:1 splash quiet 
vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x560084436590, argc=13, argv=0x7fff80e5f948, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff80e5f938) at ../csu/libc-start.c:291
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 

[Desktop-packages] [Bug 1708561] [NEW] netflix does not work Mozilla 54.0

[Fauze]

Public bug reported:

Netflix does not work Mozilla 54.0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 54.0+build3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  familia_toshiba   1462 F pulseaudio
BuildID: 20170612123102
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Aug  3 21:33:11 2017
ForcedLayersAccel: False
IfupdownConfig:
 auto lo
 iface lo inet loopback
IncompatibleExtensions:
 English (GB) Language Pack - langpack-en...@firefox.mozilla.org
 Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
 English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
 Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
 Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2015-04-27 (829 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IpRoute:
 default via 192.168.0.1 dev eth0  proto static  metric 600 
 192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.100  metric 
600
MostRecentCrashID: bp-7c60b329-9f17-4ca9-8867-a1e401170730
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=54.0/20170612123102 (In use)
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs:
 bp-7c60b329-9f17-4ca9-8867-a1e401170730
 bp-a10060bb-9c0a-488d-b739-716e21170730
 bp-73bbed15-141b-467c-b4c1-a02f21170730
 bp-5800-63b6-44cf-a44b-34fa71170730
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2005
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.80
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 8
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.80:bd08/11/2005:svnTOSHIBA:pnSatelliteM45:pvrPSM40U-07X001:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct8:cvrVersion1.0:
dmi.product.name: Satellite M45
dmi.product.version: PSM40U-07X001
dmi.sys.vendor: TOSHIBA

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


** Tags: apport-bug i386 third-party-packages xenial

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

Title:
  netflix does not work Mozilla 54.0

Status in firefox package in Ubuntu:
  New

Bug description:
  Netflix does not work Mozilla 54.0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 54.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  familia_toshiba   1462 F pulseaudio
  BuildID: 20170612123102
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Aug  3 21:33:11 2017
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Português Brasileiro Language Pack - langpack-pt...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Português Portugal Language Pack - langpack-pt...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2015-04-27 (829 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static  metric 600 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.100  metric 
600
  MostRecentCrashID: bp-7c60b329-9f17-4ca9-8867-a1e401170730
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612123102 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  SubmittedCrashIDs:
   bp-7c60b329-9f17-4ca9-8867-a1e401170730
   bp-a10060bb-9c0a-488d-b739-716e21170730
   bp-73bbed15-141b-467c-b4c1-a02f21170730
   bp-5800-63b6-44cf-a44b-34fa71170730
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

Re: [Desktop-packages] [Bug 1708470] Re: My page jumps up and down for no reason. Tried refresing firefox, password, used Tor and still same thing happens w/anything I do.

[csl]

Thanks for replying.  Didn't know it was a common issue.
Just seemed like someone was making moves; and, might be an attack of some sort.

Thanks again :)


-Original Message-
From: Seth Arnold <1708...@bugs.launchpad.net>
To: luluc210 
Sent: Thu, Aug 3, 2017 7:25 pm
Subject: [Bug 1708470] Re: My page jumps up and down for no reason. Tried 
refresing firefox, password, used Tor and still same thing happens w/anything I 
do.


Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1708470

Title:
My page jumps up and down for no reason. Tried refresing firefox,
password, used Tor and still same thing happens w/anything I do.

Status in firefox package in Ubuntu:
New

Bug description:
I use Firefox browser mainly, and used Tor twice today to check if
same thing happens - and yes it does. Like right now I'm on Firefox,
the page jumps up & down for no reason - it's frustrating to even type
a word - page keeps jumping up or down. Been happening for about
2months.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 54.0+build3-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: lc 1653 F pulseaudio
BuildID: 20170612123102
Channel: Unavailable
CurrentDesktop: LXDE
Date: Thu Aug 3 10:31:26 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-01-09 (205 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720)
IpRoute:
default via 192.168.1.254 dev wlx00e1b0677506 proto static metric 600
192.168.1.0/24 dev wlx00e1b0677506 proto kernel scope link src 192.168.1.67 
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/20170612123102 (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: 01/05/2006
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A03
dmi.board.name: 0CH775
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA03:bd01/05/2006:svnDellComputerCorporation:pnDimension3000:pvr:rvnDellComputerCorp.:rn0CH775:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: Dimension 3000
dmi.sys.vendor: Dell Computer Corporation

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

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

Title:
  My page jumps up and down for no reason. Tried refresing firefox,
  password, used Tor and still same thing happens w/anything I do.

Status in firefox package in Ubuntu:
  New

Bug description:
  I use Firefox browser mainly, and used Tor twice today to check if
  same thing happens - and yes it does.  Like right now I'm on Firefox,
  the page jumps up & down for no reason - it's frustrating to even type
  a word - page keeps jumping up or down. Been happening for about
  2months.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 54.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lc 1653 F pulseaudio
  BuildID: 20170612123102
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Thu Aug  3 10:31:26 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet 

[Desktop-packages] [Bug 1708556] [NEW] Restart from within GUI gets stuck sometimes

[jerriy]

Public bug reported:

And this happens some of the time, not all the time.

It seemingly gets stuck at random points of the process too (sometimes
it gets stuck while shutting down - other times it gets stuck after boot
begins.

This is a new phenomenon that I never experienced before I reinstalled a
fresh one from by live disk yesterday.

Note (a matter may or may not be related): I disabled the graphics
during boot and noticed that that there are "ERROR" lines when it
loading (even when the restart is succesful).

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Aug  4 01:42:12 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6620G] 
[1002:9641] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] BeaverCreek [Radeon HD 6620G] [1025:059b]
 Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] 
[1002:6760] (rev ff) (prog-if ff)
InstallationDate: Installed on 2017-08-03 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Packard Bell EasyNote LS11SB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=526db693-db5f-4daf-b737-feeb9317ed96 ro nopat vesafb.invalid=1 
plymouth:debug drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/02/2011
dmi.bios.vendor: Packard Bell
dmi.bios.version: V2.00
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SJV70-SB
dmi.board.vendor: Packard Bell
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Packard Bell
dmi.chassis.version: V2.00
dmi.modalias: 
dmi:bvnPackardBell:bvrV2.00:bd11/02/2011:svnPackardBell:pnEasyNoteLS11SB:pvrV2.00:rvnPackardBell:rnSJV70-SB:rvrBaseBoardVersion:cvnPackardBell:ct10:cvrV2.00:
dmi.product.name: EasyNote LS11SB
dmi.product.version: V2.00
dmi.sys.vendor: Packard Bell
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Aug  4 03:03:54 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.3
xserver.video_driver: radeon

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


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

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

Title:
  Restart from within GUI gets stuck sometimes

Status in xorg package in Ubuntu:
  New

Bug description:
  And this happens some of the time, not all the time.

  It seemingly gets stuck at random points of the process too (sometimes
  it gets stuck while shutting down - other times it gets stuck after
  boot begins.

  This is a new phenomenon that I never experienced before I reinstalled
  a fresh one from by live disk yesterday.

  Note (a matter may or may not be related): I disabled the graphics
  during boot and noticed that that there are "ERROR" lines when it
  loading (even when the restart is succesful).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug  4 01:42:12 2017
  

[Desktop-packages] [Bug 1708470] Re: My page jumps up and down for no reason. Tried refresing firefox, password, used Tor and still same thing happens w/anything I do.

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

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

Title:
  My page jumps up and down for no reason. Tried refresing firefox,
  password, used Tor and still same thing happens w/anything I do.

Status in firefox package in Ubuntu:
  New

Bug description:
  I use Firefox browser mainly, and used Tor twice today to check if
  same thing happens - and yes it does.  Like right now I'm on Firefox,
  the page jumps up & down for no reason - it's frustrating to even type
  a word - page keeps jumping up or down. Been happening for about
  2months.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 54.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lc 1653 F pulseaudio
  BuildID: 20170612123102
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Thu Aug  3 10:31:26 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-01-09 (205 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160720)
  IpRoute:
   default via 192.168.1.254 dev wlx00e1b0677506  proto static  metric 600 
   192.168.1.0/24 dev wlx00e1b0677506  proto kernel  scope link  src 
192.168.1.67  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/20170612123102 (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: 01/05/2006
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A03
  dmi.board.name: 0CH775
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA03:bd01/05/2006:svnDellComputerCorporation:pnDimension3000:pvr:rvnDellComputerCorp.:rn0CH775:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 3000
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Desktop-packages] [Bug 1683917] Re: General Input/Output error with Google Drive

[Guillermo]

Bug still present in Libreoffice 5.4.0.3

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

Title:
  General Input/Output error with Google Drive

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  This is a problem with Libreoffice Writer, but for some reason it
  didn't allow me to set that as package (libreoffice-writer)

  When adding a Google Drive service, before it can show the remote files it 
fails, I get the message "General Input/Output error with Google Drive". 
  The authentication  trough though, because I get an email from Google letting 
me know there was  sign-in from a new device. 
  Weirdly,the flatpack from Libre Office is being able to connect correctly. 

  Using Ubuntu 17.04, Libreoffice 1:5.3.1

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

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

[Desktop-packages] [Bug 491736] Re: nautilus takes a huge amount of memory when copy-pasting files

[Ads20000]

Does this still apply in a supported release of Ubuntu or can this be
closed?

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

Title:
  nautilus takes a huge amount of memory when copy-pasting files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nautilus


  My system has 2GB of RAM and 4GB of swap. Nautilus is taking almost
  all of them. Top says 1781M virt and 1.2G res. This happens as I´m
  doing a backup of my external USB drive into another USB drive. Around
  1.000.000 files, with music, videos, text, and thousands and thousands
  of pictures. Copying from Ext3 to Ext4 partition, with a simple copy
  and paste.

  Copy speed decreased with time, starting around 16-17MB/sec now around
  11MB/sec.

  Serious bug. Copy & paste shouldn´t destroy a machine no matter how
  big the amount of files/total size. =(

  I posted this originally as a comment, but this is a different
  behaviour to the one described on the bug report that I posted on.

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

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

[Desktop-packages] [Bug 1708539] Re: Files doesn't prompt cryptsetup-bin install when needed

[Ads20000]

For an example of how this could work, see what happens when, on a clean
install, you try to do a backup with the Backups program.

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

Title:
  Files doesn't prompt cryptsetup-bin install when needed

Status in nautilus package in Ubuntu:
  New

Bug description:
  When attempting to unlock an encrypted drive without cryptsetup-bin
  installed, Files errors out. Files should bring up a prompt to install
  cryptsetup-bin in the relevant package manager (in our case, Apt) when
  one attempts to unlock an encrypted drive. I.e., I plug in the
  encrypted drive, Files tells me that cryptsetup-bin needs to be
  installed and prompts the relevant package manager GUI (can't remember
  what this is in Ubuntu when it isn't full-blown Ubuntu Software) to
  give me a dialogue box and a button to press to install it, I enter my
  password, it is installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Aug  3 22:10:02 2017
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1708539] [NEW] Files doesn't prompt cryptsetup-bin install when needed

[Ads20000]

Public bug reported:

When attempting to unlock an encrypted drive without cryptsetup-bin
installed, Files errors out. Files should bring up a prompt to install
cryptsetup-bin in the relevant package manager (in our case, Apt) when
one attempts to unlock an encrypted drive. I.e., I plug in the encrypted
drive, Files tells me that cryptsetup-bin needs to be installed and
prompts the relevant package manager GUI (can't remember what this is in
Ubuntu when it isn't full-blown Ubuntu Software) to give me a dialogue
box and a button to press to install it, I enter my password, it is
installed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: nautilus 1:3.20.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Aug  3 22:10:02 2017
GsettingsChanges:
 
InstallationDate: Installed on 2017-08-03 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu8

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


** Tags: amd64 apport-bug zesty

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

Title:
  Files doesn't prompt cryptsetup-bin install when needed

Status in nautilus package in Ubuntu:
  New

Bug description:
  When attempting to unlock an encrypted drive without cryptsetup-bin
  installed, Files errors out. Files should bring up a prompt to install
  cryptsetup-bin in the relevant package manager (in our case, Apt) when
  one attempts to unlock an encrypted drive. I.e., I plug in the
  encrypted drive, Files tells me that cryptsetup-bin needs to be
  installed and prompts the relevant package manager GUI (can't remember
  what this is in Ubuntu when it isn't full-blown Ubuntu Software) to
  give me a dialogue box and a button to press to install it, I enter my
  password, it is installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Thu Aug  3 22:10:02 2017
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu8

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

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

[Desktop-packages] [Bug 1708497] Re: gpg-agent not started automatically

[Launchpad Bug Tracker]

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

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

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

Title:
  gpg-agent not started automatically

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  My suspicion is that there's an issue with gnome-session, but that's
  somewhat of a guess. systemd isn't starting the graphical-session-
  pre.target, which would start gpg-agent.service. This is on a fresh
  zesty install with minimal packages added.

  What I expect to see:

  pgrep gpg-agent

  This should report a process ID. Instead I see it is not running.
  Configuring gpg to use the agent results in errors because gpg can't
  communicate with an agent that doesn't exist.

  What additional information can I provide that would be of benefit?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-session 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 12:17:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1708526] [NEW] package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package docbook-xsl is not ready for configuration cannot configure (current status 'half-installed'

[Barry Parker]

Public bug reported:

Problem reported so developers can work on this issue to improve these
operating systems for everyone.  Thank you.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: docbook-xsl 1.79.1+dfsg-1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Aug  3 12:59:50 2017
DuplicateSignature:
 package:docbook-xsl:1.79.1+dfsg-1
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package docbook-xsl (--configure):
  package docbook-xsl is not ready for configuration
ErrorMessage: package docbook-xsl is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2017-05-16 (78 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: docbook-xsl
Title: package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package 
docbook-xsl is not ready for configuration  cannot configure (current status 
'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: docbook-xsl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package
  docbook-xsl is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in docbook-xsl package in Ubuntu:
  New

Bug description:
  Problem reported so developers can work on this issue to improve these
  operating systems for everyone.  Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: docbook-xsl 1.79.1+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug  3 12:59:50 2017
  DuplicateSignature:
   package:docbook-xsl:1.79.1+dfsg-1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package docbook-xsl (--configure):
package docbook-xsl is not ready for configuration
  ErrorMessage: package docbook-xsl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-16 (78 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: docbook-xsl
  Title: package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package 
docbook-xsl is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docbook-xsl/+bug/1708526/+subscriptions

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

[Desktop-packages] [Bug 1708526] Re: package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package docbook-xsl is not ready for configuration cannot configure (current status 'half-installed')

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package
  docbook-xsl is not ready for configuration  cannot configure (current
  status 'half-installed')

Status in docbook-xsl package in Ubuntu:
  New

Bug description:
  Problem reported so developers can work on this issue to improve these
  operating systems for everyone.  Thank you.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: docbook-xsl 1.79.1+dfsg-1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug  3 12:59:50 2017
  DuplicateSignature:
   package:docbook-xsl:1.79.1+dfsg-1
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package docbook-xsl (--configure):
package docbook-xsl is not ready for configuration
  ErrorMessage: package docbook-xsl is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2017-05-16 (78 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: docbook-xsl
  Title: package docbook-xsl 1.79.1+dfsg-1 failed to install/upgrade: package 
docbook-xsl is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docbook-xsl/+bug/1708526/+subscriptions

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

[Desktop-packages] [Bug 1708520] [NEW] no hdmi signal

[ryan vaughan]

Public bug reported:

i cant connect my laptop to my tv through an hdmi it says no signal

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Aug  3 15:38:45 2017
DistUpgraded: 2017-07-29 00:23:28,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
InstallationDate: Installed on 2017-07-14 (20 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=5893fc24-8d35-43ea-8baf-d032c38f7919 ro nomodeset quiet splash 
vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2017-07-29 (5 days ago)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 80B0
dmi.board.vendor: HP
dmi.board.version: 81.27
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.10:bd07/14/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.27:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion Notebook
dmi.sys.vendor: HP
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Aug  3 15:34:47 2017
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.3

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


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

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

Title:
  no hdmi signal

Status in xorg package in Ubuntu:
  New

Bug description:
  i cant connect my laptop to my tv through an hdmi it says no signal

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug  3 15:38:45 2017
  DistUpgraded: 2017-07-29 00:23:28,354 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
  InstallationDate: Installed on 2017-07-14 (20 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic 
root=UUID=5893fc24-8d35-43ea-8baf-d032c38f7919 ro nomodeset quiet splash 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-07-29 (5 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: 

[Desktop-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2

[NJ]

I experience the same state of affairs on Linux Mint x64 18.2 Cinnamon.

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

Title:
  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown
  error -2

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Apr  9 11:57:02 2015
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

[Desktop-packages] [Bug 1708513] Re: Missing network connection types in Control Center (bridge, bonde, etc)

[Julian Alarcon]

Screenshot of workarounds windows

** Attachment added: "Workarounds windows"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1708513/+attachment/4926660/+files/Screenshot%20from%202017-08-03%2014-24-05.png

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

Title:
  Missing network connection types in Control Center (bridge, bonde,
  etc)

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

Bug description:
  I don't know if this is related to the GNOME Migration of Ubuntu 17.10
  (maybe it is), but now in the gnome-control-center there are no
  options to setup multiple connection types.

  Bond, Bridge, DSL, all missing (only VPN option)

  This is a related bug, the removed from gnome-control-center .
  https://bugzilla.gnome.org/show_bug.cgi?id=747443

  
  Please enable this options or confirm that you are not going to support this 
in your implementation of gnome-control-center.

  Thanks!

  Workaround 1: You can use "nm-connection-editor" command to display a
  graphical UI of Network Manager with all the available options (I
  think that this was the Ubuntu implementation 17.04 and backward)

  Workaround 2: You can use the CLI of Network Manger using the command
  "nmtui"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.18-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 13:57:07 2017
  InstallationDate: Installed on 2017-07-04 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  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/1708513/+subscriptions

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

[Desktop-packages] [Bug 1708513] [NEW] Missing network connection types in Control Center (bridge, bonde, etc)

[Julian Alarcon]

Public bug reported:

I don't know if this is related to the GNOME Migration of Ubuntu 17.10
(maybe it is), but now in the gnome-control-center there are no options
to setup multiple connection types.

Bond, Bridge, DSL, all missing (only VPN option)

This is a related bug, the removed from gnome-control-center .
https://bugzilla.gnome.org/show_bug.cgi?id=747443


Please enable this options or confirm that you are not going to support this in 
your implementation of gnome-control-center.

Thanks!

Workaround 1: You can use "nm-connection-editor" command to display a
graphical UI of Network Manager with all the available options (I think
that this was the Ubuntu implementation 17.04 and backward)

Workaround 2: You can use the CLI of Network Manger using the command
"nmtui"

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-12.18-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug  3 13:57:07 2017
InstallationDate: Installed on 2017-07-04 (30 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
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 artful gnome-17.10 wayland-session

** Attachment added: "Gnome Control Center without connection types"
   
https://bugs.launchpad.net/bugs/1708513/+attachment/4926653/+files/Screenshot%20from%202017-08-03%2014-19-30.png

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

Title:
  Missing network connection types in Control Center (bridge, bonde,
  etc)

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

Bug description:
  I don't know if this is related to the GNOME Migration of Ubuntu 17.10
  (maybe it is), but now in the gnome-control-center there are no
  options to setup multiple connection types.

  Bond, Bridge, DSL, all missing (only VPN option)

  This is a related bug, the removed from gnome-control-center .
  https://bugzilla.gnome.org/show_bug.cgi?id=747443

  
  Please enable this options or confirm that you are not going to support this 
in your implementation of gnome-control-center.

  Thanks!

  Workaround 1: You can use "nm-connection-editor" command to display a
  graphical UI of Network Manager with all the available options (I
  think that this was the Ubuntu implementation 17.04 and backward)

  Workaround 2: You can use the CLI of Network Manger using the command
  "nmtui"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.18-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 13:57:07 2017
  InstallationDate: Installed on 2017-07-04 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  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/1708513/+subscriptions

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

[Desktop-packages] [Bug 1708503] [NEW] package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal instal

[Thomas Kügler]

Public bug reported:

Defektes Paket verhindert die Aktualisierung des Systems

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libwacom2:amd64 0.22-1~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-27-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 libwacom-common: Install
 libwacom-common: Configure
 libwacom2: Configure
 NULL: ConfigurePending
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
Date: Thu Aug  3 19:50:06 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgHistoryLog:
 Start-Date: 2017-08-03  19:50:03
 Commandline: apt-get install -f
 Requested-By: thomas (1000)
 Upgrade: libwacom-common:amd64 (0.18-1, 0.22-1~ubuntu16.04.1)
ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie die Konfiguration versuchen.
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller 
[10cf:150a]
InstallationDate: Installed on 2017-07-22 (12 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: FUJITSU LIFEBOOK AH530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=27e085d5-ec9d-4e23-81e3-fe76537c7d5c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libwacom
Title: package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to install/upgrade: 
Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es  
nochmal installieren, bevor Sie die Konfiguration versuchen.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.19
dmi.board.name: FJNBB06
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.19:bd08/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK AH530
dmi.sys.vendor: FUJITSU
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Aug  3 18:12:36 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.2
xserver.video_driver: modeset

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


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

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

Title:
  package libwacom2:amd64 0.22-1~ubuntu16.04.1 failed to
  install/upgrade: Paket ist in einem sehr schlechten inkonsistenten
  Zustand - Sie sollten es  nochmal installieren, bevor Sie die
  Konfiguration versuchen.

Status in libwacom package in Ubuntu:
  New

Bug description:
  Defektes Paket verhindert die Aktualisierung des Systems

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libwacom2:amd64 0.22-1~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   libwacom-common: Install
   libwacom-common: Configure
   libwacom2: Configure
   NULL: ConfigurePending
  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
  Date: Thu Aug  3 19:50:06 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-08-03  19:50:03
   Commandline: apt-get install -f
   Requested-By: thomas (1000)
   Upgrade: libwacom-common:amd64 (0.18-1, 0.22-1~ubuntu16.04.1)
  ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie 
sollten es  nochmal installieren, bevor Sie 

[Desktop-packages] [Bug 1665112] Re: [Snap] Open/Save dialogue not easy-to-use

[Rico Tzschichholz]

Make sure *not* to use the internal Libreoffice Open/Save dialogues
boxes.

** Attachment added: "Options - General"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1665112/+attachment/4926612/+files/lo-dialogues.png

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

Title:
  [Snap] Open/Save dialogue not easy-to-use

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  In the Deb package, LibreOffice uses the Nautilus/Nautilus-style
  Open/Save/ dialogue with a clickable directory bar and all your
  bookmarks from Nautilus. In the Snap package, it has a text-based
  directory bar, doesn't use you Nautilus bookmarks and doesn't use the
  native theming.

  Maybe it would be hard to integrate the Snap version of LibreOffice
  properly but this is still a usability bug and needs to be fixed, even
  if this has to be fixed on Snapcraft's end rather than the LibreOffice
  Snap's end.

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

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

[Desktop-packages] [Bug 1708502] Re: package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pidgin package in Ubuntu:
  New

Bug description:
  I was updating a fresh install of ubuntu gnome and got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pidgin-data 1:2.10.12-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug  3 13:32:53 2017
  Dependencies:
   
  DuplicateSignature:
   package:pidgin-data:1:2.10.12-0ubuntu5.2
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package pidgin-data (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: pidgin
  Title: package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1708502] [NEW] package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

[JCD]

Public bug reported:

I was updating a fresh install of ubuntu gnome and got this error.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: pidgin-data 1:2.10.12-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Aug  3 13:32:53 2017
Dependencies:
 
DuplicateSignature:
 package:pidgin-data:1:2.10.12-0ubuntu5.2
 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
 dpkg: error processing package pidgin-data (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-08-03 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: pidgin
Title: package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pidgin package in Ubuntu:
  New

Bug description:
  I was updating a fresh install of ubuntu gnome and got this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: pidgin-data 1:2.10.12-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Aug  3 13:32:53 2017
  Dependencies:
   
  DuplicateSignature:
   package:pidgin-data:1:2.10.12-0ubuntu5.2
   Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ...
   dpkg: error processing package pidgin-data (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: pidgin
  Title: package pidgin-data 1:2.10.12-0ubuntu5.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1708500] [NEW] [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all. Rebooting does not fix & unmuting via alsamixer addresses the issue but audio play

[Miguel Mendoza]

Public bug reported:

Rebooting does not fix & unmuting via alsamixer addresses the issue but
audio plays from internal speakers AND headphones

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
 /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
CurrentDesktop: Unity
Date: Thu Aug  3 10:28:03 2017
InstallationDate: Installed on 2015-09-29 (674 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
 /dev/snd/pcmC1D0p:   mmendoza   2636 F...m pulseaudio
 /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound 
at all
UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago)
dmi.bios.date: 05/13/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 06HN6G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7450
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound
  at all. Rebooting does not fix & unmuting via alsamixer addresses the
  issue but audio plays from internal speakers AND headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Rebooting does not fix & unmuting via alsamixer addresses the issue
  but audio plays from internal speakers AND headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
   /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug  3 10:28:03 2017
  InstallationDate: Installed on 2015-09-29 (674 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
   /dev/snd/pcmC1D0p:   mmendoza   2636 F...m pulseaudio
   /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound 
at all
  UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago)
  dmi.bios.date: 05/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1665112] Re: [Snap] Open/Save dialogue not easy-to-use

[Olivier Tilloy]

Also tested on xenial (in a VM) and same result, I'm getting the
standard open dialog with folder buttons to navigate and links to common
locations.

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

Title:
  [Snap] Open/Save dialogue not easy-to-use

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  In the Deb package, LibreOffice uses the Nautilus/Nautilus-style
  Open/Save/ dialogue with a clickable directory bar and all your
  bookmarks from Nautilus. In the Snap package, it has a text-based
  directory bar, doesn't use you Nautilus bookmarks and doesn't use the
  native theming.

  Maybe it would be hard to integrate the Snap version of LibreOffice
  properly but this is still a usability bug and needs to be fixed, even
  if this has to be fixed on Snapcraft's end rather than the LibreOffice
  Snap's end.

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

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

[Desktop-packages] [Bug 1665112] Re: [Snap] Open/Save dialogue not easy-to-use

[Olivier Tilloy]

@Ads2: I'm not seeing that with the libreoffice snap. Tested on
artful and zesty, attaching a screenshot of the open dialog I'm seeing
in zesty.

** Attachment added: "VirtualBox_zesty amd64_03_08_2017_19_18_40.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1665112/+attachment/4926577/+files/VirtualBox_zesty%20amd64_03_08_2017_19_18_40.png

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

Title:
  [Snap] Open/Save dialogue not easy-to-use

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  In the Deb package, LibreOffice uses the Nautilus/Nautilus-style
  Open/Save/ dialogue with a clickable directory bar and all your
  bookmarks from Nautilus. In the Snap package, it has a text-based
  directory bar, doesn't use you Nautilus bookmarks and doesn't use the
  native theming.

  Maybe it would be hard to integrate the Snap version of LibreOffice
  properly but this is still a usability bug and needs to be fixed, even
  if this has to be fixed on Snapcraft's end rather than the LibreOffice
  Snap's end.

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

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

[Desktop-packages] [Bug 1708497] [NEW] gpg-agent not started automatically

[fidian]

Public bug reported:

My suspicion is that there's an issue with gnome-session, but that's
somewhat of a guess. systemd isn't starting the graphical-session-
pre.target, which would start gpg-agent.service. This is on a fresh
zesty install with minimal packages added.

What I expect to see:

pgrep gpg-agent

This should report a process ID. Instead I see it is not running.
Configuring gpg to use the agent results in errors because gpg can't
communicate with an agent that doesn't exist.

What additional information can I provide that would be of benefit?

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-session 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug  3 12:17:06 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-07-15 (19 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  gpg-agent not started automatically

Status in gnome-session package in Ubuntu:
  New

Bug description:
  My suspicion is that there's an issue with gnome-session, but that's
  somewhat of a guess. systemd isn't starting the graphical-session-
  pre.target, which would start gpg-agent.service. This is on a fresh
  zesty install with minimal packages added.

  What I expect to see:

  pgrep gpg-agent

  This should report a process ID. Instead I see it is not running.
  Configuring gpg to use the agent results in errors because gpg can't
  communicate with an agent that doesn't exist.

  What additional information can I provide that would be of benefit?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-session 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug  3 12:17:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-15 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

[dlotton]

Just did a fresh install of Mint Mate 18.2 onto a new machine. Same
problem exists.  While connected to VPN DNS queries are leaking to non-
VPN interface.

This needs to be fixed!

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

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

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1708224] Re: Firefox is out of date in artful

[cpatrick08]

54.0.1 is out https://download-
origin.cdn.mozilla.net/pub/firefox/releases/54.0.1/

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

Title:
  Firefox is out of date in artful

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In artful is on version 50 and Firefox upstream is at version 54.
  Firefox on every other version of Ubuntu is at version 54.

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

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

[Desktop-packages] [Bug 2332] Re: Should pause music on lock screen

[Mathieu Leplatre]

Just had to be patient ;)

http://www.omgubuntu.co.uk/2017/08/ubuntu-pause-music-screen-lock-kicks-
resume-unlocked

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

Title:
  Should pause music on lock screen

Status in GNOME Screensaver:
  Confirmed
Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  G-s should do some d-bus foo to tell music players to pause when the
  screen gets locked, and then restart it when the screen is unlocked.

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

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

[Desktop-packages] [Bug 1708476] Re: package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-common 2.24.30-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-bin: Configure
   libgtk2.0-common: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Aug  3 20:45:10 2017
  DuplicateSignature:
   package:libgtk2.0-common:2.24.30-1ubuntu1
   Setting up libglib2.0-bin (2.48.2-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-common 2.24.30-1ubuntu1 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/gtk+2.0/+bug/1708476/+subscriptions

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

[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

[Jeremy Bicha]

gnome-software in artful-proposed uses PackageKit instead of aptdaemon
https://launchpad.net/ubuntu/+source/gnome-software/3.25.4-1ubuntu1

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

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Desktop-packages] [Bug 1708224] Re: Firefox is out of date in artful

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox is out of date in artful

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  In artful is on version 50 and Firefox upstream is at version 54.
  Firefox on every other version of Ubuntu is at version 54.

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

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

[Desktop-packages] [Bug 1708476] [NEW] package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

[Zulfikar]

Public bug reported:

update

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk2.0-common 2.24.30-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 libglib2.0-0: Install
 libglib2.0-0: Configure
 libglib2.0-bin: Configure
 libgtk2.0-common: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Thu Aug  3 20:45:10 2017
DuplicateSignature:
 package:libgtk2.0-common:2.24.30-1ubuntu1
 Setting up libglib2.0-bin (2.48.2-0ubuntu1) ...
 dpkg: error processing package libgtk2.0-common (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-08-03 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gtk+2.0
Title: package libgtk2.0-common 2.24.30-1ubuntu1 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)

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


** Tags: apport-package i386 xenial

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

Title:
  package libgtk2.0-common 2.24.30-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-common 2.24.30-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  AptOrdering:
   libglib2.0-0: Install
   libglib2.0-0: Configure
   libglib2.0-bin: Configure
   libgtk2.0-common: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Aug  3 20:45:10 2017
  DuplicateSignature:
   package:libgtk2.0-common:2.24.30-1ubuntu1
   Setting up libglib2.0-bin (2.48.2-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-08-03 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-common 2.24.30-1ubuntu1 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/gtk+2.0/+bug/1708476/+subscriptions

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

[Desktop-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Kevin Ard]

again, confirming: `sudo apt-get remove --purge dbus-user-session` and
reboot resolved it for me on Ubuntu 16.04. No side-effects. On reboot,
the Passwords>Login keyring was available, where before it wasn't.

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

Title:
  gnome-keyring not unlocked on boot

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

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Jamie Strandboge]

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: In Progress => Won't Fix

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Won't Fix
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Currently snaps on Ubuntu Classic may declare in their snap.yaml that they 
want access to pulseaudio. When installed, snapd will auto-connect the 
pulseaudio interface giving the snap access to the pulseaudio server for 
playback and recording. Because recording is allowed, snaps are allowed to 
eavesdrop on users without the user knowing. Phase 1 of the pulseaudio 
interface should block recording for snaps while the details of phase 2 (which 
combines pulseaudio/snappy interfaces and trust-store) are worked out.

  [Test Case]
  First, install pulseaudio then reboot (alternatively can 'killall pulseaudio' 
from within your session or logout then killall pulseaudio from a vt and then 
log back in). pulseaudio needs to be restarted for the changes to be in effect 
and a reboot is the easiest way to achieve that.

  1. unconfined can play audio
  2. unconfined can record audio
  3. non-snap confined can play audio
  4. non-snap confined can record audio
  5. snap confined can play audio
  6. snap confined cannot record audio
  7. snap confined devmode can record audio
  8. indicator-sound and 'Sound Settings... works'
  9. click can record audio if trust-store allows (eg, 'SnapRecorder' from the 
store)
  10. click can play audio (eg, playback of recording from 'SnapRecorder' from 
the store)

  Currently '6' is not implemented and all snaps may record audio. When
  this bug is fixed, no snaps should be able to record audio (until
  phase 2 is implemented which will be in a different bug).

  The attached script tests 1-7. 9 and 10 require testing on a device
  and using

  [Regression Potential]
  The patch is quite small and easy to understand and is implemented to only 
affect processes that want to record and are running with a security label that 
starts with 'snap.' Unconfined processes and process running under other 
security labels should not be affected.

  Original description:
  Until we have a proper trust-store implementation with snappy and on the 
desktop/ubuntu core we want pulseaudio to simply deny any audio recording 
request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Desktop-packages] [Bug 1598531] Re: raid degradation not visible fom gui

[Vlad Orlov]

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

** Project changed: linuxmint => gnome-disk-utility (Ubuntu)

** This bug has been marked a duplicate of bug 1017097
   Ubuntu does not warn of degraded software raid

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

Title:
  raid degradation not visible fom gui

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Mint 18 bug... Menu-Preferences->Disks. The Disks tool no longer
  displays RAID degradation information. If a RAID is broken or is
  resyncing this is no longer visible from the GUI.

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

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

[Desktop-packages] [Bug 1599442] Re: gnome-font-viewer doesn't pop up if started from menu

[Vlad Orlov]

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

** Project changed: linuxmint => gnome-font-viewer (Ubuntu)

** This bug has been marked a duplicate of bug 1607937
   Font Viewer fails to start from dash: Unknown option --gapplication-service

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

Title:
  gnome-font-viewer doesn't pop up if started from menu

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

Bug description:
  Fresh install LinuxMint18 - Cinnamon version (Language = dutch)

  After installation gnome-font-viewer works if selected from the menu.
  After applying all updates, gnome-font-viewer doesn't pop up any
  longer if started from the menu. Starting gnome-font-viewer from the
  terminal is ok.

  
  Effects : Error-message (syslog) :Jul  6 11:27:01 bdc-vb-lm18 
org.gnome.font-viewer[1789]: Onbekende optie --gapplication-service
  Jul  6 11:27:01 bdc-vb-lm18 org.gnome.font-viewer[1789]: Voer 
'/usr/bin/gnome-font-viewer --help' uit om een volledige lijst met mogelijke 
opties voor de opdrachtregel te zien.
  In English :  org.gnome.font-viewer[1789]: Unknown option 
–gapplication-service
  org.gnome.font-viewer[1983]: Run ‘/usr/bin/gnome-font-viewer –help’ to see a 
full list of available command line options.

  
  Secondary effect : Can't install fonts using Nemo. Normally clicking on a 
font-file, starts installing the font

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

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

[Desktop-packages] [Bug 1599442] Re: gnome-font-viewer doesn't pop up if started from menu

[Launchpad Bug Tracker]

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

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

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

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

Title:
  gnome-font-viewer doesn't pop up if started from menu

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

Bug description:
  Fresh install LinuxMint18 - Cinnamon version (Language = dutch)

  After installation gnome-font-viewer works if selected from the menu.
  After applying all updates, gnome-font-viewer doesn't pop up any
  longer if started from the menu. Starting gnome-font-viewer from the
  terminal is ok.

  
  Effects : Error-message (syslog) :Jul  6 11:27:01 bdc-vb-lm18 
org.gnome.font-viewer[1789]: Onbekende optie --gapplication-service
  Jul  6 11:27:01 bdc-vb-lm18 org.gnome.font-viewer[1789]: Voer 
'/usr/bin/gnome-font-viewer --help' uit om een volledige lijst met mogelijke 
opties voor de opdrachtregel te zien.
  In English :  org.gnome.font-viewer[1789]: Unknown option 
–gapplication-service
  org.gnome.font-viewer[1983]: Run ‘/usr/bin/gnome-font-viewer –help’ to see a 
full list of available command line options.

  
  Secondary effect : Can't install fonts using Nemo. Normally clicking on a 
font-file, starts installing the font

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

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

[Desktop-packages] [Bug 1598531] [NEW] raid degradation not visible fom gui

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Mint 18 bug... Menu-Preferences->Disks. The Disks tool no longer
displays RAID degradation information. If a RAID is broken or is
resyncing this is no longer visible from the GUI.

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

-- 
raid degradation not visible fom gui
https://bugs.launchpad.net/bugs/1598531
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-disk-utility in Ubuntu.

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

[Desktop-packages] [Bug 1705574] Re: systray.py crashed with SIGSEGV in QObjectPrivate::connectImpl()

[Launchpad Bug Tracker]

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

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

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

Title:
  systray.py crashed with SIGSEGV in QObjectPrivate::connectImpl()

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  Not sure if it is related but yesterday a partial upgrade un installed
  hplip and gui. Also virtual box. The virtual box has since been
  corrected and I re installed it. Can not install hplip, dependencies
  not meet.Hplip gui  will not install due to broken packages.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: hplip-data 3.17.6+repack0-2
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Wed Jul 19 12:32:48 2017
  Dependencies:
   gcc-7-base 7.1.0-9ubuntu1
   libc6 2.24-12ubuntu1
   libgcc1 1:7.1.0-9ubuntu1
   liblzma5 5.2.2-1.3
   xz-utils 5.2.2-1.3
  ExecutablePath: /usr/share/hplip/systray.py
  ExecutableTimestamp: 1499063093
  InterpreterPath: /usr/bin/python3.5
  Lpstat: device for DeskJet-2130-series: 
hp:/usb/DeskJet_2130_series?serial=CN6744723N068Y
  MachineType: Hewlett-Packard HP 15 Notebook PC
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet-2130-series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet-2130-series.ppd: Permission denied
  ProcCmdline: /usr/bin/python3 /usr/bin/hp-systray -x
  ProcCwd: /home/bigdavesr
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-11-generic 
root=UUID=49ce942d-755a-4ba9-bace-4ee65c70e873 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f16b933abd2 
<_ZN14QObjectPrivate11connectImplEPK7QObjectiS2_PPvPN9QtPrivate15QSlotObjectBaseEN2Qt14ConnectionTypeEPKiPK11QMetaObject+274>:
  mov0x40(%rax),%rbx
   PC (0x7f16b933abd2) ok
   source "0x40(%rax)" (0x650065007200a6) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: hplip
  StacktraceTop:
   QObjectPrivate::connectImpl(QObject const*, int, QObject const*, void**, 
QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject 
const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   QObject::connectImpl(QObject const*, void**, QObject const*, void**, 
QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*, QMetaObject 
const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnection::registerObject(QString const&, QString const&, QObject*, 
QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
   QDBusConnection::registerObject(QString const&, QObject*, 
QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  Title: systray.py crashed with SIGSEGV in QObjectPrivate::connectImpl()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 22CD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 93.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd11/04/2015:svnHewlett-Packard:pnHP15NotebookPC:pvr096C10405F00051660180:rvnHewlett-Packard:rn22CD:rvr93.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 096C10405F00051660180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1599442] [NEW] gnome-font-viewer doesn't pop up if started from menu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Fresh install LinuxMint18 - Cinnamon version (Language = dutch)

After installation gnome-font-viewer works if selected from the menu.
After applying all updates, gnome-font-viewer doesn't pop up any longer
if started from the menu. Starting gnome-font-viewer from the terminal
is ok.


Effects : Error-message (syslog) :Jul  6 11:27:01 bdc-vb-lm18 
org.gnome.font-viewer[1789]: Onbekende optie --gapplication-service
Jul  6 11:27:01 bdc-vb-lm18 org.gnome.font-viewer[1789]: Voer 
'/usr/bin/gnome-font-viewer --help' uit om een volledige lijst met mogelijke 
opties voor de opdrachtregel te zien.
In English :  org.gnome.font-viewer[1789]: Unknown option –gapplication-service
org.gnome.font-viewer[1983]: Run ‘/usr/bin/gnome-font-viewer –help’ to see a 
full list of available command line options.


Secondary effect : Can't install fonts using Nemo. Normally clicking on a 
font-file, starts installing the font

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

-- 
gnome-font-viewer doesn't pop up if started from menu
https://bugs.launchpad.net/bugs/1599442
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-font-viewer in Ubuntu.

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

[Desktop-packages] [Bug 1708446] Re: nautilus crashed with SIGSEGV

[Cristian Aravena Romero]

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I'm working and open apport.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.2.1-0ubuntu1
  Uname: Linux 4.12.4-041204-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug  2 16:50:15 2017
  Disassembly: No hay registros.
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-07-05 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  Registers: El programa no tiene registros ahora.
  SegvAnalysis: Failure: invalid literal for int() with base 16: 'programa'
  Signal: 11
  SourcePackage: nautilus
  Stacktrace: No stack.
  StacktraceTop:
   
  ThreadStacktrace:
   
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-07-05 (28 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)

[Khurshid Alam]

> - I don't understand the line `/usr/lib/purple-2*/`.

You are right. Telegram-purple only creates /usr/lib/purple-2/, so
asterix can be removed. In fact I think we don't need
"/usr/lib/purple-2*/ r",  as "/usr/lib/purple-2/*.so mr", will do the
job.


> telegram-purple is supposed to detect telepathy, and avoid the path 
> `@{HOME}/.purple/telegram-purple/`. Was it really necessary?

It should but it doesn't at the moment.

And yes, it is necessary with 1.3.x. The plugin stores data after
authentication in either @{HOME}/.purple/telegram-purple/ or @{HOME
}/.telegram-purple/ depending on plugin version number. So telepathy-
haze would require read/write access to that folder, otherwise apparmor
give access-denied and users have to re-authenticate each time after
opening the client (empathy).

I will update the patch. Thanks.

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

[Desktop-packages] [Bug 1708430] [NEW] Sync from Debian, drop Ubuntu changes.

[Timo Jyrinki]

Public bug reported:

libvoikko should be directly synced from Debian, dropping Ubuntu
changes, when/if MIR request in bug #1708428 is accepted.

** Affects: libvoikko (Ubuntu)
 Importance: Wishlist
 Status: New

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

Title:
  Sync from Debian, drop Ubuntu changes.

Status in libvoikko package in Ubuntu:
  New

Bug description:
  libvoikko should be directly synced from Debian, dropping Ubuntu
  changes, when/if MIR request in bug #1708428 is accepted.

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

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

[Desktop-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)

[bewied]

I did some work on telegram-purple.

- I don't understand the line `/usr/lib/purple-2*/`.  Is the asterisk 
misplaced, or does telepathy-haze truly create directories with unpredictable 
names in `/usr/lib/`?
- Heads up: `/etc/telegram-purple/server.tglpub` can be removed once we release 
1.4.0.  (But doesn't hurt either.)
- telegram-purple is supposed to detect telepathy, and avoid the path 
`@{HOME}/.purple/telegram-purple/`.  Was it really necessary?  Please open a 
bug report and tell us what's in the directory.  Was it just "to make sure"?  
Oh well, doesn't hurt, but shouldn't be necessary either.

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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

Re: [Desktop-packages] [Bug 1703690] Re: Add support for Budgie Desktop using GNOME Screensaver

[fossfreedom]

Thanks Łukasz

With regards to the gnome-desktop3 patch.  I had a look through the
gsettings API and there didnt seem to be a method to say "is this
gsettings key you are about to use valid" - in fact all the
documentation basically says it is up to the programmer to ensure that
a key being used is actually there ("programmer error").  GSettings
doesnt seem to-do any validation which is a shame.

I would prefer if the whole "draw-background" ubuntu patch  could be
dropped (and hence make this patch unnecessary) but I don't know
really what the current impact that would have on the Unity desktop.

Ack with regards to the static functions in gnome-screensaver.  I
suppose its a coding style to keep code as localised as possible.

I did ping on both #ubuntu-devel and #ubuntu-desktop recently but no
takers.  I don't really know anyone on the GNOME team other than
JBicha.

On 3 August 2017 at 10:15, Łukasz Zemczak <1703...@bugs.launchpad.net> wrote:
> Hello! Thanks for submitting the bug and patches!
>
> I looked briefly at the provided debdiffs and from the packaging POV
> they look good. I'm not sure about the contents though. I am not a GNOME
> developer so I'd like to get some opinion of someone that knows the code
> and would be able to say if it's the right way to go or not. Did you
> discuss these changes with the desktop team or anyone from the GNOME
> uploaders?
>
> Checking the patches I'm a bit worried about a few things. In the 
> gnome-screensaver part, the patch introduces the static function in_desktop() 
> in both gs-lock-plug.c and gs-window-x11.c. I know it's nice to have helper 
> functions like these 'local' but I'm always reluctant whenever I see 
> boilerplate code like this. Maybe it could be made global and somehow shared? 
> I guess it's fine if there's a lot of boilerplate there already, would have 
> to check the codebase.
> The gnome-desktop3 part seems good but a little bit hacky. Wonder if this 
> could be done in a more generic way. Maybe it's not possible though...
>
> Anyway, let's get someone from the GNOME people to take a look before we
> decide about uploading it.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1703690
>
> Title:
>   Add support for Budgie Desktop using GNOME Screensaver
>
> Status in gnome-desktop3 package in Ubuntu:
>   In Progress
> Status in gnome-screensaver package in Ubuntu:
>   In Progress
>
> Bug description:
>   Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
>   screen.
>
>   It also uses gnome-control-center to control both the desktop
>   background and the lock-screen background.
>
>   GNOME Screensaver does not support gnome-control-center lock screen
>   dialog - GNOME has changed to a gsettings path
>   org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the
>   path org.gnome.desktop.background.
>
>   To resolve this requires patches in two packages - gnome-screensaver
>   and gnome-desktop3.
>
>   1. GNOME Screensaver has been patched to support Budgie Desktop and 
> gnome-control-center.
>   Note - I've taken the opportunity to reuse the existing "Unity" patchwork 
> which is now defunct (I believe) since Unity uses an alternative locking 
> mechanism.  The lock-screen is styled as per the old "Unity" implementation 
> before Unity 16.04 moved to the new lock screen.
>
>   2. The consequence of making the requisite changes to GNOME
>   Screensaver has unfortunately impacted gnome-desktop3.  gnome-desktop3
>   has a Ubuntu specific patch to revert a GNOME upstream decision to
>   remove a key called draw-background.  GNOME Screensaver calls a public
>   function in gnome-desktop3 - the gsettings path causes a segmentation
>   fault since draw-background does not exist in
>   org.gnome.desktop.screensaver.  I have worked around this to check the
>   path being called before pulling the draw-background key.
>
>   All of this is explained in the dep3 headers of the two debdiff
>   patches attached
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1703690/+subscriptions

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

Title:
  Add support for Budgie Desktop using GNOME Screensaver

Status in gnome-desktop3 package in Ubuntu:
  In Progress
Status in gnome-screensaver package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  It also uses gnome-control-center to control both the desktop
  background and the lock-screen background.

  GNOME Screensaver does not support gnome-control-center lock screen
  dialog - GNOME has changed to a gsettings path
  org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the
  path org.gnome.desktop.background.

  To resolve this 

[Desktop-packages] [Bug 1708306] Re: Middle click paste not working in terminal launched from context menu

[Alan Pope  濾]

Nothing happens when I double click text then use Shift+Insert.

Also, using Shift+Ctrl+C and Shift+Ctrl+V don't work in a terminal
opened this way either.

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

Title:
  Middle click paste not working in terminal launched from context menu

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On a clean up to date Artful system I noticed some odd behavior in the
  terminal.

  Steps to reproduce:-

  1. Open a terminal by right clicking the desktop and Open Terminal.
  2. Double click the command prompt
  3. Middle click to paste

  Expected behavior

  Contents of terminal appears pasted

  Actual behavior

  Nothing

  Oddly, terminals launched from the activities menu or by pressing
  CTRL+ALT+T don't exhibit this behavior. In addition, sometimes it
  works if you copy from a terminal launched in the two mentioned ways,
  and try to paste into the one launched from the desktop.

  https://youtu.be/aKfb9DCfPUI

  Video showing me launching a terminal from the activities menu where
  middle click paste works. Launching a terminal from the desktop
  context menu and middle click paste not working. Then launching gedit
  where also I can't paste what I have highlighted in the terminal, but
  can copy from gedit to terminal via middle click paste.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  2 23:08:44 2017
  InstallationDate: Installed on 2017-08-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1703690] Re: Add support for Budgie Desktop using GNOME Screensaver

[Łukasz Zemczak]

Hello! Thanks for submitting the bug and patches!

I looked briefly at the provided debdiffs and from the packaging POV
they look good. I'm not sure about the contents though. I am not a GNOME
developer so I'd like to get some opinion of someone that knows the code
and would be able to say if it's the right way to go or not. Did you
discuss these changes with the desktop team or anyone from the GNOME
uploaders?

Checking the patches I'm a bit worried about a few things. In the 
gnome-screensaver part, the patch introduces the static function in_desktop() 
in both gs-lock-plug.c and gs-window-x11.c. I know it's nice to have helper 
functions like these 'local' but I'm always reluctant whenever I see 
boilerplate code like this. Maybe it could be made global and somehow shared? I 
guess it's fine if there's a lot of boilerplate there already, would have to 
check the codebase.
The gnome-desktop3 part seems good but a little bit hacky. Wonder if this could 
be done in a more generic way. Maybe it's not possible though...

Anyway, let's get someone from the GNOME people to take a look before we
decide about uploading it.

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

Title:
  Add support for Budgie Desktop using GNOME Screensaver

Status in gnome-desktop3 package in Ubuntu:
  In Progress
Status in gnome-screensaver package in Ubuntu:
  In Progress

Bug description:
  Ubuntu Budgie and Budgie Desktop uses GNOME Screensaver for its lock-
  screen.

  It also uses gnome-control-center to control both the desktop
  background and the lock-screen background.

  GNOME Screensaver does not support gnome-control-center lock screen
  dialog - GNOME has changed to a gsettings path
  org.gnome.desktop.screensaver.  GNOME Screensaver is expecting the
  path org.gnome.desktop.background.

  To resolve this requires patches in two packages - gnome-screensaver
  and gnome-desktop3.

  1. GNOME Screensaver has been patched to support Budgie Desktop and 
gnome-control-center.
  Note - I've taken the opportunity to reuse the existing "Unity" patchwork 
which is now defunct (I believe) since Unity uses an alternative locking 
mechanism.  The lock-screen is styled as per the old "Unity" implementation 
before Unity 16.04 moved to the new lock screen.

  2. The consequence of making the requisite changes to GNOME
  Screensaver has unfortunately impacted gnome-desktop3.  gnome-desktop3
  has a Ubuntu specific patch to revert a GNOME upstream decision to
  remove a key called draw-background.  GNOME Screensaver calls a public
  function in gnome-desktop3 - the gsettings path causes a segmentation
  fault since draw-background does not exist in
  org.gnome.desktop.screensaver.  I have worked around this to check the
  path being called before pulling the draw-background key.

  All of this is explained in the dep3 headers of the two debdiff
  patches attached

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

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

[Desktop-packages] [Bug 1587154] Re: --working-directory does not work anymore

[Thierry Bothorel]

Sorry but for me :


Passing the **full** path to --working-directory DOES NOT works as expected.

Ubuntu: 17.04
Desktop Environment : Gnome Shell 3.24.2
GNOME Terminal: 3.20.2

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

Title:
  --working-directory does not work anymore

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  
  After upgrading from ubuntu 14.04 to 16.04 one of my script the uses 
--working-directory option stopped working.

  Simply running:

  gnome-terminal --working-directory=/tmp

  Starts the terminal in my home directory. Changing the command to
  gnome-terminal.real does not solve my problem either.

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

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

[Desktop-packages] [Bug 1708306] Re: Middle click paste not working in terminal launched from context menu

[Egmont Koblinger]

Out of curiosity: What happens if you try to paste with Shift+Insert
rather than middle click?

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

Title:
  Middle click paste not working in terminal launched from context menu

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On a clean up to date Artful system I noticed some odd behavior in the
  terminal.

  Steps to reproduce:-

  1. Open a terminal by right clicking the desktop and Open Terminal.
  2. Double click the command prompt
  3. Middle click to paste

  Expected behavior

  Contents of terminal appears pasted

  Actual behavior

  Nothing

  Oddly, terminals launched from the activities menu or by pressing
  CTRL+ALT+T don't exhibit this behavior. In addition, sometimes it
  works if you copy from a terminal launched in the two mentioned ways,
  and try to paste into the one launched from the desktop.

  https://youtu.be/aKfb9DCfPUI

  Video showing me launching a terminal from the activities menu where
  middle click paste works. Launching a terminal from the desktop
  context menu and middle click paste not working. Then launching gedit
  where also I can't paste what I have highlighted in the terminal, but
  can copy from gedit to terminal via middle click paste.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  2 23:08:44 2017
  InstallationDate: Installed on 2017-08-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 335510] Re: colour printing highlighted code with oblivion scheme makes text disappear

[Bug Watch Updater]

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

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

Title:
  colour printing highlighted code with oblivion scheme makes text
  disappear

Status in gedit:
  Incomplete
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  hardy x86_64

  Open some C code with syntax highlighting in gedit and choose the
  "oblivion" colour scheme. Keywords like "if" are bold white on the
  grey background. When printing, the background becomes white, but the
  text is also white so it disappears in print preview and when actually
  printed.

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

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

[Desktop-packages] [Bug 1708375] [NEW] Add support for purple-telegram (telepathy-haze)

[Khurshid Alam]

Public bug reported:

When using purple telegram through telepathy-haze, it requires following
permissions:

# for purple telegram
/etc/telegram-purple/server.tglpub r,
/usr/lib/purple-2*/ r,
/usr/lib/purple-2/*.so  mr,
/usr/share/locale/*/LC_MESSAGES/*.mo r,
/usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
@{HOME}/.purple/telegram-purple/** rw,
@{HOME}/.telegram-purple/** rw,

under /usr/lib/telepathy/telepathy-* section. See issue
https://github.com/majn/telegram-purple/issues/346 for more details.

I have attached the necessary patch

** Affects: telepathy-mission-control-5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful patch

** Attachment added: "telepathy-purple.patch"
   
https://bugs.launchpad.net/bugs/1708375/+attachment/4926407/+files/telepathy-purple.patch

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

Title:
  Add support for purple-telegram (telepathy-haze)

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  When using purple telegram through telepathy-haze, it requires
  following permissions:

  # for purple telegram
  /etc/telegram-purple/server.tglpub r,
  /usr/lib/purple-2*/   r,
  /usr/lib/purple-2/*.somr,
  /usr/share/locale/*/LC_MESSAGES/*.mo r,
  /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r,
  @{HOME}/.purple/telegram-purple/** rw,
  @{HOME}/.telegram-purple/**   rw,

  under /usr/lib/telepathy/telepathy-* section. See issue
  https://github.com/majn/telegram-purple/issues/346 for more details.

  I have attached the necessary patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions

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