[Desktop-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

2018-01-19 Thread Paulo Marcel Coelho Aragão
In xubuntu 17.10, kdelibs5-data 4.14.34-0ubuntu2, file
/usr/share/mime/packages/kde.xml still includes MIME types all/all and
all/allfiles.

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in kdelibs:
  Won't Fix
Status in shared-mime-info:
  Confirmed
Status in kde4libs package in Ubuntu:
  Confirmed
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

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

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


[Desktop-packages] [Bug 1744429] [NEW] xorg sometimes freezes up while playing either vlc or youtube

2018-01-19 Thread gregrwm
Public bug reported:

i don't watch heaps, but enough that xorg has frozen up on me about 3
times in the last week both in vlc and youtube.  This time in particular
it was playing youtube when it froze, the sound played on a bit further
then it stopped too, the mouse was still able to move the cursor but
nothing else, for example usually merely moving the mouse would shift
the border highlight to the newly focused window, but even that wouldn't
happen when it froze up.  i logged in via ssh and invoked ubuntu-bug
xorg.  then after that i used the ssh session to kill my window manager,
twm, which caused the xorg session to logout.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Jan 19 15:29:45 2018
InstallationDate: Installed on 2016-10-15 (460 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  xorg sometimes freezes up while playing either vlc or youtube

Status in xorg package in Ubuntu:
  New

Bug description:
  i don't watch heaps, but enough that xorg has frozen up on me about 3
  times in the last week both in vlc and youtube.  This time in
  particular it was playing youtube when it froze, the sound played on a
  bit further then it stopped too, the mouse was still able to move the
  cursor but nothing else, for example usually merely moving the mouse
  would shift the border highlight to the newly focused window, but even
  that wouldn't happen when it froze up.  i logged in via ssh and
  invoked ubuntu-bug xorg.  then after that i used the ssh session to
  kill my window manager, twm, which caused the xorg session to logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Jan 19 15:29:45 2018
  InstallationDate: Installed on 2016-10-15 (460 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744417] 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

2018-01-19 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

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:
  When I install Wine HQ

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Jan 20 01:13:35 2018
  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-pWr1hM/122-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 2016-10-14 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: Upgraded to artful on 2017-10-19 (92 days ago)

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

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


[Desktop-packages] [Bug 1733061] Re: gsd-print-notifications assert failure: *** Error in `/usr/lib/gnome-settings-daemon/gsd-print-notifications': munmap_chunk(): invalid pointer: 0x00007f9884005820

2018-01-19 Thread Launchpad Bug Tracker
[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  gsd-print-notifications assert failure: *** Error in `/usr/lib/gnome-
  settings-daemon/gsd-print-notifications': munmap_chunk(): invalid
  pointer: 0x7f9884005820 ***

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

Bug description:
  Error

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-settings-daemon 3.26.1-0ubuntu5
  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
  AssertionMessage: *** Error in 
`/usr/lib/gnome-settings-daemon/gsd-print-notifications': munmap_chunk(): 
invalid pointer: 0x7f9884005820 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 20:37:11 2017
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
  InstallationDate: Installed on 2017-09-02 (76 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f98940374e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (ar_ptr=0x0, ptr=, str=0x7f9894037800 
"munmap_chunk(): invalid pointer", action=) at malloc.c:5425
   munmap_chunk (p=) at malloc.c:2877
   __GI___libc_free (mem=) at malloc.c:3137
   ?? ()
  Title: gsd-print-notifications assert failure: *** Error in 
`/usr/lib/gnome-settings-daemon/gsd-print-notifications': munmap_chunk(): 
invalid pointer: 0x7f9884005820 ***
  UpgradeStatus: Upgraded to artful on 2017-10-28 (20 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1722487] Re: Failing to open some pictures - Improper call to JPEG library in state 200

2018-01-19 Thread Launchpad Bug Tracker
[Expired for eog (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Failing to open some pictures - Improper call to JPEG library in state
  200

Status in eog package in Ubuntu:
  Expired

Bug description:
  When I am inserting the SD card of my camera in the PC and have a look
  at the pictures, eog sometimes fails to show them, giving this error:
  Improper call to JPEG library in state 200

  I get that error when I am using the keyboard arrows to go back and forth 
between the pictures I took. The next time I try to open the picture, it is 
shown without a problem.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-30 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: eog 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1733251] Re: Nautilus Quick Search Slow with Irrelevant Results

2018-01-19 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Nautilus Quick Search Slow with Irrelevant Results

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  Prior to updating to artful (Nautilus 3.26.0) using the quick search
  took no noticeable time.

  Now its broken. It takes a long time, pulls in all sorts of folders
  from outside the search path, and and is in effect, useless.

  It seems that the quick search now incorrectly initiates a full system
  wide and beyond search when it should be using quick search and not
  leaving the current folder.

  This non-standard / broken behavior results in what used to take zero
  time now being a fruitless and pointless endeavor.  This makes the
  program pointless for anything but the most basic of usage and makes
  it near impossible to navigate larger or complex file structures.

  Description:  Ubuntu 17.10
  Release:  17.10
  nautilus:
Installed: 1:3.26.0-0ubuntu1
Candidate: 1:3.26.0-0ubuntu1
Version table:
   *** 1:3.26.0-0ubuntu1 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/nautilus/+bug/1733251/+subscriptions

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


[Desktop-packages] [Bug 1744425] [NEW] htmldoc no longer handles PNG images correctly

2018-01-19 Thread Bob Pekarske
Public bug reported:

I have a workstation purchased from system76. My disk failed and they
build a new disk with 16.04 on it. I had 16.04 on the previous disk,
altho maybe a few months old.

I installed htmldoc with apt-get, and now when I convert an HTML file
that references a PNG image, the image is very faint an virtually
unreadable. The basic features are there, and the size is about right,
but the image is very bad.

Something in the latest 16.04 seems to have broken htmldoc!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: htmldoc 1.8.27-8ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 19 20:14:23 2018
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: htmldoc
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  htmldoc no longer handles PNG images correctly

Status in htmldoc package in Ubuntu:
  New

Bug description:
  I have a workstation purchased from system76. My disk failed and they
  build a new disk with 16.04 on it. I had 16.04 on the previous disk,
  altho maybe a few months old.

  I installed htmldoc with apt-get, and now when I convert an HTML file
  that references a PNG image, the image is very faint an virtually
  unreadable. The basic features are there, and the size is about right,
  but the image is very bad.

  Something in the latest 16.04 seems to have broken htmldoc!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: htmldoc 1.8.27-8ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 19 20:14:23 2018
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: htmldoc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2018-01-19 Thread jpvrlaone
I had the same problem on my desktop with Ubuntu 16.04 but #32 worked
for me.  It too was driving me crazy.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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


[Desktop-packages] [Bug 1744421] Re: I tried to upgrade from 16.4 to 17.10

2018-01-19 Thread Seth Arnold
Hello, note that apt-get -u dist-upgrade is not actually a supported
mechanism to upgrade from one release to another. The supported
mechanism is via the do-release-upgrade tool in the ubuntu-release-
upgrader-core package.

Probably you can make this work somehow, but it might be best to look
for interactive help in #ubuntu on irc.freenode.net or
https://askubuntu.com.

Thanks

** Information type changed from Private Security to Public

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

Title:
  I tried to upgrade from 16.4 to 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying to upgrade from version 16.04 to 17.10, I used the following
  command line:

  sudo apt update && sudo apt dist -upgrade

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jan 20 00:03:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.10.0-42-generic, x86_64: installed
   virtualbox, 5.0.40, 4.13.0-26-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
  InstallationDate: Installed on 2017-10-27 (84 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=9b0f7d79-6ae1-4287-8ac7-7ca5bec70fb0 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.2B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.54
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.2B:bd06/13/2016:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097810405F00010320180:rvnHewlett-Packard:rn2209:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 097810405F00010320180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan 19 23:59:58 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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


[Desktop-packages] [Bug 675919] The world's travel search engine Skyscanner compares millions of flights to find you the cheapest deal, fast.

2018-01-19 Thread steubens
Whether you want to go to  Tenerife  or  Tokyo, we'll find low cost flights to 
get you there.
We also  find the  cheapest hotels  and car hire  deals.
Just dial: (888) 369-2751.
Skyscanner is  free! When you  find  your flights and dial (888) 369-2751, we 
redirect your call  through directly to the airline  or travel  agent.We 
never charge  you commission.  Nor do we add hidden fees. See more ways we put 
you first.
Acclaimed  flight comparison  Skyscanner  is an award winning site  recommended 
by: The Independent, The Guardian, Which? Travel, BBC Radio 1 and 
more!Skyscanner has been consistently found to  be comprehensive, fast,  
and the  best way to find cheap flights.
Just dial:  (888) 369-2751.
Let’s  get  social! Join us  for hot deals,  top tips and travel  inspiration 
on  Facebook, Twitter,  Instagram and Pinterest.
Find the perfect place to stay
The  Trip by  Skyscanner  community  has  reviewed tens of thousands of hotels 
around the world so you can always find  the perfect place  to stay, based on 
your tribe and your price range.
Simply select your destination,  dial  (888) 369-2751, and you are off!
And  now Trip by Skyscanner searches all the top booking  sites to make  sure 
to always find  you the lowest  price.
Check out some of  our most popular destinations:
Chicago-New York$175.66Los Angeles-San Francisco$103.44Los Angeles-New York$175.66Chicago-Los Angeles$325.92Miami-New York$96.18Atlanta-Chicago$100.05Newark-Toronto$299.18San Francisco-New York City$293.94Los Angeles-Manila$654.67Atlanta-New  York$225.89Atlanta-Orlando$90.78Chicago-Washington DC$195.30New York City-Toronto$119.09New  York  City-Paris$545.40Top Deal 55% Off: Skyscanner's 
Flight Deals.
Primary: (888) 369-2751. 24/7  Support.
Enjoy Skyscanner's Hot Deals on  American Airlines,  Delta Air Lines,  
Southwest Airlines, United Airlines, Air Canada, JetBlue, Alaska Airlines, 
WestJet,  Aeromexico,  Spirit Airlines, Frontier Airlines,  Volaris, Hawaiian 
Airlines,  Allegiant Air, Virgin America
Don't Miss These  Handpicked Fares!

Primary (888) 369-2751. 24/7  Support

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

Title:
  F2/Renaming fonction in Nautilus : General behavior is different
  between the 3 views (list, compact or icons)

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  F2/Renaming fonction in Nautilus : General behavior is different
  between the 3 views (list, compact or icons)

  When we use the "icons" or "compact" view in nautilus and when we try
  to rename (by pressing F2 or right clik -> rename) any file with a 3
  letters extension (.jpg, .svg...whatever), the default selection is
  the text without his extension. OK, great behavior.

  BUT, when we switch to the "list" view, this behevior is different !
  The extension belong to the défault selection.

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

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


[Desktop-packages] [Bug 1744417] 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

2018-01-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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:
  When I install Wine HQ

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Jan 20 01:13:35 2018
  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-pWr1hM/122-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 2016-10-14 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: Upgraded to artful on 2017-10-19 (92 days ago)

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

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


[Desktop-packages] [Bug 1744417] [NEW] 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 o

2018-01-19 Thread Nebojša Stošić
Public bug reported:

When I install Wine HQ

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sat Jan 20 01:13:35 2018
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-pWr1hM/122-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 2016-10-14 (462 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
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: Upgraded to artful on 2017-10-19 (92 days ago)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

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:
  When I install Wine HQ

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Jan 20 01:13:35 2018
  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-pWr1hM/122-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 2016-10-14 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: Upgraded to artful on 2017-10-19 (92 days ago)

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

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


[Desktop-packages] [Bug 1743401] Re: AddressSanitizer: heap-buffer-overflow in libxkbcommon-x11.so

2018-01-19 Thread Oliver Stöneberg
I rebuild the package without optimizations got some more data. The ASAN
out now matches the gdb one

READ of size 9 at 0x6040001944b8 thread T0
#0 0x14454c2 in __interceptor_strndup 
/opt/media/clang_nightly/llvm/utils/release/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:327:3
#1 0x7ffa3f4b06f8 in get_atom_name 
/home/user/libxkbcommon-0.5.0/src/x11/util.c:146
#2 0x7ffa3f4afd63 in get_names 
/home/user/libxkbcommon-0.5.0/src/x11/keymap.c:1092
#3 0x7ffa3f4b026c in xkb_x11_keymap_new_from_device 
/home/user/libxkbcommon-0.5.0/src/x11/keymap.c:1169 

Looking at the variables in the debugger everything seems fine

#7  0x7fffc44236f9 in get_atom_name (conn=0x62aae200, atom=142,
out=0x61bef400) at src/x11/util.c:146
146 *out = strndup(name, length);
(gdb) print length
$1 = 8
(gdb) print name
$2 = 0x6040001944b0 "complete"
(gdb) print name[7]
$3 = 101 'e'
(gdb) print name[8]
$4 = 0 '\000'

But judging from the error message somehow the ASAN peaks beyond its
end.

I was able reproduce this behavior in a small sample and it turns out it
is caused by ASAN_OPTIONS=strict_string_checks=1. So it seems it is a
sanitizer issue. I will bring it up with that team.

Sorry about the apparently faulty report.

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

Title:
  AddressSanitizer: heap-buffer-overflow in libxkbcommon-x11.so

Status in libxkbcommon package in Ubuntu:
  New

Bug description:
  I am running an application which has a feature which utilizes Qt5. For 
testing purposes this application was built with the AddressSanitizer of the 
official clang 5.0.1 binariesfor ubuntu 16.04. This was working fine until a 
few days ago. It started out with another user reporting issues with Qt and the 
pt_BR.UTF-8 locale which I was able to confirm after I installed it. Shorty 
after that I was no longer able to run anything that used the Qt code. I tried 
removing the additional locale or setting a different one via the environment, 
but that didn't help. I also did some changes in the "Text Input" settings like 
removing removing the "English" keyboard layout before I encountered this.
  Unfortunately I didn't have the time yet to set the system back up from 
scratch and try to reproduce what exact change caused this.

  Below I added the traces of ASAN and the debugger.

  The code in question is found in xkbcommon/src/x11/util.c

  length = xcb_get_atom_name_name_length(reply);
  name = xcb_get_atom_name_name(reply);

  *out = strndup(name, length);

  Unfortunately I was not able to see what "name" is, but length was 8.

  lsb_release -rd
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

  libxkbcommon0:
Installed: 0.5.0-1ubuntu2
Candidate: 0.5.0-1ubuntu2
Version table:
   *** 0.5.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  qt5-default:
Installed: 5.5.1+dfsg-16ubuntu7.5
Candidate: 5.5.1+dfsg-16ubuntu7.5
Version table:
   *** 5.5.1+dfsg-16ubuntu7.5 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.1+dfsg-16ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  ==3008==ERROR: AddressSanitizer: heap-buffer-overflow on address 
0x60400015c4b8 at pc 0x01445853 bp 0x7ffd07632920 sp 0x7ffd076320b8
  READ of size 9 at 0x60400015c4b8 thread T0
  #0 0x1445852 in __interceptor___strndup 
/opt/media/clang_nightly/llvm/utils/release/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:337:3
  #1 0x7fc1481fd70e  
(/usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0+0x470e)
  #2 0x7fc1481fcd79 in xkb_x11_keymap_new_from_device 
(/usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0+0x3d79)
  #3 0x7fc149cb9c8f  (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x42c8f)
  #4 0x7fc149cba0ec  (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x430ec)
  #5 0x7fc149cb4931 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, 
bool, unsigned int, char const*) 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x3d931)
  #6 0x7fc149cb7bac in QXcbIntegration::QXcbIntegration(QStringList const&, 
int&, char**) (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x40bac)
  #7 0x7fc149d773ac in _init 
(/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so+0x13ac)
 

[Desktop-packages] [Bug 1518786] Re: Cannot open nautilus "preference settings" under gnome flashback sessi

2018-01-19 Thread Norbert
Also seen on AskUbuntu (https://askubuntu.com/q/997845/66509).

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

Title:
  Cannot open nautilus "preference settings" under gnome flashback sessi

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  There is no button or menu item to open nautilus preference settings
  under Gnome Flashback Session.

  
  Maybe a good solution to show menu always:

  in source code ( nautilus-3.14.2/src/nautilus-window-menus.c  )

  Line 761 =>

  -- if (show_menubar)
  ++ if (TRUE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.14.2-0ubuntu15
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Nov 23 07:09:20 2015
  GsettingsChanges:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority', 'warning'] 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: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   evince 3.18.2-1ubuntu1
   file-roller3.16.4-1ubuntu3
   gnome-terminal 3.18.2-1ubuntu2
   totem  3.18.1-1ubuntu2

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

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


[Desktop-packages] [Bug 1744409] [NEW] Unable to arrange displays in gnome control center with 3 connected monitors and having 1 disabled

2018-01-19 Thread Josh
Public bug reported:

Release: Ubuntu 17.10
Package: gnome-control-center
Version: 1:3.26.2-0ubuntu0.2

Expected to be able to arrange displays via the displays panel when
having three or more displays attached.

Displays are locked place as long as one display is disabled. When all
displays are enabled positioning works as expected, however when one
display is disabled (ex. a docked laptop with two external displays) you
are unable to position displays.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Jan 19 16:51:12 2018
InstallationDate: Installed on 2018-01-19 (0 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2018-01-19 (0 days ago)

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

Title:
  Unable to arrange displays in gnome control center with 3 connected
  monitors and having 1 disabled

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

Bug description:
  Release: Ubuntu 17.10
  Package: gnome-control-center
  Version: 1:3.26.2-0ubuntu0.2

  Expected to be able to arrange displays via the displays panel when
  having three or more displays attached.

  Displays are locked place as long as one display is disabled. When all
  displays are enabled positioning works as expected, however when one
  display is disabled (ex. a docked laptop with two external displays)
  you are unable to position displays.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Jan 19 16:51:12 2018
  InstallationDate: Installed on 2018-01-19 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2018-01-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1744400] [NEW] Wine installation failed

2018-01-19 Thread David Benucci
Public bug reported:

I'm trying to install from WineHQ repository according to these instructions 
https://wiki.winehq.org/Ubuntu but I get this error in apt-get install command:
/tmp/apt-dpkg-install-ei3xN0/168-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
What's wrong?

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Wine installation failed

Status in sane-backends package in Ubuntu:
  New

Bug description:
  I'm trying to install from WineHQ repository according to these instructions 
https://wiki.winehq.org/Ubuntu but I get this error in apt-get install command:
  
/tmp/apt-dpkg-install-ei3xN0/168-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  What's wrong?

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

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


[Desktop-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread Thomas Beyer
thank you #3

But it is more about having wayland as default and not beeing able to
use gparted withing 18.04 LTS!

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1328312] Re: brltty 5.0 is very buggy. Update to 5.1 or later

2018-01-19 Thread Adolfo Jayme
Ubuntu has 5.5 these days (in Bionic).

** Changed in: brltty (Ubuntu)
   Status: New => Fix Released

** Changed in: brltty (Ubuntu)
 Assignee: Stanislav Korymov (st-korymov) => (unassigned)

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

Title:
  brltty 5.0 is very buggy. Update to 5.1 or later

Status in brltty package in Ubuntu:
  Fix Released

Bug description:
  Version 5.0 does not work with the Focus 40 Blue from Freedom
  Scientific. The Grade 2 u.S. English translation table is inaccurate.
  These problems are fixed in version 5.1.

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

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


[Desktop-packages] [Bug 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)

2018-01-19 Thread Adolfo Jayme
** Changed in: brltty (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Please merge brltty (main) 5.5-4 from Debian unstable (main)

Status in brltty package in Ubuntu:
  Fix Committed

Bug description:
  Dear Ubuntu team,

  BRLTTY 5.5 was published in April 2017. It comes with several fixes
  and support of new braille devices.

  Could it be possible to upload it for Ubuntu 18.04 ?

  Best regards.

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

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


[Desktop-packages] [Bug 1744366] Re: xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

2018-01-19 Thread Brian Murray
** Package changed: ubuntu => upower (Ubuntu)

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

Title:
  xfce power manager shows wrong battery life information (Lbuntu
  16.04.3)

Status in upower package in Ubuntu:
  New

Bug description:
  As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
  16.04.3 shows a wrong battery life. What happens is that I plug in the
  laptop, it tells me the battery is 100% I unplug the write and I can
  see after maybe 10 minutes that the battery level lowered.

  I check and it gives me something like 80% and then, suddenly the
  laptop turns of because the battery is discharged.

  When i plug it back it shows as the battery is either charging
  correctly or charging and the percentage is over 70%.

  The battery is a few months old, so I think the problem lies in xfce
  power manager which displays the wrong information.Bug #1216594 opened
  in 2013 is very similar to my case, however that bug report was closed
  not because it was fixed but because it expired after 60 days.

  I tried 'upower -d' and it gives me the same info as the power manager.
  The output was:
  Device: /org/freedesktop/UPower/devices/line_power_ADP1
native-path:  ADP1
power supply: yes
updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Hewlett-Packard
model:Primary
power supply: yes
updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-empty:0 Wh
  energy-full: 26.048 Wh
  energy-full-design:  26.048 Wh
  energy-rate: 20.0392 W
  voltage: 16.444 V
  time to full:11.3 minutes
  percentage:  85%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  151638543485.000  charging
History (rate):
  151638543420.039  charging

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-full: 26.048 Wh
  energy-rate: 20.0392 W
  time to full:11.3 minutes
  percentage:  85%
  icon-name:  'battery-full-charging-symbolic'

  Daemon:
daemon-version:  0.99.4
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  Any ideas?

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

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


[Desktop-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread Curtis Gedak
The upstream GParted team added a work-around to version 0.30.0 to
enable it to run seamlessly under Wayland.

See https://gparted.org/news.php?item=214

Unfortunately the packager for Ubuntu decided to not use the --enable-
xhost-root work-around.

See https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1737248

The consequence is that GParted only runs seamlessly on X, and not on
Wayland.

If you wish to use GParted from live media, then you might consider
using GParted Live.

See https://gparted.org/livecd.php

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1744366] [NEW] xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

2018-01-19 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
16.04.3 shows a wrong battery life. What happens is that I plug in the
laptop, it tells me the battery is 100% I unplug the write and I can see
after maybe 10 minutes that the battery level lowered.

I check and it gives me something like 80% and then, suddenly the laptop
turns of because the battery is discharged.

When i plug it back it shows as the battery is either charging correctly
or charging and the percentage is over 70%.

The battery is a few months old, so I think the problem lies in xfce
power manager which displays the wrong information.Bug #1216594 opened
in 2013 is very similar to my case, however that bug report was closed
not because it was fixed but because it expired after 60 days.

I tried 'upower -d' and it gives me the same info as the power manager.
The output was:
Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:  ADP1
  power supply: yes
  updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   Hewlett-Packard
  model:Primary
  power supply: yes
  updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
warning-level:   none
energy:  22.2592 Wh
energy-empty:0 Wh
energy-full: 26.048 Wh
energy-full-design:  26.048 Wh
energy-rate: 20.0392 W
voltage: 16.444 V
time to full:11.3 minutes
percentage:  85%
capacity:100%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'
  History (charge):
1516385434  85.000  charging
  History (rate):
1516385434  20.039  charging

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   charging
warning-level:   none
energy:  22.2592 Wh
energy-full: 26.048 Wh
energy-rate: 20.0392 W
time to full:11.3 minutes
percentage:  85%
icon-name:  'battery-full-charging-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

Any ideas?

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


** Tags: battery bot-comment lubuntu manager power xfce
-- 
xfce power manager shows wrong battery life information (Lbuntu 16.04.3)
https://bugs.launchpad.net/bugs/1744366
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to upower 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 254171] Re: Nautilus can't properly unmount FUSE file systems

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Nautilus can't properly unmount FUSE file systems

Status in Nautilus:
  Confirmed
Status in Files:
  Invalid
Status in caja package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged
Status in nautilus package in Debian:
  New

Bug description:
  Normal users can create and mount fuser-filesystems, such as encfs. By
  doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly
  show up on the desktop as mounted filesystems.

  However, if you right-click and select "unmount" you get a error-
  message saying you cannot unmount the filesystem, because it does not
  appear in fstab, and you are not root.

  This is factually incorrect -- you *can* unmount the filesystem,
  assuming you're the user who mounted it in the first place, by using
  the command "fusermount -u directoryname"

  Nautilus should recognize this kind of filesystem and call the
  apropriate command for unmounting, so that it would work, instead of
  falsely claiming that you cannot unount the filesystem.

  Tested with encfs, likely to affect other similar filesystems like
  sshfs.

  Affects both Hardy and Intrepid

  Update: Tested with the latest jaunty-alpha, still present.

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

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


[Desktop-packages] [Bug 254171] Re: Nautilus can't properly unmount FUSE file systems

2018-01-19 Thread Norbert
** Tags added: artful trusty xenial zesty

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

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

Title:
  Nautilus can't properly unmount FUSE file systems

Status in Nautilus:
  Confirmed
Status in Files:
  Invalid
Status in caja package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged
Status in nautilus package in Debian:
  New

Bug description:
  Normal users can create and mount fuser-filesystems, such as encfs. By
  doing "encfs ~/somedir ~/some-other-dir", these filesystems correctly
  show up on the desktop as mounted filesystems.

  However, if you right-click and select "unmount" you get a error-
  message saying you cannot unmount the filesystem, because it does not
  appear in fstab, and you are not root.

  This is factually incorrect -- you *can* unmount the filesystem,
  assuming you're the user who mounted it in the first place, by using
  the command "fusermount -u directoryname"

  Nautilus should recognize this kind of filesystem and call the
  apropriate command for unmounting, so that it would work, instead of
  falsely claiming that you cannot unount the filesystem.

  Tested with encfs, likely to affect other similar filesystems like
  sshfs.

  Affects both Hardy and Intrepid

  Update: Tested with the latest jaunty-alpha, still present.

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

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


[Desktop-packages] [Bug 1744368] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от други

2018-01-19 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: попытка перезаписать общий
  «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от других
  экземпляров пакета libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  2123

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 21:23:47 2018
  ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  InstallationDate: Installed on 2017-10-09 (101 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета 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/1744368/+subscriptions

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


[Desktop-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread dino99
** Description changed:

  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  2. install gparted with Software:
  gparted:
-   Installiert:   0.30.0-3ubuntu1
-   Installationskandidat: 0.30.0-3ubuntu1
-   Versionstabelle:
-  *** 0.30.0-3ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installiert:   0.30.0-3ubuntu1
+   Installationskandidat: 0.30.0-3ubuntu1
+   Versionstabelle:
+  *** 0.30.0-3ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified
  
  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.
  
- 
- How to Fix: run xhost +local: before gparted!
+ How to Fix: run xhost +local: before gparted! # this only bypass the
+ wayland restriction; meaning a security violation (not a fix !!! )
  
  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic 

[Desktop-packages] [Bug 1744377] Re: apport has never worked and it just said so one more time.

2018-01-19 Thread Apport retracing service
*** This bug is a duplicate of bug 1727279 ***
https://bugs.launchpad.net/bugs/1727279

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 #1727279, 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/1744377/+attachment/5039711/+files/CoreDump.gz

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

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

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

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

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

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

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

** Tags removed: need-amd64-retrace

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

Title:
  apport has never worked and it just said so one more time.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Everytime I open a browser - FireFox, Chromium, Chrome, Opera - I get
  an error message that the browser failed to open, even while I am
  using the browser!  Then apport says it cannot report the error.  I
  try to close apport, click cancel, click "x" to close the window, it
  ignores all commands and finally shuts down when it has done whatever
  it does.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 63.0.3239.132-0ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CrashCounter: 1
  DRM.card0-DVI-D-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLYUFMzJZTTUTAQOAMx14Ku6Ro1RMmSYPUFQjCACBgIFAgQCVALMAAQEBAQEBOz0AoICAIUAwIDUA/h8RAAAa/QA4PB5REAAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOU5TQzA0MTY4CiAgAUkCAQQAAjqAGHE4LUBYLEUA/h8RAAAeAjqA0HI4LUAQLEWA/h8RAAAeAR0AclHQHiBuKFUA/h8RAAAeAR0AvFLQHiC4KFVA/h8RAAAejArQkCBAMSAMQFUA/h8RAAAYjArQiiDgLRAQPpYA/h8RAAAYBA==
   modes: 2048x1152 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1440x900 
1280x960 1280x800 1280x720 1280x720 1280x720 1024x768 800x600 800x600 720x576 
720x480 720x480 640x480 640x480
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLYQFMzJZTSwTAQMOMx14Ku6Ro1RMmSYPUFQjCACBgIFAgQCVALMAAQEBAQEBOz0AoICAIUAwIDUA/h8RAAAa/QA4PB5REAAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOU5TQTAxODU4CiAgAMU=
   modes: 2048x1152 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 
800x600 800x600 640x480
  Date: Thu Jan 18 18:38:05 2018
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  EcryptfsInUse: Yes
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-04-23 (270 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  InstalledPlugins:
   
  Load-Avg-1min: 2.17
  Load-Processes-Running-Percent:   0.2%
  Lsusb:
   Bus 001 Device 004: ID 0781:5530 SanDisk Corp. Cruzer
   Bus 001 Device 003: ID 1058:0748 Western Digital Technologies, Inc. My 
Passport (WDBKXH, WDBY8L)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq-Presario NC696AA-ABA SR5710Y
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ 
--field-trial-handle=9246880026659797601,17755421342446937564,131072\ 
--use-gl=swiftshader-webgl\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x1002\ --gpu-device-id=0x6779\ --gpu-driver-vendor=Google\ 
Inc.\ --gpu-driver-version=3.3.0.2\ 

[Desktop-packages] [Bug 1744377] [NEW] apport has never worked and it just said so one more time.

2018-01-19 Thread David Parker
Public bug reported:

Everytime I open a browser - FireFox, Chromium, Chrome, Opera - I get an
error message that the browser failed to open, even while I am using the
browser!  Then apport says it cannot report the error.  I try to close
apport, click cancel, click "x" to close the window, it ignores all
commands and finally shuts down when it has done whatever it does.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: chromium-browser 63.0.3239.132-0ubuntu1
ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
Uname: Linux 4.14.0-16-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CrashCounter: 1
DRM.card0-DVI-D-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wBMLYUFMzJZTTUTAQOAMx14Ku6Ro1RMmSYPUFQjCACBgIFAgQCVALMAAQEBAQEBOz0AoICAIUAwIDUA/h8RAAAa/QA4PB5REAAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOU5TQzA0MTY4CiAgAUkCAQQAAjqAGHE4LUBYLEUA/h8RAAAeAjqA0HI4LUAQLEWA/h8RAAAeAR0AclHQHiBuKFUA/h8RAAAeAR0AvFLQHiC4KFVA/h8RAAAejArQkCBAMSAMQFUA/h8RAAAYjArQiiDgLRAQPpYA/h8RAAAYBA==
 modes: 2048x1152 1920x1080 1920x1080 1920x1080 1680x1050 1280x1024 1440x900 
1280x960 1280x800 1280x720 1280x720 1280x720 1024x768 800x600 800x600 720x576 
720x480 720x480 640x480 640x480
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: On
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-VGA-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wBMLYQFMzJZTSwTAQMOMx14Ku6Ro1RMmSYPUFQjCACBgIFAgQCVALMAAQEBAQEBOz0AoICAIUAwIDUA/h8RAAAa/QA4PB5REAAKICAgICAg/ABTeW5jTWFzdGVyCiAg/wBIOU5TQTAxODU4CiAgAMU=
 modes: 2048x1152 1680x1050 1280x1024 1440x900 1280x960 1280x800 1024x768 
800x600 800x600 640x480
Date: Thu Jan 18 18:38:05 2018
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
 
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:
 
EcryptfsInUse: Yes
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2017-04-23 (270 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
InstalledPlugins:
 
Load-Avg-1min: 2.17
Load-Processes-Running-Percent:   0.2%
Lsusb:
 Bus 001 Device 004: ID 0781:5530 SanDisk Corp. Cruzer
 Bus 001 Device 003: ID 1058:0748 Western Digital Technologies, Inc. My 
Passport (WDBKXH, WDBY8L)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Compaq-Presario NC696AA-ABA SR5710Y
ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ 
--field-trial-handle=9246880026659797601,17755421342446937564,131072\ 
--use-gl=swiftshader-webgl\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x1002\ --gpu-device-id=0x6779\ --gpu-driver-vendor=Google\ 
Inc.\ --gpu-driver-version=3.3.0.2\ --gpu-driver-date=2017/04/07\ 
--service-request-channel-token=A5B0DA258D6B13714DFF8F2A47E74579
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.14.0-16-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
Signal: 4
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/chromium-browser/swiftshader/libGLESv2.so
 call_init (l=, argc=argc@entry=11, 
argv=argv@entry=0x7ffd205bb4d8, env=env@entry=0x7ffd205bb538) at dl-init.c:72
 call_init (env=0x7ffd205bb538, argv=0x7ffd205bb4d8, argc=11, l=) at dl-init.c:30
 _dl_init (main_map=main_map@entry=0x5570146736d0, argc=11, 
argv=0x7ffd205bb4d8, env=0x7ffd205bb538) at dl-init.c:120
 dl_open_worker (a=a@entry=0x7ffd205ba2b0) at dl-open.c:575
Title: chromium-browser crashed with SIGILL in call_init()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/19/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: V5.36
dmi.board.name: Iris8
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrV5.36:bd11/19/2008:svnCompaq-Presario:pnNC696AA-ABASR5710Y:pvr:rvnECS:rnIris8:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.family: 103C_53316J
dmi.product.name: NC696AA-ABA SR5710Y
dmi.sys.vendor: Compaq-Presario
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-crash bionic need-amd64-retrace package-from-proposed

** Information type changed from Private to Public

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

Title:
  apport has never worked and it just said so one more time.

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Everytime I open a browser - 

[Desktop-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread Thomas Beyer
I added wayland becauce there is no problem with Xorg-Windowsmanager
only with (default) wayland and the suggested workaround with xhost +

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
Installiert:   0.30.0-3ubuntu1
Installationskandidat: 0.30.0-3ubuntu1
Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  
  How to Fix: run xhost +local: before gparted!

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1744368] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от дру

2018-01-19 Thread vladislav
Public bug reported:

2123

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
Uname: Linux 4.13.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 19 21:23:47 2018
ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
InstallationDate: Installed on 2017-10-09 (101 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
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: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package 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/1744368

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: попытка перезаписать общий
  «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от других
  экземпляров пакета libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  2123

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 21:23:47 2018
  ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  InstallationDate: Installed on 2017-10-09 (101 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета 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/1744368/+subscriptions

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


[Desktop-packages] [Bug 1744352] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от други

2018-01-19 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: попытка перезаписать общий
  «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от других
  экземпляров пакета libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  Uname: Linux 4.14.4-041404-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 19:22:55 2018
  ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  UpgradeStatus: Upgraded to artful on 2018-01-17 (1 days ago)

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

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


[Desktop-packages] [Bug 1690280] Re: Classic confined snaps don't install

2018-01-19 Thread Ken VanDine
I've uploaded this with a revised changelog.

** Changed in: gnome-software (Ubuntu Xenial)
   Importance: High => Critical

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

Title:
  Classic confined snaps don't install

Status in GNOME Software:
  Confirmed
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  In Progress
Status in gnome-software source package in Zesty:
  Fix Committed
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Apps that use classic confinement show up in search results but don't install.

  [Test Case]
  1. Open GNOME Software
  2. Search for a classic snap, e.g. "atom"
  3. Install snap

  Expected result:
  Either:
  a) Snap is installed
  b) Snap is not installed and error given
  c) Snap is installed but user needs to provide some sort of confirmation 
since it is not confined.

  Observed result:
  Snap is not installed, no error given.

  [Regression Potential]
  Patch changes the code path used to request installation of all snap 
packages.  Ensure that strict confined snaps continue to be installed with 
correct confinement.

  For example, try installing "ohmygiraffe" via gnome-software, then run
  "snap info ohmygiraffe" from a terminal.  The "installed:" line should
  not include the word "classic".

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

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


[Desktop-packages] [Bug 820709] Re: "Burn Several Disks' button doesn't work.

2018-01-19 Thread Christian Romberg
Same here, Ubuntu 17.04 with Brasero 3.12.1.

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

Title:
  "Burn Several Disks' button doesn't work.

Status in Brasero:
  New
Status in brasero package in Ubuntu:
  Triaged
Status in brasero package in Debian:
  Confirmed

Bug description:
  I created a playlist of 42 songs in Rhythmbox and want to burn it. I
  click on the 'Burn' button and Brasero opens. Brasero warns me that
  there isn't enough room on the disk and asks if I want to burn on
  multiple disks. I expected this. So i click on the 'Burn Several
  Disks' button and nothing happens. I found out that this happens with
  all the Linux versions, not just Ubuntu, so it's not an OS bug.

  1. OS = Ubuntu 11.04
  2. Brasero ver = 2.32.1-0ubuntu2 
  3. I expected the button to work.
  4. It didn't!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: brasero 2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic i686
  Architecture: i386
  Date: Wed Aug  3 18:20:41 2011
  ExecutablePath: /usr/bin/brasero
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: brasero
  UpgradeStatus: Upgraded to natty on 2011-04-30 (96 days ago)

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

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


[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work

2018-01-19 Thread dmitry
"Codec: Realtek ALC233"

It's ALC3248 really. Alsa identifies it wrong.

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

Title:
  Lenovo Y700-17ISK subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Problem: Notebook subwoofer doesn't work.

  Judging from alsa-info.sh output, there is no pin declared for the bass 
output by BIOS.
  Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:02:21 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1744355] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat

2018-01-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  The only thing I know is error message about conflict about network.
  And then, the system asked me about to send a report and I agreed it.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 14:28:22 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-19 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  IpRoute:
   default via 192.168.0.1 dev enp0s25 proto dhcp src 192.168.0.10 metric 100 
   192.168.0.0/24 dev enp0s25 proto kernel scope link src 192.168.0.10 
   192.168.0.1 dev enp0s25 proto dhcp scope link src 192.168.0.10 metric 100
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----   
   enp0s25  ethernet  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--  ----   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

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

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


[Desktop-packages] [Bug 1744355] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit st

2018-01-19 Thread Evaldo Miorim Sobral
Public bug reported:

The only thing I know is error message about conflict about network. And
then, the system asked me about to send a report and I agreed it.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 19 14:28:22 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-01-19 (0 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
IpRoute:
 default via 192.168.0.1 dev enp0s25 proto dhcp src 192.168.0.10 metric 100 
 192.168.0.0/24 dev enp0s25 proto kernel scope link src 192.168.0.10 
 192.168.0.1 dev enp0s25 proto dhcp scope link src 192.168.0.10 metric 100
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
nmcli-dev:
 DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
 wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
 enp0s25  ethernet  unmanaged /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
 lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
 running  1.8.4disconnected  started  unknown   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  The only thing I know is error message about conflict about network.
  And then, the system asked me about to send a report and I agreed it.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 14:28:22 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-01-19 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  IpRoute:
   default via 192.168.0.1 dev enp0s25 proto dhcp src 192.168.0.10 metric 100 
   192.168.0.0/24 dev enp0s25 proto kernel scope link src 192.168.0.10 
   192.168.0.1 dev enp0s25 proto dhcp scope link src 192.168.0.10 metric 100
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: NAME  UUID  TYPE  TIMESTAMP  TIMESTAMP-REAL  AUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH  ACTIVE  DEVICE  STATE  ACTIVE-PATH  
SLAVE
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----   
   enp0s25  ethernet  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--  ----   
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI 

[Desktop-packages] [Bug 1220764] Re: Rhythmbox does not add VBR headers when ripping CDs to MP3

2018-01-19 Thread Derek L
This problem still occurs in 17.10.  I just ripped a kids music disc via
Rhythmbox using MP3 default settings (=VBR/medium).  Files are perceived
(by RB and nautilus) as 32Kbps:

% file 19\ -\ Five\ Days\ Old.mp3 
19 - Five Days Old.mp3: Audio file with ID3 version 2.3.0, contains:MPEG ADTS, 
layer III, v1,  32 kbps, 44.1 kHz, JntStereo

% mp3val 19\ -\ Five\ Days\ Old.mp3
Analyzing file "19 - Five Days Old.mp3"... 
WARNING: "/home/ddl/Music/Laurie Berkner/Lullabies/19 - Five Days Old.mp3": VBR 
detected, but no VBR header is present. Seeking may not work properly.  
  
INFO: "/home/ddl/Music/Laurie Berkner/Lullabies/19 - Five Days Old.mp3": 7087 
MPEG frames (MPEG 1 Layer III), +ID3v2, no VBR header   

I can partly "fix" file metadata (via vbrfix and mp3val -f), but
nautilus and RB then display bitrate as "unknown".

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

Title:
  Rhythmbox does not add VBR headers when ripping CDs to MP3

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  When ripping CDs to MP3 using Rhythmbox, by default they are VBR,
  because this is the default preset that is used in
  /usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs (cbr=false). The
  problem is that the VBR headers aren't added to the MP3 files, for
  example:

  $ mp3val 01\ -\ Gregory\ Alan\ Isakov\ -\ Dandelion\ Wine.mp3 
  Analyzing file "01 - Gregory Alan Isakov - Dandelion Wine.mp3"...
  WARNING: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern 
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": VBR detected, but no 
VBR header is present. Seeking may not work properly.
  INFO: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern 
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": 9559 MPEG frames 
(MPEG 1 Layer III), +ID3v2, no VBR header
  Done!

  This causes most programs to report incorrect track lengths, including
  Rhythmbox itself and Ubuntu's default Nautilus file manager. This
  seems to be a huge oversight considering this is the default behavior
  using the default apps. I'm not sure when this started because I only
  use the LTS versions of Ubuntu, but I know it wasn't a problem in
  10.04, because it was using a gstreamer pipeline with xingmux as
  opposed to gstreamer presets, which from what I understand don't
  support xingmux (which I believe adds the VBR headers).

  I currently have to fix any MP3s that I generate with Rhythmbox like
  so:

  sudo apt-get install vbrfix
  cd /path/to/mp3s
  find . -type f -iname '*.mp3' -exec vbrfix {} {} \;
  rm vbrfix.log vbrfix.tmp

  This bug is related to:
  https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/945987

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox-data 2.96-0ubuntu4.3 [modified: 
usr/share/gstreamer-0.10/presets/GstLameMP3Enc.prs 
usr/share/rhythmbox/rhythmbox.gep]
  ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17
  Uname: Linux 3.5.0-39-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Wed Sep  4 09:54:54 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-07-09 (12 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: rhythmbox 3.0.2-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1744352] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от дру

2018-01-19 Thread veter
Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
Uname: Linux 4.14.4-041404-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 19 19:22:55 2018
ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
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: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
UpgradeStatus: Upgraded to artful on 2018-01-17 (1 days ago)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful third-party-packages

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: попытка перезаписать общий
  «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от других
  экземпляров пакета libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  Uname: Linux 4.14.4-041404-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 19:22:55 2018
  ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  UpgradeStatus: Upgraded to artful on 2018-01-17 (1 days ago)

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

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


[Desktop-packages] [Bug 1090541] Re: Problems uploading to ftp server

2018-01-19 Thread Vej
Closing as outdated for the upstream package of Ubuntu.

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Problems uploading to ftp server

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Invalid
Status in deja-dup package in Ubuntu:
  Invalid
Status in Arch Linux:
  New

Bug description:
  Description:  Ubuntu 12.10
  deja-dup  24.0-0ubuntu1
  duplicity 0.6.19-0ubuntu2

  
  Im uploading my backups to a ftp server (Dlink DNS-323) and since Ubuntu 
12.10 the backup hangs at uploading and nothing happens. According to the 
logfile of the ftp the last duplicity-inc..to..vol.difftar.gz hasnt been 
uploaded 
  the last duplicity-inc..to..vol.difftar.gz can be found on the ftp server but 
with size 0
  it looks like it only uploads 3-4 duplicity-inc..to..vol.difftar.gz before it 
hangs.  

  1st debug run
  DUPLICITY: INFO 2 4929484316
  DUPLICITY: . Processed volume 14

  DUPLICITY: DEBUG 1
  DUPLICITY: . Registering (mktemp) temporary file 
/tmp/duplicity-xodUb_-tempdir/mktemp-xsAFTU-11

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing 
ftp://backup@192.168.0.199/HP-Mini-Marijo/duplicity-inc.20121210T045327Z.to.20121214T191855Z.vol15.difftar.gz

  2nd debug run (previus session terminated with resume later)
  DUPLICITY: INFO 2 5135117373
  DUPLICITY: . Processed volume 18

  DUPLICITY: DEBUG 1
  DUPLICITY: . Registering (mktemp) temporary file 
/tmp/duplicity-RK7THk-tempdir/mktemp-zO9Z_p-6

  DUPLICITY: INFO 11
  DUPLICITY: . AsyncScheduler: running task synchronously (asynchronicity 
disabled)

  DUPLICITY: INFO 1
  DUPLICITY: . Writing 
ftp://backup@192.168.0.199/HP-Mini-Marijo/duplicity-inc.20121210T045327Z.to.20121214T191855Z.vol19.difftar.gz

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

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


[Desktop-packages] [Bug 985512] Re: support system backups (set up a backup run by root)

2018-01-19 Thread Vej
** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  support system backups (set up a backup run by root)

Status in Déjà Dup:
  Confirmed
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  
  It would be great if you could "fix Deja Dup to ask for permission to read 
things it can't." (From answer to question #67726).

  
  Also from that thread: 
  ---
  This is what I'm using now:

  sudo duplicity / scp://username@host/backupdirectory/duplicity/
  --asynchronous-upload --exclude /tmp --exclude /proc --exclude /media
  --exclude /mnt --exclude /cdrom --exclude /sys --gpg-options
  ='--compress-algo=bzip2 --bzip2-compress-level=9' -v5

  I can *almost* do this via [deja-dup], but when I run it as root it I don't 
have access to the typical Nautilus style "Connect to Server" options. It seams 
there isn't a way to specify an scp destination. Then there's also the 
scheduling issue mentioned above.
  ---

  Deja-dup might not have to run as root just to go through the GUI to
  configure the system backup (profile). It might be enough to be able
  to trigger backups from the command line as root (su, sudo), or by
  dropping a script into /etc/cron.daily.

  OTOH with backintime you run it as root to create the config files for
  root.

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

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


[Desktop-packages] [Bug 1734499] Re: InvalidBackendURL: missing // - relative paths not supported for scheme gio+invalid: gio+invalid://

2018-01-19 Thread Vej
*** This bug is a duplicate of bug 1715582 ***
https://bugs.launchpad.net/bugs/1715582

This should be "fixed again" in 37.1-0ubuntu1, see bug #1715582.

Setting this as a duplicate.

Best

Vej

** This bug has been marked a duplicate of bug 1715582
   "Operation not supported by backend" when backing up to smb server

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

Title:
   InvalidBackendURL: missing // - relative paths not supported for
  scheme gio+invalid: gio+invalid://

Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  Same problem as https://bugs.launchpad.net/deja-dup/+bug/1717230 but
  opening a new bug because as far as I know that's standard practice
  when a bug is apparently not fixed by a previous fix? If that's not
  correct, then instead the status of the bug needs to be changed back
  to Confirmed from Fix Released.

  I ran into this bug by plugging in my external drive (with a backup on
  it) and trying to (update my) back up to it.

  The bug is potentially a regression in 36.2-0ubuntu1 (since the bug
  was apparently fixed in 36.1-0ubuntu1).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 02:39:52 2017
  InstallationDate: Installed on 2017-08-03 (114 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to artful on 2017-10-21 (35 days ago)

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

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


[Desktop-packages] [Bug 1738664] 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

2018-01-19 Thread dino99
** Description changed:

+ 
+ ***
+ to get a workaround, try:
+ 
+ sudo apt-get -o Dpkg::Options::="--force-overwrite" install --reinstall
+ sane-backends
+ 
+ ***
+ 
+ 
  An error occured
  error:broken count>0
  
  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 18 01:06:19 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-baiIM1/11-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
+  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-baiIM1/11-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-12-16 (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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
-  dpkg 1.18.24ubuntu1
-  apt  1.5.1
+  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)

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

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:
  Confirmed

Bug description:
  
  ***
  to get a workaround, try:

  sudo apt-get -o Dpkg::Options::="--force-overwrite" install
  --reinstall sane-backends

  ***

  
  An error occured
  error:broken count>0

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Dec 18 01:06:19 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-baiIM1/11-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-12-16 (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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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/1738664/+subscriptions

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


[Desktop-packages] [Bug 1533780] Re: package libsane 1.0.25+git20150528-1ubuntu2 [modified: lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/

2018-01-19 Thread dino99
** Changed in: sane-backends (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package libsane 1.0.25+git20150528-1ubuntu2 [modified:
  lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is
  different from other instances of package libsane:i386

Status in sane-backends package in Ubuntu:
  Incomplete

Bug description:
  sane-backends-extras

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: libsane 1.0.25+git20150528-1ubuntu2 [modified: 
lib/udev/rules.d/40-libsane.rules]
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Jan 13 23:33:09 2016
  DuplicateSignature: package:libsane:1.0.25+git20150528-1ubuntu2 [modified: 
lib/udev/rules.d/40-libsane.rules]:trying to overwrite shared 
'/lib/udev/rules.d/40-libsane.rules', which is different from other instances 
of package libsane:i386
  ErrorMessage: trying to overwrite shared 
'/lib/udev/rules.d/40-libsane.rules', which is different from other instances 
of package libsane:i386
  InstallationDate: Installed on 2015-12-22 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: sane-backends
  Title: package libsane 1.0.25+git20150528-1ubuntu2 [modified: 
lib/udev/rules.d/40-libsane.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/40-libsane.rules', which is different from 
other instances of package libsane: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/1533780/+subscriptions

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


[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-19 Thread Kenneth Loafman
- Please post the duplicity command line.

- Please do an 'ls -l' or equivalent of the backup target directory and
add as an attachment to this bug report.  (see green + at bottom of
display).

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  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 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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


[Desktop-packages] [Bug 1744336] 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

2018-01-19 Thread dino99
*** This bug is a duplicate of bug 1725928 ***
https://bugs.launchpad.net/bugs/1725928

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files

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

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:
  Error reported whilst installing Wine 3.0 from ppa.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 08:21:25 2018
  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-Xhw7RX/68-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-21 (89 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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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/1744336/+subscriptions

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


[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-19 Thread Olivier Crête
Here is a slightly different traceback

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1559, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1545, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1394, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1420, in do_backup
action).set_values()
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 720, 
in set_values
self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 846, 
in get_backup_chains
add_to_sets(f)
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 834, 
in add_to_sets
if set.add_filename(filename):
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 102, 
in add_filename
self.set_manifest(filename)
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 153, 
in set_manifest
self.set_files_changed()
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 129, 
in set_files_changed
mf = self.get_manifest()
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 256, 
in get_manifest
return self.get_local_manifest()
  File "/usr/lib64/python2.7/site-packages/duplicity/collections.py", line 234, 
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib64/python2.7/site-packages/duplicity/manifest.py", line 201, in 
from_string
for match in vi_iterator:
 MemoryError


With the matching status after this failure:

Warning, found incomplete backup sets, probably left from aborted session
Last full backup date: Fri Jan  5 18:45:00 2018
Collection Status
-
Connecting with backend: BackendWrapper
Archive dir: 
Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-
Chain start time: Fri Jan  5 18:45:00 2018
Chain end time: Wed Jan 17 16:44:04 2018
Number of contained backup sets: 2
Total number of contained volumes: 1741
 Type of backup set:Time:  Num volumes:
Full Fri Jan  5 18:45:00 2018  1628
 Incremental Wed Jan 17 16:44:04 2018   113
-
Also found 0 backup sets not part of any chain,
and 1 incomplete backup set.
These may be deleted by running duplicity with the "cleanup" command.

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  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 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in 

[Desktop-packages] [Bug 1744340] [NEW] missing models.dat file

2018-01-19 Thread Moses Moore
Public bug reported:

Most of the hp-* commands report "error: Unable to locate models.dat
file", and are unusable.  The "base/models.py" python module expects to
find models.dat somewhere near /usr/share/hplip/models/models.dat"


Sample error message:

# hp-setup 002:034
error: Unable to locate models.dat file

HP Linux Imaging and Printing System (ver. 3.17.7)
Printer/Fax Setup Utility ver. 9.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Searching for device...
Traceback (most recent call last):
  File "/usr/share/hplip/base/models.py", line 539, in __getitem__
return self.__cache[model]
KeyError: 'hp_laserjet_professional_p1102w'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/hp-setup", line 317, in 
dlg = ui.SetupDialog(None, param, jd_port, device_uri, remove)
  File "/usr/share/hplip/ui5/setupdialog.py", line 189, in __init__
self.initUi()
  File "/usr/share/hplip/ui5/setupdialog.py", line 221, in initUi
self.initDiscoveryPage()
  File "/usr/share/hplip/ui5/setupdialog.py", line 259, in initDiscoveryPage
if self.manualDiscovery():
  File "/usr/share/hplip/ui5/setupdialog.py", line 339, in manualDiscovery
device_uri, sane_uri, fax_uri = device.makeURI(self.param, self.jd_port)
  File "/usr/share/hplip/base/device.py", line 416, in makeURI
mq = queryModelByURI(cups_uri)
  File "/usr/share/hplip/base/device.py", line 457, in queryModelByURI
return queryModelByModel(model)
  File "/usr/share/hplip/base/device.py", line 446, in queryModelByModel
return model_dat[model]
  File "/usr/share/hplip/base/models.py", line 545, in __getitem__
if self.read_section(self.released_dat, model):
  File "/usr/share/hplip/base/models.py", line 455, in read_section
fd = open(filename)
TypeError: expected str, bytes or os.PathLike object, not NoneType

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: hplip 3.17.7+repack0-3
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CupsErrorLog: E [19/Jan/2018:09:33:03 -0500] [Job 175] Stopping unresponsive 
job.
Date: Fri Jan 19 10:40:37 2018
InstallationDate: Installed on 2016-06-05 (593 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: ASUSTeK Computer Inc. G73Sw
Papersize: letter
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/xubuntu--vg-root ro nosplash vga=773 acpi_osi=Linux
SourcePackage: hplip
UpgradeStatus: Upgraded to artful on 2017-10-22 (89 days ago)
dmi.bios.date: 02/10/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G73Sw.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G73Sw
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.:bvrG73Sw.205:bd02/10/2011:svnASUSTeKComputerInc.:pnG73Sw:pvr1.0:rvnASUSTeKComputerInc.:rnG73Sw:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G73Sw
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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

Title:
  missing models.dat file

Status in hplip package in Ubuntu:
  New

Bug description:
  Most of the hp-* commands report "error: Unable to locate models.dat
  file", and are unusable.  The "base/models.py" python module expects
  to find models.dat somewhere near /usr/share/hplip/models/models.dat"

  
  Sample error message:

  # hp-setup 002:034
  error: Unable to locate models.dat file

  HP Linux Imaging and Printing System (ver. 3.17.7)
  Printer/Fax Setup Utility ver. 9.0

  Copyright (c) 2001-15 HP Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Searching for device...
  Traceback (most recent call last):
File "/usr/share/hplip/base/models.py", line 539, in __getitem__
  return 

[Desktop-packages] [Bug 1644662] Re: Icons missing when appearance setting is "high contrast"

2018-01-19 Thread David Coronel
** Attachment added: "highcontrast-icontheme-systemsettings.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1644662/+attachment/5039569/+files/highcontrast-icontheme-systemsettings.png

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

Title:
  Icons missing when appearance setting is "high contrast"

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

Bug description:
  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

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

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


[Desktop-packages] [Bug 1644662] Re: Icons missing when appearance setting is "high contrast"

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Icons missing when appearance setting is "high contrast"

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

Bug description:
  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

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

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


[Desktop-packages] [Bug 1644662] Re: Icons missing when appearance setting is "high contrast"

2018-01-19 Thread David Coronel
It looks like after switching to the HighContrast theme in Appearance,
'Adwaita' is being set as the icon theme in dconf. We think it's not
Adwaita that should be used, but rather the HighContrast icon theme.

You can use the unity-tweak-tool to change the icon theme to
highcontrast and notice that the situation is much better. After a
reboot (and after enabling the highcontrast icon theme with unity-tweak-
tool) I get almost all the icons in high contrast.

I think if we could just use the high contrast icon theme when clicking
the high contrast theme in appearance, it'd be much better already.

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

Title:
  Icons missing when appearance setting is "high contrast"

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

Bug description:
  To reproduce this:

  Open System Settings.

  Click Appearance

  Theme: High Contrast.

  Click All Settings tab:

  Many icons are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 24 14:45:30 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-06 (537 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
   LANG=en_CA.UTF-8
   LANGUAGE=en_CA:en
   XDG_RUNTIME_DIR=
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago)

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

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


[Desktop-packages] [Bug 1744336] 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

2018-01-19 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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:
  Error reported whilst installing Wine 3.0 from ppa.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 08:21:25 2018
  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-Xhw7RX/68-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-21 (89 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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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/1744336/+subscriptions

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


[Desktop-packages] [Bug 1744336] [NEW] 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 o

2018-01-19 Thread rbmorse
Public bug reported:

Error reported whilst installing Wine 3.0 from ppa.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Jan 19 08:21:25 2018
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-Xhw7RX/68-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-21 (89 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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
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)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful package-conflict

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

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:
  Error reported whilst installing Wine 3.0 from ppa.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 19 08:21:25 2018
  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-Xhw7RX/68-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-21 (89 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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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/1744336/+subscriptions

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libjogl2-java (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libjogl2-java (Ubuntu Artful)
   Status: New => Confirmed

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode

2018-01-19 Thread connor
This bug is driving me nuts, I've lost my data countless times because I
always forget to *avoid* using VLC in fullscreen mode and to leave the
damn position cursor alone. Sometimes I can kill vlc and save, other
times it just freezes and I have to say goodbye to whatever I was
working on.

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

Title:
  VLC under Wayland causes system freezes in fullscreen mode

Status in gnome-shell package in Ubuntu:
  Invalid
Status in vlc package in Ubuntu:
  Fix Released
Status in vlc package in Debian:
  Fix Released

Bug description:
  Ubuntu version: 17.10 (most recent updates as of October 3rd)
  vlc version:  2.2.6-6

  Whan I expect to happen: When playing a video in vlc and switching to
  fullscreen mode everything should work fine. Also when changing to a
  different position of a movie in fullscreen I expect the player to
  just switch to that position.

  What actually happens: It seems to depend a little on the file type of
  the video, mostly I get problems when going to fullscreen mode and
  then switching to a different position with the playback position bar.
  With some videos it was even enough to just open the fullscreen mode.
  The video freezes just displaying a frame while the audio keeps
  playing. The computer does not react any more to mouse or keyboard
  input, I have to perform a hard reboot.

  This problem only appears under the Wayland session, in the Xorg session 
everything works fine as expected.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-30 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: vlc 2.2.6-6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Confirmed
Status in scilab package in Ubuntu:
  Confirmed
Status in libjogl2-java source package in Xenial:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in scilab source package in Xenial:
  Confirmed
Status in libjogl2-java source package in Artful:
  Confirmed
Status in mesa source package in Artful:
  Confirmed
Status in scilab source package in Artful:
  Confirmed
Status in scilab package in Debian:
  Fix Released

Bug description:
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped 
at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
at 
com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
at java.security.AccessController.doPrivileged(Native Method)
at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
at org.scilab.modules.gui.SwingView.(Unknown Source)
at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  
  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: scilab 5.5.2-2ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jan 12 12:02:32 2018
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2018-01-19 Thread Timo Aaltonen
Hello Alfonso, or anyone else affected,

Accepted modemmanager into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.6.4-1ubuntu0.16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Committed
Status in libqmi source package in Xenial:
  Fix Committed
Status in modemmanager source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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


[Desktop-packages] [Bug 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)

2018-01-19 Thread Julian Andres Klode
Uploaded.

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

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

Title:
  Please merge brltty (main) 5.5-4 from Debian unstable (main)

Status in brltty package in Ubuntu:
  Fix Committed

Bug description:
  Dear Ubuntu team,

  BRLTTY 5.5 was published in April 2017. It comes with several fixes
  and support of new braille devices.

  Could it be possible to upload it for Ubuntu 18.04 ?

  Best regards.

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

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


[Desktop-packages] [Bug 1741070] Re: Please merge brltty (main) 5.5-4 from Debian unstable (main)

2018-01-19 Thread Julian Andres Klode
But not tested apart from build, and install. Just a lot of diff reading
to make sure I caught stuff.

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

Title:
  Please merge brltty (main) 5.5-4 from Debian unstable (main)

Status in brltty package in Ubuntu:
  Fix Committed

Bug description:
  Dear Ubuntu team,

  BRLTTY 5.5 was published in April 2017. It comes with several fixes
  and support of new braille devices.

  Could it be possible to upload it for Ubuntu 18.04 ?

  Best regards.

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

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


[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2018-01-19 Thread Timo Aaltonen
Hello Alfonso, or anyone else affected,

Accepted libqmi into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libqmi/1.16.2-1ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Committed
Status in libqmi source package in Xenial:
  Fix Committed
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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


[Desktop-packages] [Bug 1699033] Re: Two-finger right click does not work in 17.10 gnome-shell

2018-01-19 Thread Tomjleo
Thanks Daniel van Vugt! Ubuntu Tweaks "gnome-tweak-tool" workaround
fixed this issue for me.

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

Title:
  Two-finger right click does not work in 17.10 gnome-shell

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Using two fingers on the clickpad to right click does not work in
  gnome-shell.

  It seems to be defaulting to the old-style single finger click in the
  bottom right corner to do a right click.

  Workaround:
  gnome-tweak-tool > Keyboard & Mouse > Touchpad > Click Method = Fingers

  Gsettings diff:
  < org.gnome.desktop.peripherals.touchpad click-method 'default'
  ---
  > org.gnome.desktop.peripherals.touchpad click-method 'fingers'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-7.12-generic 4.11.6
  Uname: Linux 4.11.0-7-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 20 14:50:10 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-06-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1741070] Re: New upstream release 5.5

2018-01-19 Thread Julian Andres Klode
** Changed in: brltty (Ubuntu)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

** Summary changed:

- New upstream release 5.5
+ Please merge brltty (main) 5.5-4 from Debian unstable (main)

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

Title:
  Please merge brltty (main) 5.5-4 from Debian unstable (main)

Status in brltty package in Ubuntu:
  New

Bug description:
  Dear Ubuntu team,

  BRLTTY 5.5 was published in April 2017. It comes with several fixes
  and support of new braille devices.

  Could it be possible to upload it for Ubuntu 18.04 ?

  Best regards.

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

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


[Desktop-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series

2018-01-19 Thread Timo Aaltonen
Hello Alfonso, or anyone else affected,

Accepted libmbim into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libmbim/1.14.0-1ubuntu0.16.04.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed verification-needed-xenial

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

Title:
  Please update modemmanager in xenial to the 1.6 series

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Xenial:
  Fix Committed
Status in libqmi source package in Xenial:
  New
Status in modemmanager source package in Xenial:
  New

Bug description:
  [Impact]

   * the new modemmanager packages bring in DW5816 supporting.
   * These modemmanager packages is needed to support new devices.

  [Test Case]

   * install modemmanager and it's dependencies from -proposed
  libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1
  libmbim-proxy 1.14.0-1ubuntu0.16.04.1
  libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1
  libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1
  libqmi-proxy 1.16.2-1ubuntu0.16.04.1
  modemmanager 1.6.4-1ubuntu0.16.04.1
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-manager, 
gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies if 
any of the required features have been changed/removed, so besides regular 
testing a general dogfooding session with the new modemmanager is advised.

  [Original Description]

  We would like to upgrade xenial to 1.6 series so it supports the same
  modems as the modem-manager snap, specifically some new Sierra modems
  (HL8548 and others from HL series, popular in IoT devices). These are
  the packages that would need to be updated:

  libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap
  libqmi: 1.12.6-1 in xenial, 1.16.2 in snap
  modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap

  This is also related to bug #1693756 which includes a subset of
  patches of what would be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions

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


[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2018-01-19 Thread Pawel Duda
Solution:

-install nvidia 390 (or any older - check or switch using "Additional Drivers" 
app on Ubuntu ), and then, install:
-DisplayLink USB Graphics Software for Ubuntu 4.1 (or newer I guess)

Restart and done!

--
Key here as it seems is that you need to:

1) update graphic card's driver first
2) then uninstall current display link drivers  (sudo displaylink-installer 
uninstall)
3) install the display link drivers for Ubuntu (that is important - it must be 
last thing)

I have two additional monitors and 16.04 Ubuntu.

Write to me: acidosen@.com if it worked for you

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2018-01-19 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Fix Released => Confirmed

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

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

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

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

  Regression Potential
  

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

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

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


[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session

2018-01-19 Thread Karl Trygve Kalleberg
I see the same thing (17.10), gedit 3.22.1:

- if I maximize gedit vertically, gedit foo always opens a new gedit window
- if I maximize gedit horizontall, gedit foo always opens a new gedit window
- if I don't maximize in either direction, gedit foo opens in the existing 
gedit window

I'm running Wayland, not sure if that has any impact.

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

Title:
  Files opened with gedit on command line no longer open within the
  existing gedit session

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  Prior to my update today to Ubuntu 16.04, I could open a file using
  gedit on the command line and it would open in the gedit window i
  already have open. After updating to 16.04 when I open a file with say
  `gedit /tmp/myleakycode.c` it opens in a new window.

  Oddly, as I was writing this bug report it's now working I expect it
  to, where opening files on the CLI adds to my existing session.

  I'll follow up if I find some pattern as to what triggers this.

  I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel,
  gedit 3.18.3, terminator 0.98 to open the files.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 22 12:54:04 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gedit
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  File system folder in nautilus Artful/Bionic flashback session does
  nothing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Go to Places > Computer, left-click to open "Files", then select File
  System either by double-click or right-click + open and nothing
  happens. If you go Places > Home > Other locations and select Computer
  the file system opens as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Jan 16 21:54:39 2018
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 
'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 
'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
   b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']"
  InstallationDate: Installed on 2018-01-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing

2018-01-19 Thread Khurshid Alam
nautilus computer:// opens for me. But the file-system under it doesn't
work.

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

Title:
  File system folder in nautilus Artful/Bionic flashback session does
  nothing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Go to Places > Computer, left-click to open "Files", then select File
  System either by double-click or right-click + open and nothing
  happens. If you go Places > Home > Other locations and select Computer
  the file system opens as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Jan 16 21:54:39 2018
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 
'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 
'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
   b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']"
  InstallationDate: Installed on 2018-01-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Files opened with gedit on command line no longer open within the
  existing gedit session

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  Prior to my update today to Ubuntu 16.04, I could open a file using
  gedit on the command line and it would open in the gedit window i
  already have open. After updating to 16.04 when I open a file with say
  `gedit /tmp/myleakycode.c` it opens in a new window.

  Oddly, as I was writing this bug report it's now working I expect it
  to, where opening files on the CLI adds to my existing session.

  I'll follow up if I find some pattern as to what triggers this.

  I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel,
  gedit 3.18.3, terminator 0.98 to open the files.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 22 12:54:04 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gedit
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1739264] Re: Gedit always open new window in gnome shell

2018-01-19 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Gedit always open new window in gnome shell

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  How to regenerate:
  1. Open dash and search for gedit
  2. Click to open gedit
  3. After opening a gedit window, open dash again and search for gedit
  4. In gnome shell, icon doesn't show any indicator that another window of 
gedit is already running and click on the icon will create a new window

  
  Possible cause:
  Installation of gedit create two .desktop file in /usr/share/applications. 
(gedit.desktop and org.gnome.gedit.desktop)

  Workaround:
  1. Delete /usr/share/applications/gedit.desktop
  2. Edit /usr/share/applications/org.gnome.gedit.desktop and modify 
NoDisplay=true to NoDisplay=false

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gedit 3.22.1-1ubuntu1 [modified: 
usr/share/applications/org.gnome.gedit.desktop]
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 20 01:05:33 2017
  InstallationDate: Installed on 2017-10-26 (54 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-19 Thread Olivier Crête
I get the same error running against this one.

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  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 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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


[Desktop-packages] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org

2018-01-19 Thread Olleg Samoylov
Ubuntu 17.10
tigervnc-xorg-extension 1.7.0+dfsg-7ubuntu1
xorg 1:7.7+19ubuntu3
cinnamon 3.4.6-1
nvidia-384 384.111-0ubuntu0.17.10.1

Bug exactly the same.

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

Title:
  Compiz / vnc screen refresh with nvidia-restricted
  driver/VirtualBox/ATI fglrx driver using X.org

Status in fglrx:
  Invalid
Status in Lucid Backports:
  Invalid
Status in maverick-backports:
  Won't Fix
Status in NVIDIA Drivers Ubuntu:
  Fix Released
Status in vino:
  Fix Released
Status in X.Org X server:
  Fix Released
Status in vino package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in vino package in Fedora:
  Invalid

Bug description:
  Binary package hint: compiz

  When using the nvidia-restricted or some ATI drivers and compiz
  desktop effects the vnc server will not refresh the screen. This is
  being caused by the xserver not getting "damaged" by the nvidia-
  restricted drivers (see https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/353126/comments/245 for details). Linked bugs
  confirm this is not an issue on intel chipsets or nv driver.

  Steps to reproduce:
  Enable desktop-effects (default) with nvidia-restricted, virtualBox's display 
or some ATI driver like RV610
  Enable remote desktop
  Connect with VNC

  Results:
  You see a screen snapshot of your desktop but if you click a menu item there 
are no updates to the screen.
  Notes:
  If you close and restart the vnc session, you get an updated snapshot but 
still no refreshes.

  Workarounds:
  Use the -noxdamage argument with vncviewer. This is really inefficient and 
bandwidth hungry since the whole screen refreshes.
  Kill compiz and use a different wm (metacity).

  [Tested with nvidia] Run compiz with the --use-root-window option, eg:
  compiz --replace --use-root-window &

  This bug has been confirmed by many others with linked reports. Might
  be an issue with xorg since there is a report of ATI drivers with
  similar issues in https://bugs.launchpad.net/bugs/328559 .

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

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


[Desktop-packages] [Bug 1718903] Re: package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1742403 ***
https://bugs.launchpad.net/bugs/1742403

** This bug has been marked a duplicate of bug 1742403
   package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to 
install/upgrade: installed network-manager-config-connectivity-ubuntu package 
post-installation script subprocess returned error exit status 1

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
  failed to install/upgrade: el subproceso instalado el script post-
  installation devolvió el código de salida de error 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  
Instalados: 1.8.2-1ubuntu8
Candidato:  1.8.2-1ubuntu8
Tabla de versión:
   *** 1.8.2-1ubuntu8 500
  500 http://es.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://es.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Tue Sep 19 19:11:46 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-18 (3 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170904)
  IpRoute:
   default via 192.168.0.1 dev eno1 proto static metric 100 
   169.254.0.0/16 dev eno1 scope link metric 1000 
   192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.109 metric 100
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
   
   enp5s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 
3.6.2-1ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5~rc4
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.2-1ubuntu8 
failed to install/upgrade: el subproceso instalado el script post-installation 
devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1bba5b78-2d8b-31a2-9135-56ae4cd4cb9f  802-3-ethernet  
1506075288  vie 22 sep 2017 12:14:48 CEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Conexión cableada 2  018bdd60-5710-36ef-851c-946a6321601b  802-3-ethernet  
1505841433  mar 19 sep 2017 19:17:13 CEST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   eno1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1bba5b78-2d8b-31a2-9135-56ae4cd4cb9f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp5s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/3  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1740651] Re: gnome-terminal-server crashed with SIGSEGV in _XInternAtom()

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1740654 ***
https://bugs.launchpad.net/bugs/1740654

** This bug has been marked a duplicate of bug 1740654
   gnome-language-selector crashed with SIGSEGV in XInternAtom()

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

Title:
  gnome-terminal-server crashed with SIGSEGV in _XInternAtom()

Status in gnome-terminal package in Ubuntu:
  New
Status in hime package in Ubuntu:
  New

Bug description:
  uh i don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 31 14:03:29 2017
  ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server
  InstallationDate: Installed on 2017-12-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server
  SegvAnalysis:
   Segfault happened at: 0x7f8b00cbd363:cmp%r11,(%r10)
   PC (0x7f8b00cbd363) ok
   source "%r11" ok
   destination "(%r10)" (0x00841f0f) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: gnome-terminal
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XInternAtom () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   get_hime_addr_atom () from 
//usr/lib/x86_64-linux-gnu/hime/libhime-im-client.so.1
   ?? () from //usr/lib/x86_64-linux-gnu/hime/libhime-im-client.so.1
   hime_im_client_open () from 
//usr/lib/x86_64-linux-gnu/hime/libhime-im-client.so.1
  Title: gnome-terminal-server crashed with SIGSEGV in XInternAtom()
  UpgradeStatus: Upgraded to bionic on 2017-12-31 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1734581] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1742403 ***
https://bugs.launchpad.net/bugs/1742403

** This bug has been marked a duplicate of bug 1742403
   package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to 
install/upgrade: installed network-manager-config-connectivity-ubuntu package 
post-installation script subprocess returned error exit status 1

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: el subproceso instalado el script post-
  installation devolvió el código de salida de error 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  hello

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  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
  Date: Sun Nov 26 16:18:03 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-11-25 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IpRoute:
   default via 192.168.0.36 dev enp1s0 proto dhcp src 192.168.0.178 metric 100 
   192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.178 
   192.168.0.36 dev enp1s0 proto dhcp scope link src 192.168.0.178 metric 100
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: el subproceso instalado el script post-installation 
devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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


[Desktop-packages] [Bug 1740054] Re: package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: triggers looping, abandoned

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1742147 ***
https://bugs.launchpad.net/bugs/1742147

** This bug has been marked a duplicate of bug 1742147
   upgrade from 17.10 to 18.04 fails with triggers looping

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

Title:
  package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade:
  triggers looping, abandoned

Status in bamf package in Ubuntu:
  New
Status in gnome-icon-theme package in Ubuntu:
  New

Bug description:
  I have problems upgrading to 17.10 from 17.04. Visually it kept equal
  to previous version

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libvlc-bin:amd64 3.0.0~rc2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  Date: Mon Dec 25 23:16:21 2017
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-08-12 (135 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: vlc
  Title: package libvlc-bin:amd64 3.0.0~rc2-2ubuntu2 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2017-12-25 (0 days ago)

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

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


[Desktop-packages] [Bug 1740755] Re: package libreoffice-style-elementary 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1740757 ***
https://bugs.launchpad.net/bugs/1740757

** This bug has been marked a duplicate of bug 1740757
   package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar

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

Title:
  package libreoffice-style-elementary 1:5.4.2-0ubuntu0.17.10.1 failed
  to install/upgrade: problemas de dependencias - se deja sin configurar

Status in libreoffice package in Ubuntu:
  New

Bug description:
  no se que paso

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-elementary 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Jan  1 12:45:03 2018
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2017-12-12 (20 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-elementary 1:5.4.2-0ubuntu0.17.10.1 failed 
to install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1741481] Re: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une err

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1742403 ***
https://bugs.launchpad.net/bugs/1742403

** This bug has been marked a duplicate of bug 1742403
   package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to 
install/upgrade: installed network-manager-config-connectivity-ubuntu package 
post-installation script subprocess returned error exit status 1

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: le sous-processus script post-installation
  installé a retourné une erreur de sortie d'état 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  when i try to update

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  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
  Date: Fri Jan  5 14:09:58 2018
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2018-01-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IpRoute:
   default via 192.168.109.1 dev enp1s0 proto dhcp src 192.168.109.111 metric 
100 
   192.168.109.0/24 dev enp1s0 proto kernel scope link src 192.168.109.111 
   192.168.109.1 dev enp1s0 proto dhcp scope link src 192.168.109.111 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  RfKill:
   
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
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)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 
8: Error: NetworkManager is not running.

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

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


[Desktop-packages] [Bug 1740754] Re: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo ante

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1740757 ***
https://bugs.launchpad.net/bugs/1740757

** This bug has been marked a duplicate of bug 1740757
   package libreoffice-style-tango 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar

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

Title:
  package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to
  install/upgrade: El paquete está en un estado grave de inconsistencia
  - debe reinstalarlo  antes de intentar su configuración.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  se repiten problemas al instalar paquetes. Puntualmente este error se
  dio al momento de instalar el GNUCash.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
  Uname: Linux 4.13.0-19-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  Date: Mon Jan  1 12:45:02 2018
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-12-12 (20 days ago)
  InstallationMedia: Ubuntu-Studio 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: libreoffice
  Title: package libreoffice-style-galaxy 1:5.4.2-0ubuntu0.17.10.1 failed to 
install/upgrade: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 34229] Re: Creating readable pdf

2018-01-19 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Invalid

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

Title:
  Creating readable pdf

Status in Mozilla Firefox:
  Invalid
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  All the new Mozilla based browsers have a Mozilla Postscript Module
  that makes the document like image. That means there is not even one
  letter there and you cannot go back to the url and not to copy
  something. I use cups-pdf 2.0.5 and ghostscript 8.53 which with
  Mozilla-suite (has a previous version of this module and doesn't
  support non latin characters) and I can print readable pdfs from web
  pages, something I can not do with Firefox, Epiphany, Galeon and
  Konqueror (has another module). I think the same problem exists with
  Gnome Print Version 2.12.1.

  I understand that with this module I can print texts in any language
  and this is very important, and the price I have to pay is that when I
  try to print it to pdf to print it as an image. However, that is not
  useful for a later use.  I can not even follow the url. I also
  understand that it is a part of all the new mozilla products and of
  products depend on them.

  
  Is it possible at least for some browsers this Mozilla postscript module to 
enabled or disabled via synaptic? Or could it someway this module be enabled or 
disabled in the printer dialog?

  
  Thank you for your time. I hope there would be a solution.

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

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


[Desktop-packages] [Bug 1577789] Re: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: triggers looping, abandoned

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1589097 ***
https://bugs.launchpad.net/bugs/1589097

** This bug has been marked a duplicate of bug 1589097
   gnome-menus and bamfdaemon failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Error came during normal startup+login after dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  Date: Tue May  3 16:36:01 2016
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-08 (208 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-05-03 (0 days ago)

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

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


[Desktop-packages] [Bug 1568576] Re: Thinkpad T460 & Ultra Dock - No audio output on dock plug

2018-01-19 Thread Krisztian Poos
4.13.0

Same issue on T47p and ultradock, ubuntu, x64, 4.13.0.

Is there any workaround? I did not find anything..

Regards,
K.

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

Title:
  Thinkpad T460 & Ultra Dock - No audio output on dock plug

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T460, Ultra dock, 2 channel speakers connected to dock.
  4.4.0-18 Kernel / 16.04.

  When the laptop is docked & speakers are connected to the dock audio
  connector, I get no audio outpout from the dock audio connector.

  Looks like the same issue as reported in:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680

  However the pin quirks appear to be different for the T*60 series of
  laptops.

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

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


[Desktop-packages] [Bug 1662076] Re: package gnome-menus 3.10.1-0ubuntu2 failed to install/upgrade: triggers looping, abandoned

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1589097 ***
https://bugs.launchpad.net/bugs/1589097

** This bug has been marked a duplicate of bug 1589097
   gnome-menus and bamfdaemon failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package gnome-menus 3.10.1-0ubuntu2 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  Update from 14.04.4 to 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.10.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Mon Feb  6 03:34:28 2017
  DuplicateSignature: package:gnome-menus:3.10.1-0ubuntu2:triggers looping, 
abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-08-03 (186 days ago)
  InstallationMedia: Pinguy 14.04 - Release amd64
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.0.1ubuntu2.17
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.10.1-0ubuntu2 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1741845] Re: installation of libsane for i386 failed

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1738664 ***
https://bugs.launchpad.net/bugs/1738664

** This bug has been marked a duplicate of bug 1738664
   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

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

Title:
  installation of libsane for i386 failed

Status in sane-backends package in Ubuntu:
  New

Bug description:
  i wanted to install package wine-devel from winehq.org. as dependency
  it added a lot of i386 packages. installation of libsane failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Jan  8 09:09:30 2018
  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-GJoSGW/63-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 2016-10-30 (434 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  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: Upgraded to artful on 2017-12-30 (8 days ago)

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

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


[Desktop-packages] [Bug 1737843] Re: Consider demoting xchat-gnome to universe

2018-01-19 Thread Iain Lane
(I'll remove it from the seed immediately)

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Consider demoting xchat-gnome to universe

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xchat-gnome package in Ubuntu:
  New

Bug description:
  xchat-gnome came up today in a discussion of main components that
  aren't ready for openssl 1.1.

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-December/040087.html

  See Steve's response
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html

  "Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then
  brought back).  Did not ship in yakkety or zesty; when restored in artful it
  went straight to main because it was still seeded, but it's unclear this was
  ever reviewed by the Desktop Team or whether they want this package still in
  main.  (The re-uploader is not a member of the Desktop Team.)"

  xchat-gnome is seeded in the supported-desktop-extra seed.

  Do we still need an IRC desktop client in main? (irssi is in main)

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

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


[Desktop-packages] [Bug 1737843] Re: Consider demoting xchat-gnome to universe

2018-01-19 Thread Iain Lane
I think we'll actually remove this - it's not been in Debian for ages
and was reintroduced in Ubuntu after being removed in the yakkety cycle.

Any objection?

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

Title:
  Consider demoting xchat-gnome to universe

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in xchat-gnome package in Ubuntu:
  New

Bug description:
  xchat-gnome came up today in a discussion of main components that
  aren't ready for openssl 1.1.

  https://lists.ubuntu.com/archives/ubuntu-
  devel/2017-December/040087.html

  See Steve's response
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-December/040089.html

  "Ubuntu-only package (dropped in Debian, dropped subsequently in Ubuntu, then
  brought back).  Did not ship in yakkety or zesty; when restored in artful it
  went straight to main because it was still seeded, but it's unclear this was
  ever reviewed by the Desktop Team or whether they want this package still in
  main.  (The re-uploader is not a member of the Desktop Team.)"

  xchat-gnome is seeded in the supported-desktop-extra seed.

  Do we still need an IRC desktop client in main? (irssi is in main)

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

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


[Desktop-packages] [Bug 1568576] Re: Thinkpad T460 & Ultra Dock - No audio output on dock plug

2018-01-19 Thread Krisztian Poos
T470p, sorry for the mistype.

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

Title:
  Thinkpad T460 & Ultra Dock - No audio output on dock plug

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T460, Ultra dock, 2 channel speakers connected to dock.
  4.4.0-18 Kernel / 16.04.

  When the laptop is docked & speakers are connected to the dock audio
  connector, I get no audio outpout from the dock audio connector.

  Looks like the same issue as reported in:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1385680

  However the pin quirks appear to be different for the T*60 series of
  laptops.

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

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


[Desktop-packages] [Bug 1525697] Re: package gnome-menus 3.13.3-6ubuntu2 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1589097 ***
https://bugs.launchpad.net/bugs/1589097

** This bug has been marked a duplicate of bug 1589097
   gnome-menus and bamfdaemon failed to install/upgrade: triggers looping, 
abandoned

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

Title:
  package gnome-menus 3.13.3-6ubuntu2 failed to install/upgrade: Trigger
  bilden eine Schleife, aufgegeben

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  2) gnome-menus:
Installiert:   3.13.3-6ubuntu2
Installationskandidat: 3.13.3-6ubuntu2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-4.13-generic 4.3.2
  Uname: Linux 4.3.0-4-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  Date: Sun Dec 13 19:58:25 2015
  Dependencies:
   
  ErrorMessage: Trigger bilden eine Schleife, aufgegeben
  InstallationDate: Installed on 2015-12-11 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.1.4
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu2 failed to install/upgrade: Trigger 
bilden eine Schleife, aufgegeben
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1625144] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1738194 ***
https://bugs.launchpad.net/bugs/1738194

** This bug has been marked a duplicate of bug 1738194
   gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, 
abandoned - gnome-menus -> gconf2

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  bloqué en boucle sur le traitement des actions différées (« triggers
  »), abandon

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  Installing 16.04 with terminal, everything installed well but after my
  laptop was very laggy and after a reboot, found this error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Sep 19 12:53:25 2016
  Dependencies:
   
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  InstallationDate: Installed on 2015-07-11 (435 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.14
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
bloqué en boucle sur le traitement des actions différées (« triggers »), abandon
  UpgradeStatus: Upgraded to xenial on 2016-09-19 (0 days ago)

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

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


[Desktop-packages] [Bug 1658726] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> desktop-file-utils

2018-01-19 Thread Jean-Baptiste Lallement
** Summary changed:

- package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers 
looping, abandoned
+ package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers 
looping, abandoned - gnome-menus -> desktop-file-utils

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned - gnome-menus -> desktop-file-utils

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  trying to upgrade from 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gnome-menus 3.13.3-6ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Jan 23 16:14:51 2017
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-23 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to yakkety on 2017-01-23 (0 days ago)

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

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


[Desktop-packages] [Bug 1730451] Re: MemoryError while verifying backup

2018-01-19 Thread Kenneth Loafman
Is this the backup causing the error reported?

If not, please run against that one.

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

Title:
  MemoryError while verifying backup

Status in Duplicity:
  In Progress
Status in duplicity package in Ubuntu:
  New

Bug description:
  While trying to verify a backup (launched from deja-dup), I receive
  the following error.  My system currently shows 11G of RAM available
  plus 23G of swap.  Possibly related to #1720159?

  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 763, in get_fileobj_iter
  manifest = backup_set.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 214, in 
from_string
  for match in vi_iterator:
  MemoryError

  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov  6 10:50:12 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-03 (1190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: duplicity
  UpgradeStatus: Upgraded to artful on 2017-09-29 (37 days ago)

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

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


[Desktop-packages] [Bug 1739994] Re: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: udløsere er cyklisk afhængige, afbrudt

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1738194 ***
https://bugs.launchpad.net/bugs/1738194

** This bug has been marked a duplicate of bug 1738194
   gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, 
abandoned - gnome-menus -> gconf2

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

Title:
  package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade:
  udløsere er cyklisk afhængige, afbrudt

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  Appeared right after startup of gui

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu5
  ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
  Uname: Linux 4.14.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  Date: Sun Dec 24 09:57:53 2017
  Dependencies:
   
  ErrorMessage: udløsere er cyklisk afhængige, afbrudt
  InstallationDate: Installed on 2017-12-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171213)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4~rc1-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: 
udløsere er cyklisk afhængige, afbrudt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1738194] Re: gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, abandoned - gnome-menus -> gconf2

2018-01-19 Thread Jean-Baptiste Lallement
** Summary changed:

- error while updating gnome-menus
+ gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, 
abandoned - gnome-menus -> gconf2

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

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

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

Title:
  gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers
  looping, abandoned - gnome-menus -> gconf2

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  apt log session:

  ...
  dpkg: a cycle was encountered while processing the triggers:
    the packet chain of these triggers are or may be responsible:
     gnome-menus -> gconf2
    triggers of pending packets that are or may be insoluble:
     gnome-menus: / usr / share / applications
     libc-bin: ldconfig
     gconf2: / usr / share / GConf / gsettings
  dpkg: error processing package gnome-menus (--configure):
    loop triggers, abandoned

  ...

  $ systemctl  status apport.service

  ● apport.service - LSB: automatic crash report generation
 Loaded: loaded (/etc/init.d/apport; generated; vendor preset: enabled)
 Active: failed (Result: timeout) since Thu 2017-12-14 08:43:36 -02; 1h 
14min ago
   Docs: man:systemd-sysv-generator(8)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/apport.service
 └─9190 plymouth --ping

  dez 14 08:38:36 etm systemd[1]: Starting LSB: automatic crash report 
generation...
  dez 14 08:43:36 etm systemd[1]: apport.service: Start operation timed out. 
Terminating.
  dez 14 08:43:36 etm systemd[1]: apport.service: Failed with result 'timeout'.
  dez 14 08:43:36 etm systemd[1]: Failed to start LSB: automatic crash report 
generation.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu5
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 14 09:50:52 2017
  Dependencies:
   
  InstallationDate: Installed on 2017-09-29 (75 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  SourcePackage: gnome-menus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1738233] Re: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: gatilhos em "loop", abandonado

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1738194 ***
https://bugs.launchpad.net/bugs/1738194

** This bug has been marked a duplicate of bug 1738194
   gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, 
abandoned - gnome-menus -> gconf2

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

Title:
  package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade:
  gatilhos em "loop", abandonado

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  
  #1738204 (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738204)

  #1738194 (https://bugs.launchpad.net/ubuntu/+source/gnome-
  menus/+bug/1738194)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gnome-menus 3.13.3-6ubuntu5
  ProcVersionSignature: Ubuntu 4.14.0-11.13-generic 4.14.3
  Uname: Linux 4.14.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu4
  Architecture: amd64
  Date: Thu Dec 14 08:38:30 2017
  Dependencies:
   
  ErrorMessage: gatilhos em "loop", abandonado
  InstallationDate: Installed on 2017-09-29 (76 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
  Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 
3.6.4~rc1-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: 
gatilhos em "loop", abandonado
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1663546] Re: package gnome-menus 3.13.3-6ubuntu4 failed to install/upgrade: los disparadores han entrado en bucle, abandonando - gconf2 -> gnome-menus

2018-01-19 Thread Jean-Baptiste Lallement
*** This bug is a duplicate of bug 1738194 ***
https://bugs.launchpad.net/bugs/1738194

** Summary changed:

- package gnome-menus 3.13.3-6ubuntu4 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
+ package gnome-menus 3.13.3-6ubuntu4 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando - gconf2 -> gnome-menus

** This bug has been marked a duplicate of bug 1738194
   gnome-menus 3.13.3-6ubuntu5 failed to install/upgrade: triggers looping, 
abandoned - gnome-menus -> gconf2

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

Title:
  package gnome-menus 3.13.3-6ubuntu4 failed to install/upgrade: los
  disparadores han entrado en bucle, abandonando - gconf2 -> gnome-menus

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gnome-menus 3.13.3-6ubuntu4
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 10 11:27:58 2017
  Dependencies:
   
  ErrorMessage: los disparadores han entrado en bucle, abandonando
  InstallationDate: Installed on 2017-02-10 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170209)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4~rc1
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.13.3-6ubuntu4 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   >