date:20170321

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

** Changed in: simple-scan (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Brother ADS-2100e Scanner does not work out of the box in 16.04

Status in simple-scan package in Ubuntu:
  Expired

Bug description:
  What I expect is my Brother ADS-2100e scanner to work out of the box.
  What happens instead is it doesn't.

  But Ubuntu lacks of a proper recognition - it seems to be a missing UDEV 
rule. The scanner is recognized by lsusb as "04f9:037d":
  Bus 003 Device 005: ID 04f9:037d Brother Industries, Ltd

  And dmesg tells me:
  [ 8075.564495] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [ 8075.693751] usb 3-1: New USB device found, idVendor=04f9, idProduct=037d
  [ 8075.693760] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 8075.693764] usb 3-1: Product: ADS-2100e
  [ 8075.693768] usb 3-1: Manufacturer: Brother
  [ 8075.693771] usb 3-1: SerialNumber: E74188A6G337846
  [ 8079.128671] usb 3-1: USB disconnect, device number 4
  [ 8080.644164] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 8080.773321] usb 3-1: New USB device found, idVendor=04f9, idProduct=037d
  [ 8080.773325] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 8080.773327] usb 3-1: Product: ADS-2100e
  [ 8080.773329] usb 3-1: Manufacturer: Brother
  [ 8080.773331] usb 3-1: SerialNumber: E74188A6G337846

  WORKAROUND: Install Brother linux (deb) driver brscan4-0.4.4-1.amd64.deb from:
  
http://support.brother.com/g/b/downloadtop.aspx?c=at&lang=de&prod=ads2100e_eu_as_cn

  Then, create file /etc/udev/rules.d/39-brother.rules :
  ATTRS{idVendor}=="04f9", ATTRS{idProduct}=="037d", ENV{libsane_matched}="yes"

  "39" because it needs to run BEFORE the
  /lib/udev/rules.d/40-libsane.rules - there is the variable
  "libsane_matched" needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: simple-scan 3.20.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 15:37:14 2017
  InstallationDate: Installed on 2016-12-13 (28 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP ProDesk 600 G1 TWR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L01 v02.21
  dmi.board.asset.tag: CZC411388T
  dmi.board.name: 18E7
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC411388T
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL01v02.21:bd12/17/2013:svnHewlett-Packard:pnHPProDesk600G1TWR:pvr:rvnHewlett-Packard:rn18E7:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 600 G1 TWR
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1657469] Re: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to build [In function ‘uvm8_test_range_allocator_sanity’: internal compiler error: Speicherzugr

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

** Changed in: gcc-5 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to
  build [In function ‘uvm8_test_range_allocator_sanity’: internal
  compiler error: Speicherzugriffsfehler]

Status in gcc-5 package in Ubuntu:
  Expired
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Invalid

Bug description:
  after update

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-367 367.57-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-59-generic
  Date: Wed Jan 18 14:52:59 2017
  InstallationDate: Installed on 2016-11-21 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 367.57-0ubuntu0.16.04.1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: nvidia-graphics-drivers-367
  Title: nvidia-367 367.57-0ubuntu0.16.04.1: nvidia-367 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

That all said... why don't we just declare gnome-screenshot unsupported
if it's really just a client of gnome-shell. Doesn't Unity8 have other
adequate screenshotting mechanisms?

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+subscriptions

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

[Desktop-packages] [Bug 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

"Is there some mir client api for scraping the screen?"

Yes, but it's also not nice. See src/utils/screencast.cpp. That's why I
suggest we need to fix Mir in bug 1660269.

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+subscriptions

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

[Desktop-packages] [Bug 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

On one hand asking the shell to own screenshotting is nice and secure.

On the other hand, persisting with an architecture where apps don't work
unless processes other than the shell happen to be running is a bit
nasty in my opinion. And similarly anything that depends on a bus is
ugly IMHO. I've lost count of the number of times in recent months where
GTK apps refused to start because they were timing out waiting for some
process or bus to become available that didn't exist in Mir.

When you develop an app for a platform, like for Mir using just
libmirclient, there should ideally be zero other dependencies on the
system. Everything should be implemented or proxied through that one
library.

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+subscriptions

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

[Desktop-packages] [Bug 722130] Re: Incorrect direction of sorting arrows

2017-03-21 Thread tom

This is consistent with other GNOME applications.

That doesn't mean it's correct!

The sort arrows are backward everywhere!

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

Title:
  Incorrect direction of sorting arrows

Status in transmission package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: transmission

  There is a logical bug in table of partners.

  For example, when I sort column with download speed, I got an
  incorrect direction of arrow.

  \/ - from bigger to smaller (because top-side of arrow is wide)

  /\ - from smaller to bigger (because top-side of arrow is null)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: transmission-gtk 2.05-0ubuntu0.2
  ProcVersionSignature: Ubuntu 2.6.35-26.46-generic-pae 2.6.35.10
  Uname: Linux 2.6.35-26-generic-pae i686
  NonfreeKernelModules: fglrx wl
  Architecture: i386
  Date: Sun Feb 20 14:29:01 2011
  ExecutablePath: /usr/bin/transmission
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=pl_PL.utf8
   SHELL=/bin/bash
  SourcePackage: transmission

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

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

[Desktop-packages] [Bug 1674477] Re: gnome screenshot gtk-mir crashes on taking the shot under Mir

2017-03-21 Thread William Hua

I don't know if that would be the easiest approach. It sounds to me like
having U8 implement that dbus interface would be the easiest and least
invasive solution, but then again, I'm not the one volunteering for that
:)

Is there some mir client api for scraping the screen? I'm worried about
whether or not that kind of change would be accepted upstream (there's
no wayland-specific code in gnome-screenshot). Also, how does it look
from a security perspective? The nice thing about that interface is that
the screenshot app never has direct access to the pixel data in the
first place (it's just file names that U8 would save the image data
directly to), and access to the interface could be restricted via
apparmor dbus rules.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

** Tags removed: gtk-mir

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

Title:
  gnome screenshot gtk-mir crashes on taking the shot under Mir

Status in Canonical System Image:
  New
Status in gnome-screenshot package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Tried this with (updated) Zesty plus ppa:attente/gtk-mir-staging
  then export GDK_BACKEND=mir
  launch from command line: gnome-screenshot -- 
--desktop_file_hint=org.gnome.Screenshot.desktop

  Attempt to take a screen shot in any form and it will crash (see
  attached log)

  
  according to attente: 
  gnome-screenshot crashes is because it delegates the screenshotting to 
org.gnome.Shell, and falls back to using x11 if that fails
  so i think the solution is to have u8 implement that interface...
  
https://git.gnome.org/browse/gnome-shell/tree/data/org.gnome.Shell.Screenshot.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1674477/+subscriptions

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

[Desktop-packages] [Bug 1674873] [NEW] It still shows "Enable Wi-Fi" after turn on AIrplane Mode

2017-03-21 Thread Hao-Sheng Lu

Public bug reported:

OS: 16.04 xenial

Steps to reproduce:
1. boot up the system
2. Do not connect to any Access Point, turn on Airplane Mode in Network 
setting(or Press hotkey)
3. found it still shows "Enable Wi-Fi" in the network menu(of the Panel)

ps. if you do connect to AP in Step 2, this issue will not happen.

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

Title:
  It still shows "Enable Wi-Fi" after turn on AIrplane Mode

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

Bug description:
  OS: 16.04 xenial

  Steps to reproduce:
  1. boot up the system
  2. Do not connect to any Access Point, turn on Airplane Mode in Network 
setting(or Press hotkey)
  3. found it still shows "Enable Wi-Fi" in the network menu(of the Panel)

  ps. if you do connect to AP in Step 2, this issue will not happen.

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

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

[Desktop-packages] [Bug 1674865] [NEW] Printing operation doesn't start

2017-03-21 Thread Deependra Dhakal

Public bug reported:

Printer does not start.

The attachment below is the output of debug log, generated by from,

$ cupsctl LogLevel=debug
$ cancel -a
$ sudo less /var/log/cups/error_log

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.8
ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
CupsErrorLog:
 E [22/Mar/2017:06:36:13 +0545] [Client 21] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
 E [22/Mar/2017:06:37:24 +0545] [Client 8] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
CurrentDesktop: Unity
Date: Wed Mar 22 06:45:17 2017
InstallationDate: Installed on 2017-02-22 (27 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A3A3ONmL
MachineType: TOSHIBA Satellite L840
Papersize: a4
PpdFiles: Canon-LBP2900: Generic text-only printer
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=6948ffd7-612e-4f3e-ae73-46d0f433dc7d ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd06/26/2012:svnTOSHIBA:pnSatelliteL840:pvrPSK8NL-00F004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L840
dmi.product.version: PSK8NL-00F004
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug trusty

** Attachment added: "error_log.txt"
   
https://bugs.launchpad.net/bugs/1674865/+attachment/4842053/+files/error_log.txt

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

Title:
  Printing operation doesn't start

Status in cups package in Ubuntu:
  New

Bug description:
  Printer does not start.

  The attachment below is the output of debug log, generated by from,

  $ cupsctl LogLevel=debug
  $ cancel -a
  $ sudo less /var/log/cups/error_log

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 4.4.0-66.87~14.04.1-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CupsErrorLog:
   E [22/Mar/2017:06:36:13 +0545] [Client 21] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
   E [22/Mar/2017:06:37:24 +0545] [Client 8] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/Canon-LBP2900) from localhost
  CurrentDesktop: Unity
  Date: Wed Mar 22 06:45:17 2017
  InstallationDate: Installed on 2017-02-22 (27 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lpstat: device for Canon-LBP2900: usb://Canon/LBP2900?serial=A3A3ONmL
  MachineType: TOSHIBA Satellite L840
  Papersize: a4
  PpdFiles: Canon-LBP2900: Generic text-only printer
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=6948ffd7-612e-4f3e-ae73-46d0f433dc7d ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd06/26/2012:svnTOSHIBA:pnSatelliteL840:pvrPSK8NL-00F004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L840
  dmi.product.version: PSK8NL-00F004
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1526155] Re: nvidia-* kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]

** Also affects: nvidia-graphics-drivers-375 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: New => Confirmed

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

Title:
  nvidia-* kernel module failed to build [cc: error: unrecognized
  command line option ‘-fstack-protector-strong’]

Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-340 340.96-0ubuntu0.14.04.1
  Uname: Linux 4.0.4-040004-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  DKMSKernelVersion: 4.3.2-040302-generic
  Date: Tue Dec 15 01:29:18 2015
  DuplicateSignature: dkms:nvidia-340:340.96-0ubuntu0.14.04.1:cc: error: 
unrecognized command line option ‘-fstack-protector-strong’
  InstallationDate: Installed on 2014-10-15 (425 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 340.96-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.96-0ubuntu0.14.04.1: nvidia-340 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.340.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1526155/+subscriptions

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

[Desktop-packages] [Bug 1665144] Re: nautilus reports that an NTFS drive is read-only while it is writeable

2017-03-21 Thread Ivan Kharlamov

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

** This bug has been marked a duplicate of bug 1021375
   Nautilus says the USB stick is read only when it is not

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

Title:
  nautilus reports that an NTFS drive is read-only while it is writeable

Status in nautilus package in Ubuntu:
  New

Bug description:
  By default, Nautilus seems to mount an NTFS partition read-only when a
  Windows system that has Fast Boot enabled accesses the partition, is
  shut down and I boot back into Ubuntu. However, when I umount the
  partition, run ntfsfix on it, and mount it again, Nautilus does not
  let me move, paste or create folders and files, but surprisingly
  allows me to delete anything. Such behavior is quite strange.

  More formally:
  Steps to reproduce the bug:
  - Boot Windows and shut it down with Fast Boot enabled (so the NTFS 
partitions will be in an unsafe state)
  - Boot into Ubuntu
  - Open an NTFS partition with Nautilus (not the one that contains Windows). 
As expected the partition is mounted read-only and menus don't allow the user 
to modify anything (items disabled).
  - Unmount the partition (I used the umount command from a terminal)
  - Run "sudo ntfsfix /dev/sdXX"
  - Reopen the NTFS partition

  What was expected:
  I should be able to create, move or delete files with Nautilus.

  What happened:
  The menu items used to create, move or delete files are enabled but when I 
actually try to create files or folders, or move any to the NTFS partition, 
Nautilus complains about the destination being read-only. Deleting files or 
moving them away from the partition works flawlessly. I can also modify 
everything with other tools, like a text editor or terminal commands.
  Restarting Nautilus (i.e. running "nautilus -q" then "nautilus") solves the 
problem.
  See screenshots: http://imgur.com/a/aJ6kF

  System : Ubuntu 16.10, Nautilus version 1:3.20.3-1ubuntu3.1

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
  Uname: Linux 4.8.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 15 22:00:04 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'202'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x645+550+227'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2017-01-14 (32 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2017-03-21 Thread WolphFang

It took me a week to figure out why I could not get networking to work
on my non-chroot desktop.

I had to add a blank file and reboot? WTF?

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1613751] Re: NM and gnome-session seem to be syslogging with facility KERN

2017-03-21 Thread Nathan Dorfman

This is actually getting worse in Debian stretch, and there affects
almost 2 dozen packages, so it might not even be the packages'
(NetworkManager, gnome-session) fault. Anyway, https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=858399

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

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

Title:
  NM and gnome-session seem to be syslogging with facility KERN

Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager's copious syslog output is for some reason making its
  way into my /var/log/kern.log file. This includes a couple dozen
   lines at startup and a similar amount when connecting to WiFi
  with DHCP.

  The NM man page states that the default facility should be DAEMON, as
  does the NM wiki -- see
  http://manpages.ubuntu.com/manpages/xenial/man8/NetworkManager.8.html
  and https://wiki.gnome.org/Projects/NetworkManager/Debugging

  Hopefully, it goes without saying that the KERN facility is reserved
  for the kernel and shouldn't be messed with by anything from userland.

  Nothing in the rsyslog configs references kern.log except the one expected 
line:
  /etc/rsyslog.d/50-default.conf:kern.* 
-/var/log/kern.log

  Nothing in NetworkManager.conf references syslog or its facilities.
  Oh, and these messages do also correctly make it to syslog.log. I've
  no idea how or why they also end up in kern.log, though.

  This doesn't happen on Ubuntu 14.04:
  % zgrep -cv kernel: /var/log/kern.log* 
  /var/log/kern.log:0
  /var/log/kern.log.1:0
  /var/log/kern.log.2.gz:0
  /var/log/kern.log.3.gz:0
  /var/log/kern.log.4.gz:0

  On Ubuntu 16.04.1, NM is the major culprit, although there were also a few 
lines from gnome-session:
  % zgrep -cv kernel: /mnt/var/log/kern.log*
  /mnt/var/log/kern.log:402
  /mnt/var/log/kern.log.1:722
  % zgrep -v kernel: /mnt/var/log/kern.log* | grep -vc NetworkManager
  17
  % zgrep -v kernel: /mnt/var/log/kern.log* | fgrep -cve NetworkManager -e 
'gnome-session-binary'
  0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.0-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 16 06:53:42 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.0.5  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/1  
86180F  674c9d27-1bb1-4055-a6e4-07de9abbb586  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.0connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth

2017-03-21 Thread D

im on 16.04.2 too, but i still see the bug. the workaround #77 didnt
help for me too..

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

Title:
  unable to import config with inlined ca, cert, key or tls-auth

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Fedora:
  New

Bug description:
  Binary package hint: network-manager-openvpn-gnome

  So a client of mine runs an OpenVPN setup. It exported a client.ovpn
  file but it fails to completely import this file using the network-
  manager (gnome) on Ubuntu 10.04.

  When I import the file, it gives me the name ("client") and gateway
  ("vpn.example.org") on the initial screen. No other fields are
  populated even though the client.ovpn file also includes a user
  certificate, server certifikate and a private key.

  When I go to advanced, some (most) of the settings obviously seem to
  import correct, others not at all. E.g. none of the TLS settings (key
  and key direction) are imported.

  From what I understand I should be able to use this without any
  additional settings.

  The following software is installed through aptitude:

   * openvpn (2.1.0)
   * openvpn-blacklist
   * network-manager-openvpn
   * network-manager-openvpn-gnome

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

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

[Desktop-packages] [Bug 1674005] Re: audiofile: Multiple security issues from March 2017

2017-03-21 Thread Mathew Hodson

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

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

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

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

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

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

Title:
  audiofile: Multiple security issues from March 2017

Status in audiofile package in Ubuntu:
  New
Status in audiofile source package in Precise:
  New
Status in audiofile source package in Trusty:
  New
Status in audiofile source package in Xenial:
  New
Status in audiofile source package in Yakkety:
  New

Bug description:
  https://security-tracker.debian.org/tracker/source-package/audiofile
  http://openwall.com/lists/oss-security/2017/02/26/
  https://github.com/mpruett/audiofile/issues/32
  
https://blogs.gentoo.org/ago/2017/02/20/audiofile-heap-based-buffer-overflow-in-msadpcminitializecoefficients-msadpcm-cpp
  https://github.com/mpruett/audiofile/commit/c48e4c6503

  
  Fixed in Debian unstable 0.3.6-4 and synced to zesty.

  debdiffs attached for 14.04 LTS and up. For 12.04 LTS, audiofile was
  in main so someone should probably try to apply the patches there too.

  I've done no testing of these packages.

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

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

[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2017-03-21 Thread Benjamin Blanchard

I also had the issue on a fresh Ubuntu 16.04, the applet not working
properly after resuming from suspend.

But I may have something to help here. A few days ago, I didn't had the
issue on a previous install, so I tried the two changes I made on that
one suspend-related.

First, I enabled hibernation, but it didn't change anything, still the
bug after resume.

And then, I installed tlp, basic with no modification, and it now works
properly every time.

Hope that may help.

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

Title:
  cannot view wifi networks after re-enabling wifi

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

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

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

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

[Desktop-packages] [Bug 1639180] Re: no login possible after update to nvidia 304.132

2017-03-21 Thread Frau Tukka

Did anyone try 304.135-0ubuntu0.16.04.1 on 16.04.2? I would not want to mess up 
my system if it doesn't work. Any success?
Thanks.

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

Title:
  no login possible after update to nvidia 304.132

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Yakkety:
  Triaged
Status in nvidia-graphics-drivers-legacy-304xx package in Debian:
  Fix Released

Bug description:
  Ubuntu 16.04 LTS

  NVIDIA driver:
  - nvidia-graphics-drivers-304
  - update to version 304.132

  dpkg.log:
  upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2

  - reboot
  - lightdm login screen
  - login
  - a few seconds some flickering
  - and the lightdm login screen appears again

  It is not possible to login. Unity is not loading.

  .xsession-errors:
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
Major opcode of failed request:  155 (GLX)
Minor opcode of failed request:  3 (X_GLXCreateContext)
Value in failed request:  0x0
Serial number of failed request:  34
Current serial number in output stream:  35

  See also bug 1634802

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions

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

[Desktop-packages] [Bug 606365] Re: unable to import config with inlined ca, cert, key or tls-auth

2017-03-21 Thread Martin Zbořil

funnily enough, the bug is actually fixed, all what is needed is
actually network-manager-openvpn-gnome (I tested it on version
1.1.93-1ubuntu1.1 in 16.04.2) installed and then the network settings
configuration gui restarted so the new VPN shows up as openvpn, after
that importing the configuration from ovpn file works..

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

Title:
  unable to import config with inlined ca, cert, key or tls-auth

Status in NetworkManager-OpenVPN:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Fedora:
  New

Bug description:
  Binary package hint: network-manager-openvpn-gnome

  So a client of mine runs an OpenVPN setup. It exported a client.ovpn
  file but it fails to completely import this file using the network-
  manager (gnome) on Ubuntu 10.04.

  When I import the file, it gives me the name ("client") and gateway
  ("vpn.example.org") on the initial screen. No other fields are
  populated even though the client.ovpn file also includes a user
  certificate, server certifikate and a private key.

  When I go to advanced, some (most) of the settings obviously seem to
  import correct, others not at all. E.g. none of the TLS settings (key
  and key direction) are imported.

  From what I understand I should be able to use this without any
  additional settings.

  The following software is installed through aptitude:

   * openvpn (2.1.0)
   * openvpn-blacklist
   * network-manager-openvpn
   * network-manager-openvpn-gnome

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

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

[Desktop-packages] [Bug 1449795] Re: keys not showing up after creation

2017-03-21 Thread Leon

Same problem on 14.04.1 Linux Mint Qiana - new keys need some minutes
before they appear in they right window pane. Found, that also with "gpg
- list-key" and "gpg2 - list-keys" it takes some time showing  new keys.

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

Title:
  keys not showing up after creation

Status in seahorse package in Ubuntu:
  Confirmed

Bug description:
  Hit "+" button -> PGP key -> details: test1 test2 t...@ohmbase.org ->
  hit create button -> test/test (username/password) -> ok

  nothing happens.  no error message, no 'seahorse/gpg is working'
  ...nothing

  ubuntu 15.04
  seahorse:
    Installed: 3.15.90-0ubuntu1
    Candidate: 3.15.90-0ubuntu1

  gnupg:
    Installed: 1.4.18-7ubuntu1
    Candidate: 1.4.18-7ubuntu1

  *once* the key showed up when I was on another window.

  what should have happened:
  if it was possible to create the key ...the key should be displayed
  if not...an error message.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: seahorse 3.15.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr 28 20:09:50 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-24 (4 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  SourcePackage: seahorse
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1650972] Re: No .vapi in Zesty

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

Title:
  No .vapi in Zesty

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The .vapi file is missing from the packaging in the Zesty version.
  This triggers some build to fail in elementary for example.

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

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

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2017-03-21 Thread mohican

Welcome Phil,
did you try the fix from post #8 ?
and rebooting from Linux (not from Windows) as I suggest in my post #16.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.

2017-03-21 Thread Kenneth Loafman

** Changed in: duplicity
Milestone: 0.7.12 => 0.7.13

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

Title:
  Backing up fails with 'IOError CRC check failed'.

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

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

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

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

[Desktop-packages] [Bug 1638990] Re: nvidia-367 with kernel 4.4.0-45-generic won't boot

2017-03-21 Thread demaniak

Kernel 4.4.0-66
Nvidia 375
Xubuntu 16.04.2
GTX965M


Long ago removed splash screens etc during boot, so after the upgrade of kernel 
and graphics driver, I could see that the "Nvidia peristence deamon" was 
failing to start. It gets retried a couple of times, but after it fails for the 
final time, the boot process is dead. And the system is then hung.

Manually adding nomodeset to the grub boot options (from boot loader
menu) at least gets me back into a desktop, BUT the nvidia driver is not
working properly at that point (nvidia settings for example does not
register the graphics card at all).

Before this upgrade today, everything was fine. I am now forced back to
the open source drivers.

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

Title:
  nvidia-367 with kernel 4.4.0-45-generic won't boot

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-367 package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded the nvidia drivers, I could no longer boot via kernel
  4.4.0-45-generic.

  WORKAROUND: Use nouveau.

  WORKAROUND: Boot with already installed kernel 4.4.0-31-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-45-generic 4.4.0-45.66
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  lost   2248 F pulseaudio
   /dev/snd/controlC0:  lost   2248 F pulseaudio
   /dev/snd/controlC1:  lost   2248 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Nov  3 12:12:55 2016
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (1 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/xubuntu--vg-root ro nomodeset quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1674816] Re: nm-applet crashed with SIGSEGV in g_simple_async_result_complete()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nm-applet crashed with SIGSEGV in g_simple_async_result_complete()

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

Bug description:
  I performed

  sudo service network-manager restart

  and nm-applet crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 21 21:36:15 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nm-applet
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   #source /etc/network/interfaces.d/*.cfg
  InstallationDate: Installed on 2014-12-02 (839 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcCmdline: nm-applet
  SegvAnalysis:
   Segfault happened at: 0x7f9371eeb50d <__strstr_sse2_unaligned+77>:   movdqu 
(%rdi),%xmm3
   PC (0x7f9371eeb50d) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%xmm3" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: network-manager-applet
  StacktraceTop:
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
  Title: nm-applet crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1434591] Re: [mako] Cannot connect to a secure, shared "ap" hotspot

2017-03-21 Thread Fice

Wi-fi hotspot works on mako with the current build of LineageOS 14.1
(the successor of CyanogenMod). Will it help to port the kernel from
LineageOS?

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

Title:
  [mako] Cannot connect to a secure, shared "ap" hotspot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  $ system-image-cli -i
  current build number: 138
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-17 15:04:46
  version version: 138
  version ubuntu: 20150317.1
  version device: 20150210
  version custom: 20150317.1

  I have tried most types of security, but the spec [2] says for maximum
  compatibility, most of the options should be left blank. Blank
  settings failed on both a and bg bands.

  How to reproduce:
  1. Create a secure hotspot (I am using this [1] script)
  2. Confirm that the hotspot is active and appears secured for other devices

  What happens:
  Connecting to it fails.

  What should have happened:
  Connecting to it should not fail.

  Excerpt from syslog
  http://pastebin.ubuntu.com/10627959/

  Insecure hotspots should work using this [3] script.

  [1] http://pastebin.ubuntu.com/10683465/
  [2] https://developer.gnome.org/NetworkManager/stable/ref-settings.html
  [3] 
http://bazaar.launchpad.net/~mathieu-tl/+junk/touch-hotspot/view/head:/hotspot.py

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

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

[Desktop-packages] [Bug 1674811] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue Mar 21 21:12:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-29 (1422 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-14 (219 days ago)

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

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

[Desktop-packages] [Bug 1674811] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-03-21 Thread Heinrich Fehn

Public bug reported:

package tex-common 6.04 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Tue Mar 21 21:12:57 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-04-29 (1422 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-14 (219 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue Mar 21 21:12:57 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-04-29 (1422 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-14 (219 days ago)

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

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

[Desktop-packages] [Bug 1593549] Re: cannot install libvdpau1 as ffmpeg need

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

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

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

Title:
  cannot install libvdpau1 as ffmpeg need

Status in ffmpeg package in Ubuntu:
  Invalid
Status in libvdpau package in Ubuntu:
  Confirmed

Bug description:
  Trying to install ffmpeg and winff but it pulls in libvdpau1. But
  cannot install libvdpau1.

  sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic 
linux-image-4.4.0-21-generic
linux-image-extra-4.4.0-21-generic linux-signed-image-4.4.0-21-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libvdpau1
  The following NEW packages will be installed:
libvdpau1
  0 upgraded, 1 newly installed, 0 to remove and 8 not upgraded.
  5 not fully installed or removed.
  Need to get 0 B/25.5 kB of archives.
  After this operation, 100 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 437125 files and directories currently installed.)
  Preparing to unpack .../libvdpau1_1.1.1-3ubuntu1_amd64.deb ...
  Unpacking libvdpau1:amd64 (1.1.1-3ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libvdpau1_1.1.1-3ubuntu1_amd64.deb (--unpack):
   trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from 
other instances of package libvdpau1:amd64
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libvdpau1_1.1.1-3ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ffmpeg 7:2.8.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 17 06:28:13 2016
  InstallationDate: Installed on 2016-04-18 (59 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: ffmpeg
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (59 days ago)
  modified.conffile..etc.ffserver.conf: [deleted]

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

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

[Desktop-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2017-03-21 Thread Thomas Leonard

I've now uploaded zeroinstall-injector 2.12-4 to Debian. That should fix
the build problem here.

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  New
Status in apturl package in Ubuntu:
  New
Status in dell-recovery package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New
Status in lubuntu-software-center package in Ubuntu:
  New
Status in mythbuntu-control-centre package in Ubuntu:
  New
Status in sessioninstaller package in Ubuntu:
  New
Status in software-properties package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New
Status in ubuntu-mate-meta package in Ubuntu:
  New
Status in ubuntu-mate-welcome package in Ubuntu:
  New
Status in update-manager package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  Triaged
Status in aptdaemon source package in aa-series:
  New
Status in apturl source package in aa-series:
  New
Status in dell-recovery source package in aa-series:
  New
Status in gnome-software source package in aa-series:
  New
Status in language-selector source package in aa-series:
  New
Status in lubuntu-software-center source package in aa-series:
  New
Status in mythbuntu-control-centre source package in aa-series:
  New
Status in sessioninstaller source package in aa-series:
  New
Status in software-properties source package in aa-series:
  New
Status in ubiquity source package in aa-series:
  New
Status in ubuntu-mate-meta source package in aa-series:
  New
Status in ubuntu-mate-welcome source package in aa-series:
  New
Status in update-manager source package in aa-series:
  New
Status in update-notifier source package in aa-series:
  New

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://bitbucket.org/ubuntu-mate/ubuntu-mate-welcome/issues/48/port-
  from-aptdaemon-to-packagekit

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

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

[Desktop-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)

2017-03-21 Thread ChristianEhrhardt

The suggestion was made to add a accountsservice file for it like:
echo -e "[User]\nSystemAccount=true" > 
/var/lib/AccountsService/users/libvirt-qemu

I agree this might be an option - and I might even be forced to take it at some 
point, but then I ask myself for how many extra Desktop envs/services would we 
make extra files if more are found.
Do we really want to make this a custom change in all those packages (and any 
else in the future who add system users).
- OR -
Wouldn't it make much much more sense to make accountsservice realize on non 
login shells as all other logins seem to do (e.g. sddm) and as itself did in 
the past (hidden-shells)?

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

Title:
  System users appears in Ligthdm and user switcher (Accountsservice has
  no filter for shell types)

Status in accountsservice package in Ubuntu:
  Confirmed
Status in base-passwd package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Confirmed
Status in ifmail package in Ubuntu:
  Confirmed
Status in libvirt package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in netqmail package in Ubuntu:
  Confirmed

Bug description:
  "Technical" user libvirt Qemu appears in the list of user in Ligthdm,
  among the real regular users. It probably shouldn't

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libvirt-bin 2.5.0-3ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Wed Feb 22 22:09:24 2017
  InstallationDate: Installed on 2017-02-01 (21 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201)
  KernLog:
   
  SourcePackage: libvirt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1614593] Re: gimp freezes at end of cage-base transform

2017-03-21 Thread A. Scheuer

Please notice that the "Fix Released" status only concerns Gimp
development, not Gimp / Ubuntu...  I am still waiting for an Ubuntu fix,
working with a (partially ill-) patched Gimp.

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

Title:
  gimp freezes at end of cage-base transform

Status in The Gimp:
  Fix Released
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  
  Hello.

  I am currently unable to apply the cage-base transform, whatever the
  image: at the end of the two first computations (creation of the cage
  and first deformation), gimp freezes (at the last pixel of the
  circle)!

  And no way to get it back...  Except closing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 18 17:36:44 2016
  InstallationDate: Installed on 2013-07-29 (1116 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (18 days ago)

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

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

[Desktop-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

2017-03-21 Thread Igor

** Attachment added: "xorg_after_lightdm.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841880/+files/xorg_after_lightdm.txt

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubun

[Desktop-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

2017-03-21 Thread Igor

** Attachment added: "xorg_faileed_monitor_detect.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841879/+files/xorg_faileed_monitor_detect.txt

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/n

[Desktop-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

2017-03-21 Thread Igor

Here you go:

** Attachment added: "logind.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1672033/+attachment/4841878/+files/logind.txt

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/16

[Desktop-packages] [Bug 1614593] Re: gimp freezes at end of cage-base transform

2017-03-21 Thread Dave Rove

"Fix Released" status is incorrect.

This is not fixed upstream but still requires action by the package
maintainer.

As others have pointed out, the only way to fix this problem for GIMP
2.8 is to build it against GECL 0.2 as is done upstream rather than the
Ubuntu-special build against GECL 0.3. This problem will of course go
away with GIMP 2.10 whenever that day comes, but marking this build as
"fix released" means that it will remain broken in Ubuntu 17.04 and
probably 17.10 as well.

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

Title:
  gimp freezes at end of cage-base transform

Status in The Gimp:
  Fix Released
Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  
  Hello.

  I am currently unable to apply the cage-base transform, whatever the
  image: at the end of the two first computations (creation of the cage
  and first deformation), gimp freezes (at the last pixel of the
  circle)!

  And no way to get it back...  Except closing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gimp 2.8.16-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Aug 18 17:36:44 2016
  InstallationDate: Installed on 2013-07-29 (1116 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gimp
  UpgradeStatus: Upgraded to xenial on 2016-07-30 (18 days ago)

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

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

[Desktop-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly

2017-03-21 Thread Cesar Herrera

In E4.5 with OTA-15
It makes a vibration.

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

Title:
  [Touch] Incoming call gets silent randomly

Status in Canonical System Image:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've experienced this strange issue 4-5 times after OTA-12. It seems pretty 
random and is hard to reproduce.
  When I get an incoming call, the screen turns on, the incoming call pop up 
appears, but there is no sound at all even though the phone is not in silent 
mode (and also the speaker volume is not set too low). I can accept this call 
and keep conversing as usual.
  Once I asked the same caller to call me once again after a few minutes, that 
time the phone rang as expected.

  Device: E5, OTA-12, stable channel

  I can provide necessary logs if this happens again. Which ones should
  I gather?

  Possibly related to bug #1614943.

  UPDATE: As mentioned in comment #7, it seems the phone rings for a
  fraction of a second and then the sound pauses abruptly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions

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

[Desktop-packages] [Bug 1674005] Re: audiofile: Multiple security issues from March 2017

2017-03-21 Thread Marc Deslauriers

ACK on the debdiffs in comments 1, 2 and 3. I'm building them now with a
slight change to add a missing CVE. I'll publish them once I've finished
backporting to precise and have tested precise and trusty.

Thanks!


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

** Also affects: audiofile (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  audiofile: Multiple security issues from March 2017

Status in audiofile package in Ubuntu:
  New
Status in audiofile source package in Precise:
  New
Status in audiofile source package in Trusty:
  New
Status in audiofile source package in Xenial:
  New
Status in audiofile source package in Yakkety:
  New

Bug description:
  https://security-tracker.debian.org/tracker/source-package/audiofile
  http://openwall.com/lists/oss-security/2017/02/26/
  https://github.com/mpruett/audiofile/issues/32
  
https://blogs.gentoo.org/ago/2017/02/20/audiofile-heap-based-buffer-overflow-in-msadpcminitializecoefficients-msadpcm-cpp
  https://github.com/mpruett/audiofile/commit/c48e4c6503

  
  Fixed in Debian unstable 0.3.6-4 and synced to zesty.

  debdiffs attached for 14.04 LTS and up. For 12.04 LTS, audiofile was
  in main so someone should probably try to apply the patches there too.

  I've done no testing of these packages.

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

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

[Desktop-packages] [Bug 1674769] Re: package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: package libpurple-bin is already installed and configured

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1674768
   package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: package 
libpurple-bin is already installed and configured

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

Title:
  package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade:
  package libpurple-bin is already installed and configured

Status in pidgin package in Ubuntu:
  New

Bug description:
  I try to install Transmaggedon, and gstreamer. There was a package
  named gstreamer ffmpeg. I choose to install. The installation began,
  but that stop because there is no more package gstreamer for ffmpeg.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpurple-bin 1:2.10.9-0ubuntu3.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Tue Mar 21 18:23:37 2017
  DuplicateSignature: package:libpurple-bin:1:2.10.9-0ubuntu3.4:package 
libpurple-bin is already installed and configured
  ErrorMessage: package libpurple-bin is already installed and configured
  InstallationDate: Installed on 2017-03-12 (9 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pidgin
  Title: package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: 
package libpurple-bin is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1674769] [NEW] package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: package libpurple-bin is already installed and configured

2017-03-21 Thread Veronique VELTER

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

Public bug reported:

I try to install Transmaggedon, and gstreamer. There was a package named
gstreamer ffmpeg. I choose to install. The installation began, but that
stop because there is no more package gstreamer for ffmpeg.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpurple-bin 1:2.10.9-0ubuntu3.4
ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
Uname: Linux 3.13.0-112-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: amd64
Date: Tue Mar 21 18:23:37 2017
DuplicateSignature: package:libpurple-bin:1:2.10.9-0ubuntu3.4:package 
libpurple-bin is already installed and configured
ErrorMessage: package libpurple-bin is already installed and configured
InstallationDate: Installed on 2017-03-12 (9 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: pidgin
Title: package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: 
package libpurple-bin is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package trusty

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

Title:
  package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade:
  package libpurple-bin is already installed and configured

Status in pidgin package in Ubuntu:
  New

Bug description:
  I try to install Transmaggedon, and gstreamer. There was a package
  named gstreamer ffmpeg. I choose to install. The installation began,
  but that stop because there is no more package gstreamer for ffmpeg.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpurple-bin 1:2.10.9-0ubuntu3.4
  ProcVersionSignature: Ubuntu 3.13.0-112.159-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-112-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Tue Mar 21 18:23:37 2017
  DuplicateSignature: package:libpurple-bin:1:2.10.9-0ubuntu3.4:package 
libpurple-bin is already installed and configured
  ErrorMessage: package libpurple-bin is already installed and configured
  InstallationDate: Installed on 2017-03-12 (9 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: pidgin
  Title: package libpurple-bin 1:2.10.9-0ubuntu3.4 failed to install/upgrade: 
package libpurple-bin is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1639019] Re: Include NVidia driver version 375.10+ for GTX1050(Ti)

2017-03-21 Thread nmaxx

Considering 375.39 was just release for Xenial, I guess we can consider
this one closed. :)

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

Title:
  Include NVidia driver version 375.10+ for GTX1050(Ti)

Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed

Bug description:
  The SRU Request for inclusion of NVidia driver version 367 
(https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1619306) 
unfortunately does not cover the latest two Pascal GPUs: GTX 1050 and GTX 
1050Ti.
  Those are supported by driver version 375.10 and up 
(http://www.nvidia.com/download/driverResults.aspx/109739/en-us).
  Therefore please consider adding the 375 drivers as well for 
Xenial/Yakkety/etc.

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

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

[Desktop-packages] [Bug 1672491] Re: New NetworkManager breaks VPN DNS.

2017-03-21 Thread Nicolás Abel Carbone

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

** This bug has been marked a duplicate of bug 1671606
   DNS server from vpn connection is not being used after network-manager 
upgrade to 1.2.6-0ubuntu0.16.04.1

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

Title:
  New NetworkManager breaks VPN DNS.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Alright, this is going to be a frustrating bug for everyone involved I
  expect, but here goes.

  On Ubuntu 16.04, using a non-released VPN client (making this _much_
  harder for anyone to reproduce), upgrading the network-manager
  packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite
  handily broke DNS over the VPN.

  And it broke it really oddly.

  dnsmasq binds to socket 12 for the new interface, just fine.

  strace shows that it does the sendto for the DNS request, and that the
  poll calls are working, just fine.

  tcpdump shows the response messages, they are coming back from the
  correct host and port, going to my IP and the port that dnsmasq is
  sending from.

  There are no iptables rules involved, nothing is set to deny.

  dnsmasq is never getting the response packet.

  The request thus times out.

  Doing a host or dig directly to the DNS server works just fine.

  And this is completely reproducible, and goes away the moment I
  downgrade back to 1.2.2-0ubuntu0.16.04.3.

  Was there some change to how network-manager handles VPN
  interfaces/tap0 in the new version?

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

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

[Desktop-packages] [Bug 1668013] Re: soffice.bin crashed with SIGSEGV in _xcb_conn_wait()

2017-03-21 Thread RussianNeuroMancer

** Information type changed from Private to Public

** Description changed:

  LibreOffice crash on start after upgrade to 5.3.0 in Kubuntu 17.04 Beta.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-core 1:5.3.0~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 26 15:40:31 2017
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  ExecutableTimestamp: 1487040521
  InstallationDate: Installed on 2011-04-03 (2155 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
- ProcCwd: /home/nikita
  SegvAnalysis:
-  Segfault happened at: 0x7ff0923ebbf6:mov%rax,0xa8(%rsp)
-  PC (0x7ff0923ebbf6) ok
-  source "%rax" ok
-  destination "0xa8(%rsp)" (0x7ffc6bb09ff8) not located in a known VMA region 
(needed writable region)!
-  Stack memory exhausted (SP below stack segment)
+  Segfault happened at: 0x7ff0923ebbf6:mov%rax,0xa8(%rsp)
+  PC (0x7ff0923ebbf6) ok
+  source "%rax" ok
+  destination "0xa8(%rsp)" (0x7ffc6bb09ff8) not located in a known VMA region 
(needed writable region)!
+  Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
-  ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
-  ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
-  xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
-  _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
-  _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
+  ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
+  ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
+  xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
+  _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
+  _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: soffice.bin crashed with SIGSEGV in xcb_writev()
  UpgradeStatus: Upgraded to zesty on 2015-04-17 (680 days ago)
  UserGroups: adm audio cdrom dialout libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

Title:
  soffice.bin crashed with SIGSEGV in _xcb_conn_wait()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice crash on start after upgrade to 5.3.0 in Kubuntu 17.04
  Beta.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-core 1:5.3.0~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 26 15:40:31 2017
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  ExecutableTimestamp: 1487040521
  InstallationDate: Installed on 2011-04-03 (2155 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7ff0923ebbf6:mov%rax,0xa8(%rsp)
   PC (0x7ff0923ebbf6) ok
   source "%rax" ok
   destination "0xa8(%rsp)" (0x7ffc6bb09ff8) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
   xcb_writev () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
   _XSend () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
  Title: soffice.bin crashed with SIGSEGV in xcb_writev()
  UpgradeStatus: Upgraded to zesty on 2015-04-17 (680 days ago)
  UserGroups: adm audio cdrom dialout libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

[Desktop-packages] [Bug 1672003] Re: soffice.bin crashed with SIGSEGV in XQueryPointer()

2017-03-21 Thread RussianNeuroMancer

** Information type changed from Private 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/1672003

Title:
  soffice.bin crashed with SIGSEGV in XQueryPointer()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice crash on start after upgrade to 5.3.0 in Kubuntu 17.04
  Beta.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: libreoffice-core 1:5.3.0~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1
  Uname: Linux 4.10.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: KDE
  Date: Tue Mar  7 09:39:11 2017
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2011-04-03 (2168 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   XQueryPointer () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   X11SalFrame::Init(SalFrameStyleFlags, SalX11Screen, SystemParentData*, bool) 
() from /usr/lib/libreoffice/program/libvclplug_genlo.so
   X11SalFrame::X11SalFrame(SalFrame*, SalFrameStyleFlags, SystemParentData*) 
() from /usr/lib/libreoffice/program/libvclplug_genlo.so
   ?? () from /usr/lib/libreoffice/program/libvclplug_kde4lo.so
   ?? () from /usr/lib/libreoffice/program/libvclplug_kde4lo.so
  Title: soffice.bin crashed with SIGSEGV in XQueryPointer()
  UpgradeStatus: Upgraded to zesty on 2015-04-17 (693 days ago)
  UserGroups: adm audio cdrom dialout libvirt libvirtd lpadmin plugdev 
sambashare sudo

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

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

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

2017-03-21 Thread Rémi Denis-Courmont

Closing VLC bug as already explained in previous comment.

** Changed in: vlc (Ubuntu)
   Status: Confirmed => Invalid

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1603600] Re: NetworkManager ignores pushed openvpn routes

2017-03-21 Thread Ben

Hi,
I am also affected by this bug. Any chance to ask maintainers to upgrade both
packages?

https://wiki.gnome.org/Projects/NetworkManager
https://git.gnome.org/browse/network-manager-openvpn

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

Title:
NetworkManager ignores pushed openvpn routes

Status in network-manager-openvpn package in Ubuntu:
Confirmed

Bug description:
Relevant information that may or may not have been included by ubuntu-
bug:

Ubuntu release 16.04
Package network-manager 1.2.0-0ubuntu0.16.04.2
Package network-manager-openvpn 1.1.93-1ubuntu1

NetworkManager ignores pushed openvpn routes when "Use this connection
only for resources on its network" is checked. This is a behavior
change since 14.04.

To repeat:

1) Use an OpenVpn server that pushes routes. I suggest using a server
that pushes several routes since this makes their absence obvious.
Set up a NetworkManager VPN of type OpenVpn to this server. Select
"Use this connection only for resources on its network" in the
"Routes" section of the IPV4 options.

2) Set up a raw OpenVpn connection to the same server.

3) Connect to the server using the raw OpenVpn connection. The pushed
routes are all there.

4) Connect to the server using NetworkManager. The only route added
is a n interface level route to the tunnel device network.

Using the same setup on 14.04, all pushed routes are added.

The missing routes are also "Resources on the VPN network", and should be
added in the absence of further direction. Ignoring pushed routes should be
controlled by the "Ignore automatically obtained routes" checkbox.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager-openvpn 1.1.93-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jul 15 23:12:55 2016
InstallationDate: Installed on 2016-05-04 (72 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1674113] Re: libreoffice snap unable to open files international file names

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

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

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

Title:
  libreoffice snap unable to open files international file names

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Context:
  ubuntu 16.10 amd64
  libreoffice snap package

  Steps to recreate:
  Symptom 1:
  Use file open dialog: all non English (latin, ascii) (e.g. Arabic) filenames 
appear empty with file size 0 bytes

  Symptom 2:
  Doubleclick any non English (latin, ascii) (e.g. Arabic) libreoffice 
associated (.odt, .ods, ...) file, the correct libreoffice application will 
open then you will receive a file not found error with garbled file name in the 
error message.

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

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

[Desktop-packages] [Bug 1672424] Re: Cannot install Debian files outside of the repositories

2017-03-21 Thread Jeremy Bicha

Robert, does it matter that your computer uses a solid state disk drive?
I don't have a SSD.

** Tags added: rls-z-incoming

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

Title:
  Cannot install Debian files outside of the repositories

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Xenial:
  Confirmed
Status in gnome-software source package in Yakkety:
  Confirmed

Bug description:
  Impact
  --
  It is not possible to use the default Software app to install .debs for 
packages that are not already available in Ubuntu.

  Test Case
  -
  1.
  a. Download the .deb for a simple app for your version of Ubuntu directly 
from Launchpad.
  For 16.10, try 
https://launchpad.net/ubuntu/+source/gnome-clocks/3.22.1-0ubuntu1/
  Click amd64 then download the last .deb on that page.

  b. Open the .deb with gnome-software:
  gnome-software --local-filename=gnome-clocks_3.22.1-0ubuntu1_amd64.deb

  gnome-software should open to a page with an Install button for the
  package.

  This test case should already work.

  2.
  a. Download a .deb that is not already in Ubuntu.
  It is important that the package not be available in your local apt cache.
  For this, I made sure that I was not using the GNOME3 Staging PPA. As of 
today, switcheroo-control is not accepted into Ubuntu 17.04.

  So I downloaded
  https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+files
  /switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb

  b. Open the .deb with gnome-software
  gnome-software 
--local-filename=switcheroo-control_1.1-0ubuntu0~zesty1_amd64.deb

  I only suggested using switcheroo-control because I know it's not because the 
package isn't packaged correctly. Alternatively, this test case should also 
work with one of these:
  https://www.google.com/chrome/
  https://itch.io/app

  gnome-software should open to a page with an Install button for the
  package.

  What Happens
  
  The second test fails. On Ubuntu 17.04, I get a popup
  "Sorry this did not work The file is not supported"

  On Ubuntu 16.04 LTS or 16.10, I get "Sorry this did not work No
  file_to_app results to show"

  Regression Potential
  

  Original Bug Report
  ---
  .deb files fail to install from non repository locations i.e. The file 
manager gnome-software claims "this file type is not supported".

  Using dpkg from the command line works as expected so the files aren't
  corrupt. This happened last distribution as well when it was first
  released. Might be a regression caused by adding snap package
  capabilities to the software-center?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-software 3.22.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Mar 13 10:02:00 2017
  InstallationDate: Installed on 2017-02-20 (20 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to zesty on 2017-02-28 (12 days ago)

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

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

[Desktop-packages] [Bug 1673625] Re: 10-globally-managed-devices.conf contained in wrong package

2017-03-21 Thread Brian Murray

I don't think many people are still upgrading from Xenial to Yakkety but
this'll likely be important to fix for people upgrading from 16.04 to
18.04.

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

Title:
  10-globally-managed-devices.conf contained in wrong package

Status in network-manager package in Ubuntu:
  Confirmed
Status in nplan package in Ubuntu:
  Incomplete

Bug description:
  /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
  installed from network-manager but without nplan it has no benefit,
  and breaks networking until you override it.  Since the config is
  there to change how NetworkManager behaves in the presence of nplan,
  the configuration file itself should actually be contained in the
  nplan package.

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

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

[Desktop-packages] [Bug 1553441] Re: [Asus K55DR] When VGA plugged into laptop, only one monitor working at a time

2017-03-21 Thread lazanet

** Tags removed: kernel-bug-exists-upstream-4.11-rc1
** Tags added: kernel-bug-exists-upstream-4.11-rc3

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

Title:
  [Asus K55DR] When VGA plugged into laptop, only one monitor working at
  a time

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

Bug description:
  Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=99784
  When my ASUS VW193 external monitor is connected to the VGA port of my laptop 
(AMD Radeon 7470m) internal laptop monitor stops working. Using the Unity 
Control Center I'm able to set laptop monitor as primary which disables 
external monitor (and vice-versa). Tried manual switch to mainline Linux 4.5 
kernel, same thing. Tested on 14.04, 15.10, 16.04 with same results.

  However, if I plug the Asus monitor into the laptop via VGA, plug my
  Vox TV into the laptop via HDMI, and set the resolution to 1280x720,
  it displays fine on both the monitor and TV.

  Also, the internal monitor and just HDMI together show properly.

  However, if I adjust to 1080i, the above working dual screen configurations 
show a graphical glitch:
  https://launchpadlibrarian.net/302517159/IMG_20170114_225834.jpg

  WORKAROUND: Use Ubuntu 14.04 with fglrx.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.5.0-040500rc6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.20-0ubuntu3
  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 Mar  5 04:32:48 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.4.0-10-generic, x86_64: installed
   virtualbox, 5.0.14, 4.4.0-8-generic, x86_64: installed
   virtualbox, 5.0.14, 4.5.0-040500rc6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903] 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7640G] [1043:106b]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2016-02-18 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. K55DR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.0-040500rc6-generic 
root=UUID=e0064410-4660-40b7-b961-76f320a921a6 ro amdgpu.powerplay=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 217
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K55DR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr217:bd09/07/2012:svnASUSTeKCOMPUTERINC.:pnK55DR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55DR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K55DR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  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.18.1-1ubuntu3
  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.6.1-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Mar  5 04:27:41 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.1-1ubuntu3
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1674704] [NEW] blank screen after software update

2017-03-21 Thread giuseppe

Public bug reported:

I ran "sudo apt-get upgrade" and after rebooting I started to have
problems with the display. Now it's black even from the boot options
screen (I mean before GRUB menu). I left the system go up end after
connecting via ssh I could see the following in dmesg:

[  796.633789] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  797.133525] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(8).
[  797.133531] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  797.633326] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(9).
[  797.61] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  798.133117] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(10).
[  798.133122] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  798.632897] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(11).
[  798.632903] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  799.132682] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(12).
[  799.132687] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  799.632462] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(13).
[  799.632467] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  800.132257] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(14).
[  800.132263] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  800.632060] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(15).
[  800.632065] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  801.131826] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(0).
[  801.131832] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  801.631619] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(1).
[  801.631624] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  802.131420] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(2).
[  802.131426] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
[  802.631209] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule IB(3).


$ uname -a
Linux ajax 3.2.0-124-generic #167-Ubuntu SMP Fri Mar 3 15:25:36 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux

Any suggestion?

Thanks in advance,

Giuseppe

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-124.167-generic 3.2.79
Uname: Linux 3.2.0-124-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.15
Architecture: amd64
Date: Tue Mar 21 15:25:55 2017
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
MarkForUpload: True
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise

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

Title:
  blank screen after software update

Status in xorg package in Ubuntu:
  New

Bug description:
  I ran "sudo apt-get upgrade" and after rebooting I started to have
  problems with the display. Now it's black even from the boot options
  screen (I mean before GRUB menu). I left the system go up end after
  connecting via ssh I could see the following in dmesg:

  [  796.633789] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  797.133525] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(8).
  [  797.133531] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  797.633326] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(9).
  [  797.61] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  798.133117] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(10).
  [  798.133122] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  798.632897] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(11).
  [  798.632903] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  799.132682] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(12).
  [  799.132687] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  799.632462] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(13).
  [  799.632467] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  800.132257] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(14).
  [  800.132263] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  800.632060] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(15).
  [  800.632065] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  801.131826] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(0).
  [  801.131832] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  801.631619] [drm:radeon_ib_schedule] *ERROR* radeon: couldn't schedule 
IB(1).
  [  801.631624] [drm:radeon_cs_ioctl] *ERROR* Failed to schedule IB !
  [  802.131420] [drm

[Desktop-packages] [Bug 1668593] Re: Wireless adapter causes hard crash

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

Title:
  Wireless adapter causes hard crash

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to a wifi using a USB wifi adapter, the system
  crashes/freezes immediately. There is nothing in the syslog or
  anywhere else. This can be reproduced on Ubuntu 14.04 and 16.04.
  Enabling the adapter works, but the freeze occurs as soon as I try to
  log into the network.

  This used to work, but has been broken for a few weeks I assume. It
  happens with all USB adapters I tested, on all machines.

  Adapter 1:

     description: Wireless interface
     physical id: 1
     bus info: usb@2:1.1.1
     logical name: wlx74da388dc809
     serial: [redacted]
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=rtl8192cu 
driverversion=4.4.0-64-generic firmware=N/A link=no multicast=yes wireless=IEEE 
802.11bgn

  Adapter 2:

     description: Wireless interface
     physical id: 1
     bus info: usb@2:1.1.1
     logical name: wlx24050f75f9a2
     serial: [redacted]
     capabilities: ethernet physical wireless
     configuration: broadcast=yes driver=rtl8192cu 
driverversion=4.4.0-64-generic firmware=N/A link=no multicast=yes wireless=IEEE 
802.11bgn

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

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

[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-03-21 Thread Łukasz Zemczak

Could anyone make sure that this bug is also fixed for yakkety (the
original bug target) and zesty? In that case I suppose we could finally
close this bug and remove it from the sponsorship queue.

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

Title:
WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
required to fix it.

Status in OEM Priority Project:
Fix Released
Status in OEM Priority Project xenial series:
Fix Released
Status in network-manager package in Ubuntu:
Confirmed

Bug description:
HOW TO REPRODUCE:
1. Install fwts by `sudo apt-get install fwts`.
2. Run the suspend & resume stress test.
sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5
--s3-delay-delta=5

RESULT:
The WiFi can not connect to any access point and we have to execute `sudo
wpa_cli scan` manually to make it work again.

WORKAROUND:

(http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend-after-16-04-upgrade)

SYSTEM INFO:
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
Packages:
libnm-glib-vpn1:amd64 1.2.2-0ubuntu2
libnm-glib4:amd64 1.2.2-0ubuntu2
libnm-util2:amd64 1.2.2-0ubuntu2
libnm0:amd641.2.2-0ubuntu2
network-manager 1.2.2-0ubuntu2

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

[Desktop-packages] [Bug 1636564] Re: Segfault from libX11.so.6.3.0

2017-03-21 Thread Jan Lachnitt

Although the referenced bug regards Nvidia, some comments mention
similar problems with Radeon (and I'm not using Nvidia drivers either -
I have integrated Intel graphics). My main point was that the syslog
lists other errors before the segfault, so this can be a result rather
than the cause. I could not find a syslog in your report.

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

Title:
  Segfault from libX11.so.6.3.0

Status in libx11 package in Ubuntu:
  Confirmed

Bug description:
  Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
  got back to the system Mattermost and a Chrome were indicating that
  the network was not working.  I started to look about and it seemed
  that my main ethernet network connection had lost its IPv4 address
  somehow.  ifconfig and the GUI network manager confirmed this.

  To try and resolve this I physically removed the connector and the
  plugged it back in.  Shortly after I did this my GUI seemed to die out
  and I ended up back at the login screen.

  Once everything had calmed down I logged back in.  After some digging
  about in the logs I noticed the following in /var/log/kern.log

  Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]: 
segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in 
libX11.so.6.3.0[7f8a9e22f000+135000]
  Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]: segfault at 
968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in 
libX11.so.6.3.0[7fd4b5c4b000+135000]

  That seemed to be the correct time for the problem I noticed.   What
  exactly caused it I am not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libx11-6 2:1.6.3-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Oct 25 17:07:28 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2015-03-12 (592 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. H81M-DS2V
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: libx11
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-DS2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd08/11/2015:svnGigabyteTechnologyCo.,Ltd.:pnH81M-DS2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H81M-DS2V
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Oct 25 13:01:04 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   30926 
   vendor BNQ
  xserver.version: 2:1.18.4-0ubuntu0.1

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

[Desktop-packages] [Bug 1674121] Re: "Restore" asks for cryptic authentication to run /bin/sh as superuser

2017-03-21 Thread Christopher Barrington-Leigh

Result of following attached:

gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

** Attachment added: "deja-dup.gsettings"
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1674121/+attachment/4841599/+files/deja-dup.gsettings

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

Title:
  "Restore" asks for cryptic authentication to run /bin/sh as superuser

Status in deja-dup package in Ubuntu:
  Incomplete

Bug description:
  I am trying to restore a full backup to an external hard drive.
  After 20 minutes or so, a cryptic gui popup arises which says that "some 
process" wants sudo authentication to run /bin/sh

  It is surely a bug to generate such a vague request for sudo use.

  I note it has been this way since 2013
  (https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1079553 which
  has been unaddressed, so the outcome of denying this request is still
  a great pain), but I am pointing out that this kind of permission
  request is itself a bug, if not a security risk because it teaches
  users to give that kind of permission to an unknown script.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: deja-dup 34.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 19 12:35:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-02-12 (400 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to yakkety on 2017-01-21 (56 days ago)

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

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

[Desktop-packages] [Bug 1674674] Re: Xorg crashed with SIGABRT in OsAbort()

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1543192
   Xorg crashed with SIGABRT in OsAbort()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  Xorg crashed with SIGABRT in OsAbort()

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.18.4-1ubuntu9
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je adresár: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 6.3.0 20170316 (Ubuntu 6.3.0-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu2
  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
  CrashCounter: 1
  Date: Tue Mar 21 13:03:16 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3901]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GF108M [GeForce GT 630M] [17aa:3901]
  InstallationDate: Installed on 2017-02-26 (22 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170226)
  MachineType: LENOVO Lenovo G780
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=52f06d69-b240-4567-bdb1-070368ca4745 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x55a96cb89300, argc=11, argv=0x7fffb835a2a8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fffb835a298) at ../csu/libc-start.c:291
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN96WW(V9.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: INVALID
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G780
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN96WW(V9.01):bd03/14/2013:svnLENOVO:pnLenovoG780:pvrLenovoG780:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrLenovoG780:
  dmi.product.name: Lenovo G780
  dmi.product.version: Lenovo G780
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.

[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer

2017-03-21 Thread Alberto Mardegan

Eugene (and others), if you are still affected by this bug, please
follow bug 1666285 instead.

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  Fix Released
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in account-plugins package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in signon-plugin-oauth2 package in Ubuntu:
  Fix Released
Status in account-plugins source package in Quantal:
  Fix Released
Status in signon-plugin-oauth2 source package in Quantal:
  Fix Released
Status in account-plugins source package in Trusty:
  Fix Released
Status in evolution-data-server source package in Trusty:
  Fix Released
Status in signon-plugin-oauth2 source package in Trusty:
  Fix Released

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case] Disable/re-enable your Google account. When affected by
  this bug, a notification will appear and you'll be asked to enter your
  Google password in the Online Accounts panel in System Settings.

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  Old description
  ===

  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions

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

[Desktop-packages] [Bug 1673850] Re: Problem with video after suspend

2017-03-21 Thread Timo Aaltonen

you're using amdgpu-pro, we can't support that

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

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

Title:
  Problem with video after suspend

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After my laptop goes from suspended state (sleep) I'm not able to
  adjust screen brightness. It goes to maximum brightness and no longer
  adjusted until laptop reboot. It's hard for my eyes to continue work.
  I don't know is it xorg problem, or amdgpu but I will do my best to
  help you to solve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Mar 17 20:09:53 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu-pro, 16.60-379184, 4.4.0-66-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-31-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-64-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b5]
 Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] 
[103c:80b5]
  InstallationDate: Installed on 2017-03-07 (10 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=433c8aa2-a343-4d03-8144-288b5cbc37f9 ro nopat vesafb.invalid=1 splash 
quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B5
  dmi.board.vendor: HP
  dmi.board.version: 81.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.13:bd08/06/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.28:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  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: Fri Mar 17 20:03:39 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2017-03-21 Thread Stephane Epardaud

Got hit by that one and lost several hours until I found the described
workaround in the duplicate issue. This is really very bad. It prevents
ethernet users from using network-manager-defined VPNs too.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

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

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

[Desktop-packages] [Bug 1673286] Re: /usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read

2017-03-21 Thread Vlad Orlov

** Package changed: mate-media (Ubuntu) => libxcb (Ubuntu)

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

Title:
  /usr/bin/mate-volume-control-
  
applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read

Status in libxcb 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/31206cc9f08f903a2d53a96328a56c00a5561c3a 
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/libxcb/+bug/1673286/+subscriptions

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

[Desktop-packages] [Bug 1664777] Re: /usr/bin/marco:11:_int_malloc:GI_libc_malloc:GI_libc_realloc:_cairo_array_grow_by:_cairo_array_allocate

2017-03-21 Thread Vlad Orlov

** Package changed: marco (Ubuntu) => cairo (Ubuntu)

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

Title:
  
/usr/bin/marco:11:_int_malloc:__GI___libc_malloc:__GI___libc_realloc:_cairo_array_grow_by:_cairo_array_allocate

Status in cairo package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
marco.  This problem was most recently seen with package version 1.12.1-1, the 
problem page at 
https://errors.ubuntu.com/problem/a5e43a4db54dc9a36b6a39dec8f2adc85a2fd50a 
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/cairo/+bug/1664777/+subscriptions

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

[Desktop-packages] [Bug 1673286] [NEW] /usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:GI_libc_malloc:read_packet:_xcb_in_read

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/31206cc9f08f903a2d53a96328a56c00a5561c3a 
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: libxcb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial
-- 
/usr/bin/mate-volume-control-applet:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:read_packet:_xcb_in_read
https://bugs.launchpad.net/bugs/1673286
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libxcb 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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-03-21 Thread FFab

Upstream kernel test - kernel 4.11-rc3

Installation without errors.


booting (no workaround) > 3 min
no local login 
remote login (ssh)

dmesg: some errors

backlight: as formerly described

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1668467] Re: gnome-calculator, you can open the Preferences window multiple times, making the window transparent the second time

2017-03-21 Thread Alan Griffiths

Not happening in miral-shell with the latest gtk to land in Zesty

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

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

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

Title:
  gnome-calculator, you can open the Preferences window multiple times,
  making the window transparent the second time

Status in Canonical System Image:
  Confirmed
Status in MirAL:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in miral package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 17.04 unity8

  gnome-calculator, you can open the Preferences window many times,
  making the window transparent the second time (see screenshot)

  it doesn't work with About or Keyboard Shortcuts, only with
  Preferences.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668467/+subscriptions

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

[Desktop-packages] [Bug 1664777] [NEW] /usr/bin/marco:11:_int_malloc:GI_libc_malloc:GI_libc_realloc:_cairo_array_grow_by:_cairo_array_allocate

You have been subscribed to a public bug:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
marco.  This problem was most recently seen with package version 1.12.1-1, the 
problem page at 
https://errors.ubuntu.com/problem/a5e43a4db54dc9a36b6a39dec8f2adc85a2fd50a 
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: cairo (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: wily xenial
-- 
/usr/bin/marco:11:_int_malloc:__GI___libc_malloc:__GI___libc_realloc:_cairo_array_grow_by:_cairo_array_allocate
https://bugs.launchpad.net/bugs/1664777
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to cairo 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 1639517] Re: [HP Pavilion Notebook - 17-g164ng] black screen when booting

2017-03-21 Thread FFab

** Tags removed: kernel-bug-exists-upstream-4.11-rc2
** Tags added: kernel-bug-exists-upstream-4.11-rc3

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

Title:
  [HP Pavilion Notebook - 17-g164ng] black screen when booting

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When booting the screen is black – backlight on – off - on.
  When HDD is inactive
  - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or 
Strg + Alt + Del
  - remote access e.g. using ssh is possible

  Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10.

  My notebook is a HP Pavilion  17-g164ng with an AMD A10-8780P APU and
  2 graphic subsystems - Carrizo, a VGA compatible controller and Topaz.

  It seems very similar to that described in #1597079.

  The bug report was generated from a remote PC. My HP notebook was started 
without any workaround parameters.
  This apport doesn't display the second graphic subsystem Topaz R7 as an 
apport generated with nomodeset xforcevesa.

  WORKAROUND: In 14.04 and 15.10 I installed fglrx – the AMD driver.

  WORKAROUND: When booting in UEFI mode, use kernel parameters:
  nomodeset

  or:
  nomodeset xforcevesa

  Resolution without xforcevesa: 800x600
  Resolution with xforcevesa: 1600x900 – the optimal resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Nov  5 23:40:19 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Carrizo [103c:80b6]
  InstallationDate: Installed on 2016-11-03 (2 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B6
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Nov  5 23:32:11 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.1
  xserver.video_driver: amdgpu

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

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

[Desktop-packages] [Bug 1674646] [NEW] package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2017-03-21 Thread jvatec

Public bug reported:

Me avisa de un error en Chromium al arrancar el ordenador pero en
realidad no noto nada.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268
ProcVersionSignature: Ubuntu 4.4.0-66.87-lowlatency 4.4.44
Uname: Linux 4.4.0-66-lowlatency i686
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
Date: Tue Mar 21 11:43:36 2017
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2016-10-27 (144 days ago)
InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: chromium-browser
Title: package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed
  to install/upgrade: problemas de dependencias - se deja sin configurar

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Me avisa de un error en Chromium al arrancar el ordenador pero en
  realidad no noto nada.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268
  ProcVersionSignature: Ubuntu 4.4.0-66.87-lowlatency 4.4.44
  Uname: Linux 4.4.0-66-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue Mar 21 11:43:36 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-10-27 (144 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: chromium-browser
  Title: package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed 
to install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1674646] Re: package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed to install/upgrade: problemas de dependencias - se deja sin configurar

** Tags removed: need-duplicate-check

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

Title:
  package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed
  to install/upgrade: problemas de dependencias - se deja sin configurar

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Me avisa de un error en Chromium al arrancar el ordenador pero en
  realidad no noto nada.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268
  ProcVersionSignature: Ubuntu 4.4.0-66.87-lowlatency 4.4.44
  Uname: Linux 4.4.0-66-lowlatency i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Tue Mar 21 11:43:36 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2016-10-27 (144 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: chromium-browser
  Title: package chromium-browser-l10n 56.0.2924.76-0ubuntu0.16.04.1268 failed 
to install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1655997] Re: [gtk] Save as dialog: dropdown menu surface positioned wrong

2017-03-21 Thread Alan Griffiths

Not happening with the latest gtk to land in zesty

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

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

Title:
  [gtk] Save as dialog: dropdown menu surface positioned wrong

Status in GTK+:
  Fix Committed
Status in MirAL:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Running miral-shell and gedit:

  1. Burger-menu -> Save As
  2. Click the "Character encoding" or "Line ending" or "All files" dropdowns

  Bug: child surfaces are positioned incorrectly, should be under/over
  the widget that invoked them

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

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

[Desktop-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

2017-03-21 Thread Miguel Rubio-Roy

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

Same problem after an upgrade from 16.04 to 16.10 via "do-release-upgrade". 
Ethernet and WiFi not managed.
Solved it creating blank file at 
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf
as per comment #6

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Desktop-packages] [Bug 1674640] [NEW] un onglet s'est détaché et s'est transformé en une nouvelle fenêtre - A tab got loose and was transformed into a new window

2017-03-21 Thread Dominique S.

Public bug reported:

it's not the first time it appears. but i do not know what exactly is
the origin of the problem

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dominique   3336 F pulseaudio
BuildID: 20170317212642
Channel: Unavailable
CurrentDesktop: Unity
Date: Tue Mar 21 11:05:18 2017
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2016-08-05 (228 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 10.0.0.1 dev enp3s0  proto static  metric 100 
 10.0.0.0/24 dev enp3s0  proto kernel  scope link  src 10.0.0.2  metric 100 
 169.254.0.0/16 dev enp3s0  scope link  metric 1000 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
Locales: extensions.sqlite corrupt or missing
Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
PrefSources: prefs.js
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=52.0.1/20170317212642 (In use)
RelatedPackageVersions: adobe-flashplugin 1:20170214.1-0ubuntu0.16.10.1
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 217
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K50IJ
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr217:bd12/04/2009:svnASUSTeKComputerInc.:pnK50IJ:pvr1.0:rvnASUSTeKComputerInc.:rnK50IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K50IJ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  un onglet s'est détaché et s'est transformé en une nouvelle fenêtre  -
  A tab got loose and was transformed into a new window

Status in firefox package in Ubuntu:
  New

Bug description:
  it's not the first time it appears. but i do not know what exactly is
  the origin of the problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dominique   3336 F pulseaudio
  BuildID: 20170317212642
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Mar 21 11:05:18 2017
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-08-05 (228 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 10.0.0.1 dev enp3s0  proto static  metric 100 
   10.0.0.0/24 dev enp3s0  proto kernel  scope link  src 10.0.0.2  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
linkdown
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=52.0.1/20170317212642 (In use)
  RelatedPackageVersions: adobe-flashplugin 1:20170214.1-0ubuntu0.16.10.1
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 217

[Desktop-packages] [Bug 1398212] Re: just take a look at that

2017-03-21 Thread Juan-Carlos Barros

Hello friend,


I've  just seen something really  fantastic,  I  guess you'd love  that too. 
Just take a look at that stuff here http://mention.watzzzup.com/9899


Very truly yours, jc

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  [recordmcount ... Bus error (core dumped)]

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  When I was Installing some updates, more text boxes said that there
  was an error with nvidia... module.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Tue Dec  2 00:04:16 2014
  InstallationDate: Installed on 2014-10-25 (37 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1398212/+subscriptions

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

[Desktop-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

2017-03-21 Thread Tim

Igor, can you post full logs from Xorg, and also any systemd-logind logs
from journalctl.

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

-- 
Mailing list: https://launchpad.net/

[Desktop-packages] [Bug 1672033] Re: Xorg does not detect displays in rootless mode on nvidia proprietary drivers (GNOME)

2017-03-21 Thread Tim

(before your workaround)

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

Title:
  Xorg does not detect displays in rootless mode on nvidia proprietary
  drivers (GNOME)

Status in NVIDIA Drivers Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  There are two bug reports in LP: #1559576, LP: #1632322 and also LP:
  #164, where GDM does not start on proprietary nvidia drivers. As
  it turned out, the reason for that was Xorg starting in rootless mode
  and apparently not initializing everything properly, which was causing
  gnome-shell/libmutter to crash.

  Installing xserver-xorg-legacy did partially fix those issues.

  Enabling modesetting for nvidia driver however still causes the
  problem.

  
  Here are some parts from log:
  Xorg startup:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (--) Log file 
renamed from "/var/lib/gdm3/.local/share/xorg/Xorg.pid-2027.log" to 
"/var/lib/gdm3/.local/share/xorg/Xorg.0.log"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X.Org X Server 
1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Release Date: 
2016-07-19
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: X Protocol Version 
11, Revision 0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Build Operating 
System: Linux 4.4.0-53-generic x86_64 Ubuntu

  glx loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"glx"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module glx: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Server Extension
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA GLX 
Module  375.39  Tue Jan 31 19:37:12 PST 2017

  nvidia loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"nvidia"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module nvidia: 
vendor="NVIDIA Corporation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 4.0.2, module version = 1.0.0
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver

  modesetting loaded:
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) LoadModule: 
"modesetting"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Loading 
/usr/lib/xorg/modules/drivers/modesetting_drv.so
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Module 
modesetting: vendor="X.Org Foundation"
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: compiled 
for 1.18.4, module version = 1.18.4
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: Module 
class: X.Org Video Driver
  Mär 11 00:43:18 arvlin /usr/lib/gdm3/gdm-x-session[2025]: ABI class: 
X.Org Video Driver, version 20.0

  
  gnome-shell fails to run:
  Mär 11 00:43:20 arvlin kernel: gnome-shell[2067]: segfault at 28 ip 
7fedba8da7c4 sp 7ffd2fb5f5a0 error 4 in 
libmutter-0.so.0.0.0[7fedba893000+12f000]

  xorg stops:
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:66
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:67
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:64
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) UnloadModule: 
"libinput"
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) 
systemd-logind: releasing fd for 13:65
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) NVIDIA(GPU-0): 
Deleting GPU-0
  Mär 11 00:43:21 arvlin /usr/lib/gdm3/gdm-x-session[2025]: (II) Server 
terminated successfully (0). Closing log file.
  Mär 11 00:43:21 arvlin gdm-launch-environment][2009]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1672033/+subscriptions

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

[Desktop-packages] [Bug 1674603] Re: signon-ui crashed with SIGSEGV in QWindow::setModality()

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  signon-ui crashed with SIGSEGV in QWindow::setModality()

Status in signon-ui package in Ubuntu:
  New

Bug description:
  Ubuntu 16:10

  Error message appeared without warning.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: signon-ui-x11 0.17+17.04.20161109-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1
  Uname: Linux 4.10.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Tue Mar 21 02:52:26 2017
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2016-02-16 (398 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/signon-ui
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f37ec699da0 
<_ZN7QWindow11setModalityEN2Qt14WindowModalityE>:   mov0x8(%rdi),%rax
   PC (0x7f37ec699da0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () at 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ()
   ()
   ()
   QMetaObject::activate(QObject*, int, int, void**) () at 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: Upgraded to zesty on 2017-02-17 (31 days ago)
  UserGroups: adm audio bluetooth cdrom dialout dip fax floppy games lightdm 
lpadmin netdev plex plugdev root sambashare scanner src sudo syslog tape 
vboxusers video wireshark

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

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

[Desktop-packages] [Bug 1674609] [NEW] package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 4 zurück

2017-03-21 Thread ruessel

Public bug reported:

I do not know how this bug occured.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bbswitch-dkms 0.8-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Mar 20 21:17:51 2017
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 4 zurück
InstallationDate: Installed on 2016-08-25 (207 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: bbswitch
Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 4 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  4 zurück

Status in bbswitch package in Ubuntu:
  New

Bug description:
  I do not know how this bug occured.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bbswitch-dkms 0.8-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Mon Mar 20 21:17:51 2017
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 4 zurück
  InstallationDate: Installed on 2016-08-25 (207 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: bbswitch
  Title: package bbswitch-dkms 0.8-3ubuntu1 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 4 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-03-21 Thread Khurshid Alam

And the problem is back in next reboot. Not sure what is happening here.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Desktop-packages] [Bug 1674600] Re: package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

** Tags removed: need-duplicate-check

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

Title:
  package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  i don't know what is this.
  but i am having ubuntu freezing any time then i only able to do is force shut 
down(power off)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libharfbuzz0b:amd64 1.2.7-1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue Mar 21 13:43:47 2017
  DuplicateSignature:
   package:libharfbuzz0b:amd64:1.2.7-1
   Setting up cups-ppdc (2.2.0-2) ...
   dpkg: error processing package libharfbuzz0b:amd64 (--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-02-05 (43 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: harfbuzz
  Title: package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to yakkety on 2017-03-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1674600] [NEW] package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat

2017-03-21 Thread gaurav agarwal

Public bug reported:

i don't know what is this.
but i am having ubuntu freezing any time then i only able to do is force shut 
down(power off)

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libharfbuzz0b:amd64 1.2.7-1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Tue Mar 21 13:43:47 2017
DuplicateSignature:
 package:libharfbuzz0b:amd64:1.2.7-1
 Setting up cups-ppdc (2.2.0-2) ...
 dpkg: error processing package libharfbuzz0b:amd64 (--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-02-05 (43 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: harfbuzz
Title: package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: Upgraded to yakkety on 2017-03-20 (0 days ago)

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


** Tags: amd64 apport-package yakkety

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

Title:
  package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  i don't know what is this.
  but i am having ubuntu freezing any time then i only able to do is force shut 
down(power off)

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libharfbuzz0b:amd64 1.2.7-1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue Mar 21 13:43:47 2017
  DuplicateSignature:
   package:libharfbuzz0b:amd64:1.2.7-1
   Setting up cups-ppdc (2.2.0-2) ...
   dpkg: error processing package libharfbuzz0b:amd64 (--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-02-05 (43 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.4
  SourcePackage: harfbuzz
  Title: package libharfbuzz0b:amd64 1.2.7-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to yakkety on 2017-03-20 (0 days ago)

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

-- 
Mailing list: https://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 1636564] Re: Segfault from libX11.so.6.3.0

2017-03-21 Thread Thomas A. F. Thorne

I don't think I'm using the Nvidia drivers on the machine I reported this
from. That would mean they could not be the route cause.

On Mon, 20 Mar 2017, 17:51 Jan Lachnitt, <1636...@bugs.launchpad.net>
wrote:

> Another report and some thoughts below
>
> HW: Asus Vivobook (touchscreen, Intel graphics), external monitor attached.
> OS: Linux Mint 18 Cinnamon x64.
> State before crash: Running X session using both displays ("big desktop"),
> several applications, Vivaldi browser active.
> My aim: Lock the computer.
> Course of action, the USUAL part: Pressed Ctrl+Alt+L, not locked - Vivaldi
> displayed its menu (to be displayed upon pressing Alt), tapped the
> touchscreen to get rid of the menu and thus actually lock the computer.
> Course of action, the UNUSUAL part: Black screen for a few seconds, then
> login screen, old X session gone.
>
> syslog:
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]: XIO:  fatal IO
> error 11 (Resource temporarily unavailable) on X server ":0"
> Mar 20 14:43:20 VivoBook org.a11y.atspi.Registry[1729]:   after 2925
> requests (2925 known processed) with 0 events remaining.
> Mar 20 14:43:20 VivoBook cinnamon-session[1640]: Gdk-WARNING:
> t+4492,79569s: cinnamon-session: Fatal IO error 11 (Prostředek je dočasně
> nepřístupný) on X server :0.
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook org.gtk.vfs.Daemon[1711]: A connection to the bus
> can't be made
> Mar 20 14:43:20 VivoBook mdm[1212]: WARNING: mdm_slave_xioerror_handler:
> Kritická chyba X - Restartování :0
> Mar 20 14:43:20 VivoBook kernel: [ 4538.677519] vivaldi-bin[4100]:
> segfault at 968 ip 7f61ac384643 sp 7ffc09f25b50 error 4 in
> libX11.so.6.3.0[7f61ac35c000+135000]
> Mar 20 14:43:20 VivoBook ag[4118]: mdm-superpost Starting...
> Mar 20 14:43:20 VivoBook ag[4122]: mdm-superpost Finished
> Mar 20 14:43:20 VivoBook console-kit-daemon[1566]: (process:4128):
> GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
> Mar 20 14:43:21 VivoBook acpid: client 1219[0:0] has disconnected
> Mar 20 14:43:21 VivoBook acpid: client connected from 4131[0:0]
> Mar 20 14:43:21 VivoBook acpid: 1 client rule loaded
> Mar 20 14:43:22 VivoBook ag[4139]: mdm-superinit Starting...
> Mar 20 14:43:22 VivoBook ag[4140]: mdm-superinit Finished
>
> Xorg.0.log covers the new session, Xorg.0.log.old has no record of the
> event.
>
> The segfault really seems to affect multiple users, especially with
> Chromium-based browsers, e.g.:
> https://bbs.archlinux.org/viewtopic.php?id=131328 - from 2011 already
> https://bbs.archlinux.org/viewtopic.php?id=221888 - solution?
>
> I don't know if syslog preserves the order of events (within a second),
> but if yes, then the segfault is just a consequence of another problem,
> e.g.:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1636564
>
> Title:
>   Segfault from libX11.so.6.3.0
>
> Status in libx11 package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Something went wrong with my Ubuntu 16.04 LTS desktop today.  When I
>   got back to the system Mattermost and a Chrome were indicating that
>   the network was not working.  I started to look about and it seemed
>   that my main ethernet network connection had lost its IPv4 address
>   somehow.  ifconfig and the GUI network manager confirmed this.
>
>   To try and resolve this I physically removed the connector and the
>   plugged it back in.  Shortly after I did this my GUI seemed to die out
>   and I ended up back at the login screen.
>
>   Once everything had calmed down I logged back in.  After some digging
>   about in the logs I noticed the following in /var/log/kern.log
>
>   Oct 25 13:01:09 thorne-ul-dt kernel: [694321.877561] Mattermost[744]:
> segfault at 968 ip 7f8a9e257643 sp 7ffe72a3b510 error 4 in
> libX11.so.6.3.0[7f8a9e22f000+135000]
>   Oct 25 13:01:09 thorne-ul-dt kernel: [694322.029362] chrome[745]:
> segfault at 968 ip 7fd4b5c73643 sp 7fff94f78d90 error 4 in
> libX11.so.6.3.0[7fd4b5c4b000+135000]
>
>   That seemed to be the correct time for the problem I noticed.   What
>   exactly caused it I am not sure.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: libx11-6 2:1.6.3-1ubuntu2
>   ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
>   Uname: Linux 4.4.0-42-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.1
>   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: Tue Oct 25 17:07:28 2016
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant:

[Desktop-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records

2017-03-21 Thread Khurshid Alam

Ah. Sorry. libnss-resolve was indeed the culprit. Removing it fixed the
issue.

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

Title:
  systemd-resolved’s 127.0.0.53 server does not follow CNAME records

Status in Nextcloud:
  Unknown
Status in systemd:
  New
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Yakkety:
  Invalid
Status in systemd source package in Yakkety:
  Triaged

Bug description:
  [SRU Justification]
  Ubuntu 16.10 server uses systemd-resolved by default, configured both as a 
DNS stub resolver on 127.0.0.53 and as an NSS module via libnss-resolved 
talking to the dbus service.  The DNS stub resolver has a bug that causes it to 
fail to resolve CNAME records.  This went unnoticed before release because by 
default the NSS module is used.  But a chroot or container on the system that 
does not include libnss-resolved and is configured to use the stub resolver 
will experience DNS failures.

  [Test case]
  1. On a yakkety server system, create a xenial chroot with mk-sbuild (or 
equivalent).
  2. Make sure that the host system has /etc/resolv.conf pointed at 127.0.0.53.
  2. Enter the chroot with 'sudo schroot -c xenial-amd64' or such.
  3. Install the iputils-ping package.
  4. ping www.freedesktop.org
  5. Confirm that the hostname does not resolve.
  6. Install the systemd package from yakkety-proposed onto the host system.
  7. ping www.freedesktop.org
  8. Confirm that the hostname does now resolve.

  [Regression potential]
  With a 247-line patch to a key service, there is some risk of regression.  
Regression risk is mitigated because this patch is already present in zesty and 
upstream, where no regressions have been reported, and because it only touches 
the DNS stub resolver which is not the code path used by default on host 
systems.

  
  $ systemd-resolve www.freedesktop.org
  www.freedesktop.org: 131.252.210.176
   2610:10:20:722:a800:ff:feda:470f
   (annarchy.freedesktop.org)

  -- Information acquired via protocol DNS in 673.6ms.
  -- Data is authenticated: no
  $ ping www.freedesktop.org
  ping: www.freedesktop.org: Name or service not known
  $ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 127.0.0.53
  $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  7146IN  CNAME   annarchy.freedesktop.org.
  $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
  ;www.freedesktop.org. IN  A
  www.freedesktop.org.  14399   IN  CNAME   annarchy.freedesktop.org.
  annarchy.freedesktop.org. 14399   IN  A   131.252.210.176

  I trust it needn’t be explained why this makes the internet almost
  completely useless in zesty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nextcloud-snap/+bug/1647031/+subscriptions

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

[Desktop-packages] [Bug 1286810] Re: exporting VPN ppp does fails with unknown error.