[Desktop-packages] [Bug 1517562] [NEW] package fglrx-updates-core (not installed) failed to install/upgrade: attemp to overwrite, »/usr/bin/clinfo« which is in package clinfo 2.0.15.04.28-1

[Johannes]

Public bug reported:

sudo apt-get install fglrx-update causes problem if package clinfo is
already installed.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: fglrx-updates-core (not installed)
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 18 17:57:14 2015
DistUpgraded: 2015-11-11 19:07:48,913 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed
 virtualbox-guest, 5.0.4, 4.2.0-18-generic, x86_64: installed
DuplicateSignature: package:fglrx-updates-core:(not installed):Versuch, 
»/usr/bin/clinfo« zu überschreiben, welches auch in Paket clinfo 2.0.15.04.28-1 
ist
ErrorMessage: Versuch, »/usr/bin/clinfo« zu überschreiben, welches auch in 
Paket clinfo 2.0.15.04.28-1 ist
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 
OEM] [1002:6810] (prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Device [1787:201c]
InstallationDate: Installed on 2015-11-11 (6 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=99bcc9e4-5b16-4fc9-9b4c-da5ec1767175 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5
 apt  1.0.10.2ubuntu1
SourcePackage: fglrx-installer-updates
Title: package fglrx-updates-core (not installed) failed to install/upgrade: 
Versuch, »/usr/bin/clinfo« zu überschreiben, welches auch in Paket clinfo 
2.0.15.04.28-1 ist
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-11-11 (6 days ago)
dmi.bios.date: 08/22/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3905
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3905:bd08/22/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Nov 18 17:46:27 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: radeon

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


** Tags: amd64 apport-package compiz-0.9 need-duplicate-check ubuntu wily

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

Title:
  package fglrx-updates-core (not installed) failed to install/upgrade:
  attemp to overwrite, »/usr/bin/clinfo« which is in package clinfo
  2.0.15.04.28-1

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

Bug description:
  sudo apt-get install fglrx-update causes problem if package clinfo is
  already installed.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-updates-core (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 18 17:57:14 2015
  DistUpgraded: 2015-11-11 19:07:48,913 DEBUG enabling apt cron job
  DistroCodename: 

[Desktop-packages] [Bug 1505705] Re: [sound] Subwoofer slider works in mysterious ways

[Sebastien Bacher]

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

** Also affects: gnome-control-center via
   https://bugzilla.gnome.org/show_bug.cgi?id=753847
   Importance: Unknown
   Status: Unknown

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

Title:
  [sound] Subwoofer slider works in mysterious ways

Status in gnome-control-center:
  Unknown
Status in HWE Next:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  Sometimes it follows master volume and sometimes it doesn't.

  Same as:
  https://bugzilla.gnome.org/show_bug.cgi?id=753847

  Also raised by OEM team.

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

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

[Desktop-packages] [Bug 1517542] Re: xdg-open doesn't allow more than 64 characters after the protocol:// part

[Stefan Freyr]

I should note that I'm on kubuntu 14.04 and the version of xdg-open I'm
using is 1.0.2.

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

Title:
  xdg-open doesn't allow more than 64 characters after the protocol://
  part

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  This may actually not be a bug I guess but I still think it's a bit
  strange.

  Our application is using quite a lot more than 64 characters there so
  I'm wondering whether we're breaking some standard (I can't find
  anything about what the length can be).

  But at least our problem is that our application does not launch
  properly which may be our own fault but in case it's not I wanted to
  check whether this 64 character limitation is actually based on some
  specification somewhere or whether this is  just a random decision and
  if so, whether this length should perhaps be increased?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1517542/+subscriptions

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

[Desktop-packages] [Bug 1510573] Re: fglrx should blacklist amdgpu

[Mathew Hodson]

** Tags removed: verification-needed
** Tags added: wily

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

Title:
  fglrx should blacklist amdgpu

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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Mathew Hodson]

** Project changed: fglrx => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions

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

[Desktop-packages] [Bug 1509005] Re: [regression] mir-client-platform-mesa-dev pkg-config file dropped

[Mathew Hodson]

** Changed in: mir (Ubuntu)
   Importance: Critical => Medium

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

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

Title:
  [regression] mir-client-platform-mesa-dev pkg-config file dropped

Status in Mir:
  Fix Committed
Status in mesa package in Ubuntu:
  Fix Released
Status in mir package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Fix Released
Status in mesa source package in Wily:
  Confirmed
Status in mir source package in Wily:
  Confirmed
Status in xorg-server source package in Wily:
  Fix Committed

Bug description:
  the mir-client-platform-mesa-dev pkg-config file was dropped in wily,
  leading to build errors for such optional packages like mesa and xorg-
  server.

  Even if you have a feature freeze exception, you shouldn't break
  existing API's after feature freeze.

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

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

[Desktop-packages] [Bug 1507062] Re: After suspend resume network manager fails to set default route entry to routing table for mobile broadband connection

[Pauli]

Seems like network-manager 1.0.4-0ubuntu5.1 fixed this bug. That makes
this like duplicate of LP: #1512749

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

Title:
  After suspend resume network manager fails to set default route entry
  to routing table for mobile broadband connection

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is regression from 10.04.

  It seems to reproduce often but not always which might point to some
  kind of race condition handled badly.

  Basic setup:
  * Huawei USB 3G modem
  * Network manager set to auto connect with saved pin
  * Laptop which has very few suspend-resume issues so I use suspending all the 
time

  I noticed the bug that modem led and network manager indicated that
  there was a connection. But connection didn't seems to work.

  My initial workaround in hurry was just to pull the modem from laptop
  and restart both modem manager and network manager. (they don't like
  modem unplugging or individual restarts but those are long standing
  separated bugs that I haven't cared to report) After restarting
  connection comes up working.

  I decided to investigate what is broken after resume and I could
  narrow issue to be that default route is missing from routing table.
  That resulted to very simple fix where I can simple manually add the
  missing default route.

  Broken table after suspend:

  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  link-local  *   255.255.0.0 U 1000   00 ppp0
  rantapallo  *   255.255.255.255 UH75000 ppp0

  Working table before suspend:
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  default *   0.0.0.0 U 75000 ppp0
  link-local  *   255.255.0.0 U 1000   00 ppp0
  rantapallo  *   255.255.255.255 UH75000 ppp0

  
  Command to add the missing route manually:

  sudo route add default netmask 0.0.0.0  metric 750 dev ppp0

  
  That is at least so far only missing part of connection setup after suspend. 
I will report a separate bug if I see a different error causing similar 
reconnecting failure after suspend-resume.

  apport should include syslog with detailed log from suspend-resume and
  service restarts to get correct route tables.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3
  Uname: Linux 4.2.0-15-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Oct 17 03:19:00 2015
  InstallationDate: Installed on 2011-11-02 (1444 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IpRoute:
   default dev ppp0  scope link  metric 750 
   169.254.0.0/16 dev ppp0  scope link  metric 1000 
   176.93.96.110 dev ppp0  proto kernel  scope link  src 176.93.96.110  metric 
750
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to wily on 2015-10-10 (6 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTIONCON-UUID  CON-PATH
   
   ttyUSB0  gsm   connected/org/freedesktop/NetworkManager/Devices/3  
Dna dna internet  17b039cf-5b74-42af-af9a-d84c2519b250  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/0  
------  
   
   wlan0wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
------  
   
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
------
  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/1507062/+subscriptions

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

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Tony Espy]

And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.

I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my previous theory is on track ( ie. that reference counting
may be the cause ).  That said, I'll need to add some more logging and
rebuild...

Also, while examining the DBus log, it looks like every time the plugin
sees a 'PropertiesChanged' message from the AccessPoint, it calls
"GetAll", which is pointless as all the changed properties are
transmitted with the signal...

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Matheus]

After the fix release, in order for the drivers to work properly do I
still need to blacklist amdgpu or run the 'amdconfig --adapter=all
--initial'? Cheers

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

Title:
  FGLRX incompatible with gcc 5

Status in Release Notes for Ubuntu:
  Fix Released
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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+subscriptions

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

[Desktop-packages] [Bug 1511301] Please test proposed package

[Chris J Arges]

Hello Kai-Heng, or anyone else affected,

Accepted fglrx-installer-updates into trusty-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/fglrx-installer-updates/2:15.200-0ubuntu0.6 in a few hours, and then in
the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

Status in fglrx-installer package in Ubuntu:
  Invalid
Status in fglrx-installer-updates package in Ubuntu:
  Invalid
Status in fglrx-installer source package in Trusty:
  Fix Committed
Status in fglrx-installer-updates source package in Trusty:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  Upgrading from the upstream fglrx driver packages to the packages in
  the Ubuntu repository fails because the /etc/ati directory is a real
  directory instead of being a link (which was common in the Ubuntu
  packages).

  [Test Case]
  1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages 
from the AMD installer 
  2. Upgrade the package to the current ubuntu release.
  3. Check the apt-get output 

  Expected results: the fglrx module should be updated correctly.

  Actual results:
  The update fails as described below.

  [Regression Potential]
  Low. The change only affects a migration from a specific release.

  
  __
  Note that the fglrx 14.502 package name is 
fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from 
Ubuntu repository.

  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for install-info (5.2.0.dfsg.1-2) ...
  Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ...

  (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for doc-base (0.10.5) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:
   /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb
  Log ended: 2015-10-22 05:31:11

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

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

[Desktop-packages] [Bug 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks

[Adam]

Me too.  Same problem, and downgrading fixes it for me too.

What exactly do the WPA Supplicant people think is wrong with the RADIUS
servers?  I can't find that anywhere online.

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

Title:
  Wily's wpasupplicant frequently fails on WPA enterprise networks

Status in hostap:
  Unknown
Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from vivid to wily on my laptop, I'm running
  into problems when connecting to my home WPA2 enterprise network.

  Typically the first connection immediately after the driver is loaded
  works as expected, however any further reconnection and the occasional
  roaming between APs cause wpasupplicant to freeze entirely requiring
  me to kill it and most often also reload my wireless driver to get
  things working again.

  ## A failed (hanging) association looks like:
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): Activation: 
(wifi) connection 'stgraber.net-secure' has security, and secrets exist.  No 
new secrets needed.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'ssid' 
value 'stgraber.net-secure'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'scan_ssid' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'key_mgmt' value 'WPA-EAP'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'eap' 
value 'TLS'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'fragment_size' value '1300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key_passwd' value ''
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'identity' value 'castiana'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'bgscan' value 'simple:30:-65:300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'proactive_key_caching' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Connection 
disconnected (reason -3)
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associated -> disconnected
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: set interface 
ap_scan to 1
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: disconnected -> scanning
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to 
authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate 
with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: scanning -> authenticating
  Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated
  Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: authenticating -> associating
  Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 
24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associating -> associated
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD 
EAP vendor 0 method 13 (TLS) selected
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=2 
subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal 
Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root 
CA/emailAddress=stgra...@stgraber.org' 

[Desktop-packages] [Bug 993655] Re: Unity looses mouse click handler when using enabling USB headset

[Christian Löpke]

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

I can confirm this bug with a Corsair VOID RGB wireless headset. 
Mouse movement works all the time but sometimes (every 15 min ca.) mouse clicks 
are not recognized any more till I switch tty with strg+alt+F1 and back to 
seven.

Im using XUbuntu 15.04 and really want to help.
But I dont know where to look for debug outputs.

Can someone help me ?
Which informations are required to debug this ?

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

Title:
  Unity looses mouse click handler when using enabling USB headset

Status in xorg-server package in Ubuntu:
  Expired
Status in xorg-server package in Debian:
  Unknown
Status in xorg-server package in Fedora:
  Unknown

Bug description:
  I have a Plantronics D100 headset.

  When I press the button on the headset to enable it, Unity looses its
  click handler, in that it can not click and drag windows.

  The cursor is visible and moves just fine. I can switch applications
  using Alt+Tab, and I can launch new applications using the keyboard.
  But I cannot close the existing window, or change focus to another
  window by using the mouse.

  The Headset microphone and speaker work just fine!

  Tested this on a laptop and desktop machine. Both running Ubuntu
  12.04.

  The headset I'm using is a Plantronics D100 unit.

  I have had this problem for the past month while on the 12.04 beta release. 
  --- 
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  NonfreeKernelModules: nvidia
  Package: unity 5.10.0-0ubuntu6
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Tags:  precise
  Uname: Linux 3.2.0-24-generic x86_64
  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/xorg-server/+bug/993655/+subscriptions

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

[Desktop-packages] [Bug 1299073] Re: [desktop] Video recording is not working

[Florian Boucault]

** Changed in: camera-app
   Status: In Progress => Confirmed

** Changed in: camera-app (Ubuntu)
   Status: In Progress => 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/1299073

Title:
  [desktop] Video recording is not working

Status in camera-app:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in cheese package in Ubuntu:
  Confirmed
Status in guvcview package in Ubuntu:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Video recording used to work fine on my trusty desktop, but now it
  freezes the application and video does not record.

  Steps to reproduce:

  1) Start camera-app in desktop mode ($ DESKTOP_MODE=1 camera-app)
  2) Switch to video
  3) Press the red button

  Expected behaviour:

  The app records  video correctly

  Actual behaviour:

  The videocamera freezes (still image) and video is not recorded
  The following error shows in the terminal:

  libv4l2: error setting pixformat: Device or resource busy
  CameraBin error: "Device '/dev/video0' is busy" 
  CameraBin error: "Could not negotiate format" 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: camera-app 2.9.1+14.04.20140307-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 28 16:32:32 2014
  InstallationDate: Installed on 2013-06-17 (283 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: camera-app
  UpgradeStatus: Upgraded to trusty on 2014-01-20 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1299073/+subscriptions

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

[Desktop-packages] [Bug 1481561] Re: Connect to XDMCP clients on address requests come from if available

[Chris J Arges]

** Tags removed: verification-done-vivid
** Tags added: verification-failed

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

Title:
  Connect to XDMCP clients on address requests come from if available

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Currently LightDM connects to an XDMCP enabled X server using the first 
suitable address in the XDMCP Request packet. However, some clients may put a 
number of addresses in this message and potentially they are not all routable. 
If the address the request message came from is in the list we should use that 
first as that is more likely to be a routable address. This also matches the 
behaviour of GDM which ignores the contents of the Request packet anyway.

  [Test Case]
  1. Start LightDM with XDMCP enabled
  2. Connect with a client that puts a number of addresses in the Request packet

  Expected result:
  LightDM prefers the address the Request came from over the other addresses.

  Observed result:
  LightDM always picks the first address.

  [Regression Potential]
  There is a possibility of a behaviour change in existing clients that had two 
valid addresses, though the particular address shouldn't matter (unless complex 
firewalling / routing rules are being used). There is a risk that XDMCP 
behaviour could have been broken by the change (tested with regression tests).

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

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

[Desktop-packages] [Bug 1493888] Update Released

[Timo Aaltonen]

The verification of the Stable Release Update for fglrx-installer-
updates has completed successfully and the package has now been released
to -updates.  Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  FGLRX incompatible with gcc 5

Status in fglrx:
  New
Status in Release Notes for Ubuntu:
  Fix Released
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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

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

[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device

[John Ritz]

I tried plugging in to two different USB ports, then repeatedly into
one. It finally took, so the problem is intermittent for me.

It turns out mtp-connect was hanging in a terminal window and I found a
lot of what might be useful debugging info when I went back to it (after
the successful mount):

mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

Listing raw device(s)
Device 0 (VID=1004 and PID=62ce) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
   Found 1 device(s):
   1004:62ce @ bus 2, dev 10
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
Error 7: Found a bad handle, trying to ignore it.
USB low-level info:
   bcdUSB: 512
   bDeviceClass: 0
   bDeviceSubClass: 0
   bDeviceProtocol: 0
   idVendor: 1004
   idProduct: 62ce
   IN endpoint maxpacket: 512 bytes
   OUT endpoint maxpacket: 512 bytes
   Raw device info:
  Bus location: 2
  Device number: 10
  Device entry info:
 Vendor: (null)
 Vendor id: 0x1004
 Product: (null)
 Vendor id: 0x62ce
 Device flags: 0x08008106
Configuration 0, interface 0, altsetting 0:
   Interface description contains the string "MTP"
   Device recognized as MTP, no further probing.
Device info:
   Manufacturer: LGE
   Model: VS990
   Device version: 1.0
   Serial number: VS9908c1542c8
   Vendor extension ID: 0x0006
   Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
   Detected object size: 64 bits
   Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
   1001: get device info
   1002: Open session
   1003: Close session
   1004: Get storage IDs
   1005: Get storage info
   1006: Get number of objects
   1007: Get object handles
   1008: Get object info
   1009: Get object
   100a: Get thumbnail
   100b: Delete object
   100c: Send object info
   100d: Send object
   1014: Get device property description
   1015: Get device property value
   1016: Set device property value
   1017: Reset device property value
   101b: Get partial object
   9801: Get object properties supported
   9802: Get object property description
   9803: Get object property value
   9804: Set object property value
   9805: Get object property list
   9810: Get object references
   9811: Set object references
   95c1: Get Partial Object (64bit Offset)
   95c2: Send Partial Object
   95c3: Truncate Object
   95c4: Begin Edit Object
   95c5: End Edit Object
Events supported:
   0x4002
   0x4003
   0x4004
   0xd402: Friendly Device Name
   0x5003: Image Size
   0x5001: Battery Level
Playable File (Object) Types and Object Properties Supported:
   3000: Undefined Type
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc04: Object Size UINT64 data type READ ONLY
  dc07: Object File Name STRING data type GET/SET
  dc09: Date Modified STRING data type DATETIME FORM READ ONLY
  dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
  dc44: Name STRING data type READ ONLY
  dce0: Display Name STRING data type READ ONLY
  dc08: Date Created STRING data type DATETIME FORM READ ONLY
   3001: Association/Directory
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc04: Object Size UINT64 data type READ ONLY
  dc07: Object File Name STRING data type GET/SET
  dc09: Date Modified STRING data type DATETIME FORM READ ONLY
  dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
  dc44: Name STRING data type READ ONLY
  dce0: Display Name STRING data type READ ONLY
  dc08: Date Created STRING data type DATETIME FORM READ ONLY
   3004: Text
  dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
  dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
  dc04: Object Size UINT64 data type READ ONLY
  dc07: Object File Name STRING data type GET/SET
  dc09: Date Modified STRING data type DATETIME FORM READ ONLY
  dc0b: Parent Object UINT32 data type ANY 

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Launchpad Bug Tracker]

This bug was fixed in the package fglrx-installer-updates -
2:15.201-0ubuntu2~15.10.2

---
fglrx-installer-updates (2:15.201-0ubuntu2~15.10.2) wily-proposed; 
urgency=medium

  * debian/rules:
- Blacklist the amdgpu driver, so that fglrx can be loaded
  on the systems where the GPU is supported by amdgpu (LP: #1510573).

fglrx-installer-updates (2:15.201-0ubuntu2~15.10.1) wily-proposed;
urgency=medium

  * debian/control.in,
debian/dkms.conf.in,
dkms/patches/force-gcc-to-4.9-instead-of-5.x.patch:
- Add a dependency on gcc-4.9, and force fglrx to use gcc-4.9.
  This prevents fglrx from dying on initialisation (LP: #1493888).
  Credit for finding out the actual problem and for suggesting a
  workaround goes to David Burrows.
  Note: this is only a workaround, and it will be dropped as soon
  as a proper fix from upstream is available.

 -- Alberto Milone   Wed, 28 Oct 2015
13:21:21 +0100

** Changed in: fglrx-installer-updates (Ubuntu Wily)
   Status: Fix Committed => 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/1493888

Title:
  FGLRX incompatible with gcc 5

Status in fglrx:
  New
Status in Release Notes for Ubuntu:
  Fix Released
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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

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

[Desktop-packages] [Bug 1493888] Re: FGLRX incompatible with gcc 5

[Launchpad Bug Tracker]

This bug was fixed in the package fglrx-installer -
2:15.201-0ubuntu2~15.10.2

---
fglrx-installer (2:15.201-0ubuntu2~15.10.2) wily-proposed; urgency=medium

  * debian/rules:
- Blacklist the amdgpu driver, so that fglrx can be loaded
  on the systems where the GPU is supported by amdgpu (LP: #1510573).

fglrx-installer (2:15.201-0ubuntu2~15.10.1) wily-proposed;
urgency=medium

  * debian/control.in,
debian/dkms.conf.in,
dkms/patches/force-gcc-to-4.9-instead-of-5.x.patch:
- Add a dependency on gcc-4.9, and force fglrx to use gcc-4.9.
  This prevents fglrx from dying on initialisation (LP: #1493888).
  Credit for finding out the actual problem and for suggesting a
  workaround goes to David Burrows.
  Note: this is only a workaround, and it will be dropped as soon
  as a proper fix from upstream is available.

 -- Alberto Milone   Wed, 28 Oct 2015
13:19:25 +0100

** Changed in: fglrx-installer (Ubuntu Wily)
   Status: Fix Committed => 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/1493888

Title:
  FGLRX incompatible with gcc 5

Status in fglrx:
  New
Status in Release Notes for Ubuntu:
  Fix Released
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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver is not compatible with gcc 5.x. This causes the
  kernel module to crash on initialisation. As a result, users will boot
  into a black screen, as X will fail (except on Intel+AMD hybrid
  systems, where intel is used).

  [Test Case]
  1. Either install (or upgrade to) Ubuntu 15.10 and fglrx
  2. Reboot
  3. Check the display, and the output of the "dmesg | grep fglrx" command (to 
see the actual crash)

  Expected results: the system should be able to start X correctly.

  Actual results:
  The kernel module fails and X doesn't start.

  [Regression Potential]
  Low. Forcing fglrx to use gcc 4.9 is only a temporary workaround, and will be 
replaced with the proper fix once AMD makes it available.


  __

  With a R9 280 and FGLRX on ubuntu 15.10 the graphics lock up. I am
  able to SSH into the machine. I booted the older kernel
  (4.1.0-3-generic) and it works with FGLRX. After purging FGLRX and
  using xserver-xorg-video-radeon I am able to get the graphics working,
  but even it has issues with my display port (The DVI ports are working
  correctly).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  Date: Wed Sep  9 09:29:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-01-07 (1705 days ago)
  InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to wily on 2015-08-18 (21 days ago)

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

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

[Desktop-packages] [Bug 1510573] Re: fglrx should blacklist amdgpu

[Launchpad Bug Tracker]

This bug was fixed in the package fglrx-installer -
2:15.201-0ubuntu2~15.10.2

---
fglrx-installer (2:15.201-0ubuntu2~15.10.2) wily-proposed; urgency=medium

  * debian/rules:
- Blacklist the amdgpu driver, so that fglrx can be loaded
  on the systems where the GPU is supported by amdgpu (LP: #1510573).

fglrx-installer (2:15.201-0ubuntu2~15.10.1) wily-proposed;
urgency=medium

  * debian/control.in,
debian/dkms.conf.in,
dkms/patches/force-gcc-to-4.9-instead-of-5.x.patch:
- Add a dependency on gcc-4.9, and force fglrx to use gcc-4.9.
  This prevents fglrx from dying on initialisation (LP: #1493888).
  Credit for finding out the actual problem and for suggesting a
  workaround goes to David Burrows.
  Note: this is only a workaround, and it will be dropped as soon
  as a proper fix from upstream is available.

 -- Alberto Milone   Wed, 28 Oct 2015
13:19:25 +0100

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

Title:
  fglrx should blacklist amdgpu

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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

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

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

[Desktop-packages] [Bug 1517509] [NEW] Remove amazon as a webapp, move to simple sensible browser call

[Bryan Quigley]

Public bug reported:

What advantages do we get from running Amazon as a webapp?

Instead provide a desktop icon with Exec=sensible-browser
https://www.amazon.com/

and we save significant space on the image by using the already existing
browser.

** Affects: webapps-applications (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Remove amazon as a webapp, move to simple sensible browser call

Status in webapps-applications package in Ubuntu:
  New

Bug description:
  What advantages do we get from running Amazon as a webapp?

  Instead provide a desktop icon with Exec=sensible-browser
  https://www.amazon.com/

  and we save significant space on the image by using the already
  existing browser.

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

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

[Desktop-packages] [Bug 1501588] Re: Wily's wpasupplicant frequently fails on WPA enterprise networks

[Adam]

Nevermind, I found the redhat bug with the RADIUS info.

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

Title:
  Wily's wpasupplicant frequently fails on WPA enterprise networks

Status in hostap:
  Unknown
Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  Ever since I upgraded from vivid to wily on my laptop, I'm running
  into problems when connecting to my home WPA2 enterprise network.

  Typically the first connection immediately after the driver is loaded
  works as expected, however any further reconnection and the occasional
  roaming between APs cause wpasupplicant to freeze entirely requiring
  me to kill it and most often also reload my wireless driver to get
  things working again.

  ## A failed (hanging) association looks like:
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): Activation: 
(wifi) connection 'stgraber.net-secure' has security, and secrets exist.  No 
new secrets needed.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'ssid' 
value 'stgraber.net-secure'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'scan_ssid' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'key_mgmt' value 'WPA-EAP'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 'eap' 
value 'TLS'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'fragment_size' value '1300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'ca_cert' value '/home/stgraber/data/certs/stgraber-radius/ca.crt'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key' value '/home/stgraber/data/certs/stgraber-radius/castiana.p12'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'private_key_passwd' value ''
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'identity' value 'castiana'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'bgscan' value 'simple:30:-65:300'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: added 
'proactive_key_caching' value '1'
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Connection 
disconnected (reason -3)
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associated -> disconnected
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Failed to 
GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not 
connected: disconnect.
  Sep 30 23:31:06 castiana NetworkManager[25815]:   Config: set interface 
ap_scan to 1
  Sep 30 23:31:06 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: disconnected -> scanning
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: SME: Trying to 
authenticate with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana kernel: [102903.079940] wlan0: authenticate with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.085128] wlan0: send auth to 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Trying to associate 
with 24:a4:3c:c8:69:03 (SSID='stgraber.net-secure' freq=2412 MHz)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: scanning -> authenticating
  Sep 30 23:31:07 castiana kernel: [102903.086942] wlan0: authenticated
  Sep 30 23:31:07 castiana kernel: [102903.090103] wlan0: associate with 
24:a4:3c:c8:69:03 (try 1/3)
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: authenticating -> associating
  Sep 30 23:31:07 castiana kernel: [102903.101962] wlan0: RX AssocResp from 
24:a4:3c:c8:69:03 (capab=0x411 status=0 aid=1)
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: Associated with 
24:a4:3c:c8:69:03
  Sep 30 23:31:07 castiana kernel: [102903.103701] wlan0: associated
  Sep 30 23:31:07 castiana NetworkManager[25815]:   (wlan0): supplicant 
interface state: associating -> associated
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-STARTED 
EAP authentication started
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: CTRL-EVENT-EAP-METHOD 
EAP vendor 0 method 13 (TLS) selected
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=2 
subject='/C=CA/ST=Quebec/L=Montreal/O=stgraber.net/OU=Internal 
Infrastructure/CN=stgraber.net Root CA/name=stgraber.net Infrastructure Root 
CA/emailAddress=stgra...@stgraber.org' 
hash=87b9750baadddac7f05164d7fde3a0eb3d3efe0c948b430a3ecd093c629956e9
  Sep 30 23:31:07 castiana wpa_supplicant[25653]: wlan0: 
CTRL-EVENT-EAP-PEER-CERT depth=1 

[Desktop-packages] [Bug 1487111] Re: camera app unresponsive if trusted prompt left for some time

[Florian Boucault]

** Changed in: camera-app
   Status: New => Confirmed

** Changed in: camera-app
   Importance: Undecided => Medium

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  camera app unresponsive if trusted prompt left for some time

Status in camera-app:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in camera-app package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  image95/arale (also on mako)
  i see this for both the audio trust prompt and the video trust prompt
  steps
  1. launch camera
  2. don't touch trust prompt - set phone down for 5 min
  3. after time, select "accept"
  (alternately - select accept on camera, hit record and wait for audio prompt, 
step2)

  expected - app continues
  result - app is frozen, shell is still responsive, camera service spinning 
50% cpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1487111/+subscriptions

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

[Desktop-packages] [Bug 1517542] [NEW] xdg-open doesn't allow more than 64 characters after the protocol:// part

[Stefan Freyr]

Public bug reported:

This may actually not be a bug I guess but I still think it's a bit
strange.

Our application is using quite a lot more than 64 characters there so
I'm wondering whether we're breaking some standard (I can't find
anything about what the length can be).

But at least our problem is that our application does not launch
properly which may be our own fault but in case it's not I wanted to
check whether this 64 character limitation is actually based on some
specification somewhere or whether this is  just a random decision and
if so, whether this length should perhaps be increased?

** Affects: xdg-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  xdg-open doesn't allow more than 64 characters after the protocol://
  part

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  This may actually not be a bug I guess but I still think it's a bit
  strange.

  Our application is using quite a lot more than 64 characters there so
  I'm wondering whether we're breaking some standard (I can't find
  anything about what the length can be).

  But at least our problem is that our application does not launch
  properly which may be our own fault but in case it's not I wanted to
  check whether this 64 character limitation is actually based on some
  specification somewhere or whether this is  just a random decision and
  if so, whether this length should perhaps be increased?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1517542/+subscriptions

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

[Desktop-packages] [Bug 1412916] Update Released

[Chris J Arges]

The verification of the Stable Release Update for poppler has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  * Many PDFs do not display correctly, including the boarding passes from a
major European airline.

  * Printing a boarding pass is a common simple task which users expect to
work, and therefore should be fixed in the stable release.

  * See upstream bug report for discussion about the mechanism of the
  fix.

  [Test Case]

  * Attempt to view the test case in the linked upstream bug using 'evince
attachment.pdf'.

  * Observe corrupted text displayed.

  [Regression Potential]

  * Theoretically, other PDFs which currently display correctly could be
  displayed incorrectly after this change, but is intended to emulate
  acroread, so this is unlikely.

  * Patch has been reviewed and committed upstream, so should be safe.

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

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

[Desktop-packages] [Bug 1412916] Re: evince: Bad PDF rendering: invalid font scale

[Launchpad Bug Tracker]

This bug was fixed in the package poppler - 0.24.5-2ubuntu4.3

---
poppler (0.24.5-2ubuntu4.3) trusty; urgency=medium

  * debian/patches/git_matrix_not_invertable.patch:
- cairo: don't render text when text matrix is not invertable
  (lp: #1412916)

 -- Sebastien Bacher   Tue, 13 Oct 2015 16:10:18
+0100

** Changed in: poppler (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  evince: Bad PDF rendering: invalid font scale

Status in Poppler:
  Fix Released
Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  * Many PDFs do not display correctly, including the boarding passes from a
major European airline.

  * Printing a boarding pass is a common simple task which users expect to
work, and therefore should be fixed in the stable release.

  * See upstream bug report for discussion about the mechanism of the
  fix.

  [Test Case]

  * Attempt to view the test case in the linked upstream bug using 'evince
attachment.pdf'.

  * Observe corrupted text displayed.

  [Regression Potential]

  * Theoretically, other PDFs which currently display correctly could be
  displayed incorrectly after this change, but is intended to emulate
  acroread, so this is unlikely.

  * Patch has been reviewed and committed upstream, so should be safe.

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

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

[Desktop-packages] [Bug 1441095] Re: novatel: improve probing for Dell branded modems

[Chris J Arges]

Hello Bin, or anyone else affected,

Accepted network-manager into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/0.9.8.8-0ubuntu7.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: network-manager (Ubuntu Trusty)
   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/1441095

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]

   * There is no gateway information in Network Manager. (See the picture in 
comment #74)
* Some ISPs like TW Mobile in Taiwan don't need the gateway to connect to 
Internet.
* Some ISPs like Chunghwa Telecom in Taiwan do need the gateway to connect 
to Internet.
* We need to see the gateway information in Network Manager to cover all 
ISPs.

  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

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

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

[Desktop-packages] [Bug 1510573] Re: fglrx should blacklist amdgpu

[Alberto Milone]

@Roger: that would be a problem with the restricted drivers manager. You
really need to remove the packages.

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

Title:
  fglrx should blacklist amdgpu

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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

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

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

[Desktop-packages] [Bug 1510573] Re: fglrx should blacklist amdgpu

[Launchpad Bug Tracker]

This bug was fixed in the package fglrx-installer-updates -
2:15.201-0ubuntu2~15.10.2

---
fglrx-installer-updates (2:15.201-0ubuntu2~15.10.2) wily-proposed; 
urgency=medium

  * debian/rules:
- Blacklist the amdgpu driver, so that fglrx can be loaded
  on the systems where the GPU is supported by amdgpu (LP: #1510573).

fglrx-installer-updates (2:15.201-0ubuntu2~15.10.1) wily-proposed;
urgency=medium

  * debian/control.in,
debian/dkms.conf.in,
dkms/patches/force-gcc-to-4.9-instead-of-5.x.patch:
- Add a dependency on gcc-4.9, and force fglrx to use gcc-4.9.
  This prevents fglrx from dying on initialisation (LP: #1493888).
  Credit for finding out the actual problem and for suggesting a
  workaround goes to David Burrows.
  Note: this is only a workaround, and it will be dropped as soon
  as a proper fix from upstream is available.

 -- Alberto Milone   Wed, 28 Oct 2015
13:21:21 +0100

** Changed in: fglrx-installer-updates (Ubuntu Wily)
   Status: Fix Committed => Fix Released

** Changed in: fglrx-installer (Ubuntu Wily)
   Status: Fix Committed => 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/1510573

Title:
  fglrx should blacklist amdgpu

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 Wily:
  Fix Released
Status in fglrx-installer-updates source package in Wily:
  Fix Released

Bug description:
  SRU Request:

  [Impact]

  The fglrx driver can't be loaded unless the amdgpu driver is
  blacklisted (as we already do with the radeon driver).

  [Test Case]
  1. Install fglrx on Ubuntu 15.10
  2. Reboot
  3. Check the output of the "lsmod | grep fglrx" command

  Expected results: the fglrx module should be loaded.

  Actual results:
  The kernel module can't be loaded because of the amdgpu driver.

  [Regression Potential]
  Low. We already blacklist the radeon driver; now that amdgpu is available in 
the kernel we should do the same.

  
  The fglrx packages should blacklist amdgpu so that the said driver does not 
prevent fglrx from loading.

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

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

[Desktop-packages] [Bug 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

[Chris J Arges]

Hello Kai-Heng, or anyone else affected,

Accepted fglrx-installer into trusty-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fglrx-
installer/2:15.200-0ubuntu0.6 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: fglrx-installer (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: New => Invalid

** Changed in: fglrx-installer-updates (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.

Status in fglrx-installer package in Ubuntu:
  Invalid
Status in fglrx-installer-updates package in Ubuntu:
  Invalid
Status in fglrx-installer source package in Trusty:
  Fix Committed
Status in fglrx-installer-updates source package in Trusty:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]

  Upgrading from the upstream fglrx driver packages to the packages in
  the Ubuntu repository fails because the /etc/ati directory is a real
  directory instead of being a link (which was common in the Ubuntu
  packages).

  [Test Case]
  1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages 
from the AMD installer 
  2. Upgrade the package to the current ubuntu release.
  3. Check the apt-get output 

  Expected results: the fglrx module should be updated correctly.

  Actual results:
  The update fails as described below.

  [Regression Potential]
  Low. The change only affects a migration from a specific release.

  
  __
  Note that the fglrx 14.502 package name is 
fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from 
Ubuntu repository.

  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for install-info (5.2.0.dfsg.1-2) ...
  Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
  Processing triggers for sgml-base (1.26+nmu4ubuntu1) ...
  Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ...

  (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
    gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.
  Processing triggers for doc-base (0.10.5) ...
  Processing 1 changed doc-base file...
  Errors were encountered while processing:
   /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb
  Log ended: 2015-10-22 05:31:11

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

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

[Desktop-packages] [Bug 1517538] [NEW] Crashes after exiting fullscreen

[Nikita Yerenkov-Scott]

Public bug reported:

I have noticed that recently upon going fullscreen in VLC on Ubuntu
GNOME 15.10 with GNOME 3.18 that on most occasions when I exit
fullscreen (even if I've only been in it for a few seconds) I get logged
out of my user session (my computer automatically puts me in TTY2 for
some reason at startup although there is another GUI session (not
console) in TTY7) and get taken to the user session at TTY7 where I am
met with the thing with the time on it that I have time slide up to log
in, though it is a metal colour (and not the one I set it to for
anything): Metal.png

But it is not even as though my user session has simply been somehow
moved there as that is actually a separate user session that asks me to
log in and not to unlock my old session. And when I then go to TTY2,
instead of finding my session, I find the console login screen of TTY2.
So now I am basically unable to use fullscreen in VLC (it doesn't appear
to happen when using anything else) because my session seems to get
destroyed every time.

And I am not sure if this is a bug with VLC or Xorg, so I thought I
should report it under both, I am also not sure if it would just happen
with VLC, but so far that has been the only fullscreen application to
have this happen at the same time as it running.

---

OS Information:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 15.10
Release:15.10
Codename:   wily
Flavour: GNOME
GNOME Version: 3.18

Package Information:

xorg:
  Installed: 1:7.7+7ubuntu4
  Candidate: 1:7.7+7ubuntu4
  Version table:
 *** 1:7.7+7ubuntu4 0
500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
100 /var/lib/dpkg/status

vlc:
  Installed: 2.2.1-3
  Candidate: 2.2.1-3
  Version table:
 *** 2.2.1-3 0
500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

** Attachment added: "Metal.png"
   https://bugs.launchpad.net/bugs/1517538/+attachment/4521458/+files/Metal.png

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

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

** No longer affects: xserver-xorg-driver-vesa

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

Title:
  Crashes after exiting fullscreen

Status in vlc package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  I have noticed that recently upon going fullscreen in VLC on Ubuntu
  GNOME 15.10 with GNOME 3.18 that on most occasions when I exit
  fullscreen (even if I've only been in it for a few seconds) I get
  logged out of my user session (my computer automatically puts me in
  TTY2 for some reason at startup although there is another GUI session
  (not console) in TTY7) and get taken to the user session at TTY7 where
  I am met with the thing with the time on it that I have time slide up
  to log in, though it is a metal colour (and not the one I set it to
  for anything): Metal.png

  But it is not even as though my user session has simply been somehow
  moved there as that is actually a separate user session that asks me
  to log in and not to unlock my old session. And when I then go to
  TTY2, instead of finding my session, I find the console login screen
  of TTY2. So now I am basically unable to use fullscreen in VLC (it
  doesn't appear to happen when using anything else) because my session
  seems to get destroyed every time.

  And I am not sure if this is a bug with VLC or Xorg, so I thought I
  should report it under both, I am also not sure if it would just
  happen with VLC, but so far that has been the only fullscreen
  application to have this happen at the same time as it running.

  ---

  OS Information:

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 15.10
  Release:15.10
  Codename:   wily
  Flavour: GNOME
  GNOME Version: 3.18

  Package Information:

  xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4
Version table:
   *** 1:7.7+7ubuntu4 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  vlc:
Installed: 2.2.1-3
Candidate: 2.2.1-3
Version table:
   *** 2.2.1-3 0
  500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Lorn Potter]

hmmm... I just noticed/remembered that upstream Qt networkmanager plugin
has been updated, which should perform a bit better as it has had some
refactoring/rewriting done. It is slightly more sane.

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Desktop-packages] [Bug 1517572] [NEW] Applications window randomly freezes

[pl7ofit]

Public bug reported:

Applications window randomly freezes (firefox, steam)not unfreezes, only
kill, freezes only the application window, and DE worked well without
freezes

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 18 19:31:08 2015
InstallationDate: Installed on 2015-11-17 (1 days ago)
InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd amd64 apport-bug freeze radeon trusty xubuntu

** Tags added: amd xubuntu

** Tags added: radeon

** Description changed:

  Applications window randomly freezes (firefox, steam)not unfreezes, only
- kill, freezes only the application window, and DE worked without freezes
+ kill, freezes only the application window, and DE worked well without
+ freezes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 18 19:31:08 2015
  InstallationDate: Installed on 2015-11-17 (1 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Applications window randomly freezes

Status in xorg package in Ubuntu:
  New

Bug description:
  Applications window randomly freezes (firefox, steam)not unfreezes,
  only kill, freezes only the application window, and DE worked well
  without freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 18 19:31:08 2015
  InstallationDate: Installed on 2015-11-17 (1 days ago)
  InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1514199] Re: GIMP's GEGL C2G operation hangs

[Esteve Boix]

Just as a final test, I've installed Ubuntu 15.10 clean, in a virtual
machine (KVM), and the problem also appears there.

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

Title:
  GIMP's GEGL C2G operation hangs

Status in gimp package in Ubuntu:
  New

Bug description:
  When I run GEGL's C2G  operator:

  - The operation hangs (it does not crash, it just hangs) more or less
  in the middle of the process.

  - The operator works in rectangles. Some of these rectangles are
  obviously darker than the rest of the image.

  - I takes way longer than before. Maybe the parameters have changed
  their meaning or the internals have changed, and the iterations and
  samples have to be lower. I don't know right now.

  I usually run at a radius of 1600, 40 samples, 20 iterations on 16MPix
  images (4928 x 3264).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gimp 2.8.14-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov  8 15:56:51 2015
  InstallationDate: Installed on 2014-12-22 (320 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1512414] Re: CVE-2015-7869

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

Title:
  CVE-2015-7869

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-304 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Precise:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-352 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Vivid:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Vivid:
  Fix Released
Status in nvidia-graphics-drivers-352 source package in Vivid:
  Fix Released
Status in nvidia-graphics-drivers-304 source package in Wily:
  Fix Released
Status in nvidia-graphics-drivers-340 source package in Wily:
  Fix Released
Status in nvidia-graphics-drivers-352 source package in Wily:
  Fix Released

Bug description:
  The issue is tracked as CVE-2015-7869, “Unsanitized User Mode Input”.
  Note that the security issue is not yet public and Nvidia plans to
  have public disclosure on 11/18/2015. This affects affects nvidia-304
  and later branches.

  The official releases from NVIDIA will be available on 11/16/15. I am
  going to take care of the packaging.

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

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

[Desktop-packages] [Bug 1517569] [NEW] after change my password using a character * i was unable to login in graphic mode, but in terminal it works ok, i change to a password without * and it works fi

[Tiago]

Public bug reported:

I'm using ubuntu 15.10 and recently change my password it works ok, but
after reboot my machine i can't login anymore using the graphic
interface, but when i enter the command line mode i can login normally.
I make sure that the problem was the password changed instaling ubuntu
in a virtual machine and trying the same thing, i realize that when i
use the * character in my password this error occurs. Once occurred the
first time i try to change the password and login again in graphic mode
but it doesn't work, only reinstalling the system.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.16.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Wed Nov 18 15:21:05 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-06 (12 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  after change my password using a character * i was unable to login in
  graphic mode, but in terminal it works ok, i change to a password
  without * and it works fine in all, graphic and terminal.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm using ubuntu 15.10 and recently change my password it works ok,
  but after reboot my machine i can't login anymore using the graphic
  interface, but when i enter the command line mode i can login
  normally. I make sure that the problem was the password changed
  instaling ubuntu in a virtual machine and trying the same thing, i
  realize that when i use the * character in my password this error
  occurs. Once occurred the first time i try to change the password and
  login again in graphic mode but it doesn't work, only reinstalling the
  system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Wed Nov 18 15:21:05 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-06 (12 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1445846] Re: nm-online returns too early

[Launchpad Bug Tracker]

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

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

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

Title:
  nm-online returns too early

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  I am setting up a totem system which mounts a remote file system at boot and 
starts an application from it.

  I found that randomly the boot fails because the mount fails due to
  "Network unreachable" errors.

  I made sure the mount unit waits for network-online.target to be
  rached, however I found that NetworkManager-wait-online.service
  returns well before the IP address has been obtained by DHCP.

  This is a cleaned up log extract:

  apr 19 02:22:13 terminale2 systemd[1]: Starting Network.
  apr 19 02:22:13 terminale2 NetworkManager[660]:  (eth2): carrier is OFF
  apr 19 02:22:13 terminale2 NetworkManager[660]:  (eth2): new Ethernet 
device (driver: 'r8169' ifindex: 2)
  apr 19 02:22:13 terminale2 NetworkManager[660]:  (eth2): exported as 
/org/freedesktop/NetworkManager/Devices/1
  apr 19 02:22:13 terminale2 NetworkManager[660]:  (eth2): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
  apr 19 02:22:13 terminale2 systemd[1]: Starting Network Manager Wait Online...
  apr 19 02:22:13 terminale2 NetworkManager[660]:  (eth2): preparing 
device
  apr 19 02:22:18 terminale2 NetworkManager[660]:  startup complete
  apr 19 02:22:18 terminale2 systemd[1]: Started Network Manager Wait Online.
  apr 19 02:22:18 terminale2 systemd[1]: Reached target Network is Online.
 
  apr 19 02:22:18 terminale2 systemd[1]: Starting Network is Online.
  apr 19 02:22:18 terminale2 systemd[1]: Mounting /nas...
  apr 19 02:22:18 terminale2 mount[810]: mount error(101): Network is 
unreachable

  Then after a while:

  apr 19 02:22:26 terminale2 NetworkManager[660]:  Activation
  (eth2) successful, device activated.

  Attached you find the whole journal.

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

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

[Desktop-packages] [Bug 1302416] Re: deja-dup monitor was taking 6GB of memory

[Scott]

Add another confirmed. Just fresh installed 15.10, was running very
snappy, soon as remote chrome desktop installed and rebooted, deja-dup-
monitor eats memory. I had 5gb being taken up and system lagging
hardcore, able to kill service running, system caught up and runs fine.
Really have to have remote desktop installed to use, so hope this is
figured out in a timely manor. Darn bugs! haha

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

Title:
  deja-dup monitor was taking 6GB of memory

Status in deja-dup package in Ubuntu:
  Confirmed
Status in deja-dup package in Debian:
  New

Bug description:
  Booted fresh, computer started to be slow and after a while i realized
  deja-dup monitor was taking 6GB of memory. Haven't tried rebooted
  again. Will do so in a moment.

  Sorry can't provide more info :/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 09:40:07 2014
  InstallationDate: Installed on 2011-11-21 (864 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=ca_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago)

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

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

[Desktop-packages] [Bug 1511841] Re: autologin fails for administrator user

[Steve Holmes]

The user's home directory was encrypted, so signing in without a
password is not valid.

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

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

Title:
  autologin fails for administrator user

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  I had two user accounts on the machine, an administrator and a normal user.
  I edited a conf file in /etc/lightdm to auto login the unprivileged user, 
which worked fine. I then deleted the unprivlieged user and changed the config 
file to autologin the remaining user. This does not work, a password prompt is 
always presented to this user.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic i686
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Oct 30 20:06:14 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-09-26 (33 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 
(20150422.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:905): WARNING **: [PIDs] Failed to execute command: 
upstart
   
   ** (lightdm-gtk-greeter:905): WARNING **: Failed to load user image: Failed 
to open file '/home/bouncysteve/.face': Permission denied
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1517599] [NEW] package emacs24-lucid 24.5+1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Troy Kinsella]

Public bug reported:

Installing emacs on a fresh install of Xubuntu 15.10 (not an upgrade)
results in this:

==
~> sudo apt-get install emacs
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  emacs24 emacs24-bin-common emacs24-common emacs24-common-non-dfsg
  imagemagick-common libfftw3-double3 liblockfile-bin liblockfile1 liblqr-1-0
  libm17n-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libotf0 m17n-db
Suggested packages:
  emacs24-el libfftw3-bin libfftw3-dev m17n-docs libmagickcore-6.q16-2-extra
The following NEW packages will be installed:
  emacs emacs24 emacs24-bin-common emacs24-common emacs24-common-non-dfsg
  imagemagick-common libfftw3-double3 liblockfile-bin liblockfile1 liblqr-1-0
  libm17n-0 libmagickcore-6.q16-2 libmagickwand-6.q16-2 libotf0 m17n-db
0 upgraded, 15 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/24.8 MB of archives.
After this operation, 108 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Selecting previously unselected package imagemagick-common.
(Reading database ... 202685 files and directories currently installed.)
Preparing to unpack .../imagemagick-common_8%3a6.8.9.9-5ubuntu2_all.deb ...
Unpacking imagemagick-common (8:6.8.9.9-5ubuntu2) ...
Selecting previously unselected package libfftw3-double3:amd64.
Preparing to unpack .../libfftw3-double3_3.3.4-2ubuntu1_amd64.deb ...
Unpacking libfftw3-double3:amd64 (3.3.4-2ubuntu1) ...
Selecting previously unselected package liblockfile-bin.
Preparing to unpack .../liblockfile-bin_1.09-6ubuntu1_amd64.deb ...
Unpacking liblockfile-bin (1.09-6ubuntu1) ...
Selecting previously unselected package liblockfile1:amd64.
Preparing to unpack .../liblockfile1_1.09-6ubuntu1_amd64.deb ...
Unpacking liblockfile1:amd64 (1.09-6ubuntu1) ...
Selecting previously unselected package liblqr-1-0:amd64.
Preparing to unpack .../liblqr-1-0_0.4.2-2_amd64.deb ...
Unpacking liblqr-1-0:amd64 (0.4.2-2) ...
Selecting previously unselected package libmagickcore-6.q16-2:amd64.
Preparing to unpack .../libmagickcore-6.q16-2_8%3a6.8.9.9-5ubuntu2_amd64.deb ...
Unpacking libmagickcore-6.q16-2:amd64 (8:6.8.9.9-5ubuntu2) ...
Selecting previously unselected package libmagickwand-6.q16-2:amd64.
Preparing to unpack .../libmagickwand-6.q16-2_8%3a6.8.9.9-5ubuntu2_amd64.deb ...
Unpacking libmagickwand-6.q16-2:amd64 (8:6.8.9.9-5ubuntu2) ...
Selecting previously unselected package libotf0:amd64.
Preparing to unpack .../libotf0_0.9.13-1ubuntu1_amd64.deb ...
Unpacking libotf0:amd64 (0.9.13-1ubuntu1) ...
Selecting previously unselected package emacs24-common-non-dfsg.
Preparing to unpack .../emacs24-common-non-dfsg_24.4+1-2_all.deb ...
Unpacking emacs24-common-non-dfsg (24.4+1-2) ...
Selecting previously unselected package emacs24-common.
Preparing to unpack .../emacs24-common_24.5+1-1ubuntu2_all.deb ...
Unpacking emacs24-common (24.5+1-1ubuntu2) ...
Selecting previously unselected package emacs24-bin-common.
Preparing to unpack .../emacs24-bin-common_24.5+1-1ubuntu2_amd64.deb ...
Unpacking emacs24-bin-common (24.5+1-1ubuntu2) ...
Selecting previously unselected package m17n-db.
Preparing to unpack .../m17n-db_1.6.5-1_all.deb ...
Unpacking m17n-db (1.6.5-1) ...
Selecting previously unselected package libm17n-0.
Preparing to unpack .../libm17n-0_1.6.4-3_amd64.deb ...
Unpacking libm17n-0 (1.6.4-3) ...
Selecting previously unselected package emacs24.
Preparing to unpack .../emacs24_24.5+1-1ubuntu2_amd64.deb ...
Unpacking emacs24 (24.5+1-1ubuntu2) ...
Selecting previously unselected package emacs.
Preparing to unpack .../archives/emacs_46.1_all.deb ...
Unpacking emacs (46.1) ...
Processing triggers for man-db (2.7.4-1) ...
Processing triggers for install-info (6.0.0.dfsg.1-3) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for mime-support (3.58ubuntu1) ...
Setting up imagemagick-common (8:6.8.9.9-5ubuntu2) ...
Setting up libfftw3-double3:amd64 (3.3.4-2ubuntu1) ...
Setting up liblockfile-bin (1.09-6ubuntu1) ...
Setting up liblockfile1:amd64 (1.09-6ubuntu1) ...
Setting up liblqr-1-0:amd64 (0.4.2-2) ...
Setting up libmagickcore-6.q16-2:amd64 (8:6.8.9.9-5ubuntu2) ...
Setting up libmagickwand-6.q16-2:amd64 (8:6.8.9.9-5ubuntu2) ...
Setting up libotf0:amd64 (0.9.13-1ubuntu1) ...
Setting up emacs24-common-non-dfsg (24.4+1-2) ...
Setting up emacs24-common (24.5+1-1ubuntu2) ...
Setting up emacs24-bin-common (24.5+1-1ubuntu2) ...
update-alternatives: using /usr/bin/ctags.emacs24 to provide /usr/bin/ctags 
(ctags) in auto mode
update-alternatives: using /usr/bin/ebrowse.emacs24 to provide /usr/bin/ebrowse 
(ebrowse) in auto mode
update-alternatives: using /usr/bin/emacsclient.emacs24 to provide 
/usr/bin/emacsclient (emacsclient) in auto mode
update-alternatives: using 

[Desktop-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Grzegorz Cieslewski]

I was wondering if this fix will also be applied to LTS Enablement
Stacks on Trusty?

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Desktop-packages] [Bug 1517383] Re: chromium browser cause heaps of apparmor warnings

[Robert Ancell]

That file is not provided by LightDM - do you know which package it is
from?

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

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

Title:
  chromium browser cause heaps of apparmor warnings

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I had recently reported that the chromium-browser cause lots of
  apparmor denial messages, thus filling the screen completely with
  those ubuntu-specific black warning message tiles.  See #1504049

  Some people then turned this into a guest session problem and fixed
  the guest session problem with

  /etc/apparmor.d/abstractions/lightdm_chromium-browser

  but this file is included only in lightdm-guest-session and thus
  effective in guest sessions only.

  usr.bin.chromium-browser instead reads abstractions/ubuntu-browsers.d
  /chromium-browser , which does not contain the bug fixes.

  
  So the people fixed a different problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 18 10:35:57 2015
  InstallationDate: Installed on 2015-09-03 (75 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1449282] Re: xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

[Robert Ancell]

14.04 LTS is currently running Xorg 1.15 so there should be no need to
bring this change back.

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

Title:
  xserver-allow-tcp=true feature doesn't work with Xorg version 1.17.0

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Vivid:
  Fix Committed
Status in lightdm source package in Wily:
  Fix Released

Bug description:
  [Impact]
  xserver-allow-tcp=true option no longer works with X.org 1.17.

  [Test Case]
  1. Edit /etc/lightdm/lightdm.conf and set [SeatDefaults] 
xserver-allow-tcp=true
  2. Start LightDM
  3. Attempt to connect to the X server using TCP

  Expected result:
  Able to connect

  Observed result:
  Unable to connect

  [Regression potential]
  Low. X.org changed their default behaviour from listen by default to listen 
if "-listen tcp" is passed as a command line flag. This is just the equivalent 
change in LightDM. Since this is a new flag to X.org if a user was to use 
another X server there is a risk it would not understand that flag. However it 
seems unlikely since X.org is the only actively developed X server.

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

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

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Updating the BIOS does not solve the problem. 
Output: of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V18.5
07/19/2014
Note that this is a regression when updating from utopic to wily.

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech 

[Desktop-packages] [Bug 1517587] [NEW] Nautilus File Chooser Doesn't Show User Dirs

[Christoph Michelbach]

Public bug reported:

# Symptoms:
In the pane on the left, there usually are "Places" items (Home, Desktop, 
Documents, Downloads, Music, Pictures, Videos, Trash) which are also shown in 
the file chooser. The problem is that items in the "Places" category can go 
missing in the file chooser.

# How to replicate the bug:
Open ~/.config/user-dirs.dirs and change some of the directories. Make sure 
these directories actually exist. Restart your machine. What you will find is 
that Nautilus will work just fine and use the new directories. But if you use 
the file chooser (just try saving this website by pressing ctrl + S in your web 
browser), everything in "Places" that isn't the default value any more, will 
not be displayed.

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

** Description changed:

- Symptoms: In the pane on the left, there usually are "Places",
+ *Symptoms*: In the pane on the left, there usually are "Places",
  "Devices", "Bookmarks", and "Network" items which are also shown in the
  file chooser. The problem is that items in the "Places" category can go
  missing in the file chooser.
  
- How to replicate the bug: Open ~/.config/user-dirs.dirs and change some
- of the directories. Make sure these directories actually exist. Restart
- your machine. What you will find is that Nautilus will work just fine
- and use the new directories. But if you use the file chooser, everything
- in "Places" that isn't the default value any more, will not be
- displayed.
+ # How to replicate the bug:
+ Open ~/.config/user-dirs.dirs and change some of the directories. Make sure 
these directories actually exist. Restart your machine. What you will find is 
that Nautilus will work just fine and use the new directories. But if you use 
the file chooser, everything in "Places" that isn't the default value any more, 
will not be displayed.

** Description changed:

- *Symptoms*: In the pane on the left, there usually are "Places",
- "Devices", "Bookmarks", and "Network" items which are also shown in the
- file chooser. The problem is that items in the "Places" category can go
- missing in the file chooser.
+ # Symptoms:
+ In the pane on the left, there usually are "Places", "Devices", "Bookmarks", 
and "Network" items which are also shown in the file chooser. The problem is 
that items in the "Places" category can go missing in the file chooser.
  
  # How to replicate the bug:
  Open ~/.config/user-dirs.dirs and change some of the directories. Make sure 
these directories actually exist. Restart your machine. What you will find is 
that Nautilus will work just fine and use the new directories. But if you use 
the file chooser, everything in "Places" that isn't the default value any more, 
will not be displayed.

** Description changed:

  # Symptoms:
  In the pane on the left, there usually are "Places", "Devices", "Bookmarks", 
and "Network" items which are also shown in the file chooser. The problem is 
that items in the "Places" category can go missing in the file chooser.
  
  # How to replicate the bug:
- Open ~/.config/user-dirs.dirs and change some of the directories. Make sure 
these directories actually exist. Restart your machine. What you will find is 
that Nautilus will work just fine and use the new directories. But if you use 
the file chooser, everything in "Places" that isn't the default value any more, 
will not be displayed.
+ Open ~/.config/user-dirs.dirs and change some of the directories. Make sure 
these directories actually exist. Restart your machine. What you will find is 
that Nautilus will work just fine and use the new directories. But if you use 
the file chooser (just try saving this website by pressing ctrl + S in your web 
browser), everything in "Places" that isn't the default value any more, will 
not be displayed.

** Description changed:

  # Symptoms:
- In the pane on the left, there usually are "Places", "Devices", "Bookmarks", 
and "Network" items which are also shown in the file chooser. The problem is 
that items in the "Places" category can go missing in the file chooser.
+ In the pane on the left, there usually are "Places" items (Home, Desktop, 
Documents, Downloads, Music, Pictures, Videos, Trash) which are also shown in 
the file chooser. The problem is that items in the "Places" category can go 
missing in the file chooser.
  
  # How to replicate the bug:
  Open ~/.config/user-dirs.dirs and change some of the directories. Make sure 
these directories actually exist. Restart your machine. What you will find is 
that Nautilus will work just fine and use the new directories. But if you use 
the file chooser (just try saving this website by pressing ctrl + S in your web 
browser), everything in "Places" that isn't the default value any more, will 
not be displayed.

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

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Lorn Potter]

Actually, the only time Qt's QNetworkManagerInterfaceAccessPoint does a
GetAll is in the QNetworkManagerInterfaceAccessPoint c'tor. But that is
in the upstream version.

And the current ubuntu version (at least the one I am seeing) does not
do GetAll at all.

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

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

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

[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Hein]

In can also coonfirm that disabling SNA seems to work so far. It was
very easy to let my system crash before. Just open Libreoffice a few
times and resize the windowsize by clicking on the title bar.

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

Title:
  Intel driver crashes on Ubuntu 15.10

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

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 

[Desktop-packages] [Bug 1514547] Re: Units conversion is not visible after gnome-calculator update

[Václav Pavlík]

Hi,
I upgraded to kernel 4.2 and suddenly the calculator is fixed.

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

Title:
  Units conversion is not visible after gnome-calculator update

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  Hi,
  the bug is exactly what it says in the title. After upgrading to the latest 
kernel the output of unit conversion in gnome-calculator is no longer visible. 
I am glad that the developers got rid of the annoying resizing of the 
calculator window while typing in, but it seems to cause this problem.

  Thanks for solving it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-calculator 1:3.10.3-0ubuntu0.1.1
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  9 19:21:59 2015
  ExecutablePath: /usr/bin/gnome-calculator
  InstallationDate: Installed on 2014-06-05 (522 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1490136] Re: periodically disappears wifi connection

[Launchpad Bug Tracker]

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

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

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

Title:
  periodically disappears wifi connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  approximately every 15-20 minutes lost wi-fi connection. only helps a system 
reboot.
  wi-fi adapter is RTL 8723 BE on laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Aug 29 18:18:20 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed
   nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:6501]
 Subsystem: CLEVO/KAPOK Computer Device [1558:6501]
  InstallationDate: Installed on 2015-08-27 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Notebook W65_67SJ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=5b7a8aa8-228b-4c25-b53e-aa0ff26ab497 ro quiet splash
  SourcePackage: compiz
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SJ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.06:bd08/25/2014:svnNotebook:pnW65_67SJ:pvrNotApplicable:rvnNotebook:rnW65_67SJ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SJ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Aug 29 18:15:42 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   intel(G1): [drm] failed to set drm interface version: Permission denied [13].
   intel(G1): Failed to claim DRM device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 851 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Desktop-packages] [Bug 1517615] [NEW] Need to disable "--enable-hardware-cursor=true" option in unity-system-compositor

[Christopher Townsend]

Public bug reported:

Recently, Unity 8 provides its own cursor, so we no longer need the
"--enable-hardware-cursor=true" option in unity-system-compositor.

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

** Affects: lightdm (Ubuntu Vivid)
 Importance: Undecided
 Status: New

** Summary changed:

- Need to disable "--enable-hardware-cursor=true" by default now
+ Need to disable "--enable-hardware-cursor=true" option in 
unity-system-compositor

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

Title:
  Need to disable "--enable-hardware-cursor=true" option in unity-
  system-compositor

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Vivid:
  New

Bug description:
  Recently, Unity 8 provides its own cursor, so we no longer need the
  "--enable-hardware-cursor=true" option in unity-system-compositor.

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

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

[Desktop-packages] [Bug 1517615] Re: Need to disable "--enable-hardware-cursor=true" option in unity-system-compositor

[Robert Ancell]

** Also affects: lightdm (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

Title:
  Need to disable "--enable-hardware-cursor=true" option in unity-
  system-compositor

Status in lightdm package in Ubuntu:
  New
Status in lightdm source package in Vivid:
  New

Bug description:
  Recently, Unity 8 provides its own cursor, so we no longer need the
  "--enable-hardware-cursor=true" option in unity-system-compositor.

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

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

[Desktop-packages] [Bug 1490136] Re: periodically disappears wifi connection

[xkill]

Same issue here with buntu 15.10 (Wily Werewolf) and all updates
installed.

All workaround known to me (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070) don't work
any more on my machine.

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

Title:
  periodically disappears wifi connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  approximately every 15-20 minutes lost wi-fi connection. only helps a system 
reboot.
  wi-fi adapter is RTL 8723 BE on laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Aug 29 18:18:20 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed
   nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:6501]
 Subsystem: CLEVO/KAPOK Computer Device [1558:6501]
  InstallationDate: Installed on 2015-08-27 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Notebook W65_67SJ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=5b7a8aa8-228b-4c25-b53e-aa0ff26ab497 ro quiet splash
  SourcePackage: compiz
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SJ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.06:bd08/25/2014:svnNotebook:pnW65_67SJ:pvrNotApplicable:rvnNotebook:rnW65_67SJ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SJ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Aug 29 18:15:42 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   intel(G1): [drm] failed to set drm interface version: Permission denied [13].
   intel(G1): Failed to claim DRM device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 851 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Desktop-packages] [Bug 1490136] Re: periodically disappears wifi connection

[xkill]

07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
Subsystem: Acer Incorporated [ALI] Device b734
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
Kernel driver in use: rtl8723be

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

Title:
  periodically disappears wifi connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  approximately every 15-20 minutes lost wi-fi connection. only helps a system 
reboot.
  wi-fi adapter is RTL 8723 BE on laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: compiz-core 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.59  Tue Mar 31 14:10:31 
PDT 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Aug 29 18:18:20 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-26-generic, x86_64: installed
   nvidia-346, 346.59, 3.19.0-26-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:6501]
 Subsystem: CLEVO/KAPOK Computer Device [1558:6501]
  InstallationDate: Installed on 2015-08-27 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Notebook W65_67SJ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=5b7a8aa8-228b-4c25-b53e-aa0ff26ab497 ro quiet splash
  SourcePackage: compiz
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SJ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.06:bd08/25/2014:svnNotebook:pnW65_67SJ:pvrNotApplicable:rvnNotebook:rnW65_67SJ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SJ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Aug 29 18:15:42 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   intel(G1): [drm] failed to set drm interface version: Permission denied [13].
   intel(G1): Failed to claim DRM device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 851 
   vendor LGD
  xserver.version: 2:1.17.1-0ubuntu3

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

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

[Desktop-packages] [Bug 1515718] Re: Xorg crash

[praepoke]

Hello Christopher,

Thanks for the reply. Unfortunately, i'm not at liberty to update my BIOS :(
On the other hand, doing the workaround found here seems to have solve my issue:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970/comments/40

/usr/share/X11/xorg.conf.d$ cat 20-intel.conf

Section "Device"
 Identifier "Card0"
 Driver "Intel"
 Option "AccelMethod" "uxa"
EndSection

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashes randomly since 15.10 upgrade

  ---
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda1: clean, 1435509/9519104 files, 28231394/38046976 blocks
   [* ] (1 of 5) A start job is running for Wait for all 
"auto" /etc/network/interfaces to be up for network-online.target (59s / 2min 
9s)
  [  OK  ] Started Detect the available GPUs and deal with any 
system changes.
    Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2015-11-06 17:57:17,396 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 3.19.0-26-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:05a4]
  MachineType: Dell Inc. OptiPlex 9020
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=6de2e5bd-6327-4991-9810-c6a0f06c2b2e ro splash quiet 
intel_pstate=enable vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Tags:  wily ubuntu
  Uname: Linux 4.2.0-18-generic x86_64
  UpgradeStatus: Upgraded to wily on 2015-11-06 (10 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0PC5F7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd08/15/2013:svnDellInc.:pnOptiPlex9020:pvr01:rvnDellInc.:rn0PC5F7:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 9020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Nov 17 09:42:24 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputDell Dell QuietKey Keyboard KEYBOARD, id 9
   inputUSB Optical MouseMOUSE, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Launchpad Bug Tracker]

This bug was fixed in the package unity-settings-daemon -
15.04.1+16.04.20151118.1-0ubuntu1

---
unity-settings-daemon (15.04.1+16.04.20151118.1-0ubuntu1) xenial; urgency=medium

  [ Shih-Yuan Lee (FourDollars) ]
  * power: On raw backlight types, clamp the value to a minumum (LP:
#1381625) gsd-rr: Apply the similar method from power plugin to fix
the lowest brightness issue. (LP: #1381625) (LP: #1381625)

 -- Shih-Yuan Lee   Wed, 18 Nov 2015
09:36:58 +

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Desktop-packages] [Bug 828316] Re: [GTK3] Navigation bar menubuttons don't look pressed when clicked

[Rahul]

** Attachment added: "possible solution.txt"
   
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/828316/+attachment/4521232/+files/possible%20solution.txt

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

Title:
  [GTK3] Navigation bar menubuttons don't look pressed when clicked

Status in software-center package in Ubuntu:
  Triaged

Bug description:
  software-center-gtk3 trunk 2114, Ubuntu Ocelot

  1. Click the menubuttons next to "All Software" or "Installed".

  What happens:
  * The triangle changes color a little.
  * The triangle sometimes wobbles.

  What should happen:
  * The whole menubutton goes dark, just like the button for the current 
section.
  * The triangle does not change color, except in the same way as the whole 
menubutton does.
  * The triangle doesn't wobble.

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

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

[Desktop-packages] [Bug 1501300] Re: Wily (15.10) this package got not compiled with __cxx11 support

[Matthias Goldhoorn]

How can this patch (or the backport) apply for a SRU update, how it is
possible to add a SRU maintainer to this thread?

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

Title:
  Wily (15.10) this package got not compiled with __cxx11 support

Status in llvm-toolchain-3.4 package in Ubuntu:
  Fix Released

Bug description:
  This packages does not contain any __cxx11 symbols when installed. This 
causes the problem that user-space applications cannot link successfully to it.
  Recompile the (untouched) dpkg source package on the same machine and 
installing it solved the problem.

  There seems something in the package generation broken.

  Steps to reproduce try to compile the attached minimal example
  https://github.com/goldhoorn/clang-sandbox

  
  Errors:
  CMakeFiles/main.dir/main.cpp.o: In function `foo()':
  /tmp/clang-sandbox/main.cpp:25: undefined reference to 
`clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)':
  /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to 
`clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  CMakeFiles/main.dir/main.cpp.o: In function 
`clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl
 const&, clang::ast_matchers::internal::ASTMatchFinder*, 
clang::ast_matchers::internal::BoundNodesTreeBuilder*) const':
  /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined 
reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function 
`handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, 
llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)':
  (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, 
bool) const'
  /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous 
namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone 
.isra.302]':

  ...

  This example is workign on privious ubuntus and debians

  Sysinfo:
  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10
  In a VirtualBox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions

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

[Desktop-packages] [Bug 1390270] Re: Ubuntu 14.10 lockscreen requires password for passwordless accounts

[Rishabh Ksheerasagar]

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

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

Title:
  Ubuntu 14.10 lockscreen requires password for passwordless accounts

Status in gnome-screensaver package in Ubuntu:
  Fix Released

Bug description:
  Orignally running Ubuntu 14.04 and upgraded to 14.10.
  After Upgrade each time one of the "passwordless accounts" is logged in - 
once the lock screen for said account is displayed, either though manual lock 
or from timeout, it requires a password.  Pressing enter (I.E. input no 
password) results in "Incorrect Password" being displayed.

  There appears to be no way back into this account.

  Potential Package: gnome-screensaver
  gnome-screensaver:
Installed: 3.6.1-0ubuntu14
Candidate: 3.6.1-0ubuntu14
Version table:
   *** 3.6.1-0ubuntu14 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main i386 Packages
  100 /var/lib/dpkg/status

  
  lsbrelease output: Ubuntu 14.10 / 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-release-upgrader-core 1:14.10.9
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Nov  7 00:37:32 2014
  InstallationDate: Installed on 2014-10-21 (16 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (12 days ago)

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

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

[Desktop-packages] [Bug 1516062] LightdmGreeterLogOld.txt

[Olivier Febwin]

apport information

** Attachment added: "LightdmGreeterLogOld.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521280/+files/LightdmGreeterLogOld.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] LightdmGreeterLog.txt

[Olivier Febwin]

apport information

** Attachment added: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521279/+files/LightdmGreeterLog.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] BootLog.txt

[Olivier Febwin]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521272/+files/BootLog.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] Lspci.txt

[Olivier Febwin]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1516062/+attachment/4521282/+files/Lspci.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] XorgLog.txt

[Olivier Febwin]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521291/+files/XorgLog.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] ProcInterrupts.txt

[Olivier Febwin]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521287/+files/ProcInterrupts.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Olivier Febwin]

.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: 2015-10-22 21:56:09,943 DEBUG enabling apt cron job
DistroCodename: wily
DistroRelease: Ubuntu 15.10
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.19.0-31-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-16-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 4.2.0-18-generic, x86_64: installed
 vboxhost, 5.0.8, 4.2.0-16-generic, x86_64: installed
 vboxhost, 5.0.8, 4.2.0-18-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0494]
InstallationDate: Installed on 2015-09-21 (57 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Dell Inc. Latitude E6520
NonfreeKernelModules: wl
Package: xorg 1:7.7+7ubuntu4
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=c4bb2c60-a78a-47ad-95a0-8c6b60156660 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Tags:  wily ubuntu compiz-0.9
UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
Uname: Linux 4.2.0-18-generic x86_64
UpgradeStatus: Upgraded to wily on 2015-10-22 (26 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 06/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A18
dmi.board.name: 0NVF5K
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd06/28/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6520
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Nov 18 11:30:36 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   21576 
 vendor SEC
xserver.version: 2:1.17.2-1ubuntu9


** Tags added: apport-collected compiz-0.9 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/1516062

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] ProcEnviron.txt

[Olivier Febwin]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521286/+files/ProcEnviron.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] xdpyinfo.txt

[Olivier Febwin]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521294/+files/xdpyinfo.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] GconfCompiz.txt

[Olivier Febwin]

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521276/+files/GconfCompiz.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] ProcCpuinfo.txt

[Olivier Febwin]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521285/+files/ProcCpuinfo.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] LightdmLog.txt

[Olivier Febwin]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521281/+files/LightdmLog.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] Dependencies.txt

[Olivier Febwin]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521274/+files/Dependencies.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] ProcModules.txt

[Olivier Febwin]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521288/+files/ProcModules.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] UdevDb.txt

[Olivier Febwin]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1516062/+attachment/4521289/+files/UdevDb.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] UnitySupportTest.txt

[Olivier Febwin]

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521290/+files/UnitySupportTest.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] LightdmDisplayLog.txt

[Olivier Febwin]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521278/+files/LightdmDisplayLog.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] Lsusb.txt

[Olivier Febwin]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1516062/+attachment/4521283/+files/Lsusb.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1517465] [NEW] Resolution too low on external monitor through Intel graphics, reversion in 4.x kernel

[Thomas Hinkle]

Public bug reported:

I have the incorrect resolution on my external monitor since upgrading
to 15.10 with the 4.x kernel.

Playing with xmode lines manually via xrandr has failed -- when I create
a correct 1920x1080 modeline and force it, it is unable to display.

Booting with the 3.19.0-26 kernel fixes the issue.

The Machine in question is a Dell XPS 12. Video card: Intel 3rd Gen
graphics controller.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Nov 18 07:58:53 2015
DistUpgraded: 2015-11-06 06:09:04,179 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0589]
InstallationDate: Installed on 2014-11-08 (375 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
MachineType: Dell Inc. XPS 12 9Q23
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=31556373-7ffa-4f76-a0f4-0a770bb0f04f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to wily on 2015-11-06 (12 days ago)
dmi.bios.date: 08/01/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0520M8
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/01/2013:svnDellInc.:pnXPS129Q23:pvrA08:rvnDellInc.:rn0520M8:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.name: XPS 12 9Q23
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Nov 18 07:57:09 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 957
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug resolution ubuntu wily

** Description changed:

  I have the incorrect resolution on my external monitor since upgrading
  to 15.10 with the 4.x kernel.
  
  Playing with xmode lines manually via xrandr has failed -- when I create
  a correct 1920x1080 modeline and force it, it is unable to display.
  
  Booting with the 3.19.0-26 kernel fixes the issue.
  
- The Machine in question is a Dell XPS 13. Video card: Intel 3rd Gen
+ The Machine in question is a Dell XPS 12. Video card: Intel 3rd Gen
  graphics controller.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Nov 18 07:58:53 2015
  DistUpgraded: 2015-11-06 06:09:04,179 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:0589]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Dell Device [1028:0589]
  InstallationDate: Installed on 2014-11-08 (375 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: Dell Inc. XPS 12 9Q23
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  

[Desktop-packages] [Bug 1512435] Re: Stop depending on gnome-control-center

[Sebastien Bacher]

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Stop depending on gnome-control-center

Status in gnome-control-center package in Ubuntu:
  Fix Committed
Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  Currently u-c-c depends on g-c-c-shared-data that prevents that one to be 
moved to universe. The shared data include 2 things
  - some image to be used for user accounts
  - some polkit rules

  the image are small, we could copy them in u-c-c, the polkit rules
  could be included in the desktop profile instead

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

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

[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C

[en23]

SImon N.
How do I write the hex value with xdd?

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

Title:
  Keyboard backlight does not work in Samsung Series 9 NP900X4C

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 13.04, the keyboard backlight does not work in Samsung
  Series 9 NP900X4C.

  Adding the FN key mappings as described in
  https://help.ubuntu.com/community/SamsungSeries9 does show information
  in the notification area when pressing the keyboard backlight's + and
  - buttons, but:

  1) The notification always identifies the backlight as "full max"
  2) It has no effect on the backlight - it's always off

  When I first installed Ubuntu on this machine (12.10), even though the
  fn keys never worked I did have intermitent backlight functionality -
  the light sensor would sometimes work and I'd see light in the
  keyboard.

  I dual boot in Windows 8 and backlighting works there, so this is not
  a hardware issue.

  More discussion can be found here:
  http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-
  fn-buttons-work-in-samsung-series-9

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

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

[Desktop-packages] [Bug 1516263] Re: Texts are not rendering properly in 15.10 which causes xorg to restart

[Christopher M. Penalver]

Pavak Paul, when xorg restarts, are there files in /var/crash ?

** Tags added: xenial

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

Title:
  Texts are not rendering properly in 15.10 which causes xorg to restart

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When I ran Ubuntu 15.10 from Live session I found some letters are not
  showing at all, some very white or bold. Sometimes hovering on them
  shows the original text, sometimes blinking. This often restarts xorg.

  WORKAROUND: Install the nvidia proprietary drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Nov 14 16:16:18 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:84ad]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  Renderer: Software
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Nov 14 20:58:08 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Tejal]

** Changed in: unity-settings-daemon (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: unity-settings-daemon (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

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

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

[Desktop-packages] [Bug 1453298]

[Carl-wolfgang]

On a zotac ci320 nano with ubuntu trusty server 14.04.3 LTS and kernel 
from openelec forum 3.19.1-legacy-turbo+ with yavdr
unstable installed and va-api-glx in softhddevice vdr plugin a kernel oops
left the following trace, maybe usefull because freezes normally don't leave
a trace in the logs,..

Nov 17 22:12:55 nano4 kernel: [ 4740.991238] [ cut here 
]
Nov 17 22:12:55 nano4 kernel: [ 4740.991365] WARNING: CPU: 3 PID: 134 at 
drivers/gpu/drm/i915/intel_pm.c:4492 valleyview_set_rps+0x167/0x1a0 [i915]()
Nov 17 22:12:55 nano4 kernel: [ 4740.991375] WARN_ON(val > 
dev_priv->rps.max_freq_softlimit)
Nov 17 22:12:55 nano4 kernel: [ 4740.991383] Modules linked in: msr(E) 
autofs4(E) rc_tt_1500(OE) ts2020(OE) m88ds3103(OE) i2c_mux(E) arc4(E) 
intel_rapl(E) intel_powerclamp(E) snd_hda_codec_hdmi(E) 
snd_hda_codec_realtek(E) snd_hda_codec_generic(E) kvm(E) crct10dif_pclmul(E) 
crc32_pclmul(E) dvb_usb_dw2102(OE) dvb_usb(OE) ghash_clmulni_intel(E) iwlmvm(E) 
cryptd(E) dvb_core(OE) snd_soc_rt5640(E) mac80211(E) media(OE) snd_hda_intel(E) 
snd_soc_rl6231(E) snd_hda_controller(E) snd_intel_sst_acpi(E) 
snd_intel_sst_core(E) snd_soc_sst_mfld_platform(E) snd_hda_codec(E) 
snd_soc_core(E) serio_raw(E) snd_compress(E) iwlwifi(E) btusb(E) 
snd_pcm_dmaengine(E) snd_hwdep(E) cfg80211(E) snd_pcm(E) snd_seq_midi(E) 
snd_seq_midi_event(E) ir_lirc_codec(OE) ir_xmp_decoder(OE) lirc_dev(OE) 
ir_mce_kbd_decoder(OE) mei_txe(E) iosf_mbi(E) ir_sharp_decoder(OE) mei(E) 
lpc_ich(E) shpchp(E) ir_sanyo_decoder(OE) snd_rawmidi(E) ir_sony_decoder(OE) 
ir_jvc_decoder(OE) ir_rc6_decoder(OE) ir_rc5_decoder(OE) snd_seq(E) ir_ne
 c_decoder(OE) snd_seq_device(E) snd_timer(E) rc_rc6_mce(OE) nuvoton_cir(OE) 
rc_core(OE) 8250_fintek(E) snd(E) rfcomm(E) bnep(E) dw_dmac(E) dw_dmac_core(E) 
i2c_hid(E) hid(E) rfkill_gpio(E) soundcore(E) bluetooth(E) snd_soc_sst_acpi(E) 
8250_dw(E) spi_pxa2xx_platform(E) i2c_designware_platform(E) 
i2c_designware_core(E) pwm_lpss_platform(E) mac_hid(E) pwm_lpss(E) i915(E) 
video(E) drm_kms_helper(E) nfsd(E) drm(E) auth_rpcgss(E) nfs_acl(E) 
i2c_algo_bit(E) nfs(E) lockd(E) grace(E) sunrpc(E) fscache(E) nct6775(E) 
hwmon_vid(E) coretemp(E) lp(E) parport(E) nls_iso8859_1(E) psmouse(E) r8169(E) 
mii(E) ahci(E) libahci(E) sdhci_acpi(E) sdhci(E)
Nov 17 22:12:55 nano4 kernel: [ 4740.991767] CPU: 3 PID: 134 Comm: kworker/3:2 
Tainted: G   OE  3.19.1-legacy-turbo+ #1
Nov 17 22:12:55 nano4 kernel: [ 4740.991778] Hardware name: Motherboard by 
ZOTAC ZBOX-CI320NANO series/ZBOX-CI320NANO series, BIOS B219P026 05/19/2015
Nov 17 22:12:55 nano4 kernel: [ 4740.991859] Workqueue: events 
intel_gen6_powersave_work [i915]
Nov 17 22:12:55 nano4 kernel: [ 4740.991871]  c06cb3c8 88003655fcc8 
8179acb0 
Nov 17 22:12:55 nano4 kernel: [ 4740.991890]  88003655fd18 88003655fd08 
81073a7a 88003655fcf8
Nov 17 22:12:55 nano4 kernel: [ 4740.991908]  88007855 00d6 
00d6 880077acd000
Nov 17 22:12:55 nano4 kernel: [ 4740.991927] Call Trace:
Nov 17 22:12:55 nano4 kernel: [ 4740.991968]  [] 
dump_stack+0x45/0x57
Nov 17 22:12:55 nano4 kernel: [ 4740.991993]  [] 
warn_slowpath_common+0x8a/0xc0
Nov 17 22:12:55 nano4 kernel: [ 4740.992013]  [] 
warn_slowpath_fmt+0x46/0x50
Nov 17 22:12:55 nano4 kernel: [ 4740.992111]  [] 
valleyview_set_rps+0x167/0x1a0 [i915]
Nov 17 22:12:55 nano4 kernel: [ 4740.992202]  [] 
intel_gen6_powersave_work+0xb2f/0x11b0 [i915]
Nov 17 22:12:55 nano4 kernel: [ 4740.992223]  [] 
process_one_work+0x14f/0x400
Nov 17 22:12:55 nano4 kernel: [ 4740.992241]  [] 
worker_thread+0x118/0x510
Nov 17 22:12:55 nano4 kernel: [ 4740.992259]  [] ? 
rescuer_thread+0x3d0/0x3d0
Nov 17 22:12:55 nano4 kernel: [ 4740.992278]  [] 
kthread+0xd2/0xf0
Nov 17 22:12:55 nano4 kernel: [ 4740.992298]  [] ? 
kthread_create_on_node+0x180/0x180
Nov 17 22:12:55 nano4 kernel: [ 4740.992319]  [] 
ret_from_fork+0x7c/0xb0
Nov 17 22:12:55 nano4 kernel: [ 4740.992339]  [] ? 
kthread_create_on_node+0x180/0x180
Nov 17 22:12:55 nano4 kernel: [ 4740.992352] ---[ end trace 6a13023d6ab83790 
]---

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

Title:
  8086:0f31 Xubuntu freeze once a day

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

Bug description:
  Xubuntu Vivid crashes once a day with Intel Celeron J1900 / HD
  Graphics, mainly when watching videos and more rarely during routine
  tasks like surfing on firefox or during a skype call

  - 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor
  Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)

  I think it may be related with this bug 
https://bugs.freedesktop.org/show_bug.cgi?id=88012 (found via 
https://bbs.archlinux.org/viewtopic.php?id=195736 i have the same config but 
another 

[Desktop-packages] [Bug 1517452] Re: Systemd + NerworkManager since 15.10 break VPN Support

[Martin]

Maybe good to know: 
In 15.04 and before this worked as expected. Since then no changes where made 
to the configuration, client and server.

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

Title:
  Systemd + NerworkManager since 15.10 break VPN Support

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  Package Version:
  apt-cache policy network-manager
  network-manager:
Installiert:   1.0.4-0ubuntu5.1
Installationskandidat: 1.0.4-0ubuntu5.1

  apt-cache policy  systemd
  systemd:
Installiert:   225-1ubuntu9
Installationskandidat: 225-1ubuntu9

  What you expected to happen:

  If I start a VPN-Client like Junipers NetworkConnect or openconnect, I
  expect a VPN-tunnel with a tun-device and the corresponding routes via
  this device.

  What happened instead:

  After a successful connection to the vpn gateway the VPN-Client gets informed 
about routes it should create on the client from the VPN gateway and performs 
the routing change. Systemd then seems to notify NetworkManager (NM) about the 
new interface (in my case tun0).   NM now does its magic to the newly created 
tun0 which is not configuered in NetworkManager.conf. After this only the host 
route to the tun0 device is left.
  There also seems to be a timing issue. About every 10th time NM is faster 
then i.e. the vpnc-scripts and routing is set up properly.

  It is possible to tell NM in /etc/NetworkManager/NetworkManager.conf to 
ignore tun0 via this:
  [keyfile]
  unmanaged-devices=interface-name:tun0

  Then however it is unclear to me how a VPN-Configuration with NM would work 
if tun0 is ignored. 
  In my case users have the opportunity to use Junipers NC which is not 
supported by NM so a standalone client has to be used, but also could want use 
openvpn via NM. As for now I assume both is not possible.

  1: I think it is necessary to be able to use both ways.
  2: It took me quite a while to find out why there where no proper routes. It 
is essential to tell people how to work around this.
  3: systemd-netword is _not_ running on these machines. I would like to 
understand why NM behaves like this. 
  4: For testing I used wicd to see if there is a difference. And it is. wicd 
does not mess with the vpn routes.

  Let me know if you need more information.

  
  NetworkManager.conf:

  [main]
  plugins=ifupdown,keyfile

  [ifupdown]
  managed=false
  #dns=dnsmasq

  [keyfile]
  unmanaged-devices=interface-name:tun0

  journal: journalctl -u NetworkManager

  NetworkManager[859]:   (tun0): new Tun device (carrier: OFF, driver: 
'tun', ifindex: 6)
  NetworkManager[859]:   devices added (path: 
/sys/devices/virtual/net/tun0, iface: tun0)
  NetworkManager[859]:   device added (path: 
/sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found.
  NetworkManager[859]:   (tun0): link connected
  NetworkManager[859]:   keyfile: add connection in-memory 
(968e1d17-6272-4a1d-9cfa-d2db26ef9607,"tun0")
  NetworkManager[859]:   (tun0): device state change: unmanaged -> 
unavailable (reason 'connection-assumed') [10 20 41]
  NetworkManager[859]:   (tun0): device state change: unavailable -> 
disconnected (reason 'connection-assumed') [20 30 41]
  NetworkManager[859]:   Device 'tun0' has no connection; scheduling 
activate_check in 0 seconds. 
  NetworkManager[859]:   (tun0): Activation: starting connection 'tun0' 
(968e1d17-6272-4a1d-9cfa-d2db26ef9607)
  NetworkManager[859]:   (tun0): device state change: disconnected -> 
prepare (reason 'none') [30 40 0]
  NetworkManager[859]:   (tun0): device state change: prepare -> config 
(reason 'none') [40 50 0]
  NetworkManager[859]:   (tun0): device state change: config -> ip-config 
(reason 'none') [50 70 0]
  NetworkManager[859]:   (tun0): device state change: ip-config -> 
ip-check (reason 'none') [70 80 0]
  NetworkManager[859]:   (tun0): device state change: ip-check -> 
secondaries (reason 'none') [80 90 0]
  NetworkManager[859]:   (tun0): device state change: secondaries -> 
activated (reason 'none') [90 100 0]
  NetworkManager[859]:   (tun0): Activation: successful, device activated.

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

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

[Desktop-packages] [Bug 1517457] Re: Error when dejq dup restor on ubuntu 14.04 64 bit LTS

[Battant]

Here is my backup manifest file

** Attachment added: "duplicity-full.20150801T103537Z.manifest"
   
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1517457/+attachment/4521337/+files/duplicity-full.20150801T103537Z.manifest

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

Title:
  Error when dejq dup restor on ubuntu 14.04 64 bit LTS

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Hello,

  I have the same erreor that

  https://bugs.launchpad.net/ubuntu/+source/deja-
  dup/+bug/826389?comments=all

  Here is the error message

  Invalid data - SHA1 hash mismatch for file:
   duplicity-inc.20151102T142228Z.to.20151104T190657Z.vol2.difftar.gz
   Calculated hash: 11f5429eb27356317a42f9a54f0d8fc297f51634
   Manifest hash: f798cffd4f08027ed1772f63bbc29f5c88b43d0a

  My configuration

  Ubuntu 14.04 64 bit

  Could you help me please ?

  Best regards

  Battant

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

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

[Desktop-packages] [Bug 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Olivier Febwin]

ok, but I have the same bug "Logitech Wireless Mouse M560 buttons Back,
Forward, don't work on Ubuntu 15.10"

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1517457] [NEW] Error when dejq dup restor on ubuntu 14.04 64 bit LTS

[Battant]

Public bug reported:

Hello,

I have the same erreor that

https://bugs.launchpad.net/ubuntu/+source/deja-
dup/+bug/826389?comments=all

Here is the error message

Invalid data - SHA1 hash mismatch for file:
 duplicity-inc.20151102T142228Z.to.20151104T190657Z.vol2.difftar.gz
 Calculated hash: 11f5429eb27356317a42f9a54f0d8fc297f51634
 Manifest hash: f798cffd4f08027ed1772f63bbc29f5c88b43d0a

My configuration

Ubuntu 14.04 64 bit

Could you help me please ?

Best regards

Battant

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

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

Title:
  Error when dejq dup restor on ubuntu 14.04 64 bit LTS

Status in deja-dup package in Ubuntu:
  New

Bug description:
  Hello,

  I have the same erreor that

  https://bugs.launchpad.net/ubuntu/+source/deja-
  dup/+bug/826389?comments=all

  Here is the error message

  Invalid data - SHA1 hash mismatch for file:
   duplicity-inc.20151102T142228Z.to.20151104T190657Z.vol2.difftar.gz
   Calculated hash: 11f5429eb27356317a42f9a54f0d8fc297f51634
   Manifest hash: f798cffd4f08027ed1772f63bbc29f5c88b43d0a

  My configuration

  Ubuntu 14.04 64 bit

  Could you help me please ?

  Best regards

  Battant

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

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

[Desktop-packages] [Bug 1517414] [NEW] package chromium-browser 45.0.2454.101-0ubuntu0.14.04.1.1099 failed to install/upgrade: cannot copy extracted data for './usr/lib/chromium-browser/libs/libcc.so'

[Cesar Urdaneta]

Public bug reported:

Message appearing on startup

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: chromium-browser 45.0.2454.101-0ubuntu0.14.04.1.1099
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Tue Nov 17 22:11:06 2015
DuplicateSignature: 
package:chromium-browser:45.0.2454.101-0ubuntu0.14.04.1.1099:cannot copy 
extracted data for './usr/lib/chromium-browser/libs/libcc.so' to 
'/usr/lib/chromium-browser/libs/libcc.so.dpkg-new': unexpected end of file or 
stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/chromium-browser/libs/libcc.so' to 
'/usr/lib/chromium-browser/libs/libcc.so.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2015-11-03 (14 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: chromium-browser
Title: package chromium-browser 45.0.2454.101-0ubuntu0.14.04.1.1099 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/chromium-browser/libs/libcc.so' to 
'/usr/lib/chromium-browser/libs/libcc.so.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: No upgrade log present (probably fresh install)
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]

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


** Tags: amd64 apport-package need-duplicate-check third-party-packages trusty

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

Title:
  package chromium-browser 45.0.2454.101-0ubuntu0.14.04.1.1099 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/chromium-
  browser/libs/libcc.so' to '/usr/lib/chromium-browser/libs/libcc.so
  .dpkg-new': unexpected end of file or stream

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Message appearing on startup

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 45.0.2454.101-0ubuntu0.14.04.1.1099
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Tue Nov 17 22:11:06 2015
  DuplicateSignature: 
package:chromium-browser:45.0.2454.101-0ubuntu0.14.04.1.1099:cannot copy 
extracted data for './usr/lib/chromium-browser/libs/libcc.so' to 
'/usr/lib/chromium-browser/libs/libcc.so.dpkg-new': unexpected end of file or 
stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/chromium-browser/libs/libcc.so' to 
'/usr/lib/chromium-browser/libs/libcc.so.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2015-11-03 (14 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: chromium-browser
  Title: package chromium-browser 45.0.2454.101-0ubuntu0.14.04.1.1099 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/chromium-browser/libs/libcc.so' to 
'/usr/lib/chromium-browser/libs/libcc.so.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1499665] Re: [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

[Christopher M. Penalver]

Yung Shen, could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the upstream kernel, please comment on which kernel version 
specifically you tested. If this issue is fixed in the mainline kernel, please 
add the following tags by clicking on the yellow circle with a black pencil 
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this
report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags removed: bios-outdated-a03
** Tags added: latest-bios-a03

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

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

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

Title:
  [SynPS/2 Synaptics TouchPad] TouchPad not working after installtion

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  During installation touchpad works perfectly, but after trusty(3.19)
  installed, and restarted, touchpad unable to use anymore.

  Steps to reproduce:

  1. Boot system with 14.04.3 live usb
  2. Install the system

  Expected result:
  Touchpad works normally as in live environment 

  Actual results:
  Touchpad no response

  
  Additional Info.:
  $ xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB-PS/2 Optical Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ DLLC6D7:00 06CB:796Aid=12   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Sleep Buttonid=8[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=15   [slave  
keyboard (3)]

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Sep 25 17:48:59 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:06d7]
  InstallationDate: Installed on 2015-09-22 (2 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 5551
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=3bf855c2-39fe-4325-a1cc-960930d96a9e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Desktop-packages] [Bug 1453298]

[Cffwet]

I have system freezes on ASRock Q1900-ITX with a kernel 3.19.31-generic
on an Ubuntu distro. I upgraded to kernel 4.2.0-16-generic last month
and recently to 4.2.0-18-generic. The system freezes got worse (less
than 10 min watching videos).

I disabled hardware acceleration in all software with this option, like
in my browsers. Further I edited the file /etc/default/acpi-support: I
disabled suspend/hibernate handling in acpi-support by changing the line
"SUSPEND_METHODS="dbus-pm dbus-hal pm-utils" to "SUSPEND_METHODS="none".

I don't get any freezes anymore, now for 24h for both kernels
3.19.31-generic and 4.2.0-18-generic with a lot of video playing. I
didn't tested on kernel 4.2.0-16-generic.

I tested disabling hardware acceleration without changing the acpi-
support file. And I tested disabling suspend/hibernate handling with
hardware acceleration. In both cases I still got freezes but it seems
less frequent. I needed both options disabled to get rid of all the
freezes.

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

Title:
  8086:0f31 Xubuntu freeze once a day

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

Bug description:
  Xubuntu Vivid crashes once a day with Intel Celeron J1900 / HD
  Graphics, mainly when watching videos and more rarely during routine
  tasks like surfing on firefox or during a skype call

  - 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor
  Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)

  I think it may be related with this bug 
https://bugs.freedesktop.org/show_bug.cgi?id=88012 (found via 
https://bbs.archlinux.org/viewtopic.php?id=195736 i have the same config but 
another distro)
  I have tried to set "NoAccel" option to xorg conf file to true but same thing 
...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  9 00:11:14 2015
  InstallationDate: Installed on 2015-05-02 (6 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1530 F pulseaudio
   /dev/snd/controlC1:  steve  1530 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=fdcd8774-2dc2-4a6b-8fa8-9d3c6baa07a9
  InstallationDate: Installed on 2015-05-02 (7 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MEDION B269
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=c1ef472e-75c1-4e99-9d2d-d8c5bdc94414 ro noprompt quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid vivid
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 3.19.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BTLTW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: BTDD-LT
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBTLTW08.110:bd09/26/2014:svnMEDION:pnB269:pvr1.0:rvnMEDION:rnBTDD-LT:rvr1.0:cvnMEDION:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B269
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

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

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

[Desktop-packages] [Bug 1453298]

[SweX]

I've got freezes on baytrail tablet ASUS Vivotab note 8 (m80ta). But for
me it looks unrelated to i915. Even with nomodeset and rmmod i915 system
hang after some random time. From minutes to several hours.

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

Title:
  8086:0f31 Xubuntu freeze once a day

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

Bug description:
  Xubuntu Vivid crashes once a day with Intel Celeron J1900 / HD
  Graphics, mainly when watching videos and more rarely during routine
  tasks like surfing on firefox or during a skype call

  - 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor
  Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e)

  I think it may be related with this bug 
https://bugs.freedesktop.org/show_bug.cgi?id=88012 (found via 
https://bbs.archlinux.org/viewtopic.php?id=195736 i have the same config but 
another distro)
  I have tried to set "NoAccel" option to xorg conf file to true but same thing 
...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  9 00:11:14 2015
  InstallationDate: Installed on 2015-05-02 (6 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  1530 F pulseaudio
   /dev/snd/controlC1:  steve  1530 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=fdcd8774-2dc2-4a6b-8fa8-9d3c6baa07a9
  InstallationDate: Installed on 2015-05-02 (7 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: MEDION B269
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=c1ef472e-75c1-4e99-9d2d-d8c5bdc94414 ro noprompt quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-16-generic N/A
   linux-backports-modules-3.19.0-16-generic  N/A
   linux-firmware 1.143
  RfKill:
   
  Tags:  vivid vivid
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 3.19.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: BTLTW08.110
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: BTDD-LT
  dmi.board.vendor: MEDION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrBTLTW08.110:bd09/26/2014:svnMEDION:pnB269:pvr1.0:rvnMEDION:rnBTDD-LT:rvr1.0:cvnMEDION:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B269
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION

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

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

[Desktop-packages] [Bug 1080612] Re: Installing fglrx/fglrx-updates does nothing. radeon still in use.

[Otus]

I'm in the same situation, with Ubuntu 14.04.3 and fglrx-updates.

Tried the instructions in comment #18 but did not change anything. The
log file is attached. Also tried removing and reinstalling fglrx, to no
effect.

Problems seemingly started when I booted without the GPU (using Intel
iGPU) to test hardware and again with the GPU. Before that fglrx was
working fine.

** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1080612/+attachment/4521265/+files/gpu-manager.log

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

Title:
  Installing fglrx/fglrx-updates does nothing. radeon still in use.

Status in fglrx-installer package in Ubuntu:
  Incomplete

Bug description:
  Installing fglrx or fglrx-updates succeeds, but I'm still stuck with
  only the radeon Xorg driver loaded (and fully functional).

  Xorg.0.log shows that it can't load fglrx no matter what I do:
  [ 1.816] (==) Matched fglrx as autoconfigured driver 0
  [ 1.816] (==) Matched ati as autoconfigured driver 1
  [ 1.816] (==) Matched fglrx as autoconfigured driver 2
  [ 1.816] (==) Matched ati as autoconfigured driver 3
  [ 1.816] (==) Matched vesa as autoconfigured driver 4
  [ 1.816] (==) Matched modesetting as autoconfigured driver 5
  [ 1.816] (==) Matched fbdev as autoconfigured driver 6
  [ 1.816] (==) Assigned the driver to the xf86ConfigLayout
  [ 1.816] (II) LoadModule: "fglrx"
  [ 1.816] (WW) Warning, couldn't open module fglrx
  [ 1.816] (II) UnloadModule: "fglrx"
  [ 1.816] (II) Unloading fglrx
  [ 1.816] (EE) Failed to load module "fglrx" (module does not exist, 0)

  BOTH kernel modules are loaded:
  $ lsmod | grep fgl
  fglrx4715211  0 
  $ lsmod | grep radeon
  radeon895653  3 
  ttm83595  1 radeon
  drm_kms_helper 46784  1 radeon
  drm   275528  5 radeon,ttm,drm_kms_helper
  i2c_algo_bit   13413  1 radeon

  And yes, the package really is installed:
  ii  fglrx 2:9.000-0ubuntu3
   amd64Video driver for the AMD graphics accelerators
  ii  fglrx-amdcccle2:9.000-0ubuntu3
   amd64Catalyst Control Center for the AMD graphics 
accelerators

  But still, I find:
  $ glxinfo | grep OpenGL
  OpenGL vendor string: X.Org
  OpenGL renderer string: Gallium 0.4 on AMD CEDAR
  OpenGL version string: 2.1 Mesa 9.0
  OpenGL shading language version string: 1.30
  OpenGL extensions:

  Does this mean my Radeon HD 5450/6350 is no longer supported? If so,
  then why has there not been a single error or log message saying so?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fglrx 2:9.000-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  Date: Mon Nov 19 17:38:00 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 9.000, 3.5.0-18-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450/6350] 
[1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:2126]
  InstallationDate: Installed on 2012-11-08 (11 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Dell Inc. OptiPlex 990
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic 
root=UUID=675af377-5092-4ac9-b56c-a52bd326cc91 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0D6H9T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0D6H9T:rvrA00:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex 990
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Desktop-packages] [Bug 1516062] Xrandr.txt

[Olivier Febwin]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1516062/+attachment/4521293/+files/Xrandr.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] xserver.devices.txt

[Olivier Febwin]

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521295/+files/xserver.devices.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] DpkgLog.txt

[Olivier Febwin]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521275/+files/DpkgLog.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] MonitorsUser.xml.txt

[Olivier Febwin]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521284/+files/MonitorsUser.xml.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] CurrentDmesg.txt

[Olivier Febwin]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521273/+files/CurrentDmesg.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1516062] XorgLogOld.txt

[Olivier Febwin]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521292/+files/XorgLogOld.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"

[Darren Davison]

>From my logs (summarized by logwatch)...

polkitd(authority=local): message repeated 473 times: [ Operator of
unix-session:c2 FAILED to authenticate to gain authorization for action
org.freedesktop.accounts.change-own-user-data for system-bus-name::1.48
[] (owned by unix-user:darren)]: 1 Time(s)

So that's 473 times the dialog appeared yesterday with no indication as
to why.  It's also affecting multiple users on my main 15.10 machine now
- in comment #5 I reported that it was only affecting a single user.
Still appears to be related to switching user sessions.

Is anyone looking into this?  Any further info/logs I can provide to
assist?

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

Title:
  Annoying dialog "Authentication is required to change your own user
  data"

Status in policykit-1-gnome package in Ubuntu:
  Confirmed

Bug description:
  Every few days a dialog pops up saying "Authentication is required to change 
your own user data" with an entry field for a password. If I type my user's 
password the dialog will reappear with an empty entry field. If I click on the 
cross to close the window many times it will be gone, but reappear a few days 
later. I don't know what this window is for and it makes no difference whether 
I close it or leave it. I don't use the gnome keyring.
  This started with Ubuntu 15.04 or maybe with an earlier release, and is still 
there in Ubuntu 15.10, also on machines I did a fresh install.

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

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

[Desktop-packages] [Bug 1516062] JournalErrors.txt

[Olivier Febwin]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1516062/+attachment/4521277/+files/JournalErrors.txt

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 828316] Re: [GTK3] Navigation bar menubuttons don't look pressed when clicked

[Ubuntu Foundations Team Bug Bot]

The attachment "possible solution.txt" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  [GTK3] Navigation bar menubuttons don't look pressed when clicked

Status in software-center package in Ubuntu:
  Triaged

Bug description:
  software-center-gtk3 trunk 2114, Ubuntu Ocelot

  1. Click the menubuttons next to "All Software" or "Installed".

  What happens:
  * The triangle changes color a little.
  * The triangle sometimes wobbles.

  What should happen:
  * The whole menubutton goes dark, just like the button for the current 
section.
  * The triangle does not change color, except in the same way as the whole 
menubutton does.
  * The triangle doesn't wobble.

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

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

[Desktop-packages] [Bug 1517452] [NEW] Systemd + NerworkManager since 15.10 break VPN Support

[Martin]

Public bug reported:

Release: lsb_release -rd
Description:Ubuntu 15.10
Release:15.10

Package Version:
apt-cache policy network-manager
network-manager:
  Installiert:   1.0.4-0ubuntu5.1
  Installationskandidat: 1.0.4-0ubuntu5.1
  
apt-cache policy  systemd
systemd:
  Installiert:   225-1ubuntu9
  Installationskandidat: 225-1ubuntu9

What you expected to happen:

If I start a VPN-Client like Junipers NetworkConnect or openconnect, I
expect a VPN-tunnel with a tun-device and the corresponding routes via
this device.

What happened instead:

After a successful connection to the vpn gateway the VPN-Client gets informed 
about routes it should create on the client from the VPN gateway and performs 
the routing change. Systemd then seems to notify NetworkManager (NM) about the 
new interface (in my case tun0).   NM now does its magic to the newly created 
tun0 which is not configuered in NetworkManager.conf. After this only the host 
route to the tun0 device is left.
There also seems to be a timing issue. About every 10th time NM is faster then 
i.e. the vpnc-scripts and routing is set up properly.

It is possible to tell NM in /etc/NetworkManager/NetworkManager.conf to ignore 
tun0 via this:
[keyfile]
unmanaged-devices=interface-name:tun0

Then however it is unclear to me how a VPN-Configuration with NM would work if 
tun0 is ignored. 
In my case users have the opportunity to use Junipers NC which is not supported 
by NM so a standalone client has to be used, but also could want use openvpn 
via NM. As for now I assume both is not possible.

1: I think it is necessary to be able to use both ways.
2: It took me quite a while to find out why there where no proper routes. It is 
essential to tell people how to work around this.
3: systemd-netword is _not_ running on these machines. I would like to 
understand why NM behaves like this. 
4: For testing I used wicd to see if there is a difference. And it is. wicd 
does not mess with the vpn routes.

Let me know if you need more information.


NetworkManager.conf:

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false
#dns=dnsmasq

[keyfile]
unmanaged-devices=interface-name:tun0

journal: journalctl -u NetworkManager

NetworkManager[859]:   (tun0): new Tun device (carrier: OFF, driver: 
'tun', ifindex: 6)
NetworkManager[859]:   devices added (path: 
/sys/devices/virtual/net/tun0, iface: tun0)
NetworkManager[859]:   device added (path: /sys/devices/virtual/net/tun0, 
iface: tun0): no ifupdown configuration found.
NetworkManager[859]:   (tun0): link connected
NetworkManager[859]:   keyfile: add connection in-memory 
(968e1d17-6272-4a1d-9cfa-d2db26ef9607,"tun0")
NetworkManager[859]:   (tun0): device state change: unmanaged -> 
unavailable (reason 'connection-assumed') [10 20 41]
NetworkManager[859]:   (tun0): device state change: unavailable -> 
disconnected (reason 'connection-assumed') [20 30 41]
NetworkManager[859]:   Device 'tun0' has no connection; scheduling 
activate_check in 0 seconds. 
NetworkManager[859]:   (tun0): Activation: starting connection 'tun0' 
(968e1d17-6272-4a1d-9cfa-d2db26ef9607)
NetworkManager[859]:   (tun0): device state change: disconnected -> 
prepare (reason 'none') [30 40 0]
NetworkManager[859]:   (tun0): device state change: prepare -> config 
(reason 'none') [40 50 0]
NetworkManager[859]:   (tun0): device state change: config -> ip-config 
(reason 'none') [50 70 0]
NetworkManager[859]:   (tun0): device state change: ip-config -> ip-check 
(reason 'none') [70 80 0]
NetworkManager[859]:   (tun0): device state change: ip-check -> 
secondaries (reason 'none') [80 90 0]
NetworkManager[859]:   (tun0): device state change: secondaries -> 
activated (reason 'none') [90 100 0]
NetworkManager[859]:   (tun0): Activation: successful, device activated.

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


** Tags: wily

** Tags added: wily

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

Title:
  Systemd + NerworkManager since 15.10 break VPN Support

Status in network-manager package in Ubuntu:
  New

Bug description:
  Release: lsb_release -rd
  Description:  Ubuntu 15.10
  Release:  15.10

  Package Version:
  apt-cache policy network-manager
  network-manager:
Installiert:   1.0.4-0ubuntu5.1
Installationskandidat: 1.0.4-0ubuntu5.1

  apt-cache policy  systemd
  systemd:
Installiert:   225-1ubuntu9
Installationskandidat: 225-1ubuntu9

  What you expected to happen:

  If I start a VPN-Client like Junipers NetworkConnect or openconnect, I
  expect a VPN-tunnel with a tun-device and the corresponding routes via
  this device.

  What happened instead:

  After a successful connection to the vpn gateway the VPN-Client gets informed 
about routes it should create on the client from the VPN gateway and performs 
the