[Desktop-packages] [Bug 1611969] Re: Newlines effective in text even if --cr-wrap is not used

[Antoine BERNARD]

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

** Changed in: dialog (Debian)
   Importance: Undecided => Unknown

** Changed in: dialog (Debian)
   Status: New => Unknown

** Changed in: dialog (Debian)
 Remote watch: None => Debian Bug tracker #867536

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

Title:
  Newlines effective in text even if --cr-wrap is not used

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

Bug description:
  e.g.
  dialog --infobox "a
  b" 10 10

  a and b are in separate lines on the dialog. Manual page says:
  --cr-wrap
  Interpret  embedded  newlines  in the dialog text as a newline on the screen. 
Otherwise, dialog will only wrap lines where needed to fit inside the text box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dialog 1.3-20160209-1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Aug 10 23:49:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (263 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: dialog
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (47 days ago)

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

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

[Desktop-packages] [Bug 1611969] Re: Newlines effective in text even if --cr-wrap is not used

[Antoine BERNARD]

Bug confirmed on debian sid.

It seems to be a bug in upstream. The bug is still present in
1.3-20170509.

I made a diff based on last upstream release.

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

** Also affects: dialog (Debian)
   Importance: Undecided
   Status: New

** Patch added: "dialog_c_wrap.diff"
   
https://bugs.launchpad.net/debian/+source/dialog/+bug/1611969/+attachment/4910712/+files/dialog_c_wrap.diff

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

Title:
  Newlines effective in text even if --cr-wrap is not used

Status in dialog package in Ubuntu:
  Confirmed
Status in dialog package in Debian:
  New

Bug description:
  e.g.
  dialog --infobox "a
  b" 10 10

  a and b are in separate lines on the dialog. Manual page says:
  --cr-wrap
  Interpret  embedded  newlines  in the dialog text as a newline on the screen. 
Otherwise, dialog will only wrap lines where needed to fit inside the text box.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dialog 1.3-20160209-1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Aug 10 23:49:35 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-21 (263 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: dialog
  UpgradeStatus: Upgraded to xenial on 2016-06-24 (47 days ago)

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

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

[Desktop-packages] [Bug 1702827] [NEW] X fails to set DPI correctly

[Jerry Quinn]

Public bug reported:

I have the common problem of everything being too small when switching
to a 4K monitor.  One issue is that X is setting DPI to 96 instead of
157 for my 28" 4K monitor.

This is a Radeon RX480 and I've installed xserver-xorg-hwe.  If I run
get-edid | parse-edid, the correct display dimensions are returned
(620x340mm).  I see:

This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
No EDID on bus 1
No EDID on bus 2
No EDID on bus 3
No EDID on bus 4
No EDID on bus 5
No EDID on bus 6
No EDID on bus 7
No EDID on bus 8
No EDID on bus 9
1 potential busses found: 0
256-byte EDID successfully retrieved from i2c bus 0
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
Identifier "MP Monitor"
ModelName "MP Monitor"
VendorName "RX_"
# Monitor Manufactured week 41 of 2016
# EDID version 1.3
# Digital Display
DisplaySize 620 340
Gamma 2.20
Option "DPMS" "true"
Horizsync 23-80
VertRefresh 30-160
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1600x900, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Not giving standard mode: 1920x1080, 60Hz
#Not giving standard mode: 1920x1200, 60Hz

#Extension block found. Parsing...
#WARNING: I may have missed a mode (CEA mode 97)
#DOUBLE WARNING: It's your first mode, too, so this may actually be important.
#WARNING: I may have missed a mode (CEA mode 96)
#WARNING: I may have missed a mode (CEA mode 101)
#WARNING: I may have missed a mode (CEA mode 102)
#WARNING: I may have missed a mode (CEA mode 93)
#WARNING: I may have missed a mode (CEA mode 94)
#WARNING: I may have missed a mode (CEA mode 95)
#WARNING: I may have missed a mode (CEA mode 98)
Modeline"Mode 18" 148.50 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync -vsync 
Modeline"Mode 0" 297.00 3840 3888 3920 4400 2160 2163 2169 2250 
+hsync -vsync 
Modeline"Mode 1" 241.50 2560 2608 2640 2720 1440 1443 1449 1481 
+hsync -vsync 
Modeline"Mode 2" 148.500 1920 2008 2052 2200 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 3" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 
+hsync +vsync interlace
Modeline"Mode 4" 74.250 1280 1390 1420 1650 720 725 730 750 
+hsync +vsync
Modeline"Mode 5" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 6" 27.027 720 736 798 858 480 489 495 525 -hsync 
-vsync
Modeline"Mode 7" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 8" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 9" 25.200 640 656 752 800 480 490 492 525 -hsync 
-vsync
Modeline"Mode 10" 148.500 1920 2448 2492 2640 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 12" 74.250 1280 1720 1760 1980 720 725 730 750 
+hsync +vsync
Modeline"Mode 13" 74.250 1920 2448 2492 2640 1080 1082 1089 
1125 +hsync +vsync interlace
Modeline"Mode 14" 74.250 1920 2558 2602 2750 1080 1084 1089 
1125 +hsync +vsync
Modeline"Mode 15" 27.000 1440 1464 1590 1728 576 578 581 625 
-hsync -vsync interlace
Modeline"Mode 16" 27.000 720 732 796 864 576 581 586 625 -hsync 
-vsync
Modeline"Mode 17" 27.027 1440 1478 1602 1716 480 484 487 525 
-hsync -vsync interlace
Modeline"Mode 19" 148.50 1920 1968 2000 2640 1080 1084 1089 
1125 +hsync -vsync 
Modeline"Mode 20" 74.25 1920 2008 2052 2200 540 542 547 562 
+hsync +vsync interlace
Option "PreferredMode" "Mode 18"
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
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: Fri Jul  7 01:51:59 2017
DistUpgraded: 2016-05-31 04:27:01,635 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/580] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb]
InstallationDate: Installed on 2016-05-30 (402 days ago)
InstallationMedia: Ubuntu

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

@Lonnie: as soon as technically possible (this might be early next
week). Have you tested the packages in the PPA? Could you confirm
whether they solve the issue for you? The more confirmations we get from
individual testers, the more confidence we can have in the validity of
the patch, which means it will be delivered as an update sooner.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser package in Debian:
  Fix Released

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702821] [NEW] [Inspiron 5559, Intel ID 2809, Digital Out, HDMI] No sound at all

[mahmoud nada]

Public bug reported:

Description:Ubuntu 12.04.5 LTS
Release:12.04

N: Unable to locate package pkgname

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
Uname: Linux 3.13.0-117-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-117-generic.
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mahmoud2157 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xd222 irq 142'
   Mixer name   : 'Intel ID 2809'
   Components   : 'HDA:10ec0255,102806b2,0012 
HDA:80862809,80860101,0010'
   Controls  : 24
   Simple ctrls  : 9
Date: Fri Jul  7 07:10:47 2017
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
  x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   e 
r r o r 
  T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t e 
d
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 2157  1616  mahmoud   F pulseaudio
 /dev/snd/seq:timidity  F timidity
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Inspiron 5559, Intel ID 2809, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 0K64R6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd11/20/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn0K64R6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug precise running-unity

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

Title:
  [Inspiron 5559, Intel ID 2809, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04

  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-117.164~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-117-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-117-generic.
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mahmoud2157 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xd222 irq 142'
 Mixer name : 'Intel ID 2809'
 Components : 'HDA:10ec0255,102806b2,0012 
HDA:80862809,80860101,0010'
 Controls  : 24
 Simple ctrls  : 9
  Date: Fri Jul  7 07:10:47 2017
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_AlsaPlaybackTestStderr:
   W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   
e r r o r 
T r a n s f e r   f a i l e d :   O p e r a t i o n   n o t   p e r m i t t 
e d
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   2157  1616  mahmoud   F pulseaudio
   /dev/snd/seq:timidity  F timidity
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Inspiron 5559, Intel ID 2809, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 0K64R6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Lonnie Lee Best]

When will this patch be available via Ubuntu's normal update program?

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser package in Debian:
  Fix Released

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702819] [NEW] Chromium is Crashing on Launch

[Lonnie Lee Best]

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

Public bug reported:

On a freshly installed, and fully updated Ubuntu 16.04.2, the Chromium
browser is crashing upon launch.

I have no extensions installed, but for some reason it will launch from the 
command line with this command:
chromium-browser --disable-extensions

Others are confirming this:
https://askubuntu.com/questions/932446/chromium-crashes-in-seconds

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1289
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: Unity
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-LVDS-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wANrwAYACgSAQOAKRd4Csy1p1RFlyYWUFQBAQEBAQEBAQEBAQEBAQEBKTaAoHA4H0AwIDUAmOYQAAAY/gBOMTg0SDQtTDAxCiAg/gBDTU8KICAgICAgICAg/gBOMTg0SDQtTDAxCiAgAKA=
 modes: 1920x1080 1680x1050 1400x1050 1280x1024 1280x960 1152x864 1024x768 
800x600 640x480 720x400 640x400 640x350
DRM.card0-VGA-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
Date: Thu Jul  6 23:40:58 2017
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
 
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
DetectedPlugins:

Env:
 'None'
 'None'
InstallationDate: Installed on 2017-07-07 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Load-Avg-1min: 0.29
Load-Processes-Running-Percent:   0.2%
MachineType: Hewlett-Packard HP Pavilion dv8 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=39b29b17-07a9-405c-b8ae-0d011935bd53 ro quiet splash vt.handoff=7
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 7001
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 35.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv8 Notebook PC
dmi.product.version: 04992224121000104
dmi.sys.vendor: Hewlett-Packard
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: amd64 apport-bug xenial

** Description changed:

- On a freshly installed, and fully updated Ubuntu 16.04, the Chromium
+ On a freshly installed, and fully updated Ubuntu 16.04.2, the Chromium
  browser is crashing upon launch.
  
  I have no extensions installed, but for some reason it will launch from the 
command line with this command:
  chromium-browser --disable-extensions
  
  Others are confirming this:
  https://askubuntu.com/questions/932446/chromium-crashes-in-seconds
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1289
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: Unity
  DRM.card0-HDMI-A-1:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-LVDS-1:
-  enabled: enabled
-  dpms: On
-  status: connected
-  edid-base64: 
AP///wANrwAYACgSAQOAKRd4Csy1p1RFlyYWUFQBAQEBAQEBAQEBAQEBAQEBKTaAoHA4H0AwIDUAmOYQAAAY/gBOMTg0SDQtTDAxCiAg/gBDTU8KICAgICAgICAg/gBOMTg0SDQtTDAxCiAgAKA=
-  modes: 1920x1080 1680x1050 1400x1050 1280x1024 1280x960 1152x864 1024x768 
800x600 640x480 720x400 640x400 640x350
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wANrwAYACgSAQOAKRd4Csy1p1RFlyYWUFQBAQEBAQEBAQEBAQEBAQEBKTaAoHA4H0AwIDUAmOYQAAAY/gBOMTg0SDQtTDAxCiAg/gBDTU8KICAgICAgICAg/gBOMTg0SDQtTDAxCiAgAKA=
+  modes: 1920x1080 1680x1050 1400x1050 1280x1024 1280x960 1152x864 1024x768 
800x600 640x480 720x400 640x400 640x350
  DRM.card0-VGA-1:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  Date: Thu Jul  6 23:40:58 2017
  Desktop-Session:
-  'ubuntu'
-  '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
-  
'/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop'
+  'ubuntu'
+  '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
+  
'/usr/sh

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

@Gareth: did you try installing the dbgsym ddeb packages, as instructed
there: https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Getting_-
dbgsym.ddeb_packages ?

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser package in Debian:
  Fix Released

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

@Björn: that crash on zesty, did it have a similar backtrace?

Regarding that debian bug, the media router component extension is
indeed disabled by default on chromium, but we have a patch to re-enable
it, and it seems to work well: http://bazaar.launchpad.net/~chromium-
team/chromium-browser/xenial-stable/view/head:/debian/patches/enable-
chromecast-by-default.patch

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser package in Debian:
  Fix Released

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1576864] Re: Unable to extend to second display

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to extend to second display

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Upgrading from UbuntuStudio 15.10 to 16.04, my 2nd display is a no
  more a 1st display extension and only a clone. xrand detects only one
  display.

  $ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1400 x 1050, current 1400 x 1050, maximum 1400 x 1050
  default connected 1400x1050+0+0 0mm x 0mm
 1400x1050 77.00* 
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9644]
  $ dmesg | egrep 'drm|radeon'
  [1.293303] [drm] Initialized drm 1.1.0 20060810
  [1.328085] [drm] VGACON disable radeon kernel modesetting.
  [1.328109] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   12.801460] [drm] VGACON disable radeon kernel modesetting.
  [   12.801484] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  $ uname -r 
  4.4.0-21-lowlatency
  $ 

  Seems same than bug 1407505, but apport-bug failed, so I created a new
  bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Apr 29 23:19:49 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-21 (252 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (5 days ago)
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.380
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  LiveMediaBuild: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: xorg 1:7.7+16ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.10.0-19.21-lowlatency 4.10.8
  Tags:  zesty
  Uname: Linux 4.10.0-19-lowlatency x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1551022] Re: mouse pointer leaves trail

[Launchpad Bug Tracker]

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

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

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

Title:
  mouse pointer leaves trail

Status in xorg package in Ubuntu:
  Expired

Bug description:
  In my desktop system Kubuntu 15.10 I have the integrated graphic card
  (Intel HD3000) and a discrete graphic card (Nvidia GTX 550). Some days
  ago I attached a monitor on the iGPU and enabled it, giving me a
  triple head system (two monitors on the Nvidia and one on the Intel).
  From that moment, the mouse pointer started to leave a trail when it
  pass over something that is animating. I'm using nouveau for the
  nvidia card. I tried to upgrade to Kubuntu 16.04, but it gives me the
  same glitch.

  ---
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  BootLog:

  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: 2016-02-24 01:06:09,804 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0122] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:844d]
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
     Subsystem: ZOTAC International (MCO) Ltd. GF116 [GeForce GTX 550 Ti] 
[19da:5194]
  InstallationDate: Installed on 2015-11-19 (106 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: System manufacturer System Product Name
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic 
root=UUID=679d8ad1-4664-4abd-a80a-3ac9339425bb ro quiet splash nomdmonddf 
nomdmonisw irqnodebug vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Tags:  xenial ubuntu single-occurrence reproducible has-workaround
  Uname: Linux 4.4.0-10-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3707
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-V
  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.:bvr3707:bd07/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-V:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build1

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

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

[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Launchpad Bug Tracker]

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

** Changed in: libunity-webapps (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Expired
Status in oxide-qt package in Ubuntu:
  Expired
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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

[Desktop-packages] [Bug 1688395] Re: Remove Oxide, webbrowser-app and the Unity webapps

[Launchpad Bug Tracker]

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

** Changed in: oxide-qt (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Remove Oxide, webbrowser-app and the Unity webapps

Status in libunity-webapps package in Ubuntu:
  Expired
Status in oxide-qt package in Ubuntu:
  Expired
Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  These projects are discontinued, unsupported and should be removed.

  I haven't done any analysis of the deps or rdeps to find out if there
  is more to cull, or if there is some untangling to do.

  I know of two tasks other than removing packages -

   Unity ships an Amazon launcher in its preset favourites which
  launches a binary from unity-webapps-service. That should be removed.

   We need to keep providing the Amazon launcher by default (in GNOME
  Shell) - it should be reimplemented and added to Shell by default.

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

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

[Desktop-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Shih-Yuan Lee]

Hi, I can still reduplicate this issue on Ubuntu 16.04.
Could someone help to nominate this for xenial series?

** Changed in: oem-priority/xenial
   Importance: Undecided => Critical

** Changed in: oem-priority/xenial
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project xenial series:
  In Progress
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

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

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

[Desktop-packages] [Bug 1573563] Re: Toggling full screen mode does not work well after upgrading to Ubuntu 16.04 from 15.10

[Eggsome]

Any ETA on a fix? This is preventing me from upgrading to 16.04.
I'm happy to try any patches that need testing.

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

Title:
  Toggling full screen mode does not work well after upgrading to Ubuntu
  16.04 from 15.10

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  I use tons of terminal windows (gnome-terminal) all the time for
  various tasks. Thus, it's important for me to be able to go into full
  screen mode (F11) - if I need more attention or space and switch back
  later.

  I haven't got any problem with this in previous Ubuntu versions, after
  "switching back" from fullscreen mode, I got the terminal window at
  its original place and size. However, after upgrading to Ubuntu 16.04
  recently, if I press F11 to switch back, the terminal window is
  enlarged to cover almost the full desktop, it's not "full screen"
  anymore (that's OK), ie I can see panel, borders, etc, but still it's
  not the original size and position of the window. So I have to
  manually resize the window all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-terminal 3.18.3-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Apr 22 13:48:12 2016
  InstallationDate: Installed on 2014-05-08 (715 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to xenial on 2015-10-08 (196 days ago)

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

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

[Desktop-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Shih-Yuan Lee]

** Changed in: oem-priority
   Status: Confirmed => In Progress

** Changed in: oem-priority/xenial
   Status: Confirmed => In Progress

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project xenial series:
  In Progress
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Judson W]

I am so sick of bugs like this in Ubuntu. Every single time I upgrade I
regret it. Is this going to be available anytime this century or do I
need to learn to juggle configuration scripts?

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1701861] Re: package libreoffice-draw 1:5.1.6~rc2-0ubuntu1~xenial2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  package libreoffice-draw 1:5.1.6~rc2-0ubuntu1~xenial2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Unable to upgrade the Ubuntu

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-draw 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic i686
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  Date: Sun Jul  2 05:50:43 2017
  DuplicateSignature:
   package:libreoffice-draw:1:5.1.6~rc2-0ubuntu1~xenial2
   Setting up libreoffice-pdfimport (1:5.1.6~rc2-0ubuntu1~xenial2) ...
   dpkg: error processing package libreoffice-draw (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-02-12 (505 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libreoffice
  Title: package libreoffice-draw 1:5.1.6~rc2-0ubuntu1~xenial2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1701774] Re: package libxdmcp6:i386 1:1.1.2-1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Emily Ratliff]

** Information type changed from Private Security to Public

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

Title:
  package libxdmcp6:i386 1:1.1.2-1.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in libxdmcp package in Ubuntu:
  New

Bug description:
  hi

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libxdmcp6:i386 1:1.1.2-1.1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jul  1 05:59:09 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8192eu, 1.0, 4.8.0-56-generic, x86_64: installed
   rtl8192eu, 1.0, 4.8.0-58-generic, x86_64: installed
  DuplicateSignature:
   package:libxdmcp6:i386:1:1.1.2-1.1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libxdmcp6:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 6770] 
[1002:68ba] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Juniper XT [Radeon HD 6770] 
[1787:2312]
  InstallationDate: Installed on 2017-06-25 (5 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 7052A9G
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=67f1a498-d038-4f58-838a-cc53bd6feca0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libxdmcp
  Title: package libxdmcp6:i386 1:1.1.2-1.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT43AUS
  dmi.board.vendor: LENOVO
  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:bvnLENOVO:bvr9HKT43AUS:bd07/11/2011:svnLENOVO:pn7052A9G:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 7052A9G
  dmi.product.version: ThinkCentre M91p
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  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: Sat Jul  1 04:54:57 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1702805] [NEW] package mesa-vulkan-drivers (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is also in packa

[trevorski]

Public bug reported:

1 pip failed need a fix for in

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: mesa-vulkan-drivers (not installed)
Uname: Linux 4.12.0-999-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.5-0ubuntu5
AptOrdering:
 libllvm4.0:amd64: Install
 mesa-vulkan-drivers:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Jul  6 20:14:40 2017
DistUpgraded: 2017-07-06 15:43:27,848 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: ubuntu
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is also in package 
libgl1-mesa-glx:amd64 1:17.2~git170629170600.277621b~z~padoka0
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 520 [1028:06b2]
   Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] 
[1028:06b2]
InstallationDate: Installed on 2017-06-26 (10 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Inspiron 5559
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-999-generic 
root=UUID=7eb94c89-5679-4fb1-8a24-1cff4a7ae732 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5~beta1
SourcePackage: mesa
Title: package mesa-vulkan-drivers (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is 
also in package libgl1-mesa-glx:amd64 1:17.2~git170629170600.277621b~z~padoka0
UpgradeStatus: Upgraded to artful on 2017-07-06 (0 days ago)
dmi.bios.date: 02/08/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.8
dmi.board.name: 052K07
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.8:bd02/08/2017:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn052K07:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5559
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170704-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.81+git1706291650.4c98652~z~padoka0
version.libgl1-mesa-dri: libgl1-mesa-dri 
1:17.2~git170629170600.277621b~z~padoka0
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
1:17.2~git170629170600.277621b~z~padoka0
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.9.99+git1706291702.c9dd28c~z~padoka0
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1706102152.6babcf1~z~padoka0
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1704222053.a7c190e~z~padoka0

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


** Tags: amd64 apport-package artful regression ubuntu

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

Title:
  package mesa-vulkan-drivers (not installed) failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libvulkan_intel.so',
  which is also in package libgl1-mesa-glx:amd64
  1:17.2~git170629170600.277621b~z~padoka0

Status in mesa package in Ubuntu:
  New

Bug description:
  1 pip failed need a fix for in

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: mesa-vulkan-drivers (not installed)
  Uname: Linux 4.12.0-999-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.5-0ubuntu5
  AptOrdering:
   libllvm4.0:amd64: Install
   mesa-vulkan-drivers:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jul  6 20:14:40 2017
  DistUpgraded: 2017-07-06 15:43:27,848 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libvulkan_intel.so', which is also in package 
libgl1-mesa-glx:amd64 1:17.2~git170629170600.277621b~z~padoka0
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 520 [1028:06b2]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] 
[1028:06b2]
  InstallationDate: Installed on 2017-06-26 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCm

[Desktop-packages] [Bug 1700994] Re: Installed snaps show twice in GNOME Software

[Robert Ancell]

** Changed in: appstream-glib (Ubuntu Zesty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: appstream-glib (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: appstream-glib (Ubuntu Zesty)
   Status: New => Fix Committed

** Changed in: appstream-glib (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: gnome-software (Ubuntu Artful)
   Status: In Progress => Fix Released

** Changed in: gnome-software (Ubuntu Zesty)
   Status: New => In Progress

** Changed in: gnome-software (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  Installed snaps show twice in GNOME Software

Status in appstream-glib package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in appstream-glib source package in Xenial:
  Fix Committed
Status in gnome-software source package in Xenial:
  In Progress
Status in appstream-glib source package in Zesty:
  Fix Committed
Status in gnome-software source package in Zesty:
  In Progress
Status in appstream-glib source package in Artful:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Installed snaps show twice in GNOME Software. The solution is to not scan the 
installed .desktop files - there is sufficient information provided by snapd.

  [Test Case]
  1. Open GNOME Software
  2. Install a snap (e.g. ohmygiraffe)
  3. Switched to "Installed" tab

  Expected result:
  ohmygiraffe is shown once in the installed list.

  Observed result:
  ohmygiraffe is shown twice. One entry has data from the snap metadata, the 
other from the installed .desktop file.

  [Regression Potential]
  There is some risk of breaking other appstream behaviour. The risk is low 
because we only filter out the snapd specific directory that contains this data.

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

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

[Desktop-packages] [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

[Bruno]

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

Same here, started a few hours ago.

Hardware: Dell Latitude 5470 (i7-6820HQ)

lsb_release -a; uname -a; apt-cache policy chromium-browser

LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety
Linux brhenrique-Latitude-E5470 4.8.0-58-generic #63-Ubuntu SMP Mon Jun 26 
17:08:21 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
chromium-browser:
  Installed: 59.0.3071.109-0ubuntu0.16.10.1357
  Candidate: 59.0.3071.109-0ubuntu0.16.10.1357
  Version table:
 *** 59.0.3071.109-0ubuntu0.16.10.1357 500
500 http://br.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 53.0.2785.143-0ubuntu1.1307 500
500 http://br.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages

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

Title:
  chromium-browser crashes soon after execution - Received signal 11
  SEGV_MAPERR 0010

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  After I updated Chromium to the latest version today, it crashed as
  soon as executed.  When executed from a terminal, I got:

  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace()
  #1 0x7f5c4b92d80b 
  #2 0x7f5c4bc58390 
  #3 0x55ae23b43dc8 
  #4 0x55ae23b46656 
  #5 0x55ae23b46df9 
  #6 0x55ae23b47143 
  #7 0x7f5c4b9a8821 
  #8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask()
  #9 0x7f5c4b957e90 base::MessageLoop::RunTask()
  #10 0x7f5c4b95997d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f5c4b95a83d 
  #12 0x7f5c4b95b300 base::MessagePumpLibevent::Run()
  #13 0x7f5c4b956f15 base::MessageLoop::RunHandler()
  #14 0x7f5c4b981628 base::RunLoop::Run()
  #15 0x7f5c4b9ade36 base::Thread::ThreadMain()
  #16 0x7f5c4b9a8726 
  #17 0x7f5c4bc4e6ba start_thread
  #18 0x7f5c352fd3dd clone
r8: 002e  r9: 55ae2559a6ec r10:  r11: 
7f5c3538af50
   r12: 7f5bc6b2aff0 r13: 0008 r14: 0008 r15: 
7f5bc6b2aeb0
di:   si: 7f5bc6b2aeb0  bp: 7f5bc6b2af00  bx: 
7f5bc6b2aeb0
dx: 0067  ax:   cx: 7f5bdc1079c0  sp: 
7f5bc6b2ae60
ip: 55ae23b43dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.

  I tried complete reinstallation,  purged and removed .config/chromium.
  Same problem.  When I restored .config/chromium from an earlier
  working version, it crashed with:

  [8159:8202:0705/102433.905625:ERROR:service_manager.cc(158)] Connection 
InterfaceProviderSpec prevented service: content_plugin from binding interface: 
memory_instrumentation::mojom::Coordinator exposed by: content_browser
  A Parser-blocking, cross site (i.e. different eTLD+1) script, 
https://ssl.google-analytics.com/ga.js, is invoked via document.write. The 
network request for this script MAY be blocked by the browser in this or a 
future page load due to poor network connectivity. If blocked in this page 
load, it will be confirmed in a subsequent console message.See 
https://www.chromestatus.com/feature/5718547946799104 for more details.
  A Parser-blocking, cross site (i.e. different eTLD+1) script, 
https://ssl.google-analytics.com/ga.js, is invoked via document.write. The 
network request for this script MAY be blocked by the browser in this or a 
future page load due to poor network connectivity. If blocked in this page 
load, it will be confirmed in a subsequent console message.See 
https://www.chromestatus.com/feature/5718547946799104 for more details.
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f3a02096425 base::debug::StackTrace::StackTrace()
  #1 0x7f3a0209680b 
  #2 0x7f3a023c1390 
  #3 0x5604c6bcadc8 
  #4 0x5604c6bcd656 
  #5 0x5604c6bcddf9 
  #6 0x5604c6bce143 
  #7 0x7f3a02111821 
  #8 0x7f3a02097eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f3a020c0e90 base::MessageLoop::RunTask()
  #10 0x7f3a020c297d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f3a020c383d 
  #12 0x7f3a020c4300 base::MessagePumpLibevent::Run()
  #13 0x7f3a020bff15 base::MessageLoop::RunHandler()
  #14 0x7f3a020ea628 base::RunLoop::Run()
  #15 0x7f3a02116e36 base::Thread::ThreadMain()
  #16 0x7f3a02111726 
  #17 0x7f3a023b76ba start_thread
  #18 0x7f39eba663dd clone
r8: 002e  r9: 5604c86216ec r10:  r11: 
7f39ebaf3f50
   r12:

[Desktop-packages] [Bug 1702794] Re: Please add module-switch-on-connect to default.pa

[Daniel van Vugt]

I like the idea. It annoys me too that this isn't the default
behaviour...

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#index65h3

I'll do some testing, see if we can get it in to artful soon and xenial
later.

** Summary changed:

- Please add this to default.pa
+ Please add module-switch-on-connect to default.pa

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

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

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

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

Title:
  Please add module-switch-on-connect to default.pa

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

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

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

[Desktop-packages] [Bug 1702794] [NEW] Please add this to default.pa

[Doug McMahon]

Public bug reported:

This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
As it stands now users have to open sound settings & switch manually. It's bad 
enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

In the ### Automatically load driver modules for Bluetooth hardware
section


.ifexists module-switch-on-connect.so
load-module module-switch-on-connect
.endif

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.3
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  doug   1843 F pulseaudio
 /dev/snd/controlC0:  doug   1843 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul  6 20:02:15 2017
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

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


** Tags: amd64 apport-bug artful xenial

** Tags added: 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/1702794

Title:
  Please add this to default.pa

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This way once a user pairs & connects a bluetooth speaker device pulseaudio 
will auto switch to it. 
  As it stands now users have to open sound settings & switch manually. It's 
bad enough that auto discover & connect don't work, (can be scripted thru 
bluetoothctl), no sense adding to frustration

  In the ### Automatically load driver modules for Bluetooth hardware
  section

  
  .ifexists module-switch-on-connect.so
  load-module module-switch-on-connect
  .endif

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doug   1843 F pulseaudio
   /dev/snd/controlC0:  doug   1843 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul  6 20:02:15 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Bug Watch Updater]

** Changed in: chromium-browser (Debian)
   Status: Unknown => Fix Released

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser package in Debian:
  Fix Released

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702791] [NEW] Authentication details are not queried when connecting to WPA2 network

[Christopher M Pierce]

Public bug reported:

When selecting a WPA2 network from network-manager-applet it will
immediately try to connect without querying for authentication details.
One has to go in after the fact and edit the connection details to
finish connecting.  Arch linux, i3 window manager.

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

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

Title:
  Authentication details are not queried when connecting to WPA2 network

Status in network-manager-applet package in Ubuntu:
  New

Bug description:
  When selecting a WPA2 network from network-manager-applet it will
  immediately try to connect without querying for authentication
  details.  One has to go in after the fact and edit the connection
  details to finish connecting.  Arch linux, i3 window manager.

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

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

[Desktop-packages] [Bug 1694011] Re: GNOME Software localization is incomplete

[Jeremy Bicha]

The first language pack for artful was released today.

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

Title:
  GNOME Software localization is incomplete

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  The language localization (at least the Czech one) of GNOME Software
  is incomplete although it is fully localized in upstream. Please,
  consider syncing with the upstream pofiles.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Björn Michaelsen]

Re comment #23:
- This happened to me on both xenial and also on zesty (though it took a while 
to trigger on the later)
=> disabling media router (or clearing the profile) fixed it.

Also linking https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477 as it 
says:
   * Disable builtin media router since it only works with official Google
 Chrome builds, not chromium (closes: #833477).

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

** Also affects: chromium-browser (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833477
   Importance: Unknown
   Status: Unknown

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress
Status in chromium-browser package in Debian:
  Unknown

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Josh Fleming]

Tested chromium-fix-1702407 ppa with 
-ubuntu 16.0.4
-setting the Media Router option to default again. 
-copied over original chromium config file. 

Everything's working so far no crashes.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1694011] Re: GNOME Software localization is incomplete

[AsciiWolf]

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

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

Title:
  GNOME Software localization is incomplete

Status in gnome-software package in Ubuntu:
  Fix Released

Bug description:
  The language localization (at least the Czech one) of GNOME Software
  is incomplete although it is fully localized in upstream. Please,
  consider syncing with the upstream pofiles.

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

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

[Desktop-packages] [Bug 1702345] Re: ubuntu-wayland: login fails if nvidia drivers are installed

[Jeremy Bicha]

** Tags added: gnome-17.10 wayland

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

Title:
  ubuntu-wayland: login fails if nvidia drivers are installed

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Just loops back to greeter.
  Where is EGLStreams support?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul  4 14:21:55 2017
  InstallationDate: Installed on 2017-07-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702345] Re: ubuntu-wayland: login fails if nvidia drivers are installed

[Doug McMahon]

With gdm3 there is no option for wayland

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

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

Title:
  ubuntu-wayland: login fails if nvidia drivers are installed

Status in gdm3 package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  Just loops back to greeter.
  Where is EGLStreams support?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-session 3.24.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul  4 14:21:55 2017
  InstallationDate: Installed on 2017-07-04 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170626)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Bug Watch Updater]

** Changed in: network-manager
   Status: Unknown => Confirmed

** Changed in: network-manager
   Importance: Unknown => Medium

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.166  metric 
100
  IwConfig:
   lono wireless extensions.
   
   eth1  no wireless extensions.
   
   eth0  no wireless extensions.
  NetworkManager.state:
   [main]
   N

Re: [Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Gareth Evans]

PPA updates fix the problem for me on 16.04.2

I'm curious as to why I couldn't install the debug symbols though - can
anyone advise?

Thanks

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Sjors Gielen]

Hi Sebastien, thanks for your comment!

I've reported the bug upstream as GNOME #784636, see
https://bugzilla.gnome.org/show_bug.cgi?id=784636. I already added a
bugwatch.

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

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

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  New

Bug description:
  I've found an issue on some of our Xenial office machines, causing
  NetworkManager to drop its IP address lease in some cases when it
  shouldn't. I'm not sure if the actual bug is in NetworkManager or
  perhaps dbus or dhclient, but I'll do my best to help to figure out
  where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').



  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After this, dhclient is supposed to keep the lease fresh, which it
  does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've
  seen this DHCPACK in a tcpdump and it contains a new lease time of
  7200 seconds.

  jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 
2708 seconds.

  However, at 03:21:07 (exactly 2 hours and 1 second after the last
  lease reported by NetworkManager) Avahi and NTP report that the IP
  address is gone:

  jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 
192.168.0.166 on eth0.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.166.
  jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer 
relevant for mDNS.
  jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 
192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, 
active_time=111819 secs

  So I suspect NetworkManager dropped the IP address from the interface,
  because it wasn't informed by dhclient that the lease was renewed. The
  logs don't explicitly say this, so I may have to turn on more verbose
  debugging logs in NetworkManager or dhclient to verify this.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Wed Jun  7 14:48:59 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-11-04 (214 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  IpRoute:
   default via 192.168.0.5 dev eth0  proto static  metric 100 
   192.168.0.0/24 dev eth0  proto kernel  scope link

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Giuseppe_M]

> To everyone affected by the crash, could you please try the packages
in that PPA, and see if the crash goes away?

Done. On xenial it works fine.
Thanks Olivier! :)

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1664147] Re: Chromium on trusty too outdated; not supported by gmail

[Mikhail N]

Can you please post 
$ glxinfo | grep OpenGL 

and
$ dmesg | grep -i drm

Chromium creates multiple processes when working, and above is the crash
of the GPU sub-process. Maybe it tries to use GPU acceleration, but
fails to do ot, and the GPU is not blacklisted or you set it to ignore
the blacklist in chrome://flags

Also try dropping chrome://flags to default

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

Title:
  Chromium on trusty too outdated; not supported by gmail

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  As of Feb 13 2017, the chromium version on trusty is 53.x which is at
  least a couple of versions behind chrome-stable. Gmail displays this
  message, "This version of Chrome is no longer supported. Please
  upgrade to asupported browser." Core functionality in gmail works
  fine, but I'm not sure of security ramifications of running an old
  browser, particularly when google advises against it.

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

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

Re: [Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial

[Rohan Bayer-Fox]

That seems to have fixed the problem - Chromium is running as before the
update.

-- Original Message --
From: Olivier Tilloy 
To: rbayer...@juno.com
Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on 
xenial
Date: Thu, 06 Jul 2017 20:48:42 -

Thanks for the quick feedback Trent!
To everyone affected by the crash, could you please try the packages in that 
PPA, and see if the crash goes away?

sudo add-apt-repository -y ppa:osomon/chromium-fix-1702407
sudo apt update
sudo apt dist-upgrade

Note that packages for trusty haven't finished building yet, but should
be done soon.

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1702501).
https://bugs.launchpad.net/bugs/1702407

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

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

Police Urge Americans to Carry This With Them at All Times
The Observer
http://thirdpartyoffers.juno.com/TGL3131/595ea8dd137d28dc70eest03vuc

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702766] [NEW] Wallch/xorg abberation

[David Oxland]

Public bug reported:

Ubuntu 16.04 LTS
 Old Fresh Install
Using Wallch set to auto start and pic of the day
Ocassionally the display shows pic only as a portion with bottom portion 
grey-out as shown in attached.
Sometime the greyed out portion occupies 80% of the screen always from the 
bottom up.
Restart makes no difference
This occurance happens only occasionally, and I've caught a snapshot today
Usually wallch displays pic of the day correctly.
On boot, I do see some different activity discussing blocks occasionally b/w 
screen.(related?)
no other display aberrations appear in daily use.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
 [  OK  ] Started LSB: automatic crash report generation.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jul  6 13:35:33 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8670D] [1002:990c] 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Richland [Radeon HD 8670D] [17aa:3674]
InstallationDate: Installed on 2016-12-02 (216 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: LENOVO 10117
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=073e377f-0d1b-496e-8464-3d1b70ce67ba ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I7KT31AUS
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 STD
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT31AUS:bd11/05/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STD:cvnLENOVO:ct3:cvr:
dmi.product.name: 10117
dmi.product.version: Lenovo H535
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
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: Thu Jul  6 12:41:37 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Attachment added: "Wallch display"
   
https://bugs.launchpad.net/bugs/1702766/+attachment/4910451/+files/Screenshot%20from%202017-07-06%2013-49-54.png

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

Title:
  Wallch/xorg abberation

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 LTS
   Old Fresh Install
  Using Wallch set to auto start and pic of the day
  Ocassionally the display shows pic only as a portion with bottom portion 
grey-out as shown in attached.
  Sometime the greyed out portion occupies 80% of the screen always from the 
bottom up.
  Restart makes no difference
  This occurance happens only occasionally, and I've caught a snapshot today
  Usually wallch displays pic of the day correctly.
  On boot, I do see some different activity discussing blocks occasionally b/w 
screen.(related?)
  no other display aberrations appear in daily use.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
   [  OK  ] Started LSB: automatic crash report generation.
  CompizPlugins: No value

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

Thanks for the quick feedback Trent!
To everyone affected by the crash, could you please try the packages in that 
PPA, and see if the crash goes away?

sudo add-apt-repository -y ppa:osomon/chromium-fix-1702407
sudo apt update
sudo apt dist-upgrade

Note that packages for trusty haven't finished building yet, but should
be done soon.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702759] [NEW] Evolution is not translated

[Francois Thirioux]

Public bug reported:

In Artful, since last langpack update, GS is well translated (in French)
but Evolution is not, even after complete reboot.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution 3.24.3-0ubuntu2
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jul  6 22:23:22 2017
InstallationDate: Installed on 2016-12-12 (206 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: Upgraded to artful on 2017-05-04 (63 days ago)

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


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

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1702759/+attachment/4910436/+files/JournalErrors.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1702759/+attachment/4910437/+files/ProcCpuinfoMinimal.txt

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

Title:
  Evolution is not translated

Status in evolution package in Ubuntu:
  New

Bug description:
  In Artful, since last langpack update, GS is well translated (in
  French) but Evolution is not, even after complete reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution 3.24.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jul  6 22:23:22 2017
  InstallationDate: Installed on 2016-12-12 (206 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20161211)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: Upgraded to artful on 2017-05-04 (63 days ago)

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

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

[Desktop-packages] [Bug 1175914] Re: Sound Settings is showing HDMI audio settings for internal speakers after HDMI cable is removed

[Jamie Nguyen]

Still seeing this on 16.04 LTS as well -- the sound settings menu does
not clean up HDMI sound sources that have been removed.

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

Title:
  Sound Settings is showing HDMI audio settings for internal speakers
  after HDMI cable is removed

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

Bug description:
  Ubuntu 12.04.2 precise

  Steps:
  1. Plug the HDMI cable to the laptop, and open the Sound Settings
  2. Switch the output device form built-in speakers to HDMI output
  3. Close the Sound Settings and play sound, make sure it's coming from the 
HDMI device
  4. Unplug the HDMI cable, play sound again.

  Expected Results:
  It should be played through the built-in speaker on the laptop.

  Actual Results:
  Nothing happened, and if you open the Sound Settings, the HDMI device is 
removed from the devices list, but still can be seen in the "Setting for 
Speakers" part on the right-hand-side (please find attachment for screen shot)
  You have select the internal speaker manually to make it back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.9
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Thu May  2 23:53:00 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu3
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: gnome-control-center 1:3.4.2-0ubuntu0.9
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Tags:  precise running-unity
  Uname: Linux 3.5.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu3
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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

[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing

[Max Gaukler]

Sorry, but the new one also works for me on Debian stretch. (0.92+devel 
trunk-61-gcd5a5eac59 2017-07-02)
Also with the very latest (Inkscape 0.92+devel trunk-90-g42bf908b41 2017-07-06) 
from a few minutes ago  (Take care, they changed some dependencies: I needed to 
install libsoup2.4-dev, remove the whole build folder and run cmake again, so 
that it finally compiled)

Could you try to tracking this down further, by finding out which commit
broke it (git bisect), and additionally by getting a backtrace at where
it gets stuck?

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

Title:
  PDF+Latex export creates multipage pdf, pages missing

Status in Inkscape:
  Fix Committed
Status in inkscape package in Ubuntu:
  Confirmed
Status in inkscape package in Debian:
  Confirmed

Bug description:
  In 0.91 the z-order information in svg is used to create multipage
  PDF+LaTeX documents as per bug 771957. However, for the SVGs I have
  been converting to PDF+LaTeX in this way, the TeX-file instructs to
  load more pages than the PDF has, for example the PDF has only three
  pages and the TeX file also includes page=4. This basically breaks the
  PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf
  package.

  The bug occurs on OpenSuse 13.1 and Windows 8.1.

  Attached a zip file with two svg files and their broken PDF+LaTeX
  counterparts.

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

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

[Desktop-packages] [Bug 550225] Re: desktopcouch-service crashed with SIGSEGV in dbus_message_get_reply_serial()

[Colin Watson]

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

** Attachment removed: "BD177261A81EB4753F71D5AF7A5B5CA4.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/550225/+attachment/4910425/+files/BD177261A81EB4753F71D5AF7A5B5CA4.jpg

** Attachment removed: "DF570B9AB50135BBD27A18D0D2CBD04E.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/550225/+attachment/4902512/+files/DF570B9AB50135BBD27A18D0D2CBD04E.jpg

** Attachment removed: "E77141110CB5AE431FF2A0BA4E5B6AD8.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/550225/+attachment/4897164/+files/E77141110CB5AE431FF2A0BA4E5B6AD8.jpg

** Attachment removed: "7B4809C1F1ED29DA07249665B3EB1AA3.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/550225/+attachment/4883837/+files/7B4809C1F1ED29DA07249665B3EB1AA3.jpg

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

Title:
  desktopcouch-service crashed with SIGSEGV in
  dbus_message_get_reply_serial()

Status in desktopcouch package in Ubuntu:
  New

Bug description:
  Binary package hint: desktopcouch

  Happens after Boot my Lucid Lynx Beta 1 Kernel 2.6.32.17. Everything seems to 
work.
  Hope this can help your troubleshhoting

  ProblemType: Crash
  DistroRelease: Ubuntu 10.04
  Package: desktopcouch 0.6.3-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-17-generic i686
  Architecture: i386
  CrashCounter: 1
  Date: Sun Mar 28 14:25:47 2010
  ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 
(20091020.3)
  InterpreterPath: /usr/bin/python2.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
  ProcEnviron:
   SHELL=/bin/bash
   LANG=it_IT.utf8
  SegvAnalysis:
   Segfault happened at: 0x4cce5c:  mov(%edx,%eax,1),%eax
   PC (0x004cce5c) ok
   source "(%edx,%eax,1)" (0x00a6) not located in a known VMA region 
(needed readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: desktopcouch
  StacktraceTop:
   ?? () from /lib/libdbus-1.so.3
   ?? () from /lib/libdbus-1.so.3
   dbus_message_get_reply_serial () from /lib/libdbus-1.so.3
   ?? () from /lib/libdbus-1.so.3
   ?? () from /lib/libdbus-1.so.3
  Title: desktopcouch-service crashed with SIGSEGV in 
dbus_message_get_reply_serial()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Trent Nelson]

Test builds seem to work here!  Casting didn't even break :)

Thanks Olivier!

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702351] Re: User installation could not be completed

[modolo]

To make everything more complicated ...

I found a parameter in the config of the sssd service that allows
replacing whitespace with another character:

[sssd]
...
override_space = _

As a result, my primary group changed to domain_users. Unfortunately,
the error persists!

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

Title:
  User installation could not be completed

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1702736] [NEW] package libgoogle-glog0v5 0.3.4-0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

[Steven Hoffer]

Public bug reported:

Applying OS updates never completed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgoogle-glog0v5 0.3.4-0.1
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
AptOrdering:
 nautilus: Install
 libgoogle-glog0v5: Configure
 nautilus: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Jul  6 14:43:36 2017
DuplicateSignature:
 package:libgoogle-glog0v5:0.3.4-0.1
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package libgoogle-glog0v5 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-05-19 (48 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: google-glog
Title: package libgoogle-glog0v5 0.3.4-0.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: google-glog (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package libgoogle-glog0v5 0.3.4-0.1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in google-glog package in Ubuntu:
  New

Bug description:
  Applying OS updates never completed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgoogle-glog0v5 0.3.4-0.1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.6
  AptOrdering:
   nautilus: Install
   libgoogle-glog0v5: Configure
   nautilus: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Jul  6 14:43:36 2017
  DuplicateSignature:
   package:libgoogle-glog0v5:0.3.4-0.1
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package libgoogle-glog0v5 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-19 (48 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: google-glog
  Title: package libgoogle-glog0v5 0.3.4-0.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702722] Re: Night Light transition is too abrupt

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-desktop/gnome-settings-daemon/ubuntu

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

Title:
  Night Light transition is too abrupt

Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  ==
  Due to a logic error, the Night Light transition is a lot more abrupt than 
the gradual transition that was intended. This has been fixed in the gnome-3-24 
git branch.

  Night Light is a new feature in GNOME 3.24 (Ubuntu 17.04) to redden
  the display during night hours.

  Test Case
  =

  Regression Potential
  

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

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

[Desktop-packages] [Bug 1702722] [NEW] Night Light transition is too abrupt

[Jeremy Bicha]

Public bug reported:

Impact
==
Due to a logic error, the Night Light transition is a lot more abrupt than the 
gradual transition that was intended. This has been fixed in the gnome-3-24 git 
branch.

Night Light is a new feature in GNOME 3.24 (Ubuntu 17.04) to redden the
display during night hours.

Test Case
=

Regression Potential


** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Low
 Status: Fix Committed

** Affects: gnome-settings-daemon (Ubuntu Zesty)
 Importance: Low
 Status: Triaged


** Tags: zesty

** Also affects: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Importance: Undecided => Low

** Changed in: gnome-settings-daemon (Ubuntu Zesty)
   Status: New => Triaged

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

Title:
  Night Light transition is too abrupt

Status in gnome-settings-daemon package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon source package in Zesty:
  Triaged

Bug description:
  Impact
  ==
  Due to a logic error, the Night Light transition is a lot more abrupt than 
the gradual transition that was intended. This has been fixed in the gnome-3-24 
git branch.

  Night Light is a new feature in GNOME 3.24 (Ubuntu 17.04) to redden
  the display during night hours.

  Test Case
  =

  Regression Potential
  

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

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

[Desktop-packages] [Bug 1701757] Re: 17.04 (Zesty) does not source ~/.profile for umask

[Greg Williams]

Ubuntu bug 1685754 seems specific to gnome-terminal. The bug I reported
is for all gnome-session apps. Gnome-terminal can be made to work if a
umask is added to .bashrc. This is not the case for other gnome apps
like gedit. These bugs may be the same, but I don't know enough to be
able to make that call.

I don't know for sure, but is this gnome bug might be related:
https://bugzilla.gnome.org/show_bug.cgi?id=780622


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

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

Title:
  17.04 (Zesty) does not source ~/.profile for umask

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I have always set umask at ~/.profile and gnome-session would source
  this. But in Zesty, this isn't happening, and I can find no way to set
  a umask default of my choosing for the gnome-session.

  Creating a document using gedit always produces the default
  (unchangeable) permission represented by umask 022.

  If I adjust umask at ~/.bashrc, creating a document in nano or vi
  works to get a different umask. But Ubuntu users should be able to
  adjust umask for GTK3 apps (like gedit) as well.

  If there is a new way to set ~/.profile variables, the documentation
  needs to be updated to reflect this so people know how to set them.

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

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

[Desktop-packages] [Bug 397892] Re: Screensaver does not turn on [Ubuntu / Xubuntu Karmic]

[Colin Watson]

** Attachment removed: "E9A698DB5D46F3F86E841079FAD1A8D5.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/397892/+attachment/4901875/+files/E9A698DB5D46F3F86E841079FAD1A8D5.jpg

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

Title:
  Screensaver does not turn on [Ubuntu / Xubuntu Karmic]

Status in Xubuntu:
  Invalid
Status in gnome-screensaver package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-screensaver

  RELEASE:  Karmic Koala
  CD/DVD VARIANT:  64bit Xubuntu installed fresh using ext4 and grub2
  ISO BUILD:  
  SYMPTOMS:  Using Applications -> Settings -> Screensaver to set the 
screensaver preferences has no effect. The screensaver is set to start in 10 
minutes. Unfortunately, it never activates.

  Run in terminal gives me:
  charlie@wecan:~$ gnome-screensaver-preferences
  ** (gnome-screensaver-preferences:6402): DEBUG: Found best visual for GL: 0x21

  There are no entries in ~/.xsession-errors log and no entries in any
  system log that I can find looking in /var/log.

  gnome-screensaver:
Installed: 2.27.0-0ubuntu3
Candidate: 2.27.0-0ubuntu3
Version table:
   *** 2.27.0-0ubuntu3 0
  500 http://us.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/xubuntu-desktop/+bug/397892/+subscriptions

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Bug Watch Updater]

** Changed in: mutter
   Status: Unknown => Confirmed

** Changed in: mutter
   Importance: Unknown => Medium

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

Packages with a tentative fix are currently building in
https://launchpad.net/~osomon/+archive/ubuntu/chromium-
fix-1702407/+packages. Once built (in a few hours), that should allow
people affected by the crash to test the fix.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702351] Re: User installation could not be completed

[modolo]

Libreoffice works very well from repositories!

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

Title:
  User installation could not be completed

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Alexandre]

I only use chromium to run signal and since the last update, on
59.0.3071.109-0u, if I start it without extensions and then with the
app-id:

chromium-browser --disable-extensions && \
/usr/bin/chromium-browser --profile-directory=Default 
--app-id=bikioccmkafdpakkkcpdbppfkghcmihk

it does run for a few minutes before crashing in the same way...
Maybe it can help someone debug it!

(16.04.2 with mainline 4.9.35)

Cheers.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Andrew Teal]

Ouch! I have been known to boast about my proofreading skills ...
confirmed that #19 does in fact work, thanks.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages

[Henrietta Forssen]

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

Happening to me too, please fix asap! Thanks

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

Title:
  GNOME Software does not install third-party .deb packages

Status in gdebi:
  New
Status in GNOME Software:
  New
Status in GRadio:
  New
Status in SoundConverter:
  New
Status in Ubuntu GNOME:
  Triaged
Status in Ubuntu Studio:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 16.04 LTS (clean install). 64-bit. Final release.
  Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
    Version table:
   *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
  500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I intended to install MEGA Sync Client, Google Chrome and Dropbox by
  downloading the needed packages from their websites (respectively
  https://mega.nz/#sync and https://www.google.com/chrome/ and
  https://www.dropbox.com/install?os=lnx ). I opened the packages one by
  one with gnome-software and pressed Install - nothing, except for a
  super-quick progress bar animation, happened. No matter how many times
  I tried, same result. Also, an icon pops up on the panel saying
  "Waiting to install", but nothing seems to happen.

  This only seems to happen with third-party packages; installing a
  random deb from packages.ubuntu.com/xenial worked.

  I even tried to reinstall the system to make this work, but same
  problem.

  Gdebi, however, installs the packages as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 21:01:52 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nn_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Trent Nelson]

Andrew,

Try the workaround in #19.

Note: --disable-extensions with an S, not --disable-extension.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

** Changed in: chromium-browser (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Andrew Teal]

Linux Mint 17.2 Rafaela "Ubuntu" VERSION="14.04.2 LTS, Trusty Tahr"

The upgrade to 59.0.3071.109 stopped chrome from starting;

Purging, etc. had no effect; likewise turning off wi-fi; also:

andrew@andrew-desktop ~/.config $ chromium-browser --disable-extension
Using PPAPI flash.
 --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
Received signal 11 SEGV_MAPERR 0008
#0 0xb4afd23f base::debug::StackTrace::StackTrace()
#1 0xb4afca63 base::debug::StackTrace::StackTrace()
#2 0xb4afd717 
#3 0xb4c58d38 ([vdso]+0xd37)
#4 0xb5150ff6 
#5 0xb515284b 
#6 0xb5152f56 
#7 0xb515356b 
#8 0xb514c4d2 
#9 0xb4b7e8e3 
#10 0xb4b7e8a2 
#11 0xb4afe8b7 base::debug::TaskAnnotator::RunTask()
#12 0xb4b2a18f base::MessageLoop::RunTask()
#13 0xb4b2ba14 base::MessageLoop::DeferOrRunPendingTask()
#14 0xb4b2c90b base::MessageLoop::DoWork()
#15 0xb4b2d53d base::MessagePumpLibevent::Run()
#16 0xb4b29d9f base::MessageLoop::RunHandler()
#17 0xb4b55e76 base::RunLoop::Run()
#18 0xb4b83f7b base::Thread::Run()
#19 0xb4b8405f base::Thread::ThreadMain()
#20 0xb4b7e79a 
#21 0xb4c27f72 start_thread
#22 0xadf3b3ee clone
  gs: 0033  fs:   es: 007b  ds: 007b
 edi: 94659938 esi: 946599c4 ebp: 94659968 esp: 946598b0
 ebx: b78f5ba8 edx:  ecx: 8e8892e8 eax: 
 trp: 000e err: 0004  ip: b5150ff6  cs: 0073
 efl: 00210282 usp: 946598b0  ss: 007b
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Can I help any other way?

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  In Progress

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend

[Joseph Salisbury]

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

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

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

Title:
  Mounted sshfs filesystems sometimes prevent suspend

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in sshfs-fuse package in Ubuntu:
  New

Bug description:
  Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30
  and sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against
  a file on an sshfs filesystem.

  Sometimes when I suspend I get:

  Jul  4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ... done.
  Jul  4 20:59:08 xps kernel: [46684.613278] PM: Preparing system for sleep 
(mem)
  Jul  4 20:59:08 xps kernel: [46684.613788] Freezing user space processes ... 
  Jul  4 20:59:08 xps kernel: [46704.620140] Freezing of tasks failed after 
20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
  Jul  4 20:59:08 xps kernel: [46704.620534] gvimD0 11155   
1336 0x0004
  Jul  4 20:59:08 xps kernel: [46704.620541] Call Trace:
  Jul  4 20:59:08 xps kernel: [46704.620556]  __schedule+0x233/0x6f0
  ...
  Jul  4 20:59:08 xps kernel: [46704.620679]  
entry_SYSCALL_64_fastpath+0x1e/0xad
  ...
  Jul  4 20:59:08 xps kernel: [46704.620711] Restarting tasks ... done.

  ...and the system fails to suspend.

  AFAICT, this is https://bugzilla.redhat.com/show_bug.cgi?id=656992 and
  https://lists.debian.org/debian-kernel/2011/10/msg00412.html has an
  extensive explanation. The corresponding Debian bug was closed long
  ago due to inactivity. It isn't exactly bug 388419 though since that
  is about behaviour after resume, rather than failure to suspend.

  This affects sshfs-fuse, but it sounds like a full fix would be in the
  kernel. I wonder if it's possible to work around in userspace
  packaging in sshfs-fuse, though, by arranging some action in userspace
  before suspend?

  It seems unlikely that this will be addressed any time soon, but it'd be nice 
to keep a bug open in Launchpad so that users can have a single rallying point.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  1519 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc
  InstallationDate: Installed on 2017-05-11 (54 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: sshfs-fuse
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  Tags:  artful
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 00GCYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

If I understand correctly 
https://bugs.chromium.org/p/chromium/issues/detail?id=409318 and if that 
information is still current, packages built with clang are not affected. Which 
would explain why all the reports affect xenial and trusty (haven't been 
getting reports for yakkety, but assuming not many people run it, as it will be 
EOL in 2 weeks). That would also explain why chrome is not affected, only 
chromium-browser.
I'll give a go at patching networking_private_linux.cc and building packages in 
a PPA so people affected by the crash can try it out.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1683460] Re: cannot save several times a scan

[jack.herbert]

so it would be more of a feature request than a bug, but could we have a "save 
as" button next to "save"?
The minimal interface is nice but I was scanning three photos at a time with a 
flatbed, and couldn't save each picture separately. Never thought of looking 
into the application menu and ended up downloading xsane and cropping with gimp.

Thinking about it now, even better than a "save as" button would be to
simply have a dialogue with the usual "This file already exists, wadya
wanna do? replace/new/cancel" when pressing save a second time.

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

Title:
  cannot save several times a scan

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  I wanted to save the same scan in png and pdf but the save button kept
  insensitive after the first save even after rotating a page hoping to
  trigger an unsaved status.

  version: 3.24.0

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

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

[Desktop-packages] [Bug 1702351] Re: User installation could not be completed

[Olivier Tilloy]

Thanks for the feedback Marcelo. Does libreoffice from the ubuntu
repositories (not the snap package) work well in that setup?

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

Title:
  User installation could not be completed

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1702351] Re: User installation could not be completed

[modolo]

Hi!

I have a lot of snaps!

modolo@gsat019046:~$ snap list
Name  Version  Rev   Developer  Notes
core  16-2 2312  canonical  -
emoj  0.3.01 popey  -
hello-world   6.3  27canonical  -
libreoffice   5.3.4.2  21canonical  -
ohmygiraffe   1.1.0a   3 popey  -
planetlander  1.0  2 fernando-j-scherf  -
termius-app   1.0.86 crystalnix -

Apparently, the problem is only with libreoffice!
I've attached an image of the emoj snap working!

This problem with libreoffice is already old, I already posted this bug
for some time but did not get an answer.

Thanks,
Marcelo Módolo

** Attachment added: "snap emoj"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1702351/+attachment/4910368/+files/Captura%20de%20tela%20de%202017-07-06%2010-48-12.png

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

Title:
  User installation could not be completed

Status in libreoffice package in Ubuntu:
  Incomplete

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 106621] Re: GNOME Trash doesn't show deleted files on other partitions (ecryptfs / encfs / Private / ntfs-3g)

[Julien Olivier]

Sorry, I'm lost here: I still see the bug in Nautilus 3.20.4. Is it
supposed to be fixed ?

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

Title:
  GNOME Trash doesn't show deleted files on other partitions (ecryptfs /
  encfs / Private / ntfs-3g)

Status in GnomeVFS:
  Fix Released
Status in gvfs:
  Fix Released
Status in Nautilus:
  Invalid
Status in ecryptfs-utils package in Ubuntu:
  Won't Fix
Status in gnome-vfs2 package in Ubuntu:
  Invalid
Status in gvfs package in Ubuntu:
  Triaged
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  If I remove files from FUSE partitions with Nautilus they are moved to
  .Trash-$USER on the FUSE partition but they aren't shown in Trash so
  the only solution to free space is to remove the trash directory.

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

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

[Desktop-packages] [Bug 1179062] Re: OpenVPN: Buggy config dialog for "Password with Certificates (TLS)" authentication

[Launchpad Bug Tracker]

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

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

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

Title:
  OpenVPN: Buggy config dialog for "Password with Certificates (TLS)"
  authentication

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For an OpenVPN connection, the "VPN" tab of the configuration dialog
  is buggy when choosing "Password with Certificates (TLS)"
  authentication. Choosing a certificate file for one of the three
  User|CA|Private sometimes clears, sometimes sets the entries for the
  two other certificates that are not affected. Also, a passphrase for
  the private key is mandatory but shouldn't be.

  Another option is to use one single PKCS#12 certificate (--pkcs12
  switch for /usr/sbin/openvpn). It took me two hours to figure out that
  the .p12 file I was given actually can be converted to three .pem
  files using these commands:

  openssl pkcs12 -nocerts -in YOUR_CERT.p12 -out userkey.pem
  openssl pkcs12 -nokeys -clcerts -in YOUR_CERT.p12 -out usercert.pem
  openssl pkcs12 -nokeys -cacerts -in YOUR_CERT.p12 -out userca.pem

  (taken from http://blog.stracca.net/?p=73). It would be very, very
  helpful to have at least a note with a helpful link in the dialog
  concerning PKCS#12 certificates, or, at best, if the GUI supported
  this type of certificate right away (perhaps through yet another
  authentication type "Password with Certificates (TLS) with PKCS#12
  key").

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Trent Nelson]

Rohan,

Confirmed.  I did have to interact with the cast extension after
enabling wifi to get it to crash though.  It may have just been
coincidence though (wireless network list was probably cached).

I also tried plugging and unplugging the ethernet cable with wifi off,
which did not seem to trigger the crash (not unsurprising given the
above stacktrace and patch).

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702684] [NEW] Xorg freeze

[Rohith Belur Ravish]

Public bug reported:

Display freezes very frequently and have to hard start every time. I
have checked if the graphics driver exists and it is fine. Its a new
laptop with NVIDIA geforce GTX 1050 card. Please help fix this problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
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: Thu Jul  6 14:42:33 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:651a]
   Subsystem: CLEVO/KAPOK Computer Device [1558:651a]
InstallationDate: Installed on 2017-06-28 (8 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Notebook W65KJ1_KK1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic 
root=UUID=7b6d5d19-08f6-4b44-9f83-8fdeabaebba5 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.05
dmi.board.asset.tag: Tag 12345
dmi.board.name: W65KJ1_KK1
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.05:bd03/10/2017:svnNotebook:pnW65KJ1_KK1:pvrW65KJ1_KK1:rvnNotebook:rnW65KJ1_KK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: W65KJ1_KK1
dmi.product.version: W65KJ1_KK1
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jul  6 14:14:48 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Display freezes very frequently and have to hard start every time. I
  have checked if the graphics driver exists and it is fine. Its a new
  laptop with NVIDIA geforce GTX 1050 card. Please help fix this
  problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  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: Thu Jul  6 14:42:33 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:5912] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:651a]
 Subsystem: CLEVO/KAPOK Computer Device [1558:651a]
  InstallationDate: Installed on 2017-06-28 (8 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Notebook W65KJ1_KK1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Dimitri John Ledkov]

Also note artful has 1.8.0, thus this fix may be included there already,
or e.g. will only need a simple git cherry-pick of the upstream 1.8
branch fix.

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Dimitri John Ledkov]

@ Nicholas Stommel (nstommel)

Could you please help to update the bug description SRU template to fix this 
issue in 17.04?
I do not fully understand the issue at hand, but I do have access to VPN and 
can set VPN setting in Netowrk Manager to route all traffic through VPN. After 
doing that, I should check dns-leak website?! to make sure all responses come 
from the VPN's DNS server rather than my ISP/public DNS servers? A write up of 
easy steps would be nice like:
1) check dns leak website, record dns servers
2) connect to vpn
3) check dns leak website again

expected: servers in #3 should be behind vpn, and different from public
dns servers listed in #1. Or some such.

Would you be able to distill testcase steps into easy steps that anybody
with a VPN connection setup via network manager can reproduce? This way
we will be able to validate this issue and release a stable release
update.

** Description changed:

+ [Impact]
+ 
+  * NetworkManager incorrectly handles dns-priority of the VPN-like
+ connections, which leads to leaking DNS queries outside of the VPN into
+ the general internet.
+ 
+  * Upstream has resolved this issue in master and 1.8 to correctly
+ configure any dns backends with negative dns-priority settings.
+ 
+ [Test Case]
+ 
+ #FIXME#
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ #FIXME#
+ 
+ [Regression Potential]
+ 
+  * If this issue is changed DNS resolution will change, for certain
+ queries, to go via VPN rather than general internet. And therefore, one
+ may get new/different results or even loose access to resolve/access
+ certain parts of the interent depending on what the DNS server on VPN
+ chooses to respond to.
+ 
+ [Other Info]
+  
+  * Original bug report
+ 
  I use a VPN configured with network-manager-openconnect-gnome in which a
  split-horizon DNS setup assigns different addresses to some names inside
  the remote network than the addresses seen for those names from outside
  the remote network.  However, systemd-resolved often decides to ignore
  the VPN’s DNS servers and use the local network’s DNS servers to resolve
  names (whether in the remote domain or not), breaking the split-horizon
  DNS.
  
  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

[Desktop-packages] [Bug 1661590] Re: GNOME Software only supports running one application from a snap

[Bug Watch Updater]

** Changed in: gnome-software
   Status: Unknown => Fix Released

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

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

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

[Desktop-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Dimitri John Ledkov]

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Artful)

** Project changed: systemd => network-manager

** Changed in: network-manager
   Importance: Undecided => Unknown

** Changed in: network-manager
   Status: New => Unknown

** Changed in: network-manager
 Remote watch: None => GNOME Bug Tracker #783569

** Also affects: network-manager (Ubuntu Zesty)
   Importance: Undecided
   Status: New

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

Title:
  systemd-resolved breaks VPN with split-horizon DNS

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Zesty:
  Confirmed
Status in network-manager source package in Artful:
  Confirmed

Bug description:
  [Impact]

   * NetworkManager incorrectly handles dns-priority of the VPN-like
  connections, which leads to leaking DNS queries outside of the VPN
  into the general internet.

   * Upstream has resolved this issue in master and 1.8 to correctly
  configure any dns backends with negative dns-priority settings.

  [Test Case]

  #FIXME#

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  #FIXME#

  [Regression Potential]

   * If this issue is changed DNS resolution will change, for certain
  queries, to go via VPN rather than general internet. And therefore,
  one may get new/different results or even loose access to
  resolve/access certain parts of the interent depending on what the DNS
  server on VPN chooses to respond to.

  [Other Info]
   
   * Original bug report

  I use a VPN configured with network-manager-openconnect-gnome in which
  a split-horizon DNS setup assigns different addresses to some names
  inside the remote network than the addresses seen for those names from
  outside the remote network.  However, systemd-resolved often decides
  to ignore the VPN’s DNS servers and use the local network’s DNS
  servers to resolve names (whether in the remote domain or not),
  breaking the split-horizon DNS.

  This related bug, reported by Lennart Poettering himself, was closed with the 
current Fedora release at the time reaching EOL:
  https://bugzilla.redhat.com/show_bug.cgi?id=1151544

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

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

Re: [Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

[carlos roberto alves benevides]

Dear Sir. Mac Abdul,


This issue was solved as per previous instructions and correct way to install 
the program. Thanks all team involved for their efforts and results to provide 
a quick answer.


De: boun...@canonical.com  em nome de Mac Abdul 
<1688...@bugs.launchpad.net>
Enviado: quinta-feira, 6 de julho de 2017 08:45:19
Para: carlosbenevid...@hotmail.com
Assunto: Re: [Bug 1688721] Re: Packages that trigger multiple debconf prompts 
fail to install

Whenever i try  to install any appliacation i have face this problem ?
Note : See the screenshot

On Fri, Jun 30, 2017 at 1:06 AM, Launchpad Bug Tracker <
1688...@bugs.launchpad.net> wrote:

> This bug was fixed in the package gnome-software -
> 3.22.7-0ubuntu3.17.04.5
>
> ---
> gnome-software (3.22.7-0ubuntu3.17.04.5) zesty; urgency=medium
>
>   * debian/patches/0001-snap-Fix-icons-not-being-converted-to-
> pixbufs.patch:
> - Fix snaps without icons not showing reliably (LP: #1697565)
>   * debian/patches/0001-snap-Backport-fixes-from-master.patch:
> - Show featured snaps (LP: #1663097)
>   * debian/patches/0017-Use-snap-name-field-for-app-name.patch:
> - Dropped, merged into above patch
>
> gnome-software (3.22.7-0ubuntu3.17.04.4) zesty; urgency=medium
>
>   * debian/patches/0006-Add-an-APT-plugin.patch:
> - Handle multiple debconf connections (LP: #1688721)
>   * debian/patches/0018-Limit-search-entry-to-100-characters.patch:
> - Limit search entry in case of accidental input (LP: #1692398)
>
> gnome-software (3.22.7-0ubuntu3.17.04.3) zesty; urgency=medium
>
>   * debian/patches/0002-Add-an-APT-plugin.patch:
> - Fix crash when debconf socket fails (LP: #1689425)
>
>  -- Robert Ancell   Fri, 16 Jun 2017
> 13:42:12 +1200
>
> ** Changed in: gnome-software (Ubuntu Zesty)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1694521).
> https://bugs.launchpad.net/bugs/1688721
>
> Title:
>   Packages that trigger multiple debconf prompts fail to install
>
> Status in gnome-software package in Ubuntu:
>   Fix Released
> Status in gnome-software source package in Xenial:
>   Fix Released
> Status in gnome-software source package in Yakkety:
>   Fix Released
> Status in gnome-software source package in Zesty:
>   Fix Released
> Status in gnome-software source package in Artful:
>   Fix Released
>
> Bug description:
>   [Impact]
>   Some packages stall on installing. These are packages that generate
> multiple debconf prompts (the prompts may be empty and so not user visible,
> e.g. gconf2-common).
>
>   [Test Case]
>   1. Remove gconf2-common (warning, may uninstall packages like
> gnome-terminal):
>   $ sudo apt purge gconf2-common
>   2. Download the debian package of Chrome from 
> www.google.com/chrome.
>   3. Install the package (browser will prompt, or double click on package
> in Nautilus).
>
>   Expected result:
>   Chrome installs correctly.
>
>   Observed result:
>   The installation hangs on 51%.
>
>   [Regression Potential]
>   The debconf conde was modified to support multiple requests. This could
> expose other debconf issues or break other .deb install code.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/
> +bug/1688721/+subscriptions
>


** Attachment added: "Screenshot from 2017-07-06 15-34-29.png"
   
https://bugs.launchpad.net/bugs/1688721/+attachment/4910281/+files/Screenshot%20from%202017-07-06%2015-34-29.png

--
You received this bug notification because you are subscribed to a
duplicate bug report (1701257).
https://bugs.launchpad.net/bugs/1688721

Title:
  Packages that trigger multiple debconf prompts fail to install

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some packages stall on installing. These are packages that generate multiple 
debconf prompts (the prompts may be empty and so not user visible, e.g. 
gconf2-common).

  [Test Case]
  1. Remove gconf2-common (warning, may uninstall packages like gnome-terminal):
  $ sudo apt purge gconf2-common
  2. Download the debian package of Chrome from 
www.google.com/chrome.
  3. Install the package (browser will prompt, or double click on package in 
Nautilus).

  Expected result:
  Chrome installs correctly.

  Observed result:
  The installation hangs on 51%.

  [Regression Potential]
  The debconf conde was modified to support multiple requests. This could 
expose other debconf issues or break other .deb install code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc

[Desktop-packages] [Bug 1694542] Re: can't get print to work

[Till Kamppeter]

Please post a new bug report following the instructions on
https://wiki.ubuntu.com/DebuggingPrintingProblems

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

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

Title:
  can't get print to work

Status in cups package in Ubuntu:
  Invalid

Bug description:
  i have a samsung m2070fw printer it will not respond

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: i386
  BootLog:
   [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb2-2\x2d8-2\x2d8.2).
   See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb2-2\\x2d8-2\\x2d8.2.service"'
 for details.
   [  OK  ] Started Network Manager Script Dispatcher Service.
   [  OK  ] Started Modem Manager.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 30 17:32:56 2017
  DistUpgraded: 2016-08-03 21:03:22,827 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82G33/G31 Express Integrated Graphics 
Controller [103c:2a6f]
  InstallationDate: Installed on 2014-11-25 (917 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: HP-Pavilion NC839AA-ABA a6838f
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic 
root=UUID=8c58f378-744f-466b-8075-ce338c5307b9 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-08-04 (299 days ago)
  dmi.bios.date: 02/23/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.37
  dmi.board.name: Benicia
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.37:bd02/23/2009:svnHP-Pavilion:pnNC839AA-ABAa6838f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion:
  dmi.product.name: NC839AA-ABA a6838f
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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: Tue May 30 21:16:22 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Microsoft Wheel Mouse Optical® MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   44416 
   vendor ACR
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Trent Nelson]

I was able to wget the diff from
https://bugs.chromium.org/p/chromium/issues/attachment?aid=116063.  I
believe adapting it to the current code base should resolve the crash.
However I do not have a 16.04 build env to test on my system with wifi
nor a wifi adapter to test on my 14.04 system.  Besides, the N2480 would
probably take a week to compile. ;)

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

Re: [Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 o n xenial

[Rohan Bayer-Fox]

Turned off WiFi, Chromium browser comes up with home page (google).
Seems OK.  Turn on WiFi, and it crashes.

-- Original Message --
From: Olivier Tilloy 
To: rbayer...@juno.com
Subject: [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on 
xenial
Date: Thu, 06 Jul 2017 09:30:50 -

To everyone affected by the crash (I haven't managed to reproduce it
locally yet): can you please disable networking on your computer (turn
off wifi) and check whether that makes chromium start normally?

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1702501).
https://bugs.launchpad.net/bugs/1702407

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

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

How To Lose Weight Fast (Drink This Daily)
Celebrity Local
http://thirdpartyoffers.juno.com/TGL3131/595e29a1d367629a10cd6st04vuc

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Trent Nelson]

Just an FYI, this can be worked around by disabling the media router
extension.

1) Start chromium on the command line with: chromium-browser 
--disable-extensions
2) Navigate to chrome://flags
3) Search for "media router" and set it to "Disabled"

I have tested 59.0.3071.109-0ubuntu0.16.04.1289 on two systems, but only
one seems to exhibit the crash.

1) Intel i7-4770, Ubuntu 14.04.5 fully up-to-date, wired network: Does NOT 
exhibit the crash.
2) Intel Celeron N2840, Ubuntu 16.04.2 fully up-to-date, wireless network: DOES 
exhibit the crash. Resolved with the above workaround.

System #2 will even exhibit the crash while running with --temp-profile.
I think it is related to wireless network scan updates and probably
caused by a function parameter order-of-execution assumption that relies
on side-effects (SEI CERT EXP50-CPP) as described in
https://bugs.chromium.org/p/chromium/issues/detail?id=409318.  More
details and a patch I don't seem to be able to download ATM at
https://bugs.chromium.org/p/chromium/issues/detail?id=572539.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

Re: [Desktop-packages] [Bug 1688721] Re: Packages that trigger multiple debconf prompts fail to install

[Mac Abdul]

Whenever i try  to install any appliacation i have face this problem ?
Note : See the screenshot

On Fri, Jun 30, 2017 at 1:06 AM, Launchpad Bug Tracker <
1688...@bugs.launchpad.net> wrote:

> This bug was fixed in the package gnome-software -
> 3.22.7-0ubuntu3.17.04.5
>
> ---
> gnome-software (3.22.7-0ubuntu3.17.04.5) zesty; urgency=medium
>
>   * debian/patches/0001-snap-Fix-icons-not-being-converted-to-
> pixbufs.patch:
> - Fix snaps without icons not showing reliably (LP: #1697565)
>   * debian/patches/0001-snap-Backport-fixes-from-master.patch:
> - Show featured snaps (LP: #1663097)
>   * debian/patches/0017-Use-snap-name-field-for-app-name.patch:
> - Dropped, merged into above patch
>
> gnome-software (3.22.7-0ubuntu3.17.04.4) zesty; urgency=medium
>
>   * debian/patches/0006-Add-an-APT-plugin.patch:
> - Handle multiple debconf connections (LP: #1688721)
>   * debian/patches/0018-Limit-search-entry-to-100-characters.patch:
> - Limit search entry in case of accidental input (LP: #1692398)
>
> gnome-software (3.22.7-0ubuntu3.17.04.3) zesty; urgency=medium
>
>   * debian/patches/0002-Add-an-APT-plugin.patch:
> - Fix crash when debconf socket fails (LP: #1689425)
>
>  -- Robert Ancell   Fri, 16 Jun 2017
> 13:42:12 +1200
>
> ** Changed in: gnome-software (Ubuntu Zesty)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1694521).
> https://bugs.launchpad.net/bugs/1688721
>
> Title:
>   Packages that trigger multiple debconf prompts fail to install
>
> Status in gnome-software package in Ubuntu:
>   Fix Released
> Status in gnome-software source package in Xenial:
>   Fix Released
> Status in gnome-software source package in Yakkety:
>   Fix Released
> Status in gnome-software source package in Zesty:
>   Fix Released
> Status in gnome-software source package in Artful:
>   Fix Released
>
> Bug description:
>   [Impact]
>   Some packages stall on installing. These are packages that generate
> multiple debconf prompts (the prompts may be empty and so not user visible,
> e.g. gconf2-common).
>
>   [Test Case]
>   1. Remove gconf2-common (warning, may uninstall packages like
> gnome-terminal):
>   $ sudo apt purge gconf2-common
>   2. Download the debian package of Chrome from www.google.com/chrome.
>   3. Install the package (browser will prompt, or double click on package
> in Nautilus).
>
>   Expected result:
>   Chrome installs correctly.
>
>   Observed result:
>   The installation hangs on 51%.
>
>   [Regression Potential]
>   The debconf conde was modified to support multiple requests. This could
> expose other debconf issues or break other .deb install code.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-software/
> +bug/1688721/+subscriptions
>


** Attachment added: "Screenshot from 2017-07-06 15-34-29.png"
   
https://bugs.launchpad.net/bugs/1688721/+attachment/4910281/+files/Screenshot%20from%202017-07-06%2015-34-29.png

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

Title:
  Packages that trigger multiple debconf prompts fail to install

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Yakkety:
  Fix Released
Status in gnome-software source package in Zesty:
  Fix Released
Status in gnome-software source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some packages stall on installing. These are packages that generate multiple 
debconf prompts (the prompts may be empty and so not user visible, e.g. 
gconf2-common).

  [Test Case]
  1. Remove gconf2-common (warning, may uninstall packages like gnome-terminal):
  $ sudo apt purge gconf2-common
  2. Download the debian package of Chrome from www.google.com/chrome.
  3. Install the package (browser will prompt, or double click on package in 
Nautilus).

  Expected result:
  Chrome installs correctly.

  Observed result:
  The installation hangs on 51%.

  [Regression Potential]
  The debconf conde was modified to support multiple requests. This could 
expose other debconf issues or break other .deb install code.

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

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

[Desktop-packages] [Bug 1683460] Re: cannot save several times a scan

[Launchpad Bug Tracker]

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

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

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

Title:
  cannot save several times a scan

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  I wanted to save the same scan in png and pdf but the save button kept
  insensitive after the first save even after rotating a page hoping to
  trigger an unsaved status.

  version: 3.24.0

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[togs]

To clarify:

togs@nb03:~$ iwconfig
vmnet8no wireless extensions.

eth0  no wireless extensions.

lono wireless extensions.

virbr0no wireless extensions.

wlan0 IEEE 802.11abgn  ESSID:off/any  
  Mode:Managed  Access Point: Not-Associated   Tx-Power=22 dBm   
  Retry  long limit:7   RTS thr:off   Fragment thr:off
  Power Management:off
  
vmnet1no wireless extensions.

togs@nb03:~$ chromium-browser
Received signal 11 SEGV_MAPERR 0010
#0 0x7f3bf1aedd47 base::debug::StackTrace::StackTrace()
#1 0x7f3bf1aee133 
#2 0x7f3bf17fa330 
#3 0x7f3bf240b9f8 
#4 0x7f3bf240cfb1 
#5 0x7f3bf240d633 
#6 0x7f3bf240dbc7 
#7 0x7f3bf1b62b91 
#8 0x7f3bf1aef269 base::debug::TaskAnnotator::RunTask()
#9 0x7f3bf1b16040 base::MessageLoop::RunTask()
#10 0x7f3bf1b1797d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7f3bf1b1879d 
#12 0x7f3bf1b19250 base::MessagePumpLibevent::Run()
#13 0x7f3bf1b15422 base::MessageLoop::RunHandler()
#14 0x7f3bf1b3ddf8 base::RunLoop::Run()
#15 0x7f3bf1b67d56 base::Thread::ThreadMain()
#16 0x7f3bf1b62a96 
#17 0x7f3bf17f2184 start_thread
#18 0x7f3be7c43ffd clone
  r8:   r9: 0003 r10: 7f3b43cd3d18 r11: 
7f3be7cd0110
 r12: 7f3b43cd3fe0 r13: 0008 r14: 0008 r15: 
7f3b43cd3fe0
  di:   si: 7f3b43cd3fe0  bp:   bx: 
7f3b43cd40f0
  dx: 7f3be872f3d8  ax: 7f3be872f3d8  cx:   sp: 
7f3b43cd3f90
  ip: 7f3bf240b9f8 efl: 00010206 cgf: 0033 erf: 
0004
 trp: 000e msk:  cr2: 0010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[togs]

@osomon: The issue seems to be unrelated to whether you are online or
offline via wifi.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

@togs: it would be useful if you could verify whether turning off wifi
makes the issue go away. If not, that might be a different issue.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

The crash happens on the following line:

NetworkMap::iterator existing_access_point_iter =
network_map->find(ssid);

in extensions::NetworkingPrivateLinux::AddOrUpdateAccessPoint(…)

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[togs]

Have the same issue here on Ubuntu 14.04.5 LTS with the following
packets installed:

dpkg -l | grep chromium
ii  chromium-browser
59.0.3071.109-0ubuntu0.14.04.1186amd64Chromium 
web browser, open-source version of Chrome
ii  chromium-browser-l10n   
59.0.3071.109-0ubuntu0.14.04.1186all  
chromium-browser language packages
ii  chromium-codecs-ffmpeg-extra
59.0.3071.109-0ubuntu0.14.04.1186amd64Extra 
ffmpeg codecs for the Chromium Browser
ii  unity-scope-chromiumbookmarks   
0.1+13.10.20130723-0ubuntu1  all  Chromium 
bookmarks scope for Unity

@osomon The issue seems to be unrelated to whether you are online or
offline.

I can get the issue to disappear and reappear with the following actions
though:

Run "chromium-browser" in terminal
..error appears. Close chromium again.

Run "chromium-browser --disable-extensions" in terminal 
..no error. Close chromium again.

Run chromium-browser
..no error. Close chromium again.

Run chromium-browser
..no error. Close chromium again.

Run chromium-browser
..no error. Close chromium again.

(..tried up to 8 times)

Run chromium-browser
..no error. 
Open a webpage like https://heise.de/newsticker. 
..Page loads. Close chromium again.

Run chromium-browser
..The error appears.


I have run the above cycle several times and this works reliably. Have disabled 
my extensions; at first some, finally all of them, but that has no impact on 
reproducibility. Only deviation: sometimes you have to open more than one 
website and close the browser to find the error reappearing upon next start.

Let me know when I can contribute more information.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Giuseppe_M]

So, I have been using the browser normally all morning without disabling
the extensions. As soon I turned on TV, which has a Chromecast dongle
attached, the browser crashed. Turned off TV, but the browser continued
crashing. So I ran `sudo network-manager stop` and I could open the
browser again, without crashes. Enabling network again and the browser
does not crash.

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

** Package changed: gst-plugins-base1.0 (Ubuntu) => mutter (Ubuntu)

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=775698
   Importance: Unknown
   Status: Unknown

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Unknown
Status in Totem:
  Confirmed
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  In Progress
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1674370] Re: /usr/bin/mate-volume-control-applet:11:__GI___libc_free:pa_xfree:property_free:pa_hashmap_remove_all:pa_hashmap_free

[Vlad Orlov]

** Package changed: mate-media (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  /usr/bin/mate-volume-control-
  
applet:11:__GI___libc_free:pa_xfree:property_free:pa_hashmap_remove_all:pa_hashmap_free

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-media.  This problem was most recently seen with package version 1.12.1-1, 
the problem page at 
https://errors.ubuntu.com/problem/8d7b981c889501e14e130e4178d1a5d70c61ce26 
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/1674370/+subscriptions

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

To everyone affected by the crash (I haven't managed to reproduce it
locally yet): can you please disable networking on your computer (turn
off wifi) and check whether that makes chromium start normally?

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1690254] Re: Ubuntu browser builds can't select text on NYTimes articles

[Olivier Tilloy]

That reminds me of a similar bug we had with the Ubuntu Touch
webbrowser-app, where text selection on touch devices wasn't working for
nytimes.com (bug #1573620). This was fixed by adding a specific
(android-like) user-agent override for that site. I wouldn't be
surprised if it was a similar issue where nytimes.com does funny things
to disallow selection based on user-agent detection.

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

Title:
  Ubuntu browser builds can't select text on NYTimes articles

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  Note: this bug *may* affect touch screen devices only. Just a hunch.

  Load an NYTimes article such as
  https://www.nytimes.com/2017/05/10/science/trappist-earth-size-
  planets-orbits-music.html and attempt to select some text, either via
  click-and-drag or double/triple click.

  Using the official Mozilla Firefox 53.0.2 build, this works as
  expected. Using the Ubuntu Zesty Firefox 53.0+build6 build however,
  the user can't select any text. Instead, click-and-drag scrolls some
  links to other articles in from the sides, while double click resizes
  the article text (equivalent touchpad and touchscreen interactions
  have the same effect). Android-style tap-and-hold does nothing. Caret
  Browsing also doesn't work, as the arrow keys are overridden. Only
  + still works as expected.

  There doesn't seem to be an invisible layer above the text, since the
  mouse pointer changes between an arrow, finger, and I-beam cursor, and
  since clicking on links works.

  This inconsistency violates the Law of Least Astonishment.

  Affected browsers:
  * Ubuntu Gnome 17.04 64-bit touchscreen: Ubuntu Firefox 53.0+build6 with 
clean profile, Ubuntu Modifications add-on only
  * Ubuntu Gnome 17.04 64-bit touchscreen: Ubuntu Firefox 53.0+build6 with 
clean profile and no add-ons
  * Ubuntu Gnome 17.04 64-bit touchscreen: Ubuntu Chromium 58.0.3029.96

  Not affected:
  * Ubuntu Gnome 17.04 64-bit touchscreen: Official Mozilla Firefox 53.0.2 with 
clean profile
  * Ubuntu 16.04 LTS 32-bit: Ubuntu Firefox 53.0+build6 on Ubuntu 16.04 LTS
  * Windows XP 32-bit: Mozilla 52.0.2

  Bugzilla reference:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1363936

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: firefox 53.0.2+build1-0ubuntu0.17.04.2
  Uname: Linux 4.11.0-041100-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  BuildID: 20170509205512
  CurrentDesktop: GNOME
  Date: Fri May 12 07:47:00 2017
  InstallationDate: Installed on 2016-12-02 (159 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1637674] Re: /usr/bin/mate-settings-daemon:7:g_mutex_lock:g_source_remove_poll:glib_io_free:pa_srbchannel_free:check_srbpending

[Vlad Orlov]

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

** Package changed: mate-settings-daemon (Ubuntu) => pulseaudio (Ubuntu)

** This bug has been marked a duplicate of bug 1571894
   mate-settings-daemon crashed with SIGSEGV in g_mutex_lock() from 
g_source_remove_poll() from glib_io_free() from pa_srbchannel_free() from 
check_srbpending()

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

Title:
  /usr/bin/mate-settings-
  
daemon:7:g_mutex_lock:g_source_remove_poll:glib_io_free:pa_srbchannel_free:check_srbpending

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.12.1-2build1, the problem page at 
https://errors.ubuntu.com/problem/77c2480f6212d8ebc57066d78c80828ec2f403ef 
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/1637674/+subscriptions

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

Upstream bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=734325

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1674370] [NEW] /usr/bin/mate-volume-control-applet:11:__GI___libc_free:pa_xfree:property_free:pa_hashmap_remove_all:pa_hashmap_free

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-media.  This problem was most recently seen with package version 1.12.1-1, 
the problem page at 
https://errors.ubuntu.com/problem/8d7b981c889501e14e130e4178d1a5d70c61ce26 
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/.

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


** Tags: xenial
-- 
/usr/bin/mate-volume-control-applet:11:__GI___libc_free:pa_xfree:property_free:pa_hashmap_remove_all:pa_hashmap_free
https://bugs.launchpad.net/bugs/1674370
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

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

[Desktop-packages] [Bug 1643093] Re: /usr/bin/mate-volume-control:11:glib_io_free:delete_events:pa_iochannel_free:pa_pstream_unlink:context_unlink

[Vlad Orlov]

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

** Package changed: mate-media (Ubuntu) => pulseaudio (Ubuntu)

** This bug has been marked a duplicate of bug 1571724
   mate-settings-daemon crashed with SIGSEGV in glib_io_free() from 
delete_events() from pa_iochannel_free() from pa_pstream_unlink() from 
context_unlink()

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

Title:
  /usr/bin/mate-volume-
  
control:11:glib_io_free:delete_events:pa_iochannel_free:pa_pstream_unlink:context_unlink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-media.  This problem was most recently seen with package version 1.12.1-1, 
the problem page at 
https://errors.ubuntu.com/problem/2eaaeef563fbc5e7df33a1e30490f22b5ed330f0 
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/1643093/+subscriptions

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

[Desktop-packages] [Bug 1662956] Re: /usr/bin/mate-volume-control-applet:11:glib_io_free:delete_events:pa_iochannel_free:pa_pstream_unlink:context_unlink

[Vlad Orlov]

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

** Package changed: mate-media (Ubuntu) => pulseaudio (Ubuntu)

** This bug has been marked a duplicate of bug 1571724
   mate-settings-daemon crashed with SIGSEGV in glib_io_free() from 
delete_events() from pa_iochannel_free() from pa_pstream_unlink() from 
context_unlink()

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

Title:
  /usr/bin/mate-volume-control-
  
applet:11:glib_io_free:delete_events:pa_iochannel_free:pa_pstream_unlink:context_unlink

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-media.  This problem was most recently seen with package version 1.12.1-1, 
the problem page at 
https://errors.ubuntu.com/problem/9c586557f4a801a0becd33cd283c6283fd23a900 
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/1662956/+subscriptions

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

[Desktop-packages] [Bug 1637674] [NEW] /usr/bin/mate-settings-daemon:7:g_mutex_lock:g_source_remove_poll:glib_io_free:pa_srbchannel_free:check_srbpending

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-settings-daemon.  This problem was most recently seen with package version 
1.12.1-2build1, the problem page at 
https://errors.ubuntu.com/problem/77c2480f6212d8ebc57066d78c80828ec2f403ef 
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/.

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


** Tags: xenial
-- 
/usr/bin/mate-settings-daemon:7:g_mutex_lock:g_source_remove_poll:glib_io_free:pa_srbchannel_free:check_srbpending
https://bugs.launchpad.net/bugs/1637674
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

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

[Desktop-packages] [Bug 1702407] Re: Startup crash after upgrading to 59.0.3071.109 on xenial

[Olivier Tilloy]

Thanks Giuseppe, that's very useful. I extracted a full backtrace from
the crash, attaching it here.

** Summary changed:

- Update breaks chromium-browser on Ubuntu Mate 16.04.2
+ Startup crash after upgrading to 59.0.3071.109 on xenial

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: chromium-browser (Ubuntu)
   Importance: High => Critical

** Attachment added: "chromium-59-startup-crash-full-bt.txt"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702407/+attachment/4910219/+files/chromium-59-startup-crash-full-bt.txt

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

Title:
  Startup crash after upgrading to 59.0.3071.109 on xenial

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 59.0.3071.109-0ubuntu0.16.04.1289
Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
Version table:
   *** 59.0.3071.109-0ubuntu0.16.04.1289 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   49.0.2623.108-0ubuntu1.1233 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ chromium-browser
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f8cc1af5425 base::debug::StackTrace::StackTrace()
  #1 0x7f8cc1af580b 
  #2 0x7f8cc1e20390 
  #3 0x5619ce286dc8 
  #4 0x5619ce289656 
  #5 0x5619ce289df9 
  #6 0x5619ce28a143 
  #7 0x7f8cc1b70821 
  #8 0x7f8cc1af6eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f8cc1b1fe90 base::MessageLoop::RunTask()
  #10 0x7f8cc1b2197d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f8cc1b2283d 
  #12 0x7f8cc1b23300 base::MessagePumpLibevent::Run()
  #13 0x7f8cc1b1ef15 base::MessageLoop::RunHandler()
  #14 0x7f8cc1b49628 base::RunLoop::Run()
  #15 0x7f8cc1b75e36 base::Thread::ThreadMain()
  #16 0x7f8cc1b70726 
  #17 0x7f8cc1e166ba start_thread
  #18 0x7f8cab4c53dd clone
r8: 002e  r9: 5619cfcdd6ec r10:  r11: 
7f8cab552f50
   r12: 7f8c1b0d1ff0 r13: 0008 r14: 0008 r15: 
7f8c1b0d1eb0
di:   si: 7f8c1b0d1eb0  bp: 7f8c1b0d1f00  bx: 
7f8c1b0d1eb0
dx: 0061  ax:   cx: 7f8bf0047070  sp: 
7f8c1b0d1e60
ip: 5619ce286dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]

  Quits <1s after starting on desktop.  Output from terminal-based launch is 
above.
  Worked earlier today before updating.

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

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

[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

[Daniel van Vugt]

More progress: gst-play-1.0 fails on Gnome Shell Wayland only (and not
in Weston) because of a mutter problem (or arguably the gstreamer-vaapi
plugin assuming that mutter should support it):

https://bugzilla.gnome.org/show_bug.cgi?id=775698

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

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Totem:
  Confirmed
Status in gst-plugins-base1.0 package in Ubuntu:
  In Progress
Status in gstreamer-vaapi package in Ubuntu:
  In Progress
Status in intel-vaapi-driver package in Ubuntu:
  Invalid
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Triaged
Status in totem package in Ubuntu:
  Invalid

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1702456] Re: Chromium cannot found pepperflash plugin

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1702407
   Update breaks chromium-browser on Ubuntu Mate 16.04.2

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

Title:
  Chromium cannot found pepperflash plugin

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu version: 16.04
  Chromium version : 59.0.3071.109-0ubuntu0.16.04.1289
  Pepperflash-plugin version: 26.0.0.131
  apt-cache policy pepperflashplugin-nonfree 
  pepperflashplugin-nonfree:
Installed: 1.8.2ubuntu1.1

  
  When try to start chromium it return this message

  PPAPI flash has config file in /etc, but library does not exist and won't be 
used. Package is uninstalled, not purged.
  Received signal 11 SEGV_MAPERR 0010
  #0 0x7f32709c2425 base::debug::StackTrace::StackTrace()
  #1 0x7f32709c280b 
  #2 0x7f3270ced390 
  #3 0x55e3d9a77dc8 
  #4 0x55e3d9a7a656 
  #5 0x55e3d9a7adf9 
  #6 0x55e3d9a7b143 
  #7 0x7f3270a3d821 
  #8 0x7f32709c3eea base::debug::TaskAnnotator::RunTask()
  #9 0x7f32709ece90 base::MessageLoop::RunTask()
  #10 0x7f32709ee97d base::MessageLoop::DeferOrRunPendingTask()
  #11 0x7f32709ef83d 
  #12 0x7f32709f0300 base::MessagePumpLibevent::Run()
  #13 0x7f32709ebf15 base::MessageLoop::RunHandler()
  #14 0x7f3270a16628 base::RunLoop::Run()
  #15 0x7f3270a42e36 base::Thread::ThreadMain()
  #16 0x7f3270a3d726 
  #17 0x7f3270ce36ba start_thread
  #18 0x7f325a3923dd clone
r8: 002e  r9: 55e3db4ce6ec r10:  r11: 
7f325a41ff50
   r12: 7f31baec1ff0 r13: 0008 r14: 0008 r15: 
7f31baec1eb0
di:   si: 7f31baec1eb0  bp: 7f31baec1f00  bx: 
7f31baec1eb0
dx: 0062  ax:   cx: 7f31940084d0  sp: 
7f31baec1e60
ip: 55e3d9a77dc8 efl: 00010206 cgf: 0033 erf: 
0004
   trp: 000e msk:  cr2: 0010
  [end of stack trace]
  Calling _exit(1). Core file will not be generated.

  
  I've tried to reinstall both chromium and pepperflash plug-in but the error 
persists.

  Launching chromium with --debug :

  
  PPAPI flash has config file in /etc, but library does not exist and won't be 
used. Package is uninstalled, not purged.
  # Env:
  # LD_LIBRARY_PATH=/usr/lib/chromium-browser
  #
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  #GTK_PATH=
  # CHROMIUM_USER_FLAGS=
  #  CHROMIUM_FLAGS= 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=26.0.0.131  --enable-pinch
  /usr/bin/gdb /usr/lib/chromium-browser/chromium-browser -x 
/tmp/chromiumargs.MRIgut
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
  Copyright (C) 2016 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"...
  Reading symbols from /usr/lib/chromium-browser/chromium-browser...(no 
debugging symbols found)...done.
  (gdb) run
  Starting program: /usr/lib/chromium-browser/chromium-browser 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so 
--ppapi-flash-version=26.0.0.131  --enable-pinch 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffcd30a700 (LWP 19941)]
  [New Thread 0x7fffccb09700 (LWP 19947)]
  [New Thread 0x7fffc7be1700 (LWP 19948)]
  [New Thread 0x7fffc73e0700 (LWP 19949)]
  [New Thread 0x7fffc6bdf700 (LWP 19950)]
  [New Thread 0x7fffc4c71700 (LWP 19951)]
  [New Thread 0x7fffb3fff700 (LWP 19952)]
  [New Thread 0x7fffb37fe700 (LWP 19953)]
  [New Thread 0x7fffb2ffd700 (LWP 19954)]
  [New Thread 0x7fffcc02b700 (LWP 19955)]
  [New Thread 0x7fffb27fc700 (LWP 19956)]
  [New Thread 0x7fff9bfff700 (LWP 19957)]
  [New Thread 0x7fff9b7fe700 (LWP 19958)]
  [New Thread 0x7fff9affd700 (LWP 19959)]
  [New Thread 0x7fff9a7fc700 (LWP 19960)]
  [New Thread 0x7fff99ffb700 (LWP 19961)]
  [New Thread 0x7fff997fa700 (LWP 19962)]
  [New Thread 0x7fff98ff9700 (LWP 19963)]
  [New Thread 0x7fff7700 (LWP 19964)]
  [New Thread 0x7fff7f7fe700 (LWP 19965)]
  [New Thread 0x7fff7effd700 (

[Desktop-packages] [Bug 1643093] [NEW] /usr/bin/mate-volume-control:11:glib_io_free:delete_events:pa_iochannel_free:pa_pstream_unlink:context_unlink

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
mate-media.  This problem was most recently seen with package version 1.12.1-1, 
the problem page at 
https://errors.ubuntu.com/problem/2eaaeef563fbc5e7df33a1e30490f22b5ed330f0 
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/.

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


** Tags: xenial
-- 
/usr/bin/mate-volume-control:11:glib_io_free:delete_events:pa_iochannel_free:pa_pstream_unlink:context_unlink
https://bugs.launchpad.net/bugs/1643093
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

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