date:20150811

 Please keep your subjective comments to yourself

I think my comments were pretty objective.
Ubuntu fails at providing a decent user experience, and it's getting worse.
Ubuntu sucks at supporting NVidia (which is probably mostly NVidia's fault, but 
other distros do better nonetheless).
Ubuntu spends very little effort in improving its desktop operating system 
since their interest have moved to mobile.
Ubuntu fails at fixing bugs in a decent time.

Now all of this may well be OT here, but they are facts, with little
margin of subjectivity.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 1462027] Re: [Needs updating] Update fglrx to include AMD 15.5

2015-08-11 Thread rued...@gmail.com

The open Source drivers don't work perfectly for everything.

For desktop use, I would certainly recommend the Open Source drivers
over the proprietary ones.   They actually run WebGL and JavaScript
canvas functions faster.

However, for gaming, the Open Source drivers currently lack full OpenGL
4.x support, and thus run into certain issues with some shaders not
rendering properly on the latest games.

Even if this were not the case, it is not a reason to refuse to update
the drivers.


As of the latest XOrg, it seems to be running fine with the X-Edgers version of 
XOrg and the current Ubuntu package.  I suspect if the XOrg support patches are 
pushed forward to the latest driver release they should still work.

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

Title:
  [Needs updating] Update fglrx to include AMD 15.5

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  AMD Catalyst 15.05 is released in 2/6/2015. Update FGLRX to include
  this latest driver.

  Source: http://support.amd.com/en-us/download/desktop?os=Linux+x86. 
  I used ubuntu-bug to report, so there's lots of information about previous 
version.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Jun  4 18:27:45 2015
  InstallationDate: Installed on 2015-05-23 (11 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1280053] Re: eclipse is a crashy mess on trusty

2015-08-11 Thread Valéry AMIOT

Same issue for me. My Trusty is a fresh install from last year, constantly 
updated when proposed by muon-updater.
I installed Eclipse for the 1st time today, then package eclipse-jdt I had 
forgotten to select initially.
Launched Eclipse, just explored menus entries, wanted to click on the Tutorials 
link, noticed Eclipse was unresponsive, before it crashed.
Rebooted my PC, launched the HelloWorld tutorial (please don't laugh ^^), 
applied the first instructions before Eclipse crashed again.
I've just applied the /etc/eclipse.ini workaround, relaunched Eclipse and 
noticed the aspect of the welcome screen (where the Tutorials link resides) 
totally changed. A visible consequence of adding 
-Dorg.eclipse.swt.browser.DefaultType=mozilla I believe :)
So far so good, Eclipse didn't crash in the past 15 min... (personal record)

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

Title:
  eclipse is a crashy mess on trusty

Status in eclipse package in Ubuntu:
  Confirmed

Bug description:
  It seems apport has stopped catching eclipse crashes, so I'm reporting
  this issue by hand. To reproduce, all I have to do is open a medium
  sized Java project in eclipse and try to navigate around (using F3 and
  F4 etc.). After 3 or 4 operations, eclipse always crashes. This
  started right after upgrading to trusty.

  What can I do to help folks debug this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: eclipse-platform 3.8.1-5.1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 13 21:11:10 2014
  InstallationDate: Installed on 2011-09-18 (879 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426)
  SourcePackage: eclipse
  UpgradeStatus: Upgraded to trusty on 2014-02-02 (11 days ago)

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

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

[Desktop-packages] [Bug 1436553] Re: Transparent windows render black with Gtk3.16 and compiz

2015-08-11 Thread luke

I just build compiz from the compiz-0.9.12.1+15.10.20150805 source code
on Debian Unstable and gtk3.17. It built fine if I disabled Google
protocol buffers, which Cmake lists as giving faster XML loading only.
The Ubuntu packages build from this could not be installed because that
dependency is not installable right now. My build went fine and ran when
compiz was restarted.

Two of the three issues were fixed but one remains: the gtk-window-
decorator works fine now, and the transparent calendars and menus in my
hacked version of Mate-panel worked perfectly. Unfortunately, issues
with CSD applications are NOT fixed, at least not in gtk3.17. I got
black borders out to the margin set by the windows rather than
compositing of client-side decorated windows. The test program was
gnome-disks, it yielded ugly black borders all the way around.

By comparison, my normal build of compiz from the older 0.9.12.0 add-
gtk-frame-extents-to-net-supported source with the gtk directory
replaced with that from  compiz_0.9.12.1+15.10.20150627.1.orig.tar.gz
works fine with CSD applications, rendering the rounded corners just
fine with normal compositing. Not only that, the build with gcc 4.9
still works even after the gcc5 transition.  I will use this until the
newest version fixes the CSD issue, I don't know if this is unique to
gtk3.17 right now or somehow related to my build not using the protocol
buffers. That I will find out when I can install the offending program
without removing Inkscape.

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

Title:
  Transparent windows render black with Gtk3.16 and compiz

Status in Compiz:
  Fix Committed
Status in compiz package in Ubuntu:
  Confirmed

Bug description:
  Running compiz_1%3a0.9.12.0+15.04.20150202-0ubuntu1 without unity (in
  mate compiled with gtk-3) and testing Gtk-3.16 I run into serious
  issues with failures to render certain Gtk Windows transparent.
  Hardware is AMD FX 8120 with radeon HD 6750 GPU.

  My theme sets popup windows used by menus transparent, and Gtk
  application windows with client side decoration (CSD) have
  transparency underlying the GtkHeaderBar. In the latter case this is
  what makes rounded corners possible.   The transparent popup windows
  used with my theme to support menus resembling gnome-shell's widgets
  in my hacked Gtk3 version of mate-panel work fine with Gtk3.14 but due
  to the window issue get black corners with compiz and Gtk-3.16.
  Windows drawn transparent with cairo still work, but windows set
  transparent by GTK usually do not,

  Changing the window manager to Mutter makes transparency work
  perfectly. In Gtk-3.14 transparency works in Metacity with compositing
  enabled, it does not with gtk-3.16.

  I am not sure whether this should be considered a compiz bug or a Gtk
  bug, but since transparency works fine in gnome-shell and mutter (as
  used by shell), I am not sure the GNOME team would consider this a bug
  they are willing to fix.  If nobody fixes this any GNOME application
  that forces client side decoration (such as the gtk3-demo or gtk3
  -widget-factory) will be ugly in Ubuntu unless the client side
  decorations have square corners.

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

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

[Desktop-packages] [Bug 1483952] [NEW] fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel module failed to build

2015-08-11 Thread Joseph

Public bug reported:

driver wont function under kernel upgrade 26

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
DKMSKernelVersion: 3.19.0-26-generic
Date: Tue Aug 11 19:57:55 2015
InstallationDate: Installed on 2015-05-20 (84 days ago)
InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
PackageVersion: 2:15.200-0ubuntu4.1
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package package-from-proposed vivid

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

Title:
  fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel
  module failed to build

Status in fglrx-installer-updates package in Ubuntu:
  New

Bug description:
  driver wont function under kernel upgrade 26

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Tue Aug 11 19:57:55 2015
  InstallationDate: Installed on 2015-05-20 (84 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  PackageVersion: 2:15.200-0ubuntu4.1
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core 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/fglrx-installer-updates/+bug/1483952/+subscriptions

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

[Desktop-packages] [Bug 1371097] Re: cupsd is not allowed to access /var/cache/samba/gencache.tdb by apparmor

2015-08-11 Thread TEN

Probably triggered by some recent package update, 
Ubuntu 14.04.3 LTS 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:21:34 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
reports in /var/log/kern.log:

type=1400 audit(1439324668.029:103): apparmor=DENIED operation=open
profile=/usr/sbin/cupsd name=/var/cache/samba/gencache.tdb pid=1019
comm=smb requested_mask=r denied_mask=r fsuid=7 ouid=0

The above message can be prevented by this addition to
/etc/apparmor.d/usr.sbin.cupsd from bug 1371097 after the following
comment:

  # Site-specific additions and overrides. See local/README for details.
  #include local/usr.sbin.cupsd

  /var/cache/samba/*.tdb r,

However, another error follows, also repeatedly:

type=1400 audit(1439325510.504:68): apparmor=DENIED operation=signal
profile=/usr/sbin/cupsd pid=952 comm=cupsd requested_mask=send
denied_mask=send signal=term peer=unconfined

For this one, suggestions not directly applicable to LTS seem to be made in bug 
1370930 with a fix for other versions.
How can this best be applied to also fix Ubuntu 14.04.3 ?

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

Title:
  cupsd is not allowed to access /var/cache/samba/gencache.tdb by
  apparmor

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  For some reason /usr/sbin/cupsd tries to access
  /var/cache/samba/gencache.tdb. I have a printer setup via samba so
  that may be the reason.

  The apparmor profile for cupsd does not allow this. I get this error
  in the logs:

   kernel: [284527.967015] type=1400 audit(1411040510.770:103):
  apparmor=DENIED operation=open profile=/usr/sbin/cupsd
  name=/var/cache/samba/gencache.tdb pid=1722 comm=smb
  requested_mask=r denied_mask=r fsuid=7 ouid=0

  A listing of the apparmor profile (/etc/apparmor.d/usr.sbin.cupsd) is here:
  http://pastebin.ubuntu.com/8372024/

  The file /etc/apparmor.d/usr.sbin.cupsd belongs to the cups-daemon
  package

  The system silently fails to print from GUI. The fanny part is that I
  printed something successfully the day I set the printer up
  (yesterday).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups-daemon 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Sep 18 15:27:52 2014
  InstallationDate: Installed on 2014-09-01 (17 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lpstat: device for SRB01PR001: smb://prs03ist00.lim.tepak.int/SRB01PR001
  MachineType: Apple Inc. MacPro5,1
  Papersize: a4
  PpdFiles: SRB01PR001: HP Color LaserJet CP3505 Postscript (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MP51.88Z.007F.B03.1010071432
  dmi.board.asset.tag: 0
  dmi.board.name: Mac-F221BEC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F221BEC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMP51.88Z.007F.B03.1010071432:bd10/07/10:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8:
  dmi.product.name: MacPro5,1
  dmi.product.version: 0.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load lp parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-23T01:20:18

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

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

[Desktop-packages] [Bug 1483914] [NEW] libreoffice-style-elementary as alternate to libreoffice-style-human

2015-08-11 Thread Sean Davis

Public bug reported:

The Xubuntu team has started to maintain a new icon theme for
LibreOffice.

Upstream: https://github.com/shimmerproject/libreoffice-style-elementary
Source Package: https://launchpad.net/ubuntu/+source/xubuntu-artwork
Package: http://packages.ubuntu.com/wily/libreoffice-style-elementary

Please consider adding this theme as an alternate Recommends for
libreoffice-gtk and libreoffice-gtk3 in Ubuntu.  Ultimately, we would
like to include this upstream in LibreOffice, and there is an initial
upstream bug report where work was started on this (though it seems
progress has slowed).

Upstream report:
https://bugs.documentfoundation.org/show_bug.cgi?id=92458

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

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

Title:
  libreoffice-style-elementary as alternate to libreoffice-style-human

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The Xubuntu team has started to maintain a new icon theme for
  LibreOffice.

  Upstream: https://github.com/shimmerproject/libreoffice-style-elementary
  Source Package: https://launchpad.net/ubuntu/+source/xubuntu-artwork
  Package: http://packages.ubuntu.com/wily/libreoffice-style-elementary

  Please consider adding this theme as an alternate Recommends for
  libreoffice-gtk and libreoffice-gtk3 in Ubuntu.  Ultimately, we would
  like to include this upstream in LibreOffice, and there is an initial
  upstream bug report where work was started on this (though it seems
  progress has slowed).

  Upstream report:
  https://bugs.documentfoundation.org/show_bug.cgi?id=92458

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

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

[Desktop-packages] [Bug 1483913] [NEW] modemmanager crashes during wily upgrade and stops everything

2015-08-11 Thread Phil Norbeck

Public bug reported:

During an upgrade from 15.04 to 15.10, modemmanager fails with:

Error in function:
Setting up modemmanager (1.4.10-1) ...
invoke-rc.d: unknown initscript, /etc/init.d/modemmanager not found.
dpkg: error processing package modemmanager (--configure):
 subprocess installed post-installation script returned error exit status 100


and then the upgrade process stops dead.

old version: modemmanager 1.4.0-1
new version: modemmanager 1.4.10-1

Ubuntu Wily Werewolf (development branch)
Ubuntu 15.10
linux 3.19.0-25 i686

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: modemmanager 1.4.10-1
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic i686
ApportVersion: 2.18-0ubuntu6
Architecture: i386
CurrentDesktop: MATE
Date: Tue Aug 11 18:13:09 2015
InstallationDate: Installed on 2015-06-27 (45 days ago)
InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Release i386 (20150422.1)
SourcePackage: modemmanager
UpgradeStatus: Upgraded to wily on 2015-08-11 (0 days ago)

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


** Tags: apport-bug i386 modemmanager upgrade wily

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

Title:
  modemmanager crashes during wily upgrade and stops everything

Status in modemmanager package in Ubuntu:
  New

Bug description:
  During an upgrade from 15.04 to 15.10, modemmanager fails with:

  Error in function:
  Setting up modemmanager (1.4.10-1) ...
  invoke-rc.d: unknown initscript, /etc/init.d/modemmanager not found.
  dpkg: error processing package modemmanager (--configure):
   subprocess installed post-installation script returned error exit status 100

  
  and then the upgrade process stops dead.

  old version: modemmanager 1.4.0-1
  new version: modemmanager 1.4.10-1

  Ubuntu Wily Werewolf (development branch)
  Ubuntu 15.10
  linux 3.19.0-25 i686

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: modemmanager 1.4.10-1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic i686
  ApportVersion: 2.18-0ubuntu6
  Architecture: i386
  CurrentDesktop: MATE
  Date: Tue Aug 11 18:13:09 2015
  InstallationDate: Installed on 2015-06-27 (45 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Release i386 
(20150422.1)
  SourcePackage: modemmanager
  UpgradeStatus: Upgraded to wily on 2015-08-11 (0 days ago)

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

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

[Desktop-packages] [Bug 1320752] Re: MAC Spoofing / Cloning for WiFi is broken in Trusty 14.04 / 14.10 and all others including Mint 17

2015-08-11 Thread Jim Omma

I too have the same problem.

CLONE MAC ADDRESS in Ubuntu does not work. I'm using Kubuntu 15.04.

This bug popped up in Debian at the same time it hit Ubuntu over a year
ago but Debian had it fixed in a couple of weeks.

FIX THIS.

On Kubuntu because PLASMA ROCKS!!

Not to mention you can still use Upstart instead of systemd-ENESSAY

Get OFF YOUR LAZY ASSES AND FIX THIS SHIT OR GO BACK TO WORK AT MS!

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

Title:
  MAC Spoofing / Cloning for WiFi  is broken in Trusty 14.04 / 14.10 and
  all others including Mint 17

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

Bug description:
  **SHORT OVERVIEW**

  Cloned MAC Address feature doesn't work with any USB WiFi adapters
  in 14.04, 14.10, Mint 17 and likely all others based on Ubuntu.

  It worked under 13.10 and was broken from day one in 14.04+.
  This is not an upgrade issue, i did a clean install to test.
  Atheros, Realtek, Ralink adapters tested, this has nothing to do with the 
driver type.

  The only symptoms are WiFi not connecting and the following dmesg
  output:

  [  214.296350] wlan0: authenticate with 98:fc:11:f2:f7:43
  [  214.305098] wlan0: send auth to 98:fc:11:f2:f7:43 (try 1/3)
  [  214.307421] wlan0: authenticated
  [  219.367559] wlan0: deauthenticating from 98:fc:11:f2:f7:43 by local choice 
(reason=3)
  
  **TEMP SOLUTION***

  This bug is caused by wpasupplicant (2.1-0ubuntu1.1) in Trusty,
  network-manager is not the culprit.

  I quick fix is to downgrade wpasupplicant to the Saucy version,
  wpasupplicant (1.0-3ubuntu2). This is relatively easy and doesn't seem
  to affect anything else.

  

  Original bug report info:

  after setting the mac to change in networkmanager i try to connect yet it 
never will, when looking at the logs it says it got disconnected by local 
choice (reason 3), it appeared it was because the mac wasnt effectively changed 
but then again i tried to do so disabling network-manager - macchanger -m - 
enabling network-manager, i checked with ifconfig if the mac has changed and it 
did however the result was the same
  maybe its because of this 
http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-4579.html?

  **UPDATE**

  now works doing the macchanger procedure, directly from network-
  manager it doesnt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Mon May 19 02:00:41 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-06 (12 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-06 (13 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=b249fe00-d117-42dc-a2a4-e2b8763b5b7c ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.53
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3568
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 21.3A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.53:bd10/24/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn3568:rvr21.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g7 Notebook PC

[Desktop-packages] [Bug 1019926] Re: [TOSHIBA NB505, Realtek ALC259, Speaker, Internal] No sound at all

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

** Changed in: alsa-driver (Ubuntu)
   Status: New = Confirmed

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

Title:
  [TOSHIBA NB505, Realtek ALC259, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  1)  The release of Ubuntu you are using, via 'lsb_release -rd' or System - 
About Ubuntu:
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  2)  The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center:
  N: Unable to locate package pkgname

  3)  What you expected to happen:
  To hear sound from my netbook.

  4)  What happened instead:
  I can't hear any sound, whether it be from the netbook or youtube. No sounds 
at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic i686
  .etc.asound.conf:
   
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  an 1912 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf030 irq 46'
 Mixer name : 'Realtek ALC259'
 Components : 'HDA:10ec0269,1179fdc6,00100100'
 Controls  : 16
 Simple ctrls  : 9
  Date: Sun Jul  1 22:36:45 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 
(20101007)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   1912/dev/snd/controlC0:  anF pulseaudio
   AND
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [TOSHIBA NB505, Realtek ALC259, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to precise on 2012-06-04 (27 days ago)
  dmi.bios.date: 06/02/2011
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: PBU00
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd06/02/2011:svnTOSHIBA:pnTOSHIBANB505:pvrPLL50U-01700C:rvnTOSHIBA:rnPBU00:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: TOSHIBA NB505
  dmi.product.version: PLL50U-01700C
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

 Just to make it clear, the status of this bug report was marked as 
 Fix released because the fix was actually released, and it's available
  to you as long as you have the trusty-updates repositories enabled 
 (which should be enabled by default).

The latest status updates are about drivers 340+ versions. 331/Trusty is
still confirmed/triaged. Last time I checked, I had 331 installed. And I
remember getting the crash at some kernel update not long ago, but I
don't know when the last kernel update was.

So, will my 331 drivers be automagically replaced with 340, or with
whatever version fixes the bug? (or perhaps they have already?) Because
otherwise, the bug is not fixed for me nor for the millions of people
having ubuntu 14.04 with 331 drivers. Anyway, if that's not going to be
automatic, what should I do to get that?

For a bug to be fix released, it requires that the issue must
disappear without me doing anything except for accepting the automatic
updates.

@Alexander donating money to Ubuntu? I hope you are kidding. That money is 
going to be wasted in making Ubuntu worse, which is the only thing Canonical 
does (whenever it does change something). Just see how Nautilus evolves or 
how grub still bricks a machine on dist-upgrade, just to name the top examples 
that come to my mind. 
You'd better donate directly to Alberto Milone or to whomever actually is 
actually doing something useful, or even something non-destructive.
Canonical has stopped giving a shit about desktop a while ago; apparently they 
are focusing on mobile (is Ubuntu mobile even a fucking thing?!?)


 Canonical wants to improve the situation for Nvidia users in the future

OMFG, whants to and in the future? For god's sake. It's been what?
20 years since NVidia has been the leader in the market of GPUs?

I am DEFINITELY done with Ubuntu. How long it will take for me to switch
to OpenSUSE is just a matter of how damn lazy I am.

(and you can bet I'll never buy a machine with an NVidia card again)

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 1454868] Re: Ubuntu 15.04 Freezes Totally

2015-08-11 Thread JGJones

Sorry, commented in the wrong area :S - I get a freeze exactly as
described here but it happens whenever I use VLC - but I'm not using
Intel GPU but nvidia so it doesn't fit in here. Please ignore.

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

Title:
  Ubuntu 15.04 Freezes Totally

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  If I'm browsing and doing some heavy stuff like streaming or runing
  multiple terminal commands (ssh, wget etc) or watching Video with VLC.
  Ubuntu just freezes entirely - no mouse or keyboard works unless
  forcing shutdown with power button, I can't guess when this actually
  happens, it happens when I don't expect it - even after a fresh boot.

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

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

[Desktop-packages] [Bug 1409110] Re: nvidia binary driver leaks vram like crazy

2015-08-11 Thread Graeme

Just retested on a fresh install of 15.04 x64 with the nvidia-346
drivers, problem still exists. In between the two nvidia-smi runs shown,
I just switched to the text console with ctl-alt-f1, and then switched
back to X.

graeme@galvatron:~⟫ nvidia-smi 
Tue Aug 11 15:48:00 2015   
+--+   
| NVIDIA-SMI 346.59 Driver Version: 346.59 |   
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce GTX 960 Off  | :01:00.0 N/A |  N/A |
|  0%   58CP8N/A /  N/A |   1148MiB /  2047MiB | N/A  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID  Type  Process name   Usage  |
|=|
|0C+G   Not Supported |
+-+
graeme@galvatron:~⟫ nvidia-smi 
Tue Aug 11 15:48:08 2015   
+--+   
| NVIDIA-SMI 346.59 Driver Version: 346.59 |   
|---+--+--+
| GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. |
|===+==+==|
|   0  GeForce GTX 960 Off  | :01:00.0 N/A |  N/A |
|  0%   59CP0N/A /  N/A |526MiB /  2047MiB | N/A  Default |
+---+--+--+
   
+-+
| Processes:   GPU Memory |
|  GPU   PID  Type  Process name   Usage  |
|=|
|0C+G   Not Supported |
+-+


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

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

Title:
  nvidia binary driver leaks vram like crazy

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  New

Bug description:
  Using the nvidia-smi tool, you can see how much VRAM the binary driver
  is using for the card. However, with the current latest driver in
  Ubuntu 14.10, the results aren't good. Just using desktop apps (no
  OpenGL apart from what Unity and Chrome naturally use), and the driver
  has consumed over a GB of VRAM:

  graeme@galvatron:~⟫ sudo nvidia-smi 
  [sudo] password for graeme: 
  Fri Jan  9 11:58:06 2015   
  +--+  
 
  | NVIDIA-SMI 331.38 Driver Version: 331.38 |  
 
  
|---+--+--+
  | GPU  NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC 
|
  | Fan  Temp  Perf  Pwr:Usage/Cap| Memory-Usage | GPU-Util  Compute M. 
|
  
|===+==+==|
  |   0  GeForce GTX 570 Off  | :01:00.0 N/A |  N/A 
|
  | 40%   43C  N/A N/A /  N/A |   1047MiB /  1279MiB | N/A  Default 
|
  
+---+--+--+

 
  
+-+
  | Compute processes:   GPU Memory 
|
  |  GPU   PID  Process name Usage  
|
  
|=|
  |0

[Desktop-packages] [Bug 1454868] Re: Ubuntu 15.04 Freezes Totally

2015-08-11 Thread JGJones

I have this issue and am using the nvidia drivers (version 346.59).

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

Title:
  Ubuntu 15.04 Freezes Totally

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  If I'm browsing and doing some heavy stuff like streaming or runing
  multiple terminal commands (ssh, wget etc) or watching Video with VLC.
  Ubuntu just freezes entirely - no mouse or keyboard works unless
  forcing shutdown with power button, I can't guess when this actually
  happens, it happens when I don't expect it - even after a fresh boot.

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

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

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

  http://www.phoronix.com/scan.php?page=news_itempx=Ubuntu-Better-
Gaming-Drivers

Btw that's going to be practically useless as long as there's no support
on linux for Optimus. Most computers with NVidia cards now seem to have
that shit.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 38946] Re: Totem-gstreamer: Aspect ratio not correctly detected

2015-08-11 Thread atseaconfused

If you have the need to change the aspect ratio, you may try this easy
and step by step guide at http://www.idealshare.net/video-converter
/change-video-aspect-ratio.html

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

Title:
  Totem-gstreamer: Aspect ratio not correctly detected

Status in totem package in Ubuntu:
  Invalid

Bug description:
  Using totem-gstreamer in an up to date Dapper system, the aspect ratio
  seems to default to square for all videos. The correct aspect ratio
  for any video I tested with (a couple dozen) was 4:3, so the default
  results in very tall-looking people.

  Once you set the aspect ratio to 4:3 it looks fine, but the setting
  isn't preserved - you have to do it every time you run totem. The
  default was correctly detected in Breezy, and I'll bet a lot of users
  won't know how to change this setting.

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

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

[Desktop-packages] [Bug 1483424] Re: Depends: libstdc++6 (= 5.2) on wily

2015-08-11 Thread Rico Tzschichholz

Use ppa:libreoffice/ppa since currently there is no point in using the
prereleases ppa.

The wily package in prereleases ppa got built against the wily-proposed
pocket which contains a huge gcc5 transition.

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

Title:
  Depends: libstdc++6 (= 5.2) on wily

Status in libreoffice package in Ubuntu:
  New

Bug description:
  on a fresh upgrade to wily, after add-apt-repo and purge of everything
  LO-related

  
  sudo apt-get install libreoffice
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libreoffice : Depends: libreoffice-base but it is not going to be installed
 Depends: libreoffice-calc but it is not going to be installed
 Depends: libreoffice-core (= 1:5.0.0~rc5-0ubuntu1~wily1+gcc5) 
but it is not going to be installed
 Depends: libreoffice-draw but it is not going to be installed
 Depends: libreoffice-impress but it is not going to be 
installed
 Depends: libreoffice-math but it is not going to be installed
 Depends: libreoffice-report-builder-bin but it is not going to 
be installed
 Depends: libreoffice-writer but it is not going to be installed
 Depends: libreoffice-avmedia-backend-gstreamer but it is not 
going to be installed
 Depends: libreoffice-java-common (= 1:5.0.0~rc5~) but it is 
not going to be installed
 Depends: python3-uno (= 4.4.0~beta2) but it is not going to 
be installed
 Recommends: libreoffice-gnome but it is not going to be 
installed or
 libreoffice-kde but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.


  sudo apt-get install uno-libs3
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   uno-libs3 : Depends: libstdc++6 (= 5.2) but 5.1.1-14ubuntu1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.


  cat /etc/os-release
  NAME=Ubuntu
  VERSION=15.10 (Wily Werewolf)


  apt-cache show libstdc++
  Package: libstdc++6
  Priority: important
  Section: libs
  Installed-Size: 1471
  Maintainer: Ubuntu Core developers ubuntu-devel-disc...@lists.ubuntu.com
  Original-Maintainer: Debian GCC Maintainers debian-...@lists.debian.org
  Architecture: amd64
  Source: gcc-5
  Version: 5.1.1-14ubuntu1
  Replaces: libstdc++6-5-dbg ( 4.9.0-3)
  Depends: gcc-5-base (= 5.1.1-14ubuntu1), libc6 (= 2.18), libgcc1 (= 1:4.1.1)
  Pre-Depends: multiarch-support
  Conflicts: scim ( 1.4.2-1)
  Breaks: gcc-4.3 ( 4.3.6-1), gcc-4.4 ( 4.4.6-4), gcc-4.5 ( 4.5.3-2)
  Filename: pool/main/g/gcc-5/libstdc++6_5.1.1-14ubuntu1_amd64.deb
  Size: 303306
  MD5sum: f050e69679199ba7929ad2b907097a6a
  SHA1: 7182dc319e2430562cebb171f8fc768caa5339d8
  SHA256: f74720abe6e736de2f879fb51064b1ed47c556c5e07b7e28bec55b633009e713

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

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

[Desktop-packages] [Bug 1477445] Re: _nl_get_vtable: assertion 'vtable.handle' failed

2015-08-11 Thread dino99

Looks like it was a transitional issue: that error is no more logged into 
journalctl.
Maybe that report can be set as 'invalid'

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

Title:
  _nl_get_vtable: assertion 'vtable.handle' failed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Get that error logged into journalctl

  this is also met on
  https://bugzilla.redhat.com/show_bug.cgi?id=1211859

  an upstream fix is available 
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=d767fb160c36bd9dc339e343ebac58274204ad4f

  Please import that upstream fix

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 0.9.10.0-4ubuntu18
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu3
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Thu Jul 23 10:17:41 2015
  IpRoute:
   default via 192.168.1.1 dev eth1  proto static  metric 100 
   169.254.0.0/16 dev eth1  scope link  metric 1000 
   192.168.1.0/24 dev eth1  proto kernel  scope link  metric 100
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-06-13T08:56:31.598901
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  READONLY  DBUS-PATH  
 ACTIVE  DEVICE  STATE  ACTIVE-PATH 
   
   Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  802-3-ethernet  
1437639256  jeu. 23 juil. 2015 10:14:16 CEST  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes eth1activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   eth1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  7086b2ff-1446-45fe-b8f3-cd333cd4cee1  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  -- 
 ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

-- 
Mailing list: https://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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Jerry

I flagged as security, since holds back kernel updates which escalated sec
probs, if not causes them.  Ianal
On Aug 11, 2015 3:21 AM, ciro santoro 1431...@bugs.launchpad.net wrote:

 I installed last updates on my ubuntu 14.04 and, after reboot, it starts
 and remains with a black screen.. I listened the ubuntu welcome sound and
 nothing appens :(

 2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net:

  Packages nvidia-331-* are now transitional packages for version 340
  where this bug has been fixed, so I guess they can be marked as Fix
  Released too. Thanks everyone involved esp. Alberto for your work.
 
  --
  You received this bug notification because you are subscribed to a
  duplicate bug report (1409930).
  https://bugs.launchpad.net/bugs/1431753
 
  Title:
Nvidia binary driver FTBS due to DKMS layer violation
 
  Status in nvidia-graphics-drivers-331 package in Ubuntu:
Confirmed
  Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed
  Status in nvidia-graphics-drivers-340 package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-346 package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
Fix Released
  Status in nvidia-graphics-drivers-331 source package in Trusty:
Triaged
  Status in nvidia-graphics-drivers-331-updates source package in Trusty:
Triaged
  Status in nvidia-graphics-drivers-340 source package in Trusty:
Fix Released
  Status in nvidia-graphics-drivers-340-updates source package in Trusty:
Fix Released
  Status in nvidia-graphics-drivers-346 source package in Trusty:
Fix Released
  Status in nvidia-graphics-drivers-346-updates source package in Trusty:
Fix Released
 
  Bug description:
Filing this against the 340-updates version but possibly the same
applies to older versions, too. The nvidia source package produces two
individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
The problem is that the DKMS build of the nvidia-uvm module runs
compile steps inside the nvidia modules build directory. This is
violating the DKMS assumption that each module can be build
independently (there is no way of describing cross-modules
dependencies and even more important, the autoinstall step after a new
kernel is installed will run the modules build in parallel).
 
Since nvidia and nvidia-uvm are very dependent on each other the right
course of action seems to be to combine both sources in one DKMS
module that produces two kernel modules (this is supported by DKMS).
For the transition this resulting dkms package needs to have a
breaks/replaces for the nvidia-uvm package.
 
  To manage notifications about this bug go to:
 
 
 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions
 


 --
 Ciro Santoro

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

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this

Re: [Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread ciro santoro

I installed last updates on my ubuntu 14.04 and, after reboot, it starts
and remains with a black screen.. I listened the ubuntu welcome sound and
nothing appens :(

2015-08-08 20:51 GMT+02:00 Nathanaël Naeri 1431...@bugs.launchpad.net:

 Packages nvidia-331-* are now transitional packages for version 340
 where this bug has been fixed, so I guess they can be marked as Fix
 Released too. Thanks everyone involved esp. Alberto for your work.

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

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in Trusty:
   Fix Released

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces two
   individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by DKMS).
   For the transition this resulting dkms package needs to have a
   breaks/replaces for the nvidia-uvm package.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions



-- 
Ciro Santoro

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1483560] [NEW] Screen tearing with bumblebee

2015-08-11 Thread Andrew

Public bug reported:

After last nvidia drivers update, I've noticed screen tearing on fast
cursor moving in menus, also in 720p video in VLC and even in QtCreator
text editor. I have bumblebee running intel i915 and NVIDIA GF117M.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
NonfreeKernelModules: wl nvidia
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.76  Thu Jan 22 12:11:08 
PST 2015
 GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 11 10:41:09 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-61-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.13.0-61-generic, x86_64: installed
 nvidia-340, 340.76, 3.13.0-61-generic, x86_64: installed
 vboxhost, 4.3.30, 3.13.0-61-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3808]
   Subsystem: Lenovo Device [17aa:380e]
InstallationDate: Installed on 2015-01-25 (197 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: LENOVO 20252
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=igfx_off 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/12/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 8ECN95WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Ginkgo 7A1
dmi.board.vendor: LENOVO
dmi.board.version: 31900059WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G710
dmi.modalias: 
dmi:bvnLENOVO:bvr8ECN95WW:bd05/12/2014:svnLENOVO:pn20252:pvrLenovoG710:rvnLENOVO:rnGinkgo7A1:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG710:
dmi.product.name: 20252
dmi.product.version: Lenovo G710
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Aug 11 10:31:35 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16982 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-bug performance third-party-packages trusty ubuntu

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

Title:
  Screen tearing with bumblebee

Status in xorg package in Ubuntu:
  New

Bug description:
  After last nvidia drivers update, I've noticed screen tearing on fast
  cursor moving in menus, also in 720p video in VLC and even in
  QtCreator text editor. I have bumblebee running intel i915 and NVIDIA
  GF117M.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: wl nvidia
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.76  Thu Jan 22 12:11:08 
PST 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 10:41:09 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-61-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.13.0-61-generic, x86_64: installed
   nvidia-340, 340.76, 3.13.0-61-generic, x86_64: installed
   vboxhost, 4.3.30, 3.13.0-61-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

strace-6288-evolution-calendar-factory.txt showing strace output of
evolution-calendar-factory taken over a few minutes.

** Attachment added: strace-6288-evolution-calendar-factory.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442846/+files/strace-6288-evolution-calendar-factory.txt

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

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

strace-7088-evolution-alarm-notify.txt showing strace for evolution-
alarm-notify taken over the same few minutes.

** Attachment added: strace-7088-evolution-alarm-notify.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442848/+files/strace-7088-evolution-alarm-notify.txt

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

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

strace-6165-evolution-source-registry.txt strace volution-source-
registry of taken over the same few minutes.

** Attachment added: strace-6165-evolution-source-registry.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442849/+files/strace-6165-evolution-source-registry.txt

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

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

strace-25363-evolution-addressbook-factory strace of evolution-
addressbook-factory taken over the same few minutes.

** Attachment added: strace-25363-evolution-addressbook-factory
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442850/+files/strace-25363-evolution-addressbook-factory

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

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

So, I'm lucky enough to be able to USE my machine just because I'm not
actually using NVidia drivers?

My problem with this bug is only that I get an error message about something 
crashing every time there's a kernel update. I thought that was it, but I see 
there are people whose system stop booting or becomes unusable because of this, 
WTF!
That is, what, everybody using ubuntu 14.04 with an NVidia card that doesn't 
have the Optimus technology (which renders the nvidia card useless on linux, 
but on the up side, avoids this bug, apparently)?
And it's been a year without fixing.

I'm done with Ubuntu.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 1480060] Re: Fonts in GUI garbled, missing characters on Lenovo X1 Carbon 3rd Gen

2015-08-11 Thread zlatko

@tjaaltonen
What latest updates I need to install? Can you point me where to look for them? 
I always install all proposed updates and I thought as 14.04 is LTS these are 
the latest stable stuff.
Thank you in advance!

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

Title:
  Fonts in GUI garbled, missing characters on Lenovo X1 Carbon 3rd Gen

Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid

Bug description:
  Quite often the characters in GUI menus(e.g. WiFi dropdown, Calendar 
dropdown) and terminal become garbled, unreadable and/or missing. In the same 
time all is OK in e.g. browser. It often happens after resume, but sometimes 
during normal operation. After a while(1-2-...10 minutes) the problem is gone. 
  Steps to take: normal Ubuntu 14.04 install
  What happens: after resume or normal operation symbols is top row GUI menus 
become garbled and unreadable 
  What should happen: graphics should be stable

  $ lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  $ sudo lshw -c video
  [sudo] password for zlatko: 
*-display   
 description: VGA compatible controller
 product: Broadwell-U Integrated Graphics
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:61 memory:f000-f0ff memory:e000-efff 
ioport:3000(size=64)

  $ modinfo i915 | head
  filename:   
/lib/modules/3.16.0-45-generic/kernel/drivers/gpu/drm/i915/i915.ko
  license:GPL and additional rights
  description:Intel Graphics
  author: Tungsten Graphics, Inc.
  srcversion: 73A8A491ABAC016823271D6
  alias:  pci:v8086d22B3sv*sd*bc03sc*i*
  alias:  pci:v8086d22B2sv*sd*bc03sc*i*
  alias:  pci:v8086d22B1sv*sd*bc03sc*i*
  alias:  pci:v8086d22B0sv*sd*bc03sc*i*
  alias:  pci:v8086d162Dsv*sd*bc03sc*i*

  PS. There is a bug filed(https://bugs.launchpad.net/xserver-xorg-
  video-intel/+bug/1432194) but it was unproperly marked as resolved and
  closed, team unsubscribed, Hence I am filing a new one.

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

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

[Desktop-packages] [Bug 1292869] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug is no longer a duplicate of private bug 1234934

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu15
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Mar 15 15:34:57 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2014-03-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140314)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb70350a8:mov%edi,0x28(%eax)
   PC (0xb70350a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1282997] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

I've traced the gst_base_parse_push_frame() function to the GstBaseParse
class in libgstreamer1.0-0

** Package changed: rhythmbox (Ubuntu) = gstreamer1.0 (Ubuntu)

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately, I don't understand what I did to make this happen. I
  simply put an MP3 to play, then closed the rhythmbox window, and saw
  the error dialog. I can't reproduce the problem consistently, but it
  happens from time to time.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
  Uname: Linux 3.13.0-10-generic i686
  NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c nvram ctr 
ccm dm_crypt joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
videodev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_hdmi kvm_intel kvm snd_hda_codec_via crc32_pclmul aesni_intel 
snd_hda_intel aes_i586 xts snd_hda_codec parport_pc lrw gf128mul ppdev arc4 
ablk_helper cryptd snd_hwdep snd_pcm iwldvm snd_page_alloc snd_seq_midi rfcomm 
bnep snd_seq_midi_event snd_rawmidi bluetooth mac80211 snd_seq iwlwifi psmouse 
cfg80211 serio_raw snd_seq_device rtsx_pci_ms microcode snd_timer memstick snd 
soundcore mei_me lpc_ich mei mac_hid lp parport hid_generic usbhid hid i915 
i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper drm r8169 ahci rtsx_pci mii libahci 
video wmi
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 21 10:57:05 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2013-08-19 (186 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  SegvAnalysis:
   Segfault happened at: 0xb70180a8:mov%edi,0x28(%eax)
   PC (0xb70180a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1282997/+subscriptions

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

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

@ciro: that could be caused by a number of things. If you can ssh into
the machine, or VT switch by pressing CTRL+ALT+F2, please collect the
following data:

1) the output of dkms status
2) the dmesg output
3) /var/log/Xorg.0.log
4) /var/log/gpu-manager.log

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 10910] Re: Default page size for printing is letter

2015-08-11 Thread John Drinkwater

Should land for Firefox 41, which will be a few weeks (22nd Sept) before
15.10 arrives.

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

Title:
  Default page size for printing is letter

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Triaged
Status in firefox package in Baltix:
  Confirmed

Bug description:
  (Default warty install, dist-upgraded to hoary, language chosen is
  Norwegian)

  about:config reports that print.postscript.paper_size is letter, which is 
wrong
  for Norway, it should be A4.  It should probably look at LC_PAPER or 
/etc/papersize

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

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

[Desktop-packages] [Bug 1292869] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

** This bug has been marked a duplicate of bug 1286563
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug is no longer a duplicate of bug 1282997
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug has been marked a duplicate of bug 1282997
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug is no longer a duplicate of bug 1282997
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug has been marked a duplicate of bug 1282997
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug is no longer a duplicate of bug 1286563
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
** This bug has been marked a duplicate of bug 1282997
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu15
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Mar 15 15:34:57 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2014-03-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140314)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb70350a8:mov%edi,0x28(%eax)
   PC (0xb70350a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1483695] [NEW] fails to build module in wily-proposed: gcc-4.9: Command not found

2015-08-11 Thread Martin Pitt

Public bug reported:

As shown by the test regression of
http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers-
common/wily/amd64/ , fglrx and fglrx-updates fail to build the module in
wily-proposed:

Setting up fglrx-core (2:15.200.1-0ubuntu2) ...
update-alternatives: using /usr/lib/fglrx-core/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) 
in auto mode
Loading new fglrx-core-15.200.1 DKMS files...
First Installation: checking all kernels...
Building only for 4.1.0-3-generic
Building for architecture x86_64
Building initial module for 4.1.0-3-generic
Error! Bad return status for module build on kernel: 4.1.0-3-generic (x86_64)
Consult /var/lib/dkms/fglrx-core/15.200.1/build/make.log for more information.
 
$ cat /var/lib/dkms/fglrx-core/15.200.1/build/make.log
DKMS make.log for fglrx-core-15.200.1 for kernel 4.1.0-3-generic (x86_64)
Tue Aug 11 14:44:15 CEST 2015
/usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200.1/build: No such file 
or directory
make.sh: 1: make.sh: gcc-4.9: not found
make.sh: 50: [: !=: unexpected operator
AMD kernel module generator version 2.1
doing Makefile based build for kernel 2.6.x and higher
rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
make -C /lib/modules/4.1.0-3-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x modules
make[1]: Entering directory '/usr/src/linux-headers-4.1.0-3-generic'
arch/x86/Makefile:114: stack-protector enabled but compiler support broken
arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support
Makefile:667: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector 
not supported by compiler
make[1]: gcc-4.9: Command not found
  CC [M]  /var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o
/bin/sh: 1: gcc-4.9: not found
scripts/Makefile.build:258: recipe for target 
'/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o' failed
make[2]: *** [/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o] 
Error 127
Makefile:1395: recipe for target 
'_module_/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x' failed
make[1]: *** [_module_/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.1.0-3-generic'
Makefile:88: recipe for target 'kmod_build' failed
make: *** [kmod_build] Error 2
build failed with return value 2

So it seems fglrx hardcodes gcc-4.9 without depending on it -- only
the default compiler is installed:

ii  gcc  4:5.2.1-3ubuntu1 amd64GNU C compiler
ii  gcc-55.2.1-15ubuntu1  amd64GNU C compiler
ii  gcc-5-base:amd64 5.2.1-15ubuntu1  amd64GCC, the GNU Compiler 
Collection (base package)

Ideally fglrx would switch to building with gcc-5 (or any gcc); if
that's not possible, please adjust the dependencies to gcc-4.9
explicitly.

** Affects: fglrx (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: fglrx (Ubuntu Wily)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Affects: fglrx-installer-updates (Ubuntu Wily)
 Importance: High
 Assignee: Alberto Milone (albertomilone)
 Status: New

** Also affects: fglrx-installer-updates (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fglrx (Ubuntu)
   Importance: Undecided = High

** Changed in: fglrx-installer-updates (Ubuntu)
   Importance: Undecided = High

** Also affects: fglrx-installer-updates (Ubuntu Wily)
   Importance: High
   Status: New

** Also affects: fglrx (Ubuntu Wily)
   Importance: High
   Status: New

** Changed in: fglrx (Ubuntu Wily)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer-updates (Ubuntu Wily)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

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

Title:
  fails to build module in wily-proposed: gcc-4.9: Command not found

Status in fglrx package in Ubuntu:
  New
Status in fglrx-installer-updates package in Ubuntu:
  New
Status in fglrx source package in Wily:
  New
Status in fglrx-installer-updates source package in Wily:
  New

Bug description:
  As shown by the test regression of
  http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers-
  common/wily/amd64/ , fglrx and fglrx-updates fail to build the module
  in wily-proposed:

  Setting up fglrx-core (2:15.200.1-0ubuntu2) ...
  update-alternatives: using /usr/lib/fglrx-core/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) 
in auto mode
  Loading new fglrx-core-15.200.1 DKMS files...
  First Installation: checking all kernels...
  Building only for

[Desktop-packages] [Bug 1286563] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

** This bug is no longer a duplicate of private bug 1234934

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  dejo de funcionar mientras cargaba archibos de una particion diferente

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Mar  1 12:01:10 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2014-03-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb6fa80a8:mov%edi,0x28(%eax)
   PC (0xb6fa80a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1286563] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

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

** Changed in: rhythmbox (Ubuntu)
   Status: New = Confirmed

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  dejo de funcionar mientras cargaba archibos de una particion diferente

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Mar  1 12:01:10 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2014-03-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb6fa80a8:mov%edi,0x28(%eax)
   PC (0xb6fa80a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1286563] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

** This bug has been marked a duplicate of bug 1282997
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  dejo de funcionar mientras cargaba archibos de una particion diferente

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sat Mar  1 12:01:10 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2014-03-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140228)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb6fa80a8:mov%edi,0x28(%eax)
   PC (0xb6fa80a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1282997] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug is no longer a duplicate of private bug 1234934

** This bug has been marked a duplicate of bug 1286563
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

** This bug is no longer a duplicate of bug 1286563
   rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately, I don't understand what I did to make this happen. I
  simply put an MP3 to play, then closed the rhythmbox window, and saw
  the error dialog. I can't reproduce the problem consistently, but it
  happens from time to time.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
  Uname: Linux 3.13.0-10-generic i686
  NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c nvram ctr 
ccm dm_crypt joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
videodev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_hdmi kvm_intel kvm snd_hda_codec_via crc32_pclmul aesni_intel 
snd_hda_intel aes_i586 xts snd_hda_codec parport_pc lrw gf128mul ppdev arc4 
ablk_helper cryptd snd_hwdep snd_pcm iwldvm snd_page_alloc snd_seq_midi rfcomm 
bnep snd_seq_midi_event snd_rawmidi bluetooth mac80211 snd_seq iwlwifi psmouse 
cfg80211 serio_raw snd_seq_device rtsx_pci_ms microcode snd_timer memstick snd 
soundcore mei_me lpc_ich mei mac_hid lp parport hid_generic usbhid hid i915 
i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper drm r8169 ahci rtsx_pci mii libahci 
video wmi
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 21 10:57:05 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2013-08-19 (186 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  SegvAnalysis:
   Segfault happened at: 0xb70180a8:mov%edi,0x28(%eax)
   PC (0xb70180a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1282997] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

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

** Changed in: rhythmbox (Ubuntu)
   Status: New = Confirmed

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately, I don't understand what I did to make this happen. I
  simply put an MP3 to play, then closed the rhythmbox window, and saw
  the error dialog. I can't reproduce the problem consistently, but it
  happens from time to time.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3
  Uname: Linux 3.13.0-10-generic i686
  NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c nvram ctr 
ccm dm_crypt joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core 
videodev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_hda_codec_hdmi kvm_intel kvm snd_hda_codec_via crc32_pclmul aesni_intel 
snd_hda_intel aes_i586 xts snd_hda_codec parport_pc lrw gf128mul ppdev arc4 
ablk_helper cryptd snd_hwdep snd_pcm iwldvm snd_page_alloc snd_seq_midi rfcomm 
bnep snd_seq_midi_event snd_rawmidi bluetooth mac80211 snd_seq iwlwifi psmouse 
cfg80211 serio_raw snd_seq_device rtsx_pci_ms microcode snd_timer memstick snd 
soundcore mei_me lpc_ich mei mac_hid lp parport hid_generic usbhid hid i915 
i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper drm r8169 ahci rtsx_pci mii libahci 
video wmi
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Fri Feb 21 10:57:05 2014
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationDate: Installed on 2013-08-19 (186 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  SegvAnalysis:
   Segfault happened at: 0xb70180a8:mov%edi,0x28(%eax)
   PC (0xb70180a8) ok
   source %edi ok
   destination 0x28(%eax) (0x0028) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstaudio-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0
   gst_base_parse_push_frame () from /usr/lib/i386-linux-gnu/libgstbase-1.0.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1483643] [NEW] evolution hangs (grey window) while previewing an email

Public bug reported:

I had left evolution running overnight.  It seems to develop issues
after being left to run for a while on my current system.

This morning I returned focus to the evolution window and tried to view
the latest email from my Exchange account in the preview window.
retrieving message 'AQMk...' is displayed in the preview area and
after a short while the application turns gray, suggesting that the
process has hung.  It has been that way for about an hour, so I started
trying to collect some diagnostic info.

$ ps -elf | grep evolution
0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

$ sudo strace -p 7492
Process 7492 attached
futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

I'll attach the other data as .txt files in a bit.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evolution 3.10.4-0ubuntu2
Uname: Linux 4.1.0-040100rc8-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 11 11:36:36 2015
InstallationDate: Installed on 2015-03-12 (151 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483643] Re: evolution hangs (grey window) while previewing an email

I did  
  $ sudo gdb --batch --ex t a a bt -pid=`pidof evolution` bt.txt
the resulting file is attached.  I had a quick look through it and could not 
see any sensitive data in there.  


** Attachment added: $ sudo gdb --batch --ex t a a bt -pid=`pidof evolution` 
bt.txt
   
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1483643/+attachment/4442844/+files/bt.txt

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

Title:
  evolution hangs (grey window) while previewing an email

Status in evolution package in Ubuntu:
  New

Bug description:
  I had left evolution running overnight.  It seems to develop issues
  after being left to run for a while on my current system.

  This morning I returned focus to the evolution window and tried to
  view the latest email from my Exchange account in the preview window.
  retrieving message 'AQMk...' is displayed in the preview area and
  after a short while the application turns gray, suggesting that the
  process has hung.  It has been that way for about an hour, so I
  started trying to collect some diagnostic info.

  $ ps -elf | grep evolution
  0 S thomast+  6165  5732  0  80   0 - 413489 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/evolution-source-registry
  0 S thomast+  6288  5732  0  80   0 - 456116 poll_s Aug10 ?   00:00:11 
/usr/lib/evolution/evolution-calendar-factory
  0 S thomast+  7088  6039  0  80   0 - 306294 poll_s Aug10 ?   00:00:00 
/usr/lib/evolution/3.10/evolution-alarm-notify
  0 S thomast+  7492  5732  0  80   0 - 975658 futex_ Aug10 ?   00:01:55 
evolution
  0 S thomast+ 25363  5732  0  80   0 - 521596 poll_s Aug10 ?   00:00:01 
/usr/lib/evolution/evolution-addressbook-factory

  $ sudo strace -p 7492
  Process 7492 attached
  futex(0x55c16bf54594, FUTEX_WAIT_PRIVATE, 1, NULL^CProcess 7492 detached

  I'll attach the other data as .txt files in a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu2
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 11:36:36 2015
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Peter Varlien

I had the same experience.

It turned out thet my xorg.conf file had been renamed with a .back
suffix. I copied it back and restarted, and all was good.

On August 11, 2015 9:14:05 AM CEST, ciro santoro 1431...@bugs.launchpad.net 
wrote:
I installed last updates on my ubuntu 14.04 and, after reboot, it
starts
and remains with a black screen.. I listened the ubuntu welcome sound
and
nothing appens :(

2015-08-08 20:51 GMT+02:00 Nathanaël Naeri
1431...@bugs.launchpad.net:

 Packages nvidia-331-* are now transitional packages for version 340
 where this bug has been fixed, so I guess they can be marked as Fix
 Released too. Thanks everyone involved esp. Alberto for your work.

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

 Title:
   Nvidia binary driver FTBS due to DKMS layer violation

 Status in nvidia-graphics-drivers-331 package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
   Confirmed
 Status in nvidia-graphics-drivers-340 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346 package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
   Fix Released
 Status in nvidia-graphics-drivers-331 source package in Trusty:
   Triaged
 Status in nvidia-graphics-drivers-331-updates source package in
Trusty:
   Triaged
 Status in nvidia-graphics-drivers-340 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-340-updates source package in
Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346 source package in Trusty:
   Fix Released
 Status in nvidia-graphics-drivers-346-updates source package in
Trusty:
   Fix Released

 Bug description:
   Filing this against the 340-updates version but possibly the same
   applies to older versions, too. The nvidia source package produces
two
   individual dkms packages: nvidia-340-updates,
nvidia-340-updates-uvm.
   The problem is that the DKMS build of the nvidia-uvm module runs
   compile steps inside the nvidia modules build directory. This is
   violating the DKMS assumption that each module can be build
   independently (there is no way of describing cross-modules
   dependencies and even more important, the autoinstall step after a
new
   kernel is installed will run the modules build in parallel).

   Since nvidia and nvidia-uvm are very dependent on each other the
right
   course of action seems to be to combine both sources in one DKMS
   module that produces two kernel modules (this is supported by
DKMS).
   For the transition this resulting dkms package needs to have a
   breaks/replaces for the nvidia-uvm package.

 To manage notifications about this bug go to:


https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions



-- 
Ciro Santoro

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
 applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
 dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

 Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this

[Desktop-packages] [Bug 1483750] [NEW] Please sync newest pcsc-lite 1.8.14-1 to Ubuntu Wily from Debian Unstable

2015-08-11 Thread Nicolas DERIVE

Public bug reported:

We currently have a one year old version of pcsc-lite in archive whereas
3 new versions have been uploaded to Debian Unstable since then.

This package is pretty easy to sync with only a small change in
debian/rules kept, to allow its use by wpasupplicant.

Test build of ready-to-upload package is here:
https://launchpad.net/~kalon33/+archive/ubuntu/rfid/+sourcepub/5293788
/+listing-archive-extra


Thanks for syncing :)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pcscd 1.8.11-3ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-3.3-generic 4.2.0-rc5
Uname: Linux 4.2.0-3-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 11 15:32:22 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-03-30 (134 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150317.1)
SourcePackage: pcsc-lite
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pcsc-lite (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

** Summary changed:

- Please sync newest pcsc-lite 1.8.14-1 to Ubuntu Wily
+ Please sync newest pcsc-lite 1.8.14-1 to Ubuntu Wily from Debian Unstable

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

Title:
  Please sync newest pcsc-lite 1.8.14-1 to Ubuntu Wily from Debian
  Unstable

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  We currently have a one year old version of pcsc-lite in archive
  whereas 3 new versions have been uploaded to Debian Unstable since
  then.

  This package is pretty easy to sync with only a small change in
  debian/rules kept, to allow its use by wpasupplicant.

  Test build of ready-to-upload package is here:
  https://launchpad.net/~kalon33/+archive/ubuntu/rfid/+sourcepub/5293788
  /+listing-archive-extra

  
  Thanks for syncing :)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pcscd 1.8.11-3ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-3.3-generic 4.2.0-rc5
  Uname: Linux 4.2.0-3-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 15:32:22 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-30 (134 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150317.1)
  SourcePackage: pcsc-lite
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1334756] Re: can't unlock user account

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

** Changed in: unity-control-center (Ubuntu)
   Status: New = Confirmed

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

Title:
  can't unlock user account

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

Bug description:
  can't add and remove user account in unity-control-center, because
  unlock may be disable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  ProcVersionSignature: hostname 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Jun 26 23:32:22 2014
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

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

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

[Desktop-packages] [Bug 1334756] Re: can't unlock user account

2015-08-11 Thread Christopher Yeleighton

I get the following tool tip: ‘ System policy prevents changes; contact
your system administrator.’

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

Title:
  can't unlock user account

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

Bug description:
  can't add and remove user account in unity-control-center, because
  unlock may be disable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1
  ProcVersionSignature: hostname 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Jun 26 23:32:22 2014
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

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

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

[Desktop-packages] [Bug 392175] Re: Implement gnome-terminal activity monitor feature

2015-08-11 Thread Bug Watch Updater

** Changed in: gnome-terminal
   Status: New = Confirmed

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

Title:
  Implement gnome-terminal activity monitor feature

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-terminal

  This is not a bug, this is a feature request.

  I've been a KDE user long time ago. In this time a used konsole as a
  terminal emulator. Since Hardy I'm using the Ubuntu default Gnome
  desktop and in this case I'm using gnome-terminal instead off konsole.

  There is a feature which is really missing for me. Konsole is able to
  monitor activity on the terminal tabs. So if I'm working on one of the
  tabs (active tab) konsole is able to alarm me when there is some
  activity on a not used one (inactive tab).

  There will be nice to see a similar feature for gnome-terminal. Please
  implement a similar feature!

  Best Regards,
  totya

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

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

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

2015-08-11 Thread Alexander Chr. Tornow

@teo1978:

Yeah, I fully agree. I recommended Ubuntu LTS to everyone I know that
has been willing to either give Ubuntu a try or to users that have
completely switched from Windows. My words, after they asked me why I
recommend LTS over normal Ubuntu: Use LTS if you prefer stability,
support and reliability.

And now I am eating my own words.

It's nice to see this bug is getting fixed... finally... but it's sad it
took so long in the first place. A lot of my friends were left with an
unstable or malfunctioning system and that's a real show stopping issue,
especially because the issue came unexpected after updating the system
as usual. Ever since reporting this bug, I have switched to an AMD 6000
series GPU, using the open and free AMD drivers Ubuntu ships and
activates at default. It's been awesome so far, gaming-wise as well.

So, personally, I am not going to lose any sleep over this issue
anymore. But my friends are still using Nvidia hardware + Ubuntu
14.04.2/3 LTS and I'd like to know if the faulty Nvidia drivers (331.x?)
available via the Ubuntu repos have been replaced with the drivers
mentioned in this bug report that include the fix - or is the solution
to activate the unstable testing/proposed repo the only way out of this
mess?

Any kind of feedback is appreciated!

Thanks!

Cheers,
Alex

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 1455533] Re: Dell systems showing DIAGS in Nautilus bar

2015-08-11 Thread Ara Pulido

** Changed in: oem-priority
   Status: Confirmed = Fix Released

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

Title:
  Dell systems showing DIAGS in Nautilus bar

Status in OEM Priority Project:
  Fix Released
Status in udisks:
  Fix Released
Status in udisks2 package in Ubuntu:
  Fix Released
Status in udisks2 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Dell factory installed Linux systems are showing the partition DIAGS in 
the Nautilus bar
   * Also, Dell systems configured as a dual boot with Windows and Ubuntu 
14.04.x show the same behavior.
   * This has been fixed in udisks2 upstream release 2.1.5

   * This partition is not supposed to be accessible easily to users in
  any OS.

  [Test Case]

   * Create a FAT32 partition called diags and verify that it doesn't
  show up in the Nautilus bar after a reboot.

  [Regression Potential]

   * Regression potential is that anyone who is using this partition to
  store data won't be able to easily access it anymore

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

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

[Desktop-packages] [Bug 1483707] [NEW] Rhythmbox crashes in source_rhythmbox.py during apport reporting of a bug

Public bug reported:

Description:Ubuntu 15.04
Release:15.04

rhythmbox:
  Installed: 3.1-1ubuntu3
  Candidate: 3.1-1ubuntu3
  Version table:
 *** 3.1-1ubuntu3 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status

I expect to be prompted to report a bug during a crash, instead nothing happens.
The crash report in /var/crash/_usr_lib_rhythmbox_rhythmbox-metadata.500.upload 
is zero bytes
In $HOME/.cache/upstart/ I have file 
update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log.1.gz
 attached

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

** Attachment added: 
update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log
   
https://bugs.launchpad.net/bugs/1483707/+attachment/4442891/+files/update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log

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

Title:
  Rhythmbox crashes in source_rhythmbox.py during apport reporting of a
  bug

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 15.04
  Release:  15.04

  rhythmbox:
Installed: 3.1-1ubuntu3
Candidate: 3.1-1ubuntu3
Version table:
   *** 3.1-1ubuntu3 0
  500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status

  I expect to be prompted to report a bug during a crash, instead nothing 
happens.
  The crash report in 
/var/crash/_usr_lib_rhythmbox_rhythmbox-metadata.500.upload is zero bytes
  In $HOME/.cache/upstart/ I have file 
update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log.1.gz
 attached

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

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

[Desktop-packages] [Bug 1483695] Re: fails to build module in wily-proposed: gcc-4.9: Command not found

2015-08-11 Thread Martin Pitt

This comes from /lib/modules/fglrx/build_mod/make.sh parsing the kernel
compiler from /proc/version, in set_GCC_version().

** Package changed: fglrx (Ubuntu Wily) = fglrx-installer (Ubuntu Wily)

** Changed in: fglrx-installer (Ubuntu Wily)
   Status: New = Triaged

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

Title:
  fails to build module in wily-proposed: gcc-4.9: Command not found

Status in fglrx-installer package in Ubuntu:
  Triaged
Status in fglrx-installer-updates package in Ubuntu:
  Triaged
Status in fglrx-installer source package in Wily:
  Triaged
Status in fglrx-installer-updates source package in Wily:
  Triaged

Bug description:
  As shown by the test regression of
  http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers-
  common/wily/amd64/ , fglrx and fglrx-updates fail to build the module
  in wily-proposed:

  Setting up fglrx-core (2:15.200.1-0ubuntu2) ...
  update-alternatives: using /usr/lib/fglrx-core/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) 
in auto mode
  Loading new fglrx-core-15.200.1 DKMS files...
  First Installation: checking all kernels...
  Building only for 4.1.0-3-generic
  Building for architecture x86_64
  Building initial module for 4.1.0-3-generic
  Error! Bad return status for module build on kernel: 4.1.0-3-generic (x86_64)
  Consult /var/lib/dkms/fglrx-core/15.200.1/build/make.log for more information.
   
  $ cat /var/lib/dkms/fglrx-core/15.200.1/build/make.log
  DKMS make.log for fglrx-core-15.200.1 for kernel 4.1.0-3-generic (x86_64)
  Tue Aug 11 14:44:15 CEST 2015
  /usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200.1/build: No such file 
or directory
  make.sh: 1: make.sh: gcc-4.9: not found
  make.sh: 50: [: !=: unexpected operator
  AMD kernel module generator version 2.1
  doing Makefile based build for kernel 2.6.x and higher
  rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
  make -C /lib/modules/4.1.0-3-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x modules
  make[1]: Entering directory '/usr/src/linux-headers-4.1.0-3-generic'
  arch/x86/Makefile:114: stack-protector enabled but compiler support broken
  arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support
  Makefile:667: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector 
not supported by compiler
  make[1]: gcc-4.9: Command not found
CC [M]  /var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o
  /bin/sh: 1: gcc-4.9: not found
  scripts/Makefile.build:258: recipe for target 
'/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o' failed
  make[2]: *** [/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o] 
Error 127
  Makefile:1395: recipe for target 
'_module_/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x' failed
  make[1]: *** [_module_/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x] Error 2
  make[1]: Leaving directory '/usr/src/linux-headers-4.1.0-3-generic'
  Makefile:88: recipe for target 'kmod_build' failed
  make: *** [kmod_build] Error 2
  build failed with return value 2

  So it seems fglrx hardcodes gcc-4.9 without depending on it -- only
  the default compiler is installed:

  ii  gcc  4:5.2.1-3ubuntu1 amd64GNU C compiler
  ii  gcc-55.2.1-15ubuntu1  amd64GNU C compiler
  ii  gcc-5-base:amd64 5.2.1-15ubuntu1  amd64GCC, the GNU Compiler 
Collection (base package)

  Ideally fglrx would switch to building with gcc-5 (or any gcc); if
  that's not possible, please adjust the dependencies to gcc-4.9
  explicitly.

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

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

[Desktop-packages] [Bug 1354987] Re: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS

2015-08-11 Thread Ara Pulido

We need to backport this fix to trusty

** Changed in: oem-priority
   Status: New = Triaged

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

Title:
  Can not stop wired network via All Setting-Network-Wired on Ubuntu
  OS

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project trusty series:
  New
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Trusty:
  New
Status in unity-control-center source package in Trusty:
  New

Bug description:
  Install Ubuntu 14.04 on the machine.
  After installation complete and go through OOBE to desktop, connect wired 
network cable to the UUT, and then open All Setting-Network-Wired, find 
that the wired network can not be stopped.

  Please see the attached file for detail.

  Note:
  1 .Ubuntu 14.04 LTS
  2. Can start or stop wired network via check or uncheck Enable Networking 
item at the top right corner.

  Steps to Reproduce:
  1.Install Ubuntu 14.04 on the machine.
  2.Go through OOBE to desktop.
  3.Connect wired network,try to stop wired network atAll 
Setting-Network-Wired.

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

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

[Desktop-packages] [Bug 1460982] Re: sound: Testing mono output plays back noise

2015-08-11 Thread Ara Pulido

** Changed in: oem-priority
   Status: New = Incomplete

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

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

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

Title:
  sound: Testing mono output plays back noise

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in Unity Control Center:
  Unknown
Status in unity-control-center package in Ubuntu:
  Triaged
Status in unity-control-center source package in Trusty:
  New

Bug description:
  When having a mono output source, such as BT HFP/HSP, unity-control-center by 
default plays /usr/share/sounds/freedesktop/stereo/audio-test-signal.oga 
   - which is a sample of noise.

  This makes it hard to know whether the speaker test works
  successfully, e g, if the sound output is noisy because of some bug,
  you will not notice (it's noise either way!).

  It would be better if the test button was a spoken voice, just like
  when you test Front Left, Front Right etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun  2 10:53:12 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-07 (451 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140307)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1483695] Re: fails to build module in wily-proposed: gcc-4.9: Command not found

2015-08-11 Thread Martin Pitt

This comes from /lib/modules/fglrx/build_mod/make.sh parsing the kernel
compiler from /proc/version, in set_GCC_version().

** Changed in: fglrx-installer-updates (Ubuntu Wily)
   Status: New = Triaged

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

Title:
  fails to build module in wily-proposed: gcc-4.9: Command not found

Status in fglrx-installer package in Ubuntu:
  Triaged
Status in fglrx-installer-updates package in Ubuntu:
  Triaged
Status in fglrx-installer source package in Wily:
  Triaged
Status in fglrx-installer-updates source package in Wily:
  Triaged

Bug description:
  As shown by the test regression of
  http://autopkgtest.ubuntu.com/packages/u/ubuntu-drivers-
  common/wily/amd64/ , fglrx and fglrx-updates fail to build the module
  in wily-proposed:

  Setting up fglrx-core (2:15.200.1-0ubuntu2) ...
  update-alternatives: using /usr/lib/fglrx-core/ld.so.conf to provide 
/etc/ld.so.conf.d/x86_64-linux-gnu_GFXCORE.conf (x86_64-linux-gnu_gfxcore_conf) 
in auto mode
  Loading new fglrx-core-15.200.1 DKMS files...
  First Installation: checking all kernels...
  Building only for 4.1.0-3-generic
  Building for architecture x86_64
  Building initial module for 4.1.0-3-generic
  Error! Bad return status for module build on kernel: 4.1.0-3-generic (x86_64)
  Consult /var/lib/dkms/fglrx-core/15.200.1/build/make.log for more information.
   
  $ cat /var/lib/dkms/fglrx-core/15.200.1/build/make.log
  DKMS make.log for fglrx-core-15.200.1 for kernel 4.1.0-3-generic (x86_64)
  Tue Aug 11 14:44:15 CEST 2015
  /usr/sbin/dkms: line 74: cd: /var/lib/dkms/fglrx/15.200.1/build: No such file 
or directory
  make.sh: 1: make.sh: gcc-4.9: not found
  make.sh: 50: [: !=: unexpected operator
  AMD kernel module generator version 2.1
  doing Makefile based build for kernel 2.6.x and higher
  rm -rf *.c *.h *.o *.ko *.a .??* *.symvers
  make -C /lib/modules/4.1.0-3-generic/build 
SUBDIRS=/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x modules
  make[1]: Entering directory '/usr/src/linux-headers-4.1.0-3-generic'
  arch/x86/Makefile:114: stack-protector enabled but compiler support broken
  arch/x86/Makefile:129: CONFIG_X86_X32 enabled but no binutils support
  Makefile:667: Cannot use CONFIG_CC_STACKPROTECTOR_REGULAR: -fstack-protector 
not supported by compiler
  make[1]: gcc-4.9: Command not found
CC [M]  /var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o
  /bin/sh: 1: gcc-4.9: not found
  scripts/Makefile.build:258: recipe for target 
'/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o' failed
  make[2]: *** [/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x/firegl_public.o] 
Error 127
  Makefile:1395: recipe for target 
'_module_/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x' failed
  make[1]: *** [_module_/var/lib/dkms/fglrx-core/15.200.1/build/2.6.x] Error 2
  make[1]: Leaving directory '/usr/src/linux-headers-4.1.0-3-generic'
  Makefile:88: recipe for target 'kmod_build' failed
  make: *** [kmod_build] Error 2
  build failed with return value 2

  So it seems fglrx hardcodes gcc-4.9 without depending on it -- only
  the default compiler is installed:

  ii  gcc  4:5.2.1-3ubuntu1 amd64GNU C compiler
  ii  gcc-55.2.1-15ubuntu1  amd64GNU C compiler
  ii  gcc-5-base:amd64 5.2.1-15ubuntu1  amd64GCC, the GNU Compiler 
Collection (base package)

  Ideally fglrx would switch to building with gcc-5 (or any gcc); if
  that's not possible, please adjust the dependencies to gcc-4.9
  explicitly.

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

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

[Desktop-packages] [Bug 1483750] Re: Please sync newest pcsc-lite 1.8.14-1 to Ubuntu Wily from Debian Unstable

2015-08-11 Thread Nicolas DERIVE

Here is the debdiff to perform the sync of the package with Debian
Unstable, keeping our changes.

** Patch added: debdiff between current wily package and updated one
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1483750/+attachment/4442916/+files/pcsc-lite_1.8.11-3ubuntu1_1.8.14-1ubuntu1.diff.gz

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

Title:
  Please sync newest pcsc-lite 1.8.14-1 to Ubuntu Wily from Debian
  Unstable

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  We currently have a one year old version of pcsc-lite in archive
  whereas 3 new versions have been uploaded to Debian Unstable since
  then.

  This package is pretty easy to sync with only a small change in
  debian/rules kept, to allow its use by wpasupplicant.

  Test build of ready-to-upload package is here:
  https://launchpad.net/~kalon33/+archive/ubuntu/rfid/+sourcepub/5293788
  /+listing-archive-extra

  
  Thanks for syncing :)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pcscd 1.8.11-3ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-3.3-generic 4.2.0-rc5
  Uname: Linux 4.2.0-3-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 15:32:22 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-30 (134 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150317.1)
  SourcePackage: pcsc-lite
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483753] Re: unity-settings-daemon crashed with signal 5 in _XReply()

2015-08-11 Thread Apport retracing service

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

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 #1306436, 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/1483753/+attachment/4442906/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1483753/+attachment/4442908/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1483753/+attachment/4442910/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1483753/+attachment/4442911/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1483753/+attachment/4442912/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1483753/+attachment/4442913/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1483753/+attachment/4442914/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1306436
   unity-settings-daemon crashed with signal 5 in _XReply()

** 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 unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1483753

Title:
  unity-settings-daemon crashed with signal 5 in _XReply()

Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  I started typing in a terminal emulator window and ended up back at
  the login page suddenly.  When I logged back in I found that
  /var/crash had 4 new .crash files.

  /var/crash$ ll
  total 74764
  drwxrwsrwt  2 root whoopsie 4096 Aug 11 14:39 ./
  drwxr-xr-x 16 root root 4096 Jul 13 16:08 ../
  ...
  -rw-r-  1 tt whoopsie  5218850 Aug 11 14:35 _usr_bin_python2.7.1000.crash
  -rw-r-  1 tt whoopsie 63921832 Aug 11 14:37 _usr_bin_skype.1000.crash
  -rw-r-  1 tt whoopsie  2291669 Aug 11 14:35 
_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash
  -rw-r-  1 root whoopsie   125489 Aug 11 14:39 
_usr_sbin_aptd.0.crash
  ...

  This is the bug raised for the 
_usr_lib_unity-settings-daemon_unity-settings-daemon.1000.crash one.  
  _usr_bin_python2.7.1000.crash was attributed to bug #982816
  _usr_sbin_aptd.0.crash was attributed to Bug #1022993

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu3
  Uname: Linux 4.1.0-040100rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 14:35:21 2015
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2015-03-12 (151 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  Signal: 5
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
  Title: unity-settings-daemon crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin mock plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1479913] Re: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build [FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 'pci_ignore_hotplug

** Changed in: fglrx-installer (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer-updates (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Also affects: fglrx-installer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: fglrx-installer-updates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: fglrx-installer (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: fglrx-installer-updates (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: fglrx-installer (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: fglrx-installer (Ubuntu Vivid)
   Status: New = Triaged

** Changed in: fglrx-installer-updates (Ubuntu Vivid)
   Status: New = Triaged

** Changed in: fglrx-installer (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: fglrx-installer (Ubuntu Vivid)
   Importance: Undecided = High

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: fglrx-installer-updates (Ubuntu Vivid)
   Importance: Undecided = High

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer-updates (Ubuntu Vivid)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer (Ubuntu Trusty)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer (Ubuntu Vivid)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

** Changed in: fglrx-installer (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to
  build [FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only
  symbol 'pci_ignore_hotplug']

Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in fglrx-installer source package in Trusty:
  In Progress
Status in fglrx-installer-updates source package in Trusty:
  In Progress
Status in fglrx-installer source package in Vivid:
  Triaged
Status in fglrx-installer-updates source package in Vivid:
  Triaged

Bug description:
  Have no idea what happened. Contact me if you need additional details.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.2
  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
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Thu Jul 30 12:05:59 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.19.0-25-generic, x86_64: installed
   vboxhost, 4.3.30, 3.19.0-25-generic, x86_64: installed
   vboxhost, 4.3.30, 3.19.0-26-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] 
(prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2010]
  InstallationDate: Installed on 2012-09-16 (1046 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
  MachineType: BIOSTAR Group A770E3
  PackageVersion: 2:15.200-0ubuntu4.1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic 
root=/dev/mapper/ubuntu-root ro radeon.nomodeset=1 radeon.dpm=1 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.1
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A770E3
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd04/21/2010:svnBIOSTARGroup:pnA770E3:pvr:rvnBIOSTARGroup:rnA770E3:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name:

[Desktop-packages] [Bug 1475052] Re: Cheese crashes on startup.

2015-08-11 Thread Ahmet A . Sabancı

Same happens on my computer too.

It's a clear 15.04 install, everything is up-to-date.

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

Title:
  Cheese crashes on startup.

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Cheese is unable to start, it encounters a segfault and quits.

  I don't know what extra info I could provide other than that I'm using
  bleeding edge intel drives (going to downgrade today to see if that
  changes anything).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cheese 3.14.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 15 18:25:12 2015
  InstallationDate: Installed on 2014-12-13 (214 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483816] [NEW] problem using loopback sound device

2015-08-11 Thread Gideon Walker

Public bug reported:

I am trying a simple test using a loopback sound device.

pacat -r -d alsa_output.pci-_00_1b.0.analog-stereo.monitor \
--latency=1msec \
| pacat -p -d alsa_output.pci-_00_1b.0.analog-stereo \
 --latency=1msec

I use the above command.  This is to take the microphone input and write
it to the loopback device.

(this is just a test.  once I have this working, I plan to pipe through
sox to modify the sound)

I find that when I do this and record, I get no sound at all.

If I record directly from the microphone, then the recording does have
sound.

I am using Ubuntu 14.4.3

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

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

Title:
  problem using loopback sound device

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am trying a simple test using a loopback sound device.

  pacat -r -d alsa_output.pci-_00_1b.0.analog-stereo.monitor \
  --latency=1msec \
  | pacat -p -d alsa_output.pci-_00_1b.0.analog-stereo \
   --latency=1msec

  I use the above command.  This is to take the microphone input and
  write it to the loopback device.

  (this is just a test.  once I have this working, I plan to pipe
  through sox to modify the sound)

  I find that when I do this and record, I get no sound at all.

  If I record directly from the microphone, then the recording does have
  sound.

  I am using Ubuntu 14.4.3

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

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

[Desktop-packages] [Bug 552920] Re: Moving diagonally from narrow menu title often opens adjacent menu

2015-08-11 Thread Andrea Azzarone

** Tags added: 16.04-hit-list

** Changed in: unity
   Status: Triaged = In Progress

** Changed in: unity (Ubuntu)
   Status: Triaged = In Progress

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Andrea Azzarone (azzar1)

** Changed in: unity
 Assignee: (unassigned) = Andrea Azzarone (azzar1)

** Changed in: unity
Milestone: None = 7.3.3

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

Title:
  Moving diagonally from narrow menu title often opens adjacent menu

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  In Progress
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress

Bug description:
  gtk 2.22, Ubuntu 10.10

  1. Click on the volume control to open the sound menu.
  2. Move the pointer diagonally to click on the maximum volume button.
  
https://launchpadlibrarian.net/42732636/Why_autoexpanding_indicators_are_a_bad_idea.png

  What often happens: The sound menu closes, and the menu next to it opens.
  Screencast: https://www.youtube.com/watch?v=lVUokjAlREs
  Example in an informal usability test: 
https://www.youtube.com/watch?feature=player_detailpagev=PgGbZfR6Vec#t=13m55s

  What should happen: The sound menu stays open.

  One solution would be to make the volume slider vertical. But this
  would not work for other menus (like the Bluetooth menu), and would
  look awkward with other items in the menu.

  Another solution would be to use a timer for closing the current menu
  and opening a new one. This is what Windows does for submenus. But it
  has the drawback of slowing down browsing, which would be worse for
  top-level menus than for submenus.

  GTK already has a more sophisticated solution for submenus, similar to Mac 
OS: a triangle based on the corners of the submenu and its parent item, in 
which there is a much longer delay for closing the submenu and changing the 
menu selection. 
http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/HierarchicalMenus.html
  Discussion of the invisible triangle for submenus in GTK:
  http://mail.gnome.org/archives/gtk-devel-list/2000-May/msg00118.html

  However, this feature in Gtk+ has been broken since July 2013.
  https://bugzilla.gnome.org/show_bug.cgi?id=710388 The code, once
  fixed, should be applied to menu titles as well.

  More information: http://thomaspark.co/2011/10/making-menus-
  escapable/

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

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

[Desktop-packages] [Bug 1475052] Re: Cheese crashes on startup.

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

** Changed in: cheese (Ubuntu)
   Status: New = Confirmed

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

Title:
  Cheese crashes on startup.

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Cheese is unable to start, it encounters a segfault and quits.

  I don't know what extra info I could provide other than that I'm using
  bleeding edge intel drives (going to downgrade today to see if that
  changes anything).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cheese 3.14.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 15 18:25:12 2015
  InstallationDate: Installed on 2014-12-13 (214 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 998546] Re: 0408:3003 [Packard Bell oneTwo (PW.U6C)] Touch-screen did work on 11.04 but no longer works on 12.04

2015-08-11 Thread jl451

** Changed in: xorg-server (Ubuntu)
   Status: Triaged = Opinion

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

Title:
  0408:3003 [Packard Bell oneTwo (PW.U6C)] Touch-screen did work on
  11.04 but no longer works on 12.04

Status in xorg-server package in Ubuntu:
  Opinion

Bug description:
  My touch-screen, Quanta Computer OpticalTouchScreen, used to work on
  Natty 11.04.

  But on Precise 12.04 it is not recognised.

  I understand this was supposed to have been fixed but it does not work
  on my system.

  I am not sure what other information to provide for you, so here is
  some:

  Ubuntu 12.04 LTS 64-bit (fully updated)
  Linux Daisy 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  http://askubuntu.com/questions/134505/touchscreen-broken-after-
  installing-12-04

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC662 rev1 Analog [ALC662 rev1 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paddy  2030 F pulseaudio
   /dev/snd/controlC1:  paddy  2030 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 46'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,10250012,00100101'
 Controls  : 31
 Simple ctrls  : 16
  Card1.Amixer.info:
   Card hw:1 'CNFA257'/'Chicony Electronics Co., Ltd. CNFA257 at 
usb-:00:1a.0-1.5, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB04f2:b28b'
 Controls  : 2
 Simple ctrls  : 1
  Date: Sat May 12 21:24:09 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: Packard Bell oneTwo L5861
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=a7c09981-302e-47e6-b6dc-5389ae51499e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8712u mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: oneTwo L5861
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd03/08/2011:svnPackardBell:pnoneTwoL5861:pvr:rvnPackardBell:rnoneTwoL5861:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.name: oneTwo L5861
  dmi.sys.vendor: Packard Bell

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

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

[Desktop-packages] [Bug 1419111] Re: memory leak

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

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

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

Title:
  memory leak

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  memory leak - after 8 days running /usr/bin/X uses 60% of 8 GB RAM
  -- machine is unusable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 19:54:53 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2014-03-16 (327 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  ProcEnviron:

  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483821] [NEW] elantech three finger tap not registering

2015-08-11 Thread misha wolf

Public bug reported:

I have an Asus X552EP with an elantech touchpad.
One and two finger gestures work well.
Three finger tap works in Win8 but not in Ubuntu 14.04 (3.13.0-37-generic).
I am using gnome-session flashback.

Bringing up xev I see no event for a three finger tap being generated.
I tried to cat the event device just to see if data was being produced but it
printed nothing for all mouse actions.

Other than making it work (which is really useful in some programs):
Is the problem in the kernel driver or in Xorg?
Is there a known fix?
Is there a known issue?
Does all version 4 hardware support pressure and width?

dmesg | less, search for 'elantech'
[ 486.982433] psmouse serio4: elantech: assuming hardware version 4 (with
firmware version 0x361f03)
[ 486.995279] psmouse serio4: elantech: Synaptics capabilities query result
0x10, 0x14, 0x0e.
[ 487.058078] input: ETPS/2 Elantech Touchpad as
/devices/platform/i8042/serio4/input/input23

no errors reported

Thoughts?

tia,
Mwolf

** Affects: xserver-xorg-input-synaptics (Ubuntu)
Importance: Undecided
Status: New

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

Title:
elantech three finger tap not registering

Status in xserver-xorg-input-synaptics package in Ubuntu:
New

Bug description:
I have an Asus X552EP with an elantech touchpad.
One and two finger gestures work well.
Three finger tap works in Win8 but not in Ubuntu 14.04 (3.13.0-37-generic).
I am using gnome-session flashback.

Bringing up xev I see no event for a three finger tap being generated.
I tried to cat the event device just to see if data was being produced but it
printed nothing for all mouse actions.

no errors reported

Thoughts?

tia,
Mwolf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1483821/+subscriptions

[Desktop-packages] [Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

Just to make it clear, the status of this bug report was marked as Fix
released because the fix was actually released, and it's available to
you as long as you have the trusty-updates repositories enabled (which
should be enabled by default).

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 552920] Re: Moving diagonally from narrow menu title often opens adjacent menu

** Branch linked: lp:~azzar1/unity/lp-552920

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

Title:
  Moving diagonally from narrow menu title often opens adjacent menu

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  In Progress
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  In Progress

Bug description:
  gtk 2.22, Ubuntu 10.10

  1. Click on the volume control to open the sound menu.
  2. Move the pointer diagonally to click on the maximum volume button.
  
https://launchpadlibrarian.net/42732636/Why_autoexpanding_indicators_are_a_bad_idea.png

  What often happens: The sound menu closes, and the menu next to it opens.
  Screencast: https://www.youtube.com/watch?v=lVUokjAlREs
  Example in an informal usability test: 
https://www.youtube.com/watch?feature=player_detailpagev=PgGbZfR6Vec#t=13m55s

  What should happen: The sound menu stays open.

  One solution would be to make the volume slider vertical. But this
  would not work for other menus (like the Bluetooth menu), and would
  look awkward with other items in the menu.

  Another solution would be to use a timer for closing the current menu
  and opening a new one. This is what Windows does for submenus. But it
  has the drawback of slowing down browsing, which would be worse for
  top-level menus than for submenus.

  GTK already has a more sophisticated solution for submenus, similar to Mac 
OS: a triangle based on the corners of the submenu and its parent item, in 
which there is a much longer delay for closing the submenu and changing the 
menu selection. 
http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/HierarchicalMenus.html
  Discussion of the invisible triangle for submenus in GTK:
  http://mail.gnome.org/archives/gtk-devel-list/2000-May/msg00118.html

  However, this feature in Gtk+ has been broken since July 2013.
  https://bugzilla.gnome.org/show_bug.cgi?id=710388 The code, once
  fixed, should be applied to menu titles as well.

  More information: http://thomaspark.co/2011/10/making-menus-
  escapable/

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

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

[Desktop-packages] [Bug 1419111] Re: memory leak

2015-08-11 Thread Valéry AMIOT

I've tagged this bug as affecting me as well, but need confirmation of
whether we're indeed in the same situation or not.

My Xorg process (/usr/bin/X) consumes more and more memory as time
passes when any OpenGL x.x option is selected in KDE Desktop effects'
Composite display mode parameter (on the Advanced options tab).

Selecting XRender option instead OpenGL x.x fixes this - what looks
like being a - memory leak issue but I lose the benefit of OpenGL
desktop effects :(

I didn't figure out if memory consumption increases faster or not when
playing Minecraft, but the fact is that after several hours of gaming, I
could end up with Xorg consuming ~ 2 GB :( Unless my KDE is configured
to use the XRender composite display mode as explained above.

I'd suspect the AMD fglrx proprietary driver to cause this memory leak,
while not being totally sure of it...

$ fglrxinfo
display: :0  screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon (TM) R7 300 Series  
OpenGL version string: 4.4.13374 Compatibility Profile Context 15.20.1013

$ apt list fglrx
Listing... Done
fglrx/trusty-updates,now 2:15.200-0ubuntu0.3 amd64 [installed]

Any feedback appreciated :)

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

Title:
  memory leak

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  memory leak - after 8 days running /usr/bin/X uses 60% of 8 GB RAM
  -- machine is unusable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 19:54:53 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2014-03-16 (327 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  ProcEnviron:

  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1482887] Re: NetworkManager not setting given DNS in resolv.conf

2015-08-11 Thread d3bugg3r

** Information type changed from Private Security to Public

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

Title:
  NetworkManager not setting given DNS in resolv.conf

Status in network-manager package in Ubuntu:
  New

Bug description:
   SYSTEM INFOS 
  # lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

  # dpkg --list cinnamon resolvconf network-manager
  ii  cinnamon2.2.16 amd64  Cinnamon desktop
  ii  network-manager 0.9.8.8-0ubunt amd64  network management 
framework (daemon and userspace tools)
  ii  resolvconf  1.69ubuntu1.1  allname server information 
handler

  --

  So, it looks like a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161
  but this was on KDE in 2009 and I doubt it would have anything to do
  with it...

  Anyway, here is how to reproduce the problem:
  - Go to network-manager settings GUI (network indicator - Network 
connections)
  - Edit current connection (wlan0 in my case)
  - Go to IPv4 settings
  - Select DHCP (addresses only)
  - Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC 
project)
  - Click save
  - Click disconnect
  - Click connect

  In the summary, you can see the DNS server you just typed. But if you
  # cat /etc/resolv.conf
  then you see the DNS server provided by your DHCP server (in my case 
192.168.1.1)

  So the only way to bypass DHCP's DNS settings is to hard-code the DNS
  in /etc/resolvconf/resolv.conf.d/head

  Since this can lead users to believe that they are using their
  favorite DNS server while they get answers from their ISP/Hotspot DNS,
  I checked the 'Security' box.

  This could also be related to
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437

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

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

[Desktop-packages] [Bug 1419111] Re: memory leak

2015-08-11 Thread Valéry AMIOT

Adding that with XRender option selected, my Xorg usually consumes ~ 40 MB - 
may I play Minecraft or not.
Note: my display resolution is 1920x1200.

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

Title:
  memory leak

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  memory leak - after 8 days running /usr/bin/X uses 60% of 8 GB RAM
  -- machine is unusable

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Fri Feb  6 19:54:53 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2014-03-16 (327 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140225)
  ProcEnviron:

  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1483560] Re: Screen tearing with bumblebee

2015-08-11 Thread Andrew

Downgrading packages nvidia-340, nvidia-340-uvm, nvidia-libopencl1-340
and nvidia-opencl-icd-340 to 331 version solved the issue.

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

Title:
  Screen tearing with bumblebee

Status in xorg package in Ubuntu:
  New

Bug description:
  After last nvidia drivers update, I've noticed screen tearing on fast
  cursor moving in menus, also in 720p video in VLC and even in
  QtCreator text editor. I have bumblebee running intel i915 and NVIDIA
  GF117M.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: wl nvidia
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.76  Thu Jan 22 12:11:08 
PST 2015
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04)
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 10:41:09 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-61-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.13.0-61-generic, x86_64: installed
   nvidia-340, 340.76, 3.13.0-61-generic, x86_64: installed
   vboxhost, 4.3.30, 3.13.0-61-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3808]
 Subsystem: Lenovo Device [17aa:380e]
  InstallationDate: Installed on 2015-01-25 (197 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: LENOVO 20252
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash intel_iommu=igfx_off 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8ECN95WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Ginkgo 7A1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G710
  dmi.modalias: 
dmi:bvnLENOVO:bvr8ECN95WW:bd05/12/2014:svnLENOVO:pn20252:pvrLenovoG710:rvnLENOVO:rnGinkgo7A1:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoG710:
  dmi.product.name: 20252
  dmi.product.version: Lenovo G710
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Aug 11 10:31:35 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16982 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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

[Desktop-packages] [Bug 1466290] Re: Update to 3.16

2015-08-11 Thread Jamie Strandboge

Having the binaries that depend on webkit2gtk be in universe with
webkitgtk2 source only in main is fine (so long as later we don't allow
its binaries to be promoted-- note the MainINclusionRequests page has
this to say New binary packages from existing source packages, where
the source package is already in main, do not require reports), so we
probably need to refine that language.

I don't understand  how source only promotion is going to fix the issue.
Aren't the packages that use webkitgtk2 going to pull the -dev and the
corresponding lib* packages from webkitgtk2 in during the build, and
therefore those webkitgtk2 packages also need to be in main? (Did I miss
a change to the archive on this point?)

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

Title:
  Update to 3.16

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Update to 3.16

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

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

[Desktop-packages] [Bug 998546] Re: 0408:3003 [Packard Bell oneTwo (PW.U6C)] Touch-screen did work on 11.04 but no longer works on 12.04

2015-08-11 Thread Paddy Landau

This has been changed to Opinion, which means that this doesn't fit
with the project (despite the fact that it used to work on Ubuntu
version 11.04).

Please would you tell me where I should file this bug report instead? I
have absolutely no idea how to proceed.

Thank you.

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

Title:
  0408:3003 [Packard Bell oneTwo (PW.U6C)] Touch-screen did work on
  11.04 but no longer works on 12.04

Status in xorg-server package in Ubuntu:
  Opinion

Bug description:
  My touch-screen, Quanta Computer OpticalTouchScreen, used to work on
  Natty 11.04.

  But on Precise 12.04 it is not recognised.

  I understand this was supposed to have been fixed but it does not work
  on my system.

  I am not sure what other information to provide for you, so here is
  some:

  Ubuntu 12.04 LTS 64-bit (fully updated)
  Linux Daisy 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  http://askubuntu.com/questions/134505/touchscreen-broken-after-
  installing-12-04

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC662 rev1 Analog [ALC662 rev1 
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  paddy  2030 F pulseaudio
   /dev/snd/controlC1:  paddy  2030 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe52 irq 46'
 Mixer name : 'Realtek ALC662 rev1'
 Components : 'HDA:10ec0662,10250012,00100101'
 Controls  : 31
 Simple ctrls  : 16
  Card1.Amixer.info:
   Card hw:1 'CNFA257'/'Chicony Electronics Co., Ltd. CNFA257 at 
usb-:00:1a.0-1.5, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB04f2:b28b'
 Controls  : 2
 Simple ctrls  : 1
  Date: Sat May 12 21:24:09 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301)
  MachineType: Packard Bell oneTwo L5861
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=a7c09981-302e-47e6-b6dc-5389ae51499e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: r8712u mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: oneTwo L5861
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd03/08/2011:svnPackardBell:pnoneTwoL5861:pvr:rvnPackardBell:rnoneTwoL5861:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.name: oneTwo L5861
  dmi.sys.vendor: Packard Bell

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

-- 
Mailing list: https://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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation

On 31-05-15 03:23:09, KennoVO wrote:
 Nice! Will this work with the 3.13 kernel in 14.04 ? Also, do you have
 any idea when it will be available to end-users?

Yes, the update is available in 14.04, and works with the kernels 14.04
ships with.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

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

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

[Desktop-packages] [Bug 1482887] Re: NetworkManager not setting given DNS in resolv.conf

2015-08-11 Thread d3bugg3r

** Information type changed from Public to Public Security

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

Title:
  NetworkManager not setting given DNS in resolv.conf

Status in network-manager package in Ubuntu:
  New

Bug description:
   SYSTEM INFOS 
  # lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

  # dpkg --list cinnamon resolvconf network-manager
  ii  cinnamon2.2.16 amd64  Cinnamon desktop
  ii  network-manager 0.9.8.8-0ubunt amd64  network management 
framework (daemon and userspace tools)
  ii  resolvconf  1.69ubuntu1.1  allname server information 
handler

  --

  So, it looks like a duplicate of
  https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161
  but this was on KDE in 2009 and I doubt it would have anything to do
  with it...

  Anyway, here is how to reproduce the problem:
  - Go to network-manager settings GUI (network indicator - Network 
connections)
  - Edit current connection (wlan0 in my case)
  - Go to IPv4 settings
  - Select DHCP (addresses only)
  - Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC 
project)
  - Click save
  - Click disconnect
  - Click connect

  In the summary, you can see the DNS server you just typed. But if you
  # cat /etc/resolv.conf
  then you see the DNS server provided by your DHCP server (in my case 
192.168.1.1)

  So the only way to bypass DHCP's DNS settings is to hard-code the DNS
  in /etc/resolvconf/resolv.conf.d/head

  Since this can lead users to believe that they are using their
  favorite DNS server while they get answers from their ISP/Hotspot DNS,
  I checked the 'Security' box.

  This could also be related to
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
  - 
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437

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

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

[Desktop-packages] [Bug 1436553] Re: Transparent windows render black with Gtk3.16 and compiz

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

** Changed in: compiz
   Status: New = Fix Committed

** Changed in: compiz
   Importance: Undecided = Medium

** Changed in: compiz (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Transparent windows render black with Gtk3.16 and compiz

Status in Compiz:
  Fix Committed
Status in compiz package in Ubuntu:
  Confirmed

Bug description:
  Running compiz_1%3a0.9.12.0+15.04.20150202-0ubuntu1 without unity (in
  mate compiled with gtk-3) and testing Gtk-3.16 I run into serious
  issues with failures to render certain Gtk Windows transparent.
  Hardware is AMD FX 8120 with radeon HD 6750 GPU.

  My theme sets popup windows used by menus transparent, and Gtk
  application windows with client side decoration (CSD) have
  transparency underlying the GtkHeaderBar. In the latter case this is
  what makes rounded corners possible.   The transparent popup windows
  used with my theme to support menus resembling gnome-shell's widgets
  in my hacked Gtk3 version of mate-panel work fine with Gtk3.14 but due
  to the window issue get black corners with compiz and Gtk-3.16.
  Windows drawn transparent with cairo still work, but windows set
  transparent by GTK usually do not,

  Changing the window manager to Mutter makes transparency work
  perfectly. In Gtk-3.14 transparency works in Metacity with compositing
  enabled, it does not with gtk-3.16.

  I am not sure whether this should be considered a compiz bug or a Gtk
  bug, but since transparency works fine in gnome-shell and mutter (as
  used by shell), I am not sure the GNOME team would consider this a bug
  they are willing to fix.  If nobody fixes this any GNOME application
  that forces client side decoration (such as the gtk3-demo or gtk3
  -widget-factory) will be ugly in Ubuntu unless the client side
  decorations have square corners.

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

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

[Desktop-packages] [Bug 1475052] Re: Cheese crashes on startup.

2015-08-11 Thread Alberto Salvia Novella

** Changed in: cheese (Ubuntu)
   Importance: Undecided = High

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

Title:
  Cheese crashes on startup.

Status in cheese package in Ubuntu:
  Confirmed

Bug description:
  Cheese is unable to start, it encounters a segfault and quits.

  I don't know what extra info I could provide other than that I'm using
  bleeding edge intel drives (going to downgrade today to see if that
  changes anything).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cheese 3.14.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 15 18:25:12 2015
  InstallationDate: Installed on 2014-12-13 (214 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: cheese
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor

2015-08-11 Thread Václav Haisman

For cross reference:  #1483868.

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

Title:
  keyboard doesn't work after screensaver shuts down the monitor

Status in gnome-screensaver package in Ubuntu:
  Incomplete
Status in xscreensaver package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: gnome-screensaver

  The keyboard doesn't work when I return to work on the computer after
  a few minutes, long enough for the screen to go blank.

  To reproduce: 
  Don't touch the keyboard nor mouse for a while.
  After the first 5 minutes, the screensaver kicks in (matrix).
  On minute 10, the screen goes blank.
  Wait a few more minutes.
  Move the mouse or press a key to keep working.

  Just type something in the window you have already opened you'll
  notice that the active window does not receive any keyboard input, and
  you can't even press alt-tab to switch to another window.

  Of course, i expect the keyboard to work as usual but it does not.

  Here, when the keyboard doesn't work, you can switch to another window
  using the mouse and the keyboard will return to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Thu May 27 14:47:06 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=es_PE.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

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

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

[Desktop-packages] [Bug 1483868] [NEW] keyboard doesn't work after xscreensaver shuts down the monitor

2015-08-11 Thread Václav Haisman

Public bug reported:

I am experiencing the same symptoms as described in
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/586528.
This bug report is new on request.

I run Xubuntu with XFCE, xscreensaver and Light Locker. Recently,
whenever I log back (twice, once through locker and once through
xscreensaver), the X11 applications are not accepting keyboard input. I
can switch desktops using keyboard shortcuts, though. What fixes the
issue for me is switching into a Terminal window. Then the keyboard
input start working.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xscreensaver 5.30-1ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-25.26-lowlatency 3.19.8-ckt2
Uname: Linux 3.19.0-25-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 11 21:23:04 2015
InstallationDate: Installed on 2011-11-13 (1367 days ago)
InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: xscreensaver
UpgradeStatus: Upgraded to vivid on 2015-04-25 (108 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  keyboard doesn't work after xscreensaver shuts down the monitor

Status in xscreensaver package in Ubuntu:
  New

Bug description:
  I am experiencing the same symptoms as described in
  https://bugs.launchpad.net/ubuntu/+source/gnome-
  screensaver/+bug/586528. This bug report is new on request.

  I run Xubuntu with XFCE, xscreensaver and Light Locker. Recently,
  whenever I log back (twice, once through locker and once through
  xscreensaver), the X11 applications are not accepting keyboard input.
  I can switch desktops using keyboard shortcuts, though. What fixes the
  issue for me is switching into a Terminal window. Then the keyboard
  input start working.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xscreensaver 5.30-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-lowlatency 3.19.8-ckt2
  Uname: Linux 3.19.0-25-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug 11 21:23:04 2015
  InstallationDate: Installed on 2011-11-13 (1367 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: xscreensaver
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (108 days ago)

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

-- 
Mailing list: https://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 1460080] Re: HP laserjet 1018 no longer works

2015-08-11 Thread Tristram Shorter

Hi Till!

Sorry I didn't answer before. I was at home, not near the hp printer.

I have again tried to print. As I had uninstalled HPLIP, I re-installed
it. The version is now: 3.15.4. Device Manager Version 15.0 (Qt4).

It still doesn't work.

I get a notice which says: Print job failed - required plugin missing.

If you could help I would be really grateful.

Best regards,

Tristram


 Date: Mon, 27 Jul 2015 13:59:31 +
 From: 1460...@bugs.launchpad.net
 To: tdshor...@hotmail.com
 Subject: [Bug 1460080] Re: HP laserjet 1018 no longer works
 
 ** Changed in: hplip (Ubuntu)
  Assignee: (unassigned) = Till Kamppeter (till-kamppeter)
 
 -- 
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1460080
 
 Title:
   HP laserjet 1018 no longer works
 
 Status in HPLIP:
   Incomplete
 Status in hplip package in Ubuntu:
   New
 
 Bug description:
   My first experience of Ubuntu was Utopic Unicorn, about 2 months ago. I 
 installed HPLIP, so as to use my HP Laserjet 1018 printer, and it all worked 
 fine. On upgrading to Ubuntu 15.04, my printer stopped working. I have tried 
 everything I can think of: upgrading HPLIP, removing HPLIP and installing an 
 alternative driver (foomatic), deleting and adding the printer, nothing 
 works. I have also downloaded and installed all updates to Ubuntu. I have 
 noticed, checking through previous bug reports, that this appears to be a 
 recurring problem: people's HP printers work OK until, on upgrading Ubuntu, 
 they suddenly stopped working. Can it be that beta versions are not being 
 properly tested? Having spent most of yesterday on this problem, and having 
 being seriously ticked off by my boss, about it, I am unwilling to spend 
 further time on it. I was going to include some screens shots to support my 
 case, but I can't see how to do this. Here are some more details:
   As of now:
   listed printers are: Canon ip1900 series
  HP Laserjet 1018 (default) / Enabled -- 
 OK / Shared -- OK
  
 Description: Hewlett-Packard HP LaserJet 1018
  
 Location: tristram-Aspire-5570Z
  
 Device URI: usb://HP/LaserJet%201018?serial=LF04EKT
  Make 
 and Model: HP LaserJet 1018 Foomatic/foo2zjs-z1 (recommended)
  
 Printer state: Idle - Sending data to printer.
 
   Trying to print a test page produces a little box that says: Submitted - 
 Test page submitted as job (whatever)
   Noticing that, above, the driver appears to be set to Foomatic, I tried 
 changing it. Now it reads:
  Make 
 and Model: HP LaserJet 1018, hpcups 3.15.4, requires proprietary plugin
 
   I pressed the Print Test Page button, and got:  Submitted - Test page 
 submitted as job 64. As usual, nothing happens.
   All this time, the printer is turned on, and connected to my laptop via USB 
 cable, needless to say. On viewing Document print status I have: Job: 64 
 /User: tristram /Document: Test Page / Printer: 
 Hewlett-Packard-HP-LaserJet-1018 / Size: 1k /Time submitted: 11 minutes ago / 
 Status (printer appears with a red sign) : Stopped - Printer error
   On viewing job attributes, I have (for instance, a screen shot would be 
 really useful here):
   job-more-info: http://localhost:631/jobs/64 (...)
   job-printer-state-message: Filter failed
   job-printer-state-reasons: ['hplip.plugin-error'] (...)
   job-state-reasons: job-completed-with-errors  (...)
 
   There's more info in this report, but I don't know what you need...
 
   I hope this is enough for you people to work on. Meanwhile, I'm
   seriously thinking of downgrading my Ubuntu version to what it was
   before, and HPLIP also, except that I don't know for sure what the
   working version was
 
   Thank you very much,
 
   Tristram
 
   ProblemType: Bug
   DistroRelease: Ubuntu 15.04
   Package: hplip 3.15.2-0ubuntu4.1
   ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
   Uname: Linux 3.19.0-18-generic i686
   ApportVersion: 2.17.2-0ubuntu1.1
   Architecture: i386
   CupsErrorLog:
E [29/May/2015:09:53:50 -0300] [cups-deviced] PID 12270 (hpfax) stopped 
 with status 1!
E [29/May/2015:09:54:39 -0300] [cups-deviced] PID 12722 (hpfax) stopped 
 with status 1!
W [29/May/2015:09:55:28 -0300] CreateProfile failed: 
 org.freedesktop.ColorManager.AlreadyExists:profile id 
 'Hewlett-Packard-HP-LaserJet-1018-Gray..' already exists
   CurrentDesktop: Unity
   Date: Fri May 29 10:00:31 2015
   InstallationDate: Installed on 2015-01-15 (134 days ago)
   InstallationMedia: Ubuntu 14.10 Utopic Unicorn -

[Desktop-packages] [Bug 971051] Re: No Alt+Tab in gnome classic session (switcher plugin not loaded)

** Changed in: compiz (Ubuntu)
   Status: Triaged = In Progress

** Changed in: compiz
   Status: New = Invalid

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

Title:
  No Alt+Tab in gnome classic session (switcher plugin not loaded)

Status in Compiz:
  Invalid
Status in Ubuntu GNOME Flashback:
  New
Status in compiz package in Ubuntu:
  In Progress
Status in gnome-session package in Ubuntu:
  New
Status in Baltix:
  New

Bug description:
  When using the Gnome Classic session (with Compiz) in Ubuntu Precise
  Pangolin, I cannot use alt + tab to switch applications.

  WORKAROUND:
  1. Install packages:
 sudo apt-get install compiz-plugins compizconfig-settings-manager
  2. Run ccsm
  3. Scroll down to Window Management and enable (tick) Application Switcher.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-panel 1:3.4.0-0ubuntu1
  Uname: Linux 3.3.0-030300-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  Date: Sun Apr  1 21:01:11 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120108)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

2015-08-11 Thread Tony Espy

** Changed in: network-manager (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Fix Committed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  In Progress

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

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

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

[Desktop-packages] [Bug 1475721] Re: (Horizontally) Maximized and Fullscreen Windows activated in different workspace move to primary display

** Changed in: compiz
   Status: In Progress = Fix Committed

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

Title:
  (Horizontally) Maximized and Fullscreen Windows activated in different
  workspace move to primary display

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in compiz package in Ubuntu:
  In Progress

Bug description:
  Prerequisite: multi monitor and multi workspace environment

  1) Move to a secondary workspace and open your default browser (firefox, 
chrome...)
 window, then move it to the secondary monitor¹ and maximize it (or full 
screen it).
  2) Move to the primary workspace and in a terminal launch:
 xdg-open http://ubuntu.com
  3) Now move back to the secondary workspace

  Expected:
  4) The browser loads Ubuntu homepage and is still in the secondary monitor 
(where it
 used to be)

  Actual:
  4) The browser loads Ubuntu homepage, but it has been moved to the primary 
monitor.

  I attached a video where this is displayed by showing that the browser 
maximized is in monitor 3 of workspace, I go to different workspace, click a 
link, upon returning the window is now in the laptop monitor.
  This only happens when the window is maximized.

  [1] primary monitor could change in compiz (and not match the xrandr
  one), then you might need to try to figure which one is yours.

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

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

[Desktop-packages] [Bug 1465647] Re: GNOME classic session using Compiz does not switch windows on Alt+TAB

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

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

** Changed in: compiz (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  GNOME classic session using Compiz does not switch windows on Alt+TAB

Status in compiz package in Ubuntu:
  In Progress
Status in gnome-session package in Ubuntu:
  New

Bug description:
  On Ubuntu 12.04, the GNOME Classic session based on Compiz does not
  provide the Alt-TAB window switching. The 'no effects' session (based
  on metacity)  however does.

  The reason is that the Compiz used does not include the Compiz
  'switcher' plugin. It is contained in the  compiz-plugins package,
  which is not installed.

  Should be fixed cleanly: The package gnome-session-fallback should not
  provide a session that depends on compiz, without providing compiz and
  the compiz-plugins package. And maybe a script that add 'switcher' to
  the default enabled plugins (seems to be using the gconf backend, so
  it just need to bring an additional gconf file I guess) is needed.

  If gnome-session-fallback should not depend on compiz, the Classic
  session using compiz may move to a new package, and this one only
  contains 'no effect' variant then.

  This is actually a variant of bug #971051 which is filed against
  compiz, which is wrong I guess, as it is not a problem of compiz
  itself, but rather its configuration in the gnome fallback package.

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

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

[Desktop-packages] [Bug 1237057] Re: Huge icons with Apllication Switcher (Alt-Tab) (Icon, but not Only show icon)