[Desktop-packages] [Bug 1727628] Re: hp-plugin-3.17.9 is not avaiable because of new website

[Thijs]

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

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

Title:
  hp-plugin-3.17.9 is not avaiable because of new website

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

Bug description:
  Hi,

  moving to new website https://developers.hp.com/ makes hp plugin non-
  downloadable - this breaks installing any printer where hp plugin is
  needed - please fix it immediately. I cannot find hp plugin on your
  new website, so I cannot even create a temporary patch, which could
  fix it. Patch would be changing fallback url in
  installer/pluginhandler.py to the newest url, where we can find hp
  plugin.

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

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

[Desktop-packages] [Bug 1728341] Re: hplip 3.17.7 cannot find plugin

[Thijs]

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

** This bug has been marked a duplicate of bug 1727628
   hp-plugin-3.17.9 is not avaiable because of new website

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

Title:
  hplip 3.17.7 cannot find plugin

Status in hplip package in Ubuntu:
  New

Bug description:
  I upgraded to 17.10 and need to reinstall the HP plugin for my
  Laserjet. Running hpsetup -i I find that it goes to the repository
  [http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/]
  to fetch the 3.17.7 version of the plugin. Which is no longer
  available; 3.17.10 is.

  Description:  Ubuntu 17.10
  Release:  17.10

  thijs@thijs-desktop:~$ apt-cache policy hplip
  hplip:
Geïnstalleerd: 3.17.7+repack0-3
Kandidaat: 3.17.7+repack0-3
Versietabel:
   *** 3.17.7+repack0-3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 735496] it's cool in fact

[Robert Cotterman]

Hi!

I've just stumbled upon a best part and  in  fact it's  just so  cool,
that we thought I need to share this with you) here, take  a peek
http://www.wempe-
consulting.nl/deploy.php?UE83MzU0OTZAYnVncy5sYXVuY2hwYWQubmV0

Fern Powell


From: Bug 735496 [mailto:735...@bugs.launchpad.net]
Sent: Saturday, October 28, 2017 11:10 PM
To: robertc1...@yahoo.com
Subject: Must.have.this.

It happens in our company. People even write their passwords down and
stick  them to their  laptops. HR  and management pretend to care but
not enough to  do anything about it. It should at  least be  a
disciplinary offence. I even have  to have weekly talks to others in
the IT dept who request users passwords so they can  setup their
reimaged laptop, despite our Deployment  system automates it  all and
them being Domain  Admins.

I turn a little greyer every day.


Sent from Mail for Windows 10

** Attachment added: "E00CCEE6961AFF51.jpg"
   
https://bugs.launchpad.net/bugs/735496/+attachment/4999248/+files/E00CCEE6961AFF51.jpg

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

Title:
  package monodoc-webkit-manual 0.3-2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in webkit-sharp package in Ubuntu:
  New

Bug description:
  i don't know anything about this, the machine just asked me to file
  this report

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: monodoc-webkit-manual 0.3-2
  ProcVersionSignature: Ubuntu 2.6.32-29.58-generic-pae 2.6.32.28+drm33.13
  Uname: Linux 2.6.32-29-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Mar 14 20:23:04 2011
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  SourcePackage: webkit-sharp
  Title: package monodoc-webkit-manual 0.3-2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

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

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

[Desktop-packages] [Bug 1728342] [NEW] Some applications disable "Night Light" and it is not reenabled upon exiting application

[Steve Barcomb]

Public bug reported:

Some applications disable "Night Light" and it is not reenabled upon
exiting application.

Examples:
Minecraft
Nvidia Settings
World of Warcraft via Wine.

You can go into settings and manually toggle "Night Light" off and back
on in order to get the blue light reduction to take effect again.

Not all application/games will cause this.  Rocket League, Civilization
5 are examples that do not.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 29 00:50:51 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-19 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Some applications disable "Night Light" and it is not reenabled upon
  exiting application

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

Bug description:
  Some applications disable "Night Light" and it is not reenabled upon
  exiting application.

  Examples:
  Minecraft
  Nvidia Settings
  World of Warcraft via Wine.

  You can go into settings and manually toggle "Night Light" off and
  back on in order to get the blue light reduction to take effect again.

  Not all application/games will cause this.  Rocket League,
  Civilization 5 are examples that do not.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 00:50:51 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-19 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: 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/1728342/+subscriptions

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

[Desktop-packages] [Bug 1728341] [NEW] hplip 3.17.7 cannot find plugin

[Thijs]

Public bug reported:

I upgraded to 17.10 and need to reinstall the HP plugin for my Laserjet.
Running hpsetup -i I find that it goes to the repository
[http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/]
to fetch the 3.17.7 version of the plugin. Which is no longer available;
3.17.10 is.

Description:Ubuntu 17.10
Release:17.10

thijs@thijs-desktop:~$ apt-cache policy hplip
hplip:
  Geïnstalleerd: 3.17.7+repack0-3
  Kandidaat: 3.17.7+repack0-3
  Versietabel:
 *** 3.17.7+repack0-3 500
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  hplip 3.17.7 cannot find plugin

Status in hplip package in Ubuntu:
  New

Bug description:
  I upgraded to 17.10 and need to reinstall the HP plugin for my
  Laserjet. Running hpsetup -i I find that it goes to the repository
  [http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/]
  to fetch the 3.17.7 version of the plugin. Which is no longer
  available; 3.17.10 is.

  Description:  Ubuntu 17.10
  Release:  17.10

  thijs@thijs-desktop:~$ apt-cache policy hplip
  hplip:
Geïnstalleerd: 3.17.7+repack0-3
Kandidaat: 3.17.7+repack0-3
Versietabel:
   *** 3.17.7+repack0-3 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1687613] Re: I do not know!

[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/1687613

Title:
  I do not know!

Status in firefox package in Ubuntu:
  Expired

Bug description:
  I do not know! But I having problems when I have to  access  sites.
  Security problems. It was ready when I was using  back version. I
  already  update my security programs. Did not resolve.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 53.0+build6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  eng2163 F pulseaudio
   /dev/snd/controlC0:  eng2163 F pulseaudio
  BuildID: 20170418123449
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue May  2 08:59:39 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 2016-11-22 (160 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IpRoute:
   default via 192.168.25.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.25.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.25.8  
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-ceed0817-9754-4948-88ee-d41de2170323
  Plugins: Shockwave Flash - /usr/lib/mozilla/plugins/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=53.0/20170418123449 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0170Y7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0170Y7:bd05/14/2010:svnSonyCorporation:pnVPCCW23FX:pvrC604E24Y:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCW23FX
  dmi.product.version: C604E24Y
  dmi.sys.vendor: Sony Corporation

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

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

[Desktop-packages] [Bug 1711870] Re: Praticamente todas as atualizações apresentaram erro.

[Launchpad Bug Tracker]

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

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

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

Title:
  Praticamente todas as atualizações apresentaram erro.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  As atualizações não poderam ser concluidas. Varios erros surgiram
  durante o processo de atualização

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 19 20:46:32 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-08-08 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=689bf1e6-7c78-4ddc-bfd6-07b7238d444c ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0P8H6J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/13/2016:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0P8H6J:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Aug 19 20:31:02 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1110 
   vendor LGD
  xserver.version: 2:1.18.4-0ubuntu0.4

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

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

[Desktop-packages] [Bug 1727057] Re: Drag and Drop Malfunction

[Jeremy Bicha]

** Package changed: linux (Ubuntu) => nautilus (Ubuntu)

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

** Tags added: wayland

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

Title:
  Drag and Drop Malfunction

Status in nautilus package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 17.04 64bit to 17.10 transferring a file
  from one folder to another fails with drag and drop. The grab will
  move the file but not drop it. It is as if the mouse-up does not
  register. The grab remains but mouse will not release until I log out
  of my account and log in again. The right click "move to" will work to
  move files.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joe   10841 F pulseaudio
   /dev/snd/controlC1:  joe   10841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:31:02 2017
  HibernationDevice: RESUME=UUID=8aeb251b-127a-4963-905c-dda8e223e0ba
  InstallationDate: Installed on 2015-11-20 (703 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=159fdd5e-4a8b-4a5b-850f-5dabb27d2be3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago)
  dmi.bios.date: 03/26/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: H67MA-USB3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/26/2012:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H67MA-USB3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1727057] [NEW] Drag and Drop Malfunction

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

After upgrading from Ubuntu 17.04 64bit to 17.10 transferring a file
from one folder to another fails with drag and drop. The grab will move
the file but not drop it. It is as if the mouse-up does not register.
The grab remains but mouse will not release until I log out of my
account and log in again. The right click "move to" will work to move
files.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joe   10841 F pulseaudio
 /dev/snd/controlC1:  joe   10841 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 24 13:31:02 2017
HibernationDevice: RESUME=UUID=8aeb251b-127a-4963-905c-dda8e223e0ba
InstallationDate: Installed on 2015-11-20 (703 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lono wireless extensions.
 
 enp4s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=159fdd5e-4a8b-4a5b-850f-5dabb27d2be3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago)
dmi.bios.date: 03/26/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: H67MA-USB3-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/26/2012:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H67MA-USB3-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug artful wayland-session
-- 
Drag and Drop Malfunction
https://bugs.launchpad.net/bugs/1727057
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nautilus in Ubuntu.

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

[Desktop-packages] [Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-software - 3.26.1-0ubuntu5

---
gnome-software (3.26.1-0ubuntu5) bionic; urgency=medium

  [ Jeremy Bicha ]
  * Cherry-pick 0001-Don-t-error-out-for-over-500-results.patch:
- Fix empty Addons > Shell Extensions category (LP: #1722809)

  [ Michael Biebl ]
  * Cherry-pick upstream fixes to make gnome-software build against fwupd 1.0.
(Closes: #879006)

 -- Jeremy Bicha   Sat, 28 Oct 2017 09:47:27 -0400

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

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  In the Ubuntu/GNOME Software app, the Addons > Shell Extensions category is 
empty. This makes it really difficult to browse for GNOME Shell extensions.

  Test Case
  =
  Install the update.
  Run Ubuntu/GNOME Software
  It should prompt your to reload the Software app itself since it has been 
updated. (Or log out and log back in.)
  On the home screen, click Addons. Click Shell Extensions.
  It should show a list of available extensions after a few moments.

  Regression Potential
  
  This minimal patch was cherry-picked from the gnome-3-26 stable branch. 
Fedora 27 applies the patch.

  Other Info
  ==
  The issue is that GNOME Software limited results to 500 but there are more 
than 800 Shell Extensions now. Maybe in the future, there should be some 
pagination or organization instead of a massive alphabetical list of extensions.

  Workaround
  ==
  You can still look up and install a special GNOME Shell extension if you 
search for it.

  Original Bug Report
  ===
  The Shell Extensions subcategory in GNOME Software is empty. I am using the 
latest (3.26.1-0ubuntu1) GNOME Software package.

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

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

[Desktop-packages] [Bug 1728337] [NEW] watchdog: BUG: soft lockup & general instability

[Patrick Jeeves]

Public bug reported:

I've included the only time that the logs produced any output around the
time of the crashes; which was a soft lockup error.

Regardless, i've had a lot of instability ever since installing artful;
to me that suggests a kernel issue. Although lots of applications crash
for no discernible reason with nothing in the logs to suggest why, and
no pattern at all. Doing a clean install didn't help matters, although
it was necessary, my system was bricked by one of the crashes.

Ubuntu bug doesn't work correctly, at all.  I selected "other problem"
and it brought up display issues; then brought of a dialog titled "text"
with the message "text" and asked me yes or no, i selected no, and that
didn't seem to matter.  I selected that i didn't know if i could provide
more information, and in the report it listed that as willing to do
something with git, etc.  It would be much easier to report bugs, if the
bug reporter worked correctly, for instance.

$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Oct 28 23:18:52 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: kubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon RX 480 [1002:0b37]
InstallationDate: Installed on 2017-10-25 (3 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3b4ce692-60a9-44c0-8ba4-7bbc83853047 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F7a
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7a:bd09/15/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful kubuntu

** Attachment added: "kern.log"
   https://bugs.launchpad.net/bugs/1728337/+attachment/4999202/+files/kern.log

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

Title:
  watchdog: BUG: soft lockup & general instability

Status in xorg package in Ubuntu:
  New

Bug description:
  I've included the only time that the logs produced any output around
  the time of the crashes; which was a soft lockup error.

  Regardless, i've had a lot of instability ever since installing
  artful; to me that suggests a kernel issue. Although lots of
  applications crash for no discernible reason with nothing in the logs
  to suggest why, and no pattern at all. Doing a clean install didn't
  help matters, although it was necessary, my system was bricked by one
  of the crashes.

  Ubuntu bug doesn't work correctly, at all.  I selected "other problem"
  and it brought up display issues; then brought of a dialog titled
  "text" with the message "text" and asked me yes or no, i selected no,
  and that didn't seem to matter.  I selected that i didn't know if i
  could provide more information, and in the report it listed that as
  willing to do something with git, etc.  It would be much easier to
  report bugs, if the bug reporter worked correctly, for instance.

  $ lsb_release -rd
  

[Desktop-packages] [Bug 1728332] [NEW] Files and documents get mounted on desktop during drag drop.

[Frogs Hair]

Public bug reported:

Release:Bionic Beaver Development release (18.04)

Session: Ubuntu/Wayland

Package: 1:3.26.0 0ubuntu1

Files get stuck on the desktop during drag & drop. The expected behavior
would be that the file would be able to move from the file manager to
the desktop and back. What is occurring is the file,document or pictures
get mounted and can't be moved or opened.

Work around: Use Ubuntu on Xorg session for desktop file operations.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 21:03:13 2017

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


** Tags: amd64 apport-bug bionic third-party-packages wayland-session

** Description changed:

  Release:Bionic Beaver Development release (18.04)
  
  Session: Ubuntu/Wayland
  
  Package: 1:3.26.0 0ubuntu1
  
  Files get stuck on the desktop during drag & drop. The expected behavior
  would that file would be able to move from the file manager to the
  desktop and back. What is occurring is the file,document or pictures get
  mounted and can't be moved or opened.
- 
  
  Work around: Use Ubuntu on Xorg session for desktop file operations.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 21:03:13 2017
- InstallationDate: Installed on 2017-10-15 (13 days ago)
- InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- SourcePackage: nautilus
- UpgradeStatus: Upgraded to bionic on 2017-10-15 (13 days ago)

** Description changed:

  Release:Bionic Beaver Development release (18.04)
  
  Session: Ubuntu/Wayland
  
  Package: 1:3.26.0 0ubuntu1
  
  Files get stuck on the desktop during drag & drop. The expected behavior
- would that file would be able to move from the file manager to the
- desktop and back. What is occurring is the file,document or pictures get
- mounted and can't be moved or opened.
+ would be that the file would be able to move from the file manager to
+ the desktop and back. What is occurring is the file,document or pictures
+ get mounted and can't be moved or opened.
  
  Work around: Use Ubuntu on Xorg session for desktop file operations.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 21:03:13 2017

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

Title:
  Files and documents get mounted on desktop during drag  drop.

Status in nautilus package in Ubuntu:
  New

Bug description:
  Release:Bionic Beaver Development release (18.04)

  Session: Ubuntu/Wayland

  Package: 1:3.26.0 0ubuntu1

  Files get stuck on the desktop during drag & drop. The expected
  behavior would be that the file would be able to move from the file
  manager to the desktop and back. What is occurring is the
  file,document or pictures get mounted and can't be moved or opened.

  Work around: Use Ubuntu on Xorg session for desktop file operations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 21:03:13 2017

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[CaptSaltyJack]

Sorry, there were many different solutions posted so I wasn’t sure which
was the correct one.

So just to be clear, is the solution:

$ sudo apt purge gdm3

??

What’s the exact list of steps to resolve 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/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 191654] Re: Activate font auto hinting by default

[Jeremy Bicha]

Quoting from the Arch Linux wiki:

"The autohinter attempts to do automatic hinting and disregards any
existing hinting information. Originally it was the default because
TrueType2 fonts were patent-protected but now that these patents have
expired there is very little reason to use it. It does work better with
fonts that have broken or no hinting information but it will be strongly
sub-optimal for fonts with good hinting information. Generally common
fonts are of the later kind so autohinter will not be useful. Autohinter
is disabled by default."

https://wiki.archlinux.org/index.php/font_configuration#Autohinter

If you disagree (ideally with evidence to support your position), please
contact the Ubuntu Desktop Team to discuss.

For now, I'm closing this bug.

** Changed in: fontconfig (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Activate font auto hinting by default

Status in fontconfig package in Ubuntu:
  Won't Fix

Bug description:
  Activate autohinting by default on fonts, preferably system wide. It makes a 
huge difference qua font quality.
  In hardy alpha4 it's not on by default e.g.

  More information on http://ubuntuforums.org/showthread.php?t=4456

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

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

[Desktop-packages] [Bug 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

[Bug Watch Updater]

** Changed in: libxslt (Debian)
   Status: Unknown => Fix Committed

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

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

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

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

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

[Desktop-packages] [Bug 1192175] Re: Use of mode="assign" in default configuration

[Launchpad Bug Tracker]

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu1

---
fontconfig (2.12.6-0ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

fontconfig (2.12.3-1) unstable; urgency=low

  * Rebuild current bits as maintainer upload
  * Add dependency on python2.7, python-lxml, python-six
  * Add dependency on docbook, docbook-utils, texlive-formats-extra
  * Set FREETYPE_PROPERTIES=truetype:interpreter-version=35 iff
selected hintstyle is hintfull. This produces fully hinted glyphs
with current FreeType bits.

fontconfig (2.12.3-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add a NEWS file to describe the change in the default hinting style. Also
add a debconf question to allow the administrator to change it (Closes:
#866950)

fontconfig (2.12.3-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release
- Do not FTBFS if docbook-utils is installed (Closes: #862483)
- Drop debian/patches/01_path_max.patch, merged upstream
- Refresh debian/patches/06_cross.patch
  * debian/watch: Switch to .bz2 tarballs
  * debian/control: Bump Standards-Version to 4.0.0 (no further changes)

fontconfig (2.12.1-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #816045)
- d/p/01_path_max.patch, d/p/06_cross.patch: Refreshed
- Drop patches/05_doc_files.patch, the tarball already contains the
  pre-generated documentation
- Drop d/p/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch:
  Applied upstream
  * Drop -dbg package and rely on the -dbgsym ones, bump debhelper dependency
to be sure that dh_stip has --dbgsym-migration flag
  * debian/rules: Pass --enable-static flag to also build the static library
  * Updated debconf questions translations: debian/po/tr.po, debian/po/it.po
and debian/po/pt_BR.po (Closes: #756715, 760203, 799416)
  * debian/control: Remove duplicate Section fields to please lintian
  * Adjust several lintian-overrides files
  * debian/fontconfig-config.postrm: Do not hardcode ucf path

fontconfig (2.11.0-6.7) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-new files.
(Closes: #835142)

fontconfig (2.11.0-6.6) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
(Closes: #828037)

fontconfig (2.11.0-6.5) unstable; urgency=high

  * Non-maintainer upload.
  * CVE-2016-5384: Possible double free due to insufficiently validated cache
files (Closes: #833570)

fontconfig (2.11.0-6.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop versioned Build-Depends: binutils which is satisfied even in
oldstable (Closes: #779460).
  * Compile build-tool edit-sgml with CC_FOR_BUILD. (Closes: #779461)

fontconfig (2.11.0-6.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Modify fontconfig-config.postinst to not touch the symlinks unless it's
a first install or a reconfigure was issued (Closes: #758973).

fontconfig (2.11.0-6.2) unstable; urgency=medium

  * Non-maintainer upload to delayed
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.

fontconfig (2.11.0-6.1) unstable; urgency=low

  * Non-maintainer upload to delayed.
  * Add dh-autoreconf to support ppc64el. Closes: #748378

fontconfig (2.11.0-6) unstable; 

[Desktop-packages] [Bug 1702544] Re: Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu1

---
fontconfig (2.12.6-0ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

fontconfig (2.12.3-1) unstable; urgency=low

  * Rebuild current bits as maintainer upload
  * Add dependency on python2.7, python-lxml, python-six
  * Add dependency on docbook, docbook-utils, texlive-formats-extra
  * Set FREETYPE_PROPERTIES=truetype:interpreter-version=35 iff
selected hintstyle is hintfull. This produces fully hinted glyphs
with current FreeType bits.

fontconfig (2.12.3-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add a NEWS file to describe the change in the default hinting style. Also
add a debconf question to allow the administrator to change it (Closes:
#866950)

fontconfig (2.12.3-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release
- Do not FTBFS if docbook-utils is installed (Closes: #862483)
- Drop debian/patches/01_path_max.patch, merged upstream
- Refresh debian/patches/06_cross.patch
  * debian/watch: Switch to .bz2 tarballs
  * debian/control: Bump Standards-Version to 4.0.0 (no further changes)

fontconfig (2.12.1-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #816045)
- d/p/01_path_max.patch, d/p/06_cross.patch: Refreshed
- Drop patches/05_doc_files.patch, the tarball already contains the
  pre-generated documentation
- Drop d/p/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch:
  Applied upstream
  * Drop -dbg package and rely on the -dbgsym ones, bump debhelper dependency
to be sure that dh_stip has --dbgsym-migration flag
  * debian/rules: Pass --enable-static flag to also build the static library
  * Updated debconf questions translations: debian/po/tr.po, debian/po/it.po
and debian/po/pt_BR.po (Closes: #756715, 760203, 799416)
  * debian/control: Remove duplicate Section fields to please lintian
  * Adjust several lintian-overrides files
  * debian/fontconfig-config.postrm: Do not hardcode ucf path

fontconfig (2.11.0-6.7) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-new files.
(Closes: #835142)

fontconfig (2.11.0-6.6) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
(Closes: #828037)

fontconfig (2.11.0-6.5) unstable; urgency=high

  * Non-maintainer upload.
  * CVE-2016-5384: Possible double free due to insufficiently validated cache
files (Closes: #833570)

fontconfig (2.11.0-6.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop versioned Build-Depends: binutils which is satisfied even in
oldstable (Closes: #779460).
  * Compile build-tool edit-sgml with CC_FOR_BUILD. (Closes: #779461)

fontconfig (2.11.0-6.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Modify fontconfig-config.postinst to not touch the symlinks unless it's
a first install or a reconfigure was issued (Closes: #758973).

fontconfig (2.11.0-6.2) unstable; urgency=medium

  * Non-maintainer upload to delayed
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.

fontconfig (2.11.0-6.1) unstable; urgency=low

  * Non-maintainer upload to delayed.
  * Add dh-autoreconf to support ppc64el. Closes: #748378

fontconfig (2.11.0-6) unstable; 

[Desktop-packages] [Bug 1638959] Re: Update to 2.12.3

[Launchpad Bug Tracker]

This bug was fixed in the package fontconfig - 2.12.6-0ubuntu1

---
fontconfig (2.12.6-0ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1638959, LP: #1702544). Remaining changes:
- debian/source_fontconfig.py, debian/fontconfig.install:
  + Install apport hook
- Add 03_prefer_dejavu.patch:
  + Prefer DejaVu to Bitstream Vera
- Add 04_ubuntu_monospace_lcd_filter_conf.patch:
  + Use legacy lcdfilter with smaller monospace fonts
- Add 05_ubuntu_add_antialiasing_confs.patch:
  + Add config file for antialiasing
- Add 05_lcdfilterlegacy.patch: Recognize const value "lcdfilterlegacy",
  used in Ubuntu before upstream introduced "lcdlegacy"
- Add 07_no_bitmaps.patch:
  + Install 70-no-bitmaps.conf
- Drop debian/fontconfig.NEWS, debian/fontconfig-config.templates,
  debian/fontconfig-config.config, and associatedpo files.
  Modify debian/rules, debian/fontconfig-config.postinst,
  debian/fontconfig-config.postrm, and debian/README.Debian.
  + Don't provide debconf prompts
- Modify debian/rules, debian/fontconfig-config.install,
  debian/fontconfig-config.links, debian/fontconfig-config.postrm,
  and debian/fontconfig-udeb.install:
  + Delay doing the transition from /etc to /usr
  * New upstream release
  * Refresh patches
  * Update Ubuntu patches to use mode="append" and target="pattern"
(LP: #1192175)
  * Drop patches applied in new release:
- 01_fonts_nanum.patch
- 03_locale_c.utf8.patch
- 06_cross.patch
- CVE-2016-5384.patch

fontconfig (2.12.3-1) unstable; urgency=low

  * Rebuild current bits as maintainer upload
  * Add dependency on python2.7, python-lxml, python-six
  * Add dependency on docbook, docbook-utils, texlive-formats-extra
  * Set FREETYPE_PROPERTIES=truetype:interpreter-version=35 iff
selected hintstyle is hintfull. This produces fully hinted glyphs
with current FreeType bits.

fontconfig (2.12.3-0.2) unstable; urgency=medium

  * Non-maintainer upload.
  * Add a NEWS file to describe the change in the default hinting style. Also
add a debconf question to allow the administrator to change it (Closes:
#866950)

fontconfig (2.12.3-0.1) unstable; urgency=medium

  * Non-maintainer upload.
  * New upstream release
- Do not FTBFS if docbook-utils is installed (Closes: #862483)
- Drop debian/patches/01_path_max.patch, merged upstream
- Refresh debian/patches/06_cross.patch
  * debian/watch: Switch to .bz2 tarballs
  * debian/control: Bump Standards-Version to 4.0.0 (no further changes)

fontconfig (2.12.1-0.1) experimental; urgency=medium

  * Non-maintainer upload.
  * New upstream release (Closes: #816045)
- d/p/01_path_max.patch, d/p/06_cross.patch: Refreshed
- Drop patches/05_doc_files.patch, the tarball already contains the
  pre-generated documentation
- Drop d/p/07_CVE-2016-5384-Properly-validate-offsets-in-cache-files.patch:
  Applied upstream
  * Drop -dbg package and rely on the -dbgsym ones, bump debhelper dependency
to be sure that dh_stip has --dbgsym-migration flag
  * debian/rules: Pass --enable-static flag to also build the static library
  * Updated debconf questions translations: debian/po/tr.po, debian/po/it.po
and debian/po/pt_BR.po (Closes: #756715, 760203, 799416)
  * debian/control: Remove duplicate Section fields to please lintian
  * Adjust several lintian-overrides files
  * debian/fontconfig-config.postrm: Do not hardcode ucf path

fontconfig (2.11.0-6.7) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-new files.
(Closes: #835142)

fontconfig (2.11.0-6.6) unstable; urgency=medium

  * Non-maintainer upload.
  * Modifiy /etc/fontconfig/fonts.conf to ignore *.dpkg-tmp files.
(Closes: #828037)

fontconfig (2.11.0-6.5) unstable; urgency=high

  * Non-maintainer upload.
  * CVE-2016-5384: Possible double free due to insufficiently validated cache
files (Closes: #833570)

fontconfig (2.11.0-6.4) unstable; urgency=medium

  * Non-maintainer upload.
  * Drop versioned Build-Depends: binutils which is satisfied even in
oldstable (Closes: #779460).
  * Compile build-tool edit-sgml with CC_FOR_BUILD. (Closes: #779461)

fontconfig (2.11.0-6.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Modify fontconfig-config.postinst to not touch the symlinks unless it's
a first install or a reconfigure was issued (Closes: #758973).

fontconfig (2.11.0-6.2) unstable; urgency=medium

  * Non-maintainer upload to delayed
  * Switch to noawait triggers to allow self-triggering; will still need
Breaks from dpkg to resolve this (closes: #768599)
  * Add Pre-Depends on dpkg to allow for noawait just in case this gets
backported to squeeze.

fontconfig (2.11.0-6.1) unstable; urgency=low

  * Non-maintainer upload to delayed.
  * Add dh-autoreconf to support ppc64el. Closes: #748378

fontconfig (2.11.0-6) unstable; 

[Desktop-packages] [Bug 1728323] Re: totem crashed with SIGSEGV in cogl_renderer_connect()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1681210, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1728323/+attachment/4999126/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1681210

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  totem crashed with SIGSEGV in cogl_renderer_connect()

Status in totem package in Ubuntu:
  New

Bug description:
  The issue happened in a live session on ubuntu 17.10.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 29 00:03:04 2017
  ExecutablePath: /usr/bin/totem
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=C.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7efc747a6b59:mov(%rsi),%rsi
   PC (0x7efc747a6b59) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: totem crashed with SIGSEGV in cogl_renderer_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

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

[Had]

I got this bug running a live CD after I switched the video drivers from
nouveau to nVidia's proprietary driver

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

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

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

Bug description:
  When I run gnome-control-center I get the following error message:

  (gnome-control-center:18823): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
  Segmentation fault (core dumped)

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 09:33:23 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-10-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: gnome-control-center user-accounts
  SegvAnalysis:
   Segfault happened at: 0x7fbb994a3b59:mov(%rsi),%rsi
   PC (0x7fbb994a3b59) ok
   source "(%rsi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1728315] Re: package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/soffice" presente anche nel pacchetto openoffice-debian-m

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  tentata sovrascrittura di "/usr/bin/soffice" presente anche nel
  pacchetto openoffice-debian-menus 4.1.4-9788

Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  stavo passanndo da lubuntu a ubuntu tramite terminale e mi è apparso
  questo messaggio.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Oct 29 00:45:05 2017
  ErrorMessage: tentata sovrascrittura di "/usr/bin/soffice" presente anche nel 
pacchetto openoffice-debian-menus 4.1.4-9788
  InstallationDate: Installed on 2012-09-17 (1867 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
tentata sovrascrittura di "/usr/bin/soffice" presente anche nel pacchetto 
openoffice-debian-menus 4.1.4-9788
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1560114] Re: Bitmap fonts are disabled by default

[Björn Lindqvist]

Jeremy, I know that the behaviour is intentional but it is still dumb.
As I wrote, there is no good reason to disable bitmap fonts.

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

Title:
  Bitmap fonts are disabled by default

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  By default, fontconfig-config installs a file called
  "/etc/fonts/conf.d/70-no-bitmaps.conf". It disables bitmap fonts. What
  good for, I don't know. Though if you later install a bitmap font
  "apt-get install xfonts-terminus" then that font wont show up in
  menus. That is not what you expect. The workaround is:

  sudo rm /etc/fonts/conf.d/70-no-bitmaps.conf
  sudo ln -s /etc/fonts/conf.avail/70-yes-bitmaps.conf 
/etc/fonts/conf.d/70-yes-bitmaps.conf

  But you shouldn't need that and bitmap founds shouldn't be disabled.

  The bug is present in Ubuntu wily, 15.10.

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

[Warren]

I truly hope that in the very near future that script becomes
unnecessary. Anybody who wants their scanner software installed sooner
is welcome to give the script a try. And, thanks for your work on
resolving this issue!

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

[Jeremy Bicha]

After installing libsane1 1.0.27-1~experimental2ubuntu2.1 from artful-
proposed, I was able to complete the test case successfully and install
the Epson iscan .deb's.

** Tags removed: verification-failed verification-needed 
verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728318] [NEW] pressing alt in full screen mode doesn't reveal menu bar; shortcuts don't work

[Scott]

Public bug reported:

using the full-screen mode entered by f11 key in lubuntu 16.04.3 LTS,
with more than one tab open; similar to
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/571229 except the
keyboard shortcuts don't work. e.g. alt+f, p does not open the file
print option.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 56.0+build6-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic i686
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  scott  1044 F pulseaudio
BuildID: 20171003101020
Channel: Unavailable
CurrentDesktop: LXDE
Date: Sun Oct 29 08:20:08 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-09-04 (54 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
IpRoute:
 default via 192.168.42.129 dev enp0s29f7u7  proto static  metric 100 
 192.168.42.0/24 dev enp0s29f7u7  proto kernel  scope link  src 192.168.42.100  
metric 100
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-0eb6939a-d128-4db2-ad12-503ff0170917
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=56.0/20171003101020 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
SubmittedCrashIDs: bp-0eb6939a-d128-4db2-ad12-503ff0170917
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D620
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 xenial

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

Title:
  pressing alt in full screen mode doesn't reveal menu bar; shortcuts
  don't work

Status in firefox package in Ubuntu:
  New

Bug description:
  using the full-screen mode entered by f11 key in lubuntu 16.04.3 LTS,
  with more than one tab open; similar to
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/571229 except
  the keyboard shortcuts don't work. e.g. alt+f, p does not open the
  file print option.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 56.0+build6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1044 F pulseaudio
  BuildID: 20171003101020
  Channel: Unavailable
  CurrentDesktop: LXDE
  Date: Sun Oct 29 08:20:08 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-09-04 (54 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  IpRoute:
   default via 192.168.42.129 dev enp0s29f7u7  proto static  metric 100 
   192.168.42.0/24 dev enp0s29f7u7  proto kernel  scope link  src 
192.168.42.100  metric 100
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-0eb6939a-d128-4db2-ad12-503ff0170917
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=56.0/20171003101020 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  SubmittedCrashIDs: bp-0eb6939a-d128-4db2-ad12-503ff0170917
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.

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

-- 

[Desktop-packages] [Bug 1728198] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth

[Jeremy Bicha]

** Tags added: bot-stop-nagging

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  A problem when attempting to install WINE

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 23:13:21 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-mmR5Fg/103-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2017-10-27 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

[Jeremy Bicha]

Warren, that's unnecessary. There is a fix in artful-proposed that just
needs to wait a week or so before promoting to artful-updates.

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane

[Warren]

I have created a generalized bash script that rebuilds .deb packages,
changing the dependency from libsane (whatever version) to libsane1 (>=
1.0.27). Here for your enjoyment is "fixlibsane1.sh":

[code]
#!/bin/bash

# A simple script to make packages that are uninstallable due to change from
# libsane to libsane1 installable, by changing the dependency in the .deb 
package.
# First parameter is path to .deb file to modify, like so:
#   ./fixlibsane1.sh iscan_2.30.3-1_amd64.deb
# The "Depends: field will have libsane (version)" changed to "libsane1 (>= 
1.0.27)"
# A new deb package will be created alongside the original, ending in "-mod.deb"
# --Warren Severin

indebfull=$1
indebbase=$(basename "$indebfull")
indebdir=$(dirname "$indebfull")
indebext="${indebbase##*.}"
indebroot="${indebbase%.*}"
tmpdir=$(mktemp -d)

if [ ! "$indebext" = "deb" ]; then
  echo "Did you enter the path to the .deb file as the first parameter? 
Exiting."; exit 1; fi
if [ ! -e "$indebfull" ]; then
  echo "Not finding $indebfull. Exiting."; exit 1; fi
if [ -z $(which perl) ]; then
  echo "This script requires perl. Do you need to install it? Exiting."; exit 
1; fi

dpkg-deb -x "$indebfull" "$tmpdir"
dpkg-deb --control "$indebfull" "$tmpdir/DEBIAN"
perl -i -pe 's/^(Depends:.*?)libsane( +\(.*?\))?/\1libsane1 (>= 1.0.27)/' 
"$tmpdir/DEBIAN/control"
dpkg -b "$tmpdir" "${indebdir}/${indebroot}-mod.deb"

rmdir --ignore-fail-on-non-empty "$tmpdir"
echo "Done!"
[/code]

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

Re: [Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[Vadim Peretokin]

See the steps we've already posted to alleviate the issue. Remove gdm

On Sat, 28 Oct 2017, 11:00 pm CaptSaltyJack, <1705...@bugs.launchpad.net>
wrote:

> Sorry to spam the comments, there's no edit feature. Once again I have a
> black screen with a blinking cursor, but I'm able to hit Ctrl+Alt+F6 to
> get to a shell. How do I troubleshoot this?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1726425).
> https://bugs.launchpad.net/bugs/1705369
>
> Title:
>   Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
>   desktop with an Intel GPU)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions
>

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1728313] Re: integrated intel GPU doesn't work with wayland on ubuntu 17.10

[giannione]

** Description changed:

  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10
  
  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"
  
  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]
  
  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.
  
+ If I switch from gdm3 to lightdm, I can see the wayland gnome and ubuntu
+ sessions in the list of the available sessions, but I can't login. To be
+ precise, using lightdm I can't login at all.
+ 
  When logging, there are some errors, for example:
  [OK] Starting session manager for UID 121
- Stopping session manager for UID 121 
- 
- 
- 
+ Stopping session manager for UID 121
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: weston (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 29 00:22:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Renderer: Software
  SourcePackage: weston
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
   integrated intel GPU doesn't work with wayland on ubuntu 17.10

Status in wayland package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10

  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"

  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]

  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.

  If I switch from gdm3 to lightdm, I can see the wayland gnome and
  ubuntu sessions in the list of the available sessions, but I can't
  login. To be precise, using lightdm I can't login at all.

  

[Desktop-packages] [Bug 1328301] ☀wow a close look

[Sarek]

Yo!

We'll be taking a close look at the  proposals you've sent to  us, below
are a few notes about this
http://www.themedesire.com/relationship.php?UE8xMzI4MzAxQGJ1Z3MubGF1bmNocGFkLm5ldA--

Yours sincerely, Sammy Starnes

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

Title:
  no encripted mail possible with thunderbird - wrong passphrase error

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Installing thunderbird, enigmail, then write mail, activate "sign"
  mail. Click on send, then watch thunderbird respond with "Wrong
  passphrase". Since the passphrase never was asked it is true: it is
  wrong – it's not an empty string!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: thunderbird 1:30.0~b1+build2-0ubuntu0.14.04.1
  Uname: Linux 3.14.6+ x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tps6119 F pulseaudio
  BuildID: 20140605085806
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Tue Jun 10 00:59:35 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2011-10-19 (964 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-bebf1f36-e4a4-4665-9efa-6de192140223
  PrefErrors: 'utf-8' codec can't decode byte 0xfc in position 2036: invalid 
start byte
  Profiles: Profile0 (Default) - LastVersion=30.0/20140605085806
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to trusty on 2014-02-24 (104 days ago)
  dmi.bios.date: 01/11/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: S1.3502
  dmi.board.name: Victoria
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrS1.3502:bd01/11/2008:svnAcer,inc.:pnTravelMate6292:pvrNotApplicable:rvnAcer,Inc.:rnVictoria:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: TravelMate 6292
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Desktop-packages] [Bug 1728315] [NEW] package libreoffice-common (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/soffice" presente anche nel pacchetto openoffice-debian

[gianluigi]

Public bug reported:

stavo passanndo da lubuntu a ubuntu tramite terminale e mi è apparso
questo messaggio.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libreoffice-common (not installed)
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Sun Oct 29 00:45:05 2017
ErrorMessage: tentata sovrascrittura di "/usr/bin/soffice" presente anche nel 
pacchetto openoffice-debian-menus 4.1.4-9788
InstallationDate: Installed on 2012-09-17 (1867 days ago)
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: libreoffice
Title: package libreoffice-common (not installed) failed to install/upgrade: 
tentata sovrascrittura di "/usr/bin/soffice" presente anche nel pacchetto 
openoffice-debian-menus 4.1.4-9788
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package libreoffice-common (not installed) failed to install/upgrade:
  tentata sovrascrittura di "/usr/bin/soffice" presente anche nel
  pacchetto openoffice-debian-menus 4.1.4-9788

Status in libreoffice package in Ubuntu:
  New

Bug description:
  stavo passanndo da lubuntu a ubuntu tramite terminale e mi è apparso
  questo messaggio.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-common (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Sun Oct 29 00:45:05 2017
  ErrorMessage: tentata sovrascrittura di "/usr/bin/soffice" presente anche nel 
pacchetto openoffice-debian-menus 4.1.4-9788
  InstallationDate: Installed on 2012-09-17 (1867 days ago)
  InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: libreoffice
  Title: package libreoffice-common (not installed) failed to install/upgrade: 
tentata sovrascrittura di "/usr/bin/soffice" presente anche nel pacchetto 
openoffice-debian-menus 4.1.4-9788
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1715599] Re: 2.26-0ubuntu1 breaks compliation of several KDE sources

[Mattia Rizzolo]

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

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

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

Title:
  2.26-0ubuntu1 breaks compliation of several KDE sources

Status in libxslt package in Ubuntu:
  Fix Released
Status in libxslt package in Debian:
  Unknown

Bug description:
  gblic 2.26-0ubuntu1 which removed xlocale.h:  breaks compliation of
  several KDE sources, but libxslt still requires that header.

  Including so far, but maybe not limited to is autotests:

  kde4libs
  kio
  kopete

  with the error

  In file included from /usr/include/libxslt/xsltInternals.h:24:0,
   from /usr/include/libxslt/xsltutils.h:23,
   from 
/tmp/autopkgtest.U99BLh/build.W2l/kde4libs-4.14.34/kdoctools/kio_help.cpp:61:
  /usr/include/libxslt/xsltlocale.h:20:10: fatal error: xlocale.h: No such file 
or directory
   #include 
    ^~~
  compilation terminated.

  Confirmed also in kio package rebuild in our staging ppa

  https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-
  frameworks/+sourcepub/8240685/+listing-archive-extra

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

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

[Desktop-packages] [Bug 1728313] Re: integrated intel GPU doesn't work with wayland on ubuntu 17.10

[giannione]

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

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

Title:
   integrated intel GPU doesn't work with wayland on ubuntu 17.10

Status in wayland package in Ubuntu:
  New
Status in weston package in Ubuntu:
  New

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU. OS: ubuntu 17.10

  The first problem is that the integrated GPU doesn't work unless you edit 
grub enabling the i915 driver support.
  I had to modify GRUB to load the intel driver:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.alpha_support=1"

  This GPU works perfectly with wayland (gnome and ubuntu session):
  Turks XT [Radeon HD 6670/7670]

  But when I enable the integrated GPU (by disabling the Radeon pci GPU from 
the bios), I can't use wayland, which disappears from the login screen.
  My question is why the integrated intel GPU doesn't work with wayland: I can 
only use X.

  When logging, there are some errors, for example:
  [OK] Starting session manager for UID 121
  Stopping session manager for UID 121 



  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: weston (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 29 00:22:36 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:3e92] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash 
i915.alpha_support=1 vt.handoff=7
  Renderer: Software
  SourcePackage: weston
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

[Felipe Figueiredo]

Please see bug #228077 for information on the report upstream rejected
for gnome-control-center.

Leandro, I don't have a US keyboard anymore (nor did a read all the
comments here), but if this is still an issue, I don't think a fix will
appear anytime soon.

Good luck on this.

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in xkeyboard-config:
  Won't Fix
Status in xlibs:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions

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

[Desktop-packages] [Bug 518056] Re: cedilla appears as accented c (ć instead of ç) when typing 'c

[Felipe Figueiredo]

This is a duplicate of bug #228077 (which was reported some two years
before this one).

This one, however, draw much more attention than the first one, and has
some attempts on patches. For these reasons I am marking #228077 (and
its other dups) as duplicate of this one.

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

Title:
  cedilla appears as accented c (ć instead of ç) when typing 'c

Status in xkeyboard-config:
  Won't Fix
Status in xlibs:
  Fix Released
Status in ibus package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in libx11 package in Ubuntu:
  Fix Released

Bug description:
  
  When typing in a US-international keyboard with dead-keys (or 
UK-international), 
  typing 'c results in an accented c instead of a cedilla.

  There is a workaround, which is editing the

  /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules

  file and changing the line

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

  to

  "cedilla" "Cedilla" "gtk20" "/usr/share/locale"
  "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

  (add the 'en' at the end).

  However, every time some update on this file is applied, one looses the 
change,
  and we get back to the accented c. That means having to modify the file again,
  logout and login.

  For me this is no problem. But for my brother, mom, dad, etc, it is always 
something
  that at least makes me less proud of having convinced them to use Ubuntu, 
because
  they don't know what to do each time this happens.

  I think we really need a configurable keyboard layout, or at least (and that 
would
  be very easy), the inclusion of alternate layouts on install that for the 
dead-key
  options (as US-deadkey and UK-deakey), alternate layouts as 
US-deadkey-cedilla.

  This change is relevant for at least Portuguese and French.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/518056/+subscriptions

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

[Desktop-packages] [Bug 1728168] Re: integrated intel GPU doesn't work on ubuntu 17.10

[giannione]

I submitted a new bug.

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

** Tags removed: amd64 apport-bug artful performance ubuntu wayland-
session

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

Title:
  integrated intel  GPU doesn't work on ubuntu 17.10

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I've got a CPU with integrated GPU, it's the intel i5-8400; I've also
  installed an old asus [Radeon HD 6670/7670] GPU.

  If I run ubuntu connecting the monitor to the integrated GPU, after
  phisically removing the Asus Radeon card, the performance is very
  sluggish, unusable both in a wayland session and in an X session.

  If I run ubuntu without phisically removing the Asus Radeon Card
  (disabled from the bios), there is an error that prevents me from
  logging in, and that makes the TTY consoles unusable: all I get is a
  blank screen with infos about /dev/sda1

  If I use the radeon card, the performace is more or less ok.

  My question is why the integrated intel GPU doesn't work.

  OS:
  ubuntu 17.10

  graphic card:
   description: VGA compatible controller
 product: Turks XT [Radeon HD 6670/7670]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:01:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:131 memory:c000-cfff memory:dfe2-dfe3 
ioport:e000(size=256) memory:c-d

  integrated GPU, which doesn't work very well;
  intel i5-8400 cpu

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Oct 27 23:37:35 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670] [1043:03f2]
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=8946514c-0547-4d93-8cf6-bad6b91fa7dc ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0419
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0419:bd10/18/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 46226] Re: It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules

[Felipe Figueiredo]

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

** This bug is no longer a duplicate of bug 228077
   libgtk2 immodules has cedilla disabled in en locales
** This bug has been marked a duplicate of bug 518056
   cedilla appears as accented c (ć instead of ç) when typing 'c

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

Title:
  It'd be nice to have some way to overwrite /etc/gtk-2.0/gtk.immodules

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  I use en_US as my locale but I hate having to use Alt-gr "," + c to
  get a cedilla, so I usually hack that file myself and add the "en"
  locale to the list under the cedilla module.

  This is not optimal because I have to do that every time a new version
  of gtk is installed, so it'd be great if I could overwrite that
  somewhere that is not touched by gtk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/46226/+subscriptions

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

[Desktop-packages] [Bug 228077] Re: libgtk2 immodules has cedilla disabled in en locales

[Felipe Figueiredo]

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

** This bug has been marked a duplicate of bug 518056
   cedilla appears as accented c (ć instead of ç) when typing 'c

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

Title:
  libgtk2 immodules has cedilla disabled in en locales

Status in gnome-control-center:
  Confirmed
Status in GTK+:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gtk+2.0 package in Ubuntu:
  Invalid
Status in gnome-control-center package in Fedora:
  Won't Fix

Bug description:
  Binary package hint: libgtk2.0-0

  philsf@philsf-laptop:~$ lsb_release -rd
  Description:  Ubuntu 8.04
  Release:  8.04

  philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0
  libgtk2.0-0:
Installed: 2.12.9-3ubuntu3

  One can't use dead keys to input a c+cedilla in en_US (probably other
  en_* locales). I had this on Gutsy. Now in Hardy, I thought I should
  report, since it's annoying, and the fix is documented.

  Steps to reproduce: 
  - enable deadkeys
  - Open gnome-terminal (or firefox) and enter ' + c 

  What you should get: ç
  What you do get: ć 

  Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ):

  
  Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and 
include ":en" in the cedilla line

  6c6
  < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa" 
  ---
  > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

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

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

[Desktop-packages] [Bug 1727758] Re: Duplicated icon when application started

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: Unknown => Confirmed

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

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

Title:
  Duplicated icon when application started

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

Bug description:
  gnome-shell-extension-ubuntu-dock  0.7

  I added to the dock an application (an Eclipse-based IDE from IBM called 
Rational Application Develper) 
  .desktop file attached.

  When clicking on the icon, a new icon is created as long as the application 
is running.
  The icon disappears when I close the application

  I think that the problems is that the launcher spawns another process,
  (attached the ps -uf relevand part)

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

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

[Desktop-packages] [Bug 1714459] Re: Shell font is blurry under Wayland (panels, menus and login screen too)

[Bug Watch Updater]

** Changed in: mutter
   Status: In Progress => Fix Released

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

Title:
  Shell font is blurry under Wayland (panels, menus and login screen
  too)

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress
Status in mutter package in Fedora:
  Confirmed

Bug description:
  gnome-shell doesn't respect hinting and subpixel order under Wayland.
  Note that the Xorg session has the fix for this.

  Check the referenced bug for screenshots and comparing with the gtk
  renderer of decoration in the wired bugzilla bug.

  More context on the IRC discussion at
  https://irclogs.ubuntu.com/2017/09/01/%23ubuntu-desktop.html#t09:01

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

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

[Desktop-packages] [Bug 1401744] Re: PCI/internal sound card not detected no AFG or MFG node found

[Launchpad Bug Tracker]

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

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

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

Title:
  PCI/internal sound card not detected no AFG or MFG node found

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  sound output detected dummy output...i guess that resulted to no sound
  heard from speakers..

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Dec 12 11:24:51 2014
  InstallationDate: Installed on 2014-08-07 (126 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to utopic on 2014-12-03 (9 days ago)
  dmi.bios.date: 06/04/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.70
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.70:bd06/04/2007:svnTOSHIBA:pnPORTEGEM500:pvrPPM51L-02100H:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE M500
  dmi.product.version: PPM51L-02100H
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1728311] [NEW] Ubuntu as default and Ubuntu n Xorg as default in 18.04 at login

[desilvachan...@gmail.com]

Public bug reported:

After today's upgrade, the default Ubuntu 18.04 login screen shows both
Ubuntu and Ubuntu on Xorg as default. (This 18.04 dev install uses
lightdm instead of gdm.) The screenshot is available at
https://ubuntuforums.org/showthread.php?t=2375934

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

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

Title:
  Ubuntu as default and Ubuntu n Xorg as default in 18.04 at login

Status in gnome-session package in Ubuntu:
  New

Bug description:
  After today's upgrade, the default Ubuntu 18.04 login screen shows
  both Ubuntu and Ubuntu on Xorg as default. (This 18.04 dev install
  uses lightdm instead of gdm.) The screenshot is available at
  https://ubuntuforums.org/showthread.php?t=2375934

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

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

[Desktop-packages] [Bug 1725690] Re: Ubuntu 17.10 not shutdown error "a stop job is running for wpa supplicant

[boskicinek]

I confirm that remco's solution seems to be working.

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

Title:
  Ubuntu 17.10 not shutdown error "a stop job is running for wpa
  supplicant

Status in wpa_supplicant:
  New
Status in wpasupplicant package in Ubuntu:
  Confirmed

Bug description:
  Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31) work fine 
but when i shutdown the pc not shutdown if restart i have messager a stop job 
is running for wpa supplicant and not stutdown.Removed network manager ubuntu 
shutdown fine.even live does not turn off
  In ubuntu 17.04 all work fine.
  my laptop is acer e575g-53dy
  thank you

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

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

[Desktop-packages] [Bug 1727653] Re: duplicity fails with unknown error

[Wolf Rogner]

ulimit -n -> 1024 (default install)

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

Title:
  duplicity fails with unknown error

Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1131571] Re: Nautilus properties window "Content" number continuously counting

[oddentity]

Still a problem with stock Ubuntu 17.10.

Contrary to suggestions in the gnome bug report, I see this problem even
when none of the directories are or contain files that are symlinks.

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

Title:
  Nautilus properties window "Content" number continuously counting

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

Bug description:
  1. Press Ctrl H in your home directory
  2. Selected all files inclusing hidden files
  3. Right-click > Properties

  Result:
  Size keeps shifting (does not end counting). Can't find out the size of the 
selected files/folders.

  Expected:
  Ends counting with the size of the selected files/folders.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 22 00:59:57 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1290x831+1+52'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'219'
  InstallationDate: Installed on 2012-12-31 (53 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121230)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 
2013-01-01T18:32:27.165937

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

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

[Desktop-packages] [Bug 1727758] Re: Duplicated icon when application started

[Nicolò Chieffo]

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

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

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

Title:
  Duplicated icon when application started

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

Bug description:
  gnome-shell-extension-ubuntu-dock  0.7

  I added to the dock an application (an Eclipse-based IDE from IBM called 
Rational Application Develper) 
  .desktop file attached.

  When clicking on the icon, a new icon is created as long as the application 
is running.
  The icon disappears when I close the application

  I think that the problems is that the launcher spawns another process,
  (attached the ps -uf relevand part)

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

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

[Desktop-packages] [Bug 1728305] [NEW] Mouse (cursor) Mirroring

[Rafael Bijos Faidiga]

Public bug reported:

I have a 3 screen setup on a notebook with intel graphics. The left one is in 
portrait view, the center one is in normal view and right is in normal view 
(buildin).
When the mouse is in left side of the center monitor it shows on the left 
monitor bottom. 

The same problem is better described here:
https://askubuntu.com/questions/964239/ubuntu-17-10-cursor-mirrored-on-
second-screen. And since this isn't my post, it affects multiple users.

Thanks

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

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

Title:
  Mouse (cursor) Mirroring

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I have a 3 screen setup on a notebook with intel graphics. The left one is in 
portrait view, the center one is in normal view and right is in normal view 
(buildin).
  When the mouse is in left side of the center monitor it shows on the left 
monitor bottom. 

  The same problem is better described here:
  https://askubuntu.com/questions/964239/ubuntu-17-10-cursor-mirrored-
  on-second-screen. And since this isn't my post, it affects multiple
  users.

  Thanks

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

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

[Desktop-packages] [Bug 1574383] Re: Allow one to search through the "Installed" apps section

[Bug Watch Updater]

** Changed in: gnome-software
   Status: Incomplete => Expired

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

Title:
  Allow one to search through the "Installed" apps section

Status in GNOME Software:
  Expired
Status in Ubuntu GNOME:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  One can use the search feature in the "All" section, but there is no
  such search facility only for the currently installed applications
  that I can find, so I think that in the "Installed" apps section there
  really should be some sort of search facility, one perhaps that comes
  up upon one doing CTRL+F.

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

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

[Desktop-packages] [Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

[Bug Watch Updater]

** Changed in: gvfs
   Status: Unknown => Invalid

** Changed in: gvfs
   Importance: Unknown => Critical

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

Title:
  Unable to open files from MTP-device: : Input/output error

Status in gvfs:
  Invalid
Status in gvfs package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Connect MTP-device to laptop
  2. Caja file browser opens
  3. Navigate to the needed file on MTP-device with Caja

  4a. Try to open text file with Pluma from Caja or from terminal:
  Unexpected error: libmtp error: Unknown error.

  4b. Try to open text file with `cat`:

  $ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt
  cat: '/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/file.txt': 
Input/output error

  4c. Try to open video file with `vlc` from Caja or from terminal:

  $ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-
  card/video.mkv

  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [00daa088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f00c4000f48] filesystem access error: read error: Input/output error
  [7f00c4001408] core stream error: cannot pre fill buffer

  4d. Try to open Markdown file with ReText from Caja or from terminal:
  Retext opens with empty document

  4e. Try to open docx-file with LibreOffice from Caja or from terminal:
  get error window with text "General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx."

  4f. Try to open ppt, pptx, xls, xlsx, odp, odt, or doc-file with LibreOffice 
from Caja or from terminal:
  get error window with text "General Error.
  The seek operation could not be run."
  or empty document

  4g. Try to open png- or jpg- image file with Eye of MATE from Caja or from 
terminal:
  "libmtp error: Unknown error."

  Note: tested with two Android devices - with Android 4.1.2 and 4.4.4.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 28 00:35:42 2017
  InstallationDate: Installed on 2014-02-07 (1358 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (194 days ago)

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

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

[Desktop-packages] [Bug 1042211] Re: [quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works)

[Bug Watch Updater]

** Changed in: mesa
   Status: Confirmed => Invalid

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

Title:
  [quantal] [regression] [i915] Corrupted display, desktop and menus
  don't repaint correctly using Mesa 9.0 (8.0.4 works)

Status in Compiz:
  Invalid
Status in Mesa:
  Invalid
Status in compiz package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  WORKAROUND:
  Download and install the old Mesa 8.0.4 packages for quantal from:
  https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1

  or add the Unity staging PPA:

  sudo add-apt-repository ppa:unity-team/staging

  ORIGINAL DESCRIPTION:
  After installing the latest updates on Quantal, desktop fails to repaint 
correctly:
  - moving a window leave trails
  - plain color is displayed instead of custom background
  - menus are flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8+bzr3319-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2
  Uname: Linux 3.5.0-12-generic i686
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Aug 27 10:38:41 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
     Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
  MachineType: ASUSTeK Computer INC. 1015PE
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-12-generic 
root=UUID=014cdf46-1d84-4e78-a68e-5d6de3419ad9 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/31/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PE
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu2
  version.libdrm2: libdrm2 2.4.38-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1-4~ubuntu1

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

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

[Desktop-packages] [Bug 872876] Re: terminal window resizes when moving around window in awesome window manager

[Bug Watch Updater]

** Changed in: awesome (Debian)
   Status: New => Fix Released

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

Title:
  terminal window resizes when moving around window in awesome window
  manager

Status in awesome package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in awesome package in Debian:
  Fix Released

Bug description:
  Reproduce:
   - start "awesome" (window manager)
   - open gnome-terminal
   - hold down "windows"-key
   - drag the terminal window with left mouse button

  What I expect:
   - Window should move around and size should stay the same

  What I actually see:
   - Window becomes smaller and smaller

  Workaround
   - resize the window before you drag it around (Win+RMB-Drag)
   - resize the window to a size that is odd to the height of a character
   - when there is a bit space in the bottom of the window (clientheight is not 
a multiple of the height of one line), moving will work correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 12 16:12:27 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110827)
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[CaptSaltyJack]

Sorry to spam the comments, there's no edit feature. Once again I have a
black screen with a blinking cursor, but I'm able to hit Ctrl+Alt+F6 to
get to a shell. How do I troubleshoot 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/1705369

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[CaptSaltyJack]

Update: Went into a recovery shell as root, ran "dpkg-reconfigure
xserver-xorg". I got no output, no prompts, nothing. Rebooted, things
are OK now.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1728214] Re: Cannot adjust screen brightness after upgrading from 17.04 to 17.10

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot adjust screen brightness after upgrading from 17.04 to 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  References:

  https://help.ubuntu.com/stable/ubuntu-help/display-brightness.html

  The screen is unusably bright and I cannot adjust its brightness by
  any of the following methods:

  "To change the brightness of your screen, click the system menu on the
  right side of the top bar and adjust the screen brightness slider to
  the value you want to use. The change should take effect immediately".

  "You can also adjust the screen brightness by using the Power panel".

  Prior to upgrade, the brightness controller app worked
  (https://github.com/LordAmit/Brightness).

  After the upgrade, it does not.

  Related posts are on Ubuntu stack exchange etc:

  https://askubuntu.com/questions/966557/how-do-we-turn-down-the-insane-
  brightness-on-ubuntu-17-10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 18:36:39 2017
  DistUpgraded: 2017-10-22 07:25:03,053 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 520 [8086:2063]
  InstallationDate: Installed on 2016-03-22 (585 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=306db387-b854-4d8f-8382-9727ad6ce642 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-21 (6 days ago)
  dmi.bios.vendor: Intel Corp.
  dmi.board.vendor: Intel corporation
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Oct 21 20:19:52 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1.3
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1726464] Re: Add option to disable sticky edges

[Rasmus Eneman]

I realized that this is only when I have the dock set to auto hide. With
always visible it's possible to move the cursor to the other screen
without issues.

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

Title:
  Add option to disable sticky edges

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  The sticky edge thing between monitors is very annoying as the cursor
  never ends up where it should when it's moved over to the other
  screen. It's annoying to the degree that I feel like I can not use
  multiple monitors with standard Ubuntu anymore.

  Unity had an option to disable this, please add one to Gnome as well.

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

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

[Desktop-packages] [Bug 1359824] Re: libvisio-dev missing dependency on libicu-dev

[Jeremy Bicha]

Fixed in Ubuntu 17.04

https://launchpad.net/ubuntu/+source/libvisio/0.1.5-4

** Changed in: libvisio (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  libvisio-dev missing dependency on libicu-dev

Status in Inkscape:
  Fix Released
Status in libvisio package in Ubuntu:
  Fix Released
Status in libvisio package in Debian:
  Fix Released

Bug description:
  pkg-config reports a missing dependency.  Please add Depends: libicu-
  dev to debian/control to rectify this.

  $ pkg-config --cflags libvisio-0.1
  Package icu-i18n was not found in the pkg-config search path.
  Perhaps you should add the directory containing `icu-i18n.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'icu-i18n', required by 'libvisio-0.1', not found

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[CaptSaltyJack]

I take that back. Just rebooted, and I have a black screen with a
blinking cursor. Ugh.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

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

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1726494, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1728295/+attachment/4998945/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1726494
   nautilus crashed with SIGSEGV in stop_cache_selection_list()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV

Status in nautilus package in Ubuntu:
  New

Bug description:
  error while copying audio to pendrive

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 21:55:52 2017
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2016-10-22 (371 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  SegvAnalysis:
   Segfault happened at: 0x55afb6675bf0:mov0x38(%r13),%rdi
   PC (0x55afb6675bf0) ok
   source "0x38(%r13)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV
  UpgradeStatus: Upgraded to artful on 2017-10-22 (5 days ago)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

[CaptSaltyJack]

Just wanted to weigh in: simply adding "nomodeset" to my kernel command
line worked! I was able to use the proprietary NVidia drivers, no
problem. I'm on a ThinkPad T570.

It looks like due to this change, I'm using X11 instead of Wayland. I
don't know if I care either way, everything works great and the graphics
are snappy. Hopefully Wayland will be ready by the time 18.04 launches.

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

Title:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS.

  * Add 'nomodeset' to your kernel command line.

  
  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 1022802] Re: XTerm and UXTerm need new icons

[Jeremy Bicha]

I'm closing this bug since Ubuntu's xterm got new icons since this bug
was filed.

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

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

Title:
  XTerm and UXTerm need new icons

Status in xterm package in Ubuntu:
  Fix Released

Bug description:
  XTerm and UXTerm need newer styled icons for better visual consistency
  with other icons in unity.

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

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

[Desktop-packages] [Bug 1707352] [sane-backends/artful] possible regression found

[Ubuntu Foundations Team Bug Bot]

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of sane-backends from artful-
proposed was performed and bug 1728198 was found.  Please investigate
this bug report to ensure that a regression will not be created by this
SRU. In the event that this is not a regression remove the
"verification-failed" tag from this bug report and add the tag "bot-
stop-nagging" to bug 1728198 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
  the change from libsane to libsane1 broke many (all?) 3rd party plug-
  ins for sane

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends source package in Artful:
  Fix Committed
Status in sane-backends package in Debian:
  New

Bug description:
  Note to SRU Team
  
  The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it 
needed to be a versioned Provides, not just a Provides.

  Impact
  ==

  1) The Debian maintainer renamed libsane to libsane1-experimental "to
  match with the soname". This apparently fixes a Lintian warning, but
  makes installing 3rd-party plug-ins hard, as they typically depend on
  "libsane", not on "libsane1". The first try to add a "Provides:
  libsane" to libsane1 (which created a virtual package) didn't make
  drivers installable that claim to depend on a minimum version of
  libsane as virtual packages are ignored in this case.

  2) The soname change might be justified by the new version breaking
  (several? most?) 3rd party plug-ins even if the library version number
  doesn't indicate any bigger change than any ordinary new version of
  the library - which might indicate that this phenomenon might be an
  upstream bug.

  libsane 1.0.25 in zesty includes libsane.so.1.25
  libsane1 1.0.27 in artful includes libsane.so.1.27

  It is to note that depending on the manufacturer for many old scanners
  there won't be new versions of the plug-ins that are recompiled like
  this.

  Test Case
  =
  Visit http://support.epson.net/linux/en/iscan_c.html
  Download the amd64 deb .tar.gz
  Unzip it.
  Install the iscan .deb from the core folder.

  It won't install before this SRU because it Depends: libsane

  Regression Potential
  
  The fix here was proposed to the Debian maintainer in July but there's been 
virtually zero response on it. In the meantime the workaround that was proposed 
initially has started to result in automatically uninstalling gtk - which makes 
the system basically useless.

  It doesn't seem like adding the Provides will make things any worse
  for third-party drivers but it has a goodme chance of making things
  better for some.

  Original Bug Report
  ===
  I don't know if that can be prevented in the long run. But both brscan (for 
my brother scanner) and iscan (for my epson scanners) have been broken by the 
change from libsane to libsane1. For iscan I have unpackaged the debian 
package, changed the dependency it contains from libsane to libsane1 and 
installed the changed package. But even then my epson scanners no more work 
leaving me without any scanner => Reporting a bug.

  Impossibility of workarounds
  
  Just installing an old version of libsane is impossible as it uninstalls 
libgtk (which depends on libsane1 which conflicts with libsane) making the 
system basically useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental1ubuntu2
  Uname: Linux 4.13.0-041300rc2-lowlatency x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Sat Jul 29 08:38:15 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1721936] Re: package cups-common 2.1.3-4ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Launchpad Bug Tracker]

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

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

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

Title:
  package cups-common 2.1.3-4ubuntu0.3 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Every time I want to update the software

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-common 2.1.3-4ubuntu0.3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sat Oct  7 12:25:55 2017
  Dependencies:
   
  DuplicateSignature:
   package:cups-common:2.1.3-4ubuntu0.3
   Setting up cups-server-common (2.1.3-4ubuntu0.3) ...
   dpkg: error processing package cups-common (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-10-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard Presario CQ57 Notebook PC
  PackageArchitecture: all
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=7edbc14a-918b-4b5a-909e-2db90e8382e7 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic 
root=UUID=7edbc14a-918b-4b5a-909e-2db90e8382e7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: cups
  Title: package cups-common 2.1.3-4ubuntu0.3 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3577
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 24.12
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.02:bd03/14/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr058F10204910002620100:rvnHewlett-Packard:rn3577:rvr24.12:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: Presario CQ57 Notebook PC
  dmi.product.version: 058F10204910002620100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1727269] Re: Window buttons and window edges are not rendered/designed cleanly - Ubuntu 17.10 Gnome

[Ragnar Dunbar]

The above mentioned darker window edges in 17.10 do not appear in all
windows. They appear in Firefox, Thunderbird and e.g. the Gnome Terminal
(maybe this has to do with gnome-terminal being at 2.24). The window
decorations in for example the file-manager are not affected.

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

Title:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome

Status in gnome-shell package in Ubuntu:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Window buttons and window edges are not rendered/designed cleanly -
  Ubuntu 17.10 Gnome. This is really just a cosmetic issue. The window
  edges (mostly only top left) and window buttons were sharper and
  clearer in Ubuntu 16.04 und the versions before. The rough window
  egdges do not appear in all windows, it is especially obvious with
  Firfox. The impression with the buttons is always present.

  This is apparent in stock Ubuntu 17.10 on various laptops (Thinkpad
  x220, Acer Aspire 5253, Macbook Pro late 2010).

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

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

[Desktop-packages] [Bug 1670089] Re: gnome-shell Crashes shortly after login

[claudio@ubuntu]

I think this is a gnome-shell-extension-dashtodock + gnome-shell-
extension-ubuntu-dock, at least in my case.

Removing gnome-shell-extension-dashtodock and reinstalling gnome-shell-
extension-ubuntu-dock allows me to login, however the dock is not
visible (it's not auto-hidden either, only visible with the meta key).

C.

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

Title:
  gnome-shell Crashes shortly after login

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  After logging in and after about 30-90 seconds gnome-shell will
  restart and take me back to the login screen. I have script that
  enables the backlight on my keyboard which is used at start up, but
  after logging in this does not work. The same script is bound to
  Scroll Lock and doesn't work after logging either. After logging in a
  second time, sometimes three times due to a gnome-shell crash the
  shortcut works.

  I've been having this problem for a few weeks now where gnome-shell
  just restarts without an error report being generated.

  This did not occur in 16.04 or 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-shell 3.23.90-0ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar  5 10:58:42 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-10-25 (130 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to zesty on 2017-01-08 (56 days ago)

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

-- 
Mailing list: https://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 1727653] Re: duplicity fails with unknown error

[Kenneth Loafman]

How many open files allowed ("ulimit -n")?  Other than memory, "too many
open files" has been the culprit that keeps fork from working.

On Sat, Oct 28, 2017 at 1:10 PM, Wolf Rogner  wrote:

> Please read my comment again:
>
> Only when autostarted the error occurs. When launched manually (the
> memory situation is the same) it works.
>
> And: I have 16 GB RAM on this machine. I think there will be some
> contiguous memory available.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1727653
>
> Title:
>   duplicity fails with unknown error
>
> Status in duplicity package in Ubuntu:
>   In Progress
>
> Bug description:
>   $ uname -a
>   Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>
>   duplicity gets started daily via deja-dup automatically.
>
>   Every now and then (approx. every third time) I get the following
>   error:
>
>   --
>
>   Failed with an unknown error.
>
>   Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1546, in 
>   with_tempdir(main)
> File "/usr/bin/duplicity", line 1540, in with_tempdir
>   fn()
> File "/usr/bin/duplicity", line 1391, in main
>   do_backup(action)
> File "/usr/bin/duplicity", line 1468, in do_backup
>   restore(col_stats)
> File "/usr/bin/duplicity", line 731, in restore
>   restore_get_patched_rop_iter(col_stats)):
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 560, in Write_ROPaths
>   for ropath in rop_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 523, in integrate_patch_iters
>   for patch_seq in collated:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 389, in yield_tuples
>   setrorps(overflow, elems)
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 378, in setrorps
>   elems[i] = iter_list[i].next()
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 107, in filter_path_iter
>   for path in path_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 121, in difftar2path_iter
>   tarinfo_list = [tar_iter.next()]
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 339, in next
>   self.set_tarfile()
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 333, in set_tarfile
>   self.current_fp = self.fileobj_iter.next()
> File "/usr/bin/duplicity", line 768, in get_fileobj_iter
>   manifest.volume_info_dict[vol_num])
> File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
>   fileobj = tdp.filtered_open_with_delete("rb")
> File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line
> 119, in filtered_open_with_delete
>   fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
> File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778,
> in filtered_open
>   return gpg.GPGFile(False, self, gpg_profile)
> File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202,
> in __init__
>   'logger': self.logger_fp})
> File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py",
> line 374, in run
>   create_fhs, attach_fhs)
> File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py",
> line 420, in _attach_fork_exec
>   process.thread.start()
> File "/usr/lib/python2.7/threading.py", line 736, in start
>   _start_new_thread(self.__bootstrap, ())
>   error: can't start new thread
>
>   --
>
>   Restarting deja-dup manually fixes the problem and the next few days,
>   automatic backup will run correctly until (see above).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: duplicity 0.7.12-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Oct 26 10:49:45 2017
>   InstallationDate: Installed on 2017-10-20 (5 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
>   SourcePackage: duplicity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/
> 1727653/+subscriptions
>

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

Title:
  duplicity fails with unknown error

Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then 

[Desktop-packages] [Bug 1728210] Re: package liferea (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Paul Gevers]

Can you please run the installation again with LC_ALL=C.UTF-8? My french
is too poor to read what is going on.

One thing I note though, it seems there is a version of liferea involved
that has never been part of Ubuntu and as such, can not be supported. If
you can't install with LC_ALL=C.UTF-8 set, I recommend removing liferea
before installing it again.

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

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

Title:
  package liferea (not installed) failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in liferea package in Ubuntu:
  Incomplete

Bug description:
  (synaptic:14964): GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid > 
0' failed
  Sélection du paquet liferea-data précédemment désélectionné.
  (Lecture de la base de données... 566770 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../liferea-data_1.11.4.git~trusty_all.deb ...
  Dépaquetage de liferea-data (1.11.4.git~trusty) ...
  Sélection du paquet liferea précédemment désélectionné.
  Préparation du dépaquetage de .../liferea_1.11.4.git~trusty_amd64.deb ...
  Dépaquetage de liferea (1.11.4.git~trusty) ...
  Sélection du paquet liferea-plugins précédemment désélectionné.
  Préparation du dépaquetage de .../liferea-plugins_1.11.4.git~trusty_all.deb 
...
  Dépaquetage de liferea-plugins (1.11.4.git~trusty) ...
  Traitement des actions différées (« triggers ») pour hicolor-icon-theme 
(0.13-1) ...
  Traitement des actions différées (« triggers ») pour desktop-file-utils 
(0.22-1ubuntu1.1) ...
  Traitement des actions différées (« triggers ») pour mime-support 
(3.54ubuntu1.1) ...
  Traitement des actions différées (« triggers ») pour gnome-menus 
(3.10.1-0ubuntu2) ...
  Traitement des actions différées (« triggers ») pour bamfdaemon 
(0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Traitement des actions différées (« triggers ») pour man-db 
(2.6.7.1-1ubuntu1) ...
  Traitement des actions différées (« triggers ») pour libglib2.0-0:amd64 
(2.40.2-0ubuntu1) ...
  Traitement des actions différées (« triggers ») pour libglib2.0-0:i386 
(2.40.2-0ubuntu1) ...
  Traitement des actions différées (« triggers ») pour menu (2.1.46ubuntu1) ...
  Paramétrage de liferea-data (1.11.4.git~trusty) ...
  Paramétrage de liferea (1.11.4.git~trusty) ...
  rmdir: échec de suppression de «/usr/share/doc/liferea»: Le dossier n'est pas 
vide
  dpkg: erreur de traitement du paquet liferea (--configure) :
   le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  Paramétrage de liferea-plugins (1.11.4.git~trusty) ...
  Des erreurs ont été rencontrées pendant l'exécution :
   liferea
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Échec de l'installation d'un paquet. Tentative de récupération :
  Paramétrage de liferea (1.11.4.git~trusty) ...
  rmdir: échec de suppression de «/usr/share/doc/liferea»: Le dossier n'est pas 
vide
  dpkg: erreur de traitement du paquet liferea (--configure) :
   le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  Des erreurs ont été rencontrées pendant l'exécution :
   liferea

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: liferea (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-133.182-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-133-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Sat Oct 28 00:57:26 2017
  DuplicateSignature: package:liferea:(not installed):le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2014-08-15 (1169 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: liferea
  Title: package liferea (not installed) failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1560114] Re: Bitmap fonts are disabled by default

[Jeremy Bicha]

Yes, this is intentional.

See /usr/share/doc/fontconfig/README.Debian for instructions on how to enable 
bitmap fonts. I copied the instructions below.
-

If you wish to enable bitmapped fonts manually, remove the
/etc/fonts/conf.d/70-no-bitmaps.conf symbolic link and add a symlink named
70-yes-bitmaps.conf pointing to ../conf.avail/70-yes-bitmaps.conf:

  cd /etc/fonts/conf.d && \
rm -f 70-no-bitmaps.conf && \
ln -s ../conf.avail/70-yes-bitmaps.conf

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

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

Title:
  Bitmap fonts are disabled by default

Status in fontconfig package in Ubuntu:
  Invalid

Bug description:
  By default, fontconfig-config installs a file called
  "/etc/fonts/conf.d/70-no-bitmaps.conf". It disables bitmap fonts. What
  good for, I don't know. Though if you later install a bitmap font
  "apt-get install xfonts-terminus" then that font wont show up in
  menus. That is not what you expect. The workaround is:

  sudo rm /etc/fonts/conf.d/70-no-bitmaps.conf
  sudo ln -s /etc/fonts/conf.avail/70-yes-bitmaps.conf 
/etc/fonts/conf.d/70-yes-bitmaps.conf

  But you shouldn't need that and bitmap founds shouldn't be disabled.

  The bug is present in Ubuntu wily, 15.10.

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

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

[Desktop-packages] [Bug 1727653] Re: duplicity fails with unknown error

[Wolf Rogner]

Please read my comment again:

Only when autostarted the error occurs. When launched manually (the
memory situation is the same) it works.

And: I have 16 GB RAM on this machine. I think there will be some
contiguous memory available.

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

Title:
  duplicity fails with unknown error

Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1323484] Re: remmina won't work with ssh ports other than 22

[Marian Hello]

I was about to write it's not working but it's actually is with :port
notation.

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

Title:
  remmina won't work with ssh ports other than 22

Status in remmina package in Ubuntu:
  Confirmed

Bug description:
  Assume an open ssh port on 6222. No problem to connect using ssh with:
  "ssh -p 6222 -l  " or with opennx giving port 6222. But
  remmina will case to connect with error message: "Error message:
  Success!".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: remmina 1.0.0-4ubuntu3
  Uname: Linux 3.14.4+ x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 27 07:01:49 2014
  InstallationDate: Installed on 2011-10-19 (950 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: remmina
  UpgradeStatus: Upgraded to trusty on 2014-02-24 (91 days ago)

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

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

[Desktop-packages] [Bug 1192175] Re: Use of mode="assign" in default configuration

[Jeremy Bicha]

Thank you for taking the time to report this bug! This bug will be fixed
in Ubuntu 18.04 LTS.

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

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

Title:
  Use of mode="assign" in default configuration

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  The additional .conf files that Ubuntu's patches create in conf.avail/ use 
mode="assign" to set preferences.
  But in this upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=17722
  it's said that the default configurations should use mode="append", and the 
use of "assign" should be limited to user configuration. The original 
fontconfig .conf files in Ubuntu already use "append", as correction of this 
bug.

  Ubuntu versions that present this bug: all.
  fontconfig versions that present this bug: all.

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

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

[Desktop-packages] [Bug 1702544] Re: Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

[Jeremy Bicha]

** Tags added: bionic upgrade-software-version

** Changed in: fontconfig (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Please merge fontconfig 2.12.3-0.1 (main) from Debian unstable (main)

  I cannot work on this merge myself. I am reporting this for reference.

  Explanation of the Ubuntu delta:
* SECURITY UPDATE: double free when handling cache files
  - debian/patches/CVE-2016-5384.patch: properly validate offsets in
cache files in src/fccache.c.
  - CVE-2016-5384
* New upstream release (LP: #1556457)
  - Fixes blurry fonts regression from previous upload (LP: #1566651)
* d/p/0001-Revert-Bug-73291-poppler-does-not-show-fl-ligature.patch,
  d/p/0002-demilight.patch:
  - Dropped, applied in new release
* Bump freetype build dep to 2.5.1 as per configure.ac.
* Drop gperf build dep again, not necessary any more.
* debian/control:
  - Add gperf to build dependencies
  - Bump FreeType build dependency version to 2.5.1
[ Mingye Wang ]
* debian/patches/0002-demilight.patch:
  - Handle Demilight sensibly (LP: #1556457)
* Make things depend on ≥ version-of-libfontconfig1-they-were-built-with, so
  that on new releases the library is upgraded before its rdeps. (LP:
  #1540591)
* debian/source_fontconfig.py:
  - include fontconfig.log in the bug reports to try to get more info
on some of the xenial upgrade issues
* 0001-Revert-Bug-73291-poppler-does-not-show-fl-ligature.patch: Now poppler
  is fixed, revert the alias of TeX Gyre Termes to Times. (LP: #1379375)
* Merge changes from Debian 2.11.0-6.1 and 2.11.0-6.2:
[ Don Armstrong ]
* Switch to noawait triggers to allow self-triggering; will still need
  Breaks from dpkg to resolve this (closes: #768599)
* Add Pre-Depends on dpkg to allow for noawait just in case this gets
  backported to squeeze.
[ Andreas Barth ]
* Add dh-autoreconf to support ppc64el. Closes: #748378
* No change rebuild to get debug symbols on all architectures.
* Merge from Debian 2.11.0-2:
  - 03_locale_c.utf8.patch: based on a patch from Martin Dickopp. Treat
C.UTF-8 and C.utf8 locales as built in the C library.
Closes: #717423.
* Merge from Debian 2.11.0-2:
  - 03_locale_c.utf8.patch: based on a patch from Martin Dickopp. Treat
C.UTF-8 and C.utf8 locales as built in the C library.
Closes: #717423.
* Make libfontconfig1-dev Multi-Arch: same.
* New upstream release
* Pass --enable-static to continue building the static library since the
  default changed in this release.
* 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Drop, applied
  upstream in this release.
* 0001-Bug-73291-poppler-does-not-show-fl-ligature.patch: Don't alias TeX
  Gyre Termes to Times as it has a broken 'fi' ligature. (LP: #1325230)
* debian/rules:
  - don't add /usr/X11R6/lib/X11/fonts to the fonts path, that's a
deprecated location and it leads to polling on the directory,
which means wakeups and extra power usage (lp: #1266873)
* Build using dh-autoreconf.
* Update font dependencies (ttf-dejavu-core -> fonts-dejavu-core and
  ttf-freefont -> fonts-freefont-ttf).
* New upstream version
* Refresh debian patches
* git_obtain_fonts_via_FT-face.patch:
  - dropped, included in the new version
* debian/patches/series: list the patch from the previous revision...
  (lp: #1177995)
* New upstream version
* Refreshed patches
* debian/patches/git_obtain_fonts_via_FT-face.patch
  - cherrypick patch from git to fix webfonts (LP: #1177995) (Thanks Tim)
* Remove versioned build dependency on binutils.
* New upstream version:
  - includes the typo fixes for lp: #1037509
* Fix fontconfig-config postinst to ignore rmdir failures when removing
  /var/lib/defoma/fontconfig.d/ as some systems have files in there.
  (LP: #1039828)
* debian/control: build-depends on pkg-config
* Cherry pick from Debian experimental: Remove defoma support.
  Closes: #651493.
* Drop 08_ug_us_orth.patch again, as per Eagle Burkut. (Locale was renamed
  to ug_CN@latin).
* Add 08_ug_us_orth.patch: Add ug_US orthography.
* Add 00git_ughur_orthography.patch: Complete Uighur orthography. Patch
  taken from upstream git head. (LP: #736413)
* debian/patches/01_fonts_nanum.patch: Fix typo, thanks Felix Geyer for
  spotting!
* debian/patches/01_fonts_nanum.patch
  - Restore Baekmuk fonts because it's still in 

[Desktop-packages] [Bug 210921] Re: Fontconfig should default to full hinting

[Jeremy Bicha]

fontconfig defaults to slight hinting both in Ubuntu and upstream. This
seems to produce the best results for the most people.

** Changed in: fontconfig (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  Fontconfig should default to full hinting

Status in One Hundred Papercuts:
  Invalid
Status in fontconfig package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: fontconfig

  
  dpkg -S /etc/fonts/conf.avail/10-hinting-medium.conf 
  fontconfig-config: /etc/fonts/conf.avail/10-hinting-medium.conf

  Ubuntu Hardy has the following symlink by default:
  lrwxrwxrwx 1 root root  34 2008-04-02 19:17 10-hinting-medium.conf -> 
../conf.avail/10-hinting-medium.conf

  This really should (instead) be:
  lrwxrwxrwx 1 root root  34 2008-04-02 19:17 10-hinting-full.conf -> 
../conf.avail/10-hinting-full.conf

  This default is causing issue like this:
  https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/190848

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

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

[Desktop-packages] [Bug 293643] Re: font settings in .fonts.conf ignored

[Jeremy Bicha]

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

Reassigning to cairo per comment #6

** Package changed: fontconfig (Ubuntu) => cairo (Ubuntu)

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

** Also affects: cairo via
   https://bugs.freedesktop.org/show_bug.cgi?id=11838
   Importance: Unknown
   Status: Unknown

** This bug has been marked a duplicate of bug 161058
   some ~/.fonts.conf settings do no override desktop-wide gnome settings 
(hinting style)

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

Title:
  font settings in .fonts.conf ignored

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: fontconfig

  The following doesn't work unless I use;

  true

  What I thought should work;

  
  
  Consolas
  
  
  hintslight
  
  

  What actually works;

  
  
  Consolas
  
  rgb
  true
  true
  true
  hintslight
  http://forums.fedoraforum.org/showthread.php?t=186789=7 for more 
information and my old .fonts.conf; http://pastebin.com/m1b3fbe51 .

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

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

[Desktop-packages] [Bug 1638959] Re: Update to 2.12.3

[Jeremy Bicha]

** Project changed: inkscape-devlibs64 => freetype (Ubuntu)

** No longer affects: freetype (Ubuntu)

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

Title:
  Update to 2.12.3

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Debian unstable now has 2.12.3. Please consider merging.
  

  Current 16.04+ releases uses fc 2.11.94 (2.12 RC4) for an early fix for bug 
#1556457. It sounds saner to move to 2.12.1, a non-RC release which contains 
some Unicode table updates, memory leak fixes, and the original fix for 
CVE-2016-5384, for the next Ubuntu release. The ABI appears unchanged since 
2.11.94.
  ---

  README (with ChangeLog): https://cgit.freedesktop.org/fontconfig/tree/README
  ABI diff: https://abi-laboratory.pro/tracker/timeline/fontconfig/

  2.12.3

  Akira TAGOH (1):
Fix make check fail with freetype-2.7.1 and 2.8 with 
PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled.

  2.12.2

  Akira TAGOH (8):
Don't call perror() if no changes happens in errno
Fix FcCacheOffsetsValid()
Fix the build issue with gperf 3.1
Fix the build issue on GNU/Hurd
Update a bit for the changes in FreeType 2.7.1
Add the description of FC_LANG envvar to the doc
Bug 101202 - fontconfig FTBFS if docbook-utils is installed
Update libtool revision

  Alan Coopersmith (1):
Correct cache version info in doc/fontconfig-user.sgml

  Khem Raj (1):
Avoid conflicts with integer width macros from TS 18661-1:2014

  Masamichi Hosoda (2):
Fix PostScript font alias name
Update aliases for URW June 2016

  2.12.1

  Akira TAGOH (6):
Add --with-default-hinting to configure
Update CaseFolding.txt to Unicode 9.0
Check python installed in autogen.sh
Fix some errors related to python3
Bug 96676 - Check range of FcWeightFromOpenType argument
Update libtool revision

  Tobias Stoeckmann (1):
Properly validate offsets in cache files.

  2.12

  Akira TAGOH (8):
Modernize fc-blanks.py
Update URL
Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with 
EACCES
45-latin.conf: Add some Windows fonts to categorize them properly
Correct one for the previous change
Bug 95481 - Build fails on Android due to broken lconv struct
Add the static raw data to generate fcblanks.h
Remove unused code

  Erik de Castro Lopo (1):
Fix a couple of minor memory leaks

  Petr Filipsky (1):
Fix memory leak in FcDirCacheLock

  2.11.95 (2.12 RC5)

  Akira TAGOH (22):
Add one more debugging option to see transformation on font-matching
Fix a crash when no objects are available after filtering
No need to be public
mark as private at this moment
Don't return FcFalse even when no fonts dirs is configured
Add a warning for blank in fonts.conf
Fix a memory leak in FcFreeTypeQueryFace
Update CaseFolding.txt to Unicode 8.0
Bug 90867 - Memory Leak during error case in fccharset
Fix the broken cache more.
Fail on make runtime as needed instead of configure if no python 
installed
Use long long to see the same size between LP64 and LLP64
Fix build issue on MinGW
Use int64_t instead of long long
Fix compiler warnings on MinGW
Fix assertion on 32bit arch
remomve unnecessary code
Bug 93075 - Possible fix for make check failure on msys/MinGW...
Avoid an error message on testing when no fonts.conf installed
Add hintstyle templates and make hintslight default
Revert "Workaround another race condition issue"
Update libtool revision

  Behdad Esfahbod (6):
Revert changes made to FcConfigAppFontAddDir() recently
Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery()
[GX] Support instance weight, width, and style name
[GX] Enumerate all named-instances in TrueType GX fonts
Improve OpenType to Fontconfig weight mapping
[GX] Improve weight mapping

  Patrick Haller (1):
Optimizations in FcStrSet

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

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

[Desktop-packages] [Bug 1700319] Re: GTK3 menus don't work over SSH forwarding

[Bug Watch Updater]

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

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

Title:
  GTK3 menus don't work over SSH forwarding

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  When connecting remotely (either SSH X11 forwarding or direct to X11
  server), drop down menus do not display properly.

  Bug upstream in gtk3:
  https://bugzilla.gnome.org/show_bug.cgi?id=780101

  Client: Ubuntu 17.04 - gtk3-3.22.11-0ubuntu3
  Server: Windows 10 Cygwin/X 1.19.2-1

  Programs exhibiting this problem:
  evince 3.24.0 (and any other gtk3 apps with menus along the top).

  Patch applied to gtk3 in cygwin to fix this problem and attached to this post:
  https://github.com/cygwinports/gtk3/blob/master/3.22.10-xrandr12-compat.patch

  Console errors:

  (evince:7390): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner:
  assertion 'G_IS_DBUS_PROXY (proxy)' failed

  (evince:7390): GLib-WARNING **: GError set over the top of a previous GError 
or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: The name org.freedesktop.portal.Desktop is 
not owned

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **:
  gtk_widget_get_preferred_height_for_width: assertion 'width >= 0'
  failed

  (evince:7390): Gtk-CRITICAL **: gtk_widget_get_preferred_height_for_width: 
assertion 'width >= 0' failed
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  
  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)

  (evince:7390): Gtk-WARNING **: Negative content width -7 (allocation 1, 
extents 4x4) while allocating gadget (node arrow, owner GtkMenu)
  *** BUG ***
  In pixman_region32_init_rect: Invalid rectangle passed
  Set a breakpoint on '_pixman_log_error' to debug

  
  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation 1, 
extents 6x6) while allocating gadget (node menuitem, owner GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

  (evince:7390): Gtk-WARNING **: Negative content width -11 (allocation
  1, extents 6x6) while allocating gadget (node menuitem, owner
  GtkModelMenuItem)

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

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

[Desktop-packages] [Bug 1638959] Re: Update to 2.12.3

[Launchpad Bug Tracker]

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

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

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

Title:
  Update to 2.12.3

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Debian unstable now has 2.12.3. Please consider merging.
  

  Current 16.04+ releases uses fc 2.11.94 (2.12 RC4) for an early fix for bug 
#1556457. It sounds saner to move to 2.12.1, a non-RC release which contains 
some Unicode table updates, memory leak fixes, and the original fix for 
CVE-2016-5384, for the next Ubuntu release. The ABI appears unchanged since 
2.11.94.
  ---

  README (with ChangeLog): https://cgit.freedesktop.org/fontconfig/tree/README
  ABI diff: https://abi-laboratory.pro/tracker/timeline/fontconfig/

  2.12.3

  Akira TAGOH (1):
Fix make check fail with freetype-2.7.1 and 2.8 with 
PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled.

  2.12.2

  Akira TAGOH (8):
Don't call perror() if no changes happens in errno
Fix FcCacheOffsetsValid()
Fix the build issue with gperf 3.1
Fix the build issue on GNU/Hurd
Update a bit for the changes in FreeType 2.7.1
Add the description of FC_LANG envvar to the doc
Bug 101202 - fontconfig FTBFS if docbook-utils is installed
Update libtool revision

  Alan Coopersmith (1):
Correct cache version info in doc/fontconfig-user.sgml

  Khem Raj (1):
Avoid conflicts with integer width macros from TS 18661-1:2014

  Masamichi Hosoda (2):
Fix PostScript font alias name
Update aliases for URW June 2016

  2.12.1

  Akira TAGOH (6):
Add --with-default-hinting to configure
Update CaseFolding.txt to Unicode 9.0
Check python installed in autogen.sh
Fix some errors related to python3
Bug 96676 - Check range of FcWeightFromOpenType argument
Update libtool revision

  Tobias Stoeckmann (1):
Properly validate offsets in cache files.

  2.12

  Akira TAGOH (8):
Modernize fc-blanks.py
Update URL
Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with 
EACCES
45-latin.conf: Add some Windows fonts to categorize them properly
Correct one for the previous change
Bug 95481 - Build fails on Android due to broken lconv struct
Add the static raw data to generate fcblanks.h
Remove unused code

  Erik de Castro Lopo (1):
Fix a couple of minor memory leaks

  Petr Filipsky (1):
Fix memory leak in FcDirCacheLock

  2.11.95 (2.12 RC5)

  Akira TAGOH (22):
Add one more debugging option to see transformation on font-matching
Fix a crash when no objects are available after filtering
No need to be public
mark as private at this moment
Don't return FcFalse even when no fonts dirs is configured
Add a warning for blank in fonts.conf
Fix a memory leak in FcFreeTypeQueryFace
Update CaseFolding.txt to Unicode 8.0
Bug 90867 - Memory Leak during error case in fccharset
Fix the broken cache more.
Fail on make runtime as needed instead of configure if no python 
installed
Use long long to see the same size between LP64 and LLP64
Fix build issue on MinGW
Use int64_t instead of long long
Fix compiler warnings on MinGW
Fix assertion on 32bit arch
remomve unnecessary code
Bug 93075 - Possible fix for make check failure on msys/MinGW...
Avoid an error message on testing when no fonts.conf installed
Add hintstyle templates and make hintslight default
Revert "Workaround another race condition issue"
Update libtool revision

  Behdad Esfahbod (6):
Revert changes made to FcConfigAppFontAddDir() recently
Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery()
[GX] Support instance weight, width, and style name
[GX] Enumerate all named-instances in TrueType GX fonts
Improve OpenType to Fontconfig weight mapping
[GX] Improve weight mapping

  Patrick Haller (1):
Optimizations in FcStrSet

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

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

[Desktop-packages] [Bug 1638959] Re: Update to 2.12.3

[Jeremy Bicha]

** Changed in: fontconfig (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Update to 2.12.3

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  Debian unstable now has 2.12.3. Please consider merging.
  

  Current 16.04+ releases uses fc 2.11.94 (2.12 RC4) for an early fix for bug 
#1556457. It sounds saner to move to 2.12.1, a non-RC release which contains 
some Unicode table updates, memory leak fixes, and the original fix for 
CVE-2016-5384, for the next Ubuntu release. The ABI appears unchanged since 
2.11.94.
  ---

  README (with ChangeLog): https://cgit.freedesktop.org/fontconfig/tree/README
  ABI diff: https://abi-laboratory.pro/tracker/timeline/fontconfig/

  2.12.3

  Akira TAGOH (1):
Fix make check fail with freetype-2.7.1 and 2.8 with 
PCF_CONFIG_OPTION_LONG_FAMILY_NAMES enabled.

  2.12.2

  Akira TAGOH (8):
Don't call perror() if no changes happens in errno
Fix FcCacheOffsetsValid()
Fix the build issue with gperf 3.1
Fix the build issue on GNU/Hurd
Update a bit for the changes in FreeType 2.7.1
Add the description of FC_LANG envvar to the doc
Bug 101202 - fontconfig FTBFS if docbook-utils is installed
Update libtool revision

  Alan Coopersmith (1):
Correct cache version info in doc/fontconfig-user.sgml

  Khem Raj (1):
Avoid conflicts with integer width macros from TS 18661-1:2014

  Masamichi Hosoda (2):
Fix PostScript font alias name
Update aliases for URW June 2016

  2.12.1

  Akira TAGOH (6):
Add --with-default-hinting to configure
Update CaseFolding.txt to Unicode 9.0
Check python installed in autogen.sh
Fix some errors related to python3
Bug 96676 - Check range of FcWeightFromOpenType argument
Update libtool revision

  Tobias Stoeckmann (1):
Properly validate offsets in cache files.

  2.12

  Akira TAGOH (8):
Modernize fc-blanks.py
Update URL
Bug 95477 - FcAtomicLock fails when SELinux denies link() syscall with 
EACCES
45-latin.conf: Add some Windows fonts to categorize them properly
Correct one for the previous change
Bug 95481 - Build fails on Android due to broken lconv struct
Add the static raw data to generate fcblanks.h
Remove unused code

  Erik de Castro Lopo (1):
Fix a couple of minor memory leaks

  Petr Filipsky (1):
Fix memory leak in FcDirCacheLock

  2.11.95 (2.12 RC5)

  Akira TAGOH (22):
Add one more debugging option to see transformation on font-matching
Fix a crash when no objects are available after filtering
No need to be public
mark as private at this moment
Don't return FcFalse even when no fonts dirs is configured
Add a warning for blank in fonts.conf
Fix a memory leak in FcFreeTypeQueryFace
Update CaseFolding.txt to Unicode 8.0
Bug 90867 - Memory Leak during error case in fccharset
Fix the broken cache more.
Fail on make runtime as needed instead of configure if no python 
installed
Use long long to see the same size between LP64 and LLP64
Fix build issue on MinGW
Use int64_t instead of long long
Fix compiler warnings on MinGW
Fix assertion on 32bit arch
remomve unnecessary code
Bug 93075 - Possible fix for make check failure on msys/MinGW...
Avoid an error message on testing when no fonts.conf installed
Add hintstyle templates and make hintslight default
Revert "Workaround another race condition issue"
Update libtool revision

  Behdad Esfahbod (6):
Revert changes made to FcConfigAppFontAddDir() recently
Call FcFreeTypeQueryFace() from fcdir.c, instead of FcFreeTypeQuery()
[GX] Support instance weight, width, and style name
[GX] Enumerate all named-instances in TrueType GX fonts
Improve OpenType to Fontconfig weight mapping
[GX] Improve weight mapping

  Patrick Haller (1):
Optimizations in FcStrSet

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

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

[Desktop-packages] [Bug 1728259] [NEW] Update ubuntu specific applications gui with gnome3/gtk3 concept

[Ahmet Aksoy]

Public bug reported:

update-manager, software-properties-gtk, gnome-language-selector, 
usb-creator-gtk... 
These applications looks like gtk2 applications. I think these apps interfaces 
need to be refreshed with Gnome3/GTK3 concept

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: usb-creator (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: language-selector (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: usb-creator (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Update ubuntu specific applications gui with gnome3/gtk3 concept

Status in language-selector package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in usb-creator package in Ubuntu:
  New

Bug description:
  update-manager, software-properties-gtk, gnome-language-selector, 
usb-creator-gtk... 
  These applications looks like gtk2 applications. I think these apps 
interfaces need to be refreshed with Gnome3/GTK3 concept

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

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

[Desktop-packages] [Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

[Jeremy Bicha]

** Description changed:

- The Shell Extensions subcategory in GNOME Software is empty. I am using
- the latest (3.26.1-0ubuntu1) GNOME Software package.
+ Impact
+ ==
+ In the Ubuntu/GNOME Software app, the Addons > Shell Extensions category is 
empty. This makes it really difficult to browse for GNOME Shell extensions.
+ 
+ Test Case
+ =
+ Install the update.
+ Run Ubuntu/GNOME Software
+ It should prompt your to reload the Software app itself since it has been 
updated. (Or log out and log back in.)
+ On the home screen, click Addons. Click Shell Extensions.
+ It should show a list of available extensions after a few moments.
+ 
+ Regression Potential
+ 
+ This minimal patch was cherry-picked from the gnome-3-26 stable branch. 
Fedora 27 applies the patch.
+ 
+ Other Info
+ ==
+ The issue is that GNOME Software limited results to 500 but there are more 
than 800 Shell Extensions now. Maybe in the future, there should be some 
pagination or organization instead of a massive alphabetical list of extensions.
+ 
+ Workaround
+ ==
+ You can still look up and install a special GNOME Shell extension if you 
search for it.
+ 
+ Original Bug Report
+ ===
+ The Shell Extensions subcategory in GNOME Software is empty. I am using the 
latest (3.26.1-0ubuntu1) GNOME Software package.

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  Impact
  ==
  In the Ubuntu/GNOME Software app, the Addons > Shell Extensions category is 
empty. This makes it really difficult to browse for GNOME Shell extensions.

  Test Case
  =
  Install the update.
  Run Ubuntu/GNOME Software
  It should prompt your to reload the Software app itself since it has been 
updated. (Or log out and log back in.)
  On the home screen, click Addons. Click Shell Extensions.
  It should show a list of available extensions after a few moments.

  Regression Potential
  
  This minimal patch was cherry-picked from the gnome-3-26 stable branch. 
Fedora 27 applies the patch.

  Other Info
  ==
  The issue is that GNOME Software limited results to 500 but there are more 
than 800 Shell Extensions now. Maybe in the future, there should be some 
pagination or organization instead of a massive alphabetical list of extensions.

  Workaround
  ==
  You can still look up and install a special GNOME Shell extension if you 
search for it.

  Original Bug Report
  ===
  The Shell Extensions subcategory in GNOME Software is empty. I am using the 
latest (3.26.1-0ubuntu1) GNOME Software package.

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

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

[Desktop-packages] [Bug 1710754] Re: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all

[Scott Palmer]

This was fixed for a while by an update that came in, but now this
problem has come back.

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

Title:
  [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I start my computer I have no sound.  If I unplug my line out and
  plug it in again sound works fine. In Windows 10 this unplug and
  replug is not required (the jack is fine).

  Running:
   $ amixer -c0 contents
  so I can compare the non working state with the working state, the following 
differences exist:

  Non Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=off
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=on

  Working:
  numid=43,iface=CARD,name='Line Out Front Jack'
; type=BOOLEAN,access=r---,values=1
: values=on
  numid=35,iface=MIXER,name='IEC958 Playback Switch'
; type=BOOLEAN,access=rw--,values=1
: values=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Aug 14 19:05:12 2017
  InstallationDate: Installed on 2017-08-07 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scott  1154 F pulseaudio
   /dev/snd/controlC1:  scott  1154 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [System Product Name, VIA VT2020, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1726464] Re: Add option to disable sticky edges

[Rasmus Eneman]

>Is this the sticky edges feature, or generally a cursor barrier
problem?

I don't know if it's the correct name. But the cursor "sticks" on the
edge between the monitors. It should move just like it does when I drag
it on a single monitor.

>Are you dragging a window when the problem happens?

No, just normal mouse movement without any window, file or other thing
"picked up"

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

Title:
  Add option to disable sticky edges

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  The sticky edge thing between monitors is very annoying as the cursor
  never ends up where it should when it's moved over to the other
  screen. It's annoying to the degree that I feel like I can not use
  multiple monitors with standard Ubuntu anymore.

  Unity had an option to disable this, please add one to Gnome as well.

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

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

[Desktop-packages] [Bug 1728157] Re: Unable to open files from MTP-device: : Input/output error

[Norbert]

There is no bug in GVFS. The problem is old Android, which does not
support MTP i/o extensions. Android 5.0 and higher is not affected. On
4.0 - 4.4 user must copy file/folder from MTP-device to the local
storage and then open it from here.

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

** Tags removed: amd64

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

Title:
  Unable to open files from MTP-device: : Input/output error

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Connect MTP-device to laptop
  2. Caja file browser opens
  3. Navigate to the needed file on MTP-device with Caja

  4a. Try to open text file with Pluma from Caja or from terminal:
  Unexpected error: libmtp error: Unknown error.

  4b. Try to open text file with `cat`:

  $ cat /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-card/file.txt
  cat: '/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/file.txt': 
Input/output error

  4c. Try to open video file with `vlc` from Caja or from terminal:

  $ vlc /run/user/1000/gvfs/mtp\:host\=%5Busb%3A003%2C003%5D/SD-
  card/video.mkv

  VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)
  [00daa088] core libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
  [7f00c4000f48] filesystem access error: read error: Input/output error
  [7f00c4001408] core stream error: cannot pre fill buffer

  4d. Try to open Markdown file with ReText from Caja or from terminal:
  Retext opens with empty document

  4e. Try to open docx-file with LibreOffice from Caja or from terminal:
  get error window with text "General input/output error while accessing 
/run/user/1000/gvfs/mtp:host=%5Busb%3A003%2C003%5D/SD-card/document.docx."

  4f. Try to open ppt, pptx, xls, xlsx, odp, odt, or doc-file with LibreOffice 
from Caja or from terminal:
  get error window with text "General Error.
  The seek operation could not be run."
  or empty document

  4g. Try to open png- or jpg- image file with Eye of MATE from Caja or from 
terminal:
  "libmtp error: Unknown error."

  Note: tested with two Android devices - with Android 4.1.2 and 4.4.4.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sat Oct 28 00:35:42 2017
  InstallationDate: Installed on 2014-02-07 (1358 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (194 days ago)

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

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

[Desktop-packages] [Bug 1728235] Re: Keyboard shortcut mapping side effect

[Gunnar Hjalmarsson]

I doubt that the keyboard shortcut feature is designed to work with a
single character as the shortcut. Try to involve some modifier key, e.g.
,  or  similarly as the predefined shortcuts.

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

Title:
  Keyboard shortcut mapping side effect

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

Bug description:
  I have defined a custom shortcut (/usr/bin/guake -t) on the key "§".
  The shortcut § works fine, but if I press the letter "s" on my keyboard, 
Guake is opened as well.

  
  What do I expect:
  > That the letter s writes an s.
  What's happening:
  > Everytime I press "s", guake opens, but I can't use the letter "s" anymore.

  
  I had to map a different shortcut (Maj §) and the "s" works fine.
  PS: I am using the Swiss French keyboard configuration

  Ubuntu 17.10
  gnome-control-center:
Installed: 1:3.26.1-0ubuntu4

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:12:21 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-05-21 (160 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (4 days ago)

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

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

[Desktop-packages] [Bug 1636282] Re: network-manager after suspend showing arrow icon instead of wifi icon and showing no wifi networks

[Ragnar Dunbar]

The problem persists in 16.04.3

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

Title:
  network-manager after suspend showing arrow icon instead of wifi icon
  and showing no wifi networks

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  As requested by Mathieu Trudel-Lapierre (cyphermox) in bug #1589401
  I'm creating my own bug report.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ apt-cache policy network-manager
  network-manager:
Installiert:   1.2.2-0ubuntu0.16.04.3
Installationskandidat: 1.2.2-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.2-0ubuntu0.16.04.3 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 http://ch.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  3) What you expected to happen
  I'm connected by WiFi only, not by a wired connection. I expect to see the 
WiFi icon anytime while being connected to my WiFi network. Also, I expect to 
see all the WiFi networks around me (at least one other network with good 
reception and about 3 with bad reception).

  4) What happened instead
  After waking up the laptop from suspend, there appears the ethernet icon 
(arrow symbols) instead of the WiFi icon.
  Also, in this state there are no other WiFi networks visible in the 
network-manager.
  However, the laptop is still connected with my WiFi and the connection works 
as usual.
  Using "service network-manager restart" in the console I can get the wireless 
icon back and all the other networks around me are visible again.
  This can be reproduced anytime and with 100% "success rate". The problem 
appeared with Ubuntu 16.10 and was persistent since.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 24 20:06:09 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-05-15 (161 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlo1  proto static  metric 600 
   169.254.0.0/16 dev wlo1  scope link  metric 1000 
   192.168.1.0/24 dev wlo1  proto kernel  scope link  src 192.168.1.244  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  
 
   wlo1wifi  connected/org/freedesktop/NetworkManager/Devices/2  
WiNet 2 162de978-4466-46b0-957b-5f9c141d702a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  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/1636282/+subscriptions

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

[Desktop-packages] [Bug 1728246] [NEW] Apport shows the window without details, regularly

[Александр]

Public bug reported:

Apport shows the window without details, on a regular basis. Missing the 
ability to hide the replay and report an error. The program automatically shuts 
down without sending error report.
When you try to use ubuntu-bug -w displays a message "cannot report a problem: 
this package is installed not correctly"

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 20:02:54 2017
InstallationDate: Installed on 2015-08-27 (792 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Apport shows the window without details, regularly

Status in evince package in Ubuntu:
  New

Bug description:
  Apport shows the window without details, on a regular basis. Missing the 
ability to hide the replay and report an error. The program automatically shuts 
down without sending error report.
  When you try to use ubuntu-bug -w displays a message "cannot report a 
problem: this package is installed not correctly"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 20:02:54 2017
  InstallationDate: Installed on 2015-08-27 (792 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)

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

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

[Desktop-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

[Rudi Daemen]

I have a very useful update on the Skylake/nvidia GTX1060 case where the
HDMI Audio device does not show up in lspci. Based on information found
on the NVidia Developer forum, I was able to get my HDMI audio device
show up in Ubuntu 17.10 as per my posting there:

https://devtalk.nvidia.com/default/topic/1024022/linux/gtx-1060-no-
audio-over-hdmi-only-hda-intel-detected-azalia/post/5216905/#5216905

Crossposting the information here so affected people can try this as
well:

Create the file "/etc/systemd/system/fix-hdmi-audio.service" as per below:
[Unit]
Description=nVidia HDMI Audio Fixer
Before=systemd-logind.service display-manager.service
After=module-init-tools.service

[Service]
Type=oneshot
ExecStart=/root/fix-hdmi-audio.sh

[Install]
WantedBy=multi-user.target


Create the file "/root/fix-hdmi-audio.sh" as per below (Note, adjust the PCI 
device paths to the PCI ID of the PCIe Bride and NVidia card):

#!/bin/sh
setpci -s 01:00.0 0x488.l=0x200:0x200
rmmod nvidia-uvm nvidia-drm nvidia-modeset nvidia
sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove'
sh -c 'echo 1 > /sys/bus/pci/devices/:00:01.0/rescan'
modprobe nvidia nvidia-modeset nvidia-drm nvidia-uvm


And then execute the following commands (as root) to make it do this at boot:

chmod +x /root/fix-hdmi-audio.sh
systemctl enable fix-hdmi-audio.service


After each reboot, I now see the HDMI audio device on my laptop:

fludizz@tongerlo:~$ lspci | grep "PCIe Controller\|NVIDIA"
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce GTX 1060 
Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller 
(rev a1)

fludizz@tongerlo:~$ aplay -l | grep NVidia
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

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

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1728235] Re: Keyboard shortcut mapping side effect

[Ragusa]

I just discovered that with the Maj+§ shortcut (Corresponding to °), if
I try to insert an equal sign (=), guake opens too.

As the journalctrl command failed, you will find it as an attached file.


** Attachment added: "journalctl -b --priority=warning --lines=1000"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1728235/+attachment/4998741/+files/journal.txt

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

Title:
  Keyboard shortcut mapping side effect

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

Bug description:
  I have defined a custom shortcut (/usr/bin/guake -t) on the key "§".
  The shortcut § works fine, but if I press the letter "s" on my keyboard, 
Guake is opened as well.

  
  What do I expect:
  > That the letter s writes an s.
  What's happening:
  > Everytime I press "s", guake opens, but I can't use the letter "s" anymore.

  
  I had to map a different shortcut (Maj §) and the "s" works fine.
  PS: I am using the Swiss French keyboard configuration

  Ubuntu 17.10
  gnome-control-center:
Installed: 1:3.26.1-0ubuntu4

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:12:21 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-05-21 (160 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (4 days ago)

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

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

[Desktop-packages] [Bug 1728237] [NEW] After locking the screen to log in again does not work.

[Александр]

Public bug reported:

After locking the screen to log in again does not work. A window appears enter 
password after entering the password, the login attempt is made and re-enter 
the password. When trying to change user input in turn the standard interface 
login, enter the password and everything is repeated again.
However, you can get to the console login and reboot the computer. After the 
reboot, log normal.

Oct 28 18:48:02 aspire kernel: [  132.845148] Could not find key with 
description: [734b90750c0c1853]
Oct 28 18:48:02 aspire kernel: [  132.845155] process_request_key_err: No key
Oct 28 18:48:02 aspire kernel: [  132.845157] Could not find valid key in user 
session keyring for sig specified in mount option: [734b90750c0c1853]
Oct 28 18:48:02 aspire kernel: [  132.845159] One or more global auth toks 
could not properly register; rc = [-2]
Oct 28 18:48:02 aspire kernel: [  132.845162] Error parsing options; rc = [-2]
Oct 28 18:48:25 aspire kernel: [  155.805449] EXT4-fs (sdb1): mounted 
filesystem with ordered data mode. Opts: (null)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evince 3.26.0-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 19:15:03 2017
InstallationDate: Installed on 2015-08-27 (792 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: evince
UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  After locking the screen to log in again does not work.

Status in evince package in Ubuntu:
  New

Bug description:
  After locking the screen to log in again does not work. A window appears 
enter password after entering the password, the login attempt is made and 
re-enter the password. When trying to change user input in turn the standard 
interface login, enter the password and everything is repeated again.
  However, you can get to the console login and reboot the computer. After the 
reboot, log normal.

  Oct 28 18:48:02 aspire kernel: [  132.845148] Could not find key with 
description: [734b90750c0c1853]
  Oct 28 18:48:02 aspire kernel: [  132.845155] process_request_key_err: No key
  Oct 28 18:48:02 aspire kernel: [  132.845157] Could not find valid key in 
user session keyring for sig specified in mount option: [734b90750c0c1853]
  Oct 28 18:48:02 aspire kernel: [  132.845159] One or more global auth toks 
could not properly register; rc = [-2]
  Oct 28 18:48:02 aspire kernel: [  132.845162] Error parsing options; rc = [-2]
  Oct 28 18:48:25 aspire kernel: [  155.805449] EXT4-fs (sdb1): mounted 
filesystem with ordered data mode. Opts: (null)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evince 3.26.0-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 19:15:03 2017
  InstallationDate: Installed on 2015-08-27 (792 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: evince
  UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago)

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

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

[Desktop-packages] [Bug 1728235] [NEW] Keyboard shortcut mapping side effect

[Ragusa]

Public bug reported:

I have defined a custom shortcut (/usr/bin/guake -t) on the key "§".
The shortcut § works fine, but if I press the letter "s" on my keyboard, Guake 
is opened as well.


What do I expect:
> That the letter s writes an s.
What's happening:
> Everytime I press "s", guake opens, but I can't use the letter "s" anymore.


I had to map a different shortcut (Maj §) and the "s" works fine.
PS: I am using the Swiss French keyboard configuration

Ubuntu 17.10
gnome-control-center:
  Installed: 1:3.26.1-0ubuntu4

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 16:12:21 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-05-21 (160 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-10-23 (4 days ago)

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

Title:
  Keyboard shortcut mapping side effect

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

Bug description:
  I have defined a custom shortcut (/usr/bin/guake -t) on the key "§".
  The shortcut § works fine, but if I press the letter "s" on my keyboard, 
Guake is opened as well.

  
  What do I expect:
  > That the letter s writes an s.
  What's happening:
  > Everytime I press "s", guake opens, but I can't use the letter "s" anymore.

  
  I had to map a different shortcut (Maj §) and the "s" works fine.
  PS: I am using the Swiss French keyboard configuration

  Ubuntu 17.10
  gnome-control-center:
Installed: 1:3.26.1-0ubuntu4

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 16:12:21 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-05-21 (160 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-10-23 (4 days ago)

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

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

[Desktop-packages] [Bug 1722151] Re: Incorrect syntax when writing to ~/.pam_environment

[Launchpad Bug Tracker]

This bug was fixed in the package accountsservice - 0.6.42-0ubuntu4

---
accountsservice (0.6.42-0ubuntu4) bionic; urgency=medium

  * debian/patches/0009-language-tools.patch:
- Modification of the update-langlist script due to new
  ~/.pam_environment syntax (LP: #1722151).

 -- Gunnar Hjalmarsson   Fri, 27 Oct 2017 22:02:00
+0200

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

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

Title:
  Incorrect syntax when writing to ~/.pam_environment

Status in accountsservice package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released
Status in accountsservice source package in Artful:
  In Progress
Status in language-selector source package in Artful:
  In Progress

Bug description:
  [Impact]

  When the syntax for the entries in ~/.pam_environment was changed, the
  GUI in language-selector-gnome for maintaining the language priority
  list was broken since language-selector-gnome reads from
  ~/.pam_environment. The language-selector upload to artful makes
  language-selector-gnome handle both the old and the new syntax
  correctly.

  An additional similar change to accountsservice (the update-langlist
  script) is needed; hence also an accountsservice upload to artful.

  [Test Case]

  * Log in to an "Ubuntu on Xorg" session.
  * Open Language Support and find that it appears as if you can only
    set one item before the "English" item in the language list.

  With the new version, it works as expected again.

  [Regression Potential]

  Low. This is necessary to fix the regression caused by the change in
  accountsservice.

  [Original description]

  While investigating bug #1662031, I found out that /usr/share
  /language-tools/save-to-pam-env writes to ~/.pam_environment using an
  incorrect syntax: "VARIABLE=value" on each line. The expected syntax
  is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: accountsservice 0.6.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  9 06:57:17 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (463 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: accountsservice
  UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago)

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

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

[Desktop-packages] [Bug 1718139] Re: Update to version 1.2.1

[Bug Watch Updater]

** Changed in: opus (Debian)
   Status: New => Fix Released

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

Title:
  Update to version 1.2.1

Status in opus package in Ubuntu:
  New
Status in opus package in Debian:
  Fix Released

Bug description:
  The package should be updated to the current last stable version
  (1.2.1).

  The current package version is 1.1.2 (the same as in xenial).
  Version from 1.1.2 to 1.1.5 bring various bug fixes.
  Version 1.2 brings improvements described here:
  https://people.xiph.org/~jm/opus/opus-1.2/

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

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

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

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1725646, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1728233/+attachment/4998712/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1725646
   gnome-control-center crashed with SIGSEGV in g_settings_get_value()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

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

Bug description:
  can-t turn off Airplane mode

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 13:19:49 2017
  ExecutablePath: /usr/bin/gnome-control-center
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f82a7224d10 :  cmp
%rax,(%rdx)
   PC (0x7f82a7224d10) ok
   source "%rax" ok
   destination "(%rdx)" (0x40003) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_boolean () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_settings_get_value()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out

[Dmitrii Shcherbakov]

Hmm, for my installation upgraded from 17.04 it got fixed - I no longer
experience the 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/1716341

Title:
  Settings for external monitor are deleted after reboot, suspension,
  log out

Status in gnome-control-center:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Artful:
  Fix Released

Bug description:
  New Gnome Settings on Ubuntu 17.10

  Settings for external monitor are working but after reboot/suspension
  /log-out log-in, the system will not remember the setup.

  Example:
  1- open Gnome Settings and select "Devices → Displays"
  2- set the external monitor as "Single Display" and click on "Apply"
  3- log-out

  After log-in the laptop monitor will be set as default instead of the
  external monitor.

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

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

[Desktop-packages] [Bug 1728234] [NEW] zooming with mouse wheel seems dysfunctional in Ubuntu's eye of GNOME

[Muelli]

Public bug reported:

I cannot zoom in and out of pictures using the wheel.  Similarly, space bar for 
going to the next picture doesn't work.
The documentation claims that it should work.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: eog 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 28 15:09:19 2017
InstallationDate: Installed on 2017-10-13 (14 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
SourcePackage: eog
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  zooming with mouse wheel seems dysfunctional in Ubuntu's eye of GNOME

Status in eog package in Ubuntu:
  New

Bug description:
  I cannot zoom in and out of pictures using the wheel.  Similarly, space bar 
for going to the next picture doesn't work.
  The documentation claims that it should work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: eog 3.26.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 28 15:09:19 2017
  InstallationDate: Installed on 2017-10-13 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10
  repositories) does not fill the screen at all when snapping the window
  to the right or left side. There are large gaps on the right and
  bottom edges of the terminal window in Wayland. On the same computer,
  with the same version of gnome-terminal in an Xorg gnome-session or
  Xorg ubuntu-session, the window fills screen space entirely and there
  is no problem. I am not using display scaling or hidpi features at
  all, my display resolution is set at default 1080p. This needs to be
  fixed or I'm ditching gnome-terminal.

  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

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

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

[Desktop-packages] [Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

[Launchpad Bug Tracker]

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

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  The Shell Extensions subcategory in GNOME Software is empty. I am
  using the latest (3.26.1-0ubuntu1) GNOME Software package.

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

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

[Desktop-packages] [Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10
  repositories) does not fill the screen at all when snapping the window
  to the right or left side. There are large gaps on the right and
  bottom edges of the terminal window in Wayland. On the same computer,
  with the same version of gnome-terminal in an Xorg gnome-session or
  Xorg ubuntu-session, the window fills screen space entirely and there
  is no problem. I am not using display scaling or hidpi features at
  all, my display resolution is set at default 1080p. This needs to be
  fixed or I'm ditching gnome-terminal.

  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

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

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

[Desktop-packages] [Bug 1722809] Re: GNOME Shell Extensions subcategory is empty in GNOME Software

[Jeremy Bicha]

** Also affects: gnome-software (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  GNOME Shell Extensions subcategory is empty in GNOME Software

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Artful:
  Triaged

Bug description:
  The Shell Extensions subcategory in GNOME Software is empty. I am
  using the latest (3.26.1-0ubuntu1) GNOME Software package.

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

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

[Desktop-packages] [Bug 1728145] Re: gnome-terminal does not fill screen when window snapping on Wayland in Ubuntu 17.10

[Egmont Koblinger]

This is a bug in GTK+, just recently fixed in git. For details, see
https://bugzilla.gnome.org/show_bug.cgi?id=789356
https://bugzilla.gnome.org/show_bug.cgi?id=789357


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

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

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

Title:
  gnome-terminal does not fill screen when window snapping on Wayland in
  Ubuntu 17.10

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland gnome-session or Wayland ubuntu-session in Ubuntu
  17.10, gnome-terminal (v3.24.2 is the version in the 17.10
  repositories) does not fill the screen at all when snapping the window
  to the right or left side. There are large gaps on the right and
  bottom edges of the terminal window in Wayland. On the same computer,
  with the same version of gnome-terminal in an Xorg gnome-session or
  Xorg ubuntu-session, the window fills screen space entirely and there
  is no problem. I am not using display scaling or hidpi features at
  all, my display resolution is set at default 1080p. This needs to be
  fixed or I'm ditching gnome-terminal.

  Expected behavior: gnome-terminal window should fill right/left of screen 
when snapped to corner in a Wayland session
  What happened instead: gnome-terminal window does not fill screen space when 
snapped to right or left edge of desktop on Wayland session, there are large 
gaps below and to the right of the snapped window on either side.

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

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