[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

[Daniel van Vugt]

Since you have applied the workaround from bug 994921 already, one of
those approaches should work now.

Please try:
  apport-cli _usr_bin_gnome-shell.1000.crash
  apport-cli _usr_bin_Xwayland.1000.crash

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-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: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750977] Re: HP Pavilion 16.04.3 Speaker works when run off USB stick, but speaker doesn't work when run from HD install

[Frank C]

** Description changed:

- When I run from USB stick, speakers work.  When I run from install on
- HD, speaker doesn't work, but headphones work.
+ When I run from USB stick (ubuntu on thumb drive), speakers work.  When
+ I run from install on HD, speaker doesn't work, but headphones work.
  
  If I right click above speaker icon (volume control), speakers work as
  long as button is held down and pointer isn't moved.  Speaker stops
  working upon release of right button.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/pcmC1D0c:   frank  1536 F...m pulseaudio
-  /dev/snd/controlC1:  frank  1536 F pulseaudio
-  /dev/snd/controlC0:  frank  1536 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/pcmC1D0c:   frank  1536 F...m pulseaudio
+  /dev/snd/controlC1:  frank  1536 F pulseaudio
+  /dev/snd/controlC0:  frank  1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 22 01:19:15 2018
  InstallationDate: Installed on 2018-02-20 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2293
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd02/02/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0971120002405F1620180:rvnHewlett-Packard:rn2293:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 0971120002405F1620180
  dmi.sys.vendor: Hewlett-Packard

** Description changed:

- When I run from USB stick (ubuntu on thumb drive), speakers work.  When
- I run from install on HD, speaker doesn't work, but headphones work.
+ When I boot from liveusb, speakers work.  When I boot from install on
+ HD, speaker doesn't work, but headphones work.
  
  If I right click above speaker icon (volume control), speakers work as
  long as button is held down and pointer isn't moved.  Speaker stops
  working upon release of right button.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   frank  1536 F...m pulseaudio
   /dev/snd/controlC1:  frank  1536 F pulseaudio
   /dev/snd/controlC0:  frank  1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 22 01:19:15 2018
  InstallationDate: Installed on 2018-02-20 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2293
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd02/02/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0971120002405F1620180:rvnHewlett-Packard:rn2293:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 0971120002405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

Title:
  HP Pavilion 16.04.3 Speaker works when 

[Desktop-packages] [Bug 1750977] [NEW] HP Pavilion 16.04.3 Speaker works when run off USB stick, but speaker doesn't work when run from HD install

[Frank C]

Public bug reported:

When I run from USB stick, speakers work.  When I run from install on
HD, speaker doesn't work, but headphones work.

If I right click above speaker icon (volume control), speakers work as
long as button is held down and pointer isn't moved.  Speaker stops
working upon release of right button.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   frank  1536 F...m pulseaudio
 /dev/snd/controlC1:  frank  1536 F pulseaudio
 /dev/snd/controlC0:  frank  1536 F pulseaudio
CurrentDesktop: Unity
Date: Thu Feb 22 01:19:15 2018
InstallationDate: Installed on 2018-02-20 (2 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: None of the above
Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] 
Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2293
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 78.21
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd02/02/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0971120002405F1620180:rvnHewlett-Packard:rn2293:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 0971120002405F1620180
dmi.sys.vendor: Hewlett-Packard

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

Title:
  HP Pavilion 16.04.3 Speaker works when run off USB stick, but speaker
  doesn't work when run from HD install

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I run from USB stick, speakers work.  When I run from install on
  HD, speaker doesn't work, but headphones work.

  If I right click above speaker icon (volume control), speakers work as
  long as button is held down and pointer isn't moved.  Speaker stops
  working upon release of right button.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   frank  1536 F...m pulseaudio
   /dev/snd/controlC1:  frank  1536 F pulseaudio
   /dev/snd/controlC0:  frank  1536 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 22 01:19:15 2018
  InstallationDate: Installed on 2018-02-20 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2293
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd02/02/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0971120002405F1620180:rvnHewlett-Packard:rn2293:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 0971120002405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

[Hadrien]

When executing ubuntu-bug with the crash file, I do not get any bug ID.

A popup opens, with two buttons on the bottom: [Details] [Continue]
I click on [Continue] and I am back to my terminal, with the prompt. Nothing is 
written in my terminal and no Web browser opens.

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-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: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750973] [NEW] Program sub menus dark gray on black, thus illegible

[KalaDude]

Public bug reported:

When using a program, for example Libre Writer, when I click on file,
open, then in the Open menu box I have the opportunity to change the
file type from "All files" to a specific file type, when I click on "All
files" the selection list appears. The font color for the different file
types is a dark grey on a black background making the list items
illegible. As I move the cursor, the font color and background change to
"normal" black on a white background but only for the item that the
cursor is hovering over at that moment. This makes the rest of the list
impossible to read and moving the cursor slowly down the list, pausing
to read each item, is a very cumbersome way to get things done.

This doesn't just happen on Libre Writer but also Inkscape, Geeqie, and
a variety of other programs and their sub menus. The only program I
could find where this didn't happen was Firefox (58.02). Furthermore
this happens on 3 different machines, each with a different processor,
different graphics card and where the machine has multiple monitors, it
happens on all monitors.

All machines are running 16.04, one with the latest updates, the others
slightly behind on updates. If I go to Settings-Appearance-Theme and
change the theme from Ambiance to anything else, the sub menus become
legible again.  Ambiance is the default theme.   If I switch the Theme
back to Ambiance the problem resumes.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Feb 21 20:57:30 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: sysdig, 0.20.0, 4.4.0-112-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1033]
InstallationDate: Installed on 2014-04-20 (1404 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=8f4996c0-c2f5-449f-a35c-47f301f66803 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: 970 Extreme3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.3+16.04.20171116-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.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
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: Wed Feb 21 19:32:42 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPixArt USB Optical Mouse MOUSE, id 8
 inputLogitech USB Keyboard KEYBOARD, id 9
 inputLogitech USB Keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: nouveau

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


** Tags: amd64 

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Ping-Wu]

Yes, ready to close this bug report.  Will continue to watch this issue
and will let you know if problem reappears.  Not likely to happen.

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1750969] Re: gnome-disks (11) udisks_partition_table_get_type_ → finish_cb → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist

[Jean-Baptiste Lallement]

** Summary changed:

- 
/usr/bin/gnome-disks:11:udisks_partition_table_get_type_:finish_cb:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist
+ gnome-disks (11) udisks_partition_table_get_type_ → finish_cb → 
g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist

** Changed in: gnome-disk-utility (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  gnome-disks (11) udisks_partition_table_get_type_ → finish_cb →
  g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-disk-utility.  This problem was most recently seen with package version 
3.27.90-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b730c61ef20c3588294a89784eaf44ebef513a36 
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-disk-utility/+bug/1750969/+subscriptions

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

[Desktop-packages] [Bug 1750969] [NEW] gnome-disks (11) udisks_partition_table_get_type_ → finish_cb → g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-disk-utility.  This problem was most recently seen with package version 
3.27.90-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b730c61ef20c3588294a89784eaf44ebef513a36 
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-disk-utility (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: bionic kylin-18.04

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

Title:
  gnome-disks (11) udisks_partition_table_get_type_ → finish_cb →
  g_closure_invoke → signal_emit_unlocked_R → g_signal_emit_valist

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-disk-utility.  This problem was most recently seen with package version 
3.27.90-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b730c61ef20c3588294a89784eaf44ebef513a36 
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-disk-utility/+bug/1750969/+subscriptions

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

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

[Jean-Baptiste Lallement]

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

** This bug has been marked a duplicate of bug 1725928
   package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with 
differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

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

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

Status in sane-backends package in Ubuntu:
  New

Bug description:
  Docky Dock didn't launch problem :(

  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: Wed Feb 21 23:29:32 2018
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu2.1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-bOgmlL/08-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb
 (--unpack):
trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2018-01-25 (27 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: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Apport retracing service]

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

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 #1505409, 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/1750962/+attachment/5060103/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1505409
   gnome-shell crashed with SIGTRAP in x_io_error() from _XIOError() from 
_XEventsQueued() from XPending() from gdk_check_xpending() ["Connection to 
xwayland lost"]

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  doing nothing made a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Tue Feb 20 07:08:07 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-05-20 (277 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: Upgraded to artful on 2018-01-24 (28 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Gunnar Hjalmarsson]

Thanks. 6.0.1 is currently in -proposed, but will be shipped with 18.04.
Can we consider the issue fixed for Ubunbu 18.04?

We switch to Noto Serif CJK as default only in 18.04. In previous
version the default serif fonts for Chinese are AR PL UMing and AR PL
UKai.

Considering that, are we ready to close this bug report?

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Hui Wang]

reply #5, yes, only xenial needs this commit because artful and bionic
already had this commit.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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

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

[Apport retracing service]

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

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 #1748450, 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/1750957/+attachment/5060092/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  didn't break anything essential to my knowledge...

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Feb 21 21:20:48 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-02-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Ping-Wu]

Problem seems to have been solved in LibreOffice 6.0.1:


** Attachment added: "LO-6.0.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1750938/+attachment/5060090/+files/LO-6.0.jpg

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Ping-Wu]

In LibreOffice 5.4.4, the noto-fonts-cjk does not show up in the
exported pdf file:

(OS: Ubuntu 18.04, fully upgraded)

** Attachment added: "LO-5.4.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1750938/+attachment/5060091/+files/LO-5.4.jpg

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Ping-Wu]

Correction: noto "sans" cjk sc seems to be OK when the same file is
exported to pdf.  It's noto "serif" cjk sc that's having problems.  (But
again, problem seems to have been solved in LibreOffice 6.0.1.)

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1184387] Re: while playing video computer becomes unresponsive

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1274115
   snd_pcm_avail() returned a value that is exceptionally large
** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  while playing video computer becomes unresponsive

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When I was playing a flash video the screen froze and the audio continued a 
bit and then stopped for a minute or so and then started for a few seconds 
again. I was able to ssh into my laptop and save the logs. Syslog said:
  pulseaudio[2242]: [alsa-sink] alsa-util.c: snd_pcm_avail() returned a value 
that is exceptionally large: 591416 bytes (3352 ms).
  pulseaudio[2242]: [alsa-sink] alsa-util.c: Most likely this is a bug in the 
ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
  so I did. The full logs are attached. This bug happens often but I can't 
reliably reproduce it and it seems very random.

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

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

[Desktop-packages] [Bug 997482] Re: High CPU & IO usage after starting VirtualBox

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1274115
   snd_pcm_avail() returned a value that is exceptionally large
** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  High CPU & IO usage after starting VirtualBox

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Operating system: Ubuntu 12.04 LTS (up-to-date) with kernel 3.2.0-24-generic 
x86_64
  System: HP EliteBook 8440p Core i7-640M / 4g 500gb 14”
  Package version: 1.0.25+dfsg-0ubuntu1

  Occurences: 1 (that's the first time I have this issue)

  Problem:
   - VirtualBox was opened and try to send sound through alsa drivers.
   - System nearly freezes and the harddrive is working hard.
   - When I get the system back, there were some logs in the /var/log/syslog:

  May 10 07:58:15 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: 
snd_pcm_avail() returned a value that is exceptionally large: 866268 bytes 
(4910 ms).
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Most 
likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this 
issue to the ALSA developers.
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: 
snd_pcm_dump():
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Soft 
volume PCM
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Control: 
PCM Playback Volume
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: min_dB: 
-51
  May 10 07:58:17 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: max_dB: 0
  May 10 07:58:20 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: 
resolution: 256
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Its 
setup is:
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   stream 
  : PLAYBACK
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   access 
  : MMAP_INTERLEAVED
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   format 
  : S16_LE
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
subformat: STD
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
channels : 2
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   rate   
  : 44100
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   exact 
rate   : 44100 (44100/1)
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   msbits 
  : 16
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
buffer_size  : 16384
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_size  : 8192
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_time  : 185759
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
tstamp_mode  : ENABLE
  May 10 07:58:22 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_step  : 1
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
avail_min: 8192
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
period_event : 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
start_threshold  : -1
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
stop_threshold   : 4611686018427387904
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
silence_threshold: 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
silence_size : 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
boundary : 4611686018427387904
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Slave: 
Hardware PCM card 0 'HDA Intel' device 0 subdevice 0
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c: Its 
setup is:
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   stream 
  : PLAYBACK
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   access 
  : MMAP_INTERLEAVED
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   format 
  : S16_LE
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
subformat: STD
  May 10 07:58:24 inf-p-ols dbus[1072]: [system] Failed to activate service 
'org.freedesktop.nm_dispatcher': timed out
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   
channels : 2
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   rate   
  : 44100
  May 10 07:58:24 inf-p-ols pulseaudio[2557]: [alsa-sink] alsa-util.c:   exact 
rate   : 

[Desktop-packages] [Bug 996808] Re: Sound stop works 10 minutes after logon

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1274115
   snd_pcm_avail() returned a value that is exceptionally large
** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  Sound stop works 10 minutes after logon

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I met this error after new installation of Ubuntu 10.04 Lucid Lynx. It's not 
a hardware problem cause I have a Windows XP in dual boot and in Win sound card 
works good without any exception.
  The sound stop works ever when I use any program and stop works if I do 
nothing probably ten minutes after logon.

  I attach a output of command:
  $ cat /var/log/syslog |grep pulseaudio

  I am sorry to say that syslog contain some Czech words… E.g. the first
  sentence means in English:

  snd_pcm_avail() navrátil hodnotu, která je nezvykle vysoká: 4294963992 bajtů 
(24347868 ms).
  snd_pcm_avail() return a value that is exceptionally large: 4294963992 bytes 
(24347868 ms).

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

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

[Desktop-packages] [Bug 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large

[Daniel van Vugt]

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

Now tracking in bug 1750947 (I think) to get a fix in 16.04.

** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  snd_pcm_avail() returned a value that is exceptionally large

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Sometimese sound begins stutter while listen to music or watching youtube. In 
syslog I see:
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 
866944 bytes (4914 ms).
  Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] 
alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. 
Please report this issue to the ALSA developers.

  I'm using Kubuntu 13.10
  $ uname -a
  Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 
2013 x86_64 x86_64 x86_64 GNU/Linux
  $ kde4-config --version
  Qt: 4.8.4
  KDE Development Platform: 4.12.0
  kde4-config: 1.0
  $ pulseaudio --version
  pulseaudio 4.0
  $ alsactl --version
  alsactl version 1.0.27.1

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

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

[Desktop-packages] [Bug 1539967] Re: Audio skips (buffer underruns) intermittently but particularly when screen blanks

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1274115
   snd_pcm_avail() returned a value that is exceptionally large
** This bug has been marked a duplicate of bug 1750947
   pulseaudio print lots of error when selecting unavailable profile

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

Title:
  Audio skips (buffer underruns) intermittently but particularly when
  screen blanks

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Audio playback via ALSA (snd_intel_hda) & pulseaudio inevitably
  'skips' (repeats buffer content) intermittently a few times each hour,
  and severely whenever the screen is blanked for inactivity.

  CPU load is low (mostly idle).

  I didn't have this problem with my previous fresh installation of
  Ubuntu (14.04.3 LTS) on this hardware.

  From dmesg, kernel appears to be using the TSC clocksource:
  [ 3.180127] clocksource: Switched to clocksource tsc

  Upon startup, Pulseaudio sees high resolution timers:
  I: [pulseaudio] main.c: Fresh high-resolution timers available! Bon appetit!

  When audio skips, alsa-sink.c logs a massive scheduling delay (e.g.
  1070.00 ms > 15.99 ms) and also that "snd_pcm_avail() returned a value
  that is exceptionally large: 623124 bytes (1177 ms)"

  Currently running Ubuntu 15.10 Wily (fresh install).
  linux-sound-base:
Installed: 1.0.25+dfsg-0ubuntu5
  pulseaudio:
  Installed: 1:6.0-0ubuntu13

  Audio output used is Built-in Audio Analogue Surround 5.1 (motherboard
  audio, Realtek ALC889A)

  Attaching log from pulseaudio -

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl fglrx
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   chinf  7928 F...m pulseaudio
   /dev/snd/controlC0:  chinf  7928 F pulseaudio
   /dev/snd/controlC1:  chinf  7928 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jan 30 18:17:01 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-11 (50 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Sound works for a while, then breaks
  Title: [GA-MA790GP-DS4H, Realtek ALC889A, Green Line Out, Rear] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-MA790GP-DS4H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-DS4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-DS4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790GP-DS4H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-12T14:13:00.166647

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Daniel van Vugt]

Commit a222a07920731f3c4967faccab7469af50b428a4 is obviously a little
old. So "Fix Released" for current series. Only needs some work to get
it into xenial.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Daniel van Vugt]

Sorry, I missed the part about the crashes being in the kernel.

Still, part of the above sounds like bug 1274115.

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: Hui Wang (hui.wang) => (unassigned)

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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

[Desktop-packages] [Bug 1740146] Re: [AMD C-60] System slow on wayland, lagging mouse (but fast in Xorg)

[Daniel van Vugt]

** Summary changed:

- [AMD C-60] System slow on wayland, lagging mouse and programs on 17.10 & 18.04
+ [AMD C-60] System slow on wayland, lagging mouse (but fast in Xorg)

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

Title:
  [AMD C-60] System slow on wayland, lagging mouse (but fast in Xorg)

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

Bug description:
  Ubuntu 18.04 development branch @ 26/12/2017

  Overall system is lagging when opening programs and mouse, not smooth to work 
with
  on gnome and the default wayland session, the xorg session is fast without 
lags. Tested the same machine on 17.10 and have same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 17:15:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6290] [1025:0598]
  InstallationDate: Installed on 2017-12-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
  Lsusb:
   Bus 002 Device 002: ID 0402:7675 ALi Corp.
   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: Acer AO722
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.family: Type1Family
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1750953] [NEW] Selecting "Single Display" often dosn't show scaling options until the settings are applied.

[Jonathan Chan]

Public bug reported:

# Release

Description:Ubuntu 17.10
Release:17.10

# Package

Not sure how to check the version of the GNOME settings applet, sorry.

# Steps to reproduce

Connect an external monitor. Open the "Displays" section of the Settings
app. Select "Single Display" and select the currently disabled monitor
in preparation for switching to it.

# Expected

The "Scale" selection appears, as it does when the monitor is both
selected and "Apply" has been clicked.

# What happens instead

The "Scale" selection does not appear, and in fact only appears after
"Apply" has been clicked. This means that in order to switch to another
monitor, you have to first apply an incorrect setting (scaling will be
wrong), click "Keep Settings," find your way to the "Scale" selection,
select the correct scaling, click "Apply" again, then click "Keep
Settings" a final time.

This is really bad when switching between monitors. The worst part is
that whether or not the option is visible is inconsistent.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 21 23:17:17 2018
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-11-30 (83 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/zsh
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  Selecting "Single Display" often dosn't show scaling options until the
  settings are applied.

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

Bug description:
  # Release

  Description:  Ubuntu 17.10
  Release:  17.10

  # Package

  Not sure how to check the version of the GNOME settings applet, sorry.

  # Steps to reproduce

  Connect an external monitor. Open the "Displays" section of the
  Settings app. Select "Single Display" and select the currently
  disabled monitor in preparation for switching to it.

  # Expected

  The "Scale" selection appears, as it does when the monitor is both
  selected and "Apply" has been clicked.

  # What happens instead

  The "Scale" selection does not appear, and in fact only appears after
  "Apply" has been clicked. This means that in order to switch to
  another monitor, you have to first apply an incorrect setting (scaling
  will be wrong), click "Keep Settings," find your way to the "Scale"
  selection, select the correct scaling, click "Apply" again, then click
  "Keep Settings" a final time.

  This is really bad when switching between monitors. The worst part is
  that whether or not the option is visible is inconsistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 21 23:17:17 2018
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-11-30 (83 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/zsh
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Hui Wang]

[ 800.271277] Freezing user space processes ...
[ 820.267656] Freezing of tasks failed after 20.006 seconds (1 tasks refusing 
to freeze, wq_busy=0):
[ 820.267704] alsa-sink-HDMI D 0 1554 1117 0x0004
[ 820.267710] Call Trace:
[ 820.267723] __schedule+0x3c2/0x8b0
[ 820.267727] schedule+0x36/0x80
[ 820.267730] schedule_timeout+0x17a/0x360
[ 820.267735] ? call_timer_fn+0x140/0x140
[ 820.267745] snd_power_wait+0xba/0x110 [snd]
[ 820.267751] ? snd_power_wait+0xba/0x110 [snd]
[ 820.267756] ? wake_up_q+0x70/0x70
[ 820.267766] snd_pcm_common_ioctl1+0x41/0x930 [snd_pcm]
[ 820.267772] snd_pcm_playback_ioctl1+0x13e/0x250 [snd_pcm]
[ 820.26] ? eventfd_ctx_read+0x67/0x210
[ 820.267784] snd_pcm_playback_ioctl+0x28/0x40 [snd_pcm]
[ 820.267789] do_vfs_ioctl+0xa1/0x5f0
[ 820.267792] SyS_ioctl+0x79/0x90
[ 820.267796] entry_SYSCALL_64_fastpath+0x1e/0xa9
[ 820.267798] RIP: 0033:0x7fb4d9bbdf07
[ 820.267800] RSP: 002b:7fb4d5d3cc78 EFLAGS: 0246 ORIG_RAX: 
0010
[ 820.267803] RAX: ffda RBX: 7fb4d5d3cca0 RCX: 7fb4d9bbdf07
[ 820.267805] RDX: 01888d20 RSI: 4122 RDI: 0016
[ 820.267807] RBP: 01888d20 R08: 0043 R09: 0001
[ 820.267808] R10: 0185f870 R11: 0246 R12: 01888d20
[ 820.267810] R13:  R14: 7fb4d5d3a650 R15: 00615080
[ 820.267837] OOM killer enabled.
[ 820.267838] Restarting tasks ... done.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

[Hui Wang]

E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_avail() returned a value that is 
exceptionally large: 26649288 bytes (151073 ms).
E: [alsa-sink-HDMI 0] alsa-util.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_dump():
E: [alsa-sink-HDMI 0] alsa-util.c: Hooks PCM
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: Slave: Hardware PCM card 0 'HD-Audio 
Generic' device 3 subdevice 0
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_delay() returned a value that is 
exceptionally large: -25928392 bytes (-146986 ms).
E: [alsa-sink-HDMI 0] alsa-util.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
E: [alsa-sink-HDMI 0] alsa-util.c: snd_pcm_dump():
E: [alsa-sink-HDMI 0] alsa-util.c: Hooks PCM
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...
E: [alsa-sink-HDMI 0] alsa-util.c: Slave: Hardware PCM card 0 'HD-Audio 
Generic' device 3 subdevice 0
E: [alsa-sink-HDMI 0] alsa-util.c: Its setup is:
...

** Summary changed:

- pulseaudio crashed when selecting unavailable profile
+ pulseaudio print lots of error when selecting unavailable profile

** Description changed:

  Only pulseaudio-xenial has this problem.
  
  we need to backport this commit to pulseaudio-xenial.
  
  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4
+ 
+ After printing out the error logs, the kernel crashes and system hangs.

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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

[Desktop-packages] [Bug 1416943] Re: gnome-shell crashed SIGTRAP in _cogl_set_error() from allocate_from_gl_foreign() from _cogl_texture_2d_gl_allocate() from cogl_texture_allocate() from cogl_texture

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gnome-shell crashed SIGTRAP in _cogl_set_error() from
  allocate_from_gl_foreign() from _cogl_texture_2d_gl_allocate() from
  cogl_texture_allocate() from cogl_texture_2d_new_from_data()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding gnome-shell.  This problem was most recently seen with
  version 3.14.3-0ubuntu2, the problem page at
  https://errors.ubuntu.com/problem/f92b415c3cc8e4c77c519c0f23a89be4d7f784ed
  contains more details.

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

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

[Desktop-packages] [Bug 1556661] Re: gnome-shell crashed with SIGSEGV in meta_screen_free()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_screen_free()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/828caaef21d44111907f5b36e8bc4ea6ffd551b2

  ---

  System send error Message for any programs who was chrashed.and start
  error messenger.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Mar 13 15:46:40 2016
  DisplayManager:

  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 13'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 11'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'false'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 11'"
  InstallationDate: Installed on 2016-03-13 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160312)
  ProcCmdline: gnome-shell
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fb1ad5fac47 :   mov
0x18(%rdi),%rbp
   PC (0x7fb1ad5fac47) ok
   source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_screen_free () from /usr/lib/libmutter.so.0
   meta_display_close () from /usr/lib/libmutter.so.0
   meta_display_open () from /usr/lib/libmutter.so.0
   meta_run () from /usr/lib/libmutter.so.0
   main ()
  Title: gnome-shell crashed with SIGSEGV in meta_screen_free()
  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/1556661/+subscriptions

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

[Desktop-packages] [Bug 1702084] Re: gnome-shell crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from meta_monitor_config_assign_crtcs() from apply_configuration() from m

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  gnome-shell crashed with SIGABRT in g_assertion_message() from
  g_assertion_message_expr() from meta_monitor_config_assign_crtcs()
  from apply_configuration() from meta_monitor_config_restore_previous()

Status in gnome-shell package in Ubuntu:
  Fix Released

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.18.5-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/73bfad71c644fab93dd08112f6abb3c0e2fa4a19 
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 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/1702084/+subscriptions

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

[Desktop-packages] [Bug 1690031] Re: pulseaudio crashed in pcm.c:2757: snd_pcm_area_copy: Assertion `src < dst || src >= dst + bytes' failed.

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  pulseaudio crashed in pcm.c:2757: snd_pcm_area_copy: Assertion `src <
  dst || src >= dst + bytes' failed.

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/e21c0bcfff3f6359b38c4cb20a7ba11d2a56ffa0 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1565387] Re: gnome-shell crashed with SIGSEGV in gjs_value_from_g_argument()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gnome-shell crashed with SIGSEGV in gjs_value_from_g_argument()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/894581d378382392e5972043d417570ba9e7fd8b

  ---

  no sure what happened, just logged in

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Apr  3 11:04:22 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-03-27 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: /usr/bin/gnome-shell
  SegvAnalysis:
   Segfault happened at: 0x7f1adaeb96f0 :
mov(%rax),%rax
   PC (0x7f1adaeb96f0) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   gjs_value_from_g_argument () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gnome-shell crashed with SIGSEGV in gjs_value_from_g_argument()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers

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

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

[Desktop-packages] [Bug 1690061] Re: pulseaudio crashed with SIGABRT in pa_close_pipe() from pa_signal_done() from main()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_close_pipe() from
  pa_signal_done() from main()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/5d3ffc4aab0eaf05067b16645c50d89b3e0c4ae4 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1561249] Re: gnome-shell crashed with SIGTRAP in _XIOError() from _XReply() from doGetScreenResources() from XRRGetScreenResourcesCurrent()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gnome-shell crashed with SIGTRAP in _XIOError() from _XReply() from
  doGetScreenResources() from XRRGetScreenResourcesCurrent()

Status in gnome-shell package in Ubuntu:
  Fix Released

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

  ---

  Crash after disconnecting my laptop from external monitor (connected
  through VGA).

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Mar 24 00:27:31 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-02-24 (28 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/libmutter.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libXrandr.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: Upgraded to xenial on 2016-03-02 (21 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1690057] Re: pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from tdb_rec_read() from tdb_find() from tdb_find_lock_hash()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from
  tdb_rec_read() from tdb_find() from tdb_find_lock_hash()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/4df1f7ebeed62837d758e11878501d46242405c8 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1691383] Re: gnome-shell crashed with SIGSEGV in init_config_from_output() from meta_monitor_config_update_current() from meta_monitor_manager_handle_apply_configuration() from

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  gnome-shell crashed with SIGSEGV in init_config_from_output() from
  meta_monitor_config_update_current() from
  meta_monitor_manager_handle_apply_configuration() from
  ffi_call_unix64() from ffi_call()

Status in gnome-shell package in Ubuntu:
  Fix Released

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.20.4-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/e975a320f57aaad38342419c90f41542d4b088e1 
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 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/1691383/+subscriptions

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

[Desktop-packages] [Bug 1691914] Re: gnome-shell crashed with SIGABRT: Assertion failure in desktop-entries.c:510: "code should not be reached" from desktop_entry_unref() from g_slist_foreach()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gnome-shell crashed with SIGABRT: Assertion failure in desktop-
  entries.c:510: "code should not be reached" from desktop_entry_unref()
  from g_slist_foreach()

Status in gnome-shell package in Ubuntu:
  Fix Released

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.23.90-0ubuntu0~ppa0, the problem page at 
https://errors.ubuntu.com/problem/9446111a3eabc3b3f76238cdd28fd0029994fdef 
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 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/1691914/+subscriptions

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

[Desktop-packages] [Bug 1714042] Re: gnome-shell crashed with SIGTRAP in _XError() from handle_error() from handle_response() from _XReply() from XIQueryPointer() from gdk_x11_device_xi2_query_state()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  gnome-shell crashed with SIGTRAP in _XError() from handle_error() from
  handle_response() from _XReply() from XIQueryPointer() from
  gdk_x11_device_xi2_query_state()

Status in gnome-shell package in Ubuntu:
  Fix Released

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

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  Uname: Linux 4.12.0-999-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug 30 13:35:52 2017
  Disassembly: $4 = 0x4 
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2015-12-02 (636 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151027)
  ProcCmdline: /usr/bin/gnome-shell
  Registers: No symbol "__nih_abort_msg" in current context.
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:

  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip fax libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1691702] Re: gnome-shell crashed with SIGSEGV in js() from () from gc() from () from Cell() from () from tenuredZone() from js() from () from Shape() from () from zone() from j

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  gnome-shell crashed with SIGSEGV in js() from () from gc() from ()
  from Cell() from () from tenuredZone() from js() from () from Shape()
  from () from zone() from js() from () from ObjectImpl() from () from
  zone() from MarkInternal() from js() from () from gc() from () from
  MarkValueRoot()

Status in gnome-shell package in Ubuntu:
  Fix Released

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.18.5-0ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/dbf4909429b1fb0777288c4a65f3587a0f585881 
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 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/1691702/+subscriptions

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

[Desktop-packages] [Bug 1722256] Re: Wifi connection status icon shows a "?" when connected

[Ken VanDine]

This was affecting me on 17.10 as well.  Added dns=default did resolve
it.  Without that there was no nameserver being set.

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

Title:
  Wifi connection status icon shows a "?" when connected

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

Bug description:
  Wifi connection status icon on the top bar shows a "?" even when connected to 
a wifi network.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (11 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: gnome-shell 3.26.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1702203] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from _meta_idle_monitor_watch_fire() from g_list_foreach() from

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a() from g_object_ref() from
  _meta_idle_monitor_watch_fire() from g_list_foreach() from
  meta_idle_monitor_xsync_handle_xevent()

Status in gnome-shell package in Ubuntu:
  Fix Released

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.18.5-0ubuntu0.3, the problem page at 
https://errors.ubuntu.com/problem/280ae858593e624b9a9f1ac0533b7673b2e35a60 
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 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/1702203/+subscriptions

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

[Desktop-packages] [Bug 1749732] Re: gnome-shell crashed with SIGSEGV in malloc_consolidate()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  gnome-shell crashed with SIGSEGV in malloc_consolidate()

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/12802bbe39099d82ed789c75b8a9b2d9eca851ce

  ---

  This is:
  apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.3
    Candidate: 3.18.5-0ubuntu0.3
    Version table:
  on Ubuntu
  lsb_release -rd
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Gnome Shell will crash just about every time when doing software
  updates. For instance this morning when updating:

  Start-Date: 2018-02-15  09:04:14
  Commandline: apt-get -y install postfix postfix-doc
  Upgrade: postfix:amd64 (3.1.0-3ubuntu0.2, 3.1.0-3ubuntu0.3), 
postfix-doc:amd64 (3.1.0-3ubuntu0.2, 3.1.0-3ubuntu0.3)
  End-Date: 2018-02-15  09:05:31

  it crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Feb 15 08:56:24 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (1210 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7f5cbb99eb20 ) at malloc.c:4183
   _int_malloc (av=av@entry=0x7f5cbb99eb20 , 
bytes=bytes@entry=32816) at malloc.c:3450
   __GI___libc_malloc (bytes=32816) at malloc.c:2913
   __alloc_dir (statp=0x7ffea71631b0, flags=0, close_fd=true, fd=33) at 
../sysdeps/posix/opendir.c:247
   opendir_tail (fd=33) at ../sysdeps/posix/opendir.c:145
  Title: gnome-shell crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1750533] Re: Proprietary software is labelled red

[Robert Ancell]

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

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

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

Title:
  Proprietary software is labelled red

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Proprietary software delivered as snaps in GNOME Software is
  highlighted red in the software details. While it's great that we show
  the license for software, it's not ideal that the implication of the
  colours is that free=good, proprietary=bad. We should provide software
  and enable users to make an informed choice what they install, but not
  make the implication that it's a bad choice.

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

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

[Desktop-packages] [Bug 1740146] Re: [AMD C-60] System slow on wayland, lagging mouse and programs on 17.10 & 18.04

[Daniel van Vugt]

** Summary changed:

- System slow on wayland, lagging mouse and programs on 17.10 & 18.04
+ [AMD C-60] System slow on wayland, lagging mouse and programs on 17.10 & 18.04

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

Title:
  [AMD C-60] System slow on wayland, lagging mouse and programs on 17.10
  & 18.04

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

Bug description:
  Ubuntu 18.04 development branch @ 26/12/2017

  Overall system is lagging when opening programs and mouse, not smooth to work 
with
  on gnome and the default wayland session, the xorg session is fast without 
lags. Tested the same machine on 17.10 and have same issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 26 17:15:16 2017
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Wrestler [Radeon HD 6290] [1025:0598]
  InstallationDate: Installed on 2017-12-18 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171215)
  Lsusb:
   Bus 002 Device 002: ID 0402:7675 ALi Corp.
   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: Acer AO722
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=b20f465f-45a3-49da-b5ea-8351b8e94c03 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE10-BZ
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd12/06/2011:svnAcer:pnAO722:pvrV1.08:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.08:
  dmi.product.family: Type1Family
  dmi.product.name: AO722
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM

[Daniel van Vugt]

Your VM's logs mention a lot about finding Razer input devices, but also:
"No input driver specified, ignoring this device."

So this might be a bug in package 'xserver-xorg-input-libinput'. Can you
install xserver-xorg-input-evdev in the VM by some means?

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

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

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

Title:
  Mouse & Keyboard completely unresponsive when starting a VM

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Could be virt-manager or gnome-shell related.

  I was passing through 1 USB device that wasn't my main mouse or
  keyboard. Otherwise pretty normal configuration that I've used before.

  After the VM's bios screen, the whole system froze except the clock in
  the desktop menu bar/panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  Uname: Linux 4.15.1-041501-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 23:47:02 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-27 (112 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1749085] Re: Applications packaged as snap and deb appear twice in the search results.

[Robert Ancell]

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

** This bug has been marked a duplicate of bug 1711801
   Packages in both Snap and .deb form show twice (e.g. GIMP)

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

Title:
  Applications packaged as snap and deb appear twice in the search
  results.

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Searching for "VLC" in Ubuntu Software shows two results. The first is
  "vlc" and has the same description as VideoLAN. However, installing
  the first entry doesn't create a VLC shortcut.

  What is the first "vlc" entry? Is it malware?

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[陳昌倬]

Cannot reprocedure this issue in Debian sid (libreoffice-writer
1:6.0.1-1, fonts-noto-cjk 1:20170601+repack1-1). Maybe there are some
changes between libreoffice 1:5.4.4-0ubuntu5 and 1:6.0.1-1 that fix this
issue?

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1750548] Re: Need some way to show multiple banners

[Robert Ancell]

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

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

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

Title:
  Need some way to show multiple banners

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  While GNOME Software allows one banner to be shown, it would be great
  to have multiple banners in rotation. Having multiple banners would
  enable us to rotate around a bunch of promoted applications rather
  than have one application stuck there for a while.

  A discussion was had on the forum. https://forum.snapcraft.io/t
  /supporting-multiple-featured-snaps-in-gnome-software/3124/7

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

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

[Desktop-packages] [Bug 1750534] Re: Channel selector doesn't look like a button

[Robert Ancell]

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

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

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

Title:
  Channel selector doesn't look like a button

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  In GNOME Software the channel selection item is a green label, but
  doesn't look like a click-able button. It should be more obviously
  clickable, so that users understand how to switch channel.

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Gunnar Hjalmarsson]

Thanks for your report.

No, changing the CJK font is certainly not "easily done", and there is
only one week left before "FeatureFreeze" for Ubuntu 18.04.

Considering that it's the same glyphs, can the issue have something to
do with the package format, i.e. weight specific OTC files, we are using
in Debian/Ubuntu? Someone commenting on the document you linked to
mentioned that using TTF files solved the problem.

Let's first and foremost make sure that we don't compare apples and
oranges.

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[陳昌倬]

** Attachment added: "Debian sid test result"
   
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1750938/+attachment/5060074/+files/debian-sid.pdf

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1662253] Re: pulseaudio crashed with SIGSEGV in pa_bluetooth_device_any_transport_connected() from transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_bluetooth_device_any_transport_connected() from
  transport_state_changed_cb() from pa_hook_fire() from
  pa_bluetooth_transport_set_state() from
  pa_bluetooth_transport_unlink()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/611e08e54b2e1bab7707f341fda104668886d193 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1690070] Re: pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from pa_msgobject_cast() from adjust_rates() from sink_input_process_msg_cb() from pa_asyncmsgq_dispat

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  pulseaudio crashed with SIGSEGV in pa_msgobject_isinstance() from
  pa_msgobject_cast() from adjust_rates() from
  sink_input_process_msg_cb() from pa_asyncmsgq_dispatch()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/002d0b29f2768aae27e98aeb96eaf53d46605a33 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1690043] Re: pulseaudio crashed with SIGSEGV in adjust_rates() from sink_input_process_msg_cb() from pa_asyncmsgq_flush() from pa_thread_mq_done() from userdata_free()

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  pulseaudio crashed with SIGSEGV in adjust_rates() from
  sink_input_process_msg_cb() from pa_asyncmsgq_flush() from
  pa_thread_mq_done() from userdata_free()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/827c89858820835d0e8f693f69e597145ab65807 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1690027] Re: pulseaudio crashed with SIGABRT in pa_msgobject_isinstance() from pa_msgobject_cast() from adjust_rates() from sink_input_process_msg_cb() from asyncmsgq_read_cb()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  pulseaudio crashed with SIGABRT in pa_msgobject_isinstance() from
  pa_msgobject_cast() from adjust_rates() from
  sink_input_process_msg_cb() from asyncmsgq_read_cb()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/35253f6f4c1d8bccfe358b8c58fb275c649b935a 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1499113] Re: pulseaudio crashed with SIGSEGV in set_profile_cb() from pa_card_set_profile() from command_set_card_profile() from pa_pdispatch_run() from pstream_packet_callback

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  pulseaudio crashed with SIGSEGV in set_profile_cb() from
  pa_card_set_profile() from command_set_card_profile() from
  pa_pdispatch_run() from pstream_packet_callback()

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/7ccf872ad0cc36d20cf02cc1c1ba6f0d881287cd

  ---

  Connect two devices, celu movil samsung and headphone

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena  26880 F...m pulseaudio
   /dev/snd/controlC0:  caravena  26880 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Sep 23 20:52:31 2015
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2015-07-26 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  SegvAnalysis:
   Segfault happened at: 0x7f1042baad12:mov0x34(%rax),%eax
   PC (0x7f1042baad12) ok
   source "0x34(%rax)" (0x0055) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/pulse-6.0/modules/module-bluez5-device.so
   pa_card_set_profile () from /usr/lib/libpulsecore-6.0.so
   ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so
   pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-6.0.so
   ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so
  Title: pulseaudio crashed with SIGSEGV in pa_card_set_profile()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Desktop-packages] [Bug 1690056] Re: pulseaudio crashed with SIGABRT in sink_input_detach() from pa_sink_process_msg() from asyncmsgq_read_work() from pa_rtpoll_run() from thread_func()

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  pulseaudio crashed with SIGABRT in sink_input_detach() from
  pa_sink_process_msg() from asyncmsgq_read_work() from pa_rtpoll_run()
  from thread_func()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/5f657ed114d93f711b0cd115f59362cb8728ac14 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1690042] Re: pulseaudio crashed with SIGSEGV in pa_bluetooth_device_any_transport_connected() from transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_

[Daniel van Vugt]

Fix released (no crashes reported after 16.10)

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

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

Title:
  pulseaudio crashed with SIGSEGV in
  pa_bluetooth_device_any_transport_connected() from
  transport_state_changed_cb() from pa_hook_fire() from
  pa_bluetooth_transport_set_state() from pa_bluetooth_transport_put()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:9.0-2ubuntu2.1, the problem page at 
https://errors.ubuntu.com/problem/182443fe9aecf3b5c56d1bcb8f87b57dd92ed3d9 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1750938] Re: Noto Chinese fonts won't print in Libreoffice

[Gunnar Hjalmarsson]

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

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in Ubuntu Kylin:
  New
Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

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

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

[Desktop-packages] [Bug 1690049] Re: pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from tdb_needs_recovery() from tdb_lock_list() from tdb_lock()

[Daniel van Vugt]

Fix released (no crashes reported after 17.04)

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

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

Title:
  pulseaudio crashed with SIGABRT in memcpy() from tdb_read() from
  tdb_needs_recovery() from tdb_lock_list() from tdb_lock()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/b27e6406aff54551cee511b54ee62a5447f3c98a 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio crashed when selecting unavailable profile

[Daniel van Vugt]

If this is a crash then it's very likely we already have a bug report
for it.

Can you find a stack trace of the crash?

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

Title:
  pulseaudio crashed when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

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

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

[Desktop-packages] [Bug 1694455] Re: Bluetooth: Cannot receive files

[Daniel van Vugt]

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

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

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

Title:
  Bluetooth: Cannot receive files

Status in bluez package in Ubuntu:
  Invalid
Status in gnome-bluetooth package in Ubuntu:
  Invalid

Bug description:
  # Use case

  Ubuntu 17.04, quite fresh installation, updated.

  Bluetooth file transmission

  I want to send files to my smartphone, and receive files sent by my
  smartphone via bluetooth. I pair both devices, initiate file transfer
  from one of the devices, and the other device asks me what to do.

  # Problems

  This is a mix from usability and technical issues.

  1. OBEX disabled (bug 1645631)

  The bluetooth file transmission service OBEX was not started. I started and 
enabled OBEX:
  `systemctl --user start obex`
  `systemctl --user enable obex`

  ```
  Mai 30 14:47:55 tp systemd[1661]: Starting Bluetooth OBEX service...
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  ```

  2. OBEX silently fails (this bug)

  After having OBEX enabled, I was able to transmit files from laptop to
  smartphone, yet I could not receive files on the laptop. In the system
  log, you could see that OBEX fails (please note `FORBIDDEN`):

  ```
  Mai 30 14:47:55 tp obexd[8168]: OBEX daemon 5.43
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: PUT(0x2), FORBIDDEN(0x43)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:48:04 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:48:04 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  I did not receive a popup notification asking me to receive the file
  or not.

  In the file sharing preferences `gnome-file-share-properties`, there
  is a setting to automatically receive files via bluetooth. With this
  box checked, you're finally able to receive files from your
  smartphone.

  Successful log for comparison:
  ```
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: CONNECT(0x0), (null)(0x0)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), (null)(0x)
  Mai 30 14:55:50 tp obexd[8168]: PUT(0x2), CONTINUE(0x10)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), (null)(0x)
  Mai 30 14:56:28 tp obexd[8168]: DISCONNECT(0x1), SUCCESS(0x20)
  Mai 30 14:56:28 tp obexd[8168]: disconnected: Transport got disconnected
  ```

  # Expected behaviour

  OBEX is started by default to handle bluetooth file transfers.

  If no automatic file receipt is configured, a popup notification asks
  me if I want to receive the file or not.

  If this is not possible, there should be a notification pointing the
  user to the configuration.

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

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

[Desktop-packages] [Bug 1690069] Re: pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from memcpy() from tdb_read() from tdb_transaction_recover() from tdb_open_ex()

[Daniel van Vugt]

Fix released (no crashes reported after 16.04)

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

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

Title:
  pulseaudio crashed with SIGABRT in __memcpy_avx_unaligned() from
  memcpy() from tdb_read() from tdb_transaction_recover() from
  tdb_open_ex()

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:8.0-0ubuntu3.2, the problem page at 
https://errors.ubuntu.com/problem/1ff87d46ce1a224f74b97b5ccaa8a4eb12bad180 
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 you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1750947] Re: pulseaudio crashed when selecting unavailable profile

[Hui Wang]

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Tags added: originate-from-1737727 somerville

** Changed in: hwe-next
   Importance: Undecided => Critical

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

Title:
  pulseaudio crashed when selecting unavailable profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

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

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

[Desktop-packages] [Bug 1750947] [NEW] pulseaudio crashed when selecting unavailable profile

[Hui Wang]

Public bug reported:

Only pulseaudio-xenial has this problem.

we need to backport this commit to pulseaudio-xenial.

https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

** Affects: pulseaudio (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 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/1750947

Title:
  pulseaudio crashed when selecting unavailable profile

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

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

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

[Desktop-packages] [Bug 1750937] Re: 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Bill Miller]

In the kernel log when I booted with the -116 kernel, I found this

nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '

This line doesn't occur in the kernel log for the -112 kernel, the case
when the driver works.

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  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: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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

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

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

[Johan Marius Wesselink]

I tested the proposed package on Lubuntu 17.10.

I tested some example programs they use either:
GLProfile glp = GLProfile.getDefault();
Or they use the GLCanvas default constructor.

Before this version all these examples emitted the typical error found
in the previous version of jogl2. The new package RESOLVED this problem.

I noticed after some experimenting that replacing getDefault with 
get(GLProfile.GL2);
also solved the problem. Then I found this thread.

I build scilab from source using the git repository. This is the master
and future 6.1 version it has the same problem. However, scilab 6 and
higher have the jogl2 library prebuild and distributed as a thirdparty
library. Removing this library doesn't work. The problem is that the
scirender module and the gui modules depend on the old syntax. The Java
path in the past was javax.media. In newer version of jogl2 this changed
to com.jogamp. This means that besides removing the faulty library from
scilab the modules scirender and gui need to be patched. I did just this
in the last days. The git master branch version 6.1 build and works with
the new jogl2 version. I noticed however one regression bug the cursor
selection in the plot window work kind of inverted. This is an old bug
which I have seen before.

So, yes this fixes the jogl2 bug. But, no likely not the scilab bug.
Depends how you get scilab and which version probably.

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

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

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

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

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

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

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

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

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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

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

[Desktop-packages] [Bug 1741839] Re: gdm3 lock screen/gnome-shell freeze after opening laptop lid

[Daniel van Vugt]

Sounds like this may be bug 1724259 (fixed last night).

Please try updating your system, make sure you then have libinput 1.8.4
installed, reboot and retest.

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

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

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

Title:
  gdm3 lock screen/gnome-shell freeze after opening laptop lid

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

Bug description:
  Sometimes when I open the lid of my laptop to input my password to
  unlock, everything freezes and I am unable to do anything but to hard
  reboot. I am talking about the lock screen (logged in already just
  locked).

  Ubuntu 17.10
  gdm3 version: 3.26.1-3ubuntu3
  gnome-shell version: 3.26.2-0ubuntu0.1
  ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-12-19 (384 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: gdm3 3.26.1-3ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Tags: artful wayland-session third-party-packages
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-20 (80 days ago)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2017-06-17T01:23:09.018818

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

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

[Desktop-packages] [Bug 1750941] [NEW] Pidgin crashes if I select text on chat and try to drag and drop it

[Leonardo Müller]

Public bug reported:

When I select text on Pidgin's chat and try to drag and drop it, the
pidgin crashes. This crash creates no file in /var/crash and gdb is very
inconclusive:

$ sudo gdb
GNU gdb (Ubuntu 8.1-0ubuntu1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) attach 23768
Anexando a process 23768
[New LWP 23769]
[New LWP 23771]
[New LWP 23772]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fc9e38ba951 in __GI___poll (fds=0x7fc9c0001650, nfds=7, timeout=6998)
at ../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: Arquivo ou diretório não encontrado.
(gdb) continue
Continuando.
[Thread 0x7fc9c9bf0700 (LWP 23772) exited]
[Thread 0x7fc9ca3f1700 (LWP 23771) exited]
[Thread 0x7fc9ccd28700 (LWP 23769) exited]
[Inferior 1 (process 23768) exited with code 01]
(gdb) bt
No stack.

This is easily reproducible, as it happens always I select text on the
chat and try to drag and drop.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pidgin 1:2.12.0-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Feb 21 22:58:19 2018
InstallationDate: Installed on 2017-06-13 (253 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: pidgin
UpgradeStatus: Upgraded to bionic on 2017-10-20 (125 days ago)

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


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

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

Title:
  Pidgin crashes if I select text on chat and try to drag and drop it

Status in pidgin package in Ubuntu:
  New

Bug description:
  When I select text on Pidgin's chat and try to drag and drop it, the
  pidgin crashes. This crash creates no file in /var/crash and gdb is
  very inconclusive:

  $ sudo gdb
  GNU gdb (Ubuntu 8.1-0ubuntu1) 8.1
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  (gdb) attach 23768
  Anexando a process 23768
  [New LWP 23769]
  [New LWP 23771]
  [New LWP 23772]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fc9e38ba951 in __GI___poll (fds=0x7fc9c0001650, nfds=7, timeout=6998)
  at ../sysdeps/unix/sysv/linux/poll.c:29
  29../sysdeps/unix/sysv/linux/poll.c: Arquivo ou diretório não encontrado.
  (gdb) continue
  Continuando.
  [Thread 0x7fc9c9bf0700 (LWP 23772) exited]
  [Thread 0x7fc9ca3f1700 (LWP 23771) exited]
  [Thread 0x7fc9ccd28700 (LWP 23769) exited]
  [Inferior 1 (process 23768) exited with code 01]
  (gdb) bt
  No stack.

  This is easily reproducible, as it happens always I select text on the
  chat and try to drag and drop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pidgin 1:2.12.0-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Feb 21 22:58:19 2018
  InstallationDate: Installed on 2017-06-13 (253 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: pidgin
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (125 days ago)

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

[Daniel van Vugt]

I've had a look at your crash files and unfortunately they do not
contain stack traces we can read yet. Sometimes they do in plain text...
Uploading the crash files with the 'ubuntu-bug' command should fix that,
allowing robots to do proper retracing on them.

Asking other people to reproduce such problems is not a good idea, since
there are too many similar gnome-shell crashes right now. Another person
is just as likely to reproduce a different crash to yours which confuses
the situation.

Next step: Please upload the crash files using the ubuntu-bug command only. We 
cannot proceed until that is done:
  ubuntu-bug _usr_bin_gnome-shell.1000.crash
  ubuntu-bug _usr_bin_Xwayland.1000.crash
When done, please tell us the new bug IDs.

P.S. Sharing crash files publicly on your own web server is considered
insecure, because it is publicly readable by anyone. A more secure
approach for sharing crash files (and only if 'ubuntu-bug' fails), is to
set your bug report to "Private" and then attach them to the bug report.
That way only a very small number of bug managers can see it, as well as
yourself. Using the ubuntu-bug command also creates 'Private' bugs by
default.

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-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: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750379] Re: Distortion Realtek ALC887

[Daniel van Vugt]

OK, please try some older (or much newer) kernels then:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Desktop-packages] [Bug 1750938] [NEW] Noto Chinese fonts won't print in Libreoffice

[Ping-Wu]

Public bug reported:

LibreOffice won't print or export to pdf when document contains Noto
fonts (both sans and serif).  Change to Source/Adobe (identical glyphs)
solves the problem.  Also there is no problem in Fedora, which uses
Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to Source/Adobe.
This should be easily done.  See:

https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

** Affects: fonts-noto-cjk (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Noto Chinese fonts won't print in Libreoffice

Status in fonts-noto-cjk package in Ubuntu:
  New

Bug description:
  LibreOffice won't print or export to pdf when document contains Noto
  fonts (both sans and serif).  Change to Source/Adobe (identical
  glyphs) solves the problem.  Also there is no problem in Fedora, which
  uses Source/Adobe cjk fonts. Ubuntu uses Noto, should switch to
  Source/Adobe.  This should be easily done.  See:

  https://www.libreofficechina.org/forum.php?mod=viewthread=1928#lastpost

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1750938/+subscriptions

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

[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off

[Daniel van Vugt]

Bug 1750773 does not seem to exist (!?)

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in Nouveau Xorg driver:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Hui Wang]

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

-- 
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:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Artful:
  Fix Committed

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 1750937] [NEW] 14.04 Kernel update on 2/21 breaks Nvidia drivers

[Bill Miller]

Public bug reported:

Running fine with nvidia-384 until this kernel update came along.  When
booted into the new kernel, got super low resolution and nvidia-settings
was missing most of its functionality - could not change resolution.

Rebooted into 4.4.0-112 kernel and all was well.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-112-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
 GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Feb 21 19:23:39 2018
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
 bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
 nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
 nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:6253]
InstallationDate: Installed on 2015-03-03 (1086 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: ASUSTeK COMPUTER INC. M11AD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/15/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M11AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: M11AD
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
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: Wed Feb 21 18:48:14 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

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


** Tags: amd64 apport-bug possible-manual-nvidia-install resolution trusty 
ubuntu

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

Title:
  14.04 Kernel update on 2/21 breaks Nvidia drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
 

[Desktop-packages] [Bug 1750087] Re: libreoffoice crashes when trying to save

[Lyn Perrine]

libreoffice-core:
  Installed: 1:5.4.4-0ubuntu5
  Candidate: 1:5.4.4-0ubuntu5
  Version table:
 *** 1:5.4.4-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  libreoffoice crashes when trying to save

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  To reproduce type hello world into a libreoffice document. Then press the 
save icon. libreoffice crashes. Description:Ubuntu Bionic Beaver 
(development branch)
  Release:18.04
   
  to try to save and then try it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Fri Feb 16 16:19:38 2018
  InstallationDate: Installed on 2017-06-20 (241 days ago)
  InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 
(20170619)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-02-02 (14 days ago)

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

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

[Desktop-packages] [Bug 1750087] Re: libreoffoice crashes when trying to save

[Lyn Perrine]

Doubt this is helpful but  it was in /var/crash/

** Attachment added: "_usr_bin_strace.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750087/+attachment/5060024/+files/_usr_bin_strace.1000.crash

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

Title:
  libreoffoice crashes when trying to save

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  To reproduce type hello world into a libreoffice document. Then press the 
save icon. libreoffice crashes. Description:Ubuntu Bionic Beaver 
(development branch)
  Release:18.04
   
  to try to save and then try it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Fri Feb 16 16:19:38 2018
  InstallationDate: Installed on 2017-06-20 (241 days ago)
  InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 
(20170619)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-02-02 (14 days ago)

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

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

[Desktop-packages] [Bug 819995] Re: "Print to file" PDF metadata broken

[gna]

I have tried some solutions before i found this bug,

An extract of metadata made with exiftool (libimage-exiftool-perl
9.46-1) shows an important difference on a document that displaying
dates right, and one sample print-to-file, the tags for PDF related date
info is totally missing:

-PDF:CreateDate=
-PDF:ModifyDate=


Example command:
exiftool -args -G1 --filename --directory PDF_FILE_NAME.PDF

Example output of Print-to-File:
-ExifTool:ExifToolVersion=9.46
-System:FileSize=107 kB
-System:FileModifyDate=2018:02:22 00:56:18+01:00
-System:FileAccessDate=2018:02:22 00:56:40+01:00
-System:FileInodeChangeDate=2018:02:22 01:30:18+01:00
-System:FilePermissions=rw-rw-r--
-File:FileType=PDF
-File:MIMEType=application/pdf
-PDF:PDFVersion=1.5
-PDF:Linearized=No
-PDF:PageCount=1
-PDF:Creator=cairo 1.13.1 (http://cairographics.org)
-PDF:Producer=cairo 1.13.1 (http://cairographics.org)

Example output of PDF with working dates:
-ExifTool:ExifToolVersion=9.46
-System:FileSize=3.2 MB
-System:FileModifyDate=2015:11:02 14:37:59+01:00
-System:FileAccessDate=2018:02:22 01:49:42+01:00
-System:FileInodeChangeDate=2015:11:02 14:37:59+01:00
-System:FilePermissions=rw-r-
-File:FileType=PDF
-File:MIMEType=application/pdf
-PDF:PDFVersion=1.5
-PDF:Linearized=No
-PDF:PageCount=89
-PDF:Language=en-US
-PDF:TaggedPDF=Yes
-PDF:Title=XenServer 6.x Best Practices
-PDF:Author=Daily, Camille
-PDF:Keywords=Minimum Restrictions, No Restrictions
-PDF:Creator=Microsoft® Word 2013
-PDF:CreateDate=2013:10:30 08:44:27-05:00
-PDF:ModifyDate=2013:10:30 08:44:27-05:00
-PDF:Producer=Microsoft® Word 2013



evince 3.10.3-0ubuntu10.4 amd64
libcairo2 1.13.0~20140204-0ubuntu1.1 amd64
Description:Ubuntu 14.04.5 LTS
Kernel: Linux 3.13.0-142-generic #191-Ubuntu SMP x86_64

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

Title:
  "Print to file" PDF metadata broken

Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.04 Natty Narwhal 64bit

  libgnomeprint2.2-0 - 2.18.8-0ubuntu1

  It seems libgnomeprint sends wrong date, Jan 1st 1970 to PDF metadata when 
printing to file (PDF)
  This behaviour is reproducible for me on both 64bit and 32bit versions of 
11.04
   
  Using dialog "print to file" choosing PDF as output format "Creation Date" 
and "Last edited" is always set to  "Thu 01 Jän 1970 00:59:59 CET" which is 
afaik Date 0 for Unices.
  I am using german localization but in case of needed screenshots I can of 
course change to english.
  This behaviour happens on my main machine (64bit) and my old notebook (32bit) 
looking to my self produced PDFs from 10.10 definitely show the same behaviour, 
I could also look on old backups for even older version.

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

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

[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland

[Mathieu Trudel-Lapierre]

Ok, I'm opening the tasks for Xenial and Trusty, and we can decide
exactly where it makes sense to do the SRU for these changes.

Plus, I understand maybe it was still reproducible in some form on
bionic, so it this should be revisited in general.

** Also affects: console-setup (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-shell (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: console-setup (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: gnome-shell (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  Input falls through to gdm3 and terminates the session on Ctrl+C after
  udevadm trigger is executed under wayland

Status in Snappy:
  Won't Fix
Status in console-setup package in Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in console-setup source package in Trusty:
  New
Status in gdm3 source package in Trusty:
  New
Status in gnome-shell source package in Trusty:
  New
Status in mutter source package in Trusty:
  New
Status in systemd source package in Trusty:
  New
Status in console-setup source package in Xenial:
  New
Status in gdm3 source package in Xenial:
  New
Status in gnome-shell source package in Xenial:
  New
Status in mutter source package in Xenial:
  New
Status in systemd source package in Xenial:
  New

Bug description:
  = Test Cases =

  Test Case 1:
  - Login under Wayland (session Ubuntu)
  - Open a terminal
  - snap install gimp
  - Wait until installation finishes successfully
  - In the terminal window press CTRL+C

  Result:
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  Test Case 2:
  - Login under Wayland (session Ubuntu)
  - Open a terminal and type the following command:
    $ sudo udevadm trigger
  - In the terminal window press CTRL+C

  Result
  - Expected: ^C is displayed in the terminal and the prompt is at the start of 
a new line
  - Actual: The session is terminated and the login screen is displayed

  = Original Description =

  Multiple times a day I find myself without a session after hitting
  Ctrl+C in a terminal, it seems the input falls through the
  Ubuntu/GNOME session and to gdm, which itself decides to terminate.

  Even worse, when this happens, you can briefly see your login password
  in plaintext in the virtual terminal. You can see the password however
  long you want if you stop the gdm service when this happens.

  I don't have a good way to reproduce, but it seems locking the session
  with a keyboard shortcut, subsequently unlocking it, maybe suspending,
  at some point brings this behaviour into the picture, until the
  session dies with a Ctrl+C.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug 14 15:54:34 2017
  InstallationDate: Installed on 2016-05-06 (464 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago)

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

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

[Desktop-packages] [Bug 1672716] Re: Inverted colors on screenshots

[Bug Watch Updater]

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

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

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

Title:
  Inverted colors on screenshots

Status in Gnome Screenshot:
  Confirmed
Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  screenshots made with gnome-screenshot have inverted colors - blue
  becomes yellow, red becomes blue, etc. Please, see attached file.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-screenshot 3.22.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 14 15:03:41 2017
  SourcePackage: gnome-screenshot
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (13 days ago)

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

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

[Desktop-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

[Bug Watch Updater]

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

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1688364] Re: Non existent host causes 100% cpu utilization by systemd-resolved and dnsmasq

[David Britton]

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

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

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

Title:
  Non existent host causes 100% cpu utilization by systemd-resolved and
  dnsmasq

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] googletagservices.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded googletagservices.com 
to 127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: forwarded cf.shareasimage.com to 
127.0.0.53
  May 04 13:32:07 cannon-fodder dnsmasq[8101]: query[A] cf.shareasimage.com 
from 127.0.0.1

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

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

[Desktop-packages] [Bug 1750322] Re: Tilix Background Transparency

[Jeremy Bicha]

I added block-proposed so that the new vte won't accidentally migrate
before tilix. tilix would be stuck because of the incomplete ldc
transition but vte wouldn't be.

https://people.canonical.com/~ubuntu-archive/transitions/html/ldc.html

** Tags added: block-proposed

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Tilix Background Transparency

Status in tilix package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  New

Bug description:
  Updated the system and now tilix background is 100% transparent.

  Developer Options - Pre-Release (proposed bionic) is enabled.

  Refer to this github issue that explains the cause of this issue

  https://github.com/gnunn1/tilix/issues/1257

  Budgie Desktop --version
  10.4

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

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

[Desktop-packages] [Bug 1746757] Re: [SRU] libreoffice 5.4.4 for artful

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice-l10n -
1:5.4.5-0ubuntu0.17.10.1

---
libreoffice-l10n (1:5.4.5-0ubuntu0.17.10.1) artful; urgency=medium

  * New upstream release (LP: #1748999)
- fixes CVE-2018-6871: Remote arbitrary file disclosure vulnerability via
  WEBSERVICE formula
  * debian/patches/apparmor-senddoc-fixes.patch: apparmor fixes for the
senddoc profile (LP: #1748895)

 -- Olivier Tilloy   Tue, 13 Feb 2018
11:25:01 +0100

** Changed in: libreoffice-l10n (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 5.4.4 for artful

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Artful:
  Fix Released
Status in libreoffice-l10n source package in Artful:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
     For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
   https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
  been available for users to test since 2017-12-24 in the official
  "LibreOffice Fresh" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages),
  and it is in bionic-proposed since 2018-01-26.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * Two new minor releases with a total of 134 bug fixes always carry
  the potential for introducing regressions, even though they are
  bugfix-only releases, meaning that no new features were added, and no
  existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox

[Hadrien]

Because I did not want to leak any personal data in the crash files, I
reinstalled an Ubuntu 17.10 on another hard drive to have a fresh
generic installation and did the tests there before rebooting on my
regular installation.

There are two crash files, one for gnome-shell, the other one for
XWayland. I put them in a zip file and, as it seemed big to me, I
uploaded the file on my web server:

http://mess.psydk.org/c18b_crash_firefox.zip

Other observations:
 - I tested the problem with a X11 session, and I can reproduce it.
 - I tested the problem on Ubuntu 16.04 and I could not reproduce it.
 - I've been looking at Firefox source code, it calls gtk_window_fullscreen(). 
I wrote a program to repeatedly call that function but I cannot make it freeze. 
There is some specific X11 code in Firefox though that I did not integrate in 
my test program.

Otherwise, are you able to reproduce the problem on your side? It seems
quite easy to get. I will test other Ubuntu 17.10 installations tomorrow
to get more statistics.

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

Title:
  System freeze when going back and forth fullscreen mode with Firefox

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Use Ubuntu 17.10
  Open a Wayland session
  Start Firefox
  Press F11 repeatedly
  --> The System freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-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: Thu Feb 15 20:09:27 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (135 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1741027] Re: screen sharing panels abort using an unexistant vino gsettings key

[Launchpad Bug Tracker]

** Branch linked: lp:~khurshid-alam/unity-settings-daemon/sharing-plugin

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

Title:
  screen sharing panels abort using an unexistant vino gsettings key

Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed
Status in vino package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unity-control-center.  This problem was most recently seen with package version 
15.04.0+17.10.20171225-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a 
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/.

  Specifically, the error report

   "Settings schema 'org.gnome.Vino' does not contain a key named
  'enabled' "

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

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

[Desktop-packages] [Bug 1746757] Re: [SRU] libreoffice 5.4.4 for artful

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:5.4.5-0ubuntu0.17.10.1

---
libreoffice (1:5.4.5-0ubuntu0.17.10.1) artful; urgency=medium

  * New upstream release (LP: #1748999)
- fixes CVE-2018-6871: Remote arbitrary file disclosure vulnerability via
  WEBSERVICE formula
  * debian/patches/apparmor-senddoc-fixes.patch: apparmor fixes for the
senddoc profile (LP: #1748895)

 -- Olivier Tilloy   Tue, 13 Feb 2018
11:25:01 +0100

** Changed in: libreoffice (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 5.4.4 for artful

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Artful:
  Fix Released
Status in libreoffice-l10n source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 5.4.4 is the fourth bugfix release of the still 5.4 line. 
Version 5.4.2 is currently in 17.10.
     For a list of fixed bugs compared to 5.4.2 see the list of bugs fixed in 
the RC1 and RC2 for 5.4.3 and the RC1 and RC2 for 5.4.4:
   https://wiki.documentfoundation.org/Releases/5.4.3/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.3/RC2#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.4/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.4 (RC2, which is effectively the final release) has
  been available for users to test since 2017-12-24 in the official
  "LibreOffice Fresh" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages),
  and it is in bionic-proposed since 2018-01-26.

  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. Each minor release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * Two new minor releases with a total of 134 bug fixes always carry
  the potential for introducing regressions, even though they are
  bugfix-only releases, meaning that no new features were added, and no
  existing features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***

[Launchpad Bug Tracker]

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

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

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

Title:
  audacious assert failure: *** Error in `audacious': double free or
  corruption (out): 0x7eff44005b70 ***

Status in audacious package in Ubuntu:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in libcdio package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  While trying to play an audio cd, likely a gvfs or libcdio17 issue

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: audacious 3.9-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AssertionMessage: *** Error in `audacious': double free or corruption (out): 
0x7eff44005b70 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 21:02:57 2017
  ExecutablePath: /usr/bin/audacious
  InstallationDate: Installed on 2017-12-17 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126)
  ProcCmdline: audacious
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: audacious
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7eff83be4870 "double free or 
corruption (out)", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7eff83e16c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17
  Title: audacious assert failure: *** Error in `audacious': double free or 
corruption (out): 0x7eff44005b70 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1744619] Re: Transitioning GNOME away from libnm-glib

[Jeremy Bicha]

Khurshid, any progress on unity-control-center?

I believe this issue is a problem if we want to try to land gnome-shell
3.27.91 before Feature Freeze next week.

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

Title:
  Transitioning GNOME away from libnm-glib

Status in network-manager-iodine package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in network-manager-pptp package in Ubuntu:
  New
Status in network-manager-vpnc package in Ubuntu:
  New

Bug description:
  Debian has dropped libnm-glib support from most of its VPN plugins.

  We need to cherry-pick the gnome-shell 3.26.2-4 changes for gnome-
  shell to properly interact with VPNs.

  unity-control-center will need to be ported away from libnm-glib for
  it to display VPNs.

  The only other known affected desktop is Cinnamon which has fixes
  "pending"

  Here's the Debian transition bug:
  
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-utopia-maintain...@lists.alioth.debian.org;tag=libnm

  At first look, KDE Plasma did not seem to be hurt by the libnm-glib
  support removal, but Kubuntu should probably check more closely.

  I am filing this bug to coordinate this transition and keep the VPN
  plugins in -proposed until we at least update gnome-shell.

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

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

[Desktop-packages] [Bug 1748895] Re: LO unable to find a working email configuration

[cement_head]

Still in LO 6.0.x

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

Title:
  LO unable to find a working email configuration

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

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

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

[Desktop-packages] [Bug 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

[AsciiWolf]

** Attachment added: "gnome_terminal_1.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+attachment/5059914/+files/gnome_terminal_1.png

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

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

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

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

[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***

[Launchpad Bug Tracker]

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

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

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

Title:
  audacious assert failure: *** Error in `audacious': double free or
  corruption (out): 0x7eff44005b70 ***

Status in audacious package in Ubuntu:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in libcdio package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  While trying to play an audio cd, likely a gvfs or libcdio17 issue

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: audacious 3.9-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AssertionMessage: *** Error in `audacious': double free or corruption (out): 
0x7eff44005b70 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 21:02:57 2017
  ExecutablePath: /usr/bin/audacious
  InstallationDate: Installed on 2017-12-17 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126)
  ProcCmdline: audacious
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: audacious
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7eff83be4870 "double free or 
corruption (out)", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7eff83e16c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17
  Title: audacious assert failure: *** Error in `audacious': double free or 
corruption (out): 0x7eff44005b70 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1748895] Re: LO unable to find a working email configuration

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:5.4.5-0ubuntu0.17.10.1

---
libreoffice (1:5.4.5-0ubuntu0.17.10.1) artful; urgency=medium

  * New upstream release (LP: #1748999)
- fixes CVE-2018-6871: Remote arbitrary file disclosure vulnerability via
  WEBSERVICE formula
  * debian/patches/apparmor-senddoc-fixes.patch: apparmor fixes for the
senddoc profile (LP: #1748895)

 -- Olivier Tilloy   Tue, 13 Feb 2018
11:25:01 +0100

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6871

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

Title:
  LO unable to find a working email configuration

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Installed from PPA: ppa:libreoffice/ppa

  $ lsb_release -a
  LSB Version:  
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Candidate: 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1
Version table:
   *** 1:6.0.1~rc1-0ubuntu0.16.04.1~lo1 500
  500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu xenial/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.1.6~rc2-0ubuntu1~xenial2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
   1:5.1.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  WHAT YOU EXPECT TO HAPPEN:

Should spawn an new Evolution eMAIL with attached ODF document

  WHAT HAPPENED INSTEAD:

Error Dialogue: LibreOffice is unable to find a working email
  configuration.  Please save your document locally and attached from
  within your eMAIL client.

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

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

[Desktop-packages] [Bug 1748999] Re: [SRU] libreoffice 5.4.5 for artful

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice-l10n -
1:5.4.5-0ubuntu0.17.10.1

---
libreoffice-l10n (1:5.4.5-0ubuntu0.17.10.1) artful; urgency=medium

  * New upstream release (LP: #1748999)
- fixes CVE-2018-6871: Remote arbitrary file disclosure vulnerability via
  WEBSERVICE formula
  * debian/patches/apparmor-senddoc-fixes.patch: apparmor fixes for the
senddoc profile (LP: #1748895)

 -- Olivier Tilloy   Tue, 13 Feb 2018
11:25:01 +0100

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

Title:
  [SRU] libreoffice 5.4.5 for artful

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 5.4.5 is the fifth bugfix release of the still 5.4 line. 
Version 5.4.4 is currently in artful-proposed.
 For a list of fixed bugs compared to 5.4.4 see the list of bugs fixed in 
the RC1:
   https://wiki.documentfoundation.org/Releases/5.4.5/RC1#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.5 fixes CVE-2018-6871

  [Test Case]

   * CVE-2018-6871 should be verified to be fixed

   * No other specific test case, bugs fixed upstream hopefully come
  with unit/regression tests, and the release itself is extensively
  exercised upstream (both in an automated manner and manually) by a
  community of testers. Each minor release usually goes through two
  release candidates, but 5.4.5 was initially unscheduled and it had a
  shortened cycle (only a single RC).

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 69 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1732454] Re: Reply to message composer window opens behind main evolution window

[C. S.]

Hopefully this gets fixed soon. It is very frustrating.

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

Title:
  Reply to message composer window opens behind main evolution window

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  In evolution, open a message which opens a 'message reader' window.

  In that window press the 'Reply' button - this opens a new 'message
  composer' window in which to type the reply

  In 17.10 running under gnome-shell, the composer window is opened, but
  it also seems that the main Evolution window is also brought to the
  front ... leaving the newly opened composer window behind in the
  window stack.

  Running 17.10 with the old unity does not have this problem

  So I guess this bug may be a problem with gnome-shell rather than
  evolution - something is making it ping the main application window to
  the front.

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

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

[Desktop-packages] [Bug 1748999] Re: [SRU] libreoffice 5.4.5 for artful

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:5.4.5-0ubuntu0.17.10.1

---
libreoffice (1:5.4.5-0ubuntu0.17.10.1) artful; urgency=medium

  * New upstream release (LP: #1748999)
- fixes CVE-2018-6871: Remote arbitrary file disclosure vulnerability via
  WEBSERVICE formula
  * debian/patches/apparmor-senddoc-fixes.patch: apparmor fixes for the
senddoc profile (LP: #1748895)

 -- Olivier Tilloy   Tue, 13 Feb 2018
11:25:01 +0100

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: libreoffice-l10n (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] libreoffice 5.4.5 for artful

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * LibreOffice 5.4.5 is the fifth bugfix release of the still 5.4 line. 
Version 5.4.4 is currently in artful-proposed.
 For a list of fixed bugs compared to 5.4.4 see the list of bugs fixed in 
the RC1:
   https://wiki.documentfoundation.org/Releases/5.4.5/RC1#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.5 fixes CVE-2018-6871

  [Test Case]

   * CVE-2018-6871 should be verified to be fixed

   * No other specific test case, bugs fixed upstream hopefully come
  with unit/regression tests, and the release itself is extensively
  exercised upstream (both in an automated manner and manually) by a
  community of testers. Each minor release usually goes through two
  release candidates, but 5.4.5 was initially unscheduled and it had a
  shortened cycle (only a single RC).

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  [Regression Potential]

   * A minor release with a total of 69 bug fixes always carries the
  potential for introducing regressions, even though it is a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

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

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

[Desktop-packages] [Bug 1750889] Re: GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

[AsciiWolf]

** Attachment added: "gnome_terminal_2.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1750889/+attachment/5059915/+files/gnome_terminal_2.png

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

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

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

[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***

[Launchpad Bug Tracker]

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

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

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

Title:
  audacious assert failure: *** Error in `audacious': double free or
  corruption (out): 0x7eff44005b70 ***

Status in audacious package in Ubuntu:
  Confirmed
Status in gvfs package in Ubuntu:
  Confirmed
Status in libcdio package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  While trying to play an audio cd, likely a gvfs or libcdio17 issue

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: audacious 3.9-2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu5
  Architecture: amd64
  AssertionMessage: *** Error in `audacious': double free or corruption (out): 
0x7eff44005b70 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 21:02:57 2017
  ExecutablePath: /usr/bin/audacious
  InstallationDate: Installed on 2017-12-17 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126)
  ProcCmdline: audacious
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: audacious
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7eff83be4870 "double free or 
corruption (out)", ptr=, ar_ptr=) at malloc.c:5425
   _int_free (av=0x7eff83e16c20 , p=, have_lock=0) 
at malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17
  Title: audacious assert failure: *** Error in `audacious': double free or 
corruption (out): 0x7eff44005b70 ***
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1733890] Re: Copy to clipboard not working

[MainframeX]

I can confirm that logging into Ubuntu using Xorg solves the issue for
me.

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

Title:
  Copy to clipboard not working

Status in gnome-screenshot package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Grab the whole screen with delay
  2. Press copy to clipboard
  3. Try pasting into any application like GIMP or Chrome (e.g. Github issue 
thread) using Ctrl + v

  It's not pasting any image because it doesn't seem to be in clipboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-screenshot 3.25.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 22 16:21:11 2017
  InstallationDate: Installed on 2017-11-12 (10 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (2017)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1750889] [NEW] GNOME Terminal scrollbar looks weird on clean GNOME session under Wayland

[AsciiWolf]

Public bug reported:

When using a clean GNOME session (with Adwaita theme) in combination
with Wayland, the scrollbar in GNOME Terminal looks weird (see
screenshot 1). The window also looks like it does not have a focus, but
it does. Clicking anywhere on the menu bar fixes the focus issue, but
the scrollbar still looks weird (see screenshot 2).

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

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: 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/1750889

Title:
  GNOME Terminal scrollbar looks weird on clean GNOME session under
  Wayland

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When using a clean GNOME session (with Adwaita theme) in combination
  with Wayland, the scrollbar in GNOME Terminal looks weird (see
  screenshot 1). The window also looks like it does not have a focus,
  but it does. Clicking anywhere on the menu bar fixes the focus issue,
  but the scrollbar still looks weird (see screenshot 2).

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

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