[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-03 Thread staedtler-przyborski
@ Ken Wright
You know this is not a helpdesk ?

open a terminal and paste

'apt list --installed |grep -e esci -e iscan -e libsane1'

this shows your installed Sane backends (libsane1) and your iscan
installion

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1716018] Re: nm-applet often disappears from panel at startup

2017-12-03 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  nm-applet often disappears from panel at startup

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  i am with ubuntu 16.04 desktop (64-bit)

  network-manager.service often doesn't start and nm-applet disappears
  from panel at startup

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

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


[Desktop-packages] [Bug 1721260] Re: Bug Report for Canon LBP1120

2017-12-03 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Bug Report for Canon LBP1120

Status in cups package in Ubuntu:
  Expired

Bug description:
  Strange nothing has changed, other than updates to Linux KERNEL(S).

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

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


[Desktop-packages] [Bug 1634354] Re: Copy and paste keyboard shortcuts on right click menu do not work

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

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

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

Title:
  Copy and paste keyboard shortcuts on right click menu do not work

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Copy and Paste with the C and P keys on the right click menu does not
  work in GNOME Terminal 3.18.3 (included with Ubuntu 16.04). The
  ability to copy and paste this way used to work in the version of
  GNOME Terminal included with Ubuntu 14.04 (3.6.2, I think?), so this
  is a regression from that version.

  The keys for the other menu options (Open Terminal (T), Profiles (R),
  Read-Only (O), Show Menubar (M)) can be restored by going into
  preferences and activating the checkbox for "Enable mnemonics (such as
  Alt+F to open the File menu)" -- however, copy and paste are not
  included.

  I frequently paste using the menu key (menu key, P), so this is a very
  annoying bug that I run into every day now that I've upgraded from
  14.04.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy gnome-terminal
  gnome-terminal:
Installed: 3.18.3-1ubuntu1
Candidate: 3.18.3-1ubuntu1
Version table:
   *** 3.18.3-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Expect to happen:

  Pressing P when the right-click context menu is open should paste from
  the clipboard. Pressing C when the menu is open should copy selected
  text to the clipboard.

  What happened instead:

  No response when pressing the keys. No underline for an alternate key
  is shown either. Presumably the shortcuts ("mnemonics"?) for these
  entries are missing in the code.

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

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


[Desktop-packages] [Bug 1736047] Re: package nvidia-opencl-icd-340 340.96-0ubuntu3.hostname.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2017-12-03 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 nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1736047

Title:
  package nvidia-opencl-icd-340 340.96-0ubuntu3.hostname.04.1 failed to
  install/upgrade: there is no script in the new version of the package
  - giving up

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

Bug description:
  I have no idea what triggers this...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-41.45-generic 4.10.17
  Uname: Linux 4.10.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start LSB: This service starts and stops 
VMware services.
   See 'systemctl status vmware.service' for details.
   [  OK  ] Started Munin Node.
   [  OK  ] Started LSB: Cisco AnyConnect Secure Mobility Client for 
Linux.
  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 Dec  2 07:01:24 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   ocl-icd-libopencl1 2.2.11-1ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DpkgHistoryLog:
   Start-Date: 2017-12-02  07:01:18
   Commandline: aptdaemon role='role-commit-packages' sender=':1.154'
   Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.17.04.2, 
1:52.5.0+build1-0ubuntu0.17.04.1), thunderbird-locale-en-us:amd64 
(1:52.4.0+build1-0ubuntu0.17.04.2, 1:52.5.0+build1-0ubuntu0.17.04.1), 
firefox-locale-en:amd64 (57.0+build4-0ubuntu0.17.04.6, 
57.0.1+build2-0ubuntu0.17.04.1), thunderbird:amd64 
(1:52.4.0+build1-0ubuntu0.17.04.2, 1:52.5.0+build1-0ubuntu0.17.04.1), 
firefox:amd64 (57.0+build4-0ubuntu0.17.04.6, 57.0.1+build2-0ubuntu0.17.04.1), 
thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.17.04.2, 
1:52.5.0+build1-0ubuntu0.17.04.1), nvidia-opencl-icd-340:amd64 
(340.96-0ubuntu3.16.04.1, 340.102-0ubuntu3)
  ErrorMessage: there is no script in the new version of the package - giving up
  GraphicsCard:
   NVIDIA Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GT200 [GeForce GTX 260] [3842:1257]
  InstallationDate: Installed on 2014-12-17 (1082 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. P55-UD4P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-41-generic 
root=UUID=4cd5d1df-59f6-4e84-a94e-bdf202a93d5b ro
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.8
  SourcePackage: nvidia-graphics-drivers-340
  Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.hostname.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P55-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd05/06/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 

[Desktop-packages] [Bug 1736047] [NEW] package nvidia-opencl-icd-340 340.96-0ubuntu3.hostname.04.1 failed to install/upgrade: there is no script in the new version of the package - giving up

2017-12-03 Thread Bullwinkle
Public bug reported:

I have no idea what triggers this...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1
ProcVersionSignature: Ubuntu 4.10.0-41.45-generic 4.10.17
Uname: Linux 4.10.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.102  Mon Jan 16 13:06:29 
PST 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: amd64
BootLog:
 [FAILED] Failed to start LSB: This service starts and stops 
VMware services.
 See 'systemctl status vmware.service' for details.
 [  OK  ] Started Munin Node.
 [  OK  ] Started LSB: Cisco AnyConnect Secure Mobility Client for 
Linux.
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 Dec  2 07:01:24 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 ocl-icd-libopencl1 2.2.11-1ubuntu1
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
DpkgHistoryLog:
 Start-Date: 2017-12-02  07:01:18
 Commandline: aptdaemon role='role-commit-packages' sender=':1.154'
 Upgrade: thunderbird-gnome-support:amd64 (1:52.4.0+build1-0ubuntu0.17.04.2, 
1:52.5.0+build1-0ubuntu0.17.04.1), thunderbird-locale-en-us:amd64 
(1:52.4.0+build1-0ubuntu0.17.04.2, 1:52.5.0+build1-0ubuntu0.17.04.1), 
firefox-locale-en:amd64 (57.0+build4-0ubuntu0.17.04.6, 
57.0.1+build2-0ubuntu0.17.04.1), thunderbird:amd64 
(1:52.4.0+build1-0ubuntu0.17.04.2, 1:52.5.0+build1-0ubuntu0.17.04.1), 
firefox:amd64 (57.0+build4-0ubuntu0.17.04.6, 57.0.1+build2-0ubuntu0.17.04.1), 
thunderbird-locale-en:amd64 (1:52.4.0+build1-0ubuntu0.17.04.2, 
1:52.5.0+build1-0ubuntu0.17.04.1), nvidia-opencl-icd-340:amd64 
(340.96-0ubuntu3.16.04.1, 340.102-0ubuntu3)
ErrorMessage: there is no script in the new version of the package - giving up
GraphicsCard:
 NVIDIA Corporation GT200 [GeForce GTX 260] [10de:05e2] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: eVga.com. Corp. GT200 [GeForce GTX 260] [3842:1257]
InstallationDate: Installed on 2014-12-17 (1082 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. P55-UD4P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-41-generic 
root=UUID=4cd5d1df-59f6-4e84-a94e-bdf202a93d5b ro
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.8
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.hostname.04.1 failed to 
install/upgrade: there is no script in the new version of the package - giving 
up
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: P55-UD4P
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd05/06/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P55-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Sun Dec  3 17:26:58 2017
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.3-1ubuntu1.3

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package 

[Desktop-packages] [Bug 911591] Re: gnome-shell crashes when resizing OpenGL window

2017-12-03 Thread James Cuzella
@dino99

Happy to open a new bug report on this, as it still appears to be an
issue in latest Ubuntu 17.10.  Usually when reporting bugs, I opt to
prefer adding information to an existing bug report that I have high
confidence describes the problem I am seeing.  I believe this helps to
reduce creating many duplicates and to focus community effort on
resolving the main underlying problem rather than bug report management
overhead from many duplicates or "me too" comments with no helpful debug
info.  If this is not preferred on this project, or for some reason
doesn't fit the developer bug triage process here, that's fine.  I'm
happy to add information upstream or in another LaunchPad bug.

Back to this problem:

As it is a segfault reported in upstream gnome-shell which has something
to do with OpenGL + resize behavior, I don't believe borked settings are
the issue, nothing I've seen yet points towards that, although it'd be
nice if the problem could be resolved by a config change instead of code
change.  This system never had any gnome-shell installed because Unity
was there instead.  Therefore, no pre-existing gnome-shell configuration
can be hanging around.  I've posted to upstream bug, but some info was
here.

To clarify: I do not have an Nvidia optimus nor do I use noveau, but use
older nvidia-340 binary drivers.  This is the nvidia recommended set of
drivers for my card.  Another comment in the upstream report mentions
the issue may not have as much to do with Nvidia as it does with Xrandr
fast video mode changes.  I have confirmed this behavior in my own
testing, and have a reproduction test case that works pretty reliably
for me:

Reproduction Command:

# Use output and modes that are valid for you...
xrandr --output HDMI-0 --mode 1920x1080 ; xrandr --output HDMI-0 --mode 
1920x1080 ; xrandr --output HDMI-0 --mode 800x600 ; xrandr --output HDMI-0 
--mode 1920x1080

I've tested this a couple times and it looks like I am able to trigger
the crash just with fast xrandr commands.

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

Title:
  gnome-shell crashes when resizing OpenGL window

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  I have a couple of applications that I wrote myself. They are OpenGL
  graphics applications. One application uses SDL for OpenGL context
  management, and the other uses GLFW.

  When I resize the windows of these applications by dragging the window
  edges, gnome-shell crashes almost 100 % of the time after a certain
  amount of resizing back and forth. This does not happen when instantly
  resizing the window (e.g. with Alt+F10, which effectively does a
  resize as far as SDL and GLFW are concerned anyway).

  Rapidly resizing the window of glxgears does not seem to crash gnome-
  shell, which confuses me. I guess it is interacting with things
  differently or something.

  Anyways, I'm using the following versions of involved software
  packages:

  gnome-shell: 3.2.1-0ubuntu1.1
  nvidia-current: 290.10-0ubuntu1~oneiric~xup1 (from the ubuntu-x-swat PPA)
  SDL: 1.2.14-6.1ubuntu4
  GLFW: 2.7.2-1

  I'm thinking that maybe the two libraries I use (SDL and GLFW) create
  new OpenGL contexts every time when using their respective resizing
  mechanisms, whereas glxgears does something different, and requesting
  new contexts with new sizes too often during a small period of time
  might not go too well? Not sure at all what details I can provide
  regarding this problem. Hopefully someone can ask the right questions
  and I will be able to provide the necessary information.

  I will be very lucky if the applications were started from a terminal.
  That way the undecorated window of the terminal has focus after the
  crash, and I can relaunch gnome-shell from there.

  Any help is appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-shell 3.2.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.0.0-15.24-generic 3.0.13
  Uname: Linux 3.0.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Wed Jan  4 04:19:48 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  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/911591/+subscriptions

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


[Desktop-packages] [Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Bug Watch Updater
** Changed in: totem (Debian)
   Status: Unknown => Fix Released

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Fix Released

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 103571] ✈Re: omg! that's interesting

2017-12-03 Thread etabeta
Dear,

Below  are a few interesting facts you might be interested in, I think
this information could  be  helpful, read  it here
http://www.studiocitymd.com/acagx.php?UE8xMDM1NzFAYnVncy5sYXVuY2hwYWQubmV0

Sent from my iPhone, Pietro Marchionda

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

Title:
  Cover art plugin regression: sidebar resizing results in bad image
  quality

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: rhythmbox

  I reported this upstream but they don't seem to think it's likely a
  problem on their end because "The cover art code was virtually
  unchanged between 0.9.8 and 0.10.0."


  This worked fine in 0.9.8 but is a regression in 0.10.0.

  Steps to reproduce:
  1. Make sure the cover art display area in the sidebar is small (or extremely 
tiny, to notice the issue easier)
  2. Start playing a track which you have a higher-resolution (than the size of 
the cover art area) cover.png image file
  in the directory for
  3. Resize the sidebar bigger, increasing the size of the cover art display 
area

  
  Actual results:
  A pixelated image, it resizes the small version of the cover art file it has
  made larger

  Expected results:
  A good quality cover art image, like in 0.9.8. Switching to a track with a
  different cover art image and back without changing the sidebar's size results
  in the good quality cover art image being used, as does disabling the cover 
art
  plugin and re-enabling it

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

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


[Desktop-packages] [Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Mateusz Mikuła
Created backport requrest for fixed version of apparmor-profiles-extra
https://bugs.launchpad.net/artful-backports/+bug/1736039

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Unknown

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

2017-12-03 Thread Mazimo
Same problem on fresh 17.10 install using LG Tone HBS920 headsets.
An LG FH2 portable rolling speaker seems to work fine though.

The workaround of disconnecting my LG headset under Bluetooth Settings
and then reconnecting does allow me to switch from HSP/HFP to A2DP.

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Mateusz Mikuła
** Bug watch added: Debian Bug tracker #879900
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879900

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

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Unknown

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1710858] Re: totem crashed with SIGSEGV in __GI_____strtoul_l_internal()

2017-12-03 Thread Mateusz Mikuła
Crash happens only if `usr.bin.totem` AppArmor profile from `apparmor-
profiles-extra` is enabled.

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

Title:
  totem crashed with SIGSEGV in __GI_strtoul_l_internal()

Status in totem package in Ubuntu:
  Confirmed
Status in totem package in Debian:
  Unknown

Bug description:
  crashed trying to open .avi video

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu1
  Uname: Linux 4.12.6-041206-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Tue Aug 15 12:20:00 2017
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2016-05-20 (451 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe5160f1bf5 <__GI_strtoul_l_internal+53>:   
movsbq (%r14),%rax
   PC (0x7fe5160f1bf5) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7fff97eb9aa8, base=10, 
group=, loc=0x7fe516474820 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
   () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: totem crashed with SIGSEGV in __GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom colord dialout dip libvirt libvirtd lpadmin 
netdev pico plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1735062] Re: Xorg freeze

2017-12-03 Thread Mr. Phazor
I probably solved this issue with:

1. Edit /etc/default/grub

-Changed line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
into:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"

2. sudo update-grub
3. sudo grub-install /dev/sdX
4. reboot

https://askubuntu.com/questions/893817/boot-very-slow-because-of-drm-
kms-helper-errors/916112

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The problem is a very short graphics freeze. I believe the issue is
  related to the i915 driver:;;

  [ 1103.153702] [ cut here ]
  [ 1103.153759] WARNING: CPU: 2 PID: 5425 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 
intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 1103.153760] Modules linked in: msr rfcomm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm bnep binfmt_misc intel_rapl 
dell_laptop x86_pkg_temp_thermal intel_powerclamp dell_smm_hwmon coretemp 
kvm_intel uvcvideo kvm videobuf2_vmalloc btusb irqbypass snd_hda_codec_hdmi 
videobuf2_memops videobuf2_v4l2 snd_hda_codec_conexant btrtl 
snd_hda_codec_generic videobuf2_core crct10dif_pclmul crc32_pclmul btbcm 
btintel ghash_clmulni_intel cryptd intel_cstate snd_hda_intel intel_rapl_perf 
bluetooth videodev snd_hda_codec snd_hda_core media ecdh_generic snd_hwdep 
dell_wmi dell_smbios arc4 snd_pcm input_leds dcdbas joydev sparse_keymap 
serio_raw wmi_bmof snd_seq_midi snd_seq_midi_event snd_rawmidi iwldvm mac80211 
snd_seq snd_seq_device snd_timer iwlwifi snd cfg80211 lpc_ich soundcore mei_me 
mei
  [ 1103.153800]  shpchp dell_smo8800 mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid i915 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
psmouse ahci drm libahci atl1c wmi video
  [ 1103.153820] CPU: 2 PID: 5425 Comm: kworker/u16:2 Tainted: G   OE   
4.13.0-17-generic #20-Ubuntu
  [ 1103.153821] Hardware name: Dell Inc.  Dell System Inspiron 
N411Z/0YWNPW, BIOS A00 06/24/2011
  [ 1103.153860] Workqueue: events_unbound intel_atomic_commit_work [i915]
  [ 1103.153862] task: 90c28720c5c0 task.stack: a496c3ee
  [ 1103.153898] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 1103.153899] RSP: 0018:a496c3ee3d88 EFLAGS: 00010282
  [ 1103.153900] RAX: 001c RBX: 0001 RCX: 

  [ 1103.153901] RDX:  RSI: 90c39fa8dc78 RDI: 
90c39fa8dc78
  [ 1103.153902] RBP: a496c3ee3e40 R08: 0001 R09: 
0323
  [ 1103.153903] R10: a496c3ee3d88 R11:  R12: 
fe3e
  [ 1103.153904] R13: 90c38d06 R14: 90c38e3db000 R15: 
0002
  [ 1103.153906] FS:  () GS:90c39fa8() 
knlGS:
  [ 1103.153907] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1103.153908] CR2: 7f2139afa000 CR3: 0001949eb000 CR4: 
000406e0
  [ 1103.153910] Call Trace:
  [ 1103.153917]  ? wait_woken+0x80/0x80
  [ 1103.153955]  intel_atomic_commit_work+0x12/0x20 [i915]
  [ 1103.153960]  process_one_work+0x1e7/0x410
  [ 1103.153962]  worker_thread+0x4a/0x410
  [ 1103.153965]  kthread+0x125/0x140
  [ 1103.153967]  ? process_one_work+0x410/0x410
  [ 1103.153969]  ? kthread_create_on_node+0x70/0x70
  [ 1103.153972]  ret_from_fork+0x25/0x30
  [ 1103.153974] Code: ff ff ff 48 83 c7 08 e8 42 a1 32 e0 4c 8b 85 70 ff ff ff 
4d 85 c0 0f 85 7b fa ff ff 8d 73 41 48 c7 c7 60 c4 66 c0 e8 d4 53 34 e0 <0f> ff 
e9 65 fa ff ff 66 90 66 2e 0f 1f 84 00 00 00 00 00 66 66 
  [ 1103.154006] ---[ end trace 3e9edf28140fd63f ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:09:19 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-40-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:051b]
  InstallationDate: Installed on 2016-01-02 (696 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmDisplayLog: (II) 

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-03 Thread Ken Wright
Yes, installing iscan was the first thing I did.  I had to install it
when I was running 16.04 and the scanner worked, so I knew it was
needed.

I tried to install sane-backends, but I got this response:

sudo aptitude install sane-backends
[sudo] password for kwright: 
Couldn't find any package matching "sane-backends", but there are 2 packages 
which contain "sane-backends" in their description:
  scanbd scanbd:i386 
Unable to apply some actions, aborting
sudo aptitude install scanbd
scanbd is already installed at the requested version (1.4.4-1build2)
scanbd is already installed at the requested version (1.4.4-1build2)
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735062] Re: Xorg freeze

2017-12-03 Thread Mr. Phazor
I have the exact same problem after installing a fresh version of 17.10
with Xubuntu on 2 laptops with the same graphics card running the
i915-driver. It happens randomly. The desktop just freezes for some
seconds. Previously running 16.04 with no problem.

Kernel: 4.13.0-17-generic x86_64 bits: 64 gcc: 7.2.0 Desktop: Xfce
4.12.3 (Gtk 2.24.31)

Machine:   Device: laptop System: Hewlett-Packard product: HP Compaq 6910p v: 
B.58 serial: N/A
   Mobo: Hewlett-Packard model: 30BE v: KBC Version 68.36 serial: N/A
   BIOS: Hewlett-Packard v: 68MCU Ver. B.58 date: 10/26/2009

CPU:   Dual core Intel Core2 Duo T7100 (-MCP-) arch: Conroe rev.13 cache: 
2048 KB
   flags: (lm nx sse sse2 sse3 ssse3 vmx) bmips: 7181
   clock speeds: max: 1801 MHz 1: 1795 MHz 2: 1795 MHz

Graphics:  Card: Intel Mobile GM965/GL960 Integrated Graphics Controller 
(primary) bus-ID: 00:02.0
   Display Server: x11 (X.Org 1.19.5 ) drivers: modesetting (unloaded: 
fbdev,vesa)
   Resolution: 1280x800@60.00hz
   OpenGL: renderer: Mesa DRI Intel 965GM version: 2.1 Mesa 17.2.2 
Direct Render: Yes

DMESG
=

WARNING: CPU: 1 PID: 753 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 
drm_wait_one_vblank+0x19b/0x1b0 [drm]
Modules linked in: bnep pata_pcmcia coretemp snd_hda_codec_hdmi kvm 
snd_hda_codec_analog snd_hda_codec_generic pcmcia snd_hda_intel snd_hda_codec 
yenta_socket input_leds irqbypass snd_hda_core snd_hwdep arc4 joydev btusb 
btrtl serio_raw pcmcia_rsrc snd_pcm btbcm btintel pcmcia_core snd_seq_midi 
bluetooth hp_wmi snd_seq_midi_event iwl4965 wmi_bmof sparse_keymap snd_rawmidi 
ecdh_generic snd_seq iwlegacy mac80211 lpc_ich snd_seq_device snd_timer 
cfg80211 snd soundcore shpchp smsc_ircc2 irda tpm_infineon hp_accel lis3lv02d 
input_polldev mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 
firewire_ohci firewire_core ahci libahci i915 pata_acpi sdhci_pci sdhci 
crc_itu_t e1000e psmouse ptp pps_core i2c_algo_bit wmi drm_kms_helper 
syscopyarea sysfillrect video sysimgblt fb_sys_fops
  drm
CPU: 1 PID: 753 Comm: Xorg Tainted: GW   4.13.0-17-generic 
#20-Ubuntu
Hardware name: Hewlett-Packard HP Compaq 6910p/30BE, BIOS 68MCU Ver. B.58 
10/26/2009
task: 9af6f5e0c200 task.stack: a980c0af4000
 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm]
 RSP: 0018:a980c0af7978 EFLAGS: 00010286
 RAX: 001f RBX: 9af6b470 RCX: 
 RDX:  RSI: 9af6ff50dc78 RDI: 9af6ff50dc78
 RBP: a980c0af79d8 R08: 0001 R09: 06b8
 R10: a980c0af7978 R11:  R12: 0001
 R13: 0170 R14: 1d00094a R15: 
 FS:  7f96d65b0a40() GS:9af6ff50() knlGS:
 CS:  0010 DS:  ES:  CR0: 80050033
 CR2: 7f030db25000 CR3: 769cd000 CR4: 06e0
 Call Trace:
  ? wait_woken+0x80/0x80
  intel_get_load_detect_pipe+0x5c6/0x640 [i915]
  intel_tv_detect+0x145/0x4d0 [i915]
  ? __i2c_transfer+0x11d/0x400
  ? __ww_mutex_lock_slowpath+0x16/0x20
  drm_helper_probe_detect+0x4d/0x90 [drm_kms_helper]
  ? drm_helper_probe_detect+0x4d/0x90 [drm_kms_helper]
  drm_helper_probe_single_connector_modes+0xe1/0x780 [drm_kms_helper]
  ? __mark_inode_dirty+0x114/0x3a0
  drm_mode_getconnector+0x153/0x330 [drm]
  ? __drm_mode_object_find+0x54/0xa0 [drm]
  ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
  drm_ioctl_kernel+0x5d/0xb0 [drm]
  drm_ioctl+0x31b/0x3d0 [drm]
  ? drm_mode_connector_property_set_ioctl+0x60/0x60 [drm]
  ? dput.part.23+0x2d/0x1e0
  do_vfs_ioctl+0xa5/0x610
  ? vfs_write+0x132/0x1a0
  SyS_ioctl+0x79/0x90
  entry_SYSCALL_64_fastpath+0x1e/0xa9
 RIP: 0033:0x7f96d3a00ea7
 RSP: 002b:7ffeca02fbe8 EFLAGS: 3246 ORIG_RAX: 0010
 RAX: ffda RBX: 7ffeca02fa00 RCX: 7f96d3a00ea7
 RDX: 7ffeca02fc20 RSI: c05064a7 RDI: 000e
 RBP: 7ffeca02f9f0 R08:  R09: 
 R10:  R11: 3246 R12: 563becfb947c
 R13: 7ffeca02fb50 R14:  R15: 
 Code: ff e8 8a ff ae d0 48 8b 7d a0 48 8d 75 a8 e8 bd 51 b3 d0 45 85 ff 0f 85 
0c ff ff ff 44 89 e6 48 c7 c7 d8 0b 1b c0 e8 56 04 b5 d0 <0f> ff e9 f6 fe ff ff 
0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The problem is a very short graphics freeze. I believe the issue is
  related to the i915 driver:;;

  [ 1103.153702] [ cut here ]
  [ 1103.153759] WARNING: CPU: 2 PID: 5425 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 
intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 1103.153760] Modules linked 

[Desktop-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2017-12-03 Thread Steffen Neumann
I also have no success with

nmcli con up id "FONIC Default"
Error: Connection activation failed: Unknown error

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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


[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-03 Thread staedtler-przyborski
Output(s) seem fine

have you installed

http://support.epson.net/linux/en/iscan.php?model=perfection-v370=1.0.1
ß

I guess so but for beeing sure ...

Also
sane-backends (1.0.27-1~experimental2ubuntu2.1) artful ?

I ask so much because in comment 21 the epson V-370 is told to be
working. So it seems a problem  with your setting

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735062] Re: Xorg freeze

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  The problem is a very short graphics freeze. I believe the issue is
  related to the i915 driver:;;

  [ 1103.153702] [ cut here ]
  [ 1103.153759] WARNING: CPU: 2 PID: 5425 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 
intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 1103.153760] Modules linked in: msr rfcomm pci_stub vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm bnep binfmt_misc intel_rapl 
dell_laptop x86_pkg_temp_thermal intel_powerclamp dell_smm_hwmon coretemp 
kvm_intel uvcvideo kvm videobuf2_vmalloc btusb irqbypass snd_hda_codec_hdmi 
videobuf2_memops videobuf2_v4l2 snd_hda_codec_conexant btrtl 
snd_hda_codec_generic videobuf2_core crct10dif_pclmul crc32_pclmul btbcm 
btintel ghash_clmulni_intel cryptd intel_cstate snd_hda_intel intel_rapl_perf 
bluetooth videodev snd_hda_codec snd_hda_core media ecdh_generic snd_hwdep 
dell_wmi dell_smbios arc4 snd_pcm input_leds dcdbas joydev sparse_keymap 
serio_raw wmi_bmof snd_seq_midi snd_seq_midi_event snd_rawmidi iwldvm mac80211 
snd_seq snd_seq_device snd_timer iwlwifi snd cfg80211 lpc_ich soundcore mei_me 
mei
  [ 1103.153800]  shpchp dell_smo8800 mac_hid parport_pc ppdev lp parport 
ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj usbhid hid i915 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
psmouse ahci drm libahci atl1c wmi video
  [ 1103.153820] CPU: 2 PID: 5425 Comm: kworker/u16:2 Tainted: G   OE   
4.13.0-17-generic #20-Ubuntu
  [ 1103.153821] Hardware name: Dell Inc.  Dell System Inspiron 
N411Z/0YWNPW, BIOS A00 06/24/2011
  [ 1103.153860] Workqueue: events_unbound intel_atomic_commit_work [i915]
  [ 1103.153862] task: 90c28720c5c0 task.stack: a496c3ee
  [ 1103.153898] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 1103.153899] RSP: 0018:a496c3ee3d88 EFLAGS: 00010282
  [ 1103.153900] RAX: 001c RBX: 0001 RCX: 

  [ 1103.153901] RDX:  RSI: 90c39fa8dc78 RDI: 
90c39fa8dc78
  [ 1103.153902] RBP: a496c3ee3e40 R08: 0001 R09: 
0323
  [ 1103.153903] R10: a496c3ee3d88 R11:  R12: 
fe3e
  [ 1103.153904] R13: 90c38d06 R14: 90c38e3db000 R15: 
0002
  [ 1103.153906] FS:  () GS:90c39fa8() 
knlGS:
  [ 1103.153907] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1103.153908] CR2: 7f2139afa000 CR3: 0001949eb000 CR4: 
000406e0
  [ 1103.153910] Call Trace:
  [ 1103.153917]  ? wait_woken+0x80/0x80
  [ 1103.153955]  intel_atomic_commit_work+0x12/0x20 [i915]
  [ 1103.153960]  process_one_work+0x1e7/0x410
  [ 1103.153962]  worker_thread+0x4a/0x410
  [ 1103.153965]  kthread+0x125/0x140
  [ 1103.153967]  ? process_one_work+0x410/0x410
  [ 1103.153969]  ? kthread_create_on_node+0x70/0x70
  [ 1103.153972]  ret_from_fork+0x25/0x30
  [ 1103.153974] Code: ff ff ff 48 83 c7 08 e8 42 a1 32 e0 4c 8b 85 70 ff ff ff 
4d 85 c0 0f 85 7b fa ff ff 8d 73 41 48 c7 c7 60 c4 66 c0 e8 d4 53 34 e0 <0f> ff 
e9 65 fa ff ff 66 90 66 2e 0f 1f 84 00 00 00 00 00 66 66 
  [ 1103.154006] ---[ end trace 3e9edf28140fd63f ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 28 22:09:19 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.30, 4.10.0-40-generic, x86_64: installed
   virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:051b]
  InstallationDate: Installed on 2016-01-02 (696 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file.
  MachineType: Dell Inc. Dell System Inspiron N411Z
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
 

[Desktop-packages] [Bug 241198] Re: gdm doesn't respect umask setting

2017-12-03 Thread Coeur Noir
There's something closely related happening in actual ubuntu 17.10 :

https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1701757
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1685754

It makes managing muti-users machines and shared folders almost
impossible…

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

Title:
  gdm doesn't respect umask setting

Status in gdm:
  Expired
Status in gdm package in Ubuntu:
  Incomplete

Bug description:
  Hello at first I wanted to add this bug to existing one:  #25910 gdm
  doesn't take care of pam_umask settings but in my case I don;t use
  pam_umask.

  What I need is to let users create files/folders with extended
  permissions - different than 022 which I think is again hardcoded in
  gnome. I tried to change umask in ~/.profile and ~/.gnomerc as well as
  /etc/X11/Xsessions.d/55gnome - nothing works :(

  This is huge problem for me as most of volumes are mounted via NFS to
  share amongst many users. But when user creates file/folder all I can
  see is : 755 for folders which is not acceptable.

  Can you confirm this bug or I;m missing something?

  My Ubuntu is Hardy 8.04 with all updates.

  Regards,
  Marcin

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

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


[Desktop-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2017-12-03 Thread Steffen Neumann
So mmcli will show me that the modem is alive,
but still the issue that I don't get an IP. Thoughts ?

mmcli -m 0

/org/freedesktop/ModemManager1/Modem/0 (device id '0ea...129')
  -
  Hardware |   manufacturer: 'Huawei Technologies Co., Ltd.'
   |  model: 'ME936'
   |   revision: '11.350.24.00.00'
   |  supported: 'gsm-umts, lte'
   |current: 'gsm-umts, lte'
   |   equipment id: '86...88'
  -
  System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-9'
   |drivers: 'option1, cdc_ncm'
   | plugin: 'Huawei'
   |   primary port: 'ttyUSB0'
   |  ports: 'ttyUSB0 (at), wwp0s20f0u9c2 (net), ttyUSB2 (at)'
  -
  Numbers  |   own : '+49176...7'
  -
  Status   |   lock: 'none'
   | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10), sim-puk2 
(10)'
   |  state: 'registered'
   |power state: 'on'
   |access tech: 'umts'
   | signal quality: '25' (recent)
  -
  Modes|  supported: 'allowed: 2g; preferred: none
   |  allowed: 3g; preferred: none
   |  allowed: 4g; preferred: none
   |  allowed: 2g, 3g, 4g; preferred: none'
   |current: 'allowed: 2g, 3g, 4g; preferred: none'
  -
  Bands|  supported: 'unknown'
   |current: 'unknown'
  -
  IP   |  supported: 'ipv4, ipv6, ipv4v6'
  -
  3GPP |   imei: '86...88'
   |  enabled locks: 'sim'
   |operator id: '26203'
   |  operator name: 'FONIC+'
   |   subscription: 'unknown'
   |   registration: 'home'
  -
  SIM  |   path: '/org/freedesktop/ModemManager1/SIM/0'

  -
  Bearers  |  paths: '/org/freedesktop/ModemManager1/Bearer/3'

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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


[Desktop-packages] [Bug 1736029] [NEW] xul-ext-* are not compatible with Firefox 57+

2017-12-03 Thread Norbert
Public bug reported:

Steps to reproduce:
1. Install modern Ubuntu with all updates and all xul-ext- extensions
2. Launch Firefox 57 or newer
3. Go to Tools|Add-ons, Legacy Extensions and find Ubuntu Modifications 3.3 and 
others marked as LEGACY.

Expected results:
Ubuntu Modifications and others are compatible with modern Firefox.

Actual results:
Ubuntu Modifications and others are not compatible with modern Firefox, it does 
not fit Mozilla's trends 
(https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing?as=u_source=inproduct).

Note:
for Ubuntu Modifications (ubufox) see bug 1711778.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xul-ext-ubufox 3.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Mon Dec  4 00:33:54 2017
PackageArchitecture: all
SourcePackage: ubufox
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: classic-theme-restorer (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: firefox-branding-iceweasel (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: form-history-control (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: https-finder (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: mozilla-password-editor (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: pdf.js (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: self-destructing-cookies (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: spdy-indicator (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ublock-origin (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: video-without-flash (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xul-ext-exteditor (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: y-u-no-validate (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug artful bionic trusty xenial zesty

** Description changed:

  Steps to reproduce:
  1. Install modern Ubuntu with all updates
  2. Launch Firefox 57 or newer
  3. Go to Tools|Add-ons, Legacy Extensions and find Ubuntu Modifications 3.3 
marked as LEGACY.
  
  Expected results:
  Ubuntu Modifications is compatible with modern Firefox.
  
  Actual results:
- Ubuntu Modifications is not compatible with modern Firefox.
+ Ubuntu Modifications is not compatible with modern Firefox, it does not fit 
Mozilla's trends 
(https://support.mozilla.org/en-US/kb/firefox-add-technology-modernizing?as=u_source=inproduct).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xul-ext-ubufox 3.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Dec  4 00:33:54 2017
  PackageArchitecture: all
  SourcePackage: ubufox
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- xul-ext-ubufox is not compatible with Firefox 57+
+ xul-ext-* are not compatible with Firefox 57+

** Also affects: classic-theme-restorer (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: form-history-control (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: https-finder (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: firefox-branding-iceweasel (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: firefox-kwallet5 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: lightning-extension (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: mozilla-password-editor (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pdf.js (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: self-destructing-cookies (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: spdy-indicator (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: ublock-origin (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: video-without-flash (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: 

[Desktop-packages] [Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens

2017-12-03 Thread Phil Pemberton
The most common issue which can cause this is setting the Page Size incorrectly 
in the driver. You'll get the red flashing light if the intended page size 
doesn't match the label.

The other issue is swapping the X and Y dimensions - the X (as far as
the printer is concerned) is across the printer; the Y axis is the
direction the label feeds.

Note that most of the Ptouch labels are longer (Y axis) than they are
wide (X axis), but the dimensions on the label box are the other way
around. This means you need to specify the paper size as it is on the
physical label (i.e. longer than wide) then rotate the label (e.g.
gLabels's "Rotated" option).

What are you trying to print, and with which application?

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  New

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1736030] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

2017-12-03 Thread Apport retracing service
*** This bug is a duplicate of bug 1732878 ***
https://bugs.launchpad.net/bugs/1732878

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 #1732878, 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/1736030/+attachment/5017922/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I'm working... and open apport.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  Uname: Linux 4.14.3-041403-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Dec  1 15:44:30 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (51 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1731417] Re: Installed printer removed after suspend/resume

2017-12-03 Thread Alberto Donato
** Summary changed:

- Installed printer disappears after suspend/resume
+ Installed printer removed after suspend/resume

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

Title:
  Installed printer removed after suspend/resume

Status in hplip package in Ubuntu:
  New

Bug description:
  After installing artful, I configured my HP LaserJet M1212nf via network as 
usual via hp-setup.
  Installation worked and I could print/scan via network, but next time I 
needed to print, the printer was gone from the system.
  Basically, every time I need to print, I have to install the printer again.
  I'm not sure when the printer disappears, but I can reproduce consistently.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: GNOME
  Date: Fri Nov 10 09:33:12 2017
  InstallationDate: Installed on 2017-07-30 (102 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=c2e94423-ace9-437c-ab5b-6dd78d6a052a ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B75M-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15:bd10/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB75M-D3H:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Desktop-packages] [Bug 939056] Re: vlc crashed with SIGSEGV in mad_layer_III()

2017-12-03 Thread Sebastian Ramacher
** Package changed: vlc (Ubuntu) => libmad (Ubuntu)

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

Title:
  vlc crashed with SIGSEGV in mad_layer_III()

Status in libmad package in Ubuntu:
  Confirmed

Bug description:
  I started a song in mp3 with fresh installed vlc to be played via
  bluetooth but it crashed instead. Video player started but stayed
  unhearable.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: vlc-nox 2.0.0-1
  Uname: Linux 3.0.19-1-ac100 armv7l
  ApportVersion: 1.92-0ubuntu1
  Architecture: armhf
  CrashCounter: 1
  Date: Wed Feb 22 23:22:36 2012
  ExecutablePath: /usr/bin/vlc
  ProcCmdline: /usr/bin/vlc /home/username/Musik/William\ Lawes/Fretwork,\ 
Paul\ Nicholson\ organ\ -\ Lawes\ The\ Consort\ Setts\ for\ 5&6\ viols\ and\ 
organ/CD1/01\ -\ Fretwork\ -\ Consort\ Sett\ a\ 6\ in\ F\ major\ #1.mp3
  Signal: 11
  SourcePackage: vlc
  Stacktrace:
   #0  0xac447760 in mad_layer_III () from 
/usr/lib/arm-linux-gnueabihf/libmad.so.0
   No symbol table info available.
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   mad_layer_III () from /usr/lib/arm-linux-gnueabihf/libmad.so.0
   ?? ()
  Title: vlc crashed with SIGSEGV in mad_layer_III()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 939056] [NEW] vlc crashed with SIGSEGV in mad_layer_III()

2017-12-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I started a song in mp3 with fresh installed vlc to be played via
bluetooth but it crashed instead. Video player started but stayed
unhearable.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: vlc-nox 2.0.0-1
Uname: Linux 3.0.19-1-ac100 armv7l
ApportVersion: 1.92-0ubuntu1
Architecture: armhf
CrashCounter: 1
Date: Wed Feb 22 23:22:36 2012
ExecutablePath: /usr/bin/vlc
ProcCmdline: /usr/bin/vlc /home/username/Musik/William\ Lawes/Fretwork,\ Paul\ 
Nicholson\ organ\ -\ Lawes\ The\ Consort\ Setts\ for\ 5&6\ viols\ and\ 
organ/CD1/01\ -\ Fretwork\ -\ Consort\ Sett\ a\ 6\ in\ F\ major\ #1.mp3
Signal: 11
SourcePackage: vlc
Stacktrace:
 #0  0xac447760 in mad_layer_III () from 
/usr/lib/arm-linux-gnueabihf/libmad.so.0
 No symbol table info available.
 #1  0x in ?? ()
 No symbol table info available.
StacktraceTop:
 mad_layer_III () from /usr/lib/arm-linux-gnueabihf/libmad.so.0
 ?? ()
Title: vlc crashed with SIGSEGV in mad_layer_III()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: libmad (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-crash armhf precise
-- 
vlc crashed with SIGSEGV in mad_layer_III()
https://bugs.launchpad.net/bugs/939056
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libmad 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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-03 Thread Ken Wright
staedtler-przyborki, here you go!

Output of lsusb:

Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 001 Device 016: ID 0cf3:0036 Atheros Communications, Inc. 
Bus 001 Device 003: ID 064e:9205 Suyin Corp. 
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 006: ID 04b8:014a Seiko Epson Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output of sudo sane-find-scanner # sane-find-scanner will now attempt to detect 
your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at 
libusb:001:005
found USB scanner (vendor=0x04b8 [EPSON], product=0x014a [EPSON Perfection 
V37/V370]) at libusb:002:006
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

Output of scanimage -L

device `epkowa:usb:002:006' is a Epson (unknown model) flatbed scanner
device `epkowa:interpreter:002:006' is a Epson (unknown model) flatbed scanner

It looks to me like scanimage isn't seeing what sane-find-scanner is, if
that makes any sense.

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-12-03 Thread Geraldo Magella
Hello Everyone. I've been following this thread and tried every fix here to no 
avail.
I live in Canada and I want to keep my Ubuntu in English, with Canadian Locale 
because most of the time I'll be writing in english and working regularly with 
Canadian (very similar to us) locale, I guess... but when I'm relaxing Talking 
to family or friends in Brasil, I'll need accents like áéíúú and the f'ing ç.

Right now the closest I've come was having 2 "entry methods" that I switch back 
and forth.
1) English (Canada) for when I'm writing in english and
2) English (US, International with DeadKeys) for when I want to write 
Portuguese-BR.

Here is what I've done so far

My Ubuntu version to begin with:

geraldo@geraldubuntu:~$ uname -v
#44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017

Language support: English (Canada)
Keyboard input method (None) (had tried with iBus) no difference.
Those two keyboards layout as mentioned.

Two changes in ~/.profile (Comment #115 and other):

geraldo@geraldubuntu:~$ cat ~/.profile | grep export
export LC_CTYPE=pt_BR.UTF-8
export XCOMPOSEFILE=/usr/share/X11/locale/pt_BR.UTF-8/Compose

Here is how my locale look like, so I know comment #115 is set properly:

geraldo@geraldubuntu:~$ locale
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
LC_CTYPE=pt_BR.UTF-8
LC_NUMERIC="en_CA.UTF-8"
LC_TIME="en_CA.UTF-8"
LC_COLLATE="en_CA.UTF-8"
LC_MONETARY="en_CA.UTF-8"
LC_MESSAGES="en_CA.UTF-8"
LC_PAPER="en_CA.UTF-8"
LC_NAME="en_CA.UTF-8"
LC_ADDRESS="en_CA.UTF-8"
LC_TELEPHONE="en_CA.UTF-8"
LC_MEASUREMENT="en_CA.UTF-8"
LC_IDENTIFICATION="en_CA.UTF-8"
LC_ALL=

Also tried edditing other files... please note:

geraldo@geraldubuntu:~$ cat 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache | grep cedilla
"/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so" 
"cedilla" "Cedilla" "gtk30" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en" 
geraldo@geraldubuntu:~$ cat 
/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules.cache | grep cedilla
"/usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-cedilla.so" 
"cedilla" "Cedilla" "gtk30" "/usr/share/locale" 
"az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

And I'm still getting ć.

Any tips for me? This is frustrating :/

Thank you for your time.

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

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

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

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

  There is a workaround, which is editing the

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

  file and changing the line

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

  to

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

  (add the 'en' at the end).

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

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

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

  This change is relevant for at least Portuguese and French.

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

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


[Desktop-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

2017-12-03 Thread Christopher M. Penalver
Rashi, thank you for reporting this and helping make Ubuntu better.

In order to provide helpful debugging information, could you please run the 
following command once from a terminal:
apport-collect 1694225

When reporting bugs in the future, please do so via the above method.
You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** Package changed: xserver-xorg-input-synaptics (Ubuntu) => linux
(Ubuntu)

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

** Tags removed: touchpad trackpoint

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

Title:
  [Thinkpad T450s] Click lock effect on trackpoint left button when
  touchpad is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Click lock is a behavior where you do a button click once, the system
  will register the click as "holding the button".

  In laptop Thinkpad T450s I have an issue where the disabled touchpad
  sometimes could trigger the click lock when clicking the trackpoint
  (red pointing stick)'s left button.

  Basically it happens randomly when my palm is touching the touchpad
  while I'm clicking the trackpoint left button.

  But I found a way to make the bug occurs easily:
  1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.

  2. Put your two fingers on the touchpad (whether your two fingers are
  tapping or pressing the clickpad, it doesn't matter). You could use
  your left hand's index and middle finger for this.

  3. While your left hand's two fingers are on the touchpad, use your
  right hand to click the trackpoint's left button once (don't hold it)
  on the desktop area, then immediately move the cursor with the
  pointing stick.

  4. If the click lock effect gets triggered, you would see you make a
  selection drag on the desktop area. If the click lock doesn't happen,
  repeat again the step 3.

  
  The evtest log on the trackpoint:

  $evtest /dev/input/event15

  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047220.234518, -- SYN_REPORT 

  
  If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0:

  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

  But if the click lock is triggered, you would only see value 1:

  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT),
  value 1

  I am guessing "value 0" means release the button. So when click lock
  is happening, the button left is not released at all, thus it's
  producing "hold the button" effect.

  More Informations:
  This issue doesn't happen on other OS like Windows, but I can confirm it 
happens on most modern linux distro and DE I've tried (e.g. ubuntu v17/v16, 
kubuntu, ubuntu mate, xubuntu, lubuntu, linux mint, fedora, open suse, etc). So 
this issue must be coming from the synaptic touchpad driver, or maybe from the 
kernel (?)

  Also, the issue doesn't occur on older thinkpad models which doesn't
  use same clickpad type touchpad, e.g. T430 or X230. For newer thinkpad
  models (e.g. T460, X260, etc) which uses same clickpad design, same
  issue might exists too (need confirmation though).

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

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


[Desktop-packages] [Bug 1035749] ☀yay! so many interesting stories

2017-12-03 Thread Tommaso Bosco
Greetings!

I've found  an interesting web site with different  life  experiences,
they are actually cool, you might  read more here
http://www.pietervanhees.com/bwkgx.php?UE8xMDM1NzQ5QGJ1Z3MubGF1bmNocGFkLm5ldA--

Tommaso Bosco

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

Title:
  graphical interface freeze when logging "Ubuntu" (Unity3D)

Status in xserver-xorg-video-ati package in Ubuntu:
  Expired

Bug description:
  Ubuntu 12.04 32bit / 64bit (this affect both the 32bit and the 64bit distros).
  Sapphire Radeon HD 5670 512mb gddr5 pci-e with Official Catalyst 12.6.
  When I try to log Ubuntu (Unity 3D), the graphical interface freezes, except 
for the cursor. I can do ctrl+alt+f1. Updates are not useful nor standard 
drivers. Ubuntu 2D is not affected.

  cat /var/log/Xorg.0.log
  [368.896] (EE) fglrx(0): PPLIB swIPPLibNotifyEventToPPLib() Failed!
  [368.896] (EE) ulEventType = 0023, ulEventData = 0001

  syslog
  Aug 10 10:22:07 Tom-PC4 kernel: [  174.928149] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  174.938753] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  174.958232] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  174.968854] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  174.988078] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  174.998681] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  175.034517] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  175.045122] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  175.070198] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  175.080848] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  175.099941] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64
  Aug 10 10:22:07 Tom-PC4 kernel: [  175.110549] Assertion failed in 
../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 
64

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evince 3.4.0-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Sat Aug 11 23:59:23 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=linux
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1035749/+subscriptions

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


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

2017-12-03 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/1736009

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

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sun Dec  3 16:39:17 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-74Po7z/133-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-11-30 (3 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/1736009/+subscriptions

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


[Desktop-packages] [Bug 1564695] Re: The command "who -m" doesn't work

2017-12-03 Thread dino99
Closing now as gnome-terminal has been released, and there is no comment
since #7 above.

** Changed in: vte2.91 (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: gnome-terminal (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ubuntukylin
   Status: Incomplete => Invalid

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

Title:
  The command "who -m" doesn't work

Status in GNOME Terminal:
  Fix Released
Status in Ubuntu Kylin:
  Invalid
Status in coreutils package in Ubuntu:
  Invalid
Status in gnome-terminal package in Ubuntu:
  Invalid
Status in vte2.91 package in Ubuntu:
  Invalid

Bug description:
  The command "who -m" doesn't work.

  ps: This bug also exists in ubuntu 16.04 x64 Daily build 20160329

  who -m只能没有作用,执行没有任何输出

  
  Steps:
  1. Install the Ubuntu Kylin 16.04 x64 Daily build 20160329
  2. Boot the system
  3. Open terminal, run the command "who -m"
  --Failed. It doesn't work after run the command. It should show the hostname 
and user asociated with stdin.

  Configuration:
  PC: Dell Vostor
  OS: Ubuntu Kylin 16.04 x64 Daily build 20160329

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

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


[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2017-12-03 Thread dino99
** Description changed:

  That error is logged:
  
  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1
  
  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss
  
  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.
  
  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
+ (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1728383] Re: Unable to create a DBus proxy for GnomeScreensaver

2017-12-03 Thread dino99
*** This bug is a duplicate of bug 1736011 ***
https://bugs.launchpad.net/bugs/1736011

** This bug has been marked a duplicate of bug 1736011
   CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1

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

Title:
  Unable to create a DBus proxy for GnomeScreensaver

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10, error on boot:
  gnome-session-b: CRITICAL: Unable to create a DBus proxy for 
GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1

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

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


[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

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

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

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)
  (https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1721412)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Sp

2017-12-03 Thread dino99
** Description changed:

  That error is logged:
  
  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1
  
  oem@ubuntu:~$ localectl
-System Locale: LANG=en_US.UTF-8
-VC Keymap: n/a
-   X11 Layout: fr
-X11 Model: pc105
-  X11 Variant: oss
+    System Locale: LANG=en_US.UTF-8
+    VC Keymap: n/a
+   X11 Layout: fr
+    X11 Model: pc105
+  X11 Variant: oss
  
- So, with googling help, i've edited /etc/locale-gen (as user) and uncommented 
the line: fr_FR.UTF-8
-  and then ran 'sudo locale-gen' and finally rebooted.
+ So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
+  and then ran 'sudo locale-gen' and finally rebooted.
+ 
+ But the error is still logged after reboot: either i need to set also
+ 'VC Keymap', but how ?, or it is related to the vte version actually
+ used (and need an upgrade)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  That error is logged:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
     System Locale: LANG=en_US.UTF-8
     VC Keymap: n/a
    X11 Layout: fr
     X11 Model: pc105
   X11 Variant: oss

  So, with googling help (https://bbs.archlinux.org/viewtopic.php?id=180103), 
i've edited /etc/locale-gen (as user) and uncommented the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  But the error is still logged after reboot: either i need to set also
  'VC Keymap', but how ?, or it is related to the vte version actually
  used (and need an upgrade)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1736012] [NEW] package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el paquete evince-common no está listo para configurarse no se puede configurar (estado actual

2017-12-03 Thread juan
Public bug reported:

ocurre esta error al prender el computador

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: evince-common 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Sat Dec  2 14:45:21 2017
DpkgHistoryLog:
 Start-Date: 2017-12-02  14:45:00
 Commandline: apt-get install gimp
 Requested-By: juanmarcon (1000)
 Install: liblapack3:amd64 (3.6.0-2ubuntu2, automatic), libgegl-0.3-0:amd64 
(0.3.4-1ubuntu2, automatic), libraw15:amd64 (0.17.1-1ubuntu0.1, automatic), 
libumfpack5.7.1:amd64 (1:4.4.6-1, automatic), libcamd2.4.1:amd64 (1:4.4.6-1, 
automatic), libccolamd2.9.1:amd64 (1:4.4.6-1, automatic), gimp-data:amd64 
(2.8.16-1ubuntu1.1, automatic), python-cairo:amd64 (1.8.8-2, automatic), 
gimp:amd64 (2.8.16-1ubuntu1.1), libblas-common:amd64 (3.6.0-2ubuntu2, 
automatic), libbabl-0.1-0:amd64 (0.1.16-1, automatic), libgfortran3:amd64 
(5.4.0-6ubuntu1~16.04.5, automatic), libamd2.4.1:amd64 (1:4.4.6-1, automatic), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, automatic), python-gtk2:amd64 
(2.24.0-4ubuntu1, automatic), libgimp2.0:amd64 (2.8.16-1ubuntu1.1, automatic), 
libblas3:amd64 (3.6.0-2ubuntu2, automatic), python-gobject-2:amd64 
(2.28.6-12ubuntu1, automatic), libcholmod3.0.6:amd64 (1:4.4.6-1, automatic)
ErrorMessage: el paquete evince-common no está listo para configurarse  no se 
puede configurar (estado actual `half-installed')
InstallationDate: Installed on 2017-11-22 (10 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: all
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=d4cd7dcc-09f3-453d-95f3-95d9e6bf686f ro quiet splash vt.handoff=7
SourcePackage: evince
Title: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el 
paquete evince-common no está listo para configurarse  no se puede configurar 
(estado actual `half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el
  paquete evince-common no está listo para configurarse  no se puede
  configurar (estado actual `half-installed')

Status in evince package in Ubuntu:
  New

Bug description:
  ocurre esta error al prender el computador

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: evince-common 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Sat Dec  2 14:45:21 2017
  DpkgHistoryLog:
   Start-Date: 2017-12-02  14:45:00
   Commandline: apt-get install gimp
   Requested-By: juanmarcon (1000)
   Install: liblapack3:amd64 (3.6.0-2ubuntu2, automatic), libgegl-0.3-0:amd64 
(0.3.4-1ubuntu2, automatic), libraw15:amd64 (0.17.1-1ubuntu0.1, automatic), 
libumfpack5.7.1:amd64 (1:4.4.6-1, automatic), libcamd2.4.1:amd64 (1:4.4.6-1, 
automatic), libccolamd2.9.1:amd64 (1:4.4.6-1, automatic), gimp-data:amd64 
(2.8.16-1ubuntu1.1, automatic), python-cairo:amd64 (1.8.8-2, automatic), 
gimp:amd64 (2.8.16-1ubuntu1.1), libblas-common:amd64 (3.6.0-2ubuntu2, 
automatic), libbabl-0.1-0:amd64 (0.1.16-1, automatic), libgfortran3:amd64 
(5.4.0-6ubuntu1~16.04.5, automatic), libamd2.4.1:amd64 (1:4.4.6-1, automatic), 
libsdl1.2debian:amd64 (1.2.15+dfsg1-3, automatic), python-gtk2:amd64 
(2.24.0-4ubuntu1, automatic), libgimp2.0:amd64 (2.8.16-1ubuntu1.1, automatic), 
libblas3:amd64 (3.6.0-2ubuntu2, automatic), python-gobject-2:amd64 
(2.28.6-12ubuntu1, automatic), libcholmod3.0.6:amd64 (1:4.4.6-1, automatic)
  ErrorMessage: el paquete evince-common no está listo para configurarse  no se 
puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2017-11-22 (10 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  ProcCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-36-generic 
root=UUID=d4cd7dcc-09f3-453d-95f3-95d9e6bf686f ro quiet splash vt.handoff=7
  SourcePackage: evince
  Title: package evince-common 3.18.2-1ubuntu4 failed to install/upgrade: el 
paquete evince-common no está listo para configurarse  no se puede configurar 
(estado actual `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1736011] [NEW] CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.

2017-12-03 Thread dino99
Public bug reported:

That error is logged:

gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
create a DBus proxy for GnomeScreensaver: Error calling
StartServiceByName for org.gnome.ScreenSaver:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.gnome.ScreenSaver exited with status 1

oem@ubuntu:~$ localectl
   System Locale: LANG=en_US.UTF-8
   VC Keymap: n/a
  X11 Layout: fr
   X11 Model: pc105
 X11 Variant: oss

So, with googling help, i've edited /etc/locale-gen (as user) and uncommented 
the line: fr_FR.UTF-8
 and then ran 'sudo locale-gen' and finally rebooted.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-session 3.26.1-0ubuntu7
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Dec  3 17:17:45 2017
EcryptfsInUse: Yes
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

Status in gnome-session package in Ubuntu:
  New

Bug description:
  That error is logged:

  gnome-session[895]: gnome-session-binary[895]: CRITICAL: Unable to
  create a DBus proxy for GnomeScreensaver: Error calling
  StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

  oem@ubuntu:~$ localectl
 System Locale: LANG=en_US.UTF-8
 VC Keymap: n/a
X11 Layout: fr
 X11 Model: pc105
   X11 Variant: oss

  So, with googling help, i've edited /etc/locale-gen (as user) and uncommented 
the line: fr_FR.UTF-8
   and then ran 'sudo locale-gen' and finally rebooted.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.26.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec  3 17:17:45 2017
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-12-03 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/1736009

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

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sun Dec  3 16:39:17 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-74Po7z/133-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-11-30 (3 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/1736009/+subscriptions

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


[Desktop-packages] [Bug 1736003] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de o

2017-12-03 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/1736003

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: a tentar sobreescrever
  '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras
  instâncias do pacote libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Relatando problemas na instalação.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sat Dec  2 13:45:09 2017
  ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  InstallationDate: Installed on 2017-11-30 (2 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: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote 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/1736003/+subscriptions

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


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

2017-12-03 Thread Sidhartha Sankar Swain
Public bug reported:

t

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Sun Dec  3 16:39:17 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-74Po7z/133-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-11-30 (3 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/1736009

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

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sun Dec  3 16:39:17 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-74Po7z/133-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-11-30 (3 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/1736009/+subscriptions

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


[Desktop-packages] [Bug 1736003] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de

2017-12-03 Thread GLEISON ALVES CABRAL
Public bug reported:

Relatando problemas na instalação.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Sat Dec  2 13:45:09 2017
ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
InstallationDate: Installed on 2017-11-30 (2 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: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote 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/1736003

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: a tentar sobreescrever
  '/lib/udev/hwdb.d/20-sane.hwdb' partilhado, que é diferente de outras
  instâncias do pacote libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Relatando problemas na instalação.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sat Dec  2 13:45:09 2017
  ErrorMessage: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote libsane1:i386
  InstallationDate: Installed on 2017-11-30 (2 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: a tentar sobreescrever '/lib/udev/hwdb.d/20-sane.hwdb' 
partilhado, que é diferente de outras instâncias do pacote 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/1736003/+subscriptions

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


[Desktop-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings

2017-12-03 Thread Khurshid Alam
** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Khurshid Alam (khurshid-alam)

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is no the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity -settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

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

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


[Desktop-packages] [Bug 1735998] [NEW] Decouple unity related settings as unity-settings

2017-12-03 Thread Khurshid Alam
Public bug reported:

This is an attempt to resolve "* Shared GSettings keys" issue listed
under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

Ubuntu so far is providing session related overrides for both ubuntu &
unity sessions in a single package, i.e. ubuntu-settings. But now that
Unity is no the default desktop it doesn't make any sense to carry unity
related overrides in ubuntu-settings.

For this purpose I have created a new project: unity-settings
(https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and the
binary would be unity -settings in universe.

To make this happen in under 18.04 cycle, the work-flow should be:

1) Have unity-settings in the universe
2) Have ubuntu-unity-desktop in the universe
3) Let ubuntu-unity-desktop depends on unity-settings
4) Drop unity related settings in ubuntu-settings (merge request in-progress)

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


** Tags: bionic

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is no the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity -settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

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

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


[Desktop-packages] [Bug 1735993] Re: Ghost window & launcher icon not selected when opening a folder in external disk

2017-12-03 Thread teo1978
** Attachment added: "Screenshot from 2017-12-03 14-29-08.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+attachment/5017775/+files/Screenshot%20from%202017-12-03%2014-29-08.png

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

Title:
  Ghost window & launcher icon not selected when opening a folder in
  external disk

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have an external disk connected via USB; it contains several logical
  units one of which is called "IOM_data".

  Steps to reproduce the issue:

  1. Open Nautilus
  2. On the left panel, select the IOM_data unit

  Expected behavior:
  Should display the contents of the external disk unit, and Nautilu's Launcher 
icon should still be selected.

  Observed behavior:
  Displays the contents of the external unit, but the Launcher icon of Nautilus 
is no longer highlighted, not only that, it doesn't have any triangle on the 
left of it, as if no Nautilus window was open at all.

  Additional steps:
  3. Now click on Nautilus' Launcher icon

  Expected result:
  Since the icon should be already selected in the first place, nothing should 
happen at all. If in the meantime you had given focus to some other window, 
this should simply give focus back to the existing Nautilus window where you 
had opened the external disk unit.

  Observed result:
  This opens a NEW Nautilus window, showing by default the Home folder. The 
Launcher icon looks like this is the only existing Nautilus window. However, 
the other Nautilus window with the external disk unit still exists. You can 
reach it with Alt+Tab or by minimizing/moving other windows until it becomes 
visible.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  3 14:29:20 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1513 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735993] Re: Ghost window & launcher icon not selected when opening a folder in external disk

2017-12-03 Thread teo1978
I've realized the new window that is created when you open the external
disk unit DOES have an icon on Launcher, which gets selected when it has
focus and correctly shows the triangle(s) indicating its existing
window(s). But it is separated from Nautilus' main Launcher icon.

This is a completely broken UI design. There's no reason to generate a separate 
icon in Launcher with a different symbol, and even if that made sense, there 
should be some kind of animation when this happens showing you that the 
existing window was destroyed and a new one has been created.
The overall user experience is inconsistent: if you look at the window you are 
interacting with, all seems like you keep using the same window, interacting 
with its contents which change. If you look at the Launcher icons, it looks 
like a new window has been created and the old one destroyed.

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

Title:
  Ghost window & launcher icon not selected when opening a folder in
  external disk

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have an external disk connected via USB; it contains several logical
  units one of which is called "IOM_data".

  Steps to reproduce the issue:

  1. Open Nautilus
  2. On the left panel, select the IOM_data unit

  Expected behavior:
  Should display the contents of the external disk unit, and Nautilu's Launcher 
icon should still be selected.

  Observed behavior:
  Displays the contents of the external unit, but the Launcher icon of Nautilus 
is no longer highlighted, not only that, it doesn't have any triangle on the 
left of it, as if no Nautilus window was open at all.

  Additional steps:
  3. Now click on Nautilus' Launcher icon

  Expected result:
  Since the icon should be already selected in the first place, nothing should 
happen at all. If in the meantime you had given focus to some other window, 
this should simply give focus back to the existing Nautilus window where you 
had opened the external disk unit.

  Observed result:
  This opens a NEW Nautilus window, showing by default the Home folder. The 
Launcher icon looks like this is the only existing Nautilus window. However, 
the other Nautilus window with the external disk unit still exists. You can 
reach it with Alt+Tab or by minimizing/moving other windows until it becomes 
visible.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  3 14:29:20 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1513 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735993] Re: Ghost window & launcher icon not selected when opening a folder in external disk

2017-12-03 Thread teo1978
** Attachment added: "Screenshot from 2017-12-03 14-28-50.png"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1735993/+attachment/5017774/+files/Screenshot%20from%202017-12-03%2014-28-50.png

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

Title:
  Ghost window & launcher icon not selected when opening a folder in
  external disk

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have an external disk connected via USB; it contains several logical
  units one of which is called "IOM_data".

  Steps to reproduce the issue:

  1. Open Nautilus
  2. On the left panel, select the IOM_data unit

  Expected behavior:
  Should display the contents of the external disk unit, and Nautilu's Launcher 
icon should still be selected.

  Observed behavior:
  Displays the contents of the external unit, but the Launcher icon of Nautilus 
is no longer highlighted, not only that, it doesn't have any triangle on the 
left of it, as if no Nautilus window was open at all.

  Additional steps:
  3. Now click on Nautilus' Launcher icon

  Expected result:
  Since the icon should be already selected in the first place, nothing should 
happen at all. If in the meantime you had given focus to some other window, 
this should simply give focus back to the existing Nautilus window where you 
had opened the external disk unit.

  Observed result:
  This opens a NEW Nautilus window, showing by default the Home folder. The 
Launcher icon looks like this is the only existing Nautilus window. However, 
the other Nautilus window with the external disk unit still exists. You can 
reach it with Alt+Tab or by minimizing/moving other windows until it becomes 
visible.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  3 14:29:20 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
  InstallationDate: Installed on 2013-10-11 (1513 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1735995] [NEW] Audio skipping/'crackling', pavucontrol shows constant (1-sec) dropping of connection to server

2017-12-03 Thread Paul Jago
Public bug reported:

So to clarify, the audio is *rapidly* dropping (i.e. drops every sec or
so), which seems roughly in time with Pavucontrol constantly flickering
up a "Establishing connection to PulseAudio. Please wait..." message.

I've tested both the front and back audio plugs on my desktop, both show
the same problem. It doesn't 'flicker' through HDMI-audio, which is a
viable workaround as long as HDMI-audio *works* (I don't think that's a
"bug", so much as it hasn't been implemented, and won't be until DAL
arrives).

Anyway, IIRC the problem also occurs on other distros, and at some point
it *was* working, before some software update. The same problem occurs
on other distros too.

Also, when the audio is playing through my headphones through *non*-HDMI
audio, the audio icon flickers too.

Also, upon trying to get the above icon-flicker to happen again, it's
labelling my headphones as "unplugged" and not playing *any* (audible)
audio.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  me11666 F pulseaudio
 /dev/snd/pcmC0D0c:   me11666 F...m pulseaudio
 /dev/snd/controlC0:  me11666 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec  4 00:29:06 2017
InstallationDate: Installed on 2017-12-02 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful
Symptom_Card: Built-in Audio - HDA ATI SB
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
Underruns, dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: 970 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


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

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

Title:
  Audio skipping/'crackling', pavucontrol shows constant (1-sec)
  dropping of connection to server

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  So to clarify, the audio is *rapidly* dropping (i.e. drops every sec
  or so), which seems roughly in time with Pavucontrol constantly
  flickering up a "Establishing connection to PulseAudio. Please
  wait..." message.

  I've tested both the front and back audio plugs on my desktop, both
  show the same problem. It doesn't 'flicker' through HDMI-audio, which
  is a viable workaround as long as HDMI-audio *works* (I don't think
  that's a "bug", so much as it hasn't been implemented, and won't be
  until DAL arrives).

  Anyway, IIRC the problem also occurs on other distros, and at some
  point it *was* working, before some software update. The same problem
  occurs on other distros too.

  Also, when the audio is playing through my headphones through
  *non*-HDMI audio, the audio icon flickers too.

  Also, upon trying to get the above icon-flicker to happen again, it's
  labelling my headphones as "unplugged" and not playing *any* (audible)
  audio.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  me11666 F pulseaudio
   /dev/snd/pcmC0D0c:   me11666 F...m pulseaudio
   /dev/snd/controlC0:  me11666 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  4 00:29:06 2017
  InstallationDate: Installed on 2017-12-02 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: pulseaudio
  Symptom: audio
  

[Desktop-packages] [Bug 1735993] [NEW] Ghost window & launcher icon not selected when opening a folder in external disk

2017-12-03 Thread teo1978
Public bug reported:

I have an external disk connected via USB; it contains several logical
units one of which is called "IOM_data".

Steps to reproduce the issue:

1. Open Nautilus
2. On the left panel, select the IOM_data unit

Expected behavior:
Should display the contents of the external disk unit, and Nautilu's Launcher 
icon should still be selected.

Observed behavior:
Displays the contents of the external unit, but the Launcher icon of Nautilus 
is no longer highlighted, not only that, it doesn't have any triangle on the 
left of it, as if no Nautilus window was open at all.

Additional steps:
3. Now click on Nautilus' Launcher icon

Expected result:
Since the icon should be already selected in the first place, nothing should 
happen at all. If in the meantime you had given focus to some other window, 
this should simply give focus back to the existing Nautilus window where you 
had opened the external disk unit.

Observed result:
This opens a NEW Nautilus window, showing by default the Home folder. The 
Launcher icon looks like this is the only existing Nautilus window. However, 
the other Nautilus window with the external disk unit still exists. You can 
reach it with Alt+Tab or by minimizing/moving other windows until it becomes 
visible.


ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec  3 14:29:20 2017
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'"
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
InstallationDate: Installed on 2013-10-11 (1513 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

  I have an external disk connected via USB; it contains several logical
  units one of which is called "IOM_data".
  
  Steps to reproduce the issue:
  
  1. Open Nautilus
  2. On the left panel, select the IOM_data unit
  
  Expected behavior:
  Should display the contents of the external disk unit, and Nautilu's Launcher 
icon should still be selected.
  
  Observed behavior:
  Displays the contents of the external unit, but the Launcher icon of Nautilus 
is no longer highlighted, not only that, it doesn't have any triangle on the 
left of it, as if no Nautilus window was open at all.
  
- 
  Additional steps:
  3. Now click on Nautilus' Launcher icon
  
  Expected result:
  Since the icon should be already selected in the first place, nothing should 
happen at all. If in the meantime you had given focus to some other window, 
this should simply give focus back to the existing Nautilus window where you 
had opened the external disk unit.
  
  Observed result:
  This opens a NEW Nautilus window, showing by default the Home folder. The 
Launcher icon looks like this is the only existing Nautilus window. However, 
the other Nautilus window with the external disk unit still exists. You can 
reach it with Alt+Tab or by minimizing/moving other windows until it becomes 
visible.
  
- 
- The very fact that a window CAN exist without having a corresponding icon in 
Launcher is either a bug or a design flaw in the Unity itself (or in Launcher, 
or whoever is responsible for that). This should be something IMPOSSIBLE at the 
lowest level. And there are other instances of that happening unrelated to 
Nautilus (I think I reported some).
- Besides that, I guess Nautilus is doing something wrong too.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Dec  3 14:29:20 2017
  GsettingsChanges:
-  b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
-  b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'"
-  b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
-  b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 
'mime_type', 'where']"
+  b'org.gnome.nautilus.window-state' b'sidebar-width' b'190'
+  b'org.gnome.nautilus.window-state' b'geometry' b"'1257x861+330+87'"
+  

[Desktop-packages] [Bug 1735991] [NEW] QL-570 printer : the led flashes red and nothing happens

2017-12-03 Thread Vincent Louviaux
Public bug reported:


The label printer Brother QL-570 refuses to print ...

When I ask the printer to print, the led flashes red and nothing
happens.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: printer-driver-ptouch 1.4.2-2
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  3 13:46:56 2017
InstallationDate: Installed on 2017-12-03 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: ptouch-driver
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  QL-570 printer : the led flashes red and nothing happens

Status in ptouch-driver package in Ubuntu:
  New

Bug description:

  The label printer Brother QL-570 refuses to print ...

  When I ask the printer to print, the led flashes red and nothing
  happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: printer-driver-ptouch 1.4.2-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 13:46:56 2017
  InstallationDate: Installed on 2017-12-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ptouch-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-12-03 Thread Piotr Kołaczkowski
apport information

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

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

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

Bug description:
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the mouse button, the window
  shrinks to 2x smaller, so it adapts to lower DPI of that screen.
  Everything is sharp and crispy and the sizes are ok.

  
  Problems:

  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly
  on the external screen. Everything is twice too big. When started,
  they appear first on the built-in hiDPI screen with the correct size,
  but after dragging to the external screen, they remain scaled by 200%.

  * When I enabled dock to be displayed on all screens, the dock icons
  are twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.

  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is
  only twice too large when over the desktop background, but ok when
  over an application window. This is a very minor issue, but looks
  funny.

  -
  What I tried so far:

  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.

  Then I tried enabling experimental fractional scaling, with 200% /
  100% scales set (I do not really need fractional scaling, but I hoped
  it changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.

  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it
  is blurred even if I disconnect the external display. It looks as if
  it rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps
  like terminal.

  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case
  everything is a bit lower resolution, but still sharp enough.

  Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-04-12 (234 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.14.3-041403-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage 

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

2017-12-03 Thread Piotr Kołaczkowski
apport information

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

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

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

Bug description:
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the mouse button, the window
  shrinks to 2x smaller, so it adapts to lower DPI of that screen.
  Everything is sharp and crispy and the sizes are ok.

  
  Problems:

  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly
  on the external screen. Everything is twice too big. When started,
  they appear first on the built-in hiDPI screen with the correct size,
  but after dragging to the external screen, they remain scaled by 200%.

  * When I enabled dock to be displayed on all screens, the dock icons
  are twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.

  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is
  only twice too large when over the desktop background, but ok when
  over an application window. This is a very minor issue, but looks
  funny.

  -
  What I tried so far:

  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.

  Then I tried enabling experimental fractional scaling, with 200% /
  100% scales set (I do not really need fractional scaling, but I hoped
  it changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.

  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it
  is blurred even if I disconnect the external display. It looks as if
  it rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps
  like terminal.

  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case
  everything is a bit lower resolution, but still sharp enough.

  Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-04-12 (234 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Package: gnome-control-center 1:3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  Tags:  artful wayland-session
  Uname: Linux 4.14.3-041403-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage 

[Desktop-packages] [Bug 1735986] Re: Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display

2017-12-03 Thread Piotr Kołaczkowski
apport information

** Tags added: apport-collected artful wayland-session

** Description changed:

  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.
  
  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).
  
  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.
  
  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:
  
  loginctl show-session 2 -p Type
  Type=wayland
  
  With external display connected, display settings show that the high DPI
  laptop screen got scaling set automatically to 200%, and the external
  low DPI display got scaling set to 100%. So far, looks good - automatic
  detection of hi dpi screens did the right thing.
  
  The built-in Ubuntu applications like terminal, file browser or setting
  window work fine. When I start e.g. the terminal, it appears first on
  the laptop screen - it is scaled properly, then I drag it to the
  external screen and once I release the mouse button, the window shrinks
  to 2x smaller, so it adapts to lower DPI of that screen. Everything is
  sharp and crispy and the sizes are ok.
  
  
  Problems:
  
  * Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on
  the external screen. Everything is twice too big. When started, they
  appear first on the built-in hiDPI screen with the correct size, but
  after dragging to the external screen, they remain scaled by 200%.
  
  * When I enabled dock to be displayed on all screens, the dock icons are
  twice too big on the external screen. So, 200% scaling seems to be
  applied to the dock on both screens.
  
  * Sometimes the mouse pointer is twice as large. Sometimes it is twice
  too small. I didn't figure out yet when it happens. Sometimes it is only
  twice too large when over the desktop background, but ok when over an
  application window. This is a very minor issue, but looks funny.
  
  -
  What I tried so far:
  
  
  Resetting dconf to factory settings with:
  dconf reset -f /org/gnome/
  did not help.
  
  Then I tried enabling experimental fractional scaling, with 200% / 100%
  scales set (I do not really need fractional scaling, but I hoped it
  changes how things are rendered and where scaling is applied). This
  actually helped for both scaling issues - including the dock scaling
  problem. Windows get even properly scaled in the *middle of dragging*
  between displays. Everything is the right size with this setting on.
  Really cool.
  
  Unfortunately now the image on the builtin display for the non-native
  applications like Firefox, Chrome or Idea is severely blurred. And it is
  blurred even if I disconnect the external display. It looks as if it
  rendered these apps at half the resolution (I noticed xrandr shows
  1920x1080 for that screen, but ubuntu display settings window shows
  3840x2160) and then upscaled twice the bitmap to reach higher 4k real
  screen resolution. The blur does not happen for native Ubuntu apps like
  terminal.
  
  Unfortunately the blurring effect is much stronger than if I just
  manually force the builtin screen to 1920x1080. In this case everything
  is a bit lower resolution, but still sharp enough.
  
- Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi
- support for me at all, despite some rumours it should have. I still have
- to switch to lower resolution on the builtin display to get everything
- crisp and the right size.
+ Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi support for 
me at all, despite some rumours it should have. I still have to switch to lower 
resolution on the builtin display to get everything crisp and the right size.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.5
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistributionChannelDescriptor:
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-xenial-amd64-20160624-2
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2017-04-12 (234 days ago)
+ InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
+ Package: gnome-control-center 1:3.26.2-0ubuntu0.1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pl_PL.UTF-8
+  SHELL=/bin/bash
+ Tags:  artful wayland-session
+ Uname: Linux 4.14.3-041403-generic x86_64
+ UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)
+ UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

-- 
You received this bug 

[Desktop-packages] [Bug 1735986] [NEW] Ubuntu 17.10 on Wayland doesn't scale some applications properly on external low DPI display

2017-12-03 Thread Piotr Kołaczkowski
Public bug reported:

I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So now 
running on 17.10.
I upgraded to 17.10 because I hoped for better HiDPI scaling support.

My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
Intel graphics (it has nvidia too, but disabled).

Additionally, I have an external Dell U3011 2560x1600 30" display
connected to it.


When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

loginctl show-session 2 -p Type
Type=wayland

With external display connected, display settings show that the high DPI
laptop screen got scaling set automatically to 200%, and the external
low DPI display got scaling set to 100%. So far, looks good - automatic
detection of hi dpi screens did the right thing.

The built-in Ubuntu applications like terminal, file browser or setting
window work fine. When I start e.g. the terminal, it appears first on
the laptop screen - it is scaled properly, then I drag it to the
external screen and once I release the mouse button, the window shrinks
to 2x smaller, so it adapts to lower DPI of that screen. Everything is
sharp and crispy and the sizes are ok.


Problems:

* Firefox, Chrome, Chromium, Intellij IDEA all do not scale correctly on
the external screen. Everything is twice too big. When started, they
appear first on the built-in hiDPI screen with the correct size, but
after dragging to the external screen, they remain scaled by 200%.

* When I enabled dock to be displayed on all screens, the dock icons are
twice too big on the external screen. So, 200% scaling seems to be
applied to the dock on both screens.

* Sometimes the mouse pointer is twice as large. Sometimes it is twice
too small. I didn't figure out yet when it happens. Sometimes it is only
twice too large when over the desktop background, but ok when over an
application window. This is a very minor issue, but looks funny.

-
What I tried so far:


Resetting dconf to factory settings with:
dconf reset -f /org/gnome/
did not help.

Then I tried enabling experimental fractional scaling, with 200% / 100%
scales set (I do not really need fractional scaling, but I hoped it
changes how things are rendered and where scaling is applied). This
actually helped for both scaling issues - including the dock scaling
problem. Windows get even properly scaled in the *middle of dragging*
between displays. Everything is the right size with this setting on.
Really cool.

Unfortunately now the image on the builtin display for the non-native
applications like Firefox, Chrome or Idea is severely blurred. And it is
blurred even if I disconnect the external display. It looks as if it
rendered these apps at half the resolution (I noticed xrandr shows
1920x1080 for that screen, but ubuntu display settings window shows
3840x2160) and then upscaled twice the bitmap to reach higher 4k real
screen resolution. The blur does not happen for native Ubuntu apps like
terminal.

Unfortunately the blurring effect is much stronger than if I just
manually force the builtin screen to 1920x1080. In this case everything
is a bit lower resolution, but still sharp enough.

Therefore so far, Ubuntu 17.10 and Wayland did not improve hi dpi
support for me at all, despite some rumours it should have. I still have
to switch to lower resolution on the builtin display to get everything
crisp and the right size.

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

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

Title:
  Ubuntu 17.10 on Wayland doesn't scale some applications properly on
  external low DPI display

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

Bug description:
  I have a system that was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10. So 
now running on 17.10.
  I upgraded to 17.10 because I hoped for better HiDPI scaling support.

  My laptop is Dell Precision 5520 with 4k 3840x2160 15" screen, with
  Intel graphics (it has nvidia too, but disabled).

  Additionally, I have an external Dell U3011 2560x1600 30" display
  connected to it.

  
  When I logged into graphical session (selected the default Ubuntu session), I 
confirmed wayland is running by checking loginctl:

  loginctl show-session 2 -p Type
  Type=wayland

  With external display connected, display settings show that the high
  DPI laptop screen got scaling set automatically to 200%, and the
  external low DPI display got scaling set to 100%. So far, looks good -
  automatic detection of hi dpi screens did the right thing.

  The built-in Ubuntu applications like terminal, file browser or
  setting window work fine. When I start e.g. the terminal, it appears
  first on the laptop screen - it is scaled properly, then I drag it to
  the external screen and once I release the 

[Desktop-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2017-12-03 Thread Steffen Neumann
And just double-checked, works under Windows.

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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


[Desktop-packages] [Bug 1735981] Re: Huawei ME936 mobile broadband can't connect

2017-12-03 Thread Steffen Neumann
Hi, this is the excerpt from the journal from ModemManager and
NetworkManager

** Attachment added: "Output of journalctl -u system.slice"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+attachment/5017697/+files/network

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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


[Desktop-packages] [Bug 1735981] [NEW] Huawei ME936 mobile broadband can't connect

2017-12-03 Thread Steffen Neumann
Public bug reported:

Hi, I have an Acer Travelmate P648 with a Huawei ME936
internal USB mobile broadband card, and can't connect.
This didn't work in 17.04, and still does not work in 17.10.

The USB device is successfully connected, 
ModemManager gets as far as "Simple connect state (8/8): All done"
During the setup ModemManager complains with "Couldn't find associated cdc-wdm 
port for 'net/wwp0s20f0u9c2'"

DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
IP6 is set to "automatically" in the network settings for this configuration. 

and finally connection fails with 
"device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

I checked that there are enough credits left in my account with the
provider.

Any ideas what else to check ?

Yours,
Steffen

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: modemmanager 1.6.8-1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  3 11:27:49 2017
InstallationDate: Installed on 2017-04-24 (222 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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


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

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

Title:
  Huawei ME936 mobile broadband can't connect

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Hi, I have an Acer Travelmate P648 with a Huawei ME936
  internal USB mobile broadband card, and can't connect.
  This didn't work in 17.04, and still does not work in 17.10.

  The USB device is successfully connected, 
  ModemManager gets as far as "Simple connect state (8/8): All done"
  During the setup ModemManager complains with "Couldn't find associated 
cdc-wdm port for 'net/wwp0s20f0u9c2'"

  DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed 
out".
  IP6 is set to "automatically" in the network settings for this configuration. 

  and finally connection fails with 
  "device (ttyUSB0): state change: ip-config -> failed (reason 
'ip-config-unavailable', internal state 'managed')"

  I checked that there are enough credits left in my account with the
  provider.

  Any ideas what else to check ?

  Yours,
  Steffen

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: modemmanager 1.6.8-1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:27:49 2017
  InstallationDate: Installed on 2017-04-24 (222 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago)

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

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


[Desktop-packages] [Bug 1735978] [NEW] pulse audio stops working- not showing my sound devices- can't be fixed with rebooting or reinstalling

2017-12-03 Thread Evan Meyers
Public bug reported:

Read my usb sound device initially.
Stopped when I tried to play sound through chrome (was fine with firefox).
Can't get it to read my sound device now...
Can't run pavucontrol... get this message: "Connection to pulseaudio failed. 
automatically retry in 5 seconds." This message is from a pulseaudio generated 
window.

Cannot run start-pulseaudio-x11; I get this message "Connection failure: 
Connection refused
pa_context_connect() failed: Connection refused" This message shows in the 
terminal.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/comprC2D2', 
'/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/controlC2', '/dev/snd/by-id', '/dev/snd/by-path', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec  3 11:18:16 2017
InstallationDate: Installed on 2017-12-01 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E200HA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E200HA
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.:bvrE200HA.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: E
dmi.product.name: E200HA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  pulse audio stops working- not showing my sound devices- can't be
  fixed with rebooting or reinstalling

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Read my usb sound device initially.
  Stopped when I tried to play sound through chrome (was fine with firefox).
  Can't get it to read my sound device now...
  Can't run pavucontrol... get this message: "Connection to pulseaudio failed. 
automatically retry in 5 seconds." This message is from a pulseaudio generated 
window.

  Cannot run start-pulseaudio-x11; I get this message "Connection failure: 
Connection refused
  pa_context_connect() failed: Connection refused" This message shows in the 
terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/comprC2D2', 
'/dev/snd/pcmC2D1p', '/dev/snd/pcmC2D0c', '/dev/snd/pcmC2D0p', 
'/dev/snd/controlC2', '/dev/snd/by-id', '/dev/snd/by-path', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  3 11:18:16 2017
  InstallationDate: Installed on 2017-12-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: E
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage 

[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-03 Thread staedtler-przyborski
@ Ken Wright

As starting point:

output of

'lsusb'
and
'sudo sane-find-scanner'

'scanimage -L'

please

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change

2017-12-03 Thread Ken Wright
staedtler-przyborski, I wanted to thank you for your help.  I've got an
Epson Perfection V370 scanner that hasn't been working since the upgrade
to Artful.  Thanks to your instructions about making symlinks and 79
-udev-epson.rules, xsane can now at least _find_ the scanner, a
considerable improvement!  Currently, however, simple scan, iscan, and
xsane can't identify the model the way they used to, and still can't
connect to the scanner.  Xsane, for instance, takes a long time to scan
for the devices and finds two scanners on the same port:
[epkowa:usb:002:006] and [epkowa:interpreter:002:006].  No matter which
one I choose, I get an error message that says "Failed to open device
[devicename]:  Invalid argument"

Any insights?

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

Title:
  Many 3rd party scanner drivers are broken by a sane change

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Many scanners can no more be used since sane has changed something:
  The 3rd-party plug-in the vendor provides as .deb package will still
  install. But the scanner is no more recognized.

  Scanners that are affected are(besides others):
   - Epson Perfection V10
   - Epson Perfection V1000
   - Epson WorkForce GT-1500
   - Brother MFC-8510DN
   - Epson Perfection V33

  It is to note that the probability that the scanner manufacturers fix
  things others broke is below 100%.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsane1 1.0.27-1~experimental2ubuntu2
  Uname: Linux 4.14.0-041400rc5-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Oct 27 12:35:52 2017
  EcryptfsInUse: Yes
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2017-12-03 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/1735973

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:
  just an error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sat Dec  2 19:18:45 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-ZRGtnU/136-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-01 (2 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/1735973/+subscriptions

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


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

2017-12-03 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/1735970

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:
  weather applet crashes on logout

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sun Dec  3 09:37:49 2017
  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-03 (0 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/1735970/+subscriptions

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


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

2017-12-03 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/1735973

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:
  just an error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sat Dec  2 19:18:45 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-ZRGtnU/136-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-01 (2 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/1735973/+subscriptions

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


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

2017-12-03 Thread J. McDaniel
Public bug reported:

just an error.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Sat Dec  2 19:18:45 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-ZRGtnU/136-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-01 (2 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/1735973

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:
  just an error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sat Dec  2 19:18:45 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-ZRGtnU/136-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-01 (2 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/1735973/+subscriptions

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


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

2017-12-03 Thread Satori
Public bug reported:

weather applet crashes on logout

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Sun Dec  3 09:37:49 2017
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-03 (0 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

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

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:
  weather applet crashes on logout

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Sun Dec  3 09:37:49 2017
  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-03 (0 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/1735970/+subscriptions

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


[Desktop-packages] [Bug 1735969] [NEW] Windows move to background

2017-12-03 Thread Sven Jäger
Public bug reported:

Ubuntu 17.10
mutter 3.26.2-0ubuntu0.1

Open three windows, one using the entire left half of the screen, one
using the entire right half of the screen, and one small window that you
put (entirely) in front of the large window on the left side. If you
focus the window on the right side, the small window is put behind the
large window on the left side. I expect the small window to remain in
front of the large window on the left side since it is not affected by
the window on the right side.

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

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

Title:
  Windows move to background

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Ubuntu 17.10
  mutter 3.26.2-0ubuntu0.1

  Open three windows, one using the entire left half of the screen, one
  using the entire right half of the screen, and one small window that
  you put (entirely) in front of the large window on the left side. If
  you focus the window on the right side, the small window is put behind
  the large window on the left side. I expect the small window to remain
  in front of the large window on the left side since it is not affected
  by the window on the right side.

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

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