[Desktop-packages] [Bug 1712005] [NEW] External displays blank, kernel errors from i915/drm driver

2017-08-21 Thread Maketsi
Public bug reported:

My two external displayport connected displays worked fine until last thursday. 
After bringing my laptop to the same HP dock station three days later, they 
stayed blank no matter what.
Displays are seen by X (other of them was powered off during the bug report) 
and detected correctly, but there is no picture.
Displays worked with the current kernel 4.4.0-92-generic on thursday.
Dmesg log is full of kernel errors from i915 driver, multiplied by me switching 
the monitors on and off while troubleshooting the issue.

$ dmesg | fgrep WARNING
[2.860874] WARNING: CPU: 0 PID: 1 at 
/build/linux-hVVhWi/linux-4.4.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2c5/0x380()
[  109.067969] WARNING: CPU: 2 PID: 78 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_dp_mst.c:493 
intel_dp_destroy_mst_connector+0xe7/0xf0 [i915]()
[  109.384569] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  110.235437] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  142.534674] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  196.127732] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  211.875798] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  273.426829] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  273.728180] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  274.583122] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  290.154952] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  301.498593] WARNING: CPU: 0 PID: 172 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  326.124417] WARNING: CPU: 1 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  355.932899] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  356.032234] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  384.356500] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  384.458966] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  448.277935] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[  448.370419] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()


When enabling OR disabling the external display via Displays applet, the 
following error happens:

[ 1782.969654] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
[ 1782.969657] encoder's enabled state mismatch (expected 1, found 0)
[ 1782.969658] Modules linked in: vmnet(OE) vmw_vsock_vmci_transport vsock 
vmw_vmci vmmon(OE) rfcomm bnep binfmt_misc arc4 hp_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm 
snd_hda_codec_hdmi mac80211 irqbypass snd_hda_codec_idt snd_hda_codec_generic 
joydev snd_hda_intel serio_raw snd_hda_codec snd_usb_audio snd_hda_core iwlwifi 
snd_usbmidi_lib snd_hwdep lpc_ich btusb btrtl input_leds snd_pcm btbcm 
rtsx_pci_ms snd_seq_midi btintel cfg80211 snd_seq_midi_event memstick bluetooth 
snd_rawmidi snd_seq snd_seq_device snd_timer snd mei_me soundcore mei shpchp 
hp_accel 8250_fintek lis3lv02d input_polldev mac_hid tpm_infineon hp_wireless 
ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 
nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4
[ 1782.969708]  nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack i

[Desktop-packages] [Bug 1712005] Re: External displays blank, kernel errors from i915/drm driver

2017-08-21 Thread Maketsi
Continued the battle for additional 1.5 hours.
I verified that both displays work fine when connected directly to the laptop 
(1 DP) without the HP ultraslim docking station (2 DPs) between. 

After powering off the docking station and rebooting the system for Nth
time, I finally got the pictures back. It's worth noting that the
password prompt for disk decryption was not shown on external displays,
nor the booting sequence. X11 login prompt was the first image.

It seems this was somehow affected by the docking station. Resolved for
now, but the ultimate cause stays unknown.

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

Title:
  External displays blank, kernel errors from i915/drm driver

Status in xorg package in Ubuntu:
  New

Bug description:
  My two external displayport connected displays worked fine until last 
thursday. After bringing my laptop to the same HP dock station three days 
later, they stayed blank no matter what.
  Displays are seen by X (other of them was powered off during the bug report) 
and detected correctly, but there is no picture.
  Displays worked with the current kernel 4.4.0-92-generic on thursday.
  Dmesg log is full of kernel errors from i915 driver, multiplied by me 
switching the monitors on and off while troubleshooting the issue.

  $ dmesg | fgrep WARNING
  [2.860874] WARNING: CPU: 0 PID: 1 at 
/build/linux-hVVhWi/linux-4.4.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2c5/0x380()
  [  109.067969] WARNING: CPU: 2 PID: 78 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_dp_mst.c:493 
intel_dp_destroy_mst_connector+0xe7/0xf0 [i915]()
  [  109.384569] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  110.235437] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  142.534674] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  196.127732] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  211.875798] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  273.426829] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  273.728180] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  274.583122] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  290.154952] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  301.498593] WARNING: CPU: 0 PID: 172 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  326.124417] WARNING: CPU: 1 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  355.932899] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  356.032234] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  384.356500] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  384.458966] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  448.277935] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  448.370419] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()

  
  When enabling OR disabling the external display via Displays applet, the 
following error happens:

  [ 1782.969654] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [ 1782.969657] encoder's enabled state mismatch (expected 1, found 0)
  [ 1782.969658] Modules l

[Desktop-packages] [Bug 1712006] Re: Unable to pick birthday in Amazon in order to watch mature videogame video trailer

2017-08-21 Thread SivArt
Please see the screencast of the issue that I have uploaded,

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

Title:
  Unable to pick birthday in Amazon in order to watch mature videogame
  video trailer

Status in firefox package in Ubuntu:
  New

Bug description:
  I am trying to watch the video on this site on FF52
  https://www.amazon.com/Uncharted-Lost-Legacy-
  
PlayStation-4/dp/B06ZYW7ZHB/ref=sr_1_1?ie=UTF8&qid=1503300112&sr=8-1&keywords=uncharted&th=1
  but the date picker closes as soon as I click on it, it is totally
  unresponsive. I even recreated my FF profile from scratch and had the
  same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.2+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epereira   2721 F pulseaudio
   /dev/snd/controlC1:  epereira   2721 F pulseaudio
  BuildID: 20170816204344
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Aug 21 01:23:30 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)
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816204344 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET82WW (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ006HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET82WW(2.32):bd01/09/2015:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQ006HUS
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

2017-08-21 Thread Daniel van Vugt
** Also affects: totem (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: totem (Ubuntu)
   Status: New => Triaged

** Changed in: totem (Ubuntu)
   Importance: Undecided => High

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

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

** Also affects: clutter-1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Status in Totem:
  Expired
Status in clutter-1.0 package in Ubuntu:
  New
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  In Progress

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

  Example 1: software playback under Gnome Shell Wayland:

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1712006] [NEW] Unable to pick birthday in Amazon in order to watch mature videogame video trailer

2017-08-21 Thread SivArt
Public bug reported:

I am trying to watch the video on this site on FF52
https://www.amazon.com/Uncharted-Lost-Legacy-
PlayStation-4/dp/B06ZYW7ZHB/ref=sr_1_1?ie=UTF8&qid=1503300112&sr=8-1&keywords=uncharted&th=1
but the date picker closes as soon as I click on it, it is totally
unresponsive. I even recreated my FF profile from scratch and had the
same issue.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: firefox 55.0.2+build1-0ubuntu0.17.04.1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  epereira   2721 F pulseaudio
 /dev/snd/controlC1:  epereira   2721 F pulseaudio
BuildID: 20170816204344
Channel: Unavailable
CurrentDesktop: GNOME
Date: Mon Aug 21 01:23:30 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)
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources:
 /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
 prefs.js
Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816204344 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET82WW (2.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQ006HUS
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET82WW(2.32):bd01/09/2015:svnLENOVO:pn20AQ006HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ006HUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQ006HUS
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug third-party-packages zesty

** Attachment added: "Screencast of the issue"
   
https://bugs.launchpad.net/bugs/1712006/+attachment/4936138/+files/Screencast%20from%2008-21-2017%2001%3A28%3A36%20AM.webm

** Summary changed:

- Unable to pick birthadate in Amazon in order to watch mature videogame video
+ Unable to pick birthday in Amazon in order to watch mature videogame video 
trailer

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

Title:
  Unable to pick birthday in Amazon in order to watch mature videogame
  video trailer

Status in firefox package in Ubuntu:
  New

Bug description:
  I am trying to watch the video on this site on FF52
  https://www.amazon.com/Uncharted-Lost-Legacy-
  
PlayStation-4/dp/B06ZYW7ZHB/ref=sr_1_1?ie=UTF8&qid=1503300112&sr=8-1&keywords=uncharted&th=1
  but the date picker closes as soon as I click on it, it is totally
  unresponsive. I even recreated my FF profile from scratch and had the
  same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.2+build1-0ubuntu0.17.04.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  epereira   2721 F pulseaudio
   /dev/snd/controlC1:  epereira   2721 F pulseaudio
  BuildID: 20170816204344
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Aug 21 01:23:30 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)
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources:
   /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
   prefs.js
  Profiles: Profile0 (Default) - LastVersion=55.0.2/20170816204344 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET82WW (2.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQ006HUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dm

[Desktop-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2017-08-21 Thread Daniel van Vugt
** Also affects: clutter-1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1712010] [NEW] totem uses about a quarter more CPU than "gst-play-1.0 --videosink=clutterautovideosink"

2017-08-21 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1698282 ***
https://bugs.launchpad.net/bugs/1698282

Public bug reported:

totem uses about a quarter more CPU than "gst-play-1.0
--videosink=clutterautovideosink"

** Affects: totem
 Importance: Unknown
 Status: Unknown

** Affects: totem (Ubuntu)
 Importance: High
 Assignee: Daniel van Vugt (vanvugt)
 Status: In Progress


** Tags: performance

** Package changed: clutter-1.0 (Ubuntu) => totem (Ubuntu)

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

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

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

Title:
  totem uses about a quarter more CPU than "gst-play-1.0
  --videosink=clutterautovideosink"

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  In Progress

Bug description:
  totem uses about a quarter more CPU than "gst-play-1.0
  --videosink=clutterautovideosink"

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

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


[Desktop-packages] [Bug 1712011] [NEW] Unable to close Printer properties

2017-08-21 Thread Charlie
Public bug reported:

>From settings I open Printers and click on settings (gear icon) for my
printer which bring up a pop-up with printer details (name , location,
address, etc). There is no way to close this pop-up. Instead of a top
toolbar there is thin dark line. The pop-up cannot be moved.

Occurs using 17.10 default and Wayland.

Screenshot added

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic i686
ApportVersion: 2.20.6-0ubuntu6
Architecture: i386
BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 21 08:55:08 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: Dell Radeon HD 6670 [1028:0b0e]
InstallationDate: Installed on 2017-07-14 (37 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
MachineType: Dell Inc. OptiPlex 9010
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0M9KCM
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 9010
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 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 N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Aug 21 08:45:01 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
 inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
 inputUSB OPTICAL MOUSEMOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu3
xserver.video_driver: radeon

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


** Tags: apport-bug artful i386 reproducible single-occurrence ubuntu 
wayland-session

** Attachment added: "Screenshot from 2017-08-20 20-22-10.png"
   
https://bugs.launchpad.net/bugs/1712011/+attachment/4936158/+files/Screenshot%20from%202017-08-20%2020-22-10.png

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

Title:
  Unable to close Printer properties

Status in xorg package in Ubuntu:
  New

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin

[Desktop-packages] [Bug 1712010] Re: totem uses about a quarter more CPU than "gst-play-1.0 --videosink=clutterautovideosink"

2017-08-21 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1698282 ***
https://bugs.launchpad.net/bugs/1698282

** This bug has been marked a duplicate of bug 1698282
   Totem uses dramatically higher CPU than any other video player

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

Title:
  totem uses about a quarter more CPU than "gst-play-1.0
  --videosink=clutterautovideosink"

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  In Progress

Bug description:
  totem uses about a quarter more CPU than "gst-play-1.0
  --videosink=clutterautovideosink"

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

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


[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

2017-08-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: clutter-1.0 (Ubuntu)
   Status: New => Confirmed

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

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

Status in Totem:
  Unknown
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  In Progress

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

  Example 1: software playback under Gnome Shell Wayland:

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

2017-08-21 Thread Daniel van Vugt
** Bug watch added: GNOME Bug Tracker #786561
   https://bugzilla.gnome.org/show_bug.cgi?id=786561

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

** Changed in: totem
   Status: Expired => Unknown

** Changed in: totem
 Remote watch: GNOME Bug Tracker #783850 => GNOME Bug Tracker #786561

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

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

Status in Totem:
  Unknown
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  In Progress

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

  Example 1: software playback under Gnome Shell Wayland:

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1393476] Re: xterm freezes

2017-08-21 Thread Johan Blomqvist
It seems that xterm freezes more frequently when scrolling in larger
files in vim using vertical splits. The effect seems to be present
regardless of using tmux splits or vim splits. The effect is worse for
me when using vim-splits (which always results in laggy scrolling in all
terminals I've tried).

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

Title:
  xterm freezes

Status in xterm package in Ubuntu:
  Confirmed

Bug description:
  i use xterm daily, it freezes maybe a couple times per week.  i
  typically run tmux, so i can just open another xterm, reattach my tmux
  session, and discard the frozen xterm.  wasn't happening in releases
  prior to trusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xterm 297-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  Date: Mon Nov 17 10:15:14 2014
  InstallationDate: Installed on 2014-01-30 (290 days ago)
  InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20140129)
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1702805] Re: package mesa-vulkan-drivers (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is also in package

2017-08-21 Thread Timo Aaltonen
that's a bug in the padoka packaging..

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

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

Title:
  package mesa-vulkan-drivers (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libvulkan_intel.so',
  which is also in package libgl1-mesa-glx:amd64
  1:17.2~git170629170600.277621b~z~padoka0

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  1 pip failed need a fix for in

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: mesa-vulkan-drivers (not installed)
  Uname: Linux 4.12.0-999-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.5-0ubuntu5
  AptOrdering:
   libllvm4.0:amd64: Install
   mesa-vulkan-drivers:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jul  6 20:14:40 2017
  DistUpgraded: 2017-07-06 15:43:27,848 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is also in package 
libgl1-mesa-glx:amd64 1:17.2~git170629170600.277621b~z~padoka0
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 520 [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] 
[1028:06b2]
  InstallationDate: Installed on 2017-06-26 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-999-generic 
root=UUID=7eb94c89-5679-4fb1-8a24-1cff4a7ae732 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~beta1
  SourcePackage: mesa
  Title: package mesa-vulkan-drivers (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is 
also in package libgl1-mesa-glx:amd64 1:17.2~git170629170600.277621b~z~padoka0
  UpgradeStatus: Upgraded to artful on 2017-07-06 (0 days ago)
  dmi.bios.date: 02/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.8
  dmi.board.name: 052K07
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn052K07:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.81+git1706291650.4c98652~z~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
1:17.2~git170629170600.277621b~z~padoka0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
1:17.2~git170629170600.277621b~z~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.9.99+git1706291702.c9dd28c~z~padoka0
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1706102152.6babcf1~z~padoka0
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1704222053.a7c190e~z~padoka0

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

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


[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

2017-08-21 Thread Bug Watch Updater
** Changed in: totem
   Status: Unknown => Confirmed

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

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

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

Status in Totem:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  In Progress

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

  Example 1: software playback under Gnome Shell Wayland:

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1698282] Re: Totem uses dramatically higher CPU than any other video player

2017-08-21 Thread Daniel van Vugt
** Branch linked: lp:~vanvugt/totem/fix-1698282

** Changed in: clutter-1.0 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: clutter-gst-3.0 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

Status in Totem:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in clutter-gst-3.0 package in Ubuntu:
  Confirmed
Status in totem package in Ubuntu:
  In Progress

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

  Example 1: software playback under Gnome Shell Wayland:

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libgstreamer1.0-0 1.12.0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:57:11 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-08-21 Thread Roderic Jones
Public bug reported:

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

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

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  New

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

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

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


[Desktop-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

2017-08-21 Thread Daniel van Vugt
** Changed in: totem (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: totem (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: clutter-1.0 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: totem (Ubuntu)
   Importance: Undecided => High

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in Totem:
  Incomplete
Status in clutter-1.0 package in Ubuntu:
  New
Status in totem package in Ubuntu:
  In Progress

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711605] Re: a2dp profile still alive even though disconnected

2017-08-21 Thread Chanho Park
Hi,

The "0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch" which
you picked from the upstream has a bug and it has been already fixed at
mainline by the same author.

Please pick below patch to address this problem.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=cb78d6f57c00f3694dae9110f7a7d6f80e3344ac

https://bugs.freedesktop.org/show_bug.cgi?id=100237

** Bug watch added: freedesktop.org Bugzilla #100237
   https://bugs.freedesktop.org/show_bug.cgi?id=100237

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

Title:
  a2dp profile still alive even though disconnected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  During connect/disconnect with BT headset repeatedly, the bluetooth
  connection(check using hcitool) is still alive even thoush the
  connection has been disconnected by bluetoothctl. The hsp profile is
  still connected on pulseaudio.

  ---

  Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 
8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just 
repeating connect/disconnect with BT headset through bluetoothctl.
  The change[1] can be retrieved from Xenial's pulseaudio source but I can't 
ensure which patch causes the problem.
  You can see the error log[2] when the error has been occurred.

  [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

    [Luke Yelavich, Konrad Zapałowicz]
    * Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
  where users would experience some combination of:
  - Bluetooth headset/speakers listed but not selectable in Sound settings
    (LP: #1283003)
  - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
    mode) (LP: #1438510)
  - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
    to HSP/HFP first (LP: #1582213)
    * Specific patches from upstream used to address the above problems:
  - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
  - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
  - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
    . Backport from upstream to fix a bug in Xenial where an incorrect
  audio profile is applied for a headset connected over Bluetooth
  making using it impossible.
  - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
    . Fix a crash that happens if the BT headset is the only non-monitor
  source in the system and the last "phone" stream dies.
  - 0700-pulsecore-add-new-card-profile-hook.patch
    . Backport from upstream (commit 7b6260140149) to allow for correct
  profile selection.
  - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
    . Backport from upstream waiting for all profiles to connect before
  creating a card.

   -- Daniel van Vugt   Tue, 23 May 2017
  16:24:14 +0800

  [2] Error log
  D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, 
interface=org.bluez.Profile1, member=NewConnection
  D: [pulseaudio] backend-native.c: dbus: NewConnection 
path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18
  D: [pulseaudio] bluez5-util.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to 
idle
  D: [pulseaudio] backend-native.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile 
headset_head_unit
  D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07
  D: [pulseaudio] backend-native.c: RFCOMM >> OK
  D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, 
interface=org.bluez.MediaEndpoint1, member=SelectConfiguration
  D: [pulseaudio] bluez5-util.c: Unknown interface 
org.freedesktop.DBus.Introspectable found, skipping
  D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 
found, skipping
  D: [pulseaudio] bluez5-util.c: Unknown interface 
org.freedesktop.DBus.Properties found, skipping
  D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, 
interface=org.bluez.MediaEndpoint1, member=SetConfiguration
  D: [pulseaudio] bluez5-util.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to 
idle
  D: [pulseaudio] bluez5-util.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 available for profile a2dp_sink
  D: [pulseaudio] bluez5-util.c: Properties changed in device 
/org/bluez/hci0/dev_00_18_09_2C_1F_41
  D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, 
interface=org.bluez.Profile1, member=RequestDisconnection
  D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, 
interface=org.bluez.MediaEndpoint1, member=ClearConfiguration
  D: [pulseaudio] bluez5-util.c: Clearing transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 profile a2dp_sink
  D: [pulseaudio] bluez5-u

[Desktop-packages] [Bug 1712021] [NEW] totem randomly fails to build [error: Package `Totem-1.0' not found in specified Vala API directories or GObject-Introspection]

2017-08-21 Thread Daniel van Vugt
Public bug reported:

totem randomly fails to build:

FAILED: 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin@sha/totem-zeitgeist-dp-plugin.c
 src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.h 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.vapi 
valac -C --debug --pkg zeitgeist-2.0 --pkg libpeas-1.0 --pkg gtk+-3.0 --pkg 
clutter-gtk-1.0 -d src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin@sha 
--library=totem-zeitgeist-dp-plugin -H 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.h --vapi 
../totem-zeitgeist-dp-plugin.vapi --girdir=/home/dan/git/totem/build/src 
--pkg=Totem-1.0 ../src/plugins/zeitgeist-dp/bacon-video.vapi 
../src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.vala
error: Package `Totem-1.0' not found in specified Vala API directories or 
GObject-Introspection GIR directories
Compilation failed: 1 error(s), 0 warning(s)

WORKAROUNDS:
Avoid parallel builds:  ninja -j1
or just keep retrying:
  ninja
  ninja
  ninja
and it will succeed after a few.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: totem 3.25.90.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
Date: Mon Aug 21 16:38:16 2017
InstallationDate: Installed on 2017-05-03 (110 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: totem
 Importance: Unknown
 Status: Unknown

** Affects: totem (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug artful

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

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

** Changed in: totem (Ubuntu)
   Importance: Undecided => High

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

Title:
  totem randomly fails to build [error: Package `Totem-1.0' not found in
  specified Vala API directories or GObject-Introspection]

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  New

Bug description:
  totem randomly fails to build:

  FAILED: 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin@sha/totem-zeitgeist-dp-plugin.c
 src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.h 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.vapi 
  valac -C --debug --pkg zeitgeist-2.0 --pkg libpeas-1.0 --pkg gtk+-3.0 --pkg 
clutter-gtk-1.0 -d src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin@sha 
--library=totem-zeitgeist-dp-plugin -H 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.h --vapi 
../totem-zeitgeist-dp-plugin.vapi --girdir=/home/dan/git/totem/build/src 
--pkg=Totem-1.0 ../src/plugins/zeitgeist-dp/bacon-video.vapi 
../src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.vala
  error: Package `Totem-1.0' not found in specified Vala API directories or 
GObject-Introspection GIR directories
  Compilation failed: 1 error(s), 0 warning(s)

  WORKAROUNDS:
  Avoid parallel builds:  ninja -j1
  or just keep retrying:
ninja
ninja
ninja
  and it will succeed after a few.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 16:38:16 2017
  InstallationDate: Installed on 2017-05-03 (110 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed

2017-08-21 Thread Raphaël HALIMI
Hi,

Debian TLP package maintainer here. Two questions :

- What version of tlp was installed ?
- Did you make changes to its default configuration ?

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

Title:
  Slow Firefox performance and high CPU load when tlp is installed

Status in firefox package in Ubuntu:
  New
Status in tlp package in Ubuntu:
  New

Bug description:
  After installing Firefox 55 the browser generates huge cpu load,
  startup is extremely slow (it takes > 10s for the taskbar to accept
  entries after launch (this is new to 55)

  Due to high cpu load the computer tends to overheat, ventilation jumps
  in making the machine extremely loud.

  Using Chromium does not show these symptoms (on the same page).

  
  ---
  LSB Ubuntu 17.04 (budgie desktop)
  firefox:
Installed: 55.0.1+build2-0ubuntu0.17.04.2
Candidate: 55.0.1+build2-0ubuntu0.17.04.2
Version table:
   *** 55.0.1+build2-0ubuntu0.17.04.2 500
  500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   50.1.0+build2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.1+build2-0ubuntu0.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BuildID: 20170814193419
  CurrentDesktop: Budgie:GNOME
  Date: Thu Aug 17 16:30:30 2017
  InstallationDate: Installed on 2017-05-25 (83 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar after logging in

2017-08-21 Thread Daniel van Vugt
I think the correct fix is for all docks and shells to implement _NET_WORKAREA:
https://specifications.freedesktop.org/wm-spec/wm-spec-1.3.html#idm140130317674416

Unfortunately that's an X11-only thing. nautilus-desktop certainly
relies on it being an X11 app, but if your dock is native Wayland then
we might have trouble fixing this because a native Wayland app would
have to make X11 calls to tell nautilus-desktop about the _NET_WORKAREA.

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

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

** Summary changed:

- Desktop icons slip under the top bar after logging in
+ Desktop icons slip under the top bar and dock after logging in

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

Title:
  Desktop icons slip under the top bar and dock after logging in

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Desktop icons slip under the top bar after logging in again.

  If I place icons on the desktop in Gnome Shell they look fine, until I
  log out and log in again. On the second login they have moved half
  under the top bar.

  The same problem is visible in the Ubuntu live session starting with
  20170607.

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

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Gnome Night Light stays warmer after overnight suspend

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

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Veron Rado
Hi I have the same bug.
Night Light stays orange after waking from sleep.
Turing it on or off etc. doesn't fix it.



Ubuntu 17.04
Kernel: 4.10.0-32-generic x86_64 (64 bit gcc: 6.3.0)
Gnome 3.24.2 (Gtk 3.22.11-0ubuntu3)
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX 470/480]
   Display Server: X.Org 1.19.3 driver
   GLX Renderer: Gallium 0.4 on AMD POLARIS10 (DRM 3.9.0 / 
4.10.0-32-generic, LLVM 4.0.0)
   GLX Version: 3.0 Mesa 17.0.7 Direct Rendering: Yes

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

Title:
  Gnome Night Light stays warmer after overnight suspend

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

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1703073] Re: Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

2017-08-21 Thread Amr Ibrahim
I think the original GNOME Shell Dock already supports right-click
quicklists.

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

Title:
  Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if it can be re-enabled for Nautilus 3.24.

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

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


[Desktop-packages] [Bug 1712021] Re: totem randomly fails to build [error: Package `Totem-1.0' not found in specified Vala API directories or GObject-Introspection]

2017-08-21 Thread Bug Watch Updater
** Changed in: totem
   Status: Unknown => Confirmed

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

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

Title:
  totem randomly fails to build [error: Package `Totem-1.0' not found in
  specified Vala API directories or GObject-Introspection]

Status in Totem:
  Confirmed
Status in totem package in Ubuntu:
  New

Bug description:
  totem randomly fails to build:

  FAILED: 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin@sha/totem-zeitgeist-dp-plugin.c
 src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.h 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.vapi 
  valac -C --debug --pkg zeitgeist-2.0 --pkg libpeas-1.0 --pkg gtk+-3.0 --pkg 
clutter-gtk-1.0 -d src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin@sha 
--library=totem-zeitgeist-dp-plugin -H 
src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.h --vapi 
../totem-zeitgeist-dp-plugin.vapi --girdir=/home/dan/git/totem/build/src 
--pkg=Totem-1.0 ../src/plugins/zeitgeist-dp/bacon-video.vapi 
../src/plugins/zeitgeist-dp/totem-zeitgeist-dp-plugin.vala
  error: Package `Totem-1.0' not found in specified Vala API directories or 
GObject-Introspection GIR directories
  Compilation failed: 1 error(s), 0 warning(s)

  WORKAROUNDS:
  Avoid parallel builds:  ninja -j1
  or just keep retrying:
ninja
ninja
ninja
  and it will succeed after a few.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Mon Aug 21 16:38:16 2017
  InstallationDate: Installed on 2017-05-03 (110 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1705222] Re: package nvidia-libopencl1-331-updates 340.102-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it bef

2017-08-21 Thread Alberto Milone
It looks like a distro upgrade issue. Nothing security related.

Also, it is ok to attach nvidia-bug-report.log.gz.

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

Title:
  package nvidia-libopencl1-331-updates 340.102-0ubuntu0.16.04.1 failed
  to install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  en blanco

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-libopencl1-331-updates 340.102-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  340.102  Mon Jan 16 12:20:46 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 19 04:50:24 2017
  DistUpgraded: 2016-10-20 20:04:18,599 DEBUG disabling apt cron job (0o755)
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-81-generic, i686: installed
   nvidia-340, 340.102, 4.4.0-81-generic, i686: installed
  DuplicateSignature:
   package:nvidia-libopencl1-331-updates:340.102-0ubuntu0.16.04.1
   Processing triggers for cracklib-runtime (2.9.2-1build2) ...
   dpkg: error processing package nvidia-libopencl1-331-updates (--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
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GF119 [GeForce GT 520] [3842:1529]
  InstallationDate: Installed on 2011-02-26 (2334 days ago)
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-81-generic 
root=UUID=f205fb7e-f88a-4da8-9843-57927c92ed63 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-libopencl1-331-updates 340.102-0ubuntu0.16.04.1 failed 
to install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: Upgraded to xenial on 2016-10-21 (271 days ago)
  dmi.bios.date: 08/04/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A7DA-S/A7DA
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.1
  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.:bvr080015:bd08/04/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnA7DA-S/A7DA:rvr1.1:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jul 18 22:08:32 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputGenius Optical Mouse MOUSE, id 8
   inputHID 04f3:0103KEYBOARD, id 9
   inputHID 04f3:0103KEYBOARD, id 10
  xserver.errors: open /dev/fb0: No such file or

[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Veron Rado
Bug #1701772 seems to be a duplicate of this.

** Tags added: light night

** Tags removed: light night
** Tags added: nightlight

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

Title:
  Gnome Night Light stays warmer after overnight suspend

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

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

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

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


[Desktop-packages] [Bug 1701772] Re: Night Light does not reset after waking up system

2017-08-21 Thread Veron Rado
This seems to be a duplicate of Bug #1686895

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

Title:
  Night Light does not reset after waking up system

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

Bug description:
  I'm using the latest gnome on Antergos 64bit.

  I scheduled the Night Light to switch on between Sunset to Sunrise.

  Last night the Night Light switched on automatically after sunset and
  then I pressed the power on/off button on my machine to set my system
  to standby.

  This morning I resumed my session and noticed that the reddish filter
  was still visible however the Night Light was switched off.

  I tried switching the Night Light on and off but that didn't remove
  the reddish filter.

  I managed to remove the night light filter by changing the resolution
  momentarily to some other resolution setting and resetting to my
  native 4k resolution.

  Does this bug affect Ubuntu users too?

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

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


[Desktop-packages] [Bug 1666181] Re: gnome-system-monitor crashed with SIGSEGV in make_protobuf_object() from mir::client::rpc::MirProtobufRpcChannel::on_data_available()

2017-08-21 Thread Alan Griffiths
Probably the same cause as lp:1675749 (but not marking as dup yet as
need to confirm the problem isn't gtk-mir/qtubuntu)

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

Title:
  gnome-system-monitor crashed with SIGSEGV in make_protobuf_object()
  from mir::client::rpc::MirProtobufRpcChannel::on_data_available()

Status in Mir:
  New
Status in gnome-system-monitor package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  ubuntu 17.04 unity8 deb session
  gnome-system-monitor crashed with SIGSEGV

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: gnome-system-monitor 3.23.90-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity8
  Date: Mon Feb 20 12:29:22 2017
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2016-12-12 (69 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
  ProcCmdline: gnome-system-monitor
  Signal: 11
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
   ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
  Title: gnome-system-monitor crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

2017-08-21 Thread Viacheslav Semykrasov
Ubuntu 16.04, have the same issue

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Desktop-packages] [Bug 1696621] Re: Desktop icons slip under the top bar and dock after logging in

2017-08-21 Thread Daniel van Vugt
Or rather docks should implement:
https://specifications.freedesktop.org/wm-spec/wm-spec-1.3.html#NETWMSTRUT

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

Title:
  Desktop icons slip under the top bar and dock after logging in

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Desktop icons slip under the top bar after logging in again.

  If I place icons on the desktop in Gnome Shell they look fine, until I
  log out and log in again. On the second login they have moved half
  under the top bar.

  The same problem is visible in the Ubuntu live session starting with
  20170607.

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

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


[Desktop-packages] [Bug 1703073] Re: Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

2017-08-21 Thread Khurshid Alam
Gnome shell has jump-list (extension:
https://extensions.gnome.org/extension/33/jump-lists/) but it also
requires zeitgeist. It doesn't have any formal api yet.

For quicklist you can use this extension:
https://extensions.gnome.org/extension/322/quicklists/

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

Title:
  Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if it can be re-enabled for Nautilus 3.24.

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

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


[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

2017-08-21 Thread bersyl91
Hi,
Perhaps it'd be time to change this bug's status: if it's still marked as 
incomplete, never anybody will take a look on it :-(

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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


[Desktop-packages] [Bug 1639531] [NEW] GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs

2017-08-21 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Release of Ubuntu being used


Description:Ubuntu 16.10
Release:16.10

Version of the package being used
=

gcc:
  Installed: 4:6.1.1-1ubuntu2
  Candidate: 4:6.1.1-1ubuntu2
  Version table:
 *** 4:6.1.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
100 /var/lib/dpkg/status

What was expected
=

Programs compiled using `gcc -o program program.c` should be runnable by
double-clicking them from a GUI file manager.

Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
5.4.0-6ubuntu1~16.04.2)`) produces the following output from
`/usr/bin/file program`:

program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

This is correct behavior, allowing the executables to run from Nautilus
and Thunar.

What happened instead
=

Programs compiled using `gcc -o program program.c` are not runnable by
double-clicking them from a GUI file manager, even though they are
runnable from the terminal.

Compiling a simple program (`void main() { }`) using the current version
of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces the
following output from `/usr/bin/file program`:

program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

The program is also identified as a "shared library" instead of an
"executable" in Thunar, causing it to not be runnable from the GUI.
Others are unable to run such programs from Nautilus.

** Affects: gcc-defaults
 Importance: Medium
 Status: Unknown

** Affects: shared-mime-info (Ubuntu)
 Importance: High
 Status: Triaged


** Tags: amd64 apport-bug yakkety
-- 
GCC compiles programs to shared object instead of executable, preventing GUI 
file managers from executing programs
https://bugs.launchpad.net/bugs/1639531
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to shared-mime-info 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 1703073] Re: Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

2017-08-21 Thread Sebastien Bacher
** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if it can be re-enabled for Nautilus 3.24.

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

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


[Desktop-packages] [Bug 1701772] Re: Night Light does not reset after waking up system

2017-08-21 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1686895 ***
https://bugs.launchpad.net/bugs/1686895

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

** This bug has been marked a duplicate of bug 1686895
   Gnome Night Light stays warmer after overnight suspend

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

Title:
  Night Light does not reset after waking up system

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

Bug description:
  I'm using the latest gnome on Antergos 64bit.

  I scheduled the Night Light to switch on between Sunset to Sunrise.

  Last night the Night Light switched on automatically after sunset and
  then I pressed the power on/off button on my machine to set my system
  to standby.

  This morning I resumed my session and noticed that the reddish filter
  was still visible however the Night Light was switched off.

  I tried switching the Night Light on and off but that didn't remove
  the reddish filter.

  I managed to remove the night light filter by changing the resolution
  momentarily to some other resolution setting and resetting to my
  native 4k resolution.

  Does this bug affect Ubuntu users too?

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

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


[Desktop-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs

2017-08-21 Thread Matthias Klose
** Package changed: gcc-defaults (Ubuntu) => shared-mime-info (Ubuntu)

** Bug watch added: freedesktop.org Bugzilla #97226
   https://bugs.freedesktop.org/show_bug.cgi?id=97226

** Also affects: shared-mime-info via
   https://bugs.freedesktop.org/show_bug.cgi?id=97226
   Importance: Unknown
   Status: Unknown

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

Title:
  GCC compiles programs to shared object instead of executable,
  preventing GUI file managers from executing programs

Status in gcc-defaults:
  Unknown
Status in shared-mime-info:
  Unknown
Status in shared-mime-info package in Ubuntu:
  Triaged

Bug description:
  Release of Ubuntu being used
  

  Description:Ubuntu 16.10
  Release:16.10

  Version of the package being used
  =

  gcc:
    Installed: 4:6.1.1-1ubuntu2
    Candidate: 4:6.1.1-1ubuntu2
    Version table:
   *** 4:6.1.1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  What was expected
  =

  Programs compiled using `gcc -o program program.c` should be runnable
  by double-clicking them from a GUI file manager.

  Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
  current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
  5.4.0-6ubuntu1~16.04.2)`) produces the following output from
  `/usr/bin/file program`:

  program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  This is correct behavior, allowing the executables to run from
  Nautilus and Thunar.

  What happened instead
  =

  Programs compiled using `gcc -o program program.c` are not runnable by
  double-clicking them from a GUI file manager, even though they are
  runnable from the terminal.

  Compiling a simple program (`void main() { }`) using the current
  version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
  the following output from `/usr/bin/file program`:

  program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  The program is also identified as a "shared library" instead of an
  "executable" in Thunar, causing it to not be runnable from the GUI.
  Others are unable to run such programs from Nautilus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+subscriptions

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

** Package changed: gnome-control-center (Ubuntu) => gnome-settings-
daemon (Ubuntu)

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

Title:
  Gnome Night Light stays warmer after overnight suspend

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

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

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


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

2017-08-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

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

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

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

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

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

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

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

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

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

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


[Desktop-packages] [Bug 1639531] Re: GCC compiles programs to shared object instead of executable, preventing GUI file managers from executing programs

2017-08-21 Thread Bug Watch Updater
** Changed in: shared-mime-info
   Status: Unknown => Confirmed

** Changed in: shared-mime-info
   Importance: Unknown => Medium

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

Title:
  GCC compiles programs to shared object instead of executable,
  preventing GUI file managers from executing programs

Status in gcc-defaults:
  Unknown
Status in shared-mime-info:
  Confirmed
Status in shared-mime-info package in Ubuntu:
  Triaged

Bug description:
  Release of Ubuntu being used
  

  Description:Ubuntu 16.10
  Release:16.10

  Version of the package being used
  =

  gcc:
    Installed: 4:6.1.1-1ubuntu2
    Candidate: 4:6.1.1-1ubuntu2
    Version table:
   *** 4:6.1.1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  What was expected
  =

  Programs compiled using `gcc -o program program.c` should be runnable
  by double-clicking them from a GUI file manager.

  Compiling a simple program (`void main() { }`) using Xubuntu 16.04's
  current version of `gcc` (`gcc version 5.4.0 20160609 (Ubuntu
  5.4.0-6ubuntu1~16.04.2)`) produces the following output from
  `/usr/bin/file program`:

  program: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  This is correct behavior, allowing the executables to run from
  Nautilus and Thunar.

  What happened instead
  =

  Programs compiled using `gcc -o program program.c` are not runnable by
  double-clicking them from a GUI file manager, even though they are
  runnable from the terminal.

  Compiling a simple program (`void main() { }`) using the current
  version of `gcc` (`6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)`) produces
  the following output from `/usr/bin/file program`:

  program: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV),
  dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for
  GNU/Linux 2.6.32, BuildID[sha1]=signature_here, not stripped

  The program is also identified as a "shared library" instead of an
  "executable" in Thunar, causing it to not be runnable from the GUI.
  Others are unable to run such programs from Nautilus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-defaults/+bug/1639531/+subscriptions

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


[Desktop-packages] [Bug 1712039] [NEW] AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache

2017-08-21 Thread ts
Public bug reported:

The evince AppArmor profile seems to miss an entry for 
/var/lib/snapd/desktop/applications/mimeinfo.cache.
If evince is launched, the following gets logged to syslog:

kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011):
apparmor="DENIED" operation="open" profile="/usr/bin/evince"
name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268
comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

I don't know if this should be allowed or denied. If you could add the
correct behaviour to the profile, that would be nice; otherwise, every
time evince is launched, a notification pops up (apparmor-notify
installed).


(Workaround:

Add to original profile (/etc/apparmor.d/usr.bin.evince):
  #include 

Insert into local profile (/etc/apparmor.d/local/usr.bin.evince):
  /var/lib/snapd/desktop/applications/mimeinfo.cache r,
)

Release: Ubuntu 16.04.3 LTS
Package Version: evince-common 3.18.2-1ubuntu4.1

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

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

Title:
  AppArmor profile misses entry for
  /var/lib/snapd/desktop/applications/mimeinfo.cache

Status in evince package in Ubuntu:
  New

Bug description:
  The evince AppArmor profile seems to miss an entry for 
/var/lib/snapd/desktop/applications/mimeinfo.cache.
  If evince is launched, the following gets logged to syslog:

  kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011):
  apparmor="DENIED" operation="open" profile="/usr/bin/evince"
  name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268
  comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  I don't know if this should be allowed or denied. If you could add the
  correct behaviour to the profile, that would be nice; otherwise, every
  time evince is launched, a notification pops up (apparmor-notify
  installed).

  
  (Workaround:

  Add to original profile (/etc/apparmor.d/usr.bin.evince):
#include 

  Insert into local profile (/etc/apparmor.d/local/usr.bin.evince):
/var/lib/snapd/desktop/applications/mimeinfo.cache r,
  )

  Release: Ubuntu 16.04.3 LTS
  Package Version: evince-common 3.18.2-1ubuntu4.1

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

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


[Desktop-packages] [Bug 1683898] Re: Compose key can't be set in Settings>Keyboard with GNOME 3.24

2017-08-21 Thread Sebastien Bacher
** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Compose key can't be set in Settings>Keyboard with GNOME 3.24

Status in gnome-control-center:
  Confirmed
Status in Gnome Documentation:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-user-docs package in Ubuntu:
  Confirmed

Bug description:
  The changes implemented with https://bugs.launchpad.net/ubuntu/+source
  /ubuntu-docs/+bug/1624778 in https://help.gnome.org/users/gnome-
  help/stable/tips-specialchars.html.en#compose do not reflect the
  current settings dialog for Ubuntu-Gnome 17.04.

  Going from "All Settings" to "Keyboard" switches to "Keyboard Shortcuts" 
immediately.
  The new "Keyboard Shortcuts" dialog does not seem to contain settings for 
'compose key' (the group "Typing" only contains "Switch to {next,previous} 
input source").

  PS: In the meantime, where do I find the settings for 'compose key' in
  Ubuntu-Gnome 17.04? :(

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

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


[Desktop-packages] [Bug 1712011] Re: Unable to close Printer properties

2017-08-21 Thread Sebastien Bacher
Thank you for your bug report, that's a known issue that has been
submitted upstream on https://bugzilla.gnome.org/show_bug.cgi?id=784562

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

** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Triaged

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

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

Title:
  Unable to close Printer properties

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

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 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 N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 08:45:01 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
   inputUSB OPTICAL MOUSEMOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu3
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1708307] Re: Broken printer icon in Printers applet

2017-08-21 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

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

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

Title:
  Broken printer icon in Printers applet

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

Bug description:
  Clean install up to date of Artful. It found my HP networked printer.
  However looking in the panel I see a broken icon next to the name of
  the printer. I'm not sure what should be there, but expect a broken
  icon isn't it :)

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  2 23:41:19 2017
  InstallationDate: Installed on 2017-08-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  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/1708307/+subscriptions

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


[Desktop-packages] [Bug 1708307] Re: Broken printer icon in Printers applet

2017-08-21 Thread Sebastien Bacher
Do you get any warning/error about an icon if you start "gnome-control-
center -v"?

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

Title:
  Broken printer icon in Printers applet

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

Bug description:
  Clean install up to date of Artful. It found my HP networked printer.
  However looking in the panel I see a broken icon next to the name of
  the printer. I'm not sure what should be there, but expect a broken
  icon isn't it :)

  See screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  2 23:41:19 2017
  InstallationDate: Installed on 2017-08-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  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/1708307/+subscriptions

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


[Desktop-packages] [Bug 1711964] Re: Breaks Firefox if logging out or restating with firefox open

2017-08-21 Thread Sebastien Bacher
** Package changed: ubuntu-settings (Ubuntu) => firefox (Ubuntu)

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

Title:
  Breaks Firefox if logging out or restating with firefox open

Status in firefox package in Ubuntu:
  New

Bug description:
  Test case:
  open firefox, go to any page
  Only open 1 instance of firefox
  restart or log out/in without closing firefox

  What happens: when opening firefox in new login it opens to default startpage 
& is unresponsive
  What should happen: should either open to page on before or offer to reload 
that page, also should be usable
  This behavior not seen in ubuntu-web-launchers (17.10.10) package version

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-web-launchers 17.10.12
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 20 19:20:33 2017
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711953] Re: deja-dup-monitor crashed with signal 5 in g_settings_get_value()

2017-08-21 Thread Sebastien Bacher
** Information type changed from Private to Public

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

Title:
  deja-dup-monitor crashed with signal 5 in g_settings_get_value()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  This error was reported soon after start-up, when executing the
  command apt-get upgrade.  The system version is

  "Linux richard-desktop 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3
  15:14:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  The error occurred on date "Sun 20 Aug 21:30:32 BST 2017"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Aug 20 21:18:29 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-03-30 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  Signal: 5
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   deja_dup_migrate_settings () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
  Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1693480] Re: Nautilus contextual menu in dockbar doesn't show common paths

2017-08-21 Thread Sebastien Bacher
** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Nautilus contextual menu in dockbar doesn't show common paths

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When right clicking on the Files icon in GNOME dock (dash to dock) the
  options don't include common places like Documents, Pictures and so
  on.

  Expected:
  A behavior similar to what happened under Unity and with most other launchers.

  What happens:
  Only the following appear: New Window, Remove from Favorites, Details.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.24.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 25 12:50:39 2017
  InstallationDate: Installed on 2017-04-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711957] Re: gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()

2017-08-21 Thread Sebastien Bacher
** Information type changed from Private to Public

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

Title:
  gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()

Status in gvfs package in Ubuntu:
  New

Bug description:
  On startup of lubuntu 17.04 I get a message that system problem
  detected when logging into lxde.

  gvfs:
Installed: 1.33.90-0ubuntu1
Candidate: 1.33.90-0ubuntu1
Version table:
   *** 1.33.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  
  I expected lubuntu to start with no errors. Inseated I got a crash and a 
browser opened up about gvfs crashing.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gvfs-backends 1.33.90-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Wed Aug 16 14:08:43 2017
  ExecutablePath: /usr/lib/gvfs/gvfsd-recent
  InstallationDate: Installed on 2015-09-20 (699 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150920)
  ProcCmdline: /usr/lib/gvfs/gvfsd-recent --spawner :1.5 
/org/gtk/gvfs/exec_spaw/1
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7fb186da5afe :  mov
0x18(%rdi),%rax
   PC (0x7fb186da5afe) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   g_vfs_monitor_emit_event () from 
/usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_value_set_enum () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gvfsd-recent crashed with SIGSEGV in g_vfs_monitor_emit_event()
  UpgradeStatus: Upgraded to artful on 2017-08-06 (14 days ago)
  UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin lxd plugdev sambashare 
sudo

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

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


[Desktop-packages] [Bug 1712011] Re: Unable to close Printer properties

2017-08-21 Thread Charlie
Sorry, missed bug #784562.

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

Title:
  Unable to close Printer properties

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

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 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 N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 08:45:01 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
   inputUSB OPTICAL MOUSEMOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu3
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1712044] [NEW] AppArmor profile misses entries

2017-08-21 Thread ts
Public bug reported:

If Chromium is started, a plethora of AppArmor notifications are shown
(apparmor-notify installed) and logged to syslog.

I would expect that these are included in the supplied AppArmor profile
and no notifications/log entries appear.

Example in syslog:

kernel: [85217.346416] kauditd_printk_skb: 67 callbacks suppressed
kernel: [85217.346418] audit: type=1400 audit(1503309729.810:2095): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" 
name="/proc/1110/setgroups" pid=1110 comm="chromium-browse" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
kernel: [85217.346419] audit: type=1400 audit(1503309729.810:2096): 
apparmor="ALLOWED" operation="capable" 
profile="/usr/lib/chromium-browser/chromium-browser" pid=1110 
comm="chromium-browse" capability=21  capname="sys_admin"
kernel: [85217.346420] audit: type=1400 audit(1503309729.810:2097): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" name="/proc/1110/gid_map" 
pid=1110 comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
kernel: [85217.346420] audit: type=1400 audit(1503309729.810:2098): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" name="/proc/1110/uid_map" 
pid=1110 comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
kernel: [85217.347648] audit: type=1400 audit(1503309729.810:2099): 
apparmor="ALLOWED" operation="capable" 
profile="/usr/lib/chromium-browser/chromium-browser" pid=1069 
comm="chromium-browse" capability=21  capname="sys_admin"
kernel: [85217.348429] audit: type=1400 audit(1503309729.814:2100): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" 
name="/proc//setgroups" pid= comm="chromium-browse" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
kernel: [85217.348430] audit: type=1400 audit(1503309729.814:2101): 
apparmor="ALLOWED" operation="capable" 
profile="/usr/lib/chromium-browser/chromium-browser" pid= 
comm="chromium-browse" capability=21  capname="sys_admin"
kernel: [85217.348431] audit: type=1400 audit(1503309729.814:2102): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" name="/proc//uid_map" 
pid= comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
kernel: [85217.348432] audit: type=1400 audit(1503309729.814:2103): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" name="/proc//gid_map" 
pid= comm="chromium-browse" requested_mask="w" denied_mask="w" fsuid=1000 
ouid=1000
kernel: [85217.654651] audit: type=1400 audit(1503309730.118:2104): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser" 
name="/proc//setgroups" pid= comm="chromium-browse" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
kernel: [85262.883573] kauditd_printk_skb: 114 callbacks suppressed
kernel: [85262.883577] audit: type=1400 audit(1503309775.343:2219): 
apparmor="ALLOWED" operation="exec" 
profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings" 
name="/usr/bin/tr" pid=1299 comm="xdg-mime" requested_mask="x" denied_mask="x" 
fsuid=1000 ouid=0 
target="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr"
kernel: [85262.883658] audit: type=1400 audit(1503309775.343:2220): 
apparmor="ALLOWED" operation="file_inherit" 
profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr"
 name="/dev/null" pid=1299 comm="tr" requested_mask="w" denied_mask="w" 
fsuid=1000 ouid=0
kernel: [85262.883677] audit: type=1400 audit(1503309775.343:2221): 
apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr"
 name="/usr/bin/tr" pid=1299 comm="tr" requested_mask="rm" denied_mask="rm" 
fsuid=1000 ouid=0
kernel: [85262.883697] audit: type=1400 audit(1503309775.343:): 
apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr"
 name="/lib/x86_64-linux-gnu/ld-2.23.so" pid=1299 comm="tr" requested_mask="rm" 
denied_mask="rm" fsuid=1000 ouid=0
kernel: [85262.883802] audit: type=1400 audit(1503309775.343:2223): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr"
 name="/etc/ld.so.cache" pid=1299 comm="tr" requested_mask="r" denied_mask="r" 
fsuid=1000 ouid=0
kernel: [85262.883813] audit: type=1400 audit(1503309775.343:2224): 
apparmor="ALLOWED" operation="open" 
profile="/usr/lib/chromium-browser/chromium-browser//xdgsettings//null-/usr/bin/tr"
 name="/lib/x86_64-linux-gnu/libc-2.23.so" pid=1299 comm="tr" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
kernel: [85262.883826] audit: type=1400 audit(1503309775.343:2225): 
apparmor="ALLOWED" operation="file_mmap" 
profile="/usr/l

[Desktop-packages] [Bug 1703073] Re: Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

2017-08-21 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1693480 ***
https://bugs.launchpad.net/bugs/1693480

** This bug has been marked a duplicate of bug 1693480
   Nautilus contextual menu in dockbar doesn't show common paths

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

Title:
  Re-enable unity-launcher quicklist bookmark support for Nautilus 3.24

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  It would be nice if it can be re-enabled for Nautilus 3.24.

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

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


[Desktop-packages] [Bug 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90

2017-08-21 Thread Jeremy Bicha
The crash comes from 0002-Only-use-a-header-bar-in-GNOME-shell.patch so
I disabled that patch since it wasn't clear to me what isn't working
after rebasing on 3.25. Someone interested in Unity development can take
a look at that, but I don't see a need to delay Nautilus updates because
of that. Uploaded.

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

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

Title:
  Unity support patch doesn't build with nautilus 3.25.90

Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu
  17.10 "artful".

  The 12_unity_launcher_support.patch has a problem that fails the build
  and I don't know how to fix it so I disabled the patch for now.

  Nautilus 3.25 introduces meson support and drops autotools support so
  that's one factor when I updated the patch.

  But when I disable the patch, nautilus crashes on start in Unity.

  Build log attached.

  Build Log Excerpt
  ==

  [164/222] cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. 
-I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  FAILED: src/nautilus@sta/unity-quicklist-handler.c.o
  cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ 
-Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  ../src/unity-quicklist-handler.c: In function 
‘unity_quicklist_handler_get_singleton’:
  ../src/unity-quicklist-handler.c:154:9: error: expected declaration or 
statement at end of input
   unity_quicklist_handler_singleton = unity_quicklist_handler_new ();
   ^
  ../src/unity-quicklist-handler.c:154:9: error: expected declaration or 
statement at end of input

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

-- 
Mailing list: https://lau

[Desktop-packages] [Bug 991471] Re: multi-device btrfs filesystem automatically mounted once for each device

2017-08-21 Thread Rolf Leggewie
Interestingly enough, one of my trusty computers apparently does not
exhibit this behaviour, even though udisks2 is installed.  Partitions
get mounted via udisks2, too.

Unfortunately, the problem seems to have gotten much worse in the latest
development release.  Whereas previously, each btrfs device of the btrfs
FS would be mounted once, it seems that in artful, one new mount happens
every few minutes.  I came back to over 20 mounts on a three-device
btrfs FS after a few hours.  This was on a very recent live CD.

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

Title:
  multi-device btrfs filesystem automatically mounted once for each
  device

Status in btrfs package in Ubuntu:
  Invalid
Status in btrfs-tools package in Ubuntu:
  Confirmed
Status in udev package in Ubuntu:
  Confirmed
Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  If I have a multi-device btrfs filesystem, and I plug it in via some
  removable interface (for example, USB3), it will automatically mount
  on the desktop multiple times.  For example, if I have a filesystem
  labeled FooBar on /dev/sdb /dev/sdc /dev/sdd and /dev/sde, it will be
  mounted as /media/FooBar, /media/FooBar1, /media/FooBar2, and
  /media/FooBar3.  It should show up only once.

  It seems like everything still basically works, but I didn't test
  writing to said filesystem under the different aliases.

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

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


[Desktop-packages] [Bug 1707056] Re: Installation progress goes several times to 100%

2017-08-21 Thread Iain Lane
I think it's probably once for downloading and once for installation,
slightly annoying I agree.

I filed it upstream, thanks for reporting!

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

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

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

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

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

Title:
  Installation progress goes several times to 100%

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

Bug description:
  Using 3.25.4 from artful proposed, when installing a deb the progress
  bar goes to 100% at the start of the installation then drop and raise
  again, it was not doing that before

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

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


[Desktop-packages] [Bug 1712011] Re: Unable to close Printer properties

2017-08-21 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => Confirmed

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

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

Title:
  Unable to close Printer properties

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

Bug description:
  From settings I open Printers and click on settings (gear icon) for my
  printer which bring up a pop-up with printer details (name , location,
  address, etc). There is no way to close this pop-up. Instead of a top
  toolbar there is thin dark line. The pop-up cannot be moved.

  Occurs using 17.10 default and Wayland.

  Screenshot added

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: i386
  BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 21 08:55:08 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Radeon HD 6670 [1028:0b0e]
  InstallationDate: Installed on 2017-07-14 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1)
  MachineType: Dell Inc. OptiPlex 9010
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0M9KCM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9010
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 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 N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 21 08:45:01 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSennheiser Sennheiser USB Headset KEYBOARD, id 8
   inputDELL Dell USB Entry Keyboard KEYBOARD, id 9
   inputUSB OPTICAL MOUSEMOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu3
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90

2017-08-21 Thread Launchpad Bug Tracker
This bug was fixed in the package nautilus - 1:3.25.90-0ubuntu1

---
nautilus (1:3.25.90-0ubuntu1) artful; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release.
  * Build with meson.
  * Refresh patches.
  * Drop build-with-tracker2.patch: Applied in new release
  * Disable 0002-Only-use-a-header-bar-in-GNOME-shell.patch:
- Nautilus crashes in Unity with this patch.
  * Add git_desktop-remove-spaces.patch:
- Backport commit to fix .desktop by removing spaces from MimeType line

  [ Khurshid Alam ]
  * 12_unity_launcher_support.patch:
- Restore lines accidentally dropped in previous merge, fixes build
  failure (LP: #1711241)

 -- Khurshid Alam   Mon, 21 Aug 2017
05:55:14 -0400

** Changed in: nautilus (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Unity support patch doesn't build with nautilus 3.25.90

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu
  17.10 "artful".

  The 12_unity_launcher_support.patch has a problem that fails the build
  and I don't know how to fix it so I disabled the patch for now.

  Nautilus 3.25 introduces meson support and drops autotools support so
  that's one factor when I updated the patch.

  But when I disable the patch, nautilus crashes on start in Unity.

  Build log attached.

  Build Log Excerpt
  ==

  [164/222] cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. 
-I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  FAILED: src/nautilus@sta/unity-quicklist-handler.c.o
  cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ 
-Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  ../src/unity-quicklist-handler.c: In function 
‘unity_quicklist_handler_get_singleton’:
  ../src/unity-quicklist-handler.c:154:9: error: expected

[Desktop-packages] [Bug 1707056] Re: Installation progress goes several times to 100%

2017-08-21 Thread Bug Watch Updater
** Changed in: gnome-software
   Status: Unknown => Confirmed

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

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

Title:
  Installation progress goes several times to 100%

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

Bug description:
  Using 3.25.4 from artful proposed, when installing a deb the progress
  bar goes to 100% at the start of the installation then drop and raise
  again, it was not doing that before

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

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


[Desktop-packages] [Bug 1711382] Re: Slow Firefox performance and high CPU load when tlp is installed

2017-08-21 Thread Wolf Rogner
tlp 0.9-3 (Ubuntu 17.04 default)
No changes to default config made.

Issues are:
higher CPU load (not only in Firefox)
not fully charged battery on laptops (stops at 94% of capacity)
kicks in fans arbitrarily (even when CPU temp is below average normal state)
terminates bluetooth connections every 2 mins
terminates network connections every 2-5 mins

Possibly effects systemd-resolverd.service as well - terminates name
resolution every 5-10 mins (had one issue after deinstall, therefore not
100% confident in this)


Mind: deinstalling eliminates a set of issues (see above).

Maybe you check whether machine is a thinkpad and only install then.

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

Title:
  Slow Firefox performance and high CPU load when tlp is installed

Status in firefox package in Ubuntu:
  New
Status in tlp package in Ubuntu:
  New

Bug description:
  After installing Firefox 55 the browser generates huge cpu load,
  startup is extremely slow (it takes > 10s for the taskbar to accept
  entries after launch (this is new to 55)

  Due to high cpu load the computer tends to overheat, ventilation jumps
  in making the machine extremely loud.

  Using Chromium does not show these symptoms (on the same page).

  
  ---
  LSB Ubuntu 17.04 (budgie desktop)
  firefox:
Installed: 55.0.1+build2-0ubuntu0.17.04.2
Candidate: 55.0.1+build2-0ubuntu0.17.04.2
Version table:
   *** 55.0.1+build2-0ubuntu0.17.04.2 500
  500 http://archive.ubuntu.com/ubuntu zesty-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   50.1.0+build2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 55.0.1+build2-0ubuntu0.17.04.2
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BuildID: 20170814193419
  CurrentDesktop: Budgie:GNOME
  Date: Thu Aug 17 16:30:30 2017
  InstallationDate: Installed on 2017-05-25 (83 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90

2017-08-21 Thread Sebastien Bacher
Jeremy, how does the new version handle fts if tracker is not installed?
Does it hide the corresponding UI elements? Upstream hinted that tracked
was an hard requirement now with that version...

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

Title:
  Unity support patch doesn't build with nautilus 3.25.90

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu
  17.10 "artful".

  The 12_unity_launcher_support.patch has a problem that fails the build
  and I don't know how to fix it so I disabled the patch for now.

  Nautilus 3.25 introduces meson support and drops autotools support so
  that's one factor when I updated the patch.

  But when I disable the patch, nautilus crashes on start in Unity.

  Build log attached.

  Build Log Excerpt
  ==

  [164/222] cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. 
-I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  FAILED: src/nautilus@sta/unity-quicklist-handler.c.o
  cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ 
-Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  ../src/unity-quicklist-handler.c: In function 
‘unity_quicklist_handler_get_singleton’:
  ../src/unity-quicklist-handler.c:154:9: error: expected declaration or 
statement at end of input
   unity_quicklist_handler_singleton = unity_quicklist_handler_new ();
   ^
  ../src/unity-quicklist-handler.c:154:9: error: expected declaration or 
statement at end of input

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

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

[Desktop-packages] [Bug 1712039] Re: AppArmor profile misses entry for /var/lib/snapd/desktop/applications/mimeinfo.cache

2017-08-21 Thread Sebastien Bacher
The file is not specific to evince, that's probably better placed in a
common file from appamor itself right?

** Package changed: evince (Ubuntu) => apparmor (Ubuntu)

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

Title:
  AppArmor profile misses entry for
  /var/lib/snapd/desktop/applications/mimeinfo.cache

Status in apparmor package in Ubuntu:
  New

Bug description:
  The evince AppArmor profile seems to miss an entry for 
/var/lib/snapd/desktop/applications/mimeinfo.cache.
  If evince is launched, the following gets logged to syslog:

  kernel: [81577.596186] audit: type=1400 audit(1503306090.062:2011):
  apparmor="DENIED" operation="open" profile="/usr/bin/evince"
  name="/var/lib/snapd/desktop/applications/mimeinfo.cache" pid=32268
  comm="evince" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  I don't know if this should be allowed or denied. If you could add the
  correct behaviour to the profile, that would be nice; otherwise, every
  time evince is launched, a notification pops up (apparmor-notify
  installed).

  
  (Workaround:

  Add to original profile (/etc/apparmor.d/usr.bin.evince):
#include 

  Insert into local profile (/etc/apparmor.d/local/usr.bin.evince):
/var/lib/snapd/desktop/applications/mimeinfo.cache r,
  )

  Release: Ubuntu 16.04.3 LTS
  Package Version: evince-common 3.18.2-1ubuntu4.1

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

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


[Desktop-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

2017-08-21 Thread Dimitri John Ledkov
This conflicts with desire to ship functional Unity7 experience in
17.10.

** Changed in: gnome-control-center-signon (Ubuntu)
 Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

** Changed in: gnome-control-center-signon (Ubuntu)
   Status: New => Incomplete

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit bug 1707794
  account-polld
  (pay-service removed)
  (qtpurchasing-opensource-src removed)
  storage-provider-webdav bug 1707799
  (sync-monitor removed)
  ubuntuone-credentials bug 1707798
  (ubuntu-push removed)
  unity-china-photo-scope
  unity-scope-gdrive bug 1707796

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper #1707801
  mcloud
  (address-book-app removed)
  address-book-service
  (dialer-app removed)
  (messaging-app removed)
  telephony-service bug 1707802
  tone-generator bug 1707802
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  (camera-app removed)
  indicator-transfer
  indicator-transfer-buteo
  libertine
  (ubuntu-experience-tests removed)
  unity-scopes-shell bug 1707797
  (unity8 removed)

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

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

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


[Desktop-packages] [Bug 1711791] Re: Remove the word 'Ubuntu' from 'Ubuntu Dock settings'

2017-08-21 Thread Sebastien Bacher
Hey Matthew, would you maybe have an opinion on this one?


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

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

Title:
  Remove the word 'Ubuntu' from 'Ubuntu Dock settings'

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

Bug description:
  I suggest removing the word 'Ubuntu' from 'Ubuntu Dock settings'. Just
  say 'Dock Settings'. It is meaningful enough. See the screenshot from
  Didier Roche.

  1:3.24.3-0ubuntu4 in Artful.

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

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


[Desktop-packages] [Bug 1705122] Re: Installed snaps do not appear among other apps in menus when using Wayland

2017-08-21 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1681547 ***
https://bugs.launchpad.net/bugs/1681547

that's bug #1681547

** This bug has been marked a duplicate of bug 1681547
   Gnome3 on Ubuntu 17.04 doesn't find snap desktop files

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

Title:
  Installed snaps do not appear among other apps in menus when using
  Wayland

Status in snapd package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  I installed the snap telegram-sergiusens but it doesn't appear among
  the other applications in the menu and I can't search for it from the
  Activities menu (GNOME Shell).

  I'm trying this from a Wayland session, I don't know if this can be
  related in any way.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: snapd 2.26.10+17.10
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 18 22:39:57 2017
  InstallationDate: Installed on 2015-03-21 (850 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago)

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

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


[Desktop-packages] [Bug 1711897] Re: gnome-control-center crashed with signal 5 in g_settings_get_value()

2017-08-21 Thread Sebastien Bacher
thanks, it seems the same issue than bug #1711920, does removing your
local schemas fixes the bug?

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

** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with signal 5 in g_settings_get_value()

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

Bug description:
  Clicking on 'Displays' will crash the program.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 20 18:40:32 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-08-20 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
  Title: gnome-control-center crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: Upgraded to artful on 2017-08-20 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1711792] Re: Replace the word 'Launcher' with 'Dock' in Dock settings

2017-08-21 Thread Sebastien Bacher
Hey Matthew, would you maybe have an opinion on this one?

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

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

Title:
  Replace the word 'Launcher' with 'Dock' in Dock settings

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

Bug description:
  I suggest to replace the word 'Launcher' with 'Dock' in the Dock
  settings section. Launcher was for Unity7. Dock is for GNOME Shell.
  See the screenshot from Didier Roche.

  1:3.24.3-0ubuntu4 in Artful.

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

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


[Desktop-packages] [Bug 1680438] Re: gnome-calculator comes up with totally wrong answer

2017-08-21 Thread Sebastien Bacher
** Changed in: gnome-calculator (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  gnome-calculator comes up with totally wrong answer

Status in GNOME Calculator:
  Confirmed
Status in gnome-calculator package in Ubuntu:
  Triaged

Bug description:
  Confirmed on:
   - Ubuntu 16.04.1: gnome-calculator version 1:3.18.3-0ubuntu1
   - Ubuntu 16.04.2: gnome-calculator version 1:3.18.3-0ubuntu1.16.04.1

  To reproduce the bug (have tried on multiple computers) do something
  along these lines in the gnome-calculator app:

   - Press 7 and Enter.  Screen should show 7 = 7, input field should show 7.
   - Press left arrow and type 12, then the right arrow and type +7.  Input 
field should show 127+7.
   - Press Enter.  Screen will show 127+7 = 91, input field will show 91.

  No scientific modes or anything; this is in normal mode.

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

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


[Desktop-packages] [Bug 1711241] Re: Unity support patch doesn't build with nautilus 3.25.90

2017-08-21 Thread Jeremy Bicha
Ok, I see now that there is a drop-down connected to the Search field
that offers the choice between "Full Text" and "File Name". Without
tracker running, they both do the same thing.

tracker is now a required build-dependency for nautilus (not a problem
since we've already been doing that for all Ubuntu architectures).

Without tracker running, you won't have the new full text search. The
Batch Rename feature allows renaming using metadata but that won't work
either.

Of course the nautilus maintainer doesn't like us not including tracker
by default but the app is still usable without tracker: it's just not as
nice and search is likely slower.

One more issue: assuming we don't install tracker by default for Ubuntu
17.10 and assuming the issue isn't fixed, I intend to release note
https://bugs.debian.org/865496

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

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

Title:
  Unity support patch doesn't build with nautilus 3.25.90

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I have prepared nautilus 3.25.90 in the GNOME3 Staging PPA for Ubuntu
  17.10 "artful".

  The 12_unity_launcher_support.patch has a problem that fails the build
  and I don't know how to fix it so I disabled the patch for now.

  Nautilus 3.25 introduces meson support and drops autotools support so
  that's one factor when I updated the patch.

  But when I disable the patch, nautilus crashes on start in Unity.

  Build log attached.

  Build Log Excerpt
  ==

  [164/222] cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. 
-I../ -Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  FAILED: src/nautilus@sta/unity-quicklist-handler.c.o
  cc  -Isrc/nautilus@sta -Isrc -Isubprojects/libgd/libgd -I../src -I. -I../ 
-Isubprojects/libgd -I../subprojects/libgd -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/mirclient -I/usr/include/mircore 
-I/usr/include/mircookie -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/gnome-autoar-0 -I/usr/include/libxml2 
-I/usr/include/zeitgeist-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/gail-3.0 -I/usr/include/gnome-desktop-3.0 
-I/usr/include/tracker-2.0 -I/usr/include/tracker-2.0/libtracker-sparql 
-I/usr/include/libexif -I/usr/include/unity/unity -I/usr/include/dee-1.0 
-I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/exempi-2.0 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 
-Wno-deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -pthread -DLIBGD_GTK_HACKS=1 -DLIBGD__VIEW_COMMON=1 
-DLIBGD_MAIN_ICON_VIEW=1 -DLIBGD_MAIN_LIST_VIEW=1 -DLIBGD_MAIN_VIEW=1 
-DLIBGD_TAGGED_ENTRY=1 -MMD -MQ 'src/nautilus@sta/unity-quicklist-handler.c.o' 
-MF 'src/nautilus@sta/unity-quicklist-handler.c.o.d' -o 
'src/nautilus@sta/unity-quicklist-handler.c.o' -c 
../src/unity-quicklist-handler.c
  ../src/unity

[Desktop-packages] [Bug 1682544] Re: xkill doesn't grab pointer in gnome/weyland

2017-08-21 Thread Jean-Baptiste Lallement
Thanks for your report.

This is a known issue with wayland documented upstream on
https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Many_well-
known_X11_utilities_don.27t_work

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

** Changed in: x11-utils (Ubuntu)
   Importance: Undecided => Low

** Changed in: x11-utils (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  xkill doesn't grab pointer in gnome/weyland

Status in x11-utils package in Ubuntu:
  Triaged

Bug description:
  1. 
  > xkill 

  expected result:
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) pointer turns to an X
  c) you can click on a window
  d) that window's process gets killed

  what actually happens
  a) output: "Select the window whose client you wish to kill with button 1..."
  b) The pointer goes invisible, until you move it, then it goes to the normal 
pointer.
  ...that's it.

  Ubuntu: 17.04 / zesty
  Desktop environment: Gnome/Weyland 
  x11-utils: 7.7+3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: x11-utils 7.7+3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Thu Apr 13 13:40:03 2017
  DistUpgraded: 2017-04-13 12:41:16,896 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0689]
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0689]
  InstallationDate: Installed on 2014-07-09 (1008 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  MachineType: Acer TravelMate P273-MG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=885e04f0-bd26-4885-aa1c-f134c674b8ff ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
  SourcePackage: x11-utils
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (0 days ago)
  dmi.bios.date: 11/27/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: BA70_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.11:bd11/27/2013:svnAcer:pnTravelMateP273-MG:pvrV2.11:rvnAcer:rnBA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: TravelMate P273-MG
  dmi.product.version: V2.11
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Thu Apr 13 12:45:10 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x11-utils/+bug/1682544/+subscriptions

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


[Desktop-packages] [Bug 1616742] Re: xdiagnose does nothing in Wayland

2017-08-21 Thread Jean-Baptiste Lallement
** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Triaged

** Changed in: xdiagnose (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  xdiagnose does nothing in Wayland

Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in xdiagnose package in Ubuntu:
  Triaged

Bug description:
  What happens
  ===
  1. Try Ubuntu GNOME 16.10 Beta on a computer using open source graphics 
drivers (Intel is recommended).
  2. On the login screen, select your user name. Before entering your password, 
click the gear button and choose "GNOME on Wayland". Enter your password and 
log in.
  3. Try to run xdiagnose.
  4. Nothing happens

  What I expected
  ===
  1. xdiagnose could be adapted to analyze and report issues with Wayland
  2. xdiagnose could explain why it doesn't work on Wayland
  3. Otherwise, it would be nice if xdiagnose wouldn't show up in the 
Activities Overview when Wayland is running but that's more complicated. (Maybe 
XDG_CURRENT_DESKTOP could be expanded to add Wayland as a string and 
xdiagnose.desktop could add NotShowIn=Wayland)

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

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


[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

2017-08-21 Thread Alberto Salvia Novella
Please in (https://bugzilla.gnome.org/show_bug.cgi?id=734959):

- Add you to the CC list.
- Answer the developers questions.

Thank you.

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Fix Released
Status in GNOME Settings Daemon:
  Incomplete
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in Ubuntu GNOME trusty series:
  Confirmed
Status in Ubuntu GNOME xenial series:
  Confirmed
Status in Ubuntu GNOME Flashback:
  Confirmed
Status in Unity:
  New
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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


[Desktop-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

2017-08-21 Thread Jeremy Bicha
My understanding is that the Ubuntu Desktop team agreed a few months ago
to drop UOA.

We dropped UOA support from Empathy, Evolution Data Server, Shotwell,
and the Unity lenses.

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

Title:
  Please remove obsolete UOA packages

Status in gnome-control-center-signon package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit bug 1707794
  account-polld
  (pay-service removed)
  (qtpurchasing-opensource-src removed)
  storage-provider-webdav bug 1707799
  (sync-monitor removed)
  ubuntuone-credentials bug 1707798
  (ubuntu-push removed)
  unity-china-photo-scope
  unity-scope-gdrive bug 1707796

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper #1707801
  mcloud
  (address-book-app removed)
  address-book-service
  (dialer-app removed)
  (messaging-app removed)
  telephony-service bug 1707802
  tone-generator bug 1707802
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  (camera-app removed)
  indicator-transfer
  indicator-transfer-buteo
  libertine
  (ubuntu-experience-tests removed)
  unity-scopes-shell bug 1707797
  (unity8 removed)

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

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

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


[Desktop-packages] [Bug 1377197] Re: Typographies in resources axis doesn't follow scale for menus and title bars

2017-08-21 Thread Bug Watch Updater
** Changed in: gnome-system-monitor
   Status: New => Confirmed

** Changed in: gnome-system-monitor
   Importance: High => Medium

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

Title:
  Typographies in resources axis doesn't follow scale for menus and
  title bars

Status in Gnome System Monitor:
  Confirmed
Status in One Hundred Papercuts:
  Triaged
Status in gnome-system-monitor package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  1. Open the "System Monitor" application.
  2. Go to the "Resources" tab.
  3. Open the "System Settings" application.
  4. Go to the "Screen Display" section.
  5. Change the value for the "scale for menu and tittle bars".

  EXPECTED BEHAVIOUR:
  - Axis to change its typography size.

  REAL BEHAVIOUR:
  - Axis typography size stays the same, making it difficult to read in high 
resolution screens; as seen in the attached screen-shot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-system-monitor 3.8.2.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  3 16:59:03 2014
  InstallationDate: Installed on 2013-05-21 (500 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-system-monitor
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (9 days ago)

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

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


[Desktop-packages] [Bug 1712072] [NEW] Setting attribute metadata::gedit-encoding not supported

2017-08-21 Thread dino99
Public bug reported:

Have written a couple sentences with gedit, and then called the printer.
That error has been displayed into the terminal:

 (gedit:22402): WARNING **: Set document metadata failed: Setting
attribute metadata::gedit-encoding not supported


Spell-checker was enabled.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 21 15:02:49 2017
EcryptfsInUse: Yes
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
   Setting attribute metadata::gedit-encoding not supported

Status in gedit package in Ubuntu:
  New

Bug description:
  Have written a couple sentences with gedit, and then called the printer.
  That error has been displayed into the terminal:

   (gedit:22402): WARNING **: Set document metadata failed: Setting
  attribute metadata::gedit-encoding not supported

  
  Spell-checker was enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 21 15:02:49 2017
  EcryptfsInUse: Yes
  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/1712072/+subscriptions

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


[Desktop-packages] [Bug 1711605] Re: a2dp profile still alive even though disconnected

2017-08-21 Thread Chanho Park
Hi,

You picked wrong patch for "bluetooth: Add optional heuristic for switching 
between hsp and a2dp profiles"[1]
Originally, it was written without "bluetooth-policy: do A2DP profile restoring 
a bit later"[2] and it was overwritten the [2] code. Please see the patch order 
and patch result.

-/* If there are still some source outputs do nothing. */   

  
-if (source_output_count(c) > 0)

  
+/* If there are still some source outputs do nothing (count is with *this* 
source_output, so +1) */
  
+if (source_output_count(c, userdata) > 1)


[1]: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=3397127f0045d3c130b59e59b4ce6b3601b239b9
[2]: 
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=2250dbfd6968bd9ce295fc7bef8595b2c6ef6a44

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

Title:
  a2dp profile still alive even though disconnected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  During connect/disconnect with BT headset repeatedly, the bluetooth
  connection(check using hcitool) is still alive even thoush the
  connection has been disconnected by bluetoothctl. The hsp profile is
  still connected on pulseaudio.

  ---

  Since the pulseaudio of Xenial has been updated from 8.0-0ubuntu3.2 to 
8.0-0ubuntu3.3 at last May, I failed my TestCase The test case is just 
repeating connect/disconnect with BT headset through bluetoothctl.
  The change[1] can be retrieved from Xenial's pulseaudio source but I can't 
ensure which patch causes the problem.
  You can see the error log[2] when the error has been occurred.

  [1] pulseaudio (1:8.0-0ubuntu3.3) xenial; urgency=medium

    [Luke Yelavich, Konrad Zapałowicz]
    * Fixed multiple interrelated problems with using Bluetooth audio (A2DP),
  where users would experience some combination of:
  - Bluetooth headset/speakers listed but not selectable in Sound settings
    (LP: #1283003)
  - [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP
    mode) (LP: #1438510)
  - [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set
    to HSP/HFP first (LP: #1582213)
    * Specific patches from upstream used to address the above problems:
  - 0103-bluetooth-Add-support-for-automatic-switch-between-h.patch
  - 0104-bluetooth-Add-support-for-automatic-switch-bluez5.patch
  - 0106-bluetooth-Add-optional-heuristic-for-switching-betwe.patch
    . Backport from upstream to fix a bug in Xenial where an incorrect
  audio profile is applied for a headset connected over Bluetooth
  making using it impossible.
  - 0105-bluetooth-policy-do-A2DP-profile-restoring-a-bit-lat.patch
    . Fix a crash that happens if the BT headset is the only non-monitor
  source in the system and the last "phone" stream dies.
  - 0700-pulsecore-add-new-card-profile-hook.patch
    . Backport from upstream (commit 7b6260140149) to allow for correct
  profile selection.
  - 0701-bluetooth-bluez5-wait-for-all-profiles-to-connect.patch
    . Backport from upstream waiting for all profiles to connect before
  creating a card.

   -- Daniel van Vugt   Tue, 23 May 2017
  16:24:14 +0800

  [2] Error log
  D: [pulseaudio] backend-native.c: dbus: path=/Profile/HSPAGProfile, 
interface=org.bluez.Profile1, member=NewConnection
  D: [pulseaudio] backend-native.c: dbus: NewConnection 
path=/org/bluez/hci0/dev_00_18_09_2C_1F_41, fd=18
  D: [pulseaudio] bluez5-util.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 state changed from disconnected to 
idle
  D: [pulseaudio] backend-native.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd18 available for profile 
headset_head_unit
  D: [pulseaudio] backend-native.c: RFCOMM << AT+VGS=07
  D: [pulseaudio] backend-native.c: RFCOMM >> OK
  D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, 
interface=org.bluez.MediaEndpoint1, member=SelectConfiguration
  D: [pulseaudio] bluez5-util.c: Unknown interface 
org.freedesktop.DBus.Introspectable found, skipping
  D: [pulseaudio] bluez5-util.c: Unknown interface org.bluez.MediaTransport1 
found, skipping
  D: [pulseaudio] bluez5-util.c: Unknown interface 
org.freedesktop.DBus.Properties found, skipping
  D: [pulseaudio] bluez5-util.c: dbus: path=/MediaEndpoint/A2DPSource, 
interface=org.bluez.MediaEndpoint1, member=SetConfiguration
  D: [pulseaudio] bluez5-util.c: Transport 
/org/bluez/hci0/dev_00_18_09_2C_1F_41/fd6 state changed from disconnected to 
idle
  D: [pulseaudio] bluez5-util.c: Transport 
/org/bluez/hc

[Desktop-packages] [Bug 1712080] [NEW] wayland: blank additioanl screen in maximum resolution

2017-08-21 Thread Adrian
Public bug reported:

I use a docking station to which I have connected 2 screens: first one
directly through the display port, second through DVI connector (from
which signal passes DVI-HDMI converter and finally to the screen). In
default gnome session, the two extra screens are set in their maximum
resolution (2560x1440@60). In Wayland session, one the second screen
gets off although it is properly detected in the screen settings. In
order to make it work, I need to decrease its resolution (2048x1152).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-session-wayland 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 21 15:31:50 2017
InstallationDate: Installed on 2015-04-02 (872 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: Upgraded to zesty on 2017-04-18 (125 days ago)

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


** Tags: amd64 apport-bug wayland-session 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/1712080

Title:
  wayland: blank additioanl screen in maximum resolution

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I use a docking station to which I have connected 2 screens: first one
  directly through the display port, second through DVI connector (from
  which signal passes DVI-HDMI converter and finally to the screen). In
  default gnome session, the two extra screens are set in their maximum
  resolution (2560x1440@60). In Wayland session, one the second screen
  gets off although it is properly detected in the screen settings. In
  order to make it work, I need to decrease its resolution (2048x1152).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-session-wayland 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 21 15:31:50 2017
  InstallationDate: Installed on 2015-04-02 (872 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (125 days ago)

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

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Veron Rado
Reported upstream
https://bugzilla.gnome.org/show_bug.cgi?id=786569

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

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

Title:
  Gnome Night Light stays warmer after overnight suspend

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686895/+subscriptions

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


[Desktop-packages] [Bug 1695928] Re: Please remove obsolete UOA packages

2017-08-21 Thread Sebastien Bacher
right, we try to keep unity7 working as best as possible but we can't
hold on other work or keep unmaintained components in the archive
because of it so it's accepted that some features are going to be
missing in the new version

** Changed in: gnome-control-center-signon (Ubuntu)
   Status: Incomplete => New

** Changed in: gnome-control-center-signon (Ubuntu)
 Assignee: Ubuntu Desktop (ubuntu-desktop) => (unassigned)

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

Title:
  Please remove obsolete UOA packages

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

Bug description:
  Ubuntu Online Accounts is no longer maintained. There is an
  alternative, GNOME Online Accounts for the GNOME desktop.

  Also, Unity's Online Accounts settings panel does not currently work
  without oxide-qt but oxide-qt will be removed from Ubuntu 17.10.

  Please remove these source packages and their binaries:
  =

  Phase 1
  ---
  gnome-control-center-signon
  account-plugins
  account-plugin-fitbit bug 1707794
  account-polld
  (pay-service removed)
  (qtpurchasing-opensource-src removed)
  storage-provider-webdav bug 1707799
  (sync-monitor removed)
  ubuntuone-credentials bug 1707798
  (ubuntu-push removed)
  unity-china-photo-scope
  unity-scope-gdrive bug 1707796

  By the way, gnome-control-center-signon fails to build with vala 0.36:
  
https://launchpadlibrarian.net/324396241/buildlog_ubuntu-artful-amd64.gnome-control-center-signon_0.1.9+16.10.20160825-0ubuntu1~ubuntu17.10.1_BUILDING.txt.gz

  Phase 2
  ---
  ubuntu-system-settings-online-accounts
  online-accounts-api
  storage-framework
  keeper #1707801
  mcloud
  (address-book-app removed)
  address-book-service
  (dialer-app removed)
  (messaging-app removed)
  telephony-service bug 1707802
  tone-generator bug 1707802
  ubuntu-system-settings
  buteo-sync-plugins-contacts-google
  (camera-app removed)
  indicator-transfer
  indicator-transfer-buteo
  libertine
  (ubuntu-experience-tests removed)
  unity-scopes-shell bug 1707797
  (unity8 removed)

  Other Notes
  ---
  The Shotwell suggests have been dropped in artful-proposed. Shotwell is 
temporarily stuck in -proposed because of an autopkgtest issue 
https://bugzilla.gnome.org/781802

  Kubuntu still uses signon-ui.

  See also https://code.launchpad.net/~xnox/ubuntu-
  seeds/unity8-removals/+merge/323615

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

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Veron Rado
You're welcome.

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

Title:
  Gnome Night Light stays warmer after overnight suspend

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686895/+subscriptions

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Sebastien Bacher
Thanks

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

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Gnome Night Light stays warmer after overnight suspend

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686895/+subscriptions

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


[Desktop-packages] [Bug 1712085] Re: gnome-control-center crashed with SIGSEGV

2017-08-21 Thread Jean-Baptiste Lallement
** Information type changed from Private to Public

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

Title:
  gnome-control-center crashed with SIGSEGV

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

Bug description:
  It just happened. Didn't have settings open at the time. However I
  don't know of that is related the past few updates bluetooth is not
  working as expected. Pairing a new device is behaving abnormally.
  Without putting device into pair mode somehow it gets added to the
  system and it shoes it connected and right after that disconnected.
  Then sometimes the settings app hangs when i turn it on/off.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 19 20:18:52 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-07-19 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170717)
  ProcCmdline: gnome-control-center online-accounts
  SegvAnalysis:
   Segfault happened at: 0x7f70ba7beb6b:mov0x8(%rax),%rax
   PC (0x7f70ba7beb6b) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   () at /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1
   () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
  Title: gnome-control-center crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1686895] Re: Gnome Night Light stays warmer after overnight suspend

2017-08-21 Thread Bug Watch Updater
** Changed in: gnome-settings-daemon
   Status: Unknown => Confirmed

** Changed in: gnome-settings-daemon
   Importance: Unknown => Medium

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

Title:
  Gnome Night Light stays warmer after overnight suspend

Status in GNOME Settings Daemon:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  Gnome Night Light is scheduled from sunset to sunrise. In the evening,
  the screen color turns warmer as expected. Going to bed, the computer
  is put in suspend mode. The next day, after sunrise, the warm color is
  still on and stays on. Turning Gnome Night Light off (and on) does not
  help.

  The Night Light settings clearly show the correct time of day in the
  slider in the blue color section.

  * Ubuntu 17.04
  * gnome-control-center:
    Installed: 1:3.24.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1686895/+subscriptions

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


[Desktop-packages] [Bug 13424] Re: Firefox crashes frequently, randomly

2017-08-21 Thread rgurumoorthy
computer crashes particularly when i see you tube &othertimes too

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

Title:
  Firefox crashes frequently, randomly

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I am running an updated hoary, and Firefox, and thunderbird are crashing 
allot,
  completely randomly.  Usually when clicking a link, hitting the back button,
  whatever loads a new page to be rendered.  The program just disapears of the
  screen, crashes hard. I opened it in the terminal to see if It said anything, 
it
  didnt.  Its runs fine for a few minuets after being started again, but crashes
  again eventually. Its not always the same links that cause the problem too. I
  have been getting more crashes for instance on Gmail pages but maybe thats
  because I use it so much.

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

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


[Desktop-packages] [Bug 1712100] [NEW] some disk volumes showing up that should probably be filtered

2017-08-21 Thread Jamie Strandboge
Public bug reported:

Starting the new ubuntu-session for gnome-shell, disk volumes are
showing up on the desktop. This is fine, but I have a couple of bind
mounts that I use for mounting in lxd that shouldn't be showing up.

$ mount|grep mapper
/dev/mapper/ubuntu--vg-root on /home/jamie/ubuntu/sbuild type ext4 
(rw,relatime,errors=remount-ro,data=ordered)
/dev/mapper/ubuntu--vg-root on /home/jamie/bzr-pulls/snappy-apps type ext4 
(rw,relatime,errors=remount-ro,data=ordered)

In Unity, these would show up in the launcher, but I could right click
on the launcher to hide them. Right click on the desktop icon in gnome-
shell does not allow this.

As a workaround, there is:

$ gsettings set org.gnome.nautilus.desktop volumes-visible false

which indeed works around the problem, but it also means that if I plug
in my phone, I don't see it show up on my desktop (and because nautilus
doesn't pop up automatically, I have to remember to open the file
manager manually and drill down to the phone).

For me, it would be great to have volumes visible with an exception list
exposed via gsettings (or ideally, right click on the volume).

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

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

Title:
  some disk volumes showing up that should probably be filtered

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting the new ubuntu-session for gnome-shell, disk volumes are
  showing up on the desktop. This is fine, but I have a couple of bind
  mounts that I use for mounting in lxd that shouldn't be showing up.

  $ mount|grep mapper
  /dev/mapper/ubuntu--vg-root on /home/jamie/ubuntu/sbuild type ext4 
(rw,relatime,errors=remount-ro,data=ordered)
  /dev/mapper/ubuntu--vg-root on /home/jamie/bzr-pulls/snappy-apps type ext4 
(rw,relatime,errors=remount-ro,data=ordered)

  In Unity, these would show up in the launcher, but I could right click
  on the launcher to hide them. Right click on the desktop icon in
  gnome-shell does not allow this.

  As a workaround, there is:

  $ gsettings set org.gnome.nautilus.desktop volumes-visible false

  which indeed works around the problem, but it also means that if I
  plug in my phone, I don't see it show up on my desktop (and because
  nautilus doesn't pop up automatically, I have to remember to open the
  file manager manually and drill down to the phone).

  For me, it would be great to have volumes visible with an exception
  list exposed via gsettings (or ideally, right click on the volume).

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

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


[Desktop-packages] [Bug 1712100] Re: some disk volumes showing up that should probably be filtered

2017-08-21 Thread Didier Roche
** Package changed: gnome-control-center (Ubuntu) => nautilus (Ubuntu)

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

Title:
  some disk volumes showing up that should probably be filtered

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting the new ubuntu-session for gnome-shell, disk volumes are
  showing up on the desktop. This is fine, but I have a couple of bind
  mounts that I use for mounting in lxd that shouldn't be showing up.

  $ mount|grep mapper
  /dev/mapper/ubuntu--vg-root on /home/jamie/ubuntu/sbuild type ext4 
(rw,relatime,errors=remount-ro,data=ordered)
  /dev/mapper/ubuntu--vg-root on /home/jamie/bzr-pulls/snappy-apps type ext4 
(rw,relatime,errors=remount-ro,data=ordered)

  In Unity, these would show up in the launcher, but I could right click
  on the launcher to hide them. Right click on the desktop icon in
  gnome-shell does not allow this.

  As a workaround, there is:

  $ gsettings set org.gnome.nautilus.desktop volumes-visible false

  which indeed works around the problem, but it also means that if I
  plug in my phone, I don't see it show up on my desktop (and because
  nautilus doesn't pop up automatically, I have to remember to open the
  file manager manually and drill down to the phone).

  For me, it would be great to have volumes visible with an exception
  list exposed via gsettings (or ideally, right click on the volume).

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

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


[Desktop-packages] [Bug 1711953] Re: deja-dup-monitor crashed with signal 5 in g_settings_get_value()

2017-08-21 Thread Michael Terry
This looks like an upgrade issue around the new gsetting key not being
registered in the schema but the new code being run...

I can't reproduce this when running deja-dup-monitor on my system.

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

Title:
  deja-dup-monitor crashed with signal 5 in g_settings_get_value()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  This error was reported soon after start-up, when executing the
  command apt-get upgrade.  The system version is

  "Linux richard-desktop 4.11.0-13-generic #19-Ubuntu SMP Thu Aug 3
  15:14:11 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  The error occurred on date "Sun 20 Aug 21:30:32 BST 2017"

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 35.4-0ubuntu3
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Aug 20 21:18:29 2017
  ExecutablePath: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2017-03-30 (143 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/deja-dup/deja-dup-monitor
  Signal: 5
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   deja_dup_migrate_settings () from 
/usr/lib/x86_64-linux-gnu/deja-dup/libdeja.so
  Title: deja-dup-monitor crashed with signal 5 in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1711791] Re: Remove the word 'Ubuntu' from 'Ubuntu Dock settings'

2017-08-21 Thread Matthew Paul Thomas
That is a very strange layout: lots of boxes, inconsistent padding, a
mysterious button, something that looks like it’s supposed to be a
switch but appears to be static text, and something that looks like it’s
supposed to be a checkbox but appears to be a switch.

Anyway. I agree with dropping the word “Ubuntu”, but I can guess why
Didier used it: to distinguish our version from Dash to Dock.

So, is the launcher called “Dock” anywhere outside of the settings UI?
If not, I would suggest retaining the name “Launcher”: it’s more
specific, it’s consistent with previous versions of Ubuntu, it avoids
using the same name as macOS, and it distinguishes our launcher from
Dash to Dock in the same way that the word “Ubuntu” did.

Either way, I suggest dropping the word “Launcher” from the three labels
below the heading. The heading makes it obvious what the labels are for.

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

Title:
  Remove the word 'Ubuntu' from 'Ubuntu Dock settings'

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

Bug description:
  I suggest removing the word 'Ubuntu' from 'Ubuntu Dock settings'. Just
  say 'Dock Settings'. It is meaningful enough. See the screenshot from
  Didier Roche.

  1:3.24.3-0ubuntu4 in Artful.

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

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


[Desktop-packages] [Bug 1712100] Re: some disk volumes showing up that should probably be filtered

2017-08-21 Thread Jamie Strandboge
Another idea might be to have:

$ gsettings set org.gnome.nautilus.desktop only-removable-volumes-
visible true

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

Title:
  some disk volumes showing up that should probably be filtered

Status in nautilus package in Ubuntu:
  New

Bug description:
  Starting the new ubuntu-session for gnome-shell, disk volumes are
  showing up on the desktop. This is fine, but I have a couple of bind
  mounts that I use for mounting in lxd that shouldn't be showing up.

  $ mount|grep mapper
  /dev/mapper/ubuntu--vg-root on /home/jamie/ubuntu/sbuild type ext4 
(rw,relatime,errors=remount-ro,data=ordered)
  /dev/mapper/ubuntu--vg-root on /home/jamie/bzr-pulls/snappy-apps type ext4 
(rw,relatime,errors=remount-ro,data=ordered)

  In Unity, these would show up in the launcher, but I could right click
  on the launcher to hide them. Right click on the desktop icon in
  gnome-shell does not allow this.

  As a workaround, there is:

  $ gsettings set org.gnome.nautilus.desktop volumes-visible false

  which indeed works around the problem, but it also means that if I
  plug in my phone, I don't see it show up on my desktop (and because
  nautilus doesn't pop up automatically, I have to remember to open the
  file manager manually and drill down to the phone).

  For me, it would be great to have volumes visible with an exception
  list exposed via gsettings (or ideally, right click on the volume).

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

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


[Desktop-packages] [Bug 1712104] [NEW] Add Hot Corner switch to Dock Settings

2017-08-21 Thread Jeremy Bicha
Public bug reported:

didrocks pointed out that the Hot Corner is roughly a 50% love/hate
thing.

If that's true (or close to it), I'd like to see a switch to turn the
Hot Corner on or off, along with the other Dock settings in Ubuntu
17.10.

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


** Tags: artful gnome-17.10

** Description changed:

  didrocks pointed out that the Hot Corner is roughly a 50% love/hate
  thing.
  
- If that's true (or close to it), I'd like to see a switch for that with
- the other Dock settings in Ubuntu 17.10.
+ If that's true (or close to it), I'd like to see a switch to turn the
+ Hot Corner on or off, along with the other Dock settings in Ubuntu
+ 17.10.

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

Title:
  Add Hot Corner switch to Dock Settings

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

Bug description:
  didrocks pointed out that the Hot Corner is roughly a 50% love/hate
  thing.

  If that's true (or close to it), I'd like to see a switch to turn the
  Hot Corner on or off, along with the other Dock settings in Ubuntu
  17.10.

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

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


[Desktop-packages] [Bug 1712108] [NEW] package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

2017-08-21 Thread Rubens Oliveira de Arruda
Public bug reported:

I got this error as alert in the first moment after booting.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-gi 3.20.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Wed Aug 16 10:19:43 2017
ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
InstallationDate: Installed on 2017-05-19 (94 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: pygobject
Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: O pacote 
está num mau estado de inconsistência; deve  reinstala-lo antes de tentar 
configura-lo.
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: O pacote
  está num mau estado de inconsistência; deve  reinstala-lo antes de
  tentar configura-lo.

Status in pygobject package in Ubuntu:
  New

Bug description:
  I got this error as alert in the first moment after booting.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-gi 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Aug 16 10:19:43 2017
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2017-05-19 (94 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: pygobject
  Title: package python-gi 3.20.0-0ubuntu1 failed to install/upgrade: O pacote 
está num mau estado de inconsistência; deve  reinstala-lo antes de tentar 
configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1201924] Re: deja-dup fails to backup to ubuntu one, with error [Errno 2] No such file or directory

2017-08-21 Thread Michael Terry
U1 is shut down, closing this bug.

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

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

Title:
  deja-dup fails to backup to ubuntu one, with error [Errno 2] No such
  file or directory

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  I am using Ubuntu 13.04 and deja-dup 26.0 version. I connect to internet 
through my Institute's Authentication Proxy. deja-dup(Backup) fails to backup 
to Ubuntu One after a long time, with this error message,
  "Giving up on request after 5 attempts, last exception [Errno 2] No such file 
or directory".

  Ubuntu One client in my system is able to sync files properly. I
  already installed 'ubuntuone-client-proxy' package.

  Steps to reproduce:
  1. Open deja-dup backup software.
  2. Set it to backup to ubuntuone.
  3. Select Backup Now.

  What is expected?
  It is expected that backup finishes successfully.

  What happens instead?
  It fails after some time with the error mentioned above.

  One more thing is that my Ubuntu One folder has enough space in it. I
  backed up data into other drive and it is not more the 500 MB, and in
  ubuntu one I have more than 4.5 GB free space. So, lack of enough
  space is not the reason.

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

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


[Desktop-packages] [Bug 1191230] Re: Backup doesn't work and an SSL error is displayed

2017-08-21 Thread Michael Terry
This was a bug with the U1 backend, which is no longer supported.
Closing.

** Changed in: deja-dup (Ubuntu)
   Status: New => Invalid

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

Title:
  Backup doesn't work and an SSL error is displayed

Status in deja-dup package in Ubuntu:
  Invalid

Bug description:
  A couple of days agoo I have found that my automatic backup doesn't
  work anymore, and this error is displayed:

  

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1411, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1404, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1386, in main
  incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 568, in incremental_backup
  sig_chain.get_fileobjs())
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 526, 
in get_fileobjs
  return map(filename_to_fileobj, self.get_filenames(time))
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 550, in 
get_fileobj_read
  self.get(filename, tdp)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 323, in 
iterate
  return fn(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/duplicity/backends/u1backend.py", 
line 201, in get
  answer = auth.request(remote_full)
File 
"/usr/lib/python2.7/dist-packages/ubuntuone-couch/ubuntuone/couch/auth.py", 
line 152, in request
  url, method=http_method, headers=headers, body=request_body)
File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1444, in 
request
  (response, content) = self._request(conn, authority, uri, request_uri, 
method, body, headers, redirections, cachekey)
File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1196, in 
_request
  (response, content) = self._conn_request(conn, request_uri, method, body, 
headers)
File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1179, in 
_conn_request
  content = response.read()
File "/usr/lib/python2.7/httplib.py", line 548, in read
  s = self._safe_read(self.length)
File "/usr/lib/python2.7/httplib.py", line 647, in _safe_read
  chunk = self.fp.read(min(amt, MAXAMOUNT))
File "/usr/lib/python2.7/socket.py", line 380, in read
  data = self._sock.recv(left)
File "/usr/lib/python2.7/ssl.py", line 241, in recv
  return self.read(buflen)
File "/usr/lib/python2.7/ssl.py", line 160, in read
  return self._sslobj.read(len)
  SSLError: The read operation timed out
  


  As you can see, the last error message line refers to an SSL Error.

  Even the restore operation seems to not work anymore. I have tried to
  restore a file, but the operation never ends. In the Déja-dup window
  the status is always "Preparing...".

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Sat Jun 15 09:23:07 2013
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it_CH:it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_CH.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 986898] Re: Icons "Privacy" and "Backup" are swapped in System Settings

2017-08-21 Thread Michael Terry
Backups has been using the safe icon for years at this point.  I'm
closing this for deja-dup.

** Changed in: deja-dup (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Icons "Privacy" and "Backup" are swapped in System Settings

Status in activity-log-manager package in Ubuntu:
  Confirmed
Status in deja-dup package in Ubuntu:
  Won't Fix

Bug description:
  Noticed the icons "Privacy" and "Backup" in System Settings are
  swapped. Dont know if this is really a bug but it makes more sense the
  backup icon being the one with the "back in time clock" and the
  privacy icon being the "safe" icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 22 16:29:45 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120421)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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


[Desktop-packages] [Bug 1019824] Re: Can't enter WebDAV Storage info

2017-08-21 Thread Michael Terry
This should be fixed these days?

** Changed in: deja-dup (Ubuntu)
   Status: New => Fix Released

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

Title:
  Can't enter WebDAV Storage info

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  After running deja-dup-preferences and changing the backup location to
  WebDAV, I can't enter anything into the Server, Port, Folder, or
  Username fields.  Clicking in the text entry boxes shows a cursor, but
  keyboard entry doesn't do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
  Uname: Linux 3.2.0-26-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  Date: Sun Jul  1 09:32:22 2012
  ExecutablePath: /usr/bin/deja-dup-preferences
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LANGUAGE=
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-05-19 (42 days ago)

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

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


[Desktop-packages] [Bug 1697155] Re: No progress dialog under Gnome Shell

2017-08-21 Thread Michael Terry
In artful, clicking on the "backup started" notification will bring up
the progress window.

** Changed in: deja-dup (Ubuntu)
   Status: New => Fix Released

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

Title:
  No progress dialog under Gnome Shell

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  When connecting the backup drive in Gnome Shell (Ubuntu Gnome), backup
  starts but does not open the progress dialog. It is hard to keep track
  of when the backup process is finished and when it's save to remove
  the drive.

  Workaround: I have to open gnome-system-monitor and look for a process
  "deja-dup" (not to confuse with deja-dup-monitor which remains running
  after completion of the backup).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: deja-dup 34.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Jun 10 11:39:49 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-05 (217 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 442130] Re: Custom fstab causes duplicate entries for partitions in Places

2017-08-21 Thread Bug Watch Updater
** Changed in: gvfs
   Status: New => Confirmed

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

Title:
  Custom fstab causes duplicate entries for partitions in Places

Status in gvfs:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: nautilus

  I wanted my disks to automount on startup, but I didnt want to address them 
directly with device path, since it can change.
  So instead i use the LABEL directive.
  Now each partition is listed twice in Nautilus Places (see screenshot).

  According to a post on ubuntuforums, this issue can also happen if you 
identify partitions by UUID:
  * http://ubuntuforums.org/showthread.php?p=8050320

  A workaround is to specify the partitions by /dev/sdXXX paths instead

  
  # /etc/fstab: static file system information.
  proc /proc proc defaults 0 0

  LABEL=ubuntu / ext3 relatime,errors=remount-ro 0 1
  UUID=4c604809-286a-4bf3-afd5-d23ff2e5464c none swap sw 0 0

  /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

  LABEL=mp3   /media/mp3 ext4   users,noauto,noexec,noatime,rw  0 2
  LABEL=tvserier  /media/tvserierext4   users,noauto,noexec,noatime,rw  0 3
  LABEL=filmer/media/filmer  ext4   users,noauto,noexec,noatime,rw  0 4
  LABEL=downloads /media/downloads   ext4   users,noauto,noexec,noatime,rw  0 5

  ProblemType: Bug
  Architecture: amd64
  Date: Sun Oct  4 13:07:08 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/nautilus
  NonfreeKernelModules: fglrx
  Package: nautilus 1:2.28.0-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
  SourcePackage: nautilus
  Uname: Linux 2.6.31-11-generic x86_64

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

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


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

2017-08-21 Thread Till Kamppeter
Can you please supply the following files:

PPD file for your printer (in /etc/cups/ppd/) on 17.04.

PPD file for your printer (in /etc/cups/ppd/) on 17.10.

Output of the following commands in a terminal window:

driverless
lpstat -v
ipptool -tv  get-printer-attributes.test

The  you can find in the output of the "driverless" or "lpstat
-v" commands. It is some expression starting with "ipp://..." or
"ipps://..." (on one of my printers it is
"ipp://HP5CB901E7DDC7.local:631/ipp/print").

Please attach the files one by one, do not compress them and do not
package them together. Thanks.

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

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

Title:
  Driverless printing only prints a blank sheet 17.10

Status in cups package in Ubuntu:
  Incomplete

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

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

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


[Desktop-packages] [Bug 1707420] Re: Cannot install package when sudo apt-get upgrade: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches] failed to install/upgrade: trying

2017-08-21 Thread Sebastien Bacher
** Changed in: gtk+2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Cannot install package when sudo apt-get upgrade: package
  libgtk2.0-bin 2.24.30-1ubuntu1 [modified: usr/sbin/update-icon-caches]
  failed to install/upgrade: trying to overwrite '/usr/sbin/update-icon-
  caches', which is also in package libgtk-3-bin 3.18.9-1ubuntu3.1

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Cannot install package when sudo apt-get upgrade

  Preparing to unpack .../libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb ...
  Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/sbin/update-icon-caches', which is also in package 
libgtk-3-bin 3.18.9-1ubuntu3.1

  Errors were encountered while processing:
   /var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb
   /var/cache/apt/archives/libgtk-3-bin_3.18.9-1ubuntu3.3_amd64.deb

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-bin 2.24.30-1ubuntu1 [modified: 
usr/sbin/update-icon-caches]
  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: Sat Jul 29 18:41:59 2017
  DuplicateSignature:
   package:libgtk2.0-bin:2.24.30-1ubuntu1 [modified: 
usr/sbin/update-icon-caches]
   Unpacking libgtk2.0-bin (2.24.30-1ubuntu1.16.04.1) over (2.24.30-1ubuntu1) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/libgtk2.0-bin_2.24.30-1ubuntu1.16.04.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/sbin/update-icon-caches', which is also in 
package libgtk-3-bin 3.18.9-1ubuntu3.1
  ErrorMessage: trying to overwrite '/usr/sbin/update-icon-caches', which is 
also in package libgtk-3-bin 3.18.9-1ubuntu3.1
  InstallationDate: Installed on 2015-08-20 (708 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-bin 2.24.30-1ubuntu1 [modified: 
usr/sbin/update-icon-caches] failed to install/upgrade: trying to overwrite 
'/usr/sbin/update-icon-caches', which is also in package libgtk-3-bin 
3.18.9-1ubuntu3.1
  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/1707420/+subscriptions

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


[Desktop-packages] [Bug 1695112] Re: GNOME creates thumbnails that leak encrypted data under default Ubuntu configuration

2017-08-21 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
tell us the number of the upstream bug (or the link), so we can add a
bugwatch that will inform us about its status. Thanks in advance.

** Changed in: gnome-desktop3 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  GNOME creates thumbnails that leak encrypted data under default Ubuntu
  configuration

Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  Tested on Ubuntu 16.04.2 LTS. Bug appears to be in libgnome-
  desktop-3-12 (3.18.2-1ubuntu1). Nautilus (1:3.18.4.is.3.14.3-0ubuntu5)
  used to confirm.

  When a user does not have an encrypted home directory, the default
  Ubuntu installation offers an encrypted Private directory for each
  user using ecryptfs. The goal, I presume, is to give the user a place
  where they can protect data from being read directly off the disk.

  This entire purpose is defeated, though, because GNOME caches
  thumbnails of files in Private. These can be detailed enough to reveal
  contents of the encrypted storage.

  To reproduce:
  1. Save an image or other thumbnail-able file directly to ~/Private. It could 
be porn, a naked selfie, ... I used the Ubuntu logo 64_logo.png from Launchpad.
  2. Open Nautilus and browse to Private. Confirm that a thumbnail is shown for 
the image.
  3. Find this file's checksum: echo -n 'file:///home/xxx/Private/64_logo.png' 
| md5sum
  4. Confirm that ~/.caches/thumbnails//.png exists and is a 
scaled-down image of the original file in Private, that has been written to 
disk outside of an encrypted location.

  If this is not a bug, I don't understand why Ubuntu would provide an
  encrypted Private directory in the first place.

  Ideally, this would be fixed by improving
  gnome_desktop_thumbnail_factory_can_thumbnail so it checks the GNOME
  Activity Journal configuration for excluded directories, and include
  ~/Private in that configuration by default. If eliminating thumbnails
  entirely impacts usability, it should be possible to make more
  extensive changes that either cache thumbnails in a location on the
  same filesystem (much like the hidden Trash directories and Windows'
  thumbnail handling) or create thumbnails without caching them to disk.

  I noticed another security problem while investigating this. libgnome-
  desktop may also be leaking thumbnail data even if a user's entire
  home folder is encrypted, through the use of a temporary file here:
  https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/gnome-
  desktop3/vivid/view/head:/libgnome-desktop/gnome-desktop-
  thumbnail.c#L1369 If /tmp is not encrypted or mounted as tmpfs, there
  is a risk of encrypted data being discovered through forensic
  investigative methods on the disk. This is probably not the only way
  encrypted home directory data can leak out to /tmp though.

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

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


[Desktop-packages] [Bug 1622363] Re: Restore a file doesn't works if the filename include one ' (apostrophe)

2017-08-21 Thread Michael Terry
Seems fixed in artful.

** Changed in: deja-dup (Ubuntu)
   Status: New => Fix Released

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

Title:
  Restore a file doesn't works if the filename include one '
  (apostrophe)

Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  Trying to restore a specific version of a file, using the context menu (right 
click) in File/Nautilus, I found out that the window of DéjàDup doesn't shows 
up. The problem is that this file has an ' (apostrophe) included in his name. 
Just to try, I have added a second apostrophe to the name, and this time the 
window of DéjàDup it was open as expected.
  I think that there is somewhere a problem of character string, opened and 
closed when a filename includes an apostrophe, that ends up with an error that 
prevents to the DéjàDup window to open up correctly.
  Of course there is no problem at all, when the file names does not include an 
apostrophe.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 11 19:17:55 2016
  InstallationDate: Installed on 2014-04-23 (871 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (42 days ago)

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

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


  1   2   3   >