[Desktop-packages] [Bug 1745907] Re: Cannot copy/paste between some applications

[Jean-Baptiste Lallement]

Thanks for your report. It seems you're running Wayland. Does it work
under Xorg (select the session Ubuntu on XOrg on the login screen)?


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

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

Title:
  Cannot copy/paste between some applications

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  When copying simple text with CTRL-C CTRL-v (or menu or context menu)
  between programs, I have noticed that some combinations work but other
  do not (no text is pasted).

  Gedit -> LibreOffice: No text pasted
  LibreOffice -> Gedit: No text pasted

  Firefox -> LibreOffice: OK
  LibreOffice -> Firefox: Not text pasted

  Geany -> Gedit: OK
  Gedit -> Geany: Not text pasted

  Geany -> LibreOffice: OK
  LibreOffice -> Geany: No text pasted

  Geany -> Firefox: OK
  Firefox -> Geany: OK

  OK means the copy/paste happened normally, with the text appearing normally 
when pasting.
  In Firefox I used the text area I am using right now at bugs.launchpad.net.
  In LibreOffice I used Calc's formula bar.

  It was working fine before I upgraded to 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 12:18:14 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-21 (679 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-01-22 (6 days ago)

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

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

[Desktop-packages] [Bug 1730460] Re: Very poor multi-monitor performance in Wayland sessions

[Daniel van Vugt]

** Description changed:

+ Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/3
+ 
+ ---
+ 
  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.
  
  Desktop scaling is 1.0, one is a WXGA screen and another FHD.
  
  Ubuntu session (wayland), 17.10.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
-  b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
-  b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
+  b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
+  b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

Title:
  Very poor multi-monitor performance in Wayland sessions

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  Upstream bug: https://gitlab.gnome.org/GNOME/mutter/issues/3

  ---

  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.

  Desktop scaling is 1.0, one is a WXGA screen and another FHD.

  Ubuntu session (wayland), 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Please note pulseaudio 1:11.1-1ubuntu4 is stuck in bionic-proposed due
to an unrelated bug in gsequencer (bug 1743511). It appears that will be
resolved and unblocked by gsequencer 1.3.6-1 getting out of proposed and
into bionic proper.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1745919] [NEW] unity-control-center crashes with segfault on launch

[No]

Public bug reported:

16.04 - This happened before Nvidia drivers where installed. Output from
executing is below. Stack trace is at:
https://gist.github.com/jjshoe/c4fa1a0f3112e97c96e994fd1bbdd882

[changed@changed-desktop (AWS: prod us-east-1)] /home/changed$ 
unity-control-center 
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".
Xlib:  extension "GLX" missing on display ":0".

(unity-control-center:10056): GLib-CRITICAL **: g_strsplit: assertion
'string != NULL' failed

(unity-control-center:10056): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
Segmentation fault (core dumped)
[changed@changed-desktop (AWS: prod us-east-1)] /home/changed$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20170214-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jan 28 23:27:31 2018
InstallationDate: Installed on 2017-04-14 (289 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
SourcePackage: unity-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  unity-control-center crashes with segfault on launch

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

Bug description:
  16.04 - This happened before Nvidia drivers where installed. Output
  from executing is below. Stack trace is at:
  https://gist.github.com/jjshoe/c4fa1a0f3112e97c96e994fd1bbdd882

  [changed@changed-desktop (AWS: prod us-east-1)] /home/changed$ 
unity-control-center 
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".
  Xlib:  extension "GLX" missing on display ":0".

  (unity-control-center:10056): GLib-CRITICAL **: g_strsplit: assertion
  'string != NULL' failed

  (unity-control-center:10056): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
  Segmentation fault (core dumped)
  [changed@changed-desktop (AWS: prod us-east-1)] /home/changed$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20170214-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
  Uname: Linux 4.4.0-103-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jan 28 23:27:31 2018
  InstallationDate: Installed on 2017-04-14 (289 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial

[Stephen]

I am experiencing this same but on 18.04 Bionic Beaver. Could this patch
be applied there as well?

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

Title:
  Unable to install mesa-opencl-icd because of unmet dependencies on
  Xenial

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Xenial:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 16.04 LTS
  2. Try to install `mesa-opencl-icd` with

  $ sudo apt-get install mesa-opencl-icd
  [sudo] password for user: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done

  
  Expected results:
  * mesa-opencl-icd is installed successfully

  Actual results:
  * got errors as follow

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is 
not going to be installed
 Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is 
not going to be installed
  E: Unable to correct problems, you have held broken packages.

  
  Note: inspired by this AskUbuntu question - 
https://askubuntu.com/q/995274/66509 .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: mesa-opencl-icd (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Jan 12 21:22:22 2018
  DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:2135]
  InstallationDate: Installed on 2014-02-07 (1434 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: ASUSTeK COMPUTER INC. UX32A
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  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.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Jan 12 20:32:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1743710] Re: Ubuntu 16.04: since 2018 text in combo boxes is black and unreadable

[Daniel van Vugt]

** Summary changed:

- Ubuntu 16.04: since 2018 all dropdown menus black and unreadable
+ Ubuntu 16.04: since 2018 text in combo boxes is black and unreadable

** Changed in: ubuntu-themes
   Status: Incomplete => Confirmed

** Changed in: ubuntu-themes (Ubuntu)
   Status: Incomplete => Confirmed

** No longer affects: libreoffice (Ubuntu)

** Tags added: visual-quality

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

Title:
  Ubuntu 16.04: since 2018 text in combo boxes is black and unreadable

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Since 23018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in 
  https://ubuntuforums.org/showthread.php?t=2382505=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+subscriptions

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

[Desktop-packages] [Bug 1745918] Re: Xorg crashed with SIGSEGV

[Apport retracing service]

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

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 #1681084, 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/1745918/+attachment/5044747/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1745918

Title:
  Xorg crashed with SIGSEGV

Status in xorg-server package in Ubuntu:
  New

Bug description:
  after some work with LibreOffice all system suspend and logout all
  users?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jan 29 06:29:57 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:3824]
  InstallationDate: Installed on 2015-12-14 (777 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80K6
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=UUID=73fd1edc-d964-40d3-a1dd-b1ca4118cce6 ro quiet splash vt.handoff=1
  Renderer: Software
  SegvAnalysis:
   Segfault happened at: 0x556abba68a6c:cmp0x10(%rax),%ecx
   PC (0x556abba68a6c) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xorg-server
  StacktraceTop:
   ()
   miPointerSetPosition ()
   ()
   ()
   GetPointerEvents ()
  Title: Xorg crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C2CN17WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Z51-70
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z51-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80K6
  dmi.product.version: Lenovo Z51-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: 

[Desktop-packages] [Bug 1743710] Re: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

[Brendan McCarthy]

Here's gimp showing the issue - bottom left.

** Attachment added: "Screenshot from 2018-01-29 14-20-10.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743710/+attachment/5044775/+files/Screenshot%20from%202018-01-29%2014-20-10.png

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

Title:
  Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

Status in Ubuntu theme:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Since 23018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in 
  https://ubuntuforums.org/showthread.php?t=2382505=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+subscriptions

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

[Desktop-packages] [Bug 1743710] Re: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

[Brendan McCarthy]

Changing this works for me:

In /usr/share/themes/Ambiance/gtk-2.0/gtkrc line 346

Change:
style "menu" = "dark" {

To:
style "menu" = "white" {

And run gtk-theme-switch2 to apply the style change.

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

Title:
  Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

Status in Ubuntu theme:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Since 23018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in 
  https://ubuntuforums.org/showthread.php?t=2382505=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+subscriptions

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

[Desktop-packages] [Bug 1745874] Re: Contradictory and unclear completion report: "Not all files could be backed up" "Your files were successfully backed up"

[Christopher Barrington-Leigh]

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

Oops. Thanks. It looks like that was nearly four years ago.

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

Title:
  Contradictory and unclear completion report: "Not all files could be
  backed up" "Your files were successfully backed up"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When Deja Dup finished, it sent a message to my OS saying that the
  backup was finished but that not all files could be backed up.  I
  clicked on the message to get more information, and it simply
  disappeared.

  I found the dialog window from deja dup and it says:

  Backup Finished

  Your files were successfully backed up and tested.

  With no more comment, it then listed two files (full paths).
  Presumably these are files that were not backed up, yet the window
  says nothing about that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:13:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (71 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745672] Re: Watching mp4 videos is broken

[Daniel van Vugt]

dino99,

Are you using integrated Intel graphics or some other card? Can you
provide output from this command?

  lspci -k

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

Title:
  Watching mp4 videos is broken

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Totem was well able to display mp4 video some days ago (local mp4
  files on hdd); but now when one of these mp4 video is selected, totem
  start as expected, set the sound normally, but the 'video' part is
  fully broken: get a black screen with some colored rectangles and
  multicolored pixels on top of the screen.

  Starting totem into a terminal and playing a video, i get that output:

  oem@ubuntu:~$ totem
  DtsGetHWFeatures: Create File Failed
  DtsGetHWFeatures: Create File Failed
  Running DIL (3.22.0) Version
  DtsDeviceOpen: Opening HW in mode 0
  DtsDeviceOpen: Create File Failed

  Totem 3.26.0-0ubuntu2 was working as expected.
  But the last changelog seems related to that problem:

  totem (3.26.0-0ubuntu3) bionic; urgency=medium

    * Drop patches that provided old-style decorations and menus for Unity7.
  This conveniently also fixes LP: #1502476. LP: #1719322

   -- Daniel van Vugt   Thu, 25 Jan 2018
  05:42:51 +0800

  note: the same mp4 videos can be smoothly played with vlc without
  problem at all. The session is a gnome-shell one under xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 26 20:42:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1745672] Re: Watching mp4 videos is broken

[Daniel van Vugt]

Please also provide a screenshot/photo of the problem, and a copy of the
mp4 file if you are legally able to do so. Or any mp4 file that
reproduces the problem.

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

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

Title:
  Watching mp4 videos is broken

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Totem was well able to display mp4 video some days ago (local mp4
  files on hdd); but now when one of these mp4 video is selected, totem
  start as expected, set the sound normally, but the 'video' part is
  fully broken: get a black screen with some colored rectangles and
  multicolored pixels on top of the screen.

  Starting totem into a terminal and playing a video, i get that output:

  oem@ubuntu:~$ totem
  DtsGetHWFeatures: Create File Failed
  DtsGetHWFeatures: Create File Failed
  Running DIL (3.22.0) Version
  DtsDeviceOpen: Opening HW in mode 0
  DtsDeviceOpen: Create File Failed

  Totem 3.26.0-0ubuntu2 was working as expected.
  But the last changelog seems related to that problem:

  totem (3.26.0-0ubuntu3) bionic; urgency=medium

    * Drop patches that provided old-style decorations and menus for Unity7.
  This conveniently also fixes LP: #1502476. LP: #1719322

   -- Daniel van Vugt   Thu, 25 Jan 2018
  05:42:51 +0800

  note: the same mp4 videos can be smoothly played with vlc without
  problem at all. The session is a gnome-shell one under xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 26 20:42:39 2018
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Desktop-packages] [Bug 1745866] Re: HDMI stays unplugged

[Daniel van Vugt]

Maybe bug 1707611?

** Summary changed:

- HDMI stays unplugged
+ Audio does not auto-switch to HDMI after switching the connected HDMI TV on

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert

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

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

[Desktop-packages] [Bug 1745866] Re: HDMI stays unplugged

[Daniel van Vugt]

Hi,

I vaguely recall other people have reported this kind of bug before but
can't find those other bugs. In the past it was an issue specific to the
type of TV. So can you please also provide:

1. The make and model of TV.
2. Run this command to give us even more info: apport-collect 1745866

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

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

Title:
  Audio does not auto-switch to HDMI after switching the connected HDMI
  TV on

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert

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

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

[Desktop-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI

[Daniel van Vugt]

** Summary changed:

- Audio doesn't auto switch when unplugging HDMI
+ Audio doesn't auto switch away from HDMI after unplugging HDMI

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

Title:
  Audio doesn't auto switch away from HDMI after unplugging HDMI

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  
  Steps to reproduce

  * Attach an external HDMI/DP monitor to watch videos on an external display 
(TV)
  * In sound settings, send audio to HDMI out, rather than internal laptop audio
  * Play a video, to show audio is going over HDMI
  * Unplug HDMI/DP cable
   - Video switches to internal panel only as expected.

  Expected behaviour

  * Audio switches to internal sound card

  Actual behaviour

  * Audio does not auto switch

  Workaround

  * Go to sound settings panel every time, and click the internal sound
  card

  Video showing it: https://www.youtube.com/watch?v=UR3LP0INMeI

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alan   1568 F pulseaudio
   /dev/snd/controlC1:  alan   1568 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 16 11:11:45 2017
  InstallationDate: Installed on 2017-08-02 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET56WW (1.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET56WW(1.21):bd01/27/2016:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BV001BUK
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1735156] Re: Chromium-browser crashes when launching

[Launchpad Bug Tracker]

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

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Chromium-browser crashes when launching

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  Chromium-browser -g  on armhf after installing new error reporting
  software today,

  Thread 1 "chromium-browse" received signal SIGSEGV, Segmentation fault.
  0x018abf3a in ?? ()
  (gdb) bt
  #0  0x018abf3a in  ()
  #1  0x024c92c4 in  ()
  #2  0x024c957e in  ()
  #3  0x024cfe9e in  ()
  #4  0x024f4520 in  ()
  #5  0x024f37c2 in  ()
  #6  0x02b9e76e in  ()
  #7  0x024ce5ee in  ()
  #8  0x02b501a2 in  ()
  #9  0x02a9aad4 in  ()
  #10 0x02a2b2da in  ()
  #11 0x02a42f56 in  ()
  #12 0x02a435f4 in  ()
  #13 0x02a42aea in  ()
  #14 0x02a426ec in  ()
  #15 0x02a40dec in  ()
  #16 0x02a40a64 in  ()
  #17 0x02a40420 in  ()
  #18 0x017e6e0c in  ()
  #19 0x017e63ba in  ()
  #20 0x00bd41c0 in  ()
  #21 0x00e1b06c in  ()
  #22 0x00bd2da6 in  ()
  ---Type  to continue, or q  to quit---
  #23 0x00bd5f76 in  ()
  #24 0x00bd1242 in  ()
  #25 0x016773f8 in  ()
  #26 0x0167cae8 in  ()
  #27 0x01676560 in  ()
  #28 0x0080f788 in ChromeMain ()
  #29 0xb6affaaa in __libc_start_main (main=
  0x80f731 <_start+272>, argc=2, argv=0xbefff004, init=, 
fini=0x430d2f1 <__libc_csu_fini>, rtld_fini=0xb6fe1bcd <_dl_fini>, 
stack_end=0xbefff004) at libc-start.c:308
  #30 0x0080f654 in _start ()

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

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

[Desktop-packages] [Bug 884336] Re: [Oneiric] HDMI output does not work immediately

[Daniel van Vugt]

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

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

Title:
  [Oneiric] HDMI output does not work immediately

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  In Oneiric, the output of 5.1 sound (not AC3 passthrough, but multi-
  channel PCM) via the HDMI connector of my onboard Intel graphics card
  is finally working. This is really great!

  For this to work, I have configured Pulseaudio to use the "Digital
  Surround 5.1 (HDMI) Output". The HDMI output of my computer is
  connected to a 5.1 receiver.

  However, there is one nuisance: Whenever I start playing sound on the
  computer (e.g., rhythmbox or VLC, both playing via PulseAudio), I hear
  no sound. On my receiver I have to re-select the input source for the
  computer, which seems to initiate a HDMI handshake (it lasts 3
  seconds). Only after this I am able to hear sound.

  If I press pause and continue in Rhythmbox, the sound continues fine.
  If I stop and restart Rhythmbox, I have to do the above procedure
  again. The same is true for VLC and probably for all other players.

  While playing around, I have noticed that sound is also working after
  killing pulseaudio while playing something in Rhythmbox. When the
  connection to Pulseaudio is killed, Rhythmbox tries a fallback to
  ALSA. As the Pulseaudio daemon was immediately restarted, this will
  result in Rhythmbox being connected via the ALSA plugin (before the
  connection was direct). It seems that Pulseaudio is doing the
  necessary things here, because after this I do hear sound (as long as
  Rhythmbox runs). However, this trick does not work for other players
  like VLC which don't fall back to ALSA.

  Note that while for me this is just a nuisance, it may be a real
  blocker for other users. As long as you don't try to fiddle with the
  receiver inputs while playing sound on the computer, you hear
  absolutely nothing via HDMI. This includes the sounds from the speaker
  test dialog of Pulseaudio. I guess a lot of users would give up and
  think that HDMI output is broken in Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: pulseaudio 1:1.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  philipp7706 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 50'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:10ec0892,80862002,00100302 
HDA:80862805,80862805,0010'
 Controls  : 31
 Simple ctrls  : 16
  Date: Mon Oct 31 18:07:22 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  ProcEnviron:
   LANGUAGE=de:en
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   LC_MESSAGES=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to oneiric on 2011-10-31 (0 days ago)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0076.2010.1115.1959
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67BL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10189-205
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0076.2010.1115.1959:bd11/15/2010:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-205:cvn:ct3:cvr:

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

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Does the fix also work for WD15? (see bug 1745765)

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Launchpad Bug Tracker]

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

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

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Launchpad Bug Tracker]

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

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

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1745765] Re: WD15 Dell Dock 2nd Audio Output not detected

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1718824, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1718824
   The analogue audio does not work on the Dell USB Dock

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

Title:
  WD15 Dell Dock 2nd Audio Output not detected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Dell WD15 Dock incorrectly only has access to the Headphones output of 
the Thunderbolt / USB3.1c Dock.
  Users of other distributions have created a workaround profile which works 
well on my machine (only the directories slightly differ.
  It would be great if the reason for this issue could be found and either be 
fixed by this patch or even better by mitigating the original issue.

  More details on the workaround can be found here
  https://github.com/edrose/dell-dock-audio-fix

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D1p:   benste 1696 F...m pulseaudio
   /dev/snd/controlC0:  benste 1696 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 19:57:23 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-13 (470 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-10-19 (99 days ago)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.3.1
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.3.1:bd10/03/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1745659] Re: gnome-shell crashed with signal 5

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1745612
   gnome-shell crashed with signal 5
** This bug has been marked a duplicate of bug 1720768
   gnome-shell crashed with SIGTRAP in object_instance_finalize from 
js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be 
unrooted: Gio.Subprocess\n"]

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I do not know what happened.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Jan 26 15:24:58 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (105 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:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  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/1745659/+subscriptions

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

[Desktop-packages] [Bug 1745612] Re: gnome-shell crashed with signal 5

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1720768, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1720768
   gnome-shell crashed with SIGTRAP in object_instance_finalize from 
js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be 
unrooted: Gio.Subprocess\n"]

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell crashed with signal 5

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-30.33-lowlatency 4.13.13
  Uname: Linux 4.13.0-30-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Jan 26 14:54:46 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-21 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/libgjs.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
   () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with signal 5
  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/1745612/+subscriptions

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

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

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1745612
   gnome-shell crashed with signal 5
** This bug has been marked a duplicate of bug 1720768
   gnome-shell crashed with SIGTRAP in object_instance_finalize from 
js::Class::doFinalize ["Finalizing proxy for an object that's scheduled to be 
unrooted: Gio.Subprocess\n"]

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Did nothing special. Used Chromium in full screen. Opened and closed
  my "Gnome shell extensions" and "Application menus" in the upper
  panel: Weather, System-monitor, Steam, Psensor, Drop Box, and "system
  menu"

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  Uname: Linux 4.15.0-041500rc7-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Jan 21 20:41:47 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-15 (133 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915)
  ProcCmdline: /usr/bin/gnome-shell
  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/1745716/+subscriptions

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

[Desktop-packages] [Bug 1745504] Re: [Asus X540LA] no sound in my laptop

[Daniel van Vugt]

Based on the above message "PulseAudio daemon running, or not running as
session daemon." I would expect you to not have sound.

1. Can you please check run this command and tell us the output?
  $ ps auxw | grep pulseaudio

2. Please also look in /var/crash and tell us if you see any crash files
relating to 'pulseaudio'.


** Summary changed:

- no sound in my laptop
+ [Asus X540LA] no sound in my laptop

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

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

Title:
  [Asus X540LA] no sound in my laptop

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  NO SOUND IS COMING OUT OF MY LAPTOP AT ALL
   i had installed mediawiki since then it happened and now i have uninstalled 
it but still sound has gone

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 05:01:52 2018
  InstallationDate: Installed on 2017-11-05 (81 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to artful on 2017-11-05 (81 days ago)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540LA.204:bd03/14/2016:svnASUSTeKCOMPUTERINC.:pnX540LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X540LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-26T04:24:06.264050

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

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

[Desktop-packages] [Bug 1745910] Re: /usr/bin/gnome-shell:11:g_type_check_instance_cast:st_label_get_text:append_actor_text:st_describe_actor:st_widget_get_theme_node

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1745516
   gnome-shell crashed with SIGSEGV in  g_type_check_instance_cast → 
st_label_get_text → append_actor_text → st_describe_actor → ffi_call_unix64 ()

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_cast:st_label_get_text:append_actor_text:st_describe_actor:st_widget_get_theme_node

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1745516] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast → st_label_get_text → append_actor_text → st_describe_actor → ffi_call_unix64 ()

[Daniel van Vugt]

Also tracking in:
https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2

** Description changed:

+ https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2
+ 
+ ---
+ 
  Hello,
  
  I searched in gnome-shell synaptic, and the monitor froze.
  
  Regards.
  --
  Cristian
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 20:13:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1512819693
  GsettingsChanges:
-  
+ 
  InstallationDate: Installed on 2017-10-13 (104 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/caravena
  SegvAnalysis:
-  Segfault happened at: 0x7fd3ca82ce0d :
movzbl 0x16(%rax),%edx
-  PC (0x7fd3ca82ce0d) ok
-  source "0x16(%rax)" (0xd1000816) not located in a known VMA region 
(needed readable region)!
-  destination "%edx" ok
+  Segfault happened at: 0x7fd3ca82ce0d :
movzbl 0x16(%rax),%edx
+  PC (0x7fd3ca82ce0d) ok
+  source "0x16(%rax)" (0xd1000816) not located in a known VMA region 
(needed readable region)!
+  destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  st_label_get_text () at /usr/lib/gnome-shell/libst-1.0.so
-  () at /usr/lib/gnome-shell/libst-1.0.so
-  st_describe_actor () at /usr/lib/gnome-shell/libst-1.0.so
-  ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
+  g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  st_label_get_text () at /usr/lib/gnome-shell/libst-1.0.so
+  () at /usr/lib/gnome-shell/libst-1.0.so
+  st_describe_actor () at /usr/lib/gnome-shell/libst-1.0.so
+  ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

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

Title:
  gnome-shell crashed with SIGSEGV in  g_type_check_instance_cast →
  st_label_get_text → append_actor_text → st_describe_actor →
  ffi_call_unix64 ()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2

  ---

  Hello,

  I searched in gnome-shell synaptic, and the monitor froze.

  Regards.
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
  Uname: Linux 4.13.0-30-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 25 20:13:35 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1512819693
  GsettingsChanges:

  InstallationDate: Installed on 2017-10-13 (104 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/caravena
  SegvAnalysis:
   Segfault happened at: 0x7fd3ca82ce0d :
movzbl 0x16(%rax),%edx
   PC (0x7fd3ca82ce0d) ok
   source "0x16(%rax)" (0xd1000816) not located in a known VMA region 
(needed readable region)!
   destination "%edx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_get_text () at /usr/lib/gnome-shell/libst-1.0.so
   () at /usr/lib/gnome-shell/libst-1.0.so
   st_describe_actor () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1745504] Re: [Asus X540LA] no sound in my laptop

[Daniel van Vugt]

Possibly also related is bug 1396640.

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

Title:
  [Asus X540LA] no sound in my laptop

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  NO SOUND IS COMING OUT OF MY LAPTOP AT ALL
   i had installed mediawiki since then it happened and now i have uninstalled 
it but still sound has gone

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 26 05:01:52 2018
  InstallationDate: Installed on 2017-11-05 (81 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to artful on 2017-11-05 (81 days ago)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540LA.204:bd03/14/2016:svnASUSTeKCOMPUTERINC.:pnX540LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X540LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2018-01-26T04:24:06.264050

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

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

[Desktop-packages] [Bug 1745910] [NEW] /usr/bin/gnome-shell:11:g_type_check_instance_cast:st_label_get_text:append_actor_text:st_describe_actor:st_widget_get_theme_node

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_cast:st_label_get_text:append_actor_text:st_describe_actor:st_widget_get_theme_node

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/af59d8248a84adcefb2be929a34d7b9bbfe831c2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1743710] Re: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

[Daniel van Vugt]

I can reproduce the bug in 16.04 using LibreOffice, same as your
screenshots show. But I can't seem to reproduce the bug in Firefox,
Thunderbird or GIMP that you mention. Can you provide screenshots of
those with the bug?

** Changed in: ubuntu-themes
   Status: New => Incomplete

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Incomplete

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

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

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

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

Title:
  Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

Status in Ubuntu theme:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Since 23018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in 
  https://ubuntuforums.org/showthread.php?t=2382505=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1743710/+subscriptions

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

[Desktop-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

[Daniel van Vugt]

Hi all,

If you would like to see fixes for issues like this in PulseAudio then
we suggest you talk to the PulseAudio people directly. You can do that
either by logging your own upstream bug or join the conversation here:
https://bugs.freedesktop.org/show_bug.cgi?id=88827

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Desktop-packages] [Bug 1745907] [NEW] Cannot copy/paste between some applications

[Nicolas_Raoul]

Public bug reported:

When copying simple text with CTRL-C CTRL-v (or menu or context menu)
between programs, I have noticed that some combinations work but other
do not (no text is pasted).

Gedit -> LibreOffice: No text pasted
LibreOffice -> Gedit: No text pasted

Firefox -> LibreOffice: OK
LibreOffice -> Firefox: Not text pasted

Geany -> Gedit: OK
Gedit -> Geany: Not text pasted

Geany -> LibreOffice: OK
LibreOffice -> Geany: No text pasted

Geany -> Firefox: OK
Firefox -> Geany: OK

OK means the copy/paste happened normally, with the text appearing normally 
when pasting.
In Firefox I used the text area I am using right now at bugs.launchpad.net.
In LibreOffice I used Calc's formula bar.

It was working fine before I upgraded to 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 29 12:18:14 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-03-21 (679 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to bionic on 2018-01-22 (6 days ago)

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


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

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

Title:
  Cannot copy/paste between some applications

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When copying simple text with CTRL-C CTRL-v (or menu or context menu)
  between programs, I have noticed that some combinations work but other
  do not (no text is pasted).

  Gedit -> LibreOffice: No text pasted
  LibreOffice -> Gedit: No text pasted

  Firefox -> LibreOffice: OK
  LibreOffice -> Firefox: Not text pasted

  Geany -> Gedit: OK
  Gedit -> Geany: Not text pasted

  Geany -> LibreOffice: OK
  LibreOffice -> Geany: No text pasted

  Geany -> Firefox: OK
  Firefox -> Geany: OK

  OK means the copy/paste happened normally, with the text appearing normally 
when pasting.
  In Firefox I used the text area I am using right now at bugs.launchpad.net.
  In LibreOffice I used Calc's formula bar.

  It was working fine before I upgraded to 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 12:18:14 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-21 (679 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-01-22 (6 days ago)

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

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

[Desktop-packages] [Bug 1745908] [NEW] [32493DC, Conexant CX20585, Speaker, Internal] No sound at all

[xiaoluotuo]

Public bug reported:

When loading the desktop, the volume icon on the right top of the
desktop was uncontrollably switched. And the link-sinks command tells
the speaker unavailable.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  chen   1857 F pulseaudio
  chen   3278 F alsamixer
CurrentDesktop: Unity
Date: Mon Jan 29 10:10:33 2018
InstallationDate: Installed on 2018-01-01 (27 days ago)
InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: 内置音频 - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  chen   1857 F pulseaudio
  chen   3278 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [32493DC, Conexant CX20585, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to xenial on 2018-01-28 (0 days ago)
dmi.bios.date: 09/15/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET53WW (1.23 )
dmi.board.name: 32493DC
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET53WW(1.23):bd09/15/2010:svnLENOVO:pn32493DC:pvrThinkPadX201:rvnLENOVO:rn32493DC:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 32493DC
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

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


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

** Description changed:

- When loading the desktop, the volume icon on the right up of the desktop
- was uncontrollably switched. And the link-sinks command tells the
- speaker unavailable.
+ When loading the desktop, the volume icon on the right top of the
+ desktop was uncontrollably switched. And the link-sinks command tells
+ the speaker unavailable.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  chen   1857 F pulseaudio
-   chen   3278 F alsamixer
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  chen   1857 F pulseaudio
+   chen   3278 F alsamixer
  CurrentDesktop: Unity
  Date: Mon Jan 29 10:10:33 2018
  InstallationDate: Installed on 2018-01-01 (27 days ago)
  InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: 内置音频 - HDA Intel MID
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  chen   1857 F pulseaudio
-   chen   3278 F alsamixer
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  chen   1857 F pulseaudio
+   chen   3278 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [32493DC, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to xenial on 2018-01-28 (0 days ago)
  dmi.bios.date: 09/15/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET53WW (1.23 )
  dmi.board.name: 32493DC
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET53WW(1.23):bd09/15/2010:svnLENOVO:pn32493DC:pvrThinkPadX201:rvnLENOVO:rn32493DC:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 32493DC
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

Title:
  [32493DC, Conexant CX20585, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When loading the desktop, the volume icon on the right top of the
  desktop was uncontrollably switched. And the link-sinks command tells
  the speaker unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 

[Desktop-packages] [Bug 1745904] Re: package transmission-daemon 2.92-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[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 transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1745904

Title:
  package transmission-daemon 2.92-2ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in transmission package in Ubuntu:
  New

Bug description:
  User@mjb:/$ sudo apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2
libmircore-dev libprotobuf-dev libxkbcommon-dev linux-headers-4.13.0-19
linux-headers-4.13.0-19-generic linux-image-4.13.0-19-generic
linux-image-extra-4.13.0-19-generic linux-signed-image-4.13.0-19-generic
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Setting up transmission-daemon (2.92-2ubuntu3.1) ...
  Job for transmission-daemon.service failed because the control process exited 
with error code.
  See "systemctl  status transmission-daemon.service" and "journalctl  -xe" for 
details.
  invoke-rc.d: initscript transmission-daemon, action "start" failed.
  ● transmission-daemon.service - Transmission BitTorrent Daemon
 Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Sun 2018-01-28 21:21:24 CST; 6ms 
ago
Process: 17620 ExecStart=/usr/bin/transmission-daemon -f --log-error 
(code=exited, status=1/FAILURE)
   Main PID: 17620 (code=exited, status=1/FAILURE)

  Jan 28 21:21:24 mjb systemd[1]: Starting Transmission BitTorrent Daemon...
  Jan 28 21:21:24 mjb transmission-daemon[17620]: [2018-01-28 21:21:24.932] 
JSON parse failed in 
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json at pos 
461: ESCAPE_INVALID -- remaining text " Book/",
  Jan 28 21:21:24 mjb transmission-daemon[17620]: "do"
  Jan 28 21:21:24 mjb transmission-daemon[17620]: [2018-01-28 21:21:24.932] 
transmission-daemon Error loading config file -- exiting. (daemon.c:693)
  Jan 28 21:21:24 mjb systemd[1]: transmission-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Jan 28 21:21:24 mjb systemd[1]: Failed to start Transmission BitTorrent 
Daemon.
  Jan 28 21:21:24 mjb systemd[1]: transmission-daemon.service: Unit entered 
failed state.
  Jan 28 21:21:24 mjb systemd[1]: transmission-daemon.service: Failed with 
result 'exit-code'.
  dpkg: error processing package transmission-daemon (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   transmission-daemon
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: transmission-daemon 2.92-2ubuntu3.1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Jan 28 21:15:53 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-26 (94 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, unpackaged
  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: transmission
  Title: package transmission-daemon 2.92-2ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.transmission-daemon.settings.json: [modified]
  mtime.conffile..etc.transmission-daemon.settings.json: 
2017-12-21T12:55:36.045583

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

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

[Desktop-packages] [Bug 1724921] Re: VLANs get incorrectly listed under Bluetooth

[Kai-Heng Feng]

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

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

Title:
  VLANs get incorrectly listed under Bluetooth

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

Bug description:
  I expected them to show up under Wired because the VLANs' associated
  adapter is wired.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager-gnome 1.8.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 11:25:17 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.50.253 dev vlan757 proto static metric 400 
   169.254.0.0/16 dev vlan757 scope link metric 1000 
   192.168.50.0/24 dev vlan757 proto kernel scope link src 192.168.50.222 
metric 400
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH SLAVE 
   VLAN Camera 1a430a37-b4b3-461c-87bd-d60b547dd369  vlan
1508437383  Thu 19 Oct 2017 11:23:03 AM PDT  yes  0 
no/org/freedesktop/NetworkManager/Settings/4  yes vlan757  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8  --
   Wired connection 1  23ca82a4-d9c5-3d59-ac84-56db17873201  802-3-ethernet  
1508433170  Thu 19 Oct 2017 10:12:50 AM PDT  no   4294966297
no/org/freedesktop/NetworkManager/Settings/1  no  --   --   
  --  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1745904] [NEW] package transmission-daemon 2.92-2ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Josiah Brown]

Public bug reported:

User@mjb:/$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2
  libmircore-dev libprotobuf-dev libxkbcommon-dev linux-headers-4.13.0-19
  linux-headers-4.13.0-19-generic linux-image-4.13.0-19-generic
  linux-image-extra-4.13.0-19-generic linux-signed-image-4.13.0-19-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up transmission-daemon (2.92-2ubuntu3.1) ...
Job for transmission-daemon.service failed because the control process exited 
with error code.
See "systemctl  status transmission-daemon.service" and "journalctl  -xe" for 
details.
invoke-rc.d: initscript transmission-daemon, action "start" failed.
● transmission-daemon.service - Transmission BitTorrent Daemon
   Loaded: loaded (/lib/systemd/system/transmission-daemon.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-01-28 21:21:24 CST; 6ms ago
  Process: 17620 ExecStart=/usr/bin/transmission-daemon -f --log-error 
(code=exited, status=1/FAILURE)
 Main PID: 17620 (code=exited, status=1/FAILURE)

Jan 28 21:21:24 mjb systemd[1]: Starting Transmission BitTorrent Daemon...
Jan 28 21:21:24 mjb transmission-daemon[17620]: [2018-01-28 21:21:24.932] JSON 
parse failed in 
/var/lib/transmission-daemon/.config/transmission-daemon/settings.json at pos 
461: ESCAPE_INVALID -- remaining text " Book/",
Jan 28 21:21:24 mjb transmission-daemon[17620]: "do"
Jan 28 21:21:24 mjb transmission-daemon[17620]: [2018-01-28 21:21:24.932] 
transmission-daemon Error loading config file -- exiting. (daemon.c:693)
Jan 28 21:21:24 mjb systemd[1]: transmission-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
Jan 28 21:21:24 mjb systemd[1]: Failed to start Transmission BitTorrent Daemon.
Jan 28 21:21:24 mjb systemd[1]: transmission-daemon.service: Unit entered 
failed state.
Jan 28 21:21:24 mjb systemd[1]: transmission-daemon.service: Failed with result 
'exit-code'.
dpkg: error processing package transmission-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 transmission-daemon
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: transmission-daemon 2.92-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sun Jan 28 21:15:53 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-10-26 (94 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, unpackaged
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: transmission
Title: package transmission-daemon 2.92-2ubuntu3.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.transmission-daemon.settings.json: [modified]
mtime.conffile..etc.transmission-daemon.settings.json: 
2017-12-21T12:55:36.045583

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

Title:
  package transmission-daemon 2.92-2ubuntu3.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in transmission package in Ubuntu:
  New

Bug description:
  User@mjb:/$ sudo apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
libmirclient-dev libmircommon-dev libmircookie-dev libmircookie2
libmircore-dev libprotobuf-dev libxkbcommon-dev linux-headers-4.13.0-19
linux-headers-4.13.0-19-generic linux-image-4.13.0-19-generic
linux-image-extra-4.13.0-19-generic linux-signed-image-4.13.0-19-generic
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you 

[Desktop-packages] [Bug 1705434] Re: akonadi_control crashed with SIGABRT in __GI_raise()

[Pierre Abbat]

I get Akonadi crashing several times a day on a new laptop running
Artful. My previous laptop, running Xenial, did not do this. I'm not
sure that it's crashing with the same signal, as I don't know how to
start Akonadi with this process being debugged. I tried attaching the
debugger to the process, but the process simply exited without gdb being
able to get a stack trace. The tail of strace looks as follows:

ppoll([{fd=-1}, {fd=-1}, {fd=-1}, {fd=116, events=POLLIN}], 4, {tv_sec=1, 
tv_nsec=0}, NULL, 8) = 1 ([{fd=116, revents=POLLIN|POLLHUP}], left {tv_sec=0, 
tv_nsec=98794})
read(116, 
"\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\251\6\7\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 152) = 
152
close(116)  = 0
close(104)  = 0
write(8, "Application '/usr/bin/akonadi_no"..., 61) = 61
write(2, "org.kde.pim.akonadicontrol: Appl"..., 90) = 90
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d85b03200, FUTEX_WAKE_PRIVATE, 1) = 1
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d64025820, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x7f9d640257d0, FUTEX_WAKE_PRIVATE, 1) = 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d85b03278, FUTEX_WAKE_PRIVATE, 1) = 1
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d64025820, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource 
temporarily unavailable)
futex(0x7f9d640257d0, FUTEX_WAKE_PRIVATE, 1) = 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d6403f4e0, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x7f9d6403f490, FUTEX_WAKE_PRIVATE, 1) = 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d85b03490, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f9d6402a540, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource 
temporarily unavailable)
futex(0x7f9d6402a4f0, FUTEX_WAKE_PRIVATE, 1) = 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d85b03298, FUTEX_WAKE_PRIVATE, 1) = 1
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x55f61fec9d30, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource 
temporarily unavailable)
futex(0x55f61fec9ce0, FUTEX_WAKE_PRIVATE, 1) = 0
write(7, "\1\v\1\0\1\0\0\0\0\0\0\0\0\0\0\0", 16) = 16
close(7)= 0
open("/sys/devices/system/cpu/online", O_RDONLY|O_CLOEXEC) = 7
read(7, "0-7\n", 8192)  = 4
close(7)= 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d6400b0b0, FUTEX_WAIT_PRIVATE, 0, NULL) = -1 EAGAIN (Resource 
temporarily unavailable)
futex(0x7f9d6400b060, FUTEX_WAKE_PRIVATE, 1) = 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d6400b0b0, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x7f9d6400b060, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, 
[{iov_base="\1\0\10\0\4\0\0\0075\1\0\0\0\0\0\0\1\0\1\0\0\0\2\0!\0\0\0\0\0\0\0"...,
 iov_len=84}], 1) = 84
futex(0x55f61fe24010, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x55f61fe23fc0, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, 
revents=POLLIN|POLLOUT}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\34\0\226\0015\1\0\0E\1\0\0*J\334\16\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 32
writev(3, [{iov_base=".\0\2\0\2\0\0\7", iov_len=8}], 1) = 8
poll([{fd=3, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=3, revents=POLLOUT}])
writev(3, [{iov_base="<0\2\0\0\0\0\7+\1\1\0", iov_len=12}, {iov_base=NULL, 
iov_len=0}, {iov_base="", iov_len=0}], 3) = 12
poll([{fd=3, events=POLLIN}], 1, -1)= 1 ([{fd=3, revents=POLLIN}])
recvmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\1\1\231\1\0\0\0\0\6\0`\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 64
shutdown(3, SHUT_RDWR)  = 0
close(3)= 0
inotify_rm_watch(6, 1)  = 0
close(6)= 0
msync(0x7f9d6aca4000, 10547304, MS_ASYNC|MS_INVALIDATE) = 0
munmap(0x7f9d6aca4000, 10547304)= 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f9d6400b0b0, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x7f9d6400b060, FUTEX_WAKE_PRIVATE, 1) = 0
write(9, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x55f61fe61370, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x55f61fe7e140, FUTEX_WAIT_PRIVATE, 0, NULL) = 0
futex(0x55f61fe7e0f0, FUTEX_WAKE_PRIVATE, 1) = 0
close(8)= 0
futex(0x7f9d84e18c20, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f9d84e18c20, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x7f9d84e18c20, FUTEX_WAKE_PRIVATE, 1) = 0
exit_group(255) = ?
+++ exited with 255 +++

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

Title:
  akonadi_control crashed with SIGABRT in 

[Desktop-packages] [Bug 1730460] Re: Framerate drops when moving windows across physical displays

[Daniel van Vugt]

Alright then, let's consider
https://gitlab.gnome.org/GNOME/mutter/issues/3 as the upstream bug here.
Unfortunately we can't link to gitlab bugs properly from Launchpad yet.

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Low => Medium

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

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

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

** Summary changed:

- Framerate drops when moving windows across physical displays
+ Very poor multi-monitor performance in Wayland sessions

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

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

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => In Progress

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

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

Title:
  Very poor multi-monitor performance in Wayland sessions

Status in gnome-shell package in Ubuntu:
  In Progress
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  When dragging a window between displays, I can see cpu usage increase
  while framerate drops dramatically to single numbers.

  Desktop scaling is 1.0, one is a WXGA screen and another FHD.

  Ubuntu session (wayland), 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Mon Nov  6 17:09:20 2017
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' 
b"['/home/development/bin/firefox.desktop', 'org.gnome.Nautilus.desktop', 
'jetbrains-phpstorm.desktop', 'code.desktop', 'postman.desktop', 
'standard_notes.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'icon-theme' b"'ePapirus'"
   b'org.gnome.desktop.interface' b'gtk-theme' b"'DarkNumix'"
  InstallationDate: Installed on 2016-03-13 (603 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-10-19 (17 days ago)

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

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

[Desktop-packages] [Bug 799486] Re: [P52F, Conexant CX20585, Speaker, Internal] No sound at all

[xiaoluotuo]

** Description changed:

  No sound detected in my laptop.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
-   List of CAPTURE Hardware Devices 
-  card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
-Subdevices: 1/1
-Subdevice #0: subdevice #0
+   List of CAPTURE Hardware Devices 
+  card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
+    Subdevices: 1/1
+    Subdevice #0: subdevice #0
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  kapil  1401 F pulseaudio
-   kapil  2325 F TeamViewer.exe
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kapil  1401 F pulseaudio
+   kapil  2325 F TeamViewer.exe
  Card0.Amixer.info:
-  Card hw:0 'Intel'/'HDA Intel at 0xd540 irq 42'
-Mixer name : 'Intel IbexPeak HDMI'
-Components : 'HDA:14f15069,104311f3,00100302 
HDA:80862804,80860101,0010'
-Controls  : 14
-Simple ctrls  : 11
+  Card hw:0 'Intel'/'HDA Intel at 0xd540 irq 42'
+    Mixer name : 'Intel IbexPeak HDMI'
+    Components : 'HDA:14f15069,104311f3,00100302 
HDA:80862804,80860101,0010'
+    Controls  : 14
+    Simple ctrls  : 11
  Date: Sun Jun 19 22:52:57 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  LANG=en_IN
-  LC_MESSAGES=en_IN.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  LANG=en_IN
+  LC_MESSAGES=en_IN.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_DevicesInUse: 1401  2325 kapil F 
TeamViewer.exe
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P52F, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to natty on 2011-06-03 (15 days ago)
  dmi.bios.date: 12/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P52F.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P52F
  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.:bvrP52F.204:bd12/10/2010:svnASUSTeKComputerInc.:pnP52F:pvr1.0:rvnASUSTeKComputerInc.:rnP52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: P52F
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

Title:
  [P52F, Conexant CX20585, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound detected in my laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: alsa-base 1.0.24+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kapil  1401 F pulseaudio
    kapil  2325 F TeamViewer.exe
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd540 irq 42'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:14f15069,104311f3,00100302 
HDA:80862804,80860101,0010'
     Controls  : 14
     Simple ctrls  : 11
  Date: Sun Jun 19 22:52:57 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   LANG=en_IN
   LC_MESSAGES=en_IN.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_DevicesInUse: 1401  2325 kapil F 
TeamViewer.exe
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [P52F, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to natty on 2011-06-03 (15 days ago)
  dmi.bios.date: 12/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P52F.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 

[Desktop-packages] [Bug 1723705] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_value_set_object() from object_get_property()

[Daniel van Vugt]

This issue is also being tracked in:
https://errors.ubuntu.com/problem/b3f30475bb4ce680bdb8c55709a9edecaf67adb2

** Description changed:

+ https://errors.ubuntu.com/problem/b3f30475bb4ce680bdb8c55709a9edecaf67adb2
+ 
+ ---
+ 
  Occurred when clicking on Thunderbird via Dash to Dock. GNOME Shell hung
  straight after clicking on Thunderbird.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Oct 15 07:23:08 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-10-25 (354 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  LANGUAGE=en_ZA:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_ZA.UTF-8
-  SHELL=/usr/bin/zsh
+  LANGUAGE=en_ZA:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_ZA.UTF-8
+  SHELL=/usr/bin/zsh
  SegvAnalysis:
-  Segfault happened at: 0x7fa17da06cdf 
:  mov(%rdx),%rdx
-  PC (0x7fa17da06cdf) ok
-  source "(%rdx)" (0x0550) not located in a known VMA region (needed 
readable region)!
-  destination "%rdx" ok
+  Segfault happened at: 0x7fa17da06cdf 
:  mov(%rdx),%rdx
+  PC (0x7fa17da06cdf) ok
+  source "(%rdx)" (0x0550) not located in a known VMA region (needed 
readable region)!
+  destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
-  g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_value_set_object () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  g_object_get_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
-  ?? () from /usr/lib/libgjs.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
+  g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_value_set_object () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  g_object_get_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
+  ?? () from /usr/lib/libgjs.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a() from g_value_set_object()
  from object_get_property()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b3f30475bb4ce680bdb8c55709a9edecaf67adb2

  ---

  Occurred when clicking on Thunderbird via Dash to Dock. GNOME Shell
  hung straight after clicking on Thunderbird.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
  Uname: Linux 4.13.0-15-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Oct 15 07:23:08 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-10-25 (354 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/usr/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x7fa17da06cdf 
:  mov(%rdx),%rdx
   PC (0x7fa17da06cdf) ok
   source "(%rdx)" (0x0550) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_value_set_object () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_get_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
  Title: gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo vboxusers

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1736300] Re: /usr/bin/gnome-shell:11:g_type_check_instance_is_fundamentally_a:g_value_set_object:object_get_property:g_object_get_property:get_prop_from_g_param

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1714989
   gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
st_label_set_text() from ffi_call_unix64()

** This bug has been marked a duplicate of bug 1723705
   gnome-shell crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a() from g_value_set_object() from 
object_get_property()

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

Title:
  /usr/bin/gnome-
  
shell:11:g_type_check_instance_is_fundamentally_a:g_value_set_object:object_get_property:g_object_get_property:get_prop_from_g_param

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.2-0ubuntu0.1, the problem page at 
https://errors.ubuntu.com/problem/b3f30475bb4ce680bdb8c55709a9edecaf67adb2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

[Daniel van Vugt]

This bug does not say Fix Released any more. It is open ("Triaged").

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

Title:
  In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in
  launcher when opened

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

Bug description:
  Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with
  the application's icons. The individual icons show up in the list of
  programs, and can be docked in the launcher - but a generic white
  libreoffice icon also shows up in the program list, and if any of the
  docked, correct, icons are clicked, a new, white icon appears that is
  generic across all libreoffice windows (e.g. if I have open writer and
  calc, the white icon gets two red dots and to access either the writer
  or calc window I have to click on the generic icon). This is annoying
  but not crippling, and not solved by a purge and reinstall.

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

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

[Desktop-packages] [Bug 1734890] Re: pulse audio does not load because "module-switch-on-connect" should be loaded once at most

[Launchpad Bug Tracker]

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

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

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

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

Title:
  pulse audio does not load because "module-switch-on-connect" should be
  loaded once at most

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  This laptop was initially loaded with kubuntu 17.04. Yesterday I used
  do-release-upgrade to update to 17.10.

  This morning I noticed that the pulse audio mixer was broken while
  chrome and amarok could still play sound.  Cold booted just in case.

  Still no pulse mixing.  But alsamixer was working.  Found that no
  pulse processes are running.

  
$ ps auxww | grep pulse
niclangf  9666  0.0  0.0  15900  1180 pts/3S+   15:13   0:00 grep 
--color=auto pulse
$ pulseaudio 
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most. 
Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.
$ ps auxww | grep pulse
niclangf  9833  0.0  0.0  15900  1036 pts/3S+   15:16   0:00 grep 
--color=auto pulse

  Removed .config/pulse and .gconf/system/pulseaudio

$ pulseaudio 
W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.config/pulse/cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to open cookie file 
'/home/niclangf/.pulse-cookie': No such file or directory
W: [pulseaudio] authkey.c: Failed to load authentication key 
'/home/niclangf/.pulse-cookie': No such file or directory
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most. Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.

$ pulseaudio 
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be 
loaded once at most.  Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.

  Nicolai

  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
  CurrentDesktop: KDE
  Date: Tue Nov 28 15:11:06 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-07-18 (133 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-11-27 (1 days ago)
  dmi.bios.date: 12/27/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET25W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HGS1C200
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET25W(1.04):bd12/27/2016:svnLENOVO:pn20HGS1C200:pvrThinkPadT470s:rvnLENOVO:rn20HGS1C200:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HGS1C200
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1721359] Re: Simple Scan translations are not synced with upstream

[AsciiWolf]

It looks like the issue has been fixed.

** Changed in: simple-scan (Ubuntu)
   Status: New => Fix Released

** Changed in: ubuntu-translations
   Status: New => Fix Released

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

Title:
  Simple Scan translations are not synced with upstream

Status in Ubuntu Translations:
  Fix Released
Status in simple-scan package in Ubuntu:
  Fix Released

Bug description:
  Czech and probably many other translations are incomplete even though
  they are translated in upstream.

  For example the Czech one:
  Launchpad - 
https://translations.launchpad.net/ubuntu/artful/+source/simple-scan/+pots/simple-scan/cs/+details
 (last update: January 2016; 62 strings untranslated)
  Upstream - https://github.com/GNOME/simple-scan/blob/master/po/cs.po (last 
update: two months ago; fully translated)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1721359/+subscriptions

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

[Desktop-packages] [Bug 1705434] Re: akonadi_control crashed with SIGABRT in __GI_raise()

[Launchpad Bug Tracker]

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

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

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

Title:
  akonadi_control crashed with SIGABRT in __GI_raise()

Status in akonadi package in Ubuntu:
  Confirmed

Bug description:
  This happens when I log in after a reboot.
  Note that this is not the first time, I needed to know that this behavior was 
not a one-time thing. It happens, however, every time I log in.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: akonadi-server 4:16.12.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Wed Jul 19 02:27:04 2017
  ExecutablePath: /usr/bin/akonadi_control
  InstallationDate: Installed on 2016-12-17 (215 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  ProcCmdline: /usr/bin/akonadi_control
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: akonadi
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
   __GI_abort () at abort.c:89
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? ()
   ?? ()
  Title: akonadi_control crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to artful on 2017-07-02 (18 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1371613] Re: Backup result message nonsense when some folders failed AND a verification test was done

[Vej]

** Tags added: artful

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

Title:
  Backup result message nonsense when some folders failed AND a
  verification test was done

Status in deja-dup package in Ubuntu:
  New

Bug description:
  There are two bugs here; I'm describing the second, layered on the
  first:

  The first is that even though I have explicitly listed ~/.cache in the
  folders to ignore, I get a complaint that it failed to back up
  something in .cache.

  the second bug is that when it does a password/restore verification
  test (which it does every two months), I end up with a completion
  message that makes no sense: it tells me that the test succeeded, but
  then lists a couple of files, suggesting maybe that they were the only
  ones which were backed up? Or the only ones for which the restore test
  was successful?

  See attached graphics.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 19 09:45:48 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-21 (29 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745874] Re: Contradictory and unclear completion report: "Not all files could be backed up" "Your files were successfully backed up"

[Vej]

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

Hello!

You already filed a bug about this. So I am marking this as a duplicate.

** This bug has been marked a duplicate of bug 1371613
   Backup result message nonsense when some folders failed AND a verification 
test was done

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

Title:
  Contradictory and unclear completion report: "Not all files could be
  backed up" "Your files were successfully backed up"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When Deja Dup finished, it sent a message to my OS saying that the
  backup was finished but that not all files could be backed up.  I
  clicked on the message to get more information, and it simply
  disappeared.

  I found the dialog window from deja dup and it says:

  Backup Finished

  Your files were successfully backed up and tested.

  With no more comment, it then listed two files (full paths).
  Presumably these are files that were not backed up, yet the window
  says nothing about that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:13:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (71 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745882] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'a

[chezleon]

Public bug reported:

Crash at the opening of Ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Sun Jan 28 22:38:22 2018
ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
InstallationDate: Installed on 2018-01-28 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet 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/1745882

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: tentative de remplacement de «
  /lib/udev/hwdb.d/20-sane.hwdb », qui est différent d'autres instances
  du paquet libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Crash at the opening of Ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu2.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sun Jan 28 22:38:22 2018
  ErrorMessage: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb », 
qui est différent d'autres instances du paquet libsane1:i386
  InstallationDate: Installed on 2018-01-28 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Aucun fichier ou dossier de ce type: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: tentative de remplacement de « /lib/udev/hwdb.d/20-sane.hwdb 
», qui est différent d'autres instances du paquet 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/1745882/+subscriptions

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

[Desktop-packages] [Bug 1710931] Re: Ctrl+N shortcut does not work when desktop has focus

[scruss]

NB: this will never be fixed, as gnome doesn't think users should have
files on the desktop. Witness the sort desktop icons bugs filed in 2003
which sat unresolved for 15 years before being quietly expired upstream.

“People keep asking for it, but there's no demand.”

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

Title:
  Ctrl+N shortcut does not work when desktop has focus

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

Bug description:
  When a Nautilus window is open, Ctrl+N opens a new window that shows
  the same folder as the focused Nautilus window.

  However, when the desktop is focused, the shortcut doesn't work -
  instead I see an error that x-nautilus-desktop:// is not supported.

  This functionality was previously reported as working in #307229.

  This is on Ubuntu 17.10 Artful Aardvark (fully patched as of today)
  with GNOME Files 3.24.2.1.

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

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

[Desktop-packages] [Bug 1745874] [NEW] Contradictory and unclear completion report: "Not all files could be backed up" "Your files were successfully backed up"

[Christopher Barrington-Leigh]

Public bug reported:

When Deja Dup finished, it sent a message to my OS saying that the
backup was finished but that not all files could be backed up.  I
clicked on the message to get more information, and it simply
disappeared.

I found the dialog window from deja dup and it says:
  
Backup Finished

Your files were successfully backed up and tested.

With no more comment, it then listed two files (full paths).
Presumably these are files that were not backed up, yet the window says
nothing about that.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: deja-dup 36.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 28 09:13:52 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-18 (71 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: deja-dup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: deja-dup (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "deja-dup-bizarre-message.png"
   
https://bugs.launchpad.net/bugs/1745874/+attachment/5044669/+files/deja-dup-bizarre-message.png

** Summary changed:

- Contradictory and unclear completion report
+ Contradictory and unclear completion report: "Not all files could be backed 
up" "Your files were successfully backed up"

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

Title:
  Contradictory and unclear completion report: "Not all files could be
  backed up" "Your files were successfully backed up"

Status in deja-dup package in Ubuntu:
  New

Bug description:
  When Deja Dup finished, it sent a message to my OS saying that the
  backup was finished but that not all files could be backed up.  I
  clicked on the message to get more information, and it simply
  disappeared.

  I found the dialog window from deja dup and it says:

  Backup Finished

  Your files were successfully backed up and tested.

  With no more comment, it then listed two files (full paths).
  Presumably these are files that were not backed up, yet the window
  says nothing about that.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: deja-dup 36.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 09:13:52 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (71 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather

[Gunnar Hjalmarsson]

On 2017-12-11 14:58, Gunnar Hjalmarsson wrote:> Discussed the proposal in 
comment #21 with Sebastien Bacher, and
> changed the template name and translation domain to "libgweather-3.0"
> in LP for bionic.
With version 1:18.04+20180118 of language-pack-gnome-*-base and version 
3.26.1-2 of libgweather-common this has now been fixed the correct way in 
bionic.

** Changed in: ubuntu-translations
   Status: In Progress => Fix Released

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

Title:
  French language locale missing : Gnome-Weather

Status in GNOME Weather:
  Unknown
Status in Ubuntu Translations:
  Fix Released
Status in gnome-weather package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Xenial:
  Fix Released
Status in libgweather source package in Zesty:
  Fix Released
Status in libgweather source package in Artful:
  Fix Released

Bug description:
  [Impact]

  The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building
  libgweather, which makes the libgweather-common binary look for
  translations in files named "libgweather-3.0.mo". The template name in
  Rosetta (LP) is "libgweather", so the files provided by the language
  packs are named "libgweather.mo". This mismatch results in the
  messages describing the weather type always be displayed in English.

  The uploaded package works around the issue by setting GETTEXT_PACKAGE
  to "libgweather".

  In bionic the template name in Rosetta has been changed to
  "libgweather-3.0", and thus the workaround will be reversed.

  [Test Case]

   * Install French language support

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is displayed in
     English.

   * Install these packages from -proposed:
     - gir1.2-gweather-3.0
     - libgweather-3-6
     - libgweather-common

   * Start gnome-weather with:
     LANGUAGE=fr gnome-weather
     and find that the description of the weather type is now displayed
     in French.

  [Regression Potential]

  None.

  [Original description]

  In Gnome Weather, part of it is not translated in french : cloudy,
  rain showers, etc. Should be : nuageux, pluie fine, etc.

  I guess it's a missing french localization. Fedora does not have that
  problem. In Gnome-Software, they have a section for languages, under
  the extensions section.

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

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

[Desktop-packages] [Bug 1745866] [NEW] HDMI stays unplugged

[Norbert]

Public bug reported:

When I start the computer is the connected TV (HDMI) is off and the
pulseaudio device stays on unplugged when I switch the TV on. If I
switch the TV on before I start the computer, everything works fine.

alsa_output.pci-_01_00.1.hdmi-stereo

linux-image-14.0-15-generic

nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic


Regards,

Norbert

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

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

Title:
  HDMI stays unplugged

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I start the computer is the connected TV (HDMI) is off and the
  pulseaudio device stays on unplugged when I switch the TV on. If I
  switch the TV on before I start the computer, everything works fine.

  alsa_output.pci-_01_00.1.hdmi-stereo

  linux-image-14.0-15-generic

  nvidia-graphics-drivers-384 (384.111-0ubuntu1) bionic

  
  Regards,

  Norbert

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

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

[Desktop-packages] [Bug 1745858] Re: chromium-browser crashed with SIGILL

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** 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 chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1745858

Title:
  chromium-browser crashed with SIGILL

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Just opening a new tab

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 63.0.3239.108-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  DRM.card0-DP-1:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-VGA-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEcpQCiFpAFCwVAQNoLBl4ruyFolRNoScSUFS/7oBxT4HAgQABAQEBAQEBAQEBMCpAyGCEZDAYUBMAuvkQAAAe/QA4TB9QDgAKICAgICAg/ABTMjAwSEwKICAgICAg/wBMVUcwUjAyNjI0MDAKALM=
   modes: 1600x900 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 
832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  Date: Sun Jan 28 13:34:31 2018
  Desktop-Session:
   'ubuntu'
   'None'
   'None'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2017-01-06 (387 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InstalledPlugins:
   /usr/lib/mozilla/plugins:
 => libgnome-shell-browser-plugin.so
   (size: 18856 bytes, mtime: Sat Dec  9 06:41:33 2017)
  Load-Avg-1min: 3.20
  Load-Processes-Running-Percent:   0.4%
  MachineType: Hewlett-Packard HP Compaq 6005 Pro SFF PC
  ProcCmdline: /usr/lib/chromium-browser/chromium-browser\ --type=gpu-process\ 
--field-trial-handle=11131593833462370751,792246450241099432,131072\ 
--use-gl=swiftshader-webgl\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x1002\ --gpu-device-id=0x9710\ --gpu-driver-vendor=Google\ 
Inc.\ --gpu-driver-version=3.3.0.2\ --gpu-driver-date=2017/04/07\ 
--service-request-channel-token=8B4555D21A1DB765D12647E809DE
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=62e7b944-3562-4edd-a369-5a1d63e44e07 ro quiet splash vt.handoff=7
  Signal: 4
  SourcePackage: chromium-browser
  StacktraceTop:
   () at /usr/lib/chromium-browser/swiftshader/libGLESv2.so
   call_init (l=, argc=argc@entry=11, 
argv=argv@entry=0x7ffc95d38318, env=env@entry=0x7ffc95d38378) at dl-init.c:72
   call_init (env=0x7ffc95d38378, argv=0x7ffc95d38318, argc=11, l=) at dl-init.c:30
   _dl_init (main_map=main_map@entry=0x555b1e1419a0, argc=11, 
argv=0x7ffc95d38318, env=0x7ffc95d38378) at dl-init.c:120
   dl_open_worker (a=a@entry=0x7ffc95d370f0) at dl-open.c:575
  Title: chromium-browser crashed with SIGILL
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 04/18/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.17
  dmi.board.asset.tag: 2UA0160N15
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA0160N15
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Rémi Denis-Courmont]

(And the following Xine error relates to XVideo, and probably is a
totally different and Xine-specific bug.)

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Rémi Denis-Courmont]

The error message is totally normal and expected if there is no driver.

It's a bit confusing because libvdpau defaults to the NVIDIA driver,
regardless of the GPU vendor or lack thereof. But either way, there are
no ways that libvdpau can work without a backend driver.

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1456016] Re: Xorg nouveau graphics driver freezes or crashes

[Christopher M. Penalver]

Diogo Gomes, it will help immensely if you use the computer the problem is 
reproducible with, file a new report with Ubuntu by first ensuring the package 
xdiagnose is installed, click the Yes button for attaching additional debugging 
information after running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Xorg nouveau graphics driver freezes or crashes

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

Bug description:
  I'm not saying xorg is the culprit, I think problem is graphics related thus 
it happens when I choose Nouveau graphics driver instead of proprietary Nvidia.
  My GPU is an integrated one and uses shared RAM, this bug is more frequent 
when hardware settings are "AUTODETECT FRAME BUFFER SIZE=enabled" otherwise 
when it's set to "FIXED=256MB" it isn't that frequent.
  The steps to reproduce this bug are not pretty clear, this crash happens at 
least once a day, appearently when there's too much memory in use.
  I used to use "Nvidia proprietary driver" with Ubuntu 14.10 with less 
problems but some crashes correctly managed by system without closing any 
application but with Ubuntu 15.04 this crashes make all applications get 
closed, that's why I decided to change to Nouveau but it gets so slow. I'm 
really considering rollback to Ubuntu 14.10 which caused less problems.
  When Systems freezes both keyboard and mouse get irresponsive too. I've 
collected some data through SSH which are attached:
   "Xorg.0.freezetime.log" is "/var/log/Xorg.0.log" at Freeze moment.
   "kikedmesg.txt" is "dmsg.txt" at Freeze moment.
  Please contact me with directions to help in solving this issue.
  Some Info:
  1)Ubuntu 15.04 64 bits
  2)xserver-xorg-video-nouveau version 1:1.0.11-1ubuntu2build1

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun May 17 20:08:57 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053b] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:82b3]
  InstallationDate: Installed on 2015-05-02 (15 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=UUID=73fab811-79d9-488b-9316-7e0df86fbc90 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xserver-xorg-video-nouveau
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0709
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-VM HDMI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0709:bd12/05/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-VMHDMI:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: 

[Desktop-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll

[Christopher M. Penalver]

Reuben Lifshay, this problem should be reported upstream. Could you please post 
this to:
https://bugs.freedesktop.org/enter_bug.cgi?product=xorg
Component: Input/libinput
Version: 7.7

Please post a URL of the report here when finished.

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

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

Title:
  Razer Naga Chroma wheel tilt being remapped to vertical scroll

Status in xorg package in Ubuntu:
  Triaged

Bug description:
  My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7)
  are being remapped to scroll up and down (buttons 4, and 5) as per
  xev.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems

   Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec  7 14:25:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1303]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 5986: Acer, Inc
   Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76 Galago Pro
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash 
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04nRSA
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago Pro
  dmi.board.vendor: System76
  dmi.board.version: galp2
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Galago Pro
  dmi.product.version: galp2
  dmi.sys.vendor: System76
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.80-1~xenial
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Dec  7 14:21:19 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Marco]

A correction to #34

$ vdpauinfo
display: :0   screen: 0
Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: 
No such file or directory
Error creating VDPAU device: 1


$ xine
Questo è xine (X11 gui) - un riproduttore video libero v0.99.9.
(c) 2000-2014 The xine Team.
Failed to open VDPAU backend libvdpau_i965.so: impossibile aprire il file 
oggetto condiviso: File o directory non esistente
vo_vdpau: Can't create vdp device : No vdpau implementation.
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  151 (XVideo)
  Minor opcode of failed request:  17 ()
  Serial number of failed request:  2632
  Current serial number in output stream:  2632

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory

[Marco]

Same problem here after a fresh install of Ubuntu 16.04.3 on a Thinkpad
T460

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)

$ vdpauinfo
display: :0   screen: 0
Failed to open VDPAU backend libvdpau_.so: cannot open shared object file: No 
such file or directory
Error creating VDPAU device: 1

$ ll /usr/lib/x86_64-linux-gnu/vdpau
lrwxrwxrwx 1 root root  25 gen 13 09:41 libvdpau_nouveau.so -> 
libvdpau_nouveau.so.1.0.0
lrwxrwxrwx 1 root root  25 gen 13 09:41 libvdpau_nouveau.so.1 -> 
libvdpau_nouveau.so.1.0.0
lrwxrwxrwx 1 root root  25 gen 13 09:41 libvdpau_nouveau.so.1.0 -> 
libvdpau_nouveau.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_nouveau.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r300.so -> 
libvdpau_r300.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r300.so.1 -> 
libvdpau_r300.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r300.so.1.0 -> 
libvdpau_r300.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_r300.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r600.so -> 
libvdpau_r600.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r600.so.1 -> 
libvdpau_r600.so.1.0.0
lrwxrwxrwx 1 root root  22 gen 13 09:41 libvdpau_r600.so.1.0 -> 
libvdpau_r600.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_r600.so.1.0.0
lrwxrwxrwx 1 root root  26 gen 13 09:41 libvdpau_radeonsi.so -> 
libvdpau_radeonsi.so.1.0.0
lrwxrwxrwx 1 root root  26 gen 13 09:41 libvdpau_radeonsi.so.1 -> 
libvdpau_radeonsi.so.1.0.0
lrwxrwxrwx 1 root root  26 gen 13 09:41 libvdpau_radeonsi.so.1.0 -> 
libvdpau_radeonsi.so.1.0.0
-rw-r--r-- 4 root root 5132328 gen 13 09:41 libvdpau_radeonsi.so.1.0.0
lrwxrwxrwx 1 root root  23 feb 19  2016 libvdpau_trace.so.1 -> 
libvdpau_trace.so.1.0.0
-rw-r--r-- 1 root root   55376 feb 19  2016 libvdpau_trace.so.1.0.0

$ xine
Questo è xine (X11 gui) - un riproduttore video libero v0.99.9.
(c) 2000-2014 The xine Team.
Failed to open VDPAU backend libvdpau_.so: impossibile aprire il file oggetto 
condiviso: File o directory non esistente
vo_vdpau: Can't create vdp device : No vdpau implementation.
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  151 (XVideo)
  Minor opcode of failed request:  17 ()
  Serial number of failed request:  2631
  Current serial number in output stream:  2631

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

Title:
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared
  object file: No such file or directory

Status in libvdpau package in Ubuntu:
  Triaged
Status in libvdpau-va-gl package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in vdr-plugin-xineliboutput package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid
Status in xine-ui package in Ubuntu:
  Confirmed
Status in libvdpau package in Debian:
  New

Bug description:
  This has been bothering me at least since precise (although there the
  missing link went to libvdpau_nvidia.so which was all the more
  mysterious since I do not own NVIDIA hardware).  In numerous cases do
  I get a warning that libvdpau_i965.so is being tried to be accessed
  but it fails.  I also can't find that file anywhere on my system or in
  the Ubuntu repository.  I tried poking around with ldd to find out
  where the call to that lib comes from but so far unsuccessful.

  $ vdpauinfo
  display: :0   screen: 0
  Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object 
file: No such file or directory
  Error creating VDPAU device: 1

  libvdpau1:i386 is version 0.7-1 and vdpauinfo is 0.1-1

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

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

[Desktop-packages] [Bug 1727958] Re: In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in launcher when opened

[Xavier Guillot]

It says "Fix released" but it was never for me and I still have the
problem of white generic LibreOffice icon in dock - I'm now on Ubuntu
18.04 but was also the case on 17.10...

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

Title:
  In Ubuntu 17.10 Libreoffice writer / calc etc show as white icon in
  launcher when opened

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

Bug description:
  Running Liboreoffice 5.4.2.2 in Ubuntu 17.10, there is an issue with
  the application's icons. The individual icons show up in the list of
  programs, and can be docked in the launcher - but a generic white
  libreoffice icon also shows up in the program list, and if any of the
  docked, correct, icons are clicked, a new, white icon appears that is
  generic across all libreoffice windows (e.g. if I have open writer and
  calc, the white icon gets two red dots and to access either the writer
  or calc window I have to click on the generic icon). This is annoying
  but not crippling, and not solved by a purge and reinstall.

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

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

[Desktop-packages] [Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)

[Xavier Guillot]

I also have this bug with HPLIP 3.17.11 on Ubuntu 18.04 - I know this is
an alpha, but just to inform.

Version 3.17.11 resolved problem of scanner non identified, but I get
the "no system tray detected" at startup...

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

Title:
  HPLIP is not compatible with modern GNOME (No system tray detected on
  this system. Unable to start, exiting.)

Status in HPLIP:
  Invalid
Status in hplip package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install hplip-gui
  3. Launch GNOME session.
  4. Get error message window with header "HPLIP Status Service"
  and text
  "No system tray detected on this system.
  Unable to start, exiting."

  Expected results:
  hp-systray is compatible with modern GNOME

  Actual results:
  hp-systray is not compatible with modern GNOME

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: hplip-gui 3.17.7+repack0-3
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CupsErrorLog: W [01/Sep/2017:17:24:48 +0300] Notifier for subscription 112 
(dbus://) went away, retrying!
  CurrentDesktop: GNOME
  Date: Sat Sep  2 14:10:19 2017
  InstallationDate: Installed on 2017-08-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. UX32A
  PackageArchitecture: all
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic 
root=UUID=c2d4f47c-f1c6-4731-b8d0-dc268c6bf996 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32A.216
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32A
  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.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX32A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1697958] Re: HPLIP cannot detect printers in your network

[Guillermo Molleda]

Riparita per unplugging ĝin de la muro dum 10 sekundoj kaj konektante
ĝin reen kaj ŝalti ĝin denove.

Se arregló desenchufándola de la pared 10 segundos y volviendo a
enchufarla y conectarla.

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

Title:
  HPLIP cannot detect printers in your network

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

Bug description:
  On a fresh install of Kubuntu 17.04 I cannot add a network printer though the 
HPLIP Toolbox. I get an error message that says "HPLIP cannot detect printers 
in your network.
  This may be due to existing firewall settings blocking the required ports. 
When you are in a trusted network environment, you may open the ports for 
network services like mdns and slp in the firewall. For detailed steps follow 
the link. http://hplipopensource.com/node/374;

  However snmpwalk finds the printer perfectly fine
  $ snmpwalk -Os -c public -v 1 192.168.1.21 1.3.6.1.4.1.11.2.3.9.1.1.7.0 
  iso.3.6.1.4.1.11.2.3.9.1.1.7.0 = STRING: 
"MFG:Hewlett-Packard;CMD:PJL,PML,PCLXL,URP,PCL,PDF,POSTSCRIPT;MDL:HP LaserJet 
200 colorMFP M276nw;CLS:PRINTER;DES:Hewlett-Packard LaserJet 200 colorMFP 
M276nw;MEM:MEM=230MB;COMMENT:RES=600x8;LEDMDIS:USB#ff#04#01;CID:HPLJPDLV1;"

  Other systems that were upgraded to 17.04 can still access and detect
  the printer.

  What I expect to happen:
  1. Open HPLIP Toolbox
  2. Add a network printer
  3. Printer is detected

  What happened instead
  1. Open HPLIP Toolbox
  2. Add a network printer
  3. No printers found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: hplip-gui 3.16.11+repack0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jun 14 11:23:50 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-09 (4 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat:
   device for Hewlett-Packard-HP-LaserJet-P1505: 
implicitclass:Hewlett-Packard-HP-LaserJet-P1505
   device for HP-LaserJet-200-colorMFP-M276nw: 
ipp://NPI62B4B3.local:631/ipp/print
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-200-colorMFP-M276nw.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P1505.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-LaserJet-200-colorMFP-M276nw.ppd: Permission denied
   grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P1505.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=e56bcb4e-c73e-4581-9f09-4ef3fe063e74 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8215
  dmi.board.vendor: HP
  dmi.board.version: 83.15
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd04/07/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8215:rvr83.15:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Desktop-packages] [Bug 1745846] Re: gnome-control-center won't open

[lirel]

** Attachment added: "/var/log/aptitude"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745846/+attachment/5044555/+files/aptitude

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

Title:
  gnome-control-center won't open

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

Bug description:
  when opening gnome-control-center nothing happens.
  event using cli will result in $? beeing 0.

  i recently installed cdparanoia and updated mesa, libgl1.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 17:35:13 2018
  InstallationDate: Installed on 2017-02-08 (353 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-11-05 (84 days ago)

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

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

[Desktop-packages] [Bug 1745846] [NEW] gnome-control-center won't open

[lirel]

Public bug reported:

when opening gnome-control-center nothing happens.
event using cli will result in $? beeing 0.

i recently installed cdparanoia and updated mesa, libgl1.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 28 17:35:13 2018
InstallationDate: Installed on 2017-02-08 (353 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to artful on 2017-11-05 (84 days ago)

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


** Tags: amd64 apport-bug artful

** Attachment added: "strace log"
   
https://bugs.launchpad.net/bugs/1745846/+attachment/5044533/+files/gnomesettings.strace.log

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

Title:
  gnome-control-center won't open

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

Bug description:
  when opening gnome-control-center nothing happens.
  event using cli will result in $? beeing 0.

  i recently installed cdparanoia and updated mesa, libgl1.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 17:35:13 2018
  InstallationDate: Installed on 2017-02-08 (353 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to artful on 2017-11-05 (84 days ago)

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

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

[Desktop-packages] [Bug 1745844] [NEW] [4290WCJ, Conexant CX20590, Speaker, Internal] Dummy Output after waking from sleep

[K Starling]

Public bug reported:

Description:Ubuntu 17.10
Release:17.10
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

My laptop goes to sleep automatically after about an hour idle.
Recently, when I wake it up, there are no audio output devices, neither
the internal speakers nor the headphone jack produce any audio, although
my computer still appears as if it's playing audio (e.g. youtube videos
will play, the sound test files act as if they are playing back).

Logging out fixes this issue, the speakers resume working on the login
screen. I don't consider this a reasonable fix, however, as it can
disrupt my work, requiring me to close and reopen all my software.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  starling   4901 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 28 07:52:31 2018
InstallationDate: Installed on 2018-01-15 (12 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1287 F pulseaudio
  starling   4901 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [4290WCJ, Conexant CX20590, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET61WW (1.31 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4290WCJ
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4290WCJ:pvrThinkPadX220:rvnLENOVO:rn4290WCJ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X220
dmi.product.name: 4290WCJ
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

** Affects: alsa-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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1745844

Title:
  [4290WCJ, Conexant CX20590, Speaker, Internal] Dummy Output after
  waking from sleep

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 17.10
  Release:  17.10
  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  My laptop goes to sleep automatically after about an hour idle.
  Recently, when I wake it up, there are no audio output devices,
  neither the internal speakers nor the headphone jack produce any
  audio, although my computer still appears as if it's playing audio
  (e.g. youtube videos will play, the sound test files act as if they
  are playing back).

  Logging out fixes this issue, the speakers resume working on the login
  screen. I don't consider this a reasonable fix, however, as it can
  disrupt my work, requiring me to close and reopen all my software.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  starling   4901 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 28 07:52:31 2018
  InstallationDate: Installed on 2018-01-15 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1287 F pulseaudio
  

[Desktop-packages] [Bug 1697958] Re: HPLIP cannot detect printers in your network

[Guillermo Molleda]

Mi uzas la presilon kutime per USB, sed hodiaŭ post presita horo antaŭe, ĝi 
subite ne presas ĉar ĝi diras min, ke ĝi haltis.
Se mi uzas hp-setup, la eraro aperas: error: No devices found on bus: usb
Sed lsusb diras: Bus 002 Device 009: ID 03f0:112a Hewlett-Packard

Se mi kuras hp-setup -g, ĝi diras:
Searching... (bus=usb, search=(None), desc=0)
hp-setup[4812]: debug: Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 
Optical Mouse
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 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 002 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
Bus 002 Device 010: ID 03f0:112a Hewlett-Packard 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

error: No devices found on bus: usb


Uso la impresora normalmente bien por USB, pero hoy tras haber imprimido una 
hora antes, de pronto no imprime dando como razón que está en pausa.
Al ejecutar hp-setup sale el error: error: No devices found on bus: usb
Pero en lsusb sale: Bus 002 Device 009: ID 03f0:112a Hewlett-Packard

Si ejecuto hp-setup -g sale:
Searching... (bus=usb, search=(None), desc=0)
hp-setup[4812]: debug: Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 
Optical Mouse
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 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
Bus 002 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
Bus 002 Device 010: ID 03f0:112a Hewlett-Packard 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

error: No devices found on bus: usb

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

Title:
  HPLIP cannot detect printers in your network

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

Bug description:
  On a fresh install of Kubuntu 17.04 I cannot add a network printer though the 
HPLIP Toolbox. I get an error message that says "HPLIP cannot detect printers 
in your network.
  This may be due to existing firewall settings blocking the required ports. 
When you are in a trusted network environment, you may open the ports for 
network services like mdns and slp in the firewall. For detailed steps follow 
the link. http://hplipopensource.com/node/374;

  However snmpwalk finds the printer perfectly fine
  $ snmpwalk -Os -c public -v 1 192.168.1.21 1.3.6.1.4.1.11.2.3.9.1.1.7.0 
  iso.3.6.1.4.1.11.2.3.9.1.1.7.0 = STRING: 
"MFG:Hewlett-Packard;CMD:PJL,PML,PCLXL,URP,PCL,PDF,POSTSCRIPT;MDL:HP LaserJet 
200 colorMFP M276nw;CLS:PRINTER;DES:Hewlett-Packard LaserJet 200 colorMFP 
M276nw;MEM:MEM=230MB;COMMENT:RES=600x8;LEDMDIS:USB#ff#04#01;CID:HPLJPDLV1;"

  Other systems that were upgraded to 17.04 can still access and detect
  the printer.

  What I expect to happen:
  1. Open HPLIP Toolbox
  2. Add a network printer
  3. Printer is detected

  What happened instead
  1. Open HPLIP Toolbox
  2. Add a network printer
  3. No printers found

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: hplip-gui 3.16.11+repack0-2
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jun 14 11:23:50 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-06-09 (4 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat:
   device for Hewlett-Packard-HP-LaserJet-P1505: 
implicitclass:Hewlett-Packard-HP-LaserJet-P1505
   device for HP-LaserJet-200-colorMFP-M276nw: 
ipp://NPI62B4B3.local:631/ipp/print
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  PackageArchitecture: all
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-200-colorMFP-M276nw.ppd', 
'/etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P1505.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP-LaserJet-200-colorMFP-M276nw.ppd: Permission denied
   grep: /etc/cups/ppd/Hewlett-Packard-HP-LaserJet-P1505.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed 
root=UUID=e56bcb4e-c73e-4581-9f09-4ef3fe063e74 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: 

[Desktop-packages] [Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters

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

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Desktop-packages] [Bug 1745273] Re: Cannot open terminal with long working directory name containing Unicode characters

[Launchpad Bug Tracker]

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

** Changed in: bash (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/1745273

Title:
  Cannot open terminal with long working directory name containing
  Unicode characters

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using: Ubuntu 17.10

  2) The version of the package you are using: gnome-terminal version
  3.24.2-0ubuntu4; bash version 4.4-5ubuntu1

  3) What you expected to happen: When opening a terminal window with a
  long working directory path containing Unicode characters (such as
  
“/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789”
  in a 80×24 window), gnome-terminal opens normally.

  4) What happened instead: gnome-terminal closes immediately, both when opened 
using
  gnome-terminal 
--working-directory=/home/test/01234567890123456789/01234567890123456789/ä/01234567890123456789/01234567890123456789/01234567890123456789/01234567890123456789
  and when changing to this directory using “cd”. There is no output on stderr 
or anywhere else, the window just closes.

  It seems that gnome-terminal closes because bash crashes with a
  segmentation fault, see https://bugs.launchpad.net/ubuntu/+source
  /gnome-terminal/+bug/1745273/comments/4.

  This makes it impossible to use the shell for many directories with
  long paths. This did NOT happen in Ubuntu 16.04.

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

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

[Desktop-packages] [Bug 1745815] Re: [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Ubuntu Foundations Team Bug Bot]

The attachment "Debdiff with the fix for Bionic" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  New
Status in screen-resolution-extra source package in Bionic:
  New

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

[Desktop-packages] [Bug 1737648] Re: Hold libgweather in -proposed until first bionic language pack

[Gunnar Hjalmarsson]

Time to drop the "block-proposed" tag.

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

** Tags removed: block-proposed

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

Title:
  Hold libgweather in -proposed until first bionic language pack

Status in libgweather package in Ubuntu:
  Fix Released

Bug description:
  In https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu1 we
  worked around a Launchpad configuration bug for Ubuntu language packs.
  That configuration issue has been fixed but we still need a language
  pack to be built after the change was made or we'll end up
  reintroducing LP: #1704533.

  Therefore, I'm filing this bug to keep libgweather in proposed until
  the first bionic language pack is published. Feel free to close this
  bug once that happens.

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

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Wolf Rogner]

Just adding -n 4096 or -s 16384 alone or in combination does not do the
trick.

Only adding these two PLUS removing -v 100 works.

This and the fact that on my mbpr15a the original line works fine
confuses me.

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

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

  duplicity gets started daily via deja-dup automatically.

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

  --

  Failed with an unknown error.

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

  --

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

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

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

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

[Desktop-packages] [Bug 1745825] Re: Crash in "gnome-terminal --preferences" due to downstream patch

[Egmont Koblinger]

Looking a bit into the near future:

gnome-terminal 3.27.90, released in a week, is most likely going to
receive a big change to the Preferences dialogs
(https://bugzilla.gnome.org/show_bug.cgi?id=722114).

I've already prepared porting the transparency patch, except for this
part. I have no intention to port a code that's buggy by design and
hence necessarily buggy by implementation. I'll skip the offending part
in my patch and just unconditionally show the second config option too.

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

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

Title:
  Crash in "gnome-terminal --preferences" due to downstream patch

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When gnome-terminal is _not_ running, execute the command

gnome-terminal --preferences

  Select the Profiles tab, and click on Edit to edit whichever profile.

  gnome-terminal crashes.

  The main idea behind "gnome-terminal --preferences" is that if someone
  screws up their gnome-terminal configuration big time (e.g. set a
  custom command that fails), they can fix it. This crash makes it
  impossible using this convenient approach.

  The crash is not present in upstream gnome-terminal, it is caused by
  the transparency patch. 0001-Restore-transparency.patch adds this
  snippet to src/profile-editor.c:

gtk_widget_style_get (GTK_WIDGET (
terminal_window_get_active (TERMINAL_WINDOW 
(transient_parent))),
  "background-darkness", _darkness,
  NULL);

  transient_parent is NULL in this case, and
  terminal_window_get_active() is not prepared for that.

  Crash is present in Artful (3.24.2-0ubuntu4) as well as current Bionic
  (3.26.2-3ubuntu1). Xenial is not affected because the cmdline option
  --preferences didn't exist back then.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jan 28 11:51:23 2018
  InstallationDate: Installed on 2016-11-09 (444 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-09-21 (128 days ago)

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

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

[Desktop-packages] [Bug 1745825] Re: Crash in "gnome-terminal --preferences" due to downstream patch

[Egmont Koblinger]

Given the existence of this cmdline option, the approach the
transparency patch takes here (locating a terminal window) is broken by
design.

One possibility would be to no longer rely on the transient parent (and
not set that property either), but instead figure out the value of
background-darkness without having access to a terminal window.

The last time I looked at GTK+'s API, it seemed pretty easy to build up
an imaginary node with imaginary widgets of certain CSS classes/names
along its path, and query its style. I've never done it, though.

Another, probably simpler and cleaner solution would be to redesign the
Preferences UI not to require knowing this value.

Gnome-terminal's Preferences UI had several changes throughout the
years, and they went in the direction of simplification, and squeezing
into a simple line the features that really don't require two lines.
E.g. it used to have

  [x] Use the system fixed with font
  Font: [Monospace 9]

and now it has

  [x] Custom font: [Monospace 9]

Transparency also occupies two lines:

  [x] Use transparent background:  none --o- full
  [x] Use transparency from system theme

The second one is only shown if the system theme defines a level of
transparency, as for example Ubuntu's default Ambiance does, while
GTK+'s default Adwaita doesn't. Detecting this is what causes the crash,
so would be nice not to require knowing. (On a side note, the first
option is insensitive if the second one is checked, which means the two
lines should really be swapped.)

My recommendation, in the spirit of Font's simplification on the UI:

  [x] Custom transparency:  none --o- full

When unchecked, the transparency defined by the theme would be used
(which may be translucent, or may be fully opaque). When checked, the
slider becomes sensitive and its setting is used instead of the theme's.
There's no need for an explicit checkbox to disable/enable transparency,
disabling it can simply be achieved by sliding the slider all the way to
the left.

This would also require reducing the number of dconf options from 3 to
2, which is again IMHO a nice simplification (although ideally a one-
shot migration should be performed).

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

Title:
  Crash in "gnome-terminal --preferences" due to downstream patch

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When gnome-terminal is _not_ running, execute the command

gnome-terminal --preferences

  Select the Profiles tab, and click on Edit to edit whichever profile.

  gnome-terminal crashes.

  The main idea behind "gnome-terminal --preferences" is that if someone
  screws up their gnome-terminal configuration big time (e.g. set a
  custom command that fails), they can fix it. This crash makes it
  impossible using this convenient approach.

  The crash is not present in upstream gnome-terminal, it is caused by
  the transparency patch. 0001-Restore-transparency.patch adds this
  snippet to src/profile-editor.c:

gtk_widget_style_get (GTK_WIDGET (
terminal_window_get_active (TERMINAL_WINDOW 
(transient_parent))),
  "background-darkness", _darkness,
  NULL);

  transient_parent is NULL in this case, and
  terminal_window_get_active() is not prepared for that.

  Crash is present in Artful (3.24.2-0ubuntu4) as well as current Bionic
  (3.26.2-3ubuntu1). Xenial is not affected because the cmdline option
  --preferences didn't exist back then.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jan 28 11:51:23 2018
  InstallationDate: Installed on 2016-11-09 (444 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-09-21 (128 days ago)

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

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

[Desktop-packages] [Bug 1745825] [NEW] Crash in "gnome-terminal --preferences" due to downstream patch

[Egmont Koblinger]

Public bug reported:

When gnome-terminal is _not_ running, execute the command

  gnome-terminal --preferences

Select the Profiles tab, and click on Edit to edit whichever profile.

gnome-terminal crashes.

The main idea behind "gnome-terminal --preferences" is that if someone
screws up their gnome-terminal configuration big time (e.g. set a custom
command that fails), they can fix it. This crash makes it impossible
using this convenient approach.

The crash is not present in upstream gnome-terminal, it is caused by the
transparency patch. 0001-Restore-transparency.patch adds this snippet to
src/profile-editor.c:

  gtk_widget_style_get (GTK_WIDGET (
  terminal_window_get_active (TERMINAL_WINDOW (transient_parent))),
"background-darkness", _darkness,
NULL);

transient_parent is NULL in this case, and terminal_window_get_active()
is not prepared for that.

Crash is present in Artful (3.24.2-0ubuntu4) as well as current Bionic
(3.26.2-3ubuntu1). Xenial is not affected because the cmdline option
--preferences didn't exist back then.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-terminal 3.24.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jan 28 11:51:23 2018
InstallationDate: Installed on 2016-11-09 (444 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: gnome-terminal
UpgradeStatus: Upgraded to artful on 2017-09-21 (128 days ago)

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


** Tags: amd64 apport-bug artful bionic

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

Title:
  Crash in "gnome-terminal --preferences" due to downstream patch

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  When gnome-terminal is _not_ running, execute the command

gnome-terminal --preferences

  Select the Profiles tab, and click on Edit to edit whichever profile.

  gnome-terminal crashes.

  The main idea behind "gnome-terminal --preferences" is that if someone
  screws up their gnome-terminal configuration big time (e.g. set a
  custom command that fails), they can fix it. This crash makes it
  impossible using this convenient approach.

  The crash is not present in upstream gnome-terminal, it is caused by
  the transparency patch. 0001-Restore-transparency.patch adds this
  snippet to src/profile-editor.c:

gtk_widget_style_get (GTK_WIDGET (
terminal_window_get_active (TERMINAL_WINDOW 
(transient_parent))),
  "background-darkness", _darkness,
  NULL);

  transient_parent is NULL in this case, and
  terminal_window_get_active() is not prepared for that.

  Crash is present in Artful (3.24.2-0ubuntu4) as well as current Bionic
  (3.26.2-3ubuntu1). Xenial is not affected because the cmdline option
  --preferences didn't exist back then.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-terminal 3.24.2-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Jan 28 11:51:23 2018
  InstallationDate: Installed on 2016-11-09 (444 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to artful on 2017-09-21 (128 days ago)

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

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

Re: [Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Kenneth Loafman]

It's probably the -n option (number of open files).  The default is 1024
and that's way too low.


On Sun, Jan 28, 2018 at 4:07 AM, Wolf Rogner  wrote:

> Sorry for the delay, I wanted to make sure my answer is accurate.
>
> I have three machines set up with 17.10 afresh.
> mbpr13a 8GB,  4.13.0-25-generic
> mbpr15a 16GB, 4.13.0-25-generic
> mbpr13b 16GB, 4.13.0-32-generic
>
> mbpr15a does backups ooB
> mbpr13a/b have the reported issue
>
> The original line in
> /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop
>
> Exec=sh -c "ulimit -v 100; exec /usr/lib/x86_64-linux-gnu/deja-dup
> /deja-dup-monitor"
>
> leads to the issue
>
> Setting ulimit -n or ulimit -s additionally does not remedy the error
>
> This line worked
>
> Exec=sh -c "ulimit -s 16384; ulimit -n 4096; exec /usr/lib/x86_64-linux-
> gnu/deja-dup/deja-dup-monitor"
>
> @Vaclav #35: I always test after reboot and consequently after suspend to
> RAM.
> The solution works under those conditions.
>
> What irritates my: mbpr15a works with the original line. ???
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1727653
>
> Title:
>   error: can't start new thread
>
> Status in Duplicity:
>   In Progress
> Status in deja-dup package in Ubuntu:
>   Confirmed
> Status in duplicity package in Ubuntu:
>   In Progress
>
> Bug description:
>   $ uname -a
>   Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>
>   duplicity gets started daily via deja-dup automatically.
>
>   Every now and then (approx. every third time) I get the following
>   error:
>
>   --
>
>   Failed with an unknown error.
>
>   Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1546, in 
>   with_tempdir(main)
> File "/usr/bin/duplicity", line 1540, in with_tempdir
>   fn()
> File "/usr/bin/duplicity", line 1391, in main
>   do_backup(action)
> File "/usr/bin/duplicity", line 1468, in do_backup
>   restore(col_stats)
> File "/usr/bin/duplicity", line 731, in restore
>   restore_get_patched_rop_iter(col_stats)):
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 560, in Write_ROPaths
>   for ropath in rop_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 523, in integrate_patch_iters
>   for patch_seq in collated:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 389, in yield_tuples
>   setrorps(overflow, elems)
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 378, in setrorps
>   elems[i] = iter_list[i].next()
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 107, in filter_path_iter
>   for path in path_iter:
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 121, in difftar2path_iter
>   tarinfo_list = [tar_iter.next()]
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 339, in next
>   self.set_tarfile()
> File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line
> 333, in set_tarfile
>   self.current_fp = self.fileobj_iter.next()
> File "/usr/bin/duplicity", line 768, in get_fileobj_iter
>   manifest.volume_info_dict[vol_num])
> File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
>   fileobj = tdp.filtered_open_with_delete("rb")
> File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line
> 119, in filtered_open_with_delete
>   fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
> File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778,
> in filtered_open
>   return gpg.GPGFile(False, self, gpg_profile)
> File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202,
> in __init__
>   'logger': self.logger_fp})
> File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py",
> line 374, in run
>   create_fhs, attach_fhs)
> File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py",
> line 420, in _attach_fork_exec
>   process.thread.start()
> File "/usr/lib/python2.7/threading.py", line 736, in start
>   _start_new_thread(self.__bootstrap, ())
>   error: can't start new thread
>
>   --
>
>   Restarting deja-dup manually fixes the problem and the next few days,
>   automatic backup will run correctly until (see above).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: duplicity 0.7.12-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Uname: Linux 4.13.0-16-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Oct 26 10:49:45 2017
>   InstallationDate: Installed on 2017-10-20 (5 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64
> (20171018)
>   SourcePackage: duplicity
>   

[Desktop-packages] [Bug 1745805] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Mattia Rizzolo]

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

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

Title:
  package python-libxml2 2.9.3+dfsg1-1ubuntu0.5 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 127

Status in libxml2 package in Ubuntu:
  Incomplete

Bug description:
  while  installing yum this error occured

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Jan 28 12:28:55 2018
  DuplicateSignature:
   package:python-libxml2:2.9.3+dfsg1-1ubuntu0.5
   Setting up python-libxml2 (2.9.3+dfsg1-1ubuntu0.5) ...
   /var/lib/dpkg/info/python-libxml2.postinst: 6: 
/var/lib/dpkg/info/python-libxml2.postinst: pycompile: not found
   dpkg: error processing package python-libxml2 (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2018-01-13 (14 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libxml2
  Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.5 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745815] Re: [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Graham Inggs]

** Also affects: screen-resolution-extra (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  New
Status in screen-resolution-extra source package in Bionic:
  New

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

[Desktop-packages] [Bug 1727653] Re: error: can't start new thread

[Wolf Rogner]

Sorry for the delay, I wanted to make sure my answer is accurate.

I have three machines set up with 17.10 afresh.
mbpr13a 8GB,  4.13.0-25-generic
mbpr15a 16GB, 4.13.0-25-generic
mbpr13b 16GB, 4.13.0-32-generic

mbpr15a does backups ooB
mbpr13a/b have the reported issue

The original line in
/etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop

Exec=sh -c "ulimit -v 100; exec /usr/lib/x86_64-linux-gnu/deja-dup
/deja-dup-monitor"

leads to the issue

Setting ulimit -n or ulimit -s additionally does not remedy the error

This line worked

Exec=sh -c "ulimit -s 16384; ulimit -n 4096; exec /usr/lib/x86_64-linux-
gnu/deja-dup/deja-dup-monitor"

@Vaclav #35: I always test after reboot and consequently after suspend to RAM.
The solution works under those conditions.

What irritates my: mbpr15a works with the original line. ???

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Confirmed
Status in duplicity package in Ubuntu:
  In Progress

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

  duplicity gets started daily via deja-dup automatically.

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

  --

  Failed with an unknown error.

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

  --

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

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

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

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

[Desktop-packages] [Bug 511086] Re: Missing some Czech unicode characters in selected text

[sam tygier]

Seems to work fine in current evince 3.26.0-3 with poppler
0.57.0-2ubuntu5

** Changed in: poppler (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Missing some Czech unicode characters in selected text

Status in poppler package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: evince

  I have a small problem with Document Viewer 2.28.1 (evince). I have 
downloaded the time table (pdf file) of the Prague bus 165 
(http://jrportal.dpp.cz/jrportal/LineList.aspx?t=3=5=1=165=2010-01-04)
 in Firefox and it was opened by Document Viewer. It looked well including 
special Czech character. But when I selected the text by mouse, some Czech 
characters were missing. Like 'ř', 'š' etc. For example "Přístav Radotín" 
looked like 'P ístav Radotín' when selected etc. It seem that some fonts are 
missing and it is all but I think things like this should work automatically on 
Ubuntu.
  (Ubuntu 9.10, Czech language)

  ProblemType: Bug
  Architecture: i386
  Date: Fri Jan 22 09:55:54 2010
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/evince
  Package: evince 2.28.1-0ubuntu1.2
  ProcEnviron:
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
  SourcePackage: evince
  Uname: Linux 2.6.31-17-generic i686

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

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

[Desktop-packages] [Bug 1716230] Re: gnome-software wont install thirdparty debs

[sam tygier]

I don't have a 16.04 install around currently. But it seems to be fixed
in 3.26.3-2ubuntu1

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

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

Title:
  gnome-software wont install thirdparty debs

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  If I download .deb file e.g. chrome or skype, it will open in gnome-
  software, but pressing the install button does nothing.

  This is on ubuntu 16.04 (installed today from a 16.04.2 image, and
  fully updated).

  This is maybe a re-occurrence of Bug #1672424 or Bug #1573408

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.5-0ubuntu0.16.04.5
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep 10 14:53:44 2017
  InstallationDate: Installed on 2017-09-10 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1745815] [NEW] [patch] screen-resolution-extra should depend on polkit-1-auth-agent instead of policykit-1-gnome

[Vlad Orlov]

Public bug reported:

System: Ubuntu MATE 18.04
Package version: 0.17.1

Expected behavior:

Package screen-resolution-extra should depend on polkit-1-auth-agent.
This would allow installing it in desktop environments that provide
their own PolicyKit authentication agents, like MATE which has mate-
polkit. All these agents provide polkit-1-auth-agent (which is a virtual
package).

Actual behavior:

Package screen-resolution-extra depends on policykit-1-gnome. In MATE
desktop it leads to installation of both mate-polkit and
policykit-1-gnome, which is not needed.

Additional info:

Package screen-resolution-extra is used by nvidia-settings tool,
therefore the problem affects everyone who uses proprietary nvidia
drivers.

The debdiff that is attached below makes screen-resolution-extra depend
on polkit-1-auth-agent, fixing the problem.

** Affects: screen-resolution-extra (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic patch

** Patch added: "Debdiff with the fix for Bionic"
   
https://bugs.launchpad.net/bugs/1745815/+attachment/5044398/+files/screen-resolution-extra-debdiff-bionic

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

Title:
  [patch] screen-resolution-extra should depend on polkit-1-auth-agent
  instead of policykit-1-gnome

Status in screen-resolution-extra package in Ubuntu:
  New

Bug description:
  System: Ubuntu MATE 18.04
  Package version: 0.17.1

  Expected behavior:

  Package screen-resolution-extra should depend on polkit-1-auth-agent.
  This would allow installing it in desktop environments that provide
  their own PolicyKit authentication agents, like MATE which has mate-
  polkit. All these agents provide polkit-1-auth-agent (which is a
  virtual package).

  Actual behavior:

  Package screen-resolution-extra depends on policykit-1-gnome. In MATE
  desktop it leads to installation of both mate-polkit and
  policykit-1-gnome, which is not needed.

  Additional info:

  Package screen-resolution-extra is used by nvidia-settings tool,
  therefore the problem affects everyone who uses proprietary nvidia
  drivers.

  The debdiff that is attached below makes screen-resolution-extra
  depend on polkit-1-auth-agent, fixing the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1745815/+subscriptions

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

[Desktop-packages] [Bug 1745811] [NEW] kernel 4.13.0-32.35 mangles display

[Serpico]

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

Public bug reported:

After latest update 80% of the screen is corrupted, leaving a strip down the 
right side which is legible.
Starting up in "recovering" mode ( from GRUB menu ) allow to use the whole 
screen ( logs files were collected in recovering mode - lower resolution )
Eee PC 1005HA

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CurrentDesktop: XFCE
Date: Sun Jan 28 08:47:05 2018
InstallationDate: Installed on 2017-08-14 (166 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug corruption i386 regression-update xenial

** This bug has been marked a duplicate of bug 1745734
   kernel 4.13.0-32.35 mangles display

** Description changed:

  After latest update 80% of the screen is corrupted, leaving a strip down the 
right side which is legible.
  Starting up in "recovering" mode ( from GRUB menu ) allow to use the whole 
screen ( logs files were collected in recovering mode - lower resolution )
+ Eee PC 1005HA
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Jan 28 08:47:05 2018
  InstallationDate: Installed on 2017-08-14 (166 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1745811

Title:
  kernel 4.13.0-32.35 mangles display

Status in xorg package in Ubuntu:
  New

Bug description:
  After latest update 80% of the screen is corrupted, leaving a strip down the 
right side which is legible.
  Starting up in "recovering" mode ( from GRUB menu ) allow to use the whole 
screen ( logs files were collected in recovering mode - lower resolution )
  Eee PC 1005HA

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Jan 28 08:47:05 2018
  InstallationDate: Installed on 2017-08-14 (166 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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