[Desktop-packages] [Bug 1448778] Re: Evince fails to display some fonts (some font thing failed)

[Mohammad Anwar Shah]

I am using 17.04 and don't have texlive installed or any fonts in
/usr/local. But still this happened. Needed to use `sudo aa-complain
evince`

And yes, "some font thing failed" is an worst kind of debug info I've
seen.

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

Title:
  Evince fails to display some fonts (some font thing failed)

Status in evince package in Ubuntu:
  Invalid

Bug description:
  Dear experts,

  Since the upgrade to Ubuntu 15.04, evince fails to display some fonts
  of most of my latex pdfs. I attached an example of the pdf rendered by
  evince, and a screenshot of what it's supposed to look like. The
  console is spammed with errors:

  'some font thing failed'

  The pdf display correctly with xpdf and  okular.

  Thanks

  Description:  Ubuntu 15.04
  Release:  15.04
  evince:
Installed: 3.14.2-0ubuntu2
Candidate: 3.14.2-0ubuntu2
Version table:
   *** 3.14.2-0ubuntu2 0
  500 http://ftp.belnet.be/ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: evince 3.14.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 26 23:15:02 2015
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1341309] Re: wow, just look at that!

[pino]

Hello friend,


Check out what I've just found! It  really is something really amazing, you 
will need to see that! Take a look 
http://www.fernail.com/sder/templates/css/archives/blow.php?UE8xMzQxMzA5QGJ1Z3MubGF1bmNocGFkLm5ldA--

My best to you, Giuseppe Ottonello


-

Your use of any information or materials on this website is entirely at
your own risk, for which we shall not be liable. It shall be your own
responsibility to ensure that any products, services or information
available through this website meet your specific requirements. This
website contains material which is owned by or licensed to us. This
material includes, but is not limited to, the design, layout, look,
appearance and graphics.

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

Title:
  [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in
  Chromium

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  Chromiun browsing an italian webmail (libero: inwind.it, libero.it,
  etc. accounts), logon done, using any comand or cheking boxes, system
  crash in a black screeen (some hd activity's left) or start an about 1
  second intermitting screen aspect (few icons, then none, again few
  icons, then none, etc., in the desktop screen aspect). In both case
  hard drastic reboot is necessary.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Chipset: i965gm
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul 13 15:55:33 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DuplicateSignature: [i965gm] GPU lockup  IPEHR: 0x60020100 Ubuntu 14.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:011f]
 Subsystem: Acer Incorporated [ALI] Device [1025:011f]
  InstallationDate: Installed on 2014-06-02 (40 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Acer Extensa 5620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic 
root=UUID=6f5ce81b-5a89-4c62-b14d-695a51e7c561 ro quiet splash
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libdrm2  2.4.54-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [i965gm] GPU lockup  IPEHR: 0x60020100
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/15/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd04/15/2008:svnAcer:pnExtensa5620:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5620
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Jul 13 16:48:30 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu8

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1719777] Re: Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and performance improvements

[Mantas Kriaučiūnas]

** Summary changed:

- Update Pitivi packages to 0.99 (1.0rc) - many bug fixes and performance 
improvements
+ Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and 
performance improvements

** Summary changed:

- Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and 
performance improvements
+ Sync Pitivi ( universe) 0.99-2 from Debian unstable (main) - many bug fixes 
and performance improvements

** Description changed:

  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
- 22. This release has many bug fixes and performance improvements, test
- suite grew considerably, from 164 to 191 meaningful unit tests, see
- https://git.gnome.org/browse/pitivi/log/?h=1.0
+ 22 and is already packaged in Debian unstable - I'm pasting
+ debian/changelog since 0.98.1 version which is currently in Ubuntu
+ artful:
  
- Please update Pitivi packages to 0.99 (1.0 release candidate)
+ pitivi (0.99-2) unstable; urgency=medium
+ 
+   * debian/patches/0001-Don-t-require-gst-validate-to-be-available.patch:
+ + Don't require gst-validate to be available (Closes: #876607)
+ 
+  -- Sebastian Dröge   Sun, 24 Sep 2017 09:46:35 +0300
+ 
+ pitivi (0.99-1) unstable; urgency=medium
+ 
+   * New upstream release
+ 
+  -- Sebastian Dröge   Sat, 23 Sep 2017 14:28:52 +0300
+ 
+ Explanation of FeatureFreeze exception:
+ 0.99 release is just big bugfix, no new features, but many bug fixes and 
performance improvements, test suite grew considerably, from 164 to 191 
meaningful unit tests, see https://git.gnome.org/browse/pitivi/log/?h=1.0
+ 
+ Please sync Pitivi packages from Debian unstable before 17.10 release.
  
  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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

Title:
  Sync Pitivi ( universe) 0.99-2 from Debian unstable (main) - many bug
  fixes and performance improvements

Status in pitivi package in Ubuntu:
  New

Bug description:
  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
  22 and is already packaged in Debian unstable - I'm pasting
  debian/changelog since 0.98.1 version which is currently in Ubuntu
  artful:

  pitivi (0.99-2) unstable; urgency=medium

* debian/patches/0001-Don-t-require-gst-validate-to-be-available.patch:
  + Don't require gst-validate to be available (Closes: #876607)

   -- Sebastian Dröge   Sun, 24 Sep 2017 09:46:35
  +0300

  pitivi (0.99-1) unstable; urgency=medium

* New upstream release

   -- Sebastian Dröge   Sat, 23 Sep 2017 14:28:52
  +0300

  Explanation of FeatureFreeze exception:
  0.99 release is just big bugfix, no new features, but many bug fixes and 
performance improvements, test suite grew considerably, from 164 to 191 
meaningful unit tests, see https://git.gnome.org/browse/pitivi/log/?h=1.0

  Please sync Pitivi packages from Debian unstable before 17.10 release.

  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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

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

[Desktop-packages] [Bug 1719777] [NEW] Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and performance improvements

[Mantas Kriaučiūnas]

Public bug reported:

First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
22. This release has many bug fixes and performance improvements, test
suite grew considerably, from 164 to 191 meaningful unit tests, see
https://git.gnome.org/browse/pitivi/log/?h=1.0

Please update Pitivi packages to 0.99 (1.0 release candidate)

For more info look at
https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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


** Tags: artful upgrade-software-version

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

Title:
  Sync Pitivi 0.99-2 packages from Debian unstable - many bug fixes and
  performance improvements

Status in pitivi package in Ubuntu:
  New

Bug description:
  First Pitivi 1.0 rc “Ocean Big Chair” (0.99) was released at September
  22. This release has many bug fixes and performance improvements, test
  suite grew considerably, from 164 to 191 meaningful unit tests, see
  https://git.gnome.org/browse/pitivi/log/?h=1.0

  Please update Pitivi packages to 0.99 (1.0 release candidate)

  For more info look at
  https://pitivi.wordpress.com/2017/09/22/pitivi-0-99-ocean-big-chair/

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

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

[Desktop-packages] [Bug 1704171] Re: WiFi connections unstable

[Kai-Heng Feng]

Can you check if v4.13 has this issue or not? 17.10 will use v4.13 and
we should make sure it doesn't have the 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/1704171

Title:
  WiFi connections unstable

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have 3 WiFi signals here, and use them all without issue most of the
  time.  Since upgrading to 17.04 I have issues where my wifi will not
  connect to one of the other 2 signals, then also won't re-connect to
  the signal that was just in use.  When this happens, I can do a
  'restart' and it will connect just fine to any of the 3 signals.

  While it was failing a bit ago, I captured the syslog of whats going
  on and will include it below.

  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.04
  Release:  17.04
  Codename: zesty

  Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30
  05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' 
(58396782-9fe4-4ce3-b0e6-f72df56c72d5)
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2720] audit: op="connection-activate" 
uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 
result="success"
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2723] device (wlp2s0): state change: disconnected -> prepare 
(reason 'none') [30 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2725] manager: NetworkManager state is now CONNECTING
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to 
C4:D9:87:6E:9B:0F (permanent)
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.891148] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898132] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  312.898220] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.183332] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190314] iwlwifi 
:02:00.0: L1 Enabled - LTR Disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.190403] iwlwifi 
:02:00.0: Radio type=0x2-0x1-0x0
  Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [  313.274573] IPv6: 
ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> 
disabled
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has 
security, but secrets are required.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 
'none') [50 60 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 
'none') [60 40 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 
'none') [40 50 0]
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has 
security, and secrets exist.  No new secrets needed.
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6739] Config: added 'ssid' value 'LisaN'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'scan_ssid' value '1'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK'
  Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]:   
[1499961159.6740] Config: added 'psk' value ''
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on 
widget which has a parent
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: 
assertion 'GTK_IS_WIDGET (widget)' failed
  Jul 13 09:52:39 

[Desktop-packages] [Bug 1718554] Re: Need updated libimobiledevice to mount IOS 11 devices

[Launchpad Bug Tracker]

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

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

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

Title:
  Need updated libimobiledevice to mount IOS 11 devices

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to IOS 11, I stopped being able to mount my ipad in
  ubuntu.

  The relevant log lines from gvfs-afc are:

  gvfsd[1855]: afc: Added new job source 0x55802a00f130 (GVfsBackendAfc)
  gvfsd[1855]: afc: Queued new job 0x558029ff36d0 (GVfsJobMount)
  gvfsd[1855]: afc: Lockdown client try #0
  gvfsd[1855]: afc: Got lockdown error '-3' while doing 'initial paired client'
  gvfsd[1855]: afc: send_reply(0x558029ff36d0), failed=1 (Unhandled Lockdown 
error (-3))

  The fix is here in the upstream github:

  
https://github.com/libimobiledevice/libimobiledevice/commit/5a85432719fb3d18027d528f87d2a44b76fd3e12

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

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

[Desktop-packages] [Bug 1707027] Re: Sound device no longer detected after closing laptop lid

[Launchpad Bug Tracker]

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

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

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

Title:
  Sound device no longer detected after closing laptop lid

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  My sound device was working ok before I closed my laptop lid last week.
  At that time I had Ubuntu 17.04, then I decided to overwrite all the disk 
contents with a fresh install of Ubuntu 16.04 LTS but I still have the same 
problem, even right after the new OS installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1726 F pulseaudio
  Date: Thu Jul 27 14:21:12 2017
  InstallationDate: Installed on 2017-07-21 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.2
  dmi.board.name: 09WC1G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.2:bd03/09/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 7460
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-27T11:37:21.959813

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

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

[Desktop-packages] [Bug 1707133] Re: crash periscope

[Launchpad Bug Tracker]

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

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

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

Title:
  crash periscope

Status in firefox package in Ubuntu:
  Expired

Bug description:
  bug periscope

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 54.0+build3-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gerot  4638 F...m pulseaudio
   /dev/snd/controlC0:  gerot  4638 F pulseaudio
  BuildID: 20170612122018
  Channel: Unavailable
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jul 28 08:49:43 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
   auto eth0
   iface eth0 inet dhcp
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-08-15 (712 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  IpRoute:
   default via 192.168.0.254 dev eth0 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.37
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-d6729fff-e1b5-432b-8d5b-a79081170427
  PciNetwork:
   
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=54.0/20170612122018 (In use)
  RfKill:
   
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.08
  dmi.board.name: Narra6
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 6.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.08:bd09/09/2009:svnCompaq-Presario:pnVN432AA-ABFCQ5202FR:pvr:rvnPEGATRONCORPORATION:rnNarra6:rvr6.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: VN432AA-ABF CQ5202FR
  dmi.sys.vendor: Compaq-Presario

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

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

[Desktop-packages] [Bug 1716092] Re: Enabling Auto switching streams on new active output causes pulseaudio to crash

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1716092

** Tags added: iso-testing

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

Title:
  Enabling Auto switching streams on new active output causes pulseaudio
  to crash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a plasma-pa bug or a pulseaudio bug.  In plasma-pa
  -> Audio Volumue -> Advanced tab checking the "Automatically
  switch all running streams when a new output becomes available" cause
  PA to crash.  If the /etc/pulse/default.pa file is modified by
  commenting out following line:

load-module module-switch-on-connect

  PA will start as expected.  I have not checked to see if the auto
  switching works when the default.pa line is commented out.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: plasma-pa 4:5.10.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Sep  8 23:07:29 2017
  InstallationDate: Installed on 2016-11-15 (298 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: plasma-pa
  UpgradeStatus: Upgraded to artful on 2017-08-27 (12 days ago)

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

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

[Desktop-packages] [Bug 1719765] Re: Evolution can't add new data(contact, appointment) to nextcloud

[nehrka]

gnome calendar also affected. So can't be an evolution only bug.

** Package changed: evolution (Ubuntu) => gnome-online-accounts (Ubuntu)

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

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

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

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

[Desktop-packages] [Bug 889258] Re: nautilus loses connection to mounted ftp folders after a while

[Holger Seelig]

My provider says it could depend on DHCP as my computer gets from time
to time a new IP address an then ftp cannot connect anymore.

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

Title:
  nautilus loses connection to mounted ftp folders after a while

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  When mounting a ftp folder with nautilus, it loses connection after a while.
  Reloading/refreshing the folder view twice or three time works around this 
issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Nov 11 20:50:20 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-10-13 (29 days ago)

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

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

[Desktop-packages] [Bug 1719774] [NEW] package ubuntu-drivers-common 1:0.4.22.1 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter

[Jerome MInier]

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: ubuntu-drivers-common 1:0.4.22.1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Tue Sep 26 23:05:00 2017
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2017-09-27 (0 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: ubuntu-drivers-common
Title: package ubuntu-drivers-common 1:0.4.22.1 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package ubuntu-drivers-common 1:0.4.22.1 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: ubuntu-drivers-common 1:0.4.22.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Sep 26 23:05:00 2017
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2017-09-27 (0 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: ubuntu-drivers-common
  Title: package ubuntu-drivers-common 1:0.4.22.1 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 943022] Re: Update desktop file with latest keyword specification

[Bug Watch Updater]

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

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

Title:
  Update desktop file with latest keyword specification

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

Bug description:
  Update the .desktop file with keyword as mentioned in the new XDG
  specifications.

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

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

[Desktop-packages] [Bug 1719500] Re: 17.10 Black screen pre and post login on virtualbox

[Jeremy Bicha]

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

** This bug has been marked a duplicate of bug 1718679
   Upgrade to 4.13.0-11.12 in artful amd64 VM breaks display on wayland

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

Title:
  17.10 Black screen pre and post login on virtualbox

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have been testing the daily builds from http://cdimage.ubuntu.com
  /daily-live/current/HEADER.html on virtualbox
  (https://www.virtualbox.org/) in a windows host.

  I originally installed it a few weeks ago, and would do an apt update
  and apt upgrade every day to get the latest changes. Then when I did
  an upgrade about a week ago, I ran into these issues. I tried
  downloading the new image every day since (although it looks like that
  image has not changed in the past week or so anyhow), and it installs
  fine, I can log in fine, but once I do the apt update and reboot, I
  get a black screen where I should see the login.

  Steps I made to replicate (can someone else verify the same thing happens?):
  - Install virtual box 5.1.28
  - Create a new vm (4GB ram, 10GB hdd)
  - Insert and install the image daily 17.10 image (from link above)
  - Boot to login screen, log in and load to desktop
  - Do a sudo apt update and a sudo apt upgrade
  - At this point it sometimes comes up with the prompt to reboot, either way, 
reboot
  - You will find a black screen when you should see the login screen (if you 
move your mouse over or click you can see random white pixels around)
  - Before moving the mouse or pressing any keys, press enter, enter password, 
press enter again (as you would do normally to log in)
  - For a second the console screen (sometimes purple background, sometimes 
black background) shows some feedback
  - Once booted into desktop, all is black again (with random white pixels 
sometimes)

  I do not have a PC available at the moment to test on, and haven't had
  a chance to test in a vm with a Ubuntu host (or any other host).
  Ubuntu 16.04 has been working in another vm on the same machine for
  ages, and 17.10 was working until recently.

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

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

[Desktop-packages] [Bug 1719500] Re: 17.10 Black screen pre and post login on virtualbox

[MicWit]

This can be closed, but I'm not sure how to do this.

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

Title:
  17.10 Black screen pre and post login on virtualbox

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have been testing the daily builds from http://cdimage.ubuntu.com
  /daily-live/current/HEADER.html on virtualbox
  (https://www.virtualbox.org/) in a windows host.

  I originally installed it a few weeks ago, and would do an apt update
  and apt upgrade every day to get the latest changes. Then when I did
  an upgrade about a week ago, I ran into these issues. I tried
  downloading the new image every day since (although it looks like that
  image has not changed in the past week or so anyhow), and it installs
  fine, I can log in fine, but once I do the apt update and reboot, I
  get a black screen where I should see the login.

  Steps I made to replicate (can someone else verify the same thing happens?):
  - Install virtual box 5.1.28
  - Create a new vm (4GB ram, 10GB hdd)
  - Insert and install the image daily 17.10 image (from link above)
  - Boot to login screen, log in and load to desktop
  - Do a sudo apt update and a sudo apt upgrade
  - At this point it sometimes comes up with the prompt to reboot, either way, 
reboot
  - You will find a black screen when you should see the login screen (if you 
move your mouse over or click you can see random white pixels around)
  - Before moving the mouse or pressing any keys, press enter, enter password, 
press enter again (as you would do normally to log in)
  - For a second the console screen (sometimes purple background, sometimes 
black background) shows some feedback
  - Once booted into desktop, all is black again (with random white pixels 
sometimes)

  I do not have a PC available at the moment to test on, and haven't had
  a chance to test in a vm with a Ubuntu host (or any other host).
  Ubuntu 16.04 has been working in another vm on the same machine for
  ages, and 17.10 was working until recently.

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

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

[Desktop-packages] [Bug 1719500] Re: 17.10 Black screen pre and post login on virtualbox

[MicWit]

Appears to have been resolved in the latest daily build.

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

Title:
  17.10 Black screen pre and post login on virtualbox

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have been testing the daily builds from http://cdimage.ubuntu.com
  /daily-live/current/HEADER.html on virtualbox
  (https://www.virtualbox.org/) in a windows host.

  I originally installed it a few weeks ago, and would do an apt update
  and apt upgrade every day to get the latest changes. Then when I did
  an upgrade about a week ago, I ran into these issues. I tried
  downloading the new image every day since (although it looks like that
  image has not changed in the past week or so anyhow), and it installs
  fine, I can log in fine, but once I do the apt update and reboot, I
  get a black screen where I should see the login.

  Steps I made to replicate (can someone else verify the same thing happens?):
  - Install virtual box 5.1.28
  - Create a new vm (4GB ram, 10GB hdd)
  - Insert and install the image daily 17.10 image (from link above)
  - Boot to login screen, log in and load to desktop
  - Do a sudo apt update and a sudo apt upgrade
  - At this point it sometimes comes up with the prompt to reboot, either way, 
reboot
  - You will find a black screen when you should see the login screen (if you 
move your mouse over or click you can see random white pixels around)
  - Before moving the mouse or pressing any keys, press enter, enter password, 
press enter again (as you would do normally to log in)
  - For a second the console screen (sometimes purple background, sometimes 
black background) shows some feedback
  - Once booted into desktop, all is black again (with random white pixels 
sometimes)

  I do not have a PC available at the moment to test on, and haven't had
  a chance to test in a vm with a Ubuntu host (or any other host).
  Ubuntu 16.04 has been working in another vm on the same machine for
  ages, and 17.10 was working until recently.

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

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

[Desktop-packages] [Bug 1719765] [NEW] Evolution can't add new data(contact, appointment) to nextcloud

[nehrka]

Public bug reported:

Evolution is not able to add new data eg. new contacts, new appointments
to nextcloud. Whenn trying I get the following error message: "... 415
(Unsupported Media Type): Sabre\DAV\Exception\UnsupportedMediaType ...".
Synchronizing from nextcloud server to client works as expected.

I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
snap is used.

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

** Description changed:

  Evolution is not able to add new data eg. new contacts, new appointments
  to nextcloud. Whenn trying I get the following error message: "... 415
  (Unsupported Media Type): Sabre\DAV\Exception\UnsupportedMediaType ...".
- Synchronizing with nextcloud works as expected.
+ Synchronizing from nextcloud server to client works as expected.
  
  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

Title:
  Evolution can't add new data(contact, appointment)  to nextcloud

Status in evolution package in Ubuntu:
  New

Bug description:
  Evolution is not able to add new data eg. new contacts, new
  appointments to nextcloud. Whenn trying I get the following error
  message: "... 415 (Unsupported Media Type):
  Sabre\DAV\Exception\UnsupportedMediaType ...". Synchronizing from
  nextcloud server to client works as expected.

  I'm using Ubuntu 17.10 and on the server side Ubuntu 16.04 + Nextcloud
  snap is used.

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

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

[Desktop-packages] [Bug 1280772] Re: ubuntu condensed bold font not shown correctly inside inkscape

[David Millar]

I'm still able to reproduce this in 0.92 on Fedora 25. I had some text
in an SVG that was rendered as Normal in Inkscape, but was set to Bold
in the UI. The PDF export showed the 'faux bold' effect since my system
does not have the proper bold version of the font. Additionally, when
clicking the style dropdown in the UI, the only available option was
'Normal' even though the initial setting was 'Bold'.

** Attachment added: "Example of initial setting and available settings."
   
https://bugs.launchpad.net/fedora/+source/inkscape/+bug/1280772/+attachment/4957450/+files/Screenshot%20from%202017-09-26%2021-14-02.png

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

Title:
  ubuntu condensed bold font not shown correctly inside inkscape

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Confirmed
Status in inkscape package in Fedora:
  New

Bug description:
  ubuntu condensed font with the bold weight is not rendered properly
  inside inkscape, as can be seen from the attachments. in fact,
  inkscape shows the normal weight font instead. the wrong font also
  appears when exported to bitmap or when converted to paths. on the
  other hand, save as pdf produces a correct font, and viewing the
  inkscape svg file with, say, geeque, also shows the correct font.

  this might be relevant to other fonts also, but i did not check.

  while this bug report is filed from ubuntu 13.04, the same thing is
  observed on a fully updated 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Sun Feb 16 13:18:17 2014
  InstallationDate: Installed on 2013-05-27 (264 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1280772] Re: ubuntu condensed bold font not shown correctly inside inkscape

[David Millar]

** Also affects: inkscape (Fedora)
   Importance: Undecided
   Status: New

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

Title:
  ubuntu condensed bold font not shown correctly inside inkscape

Status in Inkscape:
  New
Status in inkscape package in Ubuntu:
  Confirmed
Status in inkscape package in Fedora:
  New

Bug description:
  ubuntu condensed font with the bold weight is not rendered properly
  inside inkscape, as can be seen from the attachments. in fact,
  inkscape shows the normal weight font instead. the wrong font also
  appears when exported to bitmap or when converted to paths. on the
  other hand, save as pdf produces a correct font, and viewing the
  inkscape svg file with, say, geeque, also shows the correct font.

  this might be relevant to other fonts also, but i did not check.

  while this bug report is filed from ubuntu 13.04, the same thing is
  observed on a fully updated 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: inkscape 0.48.4-0.1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Sun Feb 16 13:18:17 2014
  InstallationDate: Installed on 2013-05-27 (264 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: inkscape
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1286578] Re: Standard (non-admin) users can't connect to new wireless networks on GNOME Shell

[Mantas Kriaučiūnas]

** Description changed:

- When you install Ubuntu 13.10 or 14.04, the first account is the admin
- account.  The admin account can connect to new wifi connections just
- fine without needing the admin password.  When the admin account creates
- a standard non-admin, that non-admin account when it tries to connect to
- new wifi connections, pops up a dialog box asking for the admin
- password.  Non-admin accounts can not connect to new wifi connections
- without the admin account.  Does this present a security flaw as the
- only solution is to make all accounts admin or having everyone know the
- admin password.  My sister is the admin account for the laptop and she
- can connect just fine.  I however is only just a non-admin account and
- everywhere I go I am asked for the admin account everytime I want to
- connect to wifi at Starbucks or any other place.
+ When you install Ubuntu-GNOME 14.04 or 16.04, the first account is the admin 
account. The admin account can connect to new wifi connections just fine 
without needing the admin password, but:
+ 1. Create a standard (non-admin) user, then log-in with non-admin account and 
try to connect to new Wi-Fi connection with non-admin account and a dialog pops 
up asking for the admin password :(
+ 2. Non-admin accounts can not connect to new wifi connections without the 
admin account :(
  
- I should note that wired ethernet connections work just fine, however it
- is annoying to find some business that has wired ports and some have
- none at all :(
+ This present a security flaw as the only solution is to add all users to
+ netdev group or make all accounts admin (or having everyone know the
+ admin password).
  
- This bug is present in 13.10 AND 14.04
+ Wired ethernet connections work just fine for non-admin users, however
+ it is annoying to find some public places that has wired ports and some
+ have none at all :(
  
- Tested on 14.04 as of Febuary 28, 2014
+ Tested on 14.04.4 and 16.04.3 with latest updates
  
  ProblemType: Bug
- DistroRelease: Ubuntu 13.10
- Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
- ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
- Uname: Linux 3.11.0-15-generic x86_64
- NonfreeKernelModules: nvidia
- ApportVersion: 2.12.5-0ubuntu2.2
- Architecture: amd64
- Date: Sat Mar  1 09:52:27 2014
- ExecutablePath: /usr/bin/nm-applet
- IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
- InstallationDate: Installed on 2013-10-25 (127 days ago)
- InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
- IpRoute:
-  default via 69.145.136.1 dev eth0  proto static 
-  69.145.136.0/22 dev eth0  proto kernel  scope link  src 69.145.137.13  
metric 1
- IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
- MarkForUpload: True
- NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
-  WimaxEnabled=true
- ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
- SourcePackage: network-manager-applet
- UpgradeStatus: No upgrade log present (probably fresh install)
- nmcli-con:
-  NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
-  Wired connection 12e05c40f-3e1f-4b48-a4f3-2efbe1450403   
802-3-ethernet1393692735   Sat 01 Mar 2014 09:52:15 AM MSTyes   
no /org/freedesktop/NetworkManager/Settings/0
- nmcli-dev:
-  DEVICE TYPE  STATE DBUS-PATH 
 
-  eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
- nmcli-nm:
-  RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
-  running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled
+ DistroRelease: Ubuntu 16.04
+ Package: gnome-control-center 1:3.18.2-1ubuntu6

** Tags removed: amd64 apport-bug saucy
** Tags added: trusty xenial

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

Title:
  Standard (non-admin) users can't connect to new wireless networks on
  GNOME Shell

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu-GNOME 14.04 or 16.04, the first account is the admin 
account. The admin account can connect to new wifi connections just fine 
without needing the admin password, but:
  1. Create a standard (non-admin) user, then log-in with non-admin account and 

[Desktop-packages] [Bug 1286578] Re: Standard (non-admin) users can't connect to new wireless networks on GNOME Shell

[Launchpad Bug Tracker]

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

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

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

Title:
  Standard (non-admin) users can't connect to new wireless networks on
  GNOME Shell

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu 13.10 or 14.04, the first account is the admin
  account.  The admin account can connect to new wifi connections just
  fine without needing the admin password.  When the admin account
  creates a standard non-admin, that non-admin account when it tries to
  connect to new wifi connections, pops up a dialog box asking for the
  admin password.  Non-admin accounts can not connect to new wifi
  connections without the admin account.  Does this present a security
  flaw as the only solution is to make all accounts admin or having
  everyone know the admin password.  My sister is the admin account for
  the laptop and she can connect just fine.  I however is only just a
  non-admin account and everywhere I go I am asked for the admin account
  everytime I want to connect to wifi at Starbucks or any other place.

  I should note that wired ethernet connections work just fine, however
  it is annoying to find some business that has wired ports and some
  have none at all :(

  This bug is present in 13.10 AND 14.04

  Tested on 14.04 as of Febuary 28, 2014

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Mar  1 09:52:27 2014
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-25 (127 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 69.145.136.1 dev eth0  proto static 
   69.145.136.0/22 dev eth0  proto kernel  scope link  src 69.145.137.13  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 12e05c40f-3e1f-4b48-a4f3-2efbe1450403   
802-3-ethernet1393692735   Sat 01 Mar 2014 09:52:15 AM MSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1286578] Re: Standard (non-admin) users can't connect to new wireless networks on GNOME Shell

[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 network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1286578

Title:
  Standard (non-admin) users can't connect to new wireless networks on
  GNOME Shell

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu 13.10 or 14.04, the first account is the admin
  account.  The admin account can connect to new wifi connections just
  fine without needing the admin password.  When the admin account
  creates a standard non-admin, that non-admin account when it tries to
  connect to new wifi connections, pops up a dialog box asking for the
  admin password.  Non-admin accounts can not connect to new wifi
  connections without the admin account.  Does this present a security
  flaw as the only solution is to make all accounts admin or having
  everyone know the admin password.  My sister is the admin account for
  the laptop and she can connect just fine.  I however is only just a
  non-admin account and everywhere I go I am asked for the admin account
  everytime I want to connect to wifi at Starbucks or any other place.

  I should note that wired ethernet connections work just fine, however
  it is annoying to find some business that has wired ports and some
  have none at all :(

  This bug is present in 13.10 AND 14.04

  Tested on 14.04 as of Febuary 28, 2014

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Mar  1 09:52:27 2014
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-25 (127 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 69.145.136.1 dev eth0  proto static 
   69.145.136.0/22 dev eth0  proto kernel  scope link  src 69.145.137.13  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 12e05c40f-3e1f-4b48-a4f3-2efbe1450403   
802-3-ethernet1393692735   Sat 01 Mar 2014 09:52:15 AM MSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1286578] Re: Standard (non-admin) users can't connect to new wireless networks on GNOME Shell

[Mantas Kriaučiūnas]

** Summary changed:

- Non-admin users need admin access to connect to new wifi.  A problem on 
mobile devices with standard non admin accounts.  Present on 13.10 to 14.04
+ Standard (non-admin) users can't connect to new wireless networks on GNOME 
Shell

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

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

Title:
  Standard (non-admin) users can't connect to new wireless networks on
  GNOME Shell

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  When you install Ubuntu 13.10 or 14.04, the first account is the admin
  account.  The admin account can connect to new wifi connections just
  fine without needing the admin password.  When the admin account
  creates a standard non-admin, that non-admin account when it tries to
  connect to new wifi connections, pops up a dialog box asking for the
  admin password.  Non-admin accounts can not connect to new wifi
  connections without the admin account.  Does this present a security
  flaw as the only solution is to make all accounts admin or having
  everyone know the admin password.  My sister is the admin account for
  the laptop and she can connect just fine.  I however is only just a
  non-admin account and everywhere I go I am asked for the admin account
  everytime I want to connect to wifi at Starbucks or any other place.

  I should note that wired ethernet connections work just fine, however
  it is annoying to find some business that has wired ports and some
  have none at all :(

  This bug is present in 13.10 AND 14.04

  Tested on 14.04 as of Febuary 28, 2014

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: network-manager-gnome 0.9.8.0-1ubuntu5.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Mar  1 09:52:27 2014
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-25 (127 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 69.145.136.1 dev eth0  proto static 
   69.145.136.0/22 dev eth0  proto kernel  scope link  src 69.145.137.13  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 12e05c40f-3e1f-4b48-a4f3-2efbe1450403   
802-3-ethernet1393692735   Sat 01 Mar 2014 09:52:15 AM MSTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1706456] Re: "JulyShakedown" When I open firefox, I get some really weird scrambling of the screen.

[Charlie Luna]

i'm still having this issue but very rarely.

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

Title:
  "JulyShakedown" When I open firefox, I get some really weird
  scrambling of the screen.

Status in firefox package in Ubuntu:
  New

Bug description:
  It happens almost everytime I open firefox. I'm using a lenovo ideapad
  310-15ABR with a quad-core, 7th generation AMD A12 processor, 8GBs
  RAM, A Samsung SSD, and I'm not sure what graphic chipset I've got but
  it's all fairly new hardware. I'm running Ubuntu 17.10 daily build
  from today, 2017-07-25. The scrambling happens around the window as it
  opens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 54.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  charlie1036 F pulseaudio
   /dev/snd/controlC0:  charlie1036 F pulseaudio
  BuildID: 20170616154447
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Tue Jul 25 15:17:40 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-07-25 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725)
  IpRoute:
   default via 192.168.1.1 dev wlp1s0 proto static metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.2 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 1LCN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Toronto 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15ABR
  dmi.modalias: 
dmi:bvnLENOVO:bvr1LCN32WW:bd09/05/2016:svnLENOVO:pn80ST:pvrLenovoideapad310-15ABR:rvnLENOVO:rnToronto5B1:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15ABR:
  dmi.product.name: 80ST
  dmi.product.version: Lenovo ideapad 310-15ABR
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1706476] Re: Mysterious shadow around window when check marking an option box inside of window

[Charlie Luna]

i'm still having this issue.

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

Title:
  Mysterious shadow around window when check marking an option box
  inside of window

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  this mysterious shadow occurs when I click inside an empty option box
  in a window to download a file from my cloud service. it's the option
  box for "do this automatically for files like this for now on." the
  shadow is very brief and completely surrounds the window and is the
  same shape as the window, square. I've never seen this type of
  behavior on any version of Ubuntu so I thought it was a bug of some
  kind worth mentioning and it occurs every time I click the box to
  select/deselect it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 25 18:25:25 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 
'refresh-w...@kgshank.net']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 'gimp.desktop', 
'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Calculator.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-07-25 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1706807] Re: [amdgpu] scrambling/pixelation and jutter upon opening thunderbird

[Charlie Luna]

still happens from time to time

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

Title:
  [amdgpu] scrambling/pixelation and jutter upon opening thunderbird

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  There's some screen scrambling/pixelation and jutter upon opening
  thunderbird. sometimes there's only a small portion of the opened
  window where you can parts of emails and it has a flickering to it and
  then the rest of the window opens. I'll provide a video of it once I'm
  able to record the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-11.16-generic 4.11.10
  Uname: Linux 4.11.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 26 16:14:39 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['dash-to-d...@micxgx.gmail.com', 
'refresh-w...@kgshank.net']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 'gimp.desktop', 
'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Calculator.desktop', 
'org.gnome.Software.desktop', 'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-07-25 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1710425] Re: Wifi icon becomes a white square when connection lost.

[Charlie Luna]

just revisiting this bug report to make an update. i still get the white
box where the wifi signal icon should be when i click the arrow in the
top right corner for the menu located there but it's very rare anymore.
it still seems like i've lost connection when it happens and i've got to
click on select network and then the box disappears and the wifi signal
icon reappears and my connection comes back.

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

Title:
  Wifi icon becomes a white square when connection lost.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When my laptop has been idle for a little while, somewhere between 30
  minutes to an hour, my wifi connection will drop and disappear and a
  small white box will present where the name of my connection should in
  the window for connections, battery percentage/time, etc. I'm
  attaching screen grabs for analysis.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.3-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-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Aug 12 16:00:39 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'firefox.desktop', 'thunderbird.desktop', 'hexchat.desktop', 
'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 
'org.gnome.Terminal.desktop', 'org.gnome.Software.desktop', 
'gnome-control-center.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'gtk-color-scheme' 
b"'selected_bg_color:#3465a4;selected_fg_color:#ff;'"
  InstallationDate: Installed on 2017-08-09 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170809)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1418400] Re: 'Failed to add/activate connection' error pops up when user try to connect guest wifi in login interface.

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => 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/1418400

Title:
  'Failed to add/activate connection' error pops up when user try to
  connect guest wifi in login interface.

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Install stock ubuntu image
  2. Do not connect wifi on OOBE stage
  3. Log in 'Guest' session
  4. Connect a available wifi
  5. Log out
  6. In login interface, select the user whom configured on OOBE stage
  7. Try to connect previous wifi which 'Guest' connected in login interface
  8. Verify the result

  Actual result:
  'Failed to add/activate connection' error pops up

  Expected result:
  User could connect the wifi successfully without error message

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

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

[Desktop-packages] [Bug 1711851] Re: bad default setting

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => 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/1711851

Title:
  Disable MAC address randomization on Live system

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using the pre-release version of artful 17.10 and network manager
  1.8.2-1ubuntu2 Much like in Debian Stretch, network-manager is set to
  use the random mac address feature of network manager, which doesn't
  allow certain wifi cards/ routers to work together. See Debian bug
  836351.  I think this feature should be disabled on a live cd, because
  it isn't fixable during an install and it might cause a user just to
  give up and not install Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug 19 14:00:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170818)
  IpRoute:
   default via 192.168.1.1 dev wlxec086b17f6d1 proto static metric 600 
   169.254.0.0/16 dev wlxec086b17f6d1 scope link metric 1000 
   192.168.1.0/24 dev wlxec086b17f6d1 proto kernel scope link src 192.168.1.4 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-08-19T13:51:03.103665
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH SLAVE 
   556F02  72b161b9-3dad-4583-ae59-1d3e0402b37e  802-11-wireless  
1503165502  Sat 19 Aug 2017 01:58:22 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxec086b17f6d1  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  1d860881-8bc6-3d0d-8455-2b15a87f1307  802-3-ethernet   
1503165498  Sat 19 Aug 2017 01:58:18 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   wlxec086b17f6d1  wifi  connected
/org/freedesktop/NetworkManager/Devices/3  556F02  
72b161b9-3dad-4583-ae59-1d3e0402b37e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1 ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1711851] Re: Disable MAC address randomization on Live system

[Mantas Kriaučiūnas]

** Summary changed:

- bad default setting
+ Disable MAC address randomization on Live system

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

Title:
  Disable MAC address randomization on Live system

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I'm using the pre-release version of artful 17.10 and network manager
  1.8.2-1ubuntu2 Much like in Debian Stretch, network-manager is set to
  use the random mac address feature of network manager, which doesn't
  allow certain wifi cards/ routers to work together. See Debian bug
  836351.  I think this feature should be disabled on a live cd, because
  it isn't fixable during an install and it might cause a user just to
  give up and not install Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Aug 19 14:00:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-08-19 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 
(20170818)
  IpRoute:
   default via 192.168.1.1 dev wlxec086b17f6d1 proto static metric 600 
   169.254.0.0/16 dev wlxec086b17f6d1 scope link metric 1000 
   192.168.1.0/24 dev wlxec086b17f6d1 proto kernel scope link src 192.168.1.4 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-08-19T13:51:03.103665
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH SLAVE 
   556F02  72b161b9-3dad-4583-ae59-1d3e0402b37e  802-11-wireless  
1503165502  Sat 19 Aug 2017 01:58:22 PM EDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlxec086b17f6d1  
activated  /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  1d860881-8bc6-3d0d-8455-2b15a87f1307  802-3-ethernet   
1503165498  Sat 19 Aug 2017 01:58:18 PM EDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --   
-- --  --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   wlxec086b17f6d1  wifi  connected
/org/freedesktop/NetworkManager/Devices/3  556F02  
72b161b9-3dad-4583-ae59-1d3e0402b37e  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1 ethernet  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1718850] Re: System extensions appear off by default

[Daniel van Vugt]

Do you mean classic or default? Because the gnome-classic session is
part of package 'gnome-shell-extensions', not installed by default :)

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

Title:
  System extensions appear off by default

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-tweak-tool package in Ubuntu:
  New

Bug description:
  Go to the Extensions panel in Tweaks.
  System extensions (dock and appindicators) appear off by default, where they 
are obviously not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-tweak-tool 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 08:02:59 2017
  ExecutablePath: /usr/bin/gnome-tweak-tool
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  SourcePackage: gnome-tweak-tool
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1718927] Re: No hdmi sound after suspend/resume on 16.04

[Daniel van Vugt]

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

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

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

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

[Desktop-packages] [Bug 1661329] Re: Wifi password not taken into account if not entered rapidly

[Mantas Kriaučiūnas]

Maybe this bug is a duplicate of LP bug #1650835 (wifi association times
out while typing password)?

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

Title:
  Wifi password not taken into account if not entered rapidly

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  We install ubuntu/mint to numerous people and we got multiple
  reports that the wifi password was not taken into account. We managed
  to reproduce it by

  1 - Select your wifi network
  2 - Enter a fake password (Just to simulate a user error not entering well 
his wifi password)
  3 - Obviously here we cannot connect, so we wait
  4 - Password is asked a second time, and we enter it without error but we 
take our time to do so ( or wait some time after ). By taking our time we 
simulate people who are not fluent with their keyboard.
  5 - Wait to connect
  6 - Password is asked a third time.
  7 - Here if we go into the properties of the wifi (Applet > Modify > Modify) 
and check the password… the first fake password is still there

  Nice day

  It might be a double of this bug
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1219171

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

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

[Desktop-packages] [Bug 1650835] Re: wifi association times out while typing password

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => 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/1650835

Title:
  wifi association times out while typing password

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Visiting inlaws for the holidays.

  The wifi password is a long numeric string, which takes a long time to
  type.

  I typed it several times and failed to connect.  I verified it and
  tried again and again.  Finally typed it into text file, copied and
  pasted, it connected.

  I suspect the connection was timing out or something while I typed the
  stupid long numeric password.

  What I expected to happen:

  type password, click connect, get connection, or some useful error.
  user happy.

  What actually happened:

  type password, click connect, dialog disappears and nothing else
  happens. user confused and unhappy.

  It shouldn't silently fail because I'm taking a long time to type.

  
  thanks, love you!  <3

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  $ apt-cache policy network-manager
  network-manager:
Installed: 1.2.2-0ubuntu0.16.04.3
Candidate: 1.2.2-0ubuntu0.16.04.3
Version table:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 17 21:24:22 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-03 (76 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp4s0  proto static  metric 600 
   169.254.0.0/16 dev wlp4s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp4s0  proto kernel  scope link  src 192.168.0.27  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp4s0 wifi  connected/org/freedesktop/NetworkManager/Devices/0  
Harry 5G10d05741-6f9e-468e-b6fd-8f0d5a739ce2  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   enp0s31f6  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 964705] Re: System policy prevents modification of network settings for all users

[Mantas Kriaučiūnas]

It seems Debian fix is simply to allow users from netdev (and sudo)
group add/change system-wide NetworkManager connections, this fix is
added in network-manager 0.9.4.0-7 and is merged in Ubuntu,

look at
/var/lib/polkit-1/localauthority/10-vendor.d/org.freedesktop.NetworkManager.pkla

[Adding or changing system-wide NetworkManager connections]
Identity=unix-group:netdev;unix-group:sudo
Action=org.freedesktop.NetworkManager.settings.modify.system

So, main problem is that GNOME-Shell users aren't added to netdev group
by default?

Walter Lapchynski (wxl) wrote on 2015-06-29:#38
> Mathieu, it doesn't seem that the upstream fix in Debian ever got merged into 
> Ubuntu.
> Is there a reason for this?

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

Title:
  System policy prevents modification of network settings for all users

Status in NetworkManager:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Debian:
  Fix Released
Status in network-manager package in openSUSE:
  Fix Released

Bug description:
  This seems like a regression? The screen shot is at
  http://thesii.org/Screenshot.jpg The nearest link I can find is from
  the forum area at http://ubuntuforums.org/showthread.php?p=1146

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sun Mar 25 19:36:45 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120323)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Re: [Desktop-packages] [Bug 1718927] Re: No hdmi sound after suspend/resume on 16.04

[Jacek Wróbel]

Hi Daniel,
I have Ubuntu Gnome 16.04.3. After resuming I can change device in settings
but it gives no result - still silence. The sound is only on the speakers.
The only way to restore sound in HDMI is to reboot.
But I am not pretty sure if the problem relates to pulse audio. I
reinstalled the system and did not install pulseaudio at all. Still the
same. After resuming there is no sound in HDMI.
Regards

Jacek Wróbel SAC, Kielecka 33, Święta Katarzyna, 26-010 Bodzentyn

2017-09-25 21:56 GMT+02:00 Daniel van Vugt
:

> At a guess, your system is probably reverting back to the default audio
> device on resume.
>
> What does it look like in Settings after resuming? Can you change the
> audio playback device back to HDMI by hand?
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1718927
>
> Title:
>   No hdmi sound after suspend/resume on 16.04
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
>   perfectly, but when I suspend computer and resume it there is no sound
>   via HDMI in TV. However sound via built in speakers works fine. The
>   only thing I can do to restore sound is to reboot the machine. Similar
>   problem was discussed in following thread
>   https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
>   tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
>   solution.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+
> bug/1718927/+subscriptions
>

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

Title:
  No hdmi sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

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

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

[Desktop-packages] [Bug 1718850] Re: System extensions appear off by default

[Jeremy Bicha]

Daniel, no this is a bug for all GNOME Shell modes including GNOME
Classic.

** Tags added: rls-aa-incoming

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

Title:
  System extensions appear off by default

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-tweak-tool package in Ubuntu:
  New

Bug description:
  Go to the Extensions panel in Tweaks.
  System extensions (dock and appindicators) appear off by default, where they 
are obviously not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-tweak-tool 3.26.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 08:02:59 2017
  ExecutablePath: /usr/bin/gnome-tweak-tool
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 
3.6.1-0ubuntu3
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
  SourcePackage: gnome-tweak-tool
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719201] Re: when unlocking users in gnome settings the app crashes

[Jeremy Bicha]

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

** This bug has been marked a duplicate of bug 1718793
   Unable to unlock account to enable auto-login

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

Title:
  when unlocking users in gnome settings the app crashes

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

Bug description:
  When unlocking "users" section of gnome (shell 3.26) settings app in
  current daily build  (Ubuntu Gnome 17.10) the app closes without
  error.

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

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

[Desktop-packages] [Bug 1718793] Re: 17.10 Settings > Users crashes when unlocked

[Jeremy Bicha]

** Summary changed:

- Unable to unlock account to enable auto-login
+ 17.10 Settings > Users crashes when unlocked

** Tags added: rls-aa-incoming

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

Title:
  17.10 Settings > Users crashes when unlocked

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Please take a look @ screencast. Account isn't unlocked after entering 
password and setting window disappears.
  Can assist with fixing it, but need guidelines how to do it.

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

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

[Desktop-packages] [Bug 1719485] Re: gnome-control-center user-accounts crashes on unlock

[Jeremy Bicha]

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

** This bug has been marked a duplicate of bug 1718793
   17.10 Settings > Users crashes when unlocked

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

Title:
  gnome-control-center user-accounts crashes on unlock

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

Bug description:
  gnome-control-center user-accounts crashes on unlock.
  gnome-control-center does not crash when unlocking if the password is wrong - 
only when password is accepted.

  This is on a fresh install of 17.10 daily
  Apport does not detect the crash so I cannot generate a crash report with 
this.

  Running `sudo gnome-control-center` shows a completely different menu
  and does not respond to clicks.

  Release:17.10

  gnome-control-center:
Installed: 1:3.26.0-0ubuntu2
Candidate: 1:3.26.0-0ubuntu2
Version table:
   *** 1:3.26.0-0ubuntu2 500
  500 http://nz.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  Expected:
  Unlock at `user-accounts` by supplying correct password - then able to enable 
automatic login etc.

  What happened:
  gnome-control-center closes with no message

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

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

[xtsbdu3reyrbrmroezob]

@jim no the ubuntu security team also did not respond regarding this
issue. unfortunately, it is actually being abused by the great firewall
of china to spy on ubuntu users within the border of china. from what we
can tell, the ubuntu security team does not take nation state level
issues very seriously, which is unfortunate, since google is one of the
largest commercial users of ubuntu distro and they are the main target
of nation states.

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Incomplete

Bug description:
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over
  HTTP. This can potentially be utilized by nation state adversaries to
  compromise user privacy. This service is called multiple times per day
  by the OS in order to track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1718885] Re: chromium 61 doesn't start in guest session

[Olivier Tilloy]

** Summary changed:

- chromium doesn't start in guest session (xubuntu 16.04)
+ chromium 61 doesn't start in guest session

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

Title:
  chromium 61 doesn't start in guest session

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  Hi,

  on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion
  4.4.0-28-generic) chromium stop working today. It just won't start
  anymore. When I try to run the launcher from shell it just reports:

  /usr/lib/chromium-browser/chromium-browser: error while loading shared
  libraries: libffmpeg.so: cannot open shared object file: No such file
  or directory

  The funny thing is ffmpeg was'n installed in the first place and
  chromium runs just fine in the context of a normal userprofile.

  I checked the apt histroy and saw chromium was updated today. I then
  tried to install ffmpeg in the hopes to solve the issue but to no
  avail. Now I can find libffmpeg in the guest user contest via locate
  but chromium still repsonds with the same error message.

  apt-cache policy chromium-browser
  chromium-browser:
    Installiert:   61.0.3163.79-0ubuntu0.16.04.1300
    Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300
    Versionstabelle:
   *** 61.0.3163.79-0ubuntu0.16.04.1300 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
   18.0.1025.151~r130497-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 
Packages

  I start chromium via a custom starter with line:
  chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php --
  kiosk

  The behavior started after unattended upgrades

  Start-Date: 2017-09-22  09:28:13
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubun  tu0.16.04.11), 
libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg   
   -0ubuntu0.16.04.11), samba-libs:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+  
dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 
(60.0.3112.113-0ubuntu0.16.04.12  98, 
61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu
  0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), 
chromium-codecs-ffmpeg-extra:amd64   
(60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), 
libsmbcli  ent:amd64 
(2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam  
ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 
2:4.3.11+dfsg-0ubuntu0.16.0  4.11), 
chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163   
   .79-0ubuntu0.16.04.1300)
  End-Date: 2017-09-22  09:28:30

  Start-Date: 2017-09-22  10:32:17
  Requested-By: gast-settings (1001)
  End-Date: 2017-09-22  10:32:17

  Start-Date: 2017-09-22  10:43:42
  Requested-By: gast-settings (1001)
  Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), 
ffmp  eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut  
omatic)
  End-Date: 2017-09-22  10:43:44

  Any ideas?
  Best Regards

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

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

[Desktop-packages] [Bug 1617535] Re: geoip.ubuntu.com does not utilize HTTPS

[Jim Campbell]

Any update to this bug?  Seems that it would be adviseable to make the
change to https for any services possible. The less unencrypted traffic
over the web, the better.

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

Title:
  geoip.ubuntu.com does not utilize HTTPS

Status in ubuntu-geoip package in Ubuntu:
  Incomplete

Bug description:
  geoip.ubuntu.com does not utilize HTTPS and leaks unencrypted over
  HTTP. This can potentially be utilized by nation state adversaries to
  compromise user privacy. This service is called multiple times per day
  by the OS in order to track users.

  $ nc -zv geoip.ubuntu.com 80
  Connection to geoip.ubuntu.com 80 port [tcp/http] succeeded!

  $ nc -zv -w 3 geoip.ubuntu.com 443
  nc: connect to geoip.ubuntu.com port 443 (tcp) timed out

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Sebastien Bacher]

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

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

Title:
  UIFe, white backgound for list

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719729] ChromiumPrefs.txt

[DiagonalArg]

apport information

** Attachment added: "ChromiumPrefs.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957399/+files/ChromiumPrefs.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] Dependencies.txt

[DiagonalArg]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957400/+files/Dependencies.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Sebastien Bacher]

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

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

Title:
  UIFe, white backgound for list

Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719729] ProcCpuinfoMinimal.txt

[DiagonalArg]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957403/+files/ProcCpuinfoMinimal.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] etcconfigc00example.txt

[DiagonalArg]

apport information

** Attachment added: "etcconfigc00example.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957406/+files/etcconfigc00example.txt

** Description changed:

- Since the update which included the kernel update from 4.4.0-92 to 4.4.0-93, 
the bottom scroll bar on chromium is continually flashing on/off, even when the 
screen is large enough (horizontally) for the page (so usually there wouldn't 
be a scroll bar) and even when there's no activity in the browser (I just let 
it sit for a while and it continually flashes).  The rate seems a bit random.
- --- 
- ApportVersion: 2.20.1-0ubuntu2.10
- Architecture: amd64
- CurrentDesktop: GNOME
- DetectedPlugins:
-  
- DistroRelease: Ubuntu 16.04
- InstallationDate: Installed on 2016-05-31 (482 days ago)
- InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
- Package: chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300
- PackageArchitecture: amd64
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
- Tags: xenial third-party-packages
- Uname: Linux 4.4.0-96-generic x86_64
- UpgradeStatus: No upgrade log present (probably fresh install)
- UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
- _MarkForUpload: True
- modified.conffile..etc.default.chromium-browser: [deleted]
+ Since the update which included the kernel update from 4.4.0-92 to
+ 4.4.0-93, the bottom scroll bar on chromium is continually flashing
+ on/off, even when the screen is large enough (horizontally) for the page
+ (so usually there wouldn't be a scroll bar) and even when there's no
+ activity in the browser (I just let it sit for a while and it
+ continually flashes).  The rate seems a bit random.  This is happening
+ in both regular and incognito mode.

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] RelatedPackageVersions.txt

[DiagonalArg]

apport information

** Attachment added: "RelatedPackageVersions.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957404/+files/RelatedPackageVersions.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] JournalErrors.txt

[DiagonalArg]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957402/+files/JournalErrors.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] Re: Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

[DiagonalArg]

When running apport -p chromium-browser , I get this error
in the terminal (and end up with a popup screen asking me to send bug
info to the developers):

ERROR: hook /usr/share/apport/package-hooks/chromium-browser.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 197, in 
_run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/chromium-browser.py", line 185, in 
add_info
user_prefs(report, user_dir + "/Preferences")
  File "/usr/share/apport/package-hooks/chromium-browser.py", line 116, in 
user_prefs
"   - enabled = " + str(plugin['enabled']) + "\n"
KeyError: 'enabled'

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] HookError_chromium_browser.txt

[DiagonalArg]

apport information

** Attachment added: "HookError_chromium_browser.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957401/+files/HookError_chromium_browser.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] RelatedPackagesPolicy.txt

[DiagonalArg]

apport information

** Attachment added: "RelatedPackagesPolicy.txt"
   
https://bugs.launchpad.net/bugs/1719729/+attachment/4957405/+files/RelatedPackagesPolicy.txt

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1719729] [NEW] Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

[DiagonalArg]

Public bug reported:

Since the update which included the kernel update from 4.4.0-92 to
4.4.0-93, the bottom scroll bar on chromium is continually flashing
on/off, even when the screen is large enough (horizontally) for the page
(so usually there wouldn't be a scroll bar) and even when there's no
activity in the browser (I just let it sit for a while and it
continually flashes).  The rate seems a bit random.  This is happening
in both regular and incognito mode.

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


** Tags: apport-collected third-party-packages xenial

** Tags added: apport-collected third-party-packages xenial

** Description changed:

- Since the update which included the kernel update from 4.4.0-92 to
- 4.4.0-93, the bottom scroll bar on chromium is continually flashing
- on/off, even when the screen is large enough (horizontally) for the page
- (so usually there wouldn't be a scroll bar) and even when there's no
- activity in the browser (I just let it sit for a while and it
- continually flashes).  The rate seems a bit random.
+ Since the update which included the kernel update from 4.4.0-92 to 4.4.0-93, 
the bottom scroll bar on chromium is continually flashing on/off, even when the 
screen is large enough (horizontally) for the page (so usually there wouldn't 
be a scroll bar) and even when there's no activity in the browser (I just let 
it sit for a while and it continually flashes).  The rate seems a bit random.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ CurrentDesktop: GNOME
+ DetectedPlugins:
+  
+ DistroRelease: Ubuntu 16.04
+ InstallationDate: Installed on 2016-05-31 (482 days ago)
+ InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
+ Package: chromium-browser 61.0.3163.79-0ubuntu0.16.04.1300
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
+ Tags: xenial third-party-packages
+ Uname: Linux 4.4.0-96-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ modified.conffile..etc.default.chromium-browser: [deleted]

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

Title:
  Chromium Browser - Bottom Scroll Bar Flashing On/Off Continually

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Since the update which included the kernel update from 4.4.0-92 to
  4.4.0-93, the bottom scroll bar on chromium is continually flashing
  on/off, even when the screen is large enough (horizontally) for the
  page (so usually there wouldn't be a scroll bar) and even when there's
  no activity in the browser (I just let it sit for a while and it
  continually flashes).  The rate seems a bit random.  This is happening
  in both regular and incognito mode.

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

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

[Desktop-packages] [Bug 1450147] Re: 'im-config -l' complains about zenity not installed

[Bug Watch Updater]

** Changed in: im-config (Debian)
   Status: New => Fix Released

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

Title:
  'im-config -l' complains about zenity not installed

Status in im-config package in Ubuntu:
  Fix Released
Status in im-config source package in Trusty:
  Fix Released
Status in im-config source package in Wily:
  Fix Released
Status in im-config package in Debian:
  Fix Released

Bug description:
  trusty and wily SRU request
  ===

  [Impact]
  The 'im-config -l' call causes language-selector-gnome to crash for users who 
don't have zenity installed. The proposed change prevents this unwarranted 
check.

  [Test Case]
  * Uninstall zenity
  * Open a terminal window and run gnome-language-selector.

  [Regression Potential]
  Low, since the change only delays the "sanity check" until after the l-option 
code.

  [Original description]
  The package language-selector-gnome 0.143 from the Vivid edition fails to 
start, complaining zenity is missing.

  $ gnome-language-selector
  E : zenity doit être installé.
  Traceback (most recent call last):
    File "/usr/bin/gnome-language-selector", line 22, in on_activate
  options=options)
    File 
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 199, in __init__
  self.check_input_methods()
    File 
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 54, in wrapper
  res = f(*args, **kwargs)
    File 
"/usr/lib/python3/dist-packages/LanguageSelector/gtk/GtkLanguageSelector.py", 
line 454, in check_input_methods
  for (i, IM) in enumerate(self.ImConfig.getAvailableInputMethods()):
    File "/usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py", line 
19, in getAvailableInputMethods
  inputMethods = subprocess.check_output(['im-config', 
'-l']).decode().split()
    File "/usr/lib/python3.4/subprocess.py", line 620, in check_output
  raise CalledProcessError(retcode, process.args, output=output)
  subprocess.CalledProcessError: Command '['im-config', '-l']' returned 
non-zero exit status 1
  $

  Once zenity is installed it starts and works perfectly.

  Thanks for fixing.

  Best regards,
  Mélodie

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

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

[Desktop-packages] [Bug 1704618] Re: gnome-control-center crashed with SIGSEGV in manager_recheck_permissions()

[Jean-Baptiste Lallement]

network-manager (1.8.4-1ubuntu1) artful; urgency=medium

  * debian/patches/manager-Disconnect-from-signals-on-the-proxy-when-we.patch,
debian/patches/vpn-remote-connection-disconnect-signal-handlers-whe.patch:
Cherry-pick two patches from upstream. Fix leaked signal connections which
caused handlers to be called on disposed objects, leading to crashes in
some situations. (LP: #1704618) (LP: #1718006)

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

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

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

Title:
  gnome-control-center crashed with SIGSEGV in
  manager_recheck_permissions()

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Test Case:
  1. Open the 'Users' panel in gnome-control-center
  2. Select a user then click on 'Unlock' (top right button in the title bar)

  Expected result
  The panel is unlocked

  Actual Result
  This crash.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.24.2-0ubuntu5
  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: Sun Jul 16 10:09:12 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-06-26 (20 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7ff4ea6fe6e9:cmpq   $0x0,0x58(%rax)
   PC (0x7ff4ea6fe6e9) ok
   source "$0x0" ok
   destination "0x58(%rax)" (0x0058) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   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_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
  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/network-manager/+bug/1704618/+subscriptions

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

[Desktop-packages] [Bug 1718158] Re: gnome software doesn't show all categories in a live session

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome software doesn't show all categories in a live session

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  gnome software doesn't show all categories or recent releases in a
  live session.

  Show fine when the system is installed

  see images

  Live session https://i.imgur.com/wqPJxSq.png

  Installed system https://i.imgur.com/07t7pBH.png

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: XFCE
  Date: Tue Sep 19 09:36:10 2017
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.0-0ubuntu1
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome-software-service.desktop: [deleted]

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

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

[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Daniel van Vugt]

That's great. But all we intended to fix was...
https://launchpad.net/ubuntu/+source/pulseaudio/1:8.0-0ubuntu3.4

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Jason Gambrel]

Received pulseaudio update last night.  Appears to have resolved issue
so far for me, still need a bit of testing.  If it is resolved then MANY
thanks to those who squashed this annoying bug.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Desktop-packages] [Bug 1659517] Re: media keys stopped working: "Could not find accelerator for accel id 123"

[Launchpad Bug Tracker]

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

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

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

Title:
  media keys stopped working: "Could not find accelerator for accel id
  123"

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Today after an involuntary reboot (laptop battery ran down) I can no
  longer use media keys like Mute, Volume Up/Down, PrintScreen.

  Every time I hit one of those keys I see messages like this in
  journalctl:

Sau 26 11:53:30 platonas gnome-settings-[4972]: Could not find
  accelerator for accel id 123

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-settings-daemon 3.22.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 26 11:56:17 2017
  InstallationDate: Installed on 2016-09-10 (138 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (102 days ago)

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

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

[Desktop-packages] [Bug 1098362] Re: DHCP settings for network manager shared connection are hard-coded source, should be editable

[Lucas Magasweran]

This has been fixed and merged upstream in nm-applet/network-manager
1.4.2.

https://bugzilla.gnome.org/show_bug.cgi?id=763937#c14

Ubuntu 17.04 has 1.4.4. Is it possible to backport this to 16.04 LTS?

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

Title:
  DHCP settings for network manager shared connection are hard-coded
  source, should be editable

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu 10.04, but it's in all versions.
  2) any version of network manager
  3) I want to be able to change the DHCP settings for a shared network 
connection
  4) YOUR OPERATING SYSTEM WON'T LET ME!

  The file nm-device.c contains this line:

  nm-device.c:guint32 start = (guint32) ntohl (0x0a2a2b01); /*
  10.42.43.1 */

  hard-coding DHCP settings that should obviously be editable by the
  user is a TERRIBLE IDEA.  PLEASE FIX.

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

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

[Desktop-packages] [Bug 1716277] Re: Moving a file to another folder, holding shift key, blocks mouse pointer

[Launchpad Bug Tracker]

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

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

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

Title:
  Moving a file to another folder, holding shift key,  blocks  mouse
  pointer

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When I try to move a file that's on the Desktop to another folder
  holding the shift after having clicked on it and started dragging it
  to the destination folder, the mouse pointer from an arrow becomes a
  hand and after this you are unable to click on other files or folders,
  even in Firefox you are unable to open another tab by clicking on the
  plus near the other tabs.

  To reproduce the bug:

  Open Files.
  Click on a file on the Desktop.
  Start dragging it to another folder in Files and while dragging press the 
shift key.
  The mouse arrow becomes a hand.
  Try to click on another file, you won't be able to.
  Open Firefox and try to open another tab, you won't be able to.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.25.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 21:56:09 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'343'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1394x615+36+32'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2017-06-01 (101 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1716277] Re: Moving a file to another folder, holding shift key, blocks mouse pointer

[Ldx]

Same issue on my Ubuntu 17.10 beta, freshly installed (no upgrade).

Just for completeness, this behaviour happens by just dragging a file
from desktop to any other window of nautilus (no shift key necessary).

Dragging from nautilus to desktop works.
Dragging from nautilus to another nautilus windows works.
Cut/Paste from/to desktop works.

It's the dragging action from desktop that looks flawed.

If useful, here is a screen recording that shows the issue (well, the
initial mouse drag and subsequent click attempts are not clearly visible
but I think that one can get the idea of the problem):

https://www.dropbox.com/s/kjzqucqb7hdcnvy/Screencast_drag_issue_ubuntu-17-10-beta.mp4?dl=0

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

Title:
  Moving a file to another folder, holding shift key,  blocks  mouse
  pointer

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  When I try to move a file that's on the Desktop to another folder
  holding the shift after having clicked on it and started dragging it
  to the destination folder, the mouse pointer from an arrow becomes a
  hand and after this you are unable to click on other files or folders,
  even in Firefox you are unable to open another tab by clicking on the
  plus near the other tabs.

  To reproduce the bug:

  Open Files.
  Click on a file on the Desktop.
  Start dragging it to another folder in Files and while dragging press the 
shift key.
  The mouse arrow becomes a hand.
  Try to click on another file, you won't be able to.
  Open Firefox and try to open another tab, you won't be able to.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.25.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 10 21:56:09 2017
  ExecutablePath: /usr/bin/nautilus-desktop
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'343'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1394x615+36+32'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency']"
  InstallationDate: Installed on 2017-06-01 (101 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170525)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: dropbox 2015.10.28

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

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

[Desktop-packages] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

[Naël]

Sounds right. I just assumed that there wasn't any users of releases <
Trusty any more, as all those releases are EOL. But actually there may
still be, indeed.

Bug should stay Confirmed until Trusty itself is EOL.

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Won't Fix
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

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

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

[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

[Jeremy Bicha]

Daniel, could you attach some screenshots to show the brokenness?

The patches could probably be updated to not change the UI on
Elementary.

What's the output of

echo $XDG_CURRENT_DESKTOP

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  New
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Incomplete
Status in gnome-contacts package in Ubuntu:
  Incomplete

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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

[Desktop-packages] [Bug 1719322] Re: Remove patch to remove headerbar

[Daniel Fore]

Mainly the issue for us is that it appears quite broken. It would be
preferable to use the upstream version of the application's UI.

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

Title:
  Remove patch to remove headerbar

Status in epiphany-browser package in Ubuntu:
  New
Status in evince package in Ubuntu:
  Incomplete
Status in file-roller package in Ubuntu:
  Incomplete
Status in gnome-contacts package in Ubuntu:
  Incomplete

Bug description:
  As of Artful, it seems that there are still patches against various
  apps that remove/replace the Gtk.HeaderBar with a Gtk.Toolbar.

  Now that GNOME Shell is default in Ubuntu and there is better support
  for client-side decorations, these patches can probably go away

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

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

[Desktop-packages] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

[Kenrick Bingham]

Please observe that this bug causes all lines in /etc/mailcap after the
broken line to be skipped. Therefore it also prevents other mime type
files from being opened by the intended application.

(In my case, I ran into this because alpine start saying that it did not
know how to handle files of type Application/VND.OPENXMLFORMATS-
OFFICEDOCUMENT.WORDPROCESSINGML.DOCUMENT, even though /etc/mailcap
contains the proper line, evoking soffice.)

Would this raise the importance of the bug?

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

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

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.4.4-1ubuntu3.2

---
network-manager (1.4.4-1ubuntu3.2) zesty; urgency=medium

  * debian/network-manager.postinst: drop in an empty override file for
NetworkManager to manage all devices for upgrade from any version, as long
as there is no netplan configuration yet. (LP: #1676547)

 -- Brian Murray   Fri, 08 Sep 2017 11:29:32 -0700

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

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  Fix Released

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you 
will boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety or zesty
  3.5) Enable -proposed and download the new version of n-m "apt-get download 
network-manager"
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  and then reboot you should have a network connection.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install nplan, configure to set up static network on an ethernet device 
using nplan.
  4) Upgrade to yakkety or zesty
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Desktop-packages] [Bug 1719690] Re: Chromedriver 2.30 does not work with Chrome 61

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1719572
   chromedriver can't click links outside of the window with Chromium 61

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

Title:
  Chromedriver 2.30 does not work with Chrome 61

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The latest `chromium-chromedriver` release
  (`61.0.3163.79-0ubuntu0.14.04.1196`) is actually Chromedriver 2.30,
  which does not work with Chromium 61, both according to the release
  notes [ https://chromedriver.storage.googleapis.com/2.32/notes.txt ]
  and to my attempts to use it.

  Ubuntu version:

  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  `chromium-chromedriver` version: 61.0.3163.79-0ubuntu0.14.04.1196
  `chromium-browser` version: 61.0.3163.79-0ubuntu0.14.04.1196

  What I expected to happen: `chromium-chromedriver` works with the
  `chromium-browser` version of the same version number.

  What happened instead: Selenium reported an error from `chromium-
  chromedriver` when trying to use it to boot Chromium

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

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

[Desktop-packages] [Bug 1719685] Re: Long delays on opening & freezes on closing application with SMB shared files

[Dan Bright]

Note that this is unlikely to be a network issue. Much larger files from
the same SMB share are opened with other applications almost
instantaneously.

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

Title:
  Long delays on opening & freezes on closing application with SMB
  shared files

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opening even small files (14.3kB) from an SMB share results in delays
  of 20 seconds or more.

  Clicking to close the Calc application after the file is saved results
  in a freeze. Only manually killing the libreoffice processes will
  close the application.

  (journal.txt deleted - judged irrelevant after replication of bug
  resulted in no log output during the period the issue was taking
  place).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1712200] Re: Changing keyboard layout with alt+shift always triggers "ui.key.menuAccessKey" on Wayland

[Valery]

** Also affects: firefox
   Importance: Undecided
   Status: New

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

Title:
  Changing keyboard layout with alt+shift always triggers
  "ui.key.menuAccessKey" on Wayland

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

Bug description:
  I'm on Ubuntu 17.10 with artful-proposed enabled.

  Changing keyboard layout with alt+shift always triggers "show menu"on
  Wayland, which makes firefox unusable for users who don't know how to
  disable the value "ui.key.menuAccessKeyFocuses" from about:config.

  Is there any fix? Or maybe you can set "ui.key.menuAccessKeyFocuses"
  to false  by default?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: firefox 54.0+build3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thanos25842 F pulseaudio
   /dev/snd/controlC0:  thanos25842 F pulseaudio
   /dev/snd/controlC1:  thanos25842 F pulseaudio
  BuildID: 20170616154447
  Channel: Unavailable
  CurrentDesktop: GNOME
  Date: Mon Aug 21 23:42:26 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-08-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  IpRoute:
   default via 192.168.2.1 dev wlp4s7 proto static metric 600 
   169.254.0.0/16 dev wlp4s7 scope link metric 1000 
   192.168.2.0/24 dev wlp4s7 proto kernel scope link src 192.168.2.2 metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=54.0/20170616154447 (In use)
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7d
  dmi.board.name: GA-970A-DS3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7d:bd09/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1719685] Re: Long delays on opening & freezes on closing application with SMB shared files

[Dan Bright]

** Attachment removed: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1719685/+attachment/4957362/+files/journal.txt

** Description changed:

  Opening even small files (14.3kB) from an SMB share results in delays of
  20 seconds or more.
  
  Clicking to close the Calc application after the file is saved results
  in a freeze. Only manually killing the libreoffice processes will close
  the application.
  
- See attached journal.txt for relevant log entries.
+ (journal.txt deleted - judged irrelevant after replication of bug
+ resulted in no log output during the period the issue was taking place).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Long delays on opening & freezes on closing application with SMB
  shared files

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opening even small files (14.3kB) from an SMB share results in delays
  of 20 seconds or more.

  Clicking to close the Calc application after the file is saved results
  in a freeze. Only manually killing the libreoffice processes will
  close the application.

  (journal.txt deleted - judged irrelevant after replication of bug
  resulted in no log output during the period the issue was taking
  place).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719691] [NEW] Featured subcategory missing on Ubuntu 17.10

[AsciiWolf]

Public bug reported:

The "Featured" subcategory in GNOME Software is missing in every
category except Graphics & Photography on my Ubuntu 17.10 installation.
I use non-english (Czech) system, but I believe this issue is not
related to the system language.

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


** Tags: artful

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

Title:
  Featured subcategory missing on Ubuntu 17.10

Status in gnome-software package in Ubuntu:
  New

Bug description:
  The "Featured" subcategory in GNOME Software is missing in every
  category except Graphics & Photography on my Ubuntu 17.10
  installation. I use non-english (Czech) system, but I believe this
  issue is not related to the system language.

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

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

[Desktop-packages] [Bug 1719685] Re: Freezes on application close

[Dan Bright]

** Description changed:

+ Opening even small files (14.3kB) from an SMB share results in delays of
+ 20 seconds or more.
+ 
  Clicking to close the Calc application after the file is saved results
- in a freeze.
+ in a freeze. Only manually killing the libreoffice processes will close
+ the application.
  
- When this happens, only manually killing the libreoffice processes will
- close the application.
+ See attached journal.txt for relevant log entries.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- Freezes on application close
+ Long delays on opening & freezes on closing application with SMB shared files

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1719685/+attachment/4957362/+files/journal.txt

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

Title:
  Long delays on opening & freezes on closing application with SMB
  shared files

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Opening even small files (14.3kB) from an SMB share results in delays
  of 20 seconds or more.

  Clicking to close the Calc application after the file is saved results
  in a freeze. Only manually killing the libreoffice processes will
  close the application.

  See attached journal.txt for relevant log entries.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719690] [NEW] Chromedriver 2.30 does not work with Chrome 61

[Noemi Lapresta]

Public bug reported:

The latest `chromium-chromedriver` release
(`61.0.3163.79-0ubuntu0.14.04.1196`) is actually Chromedriver 2.30,
which does not work with Chromium 61, both according to the release
notes [ https://chromedriver.storage.googleapis.com/2.32/notes.txt ] and
to my attempts to use it.

Ubuntu version:

Description:Ubuntu 14.04.5 LTS
Release:14.04

`chromium-chromedriver` version: 61.0.3163.79-0ubuntu0.14.04.1196
`chromium-browser` version: 61.0.3163.79-0ubuntu0.14.04.1196

What I expected to happen: `chromium-chromedriver` works with the
`chromium-browser` version of the same version number.

What happened instead: Selenium reported an error from `chromium-
chromedriver` when trying to use it to boot Chromium

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

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

Title:
  Chromedriver 2.30 does not work with Chrome 61

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The latest `chromium-chromedriver` release
  (`61.0.3163.79-0ubuntu0.14.04.1196`) is actually Chromedriver 2.30,
  which does not work with Chromium 61, both according to the release
  notes [ https://chromedriver.storage.googleapis.com/2.32/notes.txt ]
  and to my attempts to use it.

  Ubuntu version:

  Description:  Ubuntu 14.04.5 LTS
  Release:  14.04

  `chromium-chromedriver` version: 61.0.3163.79-0ubuntu0.14.04.1196
  `chromium-browser` version: 61.0.3163.79-0ubuntu0.14.04.1196

  What I expected to happen: `chromium-chromedriver` works with the
  `chromium-browser` version of the same version number.

  What happened instead: Selenium reported an error from `chromium-
  chromedriver` when trying to use it to boot Chromium

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

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

[Desktop-packages] [Bug 1719685] Re: Freezes on application close

[Dan Bright]

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1719685/+attachment/4957347/+files/JournalErrors.txt

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

Title:
  Freezes on application close

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Clicking to close the Calc application after the file is saved results
  in a freeze.

  When this happens, only manually killing the libreoffice processes
  will close the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719458] Re: "Add a color profile" window is too small

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Unknown => Fix Released

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

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

Title:
  "Add a color profile" window is too small

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  In gnome-control-center the dialog that lists the profiles available
  when adding a color profile is too small (1 line height) cf screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 17:12:23 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   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)

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

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

[Desktop-packages] [Bug 1719678] Re: screen lock does not go off after resume from suspend

[Jean-Baptiste Lallement]

** Description changed:

  Not always reproducible, sometimes, screen lock doesn't go off when the
  device resumes from suspend.
+ 
+ A reboot does not fix the issue.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 12:11:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
-  TERM=screen-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  TERM=screen-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  screen lock does not go off after resume from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not always reproducible, sometimes, screen lock doesn't go off when
  the device resumes from suspend.

  A reboot does not fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 12:11:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719043] Re: Gnome web urlbar very slow to show typed input

[Bug Watch Updater]

** Changed in: epiphany-browser
   Status: Confirmed => Incomplete

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

Title:
  Gnome web urlbar very slow to show typed input

Status in Epiphany Browser:
  Incomplete
Status in epiphany-browser package in Ubuntu:
  Triaged
Status in epiphany-browser package in Debian:
  New

Bug description:
  First two characters typed in urlbar show immediately, other
  characters take up to 30 seconds to appear, or url will appear in full
  once enter key is pressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: epiphany-browser 3.26.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 18:42:19 2017
  InstallationDate: Installed on 2017-09-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: epiphany-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1719685] [NEW] Freezes on application close

[Dan Bright]

Public bug reported:

Clicking to close the Calc application after the file is saved results
in a freeze.

When this happens, only manually killing the libreoffice processes will
close the application.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: libreoffice 1:5.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 26 17:27:13 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-09-14 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Freezes on application close

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Clicking to close the Calc application after the file is saved results
  in a freeze.

  When this happens, only manually killing the libreoffice processes
  will close the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 17:27:13 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-14 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170912)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1132736] Re: Xorg fails to start after installing the Hardware Enablement Stack due to missing symlink after purging old xserver-xorg

[Robie Basak]

> 13:47  Hi guys, anybody from Bug Control here can please switch
bug 1132736 xorg-lts-trusty from Confirmed to Won't Fix? Please see last
comment for rationale. Thanks!

Users may still want to upgrade from an EOL release to a supported
release though. Surely we should encourage this!

I think the bug sounds valid for Trusty still and an SRU to Trusty
shouldn't be rejected on this basis if someone wants to contribute one.
Won't Fix generally implies that we'd reject a fix even if were
contributed, and I don't think that's the case here.

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

Title:
  Xorg fails to start after installing the Hardware Enablement Stack due
  to missing symlink after purging old xserver-xorg

Status in xorg package in Ubuntu:
  Invalid
Status in xorg-lts-trusty package in Ubuntu:
  Confirmed
Status in xorg-lts-utopic package in Ubuntu:
  Won't Fix
Status in xorg-lts-vivid package in Ubuntu:
  Fix Released

Bug description:
  Bug:

  The bug happens whenever the remaining configuration files of the
  original X stack is removed, ie purging. It does not happen for users
  who do not explicitly remove those.

  Workaround:

  For example, if upgraded 14.04 LTS to the 14.04.2 HWE stack
  (=14.10/utopic):

  sudo dpkg-reconfigure xserver-xorg-lts-utopic

  This restores the symlink /etc/X11/X -> /usr/bin/Xorg

  ---

  After installing the hardware enablement stack on precise by running:
  sudo apt-get install linux-generic-lts-quantal xserver-xorg-lts-quantal

  Xorg fail to start. There is no error message or anything, just a black 
screen. Switching to a vt i possible and lightdm/x-0.log shows that a symlink 
is missing:
  X: cannot stat /etc/X11/X (No such file or directory), aborting.

  I updates two computers running precise x86_64 and both had the
  problem.

  Just recreating the symlink fixes the problem and then precise runs
  perfectly fine with the new stack (in fact, it's more stable so far).

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

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

[Desktop-packages] [Bug 1708753] Re: Crash in evince (seems related with AppArmor profile) (display_wayland->cursor_theme_name)

[Sebastien Bacher]

the issue has been fixed in
https://launchpad.net/ubuntu/+source/apparmor/2.11.0-2ubuntu16

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

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

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

Title:
  Crash in evince (seems related with AppArmor profile)
  (display_wayland->cursor_theme_name)

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  I have problems with Evince

  Seems very similar to an old Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827335

  This is the log when I try to open Evince from Terminal:
  julian@e01a27166:~$ evince

  (evince:5757): Gdk-WARNING **: Failed to load cursor theme DMZ-White

  (evince:5757): Gdk-WARNING **: Failed to load cursor theme DMZ-White
  **
  
Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme:
 assertion failed: (display_wayland->cursor_theme_name)
  Aborted (core dumped)
  julian@e01a27166:

  Also, this is the syslog with the error related to AppArmor:
  Aug  4 16:32:33 e01a27166 kernel: [ 2771.175434] audit: type=1400 
audit(1501882353.078:50): apparmor="DENIED" operation="mknod" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-CQkM8G" 
pid=5803 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000


  julian@e01a27166:~$ sudo apparmor_status
  [sudo] password for julian: 
  apparmor module is loaded.
  22 profiles are loaded.
  22 profiles are in enforce mode.
 /sbin/dhclient
 /usr/bin/evince
 /usr/bin/evince-previewer
 /usr/bin/evince-previewer//sanitized_helper
 /usr/bin/evince-thumbnailer
 /usr/bin/evince-thumbnailer//sanitized_helper
 /usr/bin/evince//sanitized_helper
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/snapd/snap-confine
 /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/ippusbxd
 /usr/sbin/libvirtd
 /usr/sbin/libvirtd//qemu_bridge_helper
 /usr/sbin/tcpdump
 libvirt-3d791c0a-939c-4f97-af9c-e2fa951adad6
 virt-aa-helper
  0 profiles are in complain mode.
  7 processes have profiles defined.
  7 processes are in enforce mode.
 /sbin/dhclient () 
 /usr/sbin/cups-browsed (895) 
 /usr/sbin/cupsd (842) 
 /usr/sbin/cupsd (1227) 
 /usr/sbin/cupsd (1228) 
 /usr/sbin/libvirtd (1013) 
 libvirt-3d791c0a-939c-4f97-af9c-e2fa951adad6 (2636) 
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  
  After using this commands:
  sudo aa-complain/usr/bin/evince
  sudo aa-complain/usr/bin/evince-previewer
  sudo aa-complain/usr/bin/evince-thumbnailer

  I was able to open Evince again and this is the log of syslog:

  Aug  4 16:41:14 e01a27166 kernel: [ 3292.825954] audit: type=1400 
audit(1501882874.732:100): apparmor="ALLOWED" operation="mknod" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.825957] audit: type=1400 
audit(1501882874.732:101): apparmor="ALLOWED" operation="open" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="wrc" denied_mask="wrc" fsuid=1000 
ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.825958] audit: type=1400 
audit(1501882874.732:102): apparmor="ALLOWED" operation="unlink" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.826148] audit: type=1400 
audit(1501882874.732:103): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.826208] audit: type=1400 
audit(1501882874.732:104): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.827153] audit: type=1400 
audit(1501882874.732:105): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.827185] audit: type=1400 

[Desktop-packages] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

[Sebastien Bacher]

That's a regression from CVE-2017-183.patch, upstream fixed it with
https://git.gnome.org/browse/evince/commit/?h=gnome-3-20=ef6c1d98

Steve, how do we handle regression due to security uploads like that?
(the problem is minor but ideally should be addressed)

** CVE added: https://cve.mitre.org/cgi-
bin/cvename.cgi?name=2017-183

** Changed in: evince (Ubuntu)
 Assignee: (unassigned) => Steve Beattie (sbeattie)

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

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

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

[Desktop-packages] [Bug 1719324] Re: 'Set date automatically' doesn't work

[Jean-Baptiste Lallement]

Location is desactivated in privacy settings.

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => 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/1719324

Title:
  'Set date automatically' doesn't work

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I'm travelling from France to US (NYC) The date is set to 'update
  automatically' but the time is still France time, even after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 15:59:03 2017
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   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)

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

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

[Desktop-packages] [Bug 1719324] Re: 'Set date automatically' doesn't work

[Jean-Baptiste Lallement]

Date is set automatically after turning this setting on. I'm closing
this report but it is clearly not obvious.

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

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

Title:
  'Set date automatically' doesn't work

Status in gnome-control-center package in Ubuntu:
  Won't Fix

Bug description:
  I'm travelling from France to US (NYC) The date is set to 'update
  automatically' but the time is still France time, even after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 15:59:03 2017
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   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)

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

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

[Desktop-packages] [Bug 1719678] [NEW] screen lock does not go off after resume from suspend

[Jean-Baptiste Lallement]

Public bug reported:

Not always reproducible, sometimes, screen lock doesn't go off when the
device resumes from suspend.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 26 12:11:12 2017
DisplayManager: gdm3
InstallationDate: Installed on 2013-09-03 (1483 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  screen lock does not go off after resume from suspend

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Not always reproducible, sometimes, screen lock doesn't go off when
  the device resumes from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 26 12:11:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1716357] Re: a typo in evince-previewer.desktop breaks /etc/mailcap

[Sebastien Bacher]

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

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

Title:
  a typo in evince-previewer.desktop breaks /etc/mailcap

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Release version: Ubuntu 16.04.3 LTS
  Package version: 3.18.2-1ubuntu4.1

  /usr/share/applications/evince-previewer.desktop comes from the evince
  package. It has an empty entry in mime types between application/x
  -ext-cb7 and application/oxps.

  ===8<===
  ...
  
MimeType=application/pdf;application/x-bzpdf;application/x-gzpdf;application/x-xzpdf;application/x-ext-pdf;application/postscript;application/x-bzpostscript;application/x-gzpostscript;image/x-eps;image/x-bzeps;image/x-gzeps;application/x-ext-ps;application/x-ext-eps;application/x-dvi;application/x-bzdvi;application/x-gzdvi;application/x-ext-dvi;image/vnd.djvu;application/x-ext-djv;application/x-ext-djvu;image/tiff;application/x-cbr;application/x-cbz;application/x-cb7;application/x-ext-cbr;application/x-ext-cbz;application/x-ext-cb7;;application/oxps;application/vnd.ms-xpsdocument;
  ...
  ===>8===

  This entry gets included in /etc/mailcap via update-mime trigger from
  the package mime-support and the result is a broken line:

  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  ; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

  Some programs that use /etc/mailcap get confused by the broken line so
  it would be nice if the typo it originates from was fixed.

  The expected result in /etc/mailcap from running update-mime:
  ===8<===
  ...
  application/x-ext-cb7; evince-previewer %s; test=test -n "$DISPLAY"
  application/oxps; evince-previewer %s; test=test -n "$DISPLAY"
  ...
  ===>8===

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

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

[Desktop-packages] [Bug 1708753] Re: Crash in evince (seems related with AppArmor profile) (display_wayland->cursor_theme_name)

[Sebastien Bacher]

is that still an issue?

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

Title:
  Crash in evince (seems related with AppArmor profile)
  (display_wayland->cursor_theme_name)

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  I have problems with Evince

  Seems very similar to an old Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827335

  This is the log when I try to open Evince from Terminal:
  julian@e01a27166:~$ evince

  (evince:5757): Gdk-WARNING **: Failed to load cursor theme DMZ-White

  (evince:5757): Gdk-WARNING **: Failed to load cursor theme DMZ-White
  **
  
Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme:
 assertion failed: (display_wayland->cursor_theme_name)
  Aborted (core dumped)
  julian@e01a27166:

  Also, this is the syslog with the error related to AppArmor:
  Aug  4 16:32:33 e01a27166 kernel: [ 2771.175434] audit: type=1400 
audit(1501882353.078:50): apparmor="DENIED" operation="mknod" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-CQkM8G" 
pid=5803 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000


  julian@e01a27166:~$ sudo apparmor_status
  [sudo] password for julian: 
  apparmor module is loaded.
  22 profiles are loaded.
  22 profiles are in enforce mode.
 /sbin/dhclient
 /usr/bin/evince
 /usr/bin/evince-previewer
 /usr/bin/evince-previewer//sanitized_helper
 /usr/bin/evince-thumbnailer
 /usr/bin/evince-thumbnailer//sanitized_helper
 /usr/bin/evince//sanitized_helper
 /usr/lib/NetworkManager/nm-dhcp-client.action
 /usr/lib/NetworkManager/nm-dhcp-helper
 /usr/lib/connman/scripts/dhclient-script
 /usr/lib/cups/backend/cups-pdf
 /usr/lib/snapd/snap-confine
 /usr/lib/snapd/snap-confine//mount-namespace-capture-helper
 /usr/sbin/cups-browsed
 /usr/sbin/cupsd
 /usr/sbin/cupsd//third_party
 /usr/sbin/ippusbxd
 /usr/sbin/libvirtd
 /usr/sbin/libvirtd//qemu_bridge_helper
 /usr/sbin/tcpdump
 libvirt-3d791c0a-939c-4f97-af9c-e2fa951adad6
 virt-aa-helper
  0 profiles are in complain mode.
  7 processes have profiles defined.
  7 processes are in enforce mode.
 /sbin/dhclient () 
 /usr/sbin/cups-browsed (895) 
 /usr/sbin/cupsd (842) 
 /usr/sbin/cupsd (1227) 
 /usr/sbin/cupsd (1228) 
 /usr/sbin/libvirtd (1013) 
 libvirt-3d791c0a-939c-4f97-af9c-e2fa951adad6 (2636) 
  0 processes are in complain mode.
  0 processes are unconfined but have a profile defined.

  
  After using this commands:
  sudo aa-complain/usr/bin/evince
  sudo aa-complain/usr/bin/evince-previewer
  sudo aa-complain/usr/bin/evince-thumbnailer

  I was able to open Evince again and this is the log of syslog:

  Aug  4 16:41:14 e01a27166 kernel: [ 3292.825954] audit: type=1400 
audit(1501882874.732:100): apparmor="ALLOWED" operation="mknod" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.825957] audit: type=1400 
audit(1501882874.732:101): apparmor="ALLOWED" operation="open" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="wrc" denied_mask="wrc" fsuid=1000 
ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.825958] audit: type=1400 
audit(1501882874.732:102): apparmor="ALLOWED" operation="unlink" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="d" denied_mask="d" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.826148] audit: type=1400 
audit(1501882874.732:103): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.826208] audit: type=1400 
audit(1501882874.732:104): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.827153] audit: type=1400 
audit(1501882874.732:105): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  Aug  4 16:41:14 e01a27166 kernel: [ 3292.827185] audit: type=1400 
audit(1501882874.732:106): apparmor="ALLOWED" operation="truncate" 
profile="/usr/bin/evince" name="/run/user/1000/wayland-cursor-shared-bPXPw9" 
pid=6463 comm="evince" requested_mask="w" denied_mask="w" fsuid=1000 

[Desktop-packages] [Bug 1719324] Re: 'Set date automatically' doesn't work

[Sebastien Bacher]

Thank you for your bug report, could you check in the privacy setting it
you allow location sharing?

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

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

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

Title:
  'Set date automatically' doesn't work

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

Bug description:
  I'm travelling from France to US (NYC) The date is set to 'update
  automatically' but the time is still France time, even after a reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 15:59:03 2017
  InstallationDate: Installed on 2013-09-03 (1482 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   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)

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Gunnar Hjalmarsson]

No problem from a docs POV. Unfortunately we hadn't the time to include
Ubuntu specific screenshots this cycle.

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Sebastien Bacher]

** Patch added: "the code change"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719668/+attachment/4957318/+files/gcc.diff

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719458] Re: "Add a color profile" window is too small

[Sebastien Bacher]

Right, I noticed that as well some days ago and got a fix commited
upstream which we are going to get with 3.26.1

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

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

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

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=787931
   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/1719458

Title:
  "Add a color profile" window is too small

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  In gnome-control-center the dialog that lists the profiles available
  when adding a color profile is too small (1 line height) cf screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 25 17:12:23 2017
  InstallationDate: Installed on 2013-09-03 (1483 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   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)

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Didier Roche]

After a quick review, the code looks good to me.

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Sebastien Bacher]

** Attachment added: "screenshot before change"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719668/+attachment/4957316/+files/gccbefore.png

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719668] Re: UIFe, white backgound for list

[Sebastien Bacher]

** Attachment added: "screenshot after change"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1719668/+attachment/4957317/+files/gccafter.png

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1719668] [NEW] UIFe, white backgound for list

[Sebastien Bacher]

Public bug reported:

Upstream stated that it's the way it should be so it's somewhat a bug
fix in our theme, it also improves readability

The theme should be updated but we don't want to land changes that could
impact other softwares that late in the cycle so we propose doing it as
a g-c-c patch for artful and update the theme next cycle

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

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

Title:
  UIFe, white backgound for list

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

Bug description:
  Upstream stated that it's the way it should be so it's somewhat a bug
  fix in our theme, it also improves readability

  The theme should be updated but we don't want to land changes that
  could impact other softwares that late in the cycle so we propose
  doing it as a g-c-c patch for artful and update the theme next cycle

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

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

[Desktop-packages] [Bug 1385674] Re: "Shared to other computers" Method missing from "Addresses"

[David Lechner]

I assume the patch tag was removed because it has bitrotted?

I have submitted a new patch recently upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=696793

I would really like to see this in 18.04 one way or another. I'm not too
keen on another two years of "ALT+F2 nm-connection-editor" to be able to
use this setting.

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

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

Title:
  "Shared to other computers" Method missing from "Addresses"

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

Bug description:
  As described, the "Shared to other computers" option is missing from
  "Addresses" dropbox.

  In the attached screenshot, on the left we see the "Network" GUI and on the 
right we see the "Network Connections" GUI.
  As this option is only accessible through the "Network Connections" GUI, we 
see that the option is not accessible in the "Network" GUI and is blank.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-05-23 (160 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  NonfreeKernelModules: nvidia
  Package: gnome-control-center 1:3.12.1-5ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Tags:  utopic
  Uname: Linux 3.16.0-24-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (5 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1719572] Re: chromedriver can't click links outside of the window with Chromium 61

[Olivier Tilloy]

Relevant commits appear to be
https://chromium.googlesource.com/chromium/src/+/dac98ec90b237d6786e2a508d1e74a2d4012ff33
and
https://chromium.googlesource.com/chromium/src/+/8a2bcc815371466a141910a09f7d844c00a09887,
but they haven't been backported to the 61 branch, as far as I can tell.

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

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  chromedriver can't click links outside of the window with Chromium 61

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  The latest version of chromium (61) introduces a change that breaks the 
ability of clicking to links outside of the current view using chromedriver.
  It seems that there is a fix for it in chromedriver 2.32:
  > Fixes a bug where Chromedriver fails to click due to page scrolling changes 
in Chrome 61+.

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

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