[Desktop-packages] [Bug 1492655] Re: upower crashed after plugging usb device

[Herminio]

** Attachment added: "upower.log"
   
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1492655/+attachment/4458573/+files/upower.log

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

Title:
  upower crashed after plugging usb device

Status in upower package in Ubuntu:
  New

Bug description:
  I plugged in my iphone into my usb port and got no connection, then I
  plugged it into another usb port and upower crashed. below is the
  dmesg log.

  [  249.000800] traps: upowerd[1710] general protection ip:7ffac40f31cb 
sp:7ffdad8ebeb0 error:0 in libc-2.21.so[7ffac4074000+1c]
  [  250.830414] panel-5-power-m[1753]: segfault at 8 ip 7fe58fe5c6fa sp 
7ffc40ce3778 error 4 in libc-2.21.so[7fe58fdd1000+1c]
  [  255.001463] traps: upowerd[2037] general protection ip:7f11da00f693 
sp:7ffc517d43d0 error:0 in libplist.so.3.0.0[7f11da009000+a000]
  [  255.764318] panel-5-power-m[2040]: segfault at 8 ip 7ff6e0cf76fa sp 
7ffdf90df9d8 error 4 in libc-2.21.so[7ff6e0c6c000+1c]
  [  258.000892] traps: upowerd[2086] general protection ip:7fd25097c1cb 
sp:7ffe045442e0 error:0 in libc-2.21.so[7fd2508fd000+1c]
  [  263.782267] panel-5-power-m[2205]: segfault at 8 ip 7f3086c2f6fa sp 
7ffd43f574e8 error 4 in libc-2.21.so[7f3086ba4000+1c]
  [  266.002118] traps: upowerd[2211] general protection ip:7f23d0f3f1cb 
sp:7ffc1b4a2b10 error:0 in libc-2.21.so[7f23d0ec+1c]
  [  273.784371] panel-5-power-m[2357]: segfault at 8 ip 7fa697e5a6fa sp 
7fff80fb5d98 error 4 in libc-2.21.so[7fa697dcf000+1c]
  [  276.001565] traps: upowerd[2363] general protection ip:7f1591a971cb 
sp:7ffcd9dbdb60 error:0 in libc-2.21.so[7f1591a18000+1c]
  [  276.827205] panel-5-power-m[2401]: segfault at 8 ip 7fc32e4f76fa sp 
7ffea2e4cc38 error 4 in libc-2.21.so[7fc32e46c000+1c]
  [  279.848223] panel-5-power-m[2453]: segfault at 8 ip 7f67caf2a6fa sp 
7ffe2cca8958 error 4 in libc-2.21.so[7f67cae9f000+1c]
  [  284.001686] traps: upowerd[2501] general protection ip:7fd7125011cb 
sp:7ffe31685b20 error:0 in libc-2.21.so[7fd712482000+1c]
  [  287.001308] traps: upowerd[2538] general protection ip:7fa08e0641cb 
sp:7ffe1acc0ab0 error:0 in libc-2.21.so[7fa08dfe5000+1c]
  [  290.000986] traps: upowerd[2620] general protection ip:7f283691b1cb 
sp:7ffc7833ed70 error:0 in libc-2.21.so[7f283689c000+1c]
  [  293.000365] traps: upowerd[2742] general protection ip:7f9610bb91cb 
sp:7fffd83804c0 error:0 in libc-2.21.so[7f9610b3a000+1c]
  [  296.001657] traps: upowerd[2874] general protection ip:7f4c8ca461cb 
sp:7ffed229c480 error:0 in libc-2.21.so[7f4c8c9c7000+1c]
  [  305.001335] traps: upowerd[3308] general protection ip:7f92dd6da1cb 
sp:7ffe62057490 error:0 in libc-2.21.so[7f92dd65b000+1c]
  [  308.001320] traps: upowerd[3384] general protection ip:7fea523a81cb 
sp:7fff3de785a0 error:0 in libc-2.21.so[7fea52329000+1c]
  [  314.001036] traps: upowerd[3475] general protection ip:7fc37c7a61cb 
sp:7ffda5f5e630 error:0 in libc-2.21.so[7fc37c727000+1c]
  [  317.001537] traps: upowerd[3519] general protection ip:7f8da1f911cb 
sp:7ffdc042c440 error:0 in libc-2.21.so[7f8da1f12000+1c]
  [  325.390590] traps: upowerd[3556] general protection ip:7fd75cbb01cb 
sp:7ffddf371cb0 error:0 in libc-2.21.so[7fd75cb31000+1c]
  [  328.000949] traps: upowerd[3886] general protection ip:7f77012161cb 
sp:7fff096428f0 error:0 in libc-2.21.so[7f7701197000+1c]
  [  333.001386] traps: upowerd[4042] general protection ip:7f12bc7351cb 
sp:7ffea69256e0 error:0 in libc-2.21.so[7f12bc6b6000+1c]
  [  336.000552] traps: upowerd[4087] general protection ip:7fa0a39131cb 
sp:7ffd7c666d50 error:0 in libc-2.21.so[7fa0a3894000+1c]
  [  339.001602] traps: upowerd[4209] general protection ip:7f744fd241cb 
sp:7ffe3d033260 error:0 in libc-2.21.so[7f744fca5000+1c]
  [  342.001113] upowerd[4390]: segfault at 0 ip 7faa9e668a1f sp 
7ffeec04c190 error 4 in libplist.so.3.0.0[7faa9e661000+a000]
  [  345.001387] traps: upowerd[4567] general protection ip:7f75ba9de1cb 
sp:7ffe69a21c00 error:0 in libc-2.21.so[7f75ba95f000+1c]
  [  350.001263] traps: upowerd[4642] general protection ip:7fb7050d01cb 
sp:7ffec44a7740 error:0 in libc-2.21.so[7fb705051000+1c]
  [  353.001649] traps: upowerd[4678] general protection ip:7fdceaa911cb 
sp:7ffcf03ce3b0 error:0 in libc-2.21.so[7fdceaa12000+1c]
  [  356.001052] traps: upowerd[4714] general protection ip:7f143c2a31cb 
sp:7ffc7c58d6f0 error:0 in libc-2.21.so[7f143c224000+1c]
  [  359.001678] traps: upowerd[4750] general protection ip:7f27b35371cb 
sp:7ffc4ed225f0 error:0 in libc-2.21.so[7f27b34b8000+1c]
  [  362.001725] traps: upowerd[4798] general protection ip:7fe75e24c1cb 
sp:7ffc21fd27a0 error:0 in libc-2.21.so[7fe75e1cd000+1c]
  [  365.001910] traps: upowerd[4834] general protection ip:7f1790f841cb 

[Desktop-packages] [Bug 1492840] [NEW] Softlockup on boot of Kubuntu 14.04-3 Live-ISO

[private_lock]

Public bug reported:

Summary:
Booting a Live-session, I reach the language selection. On click on "try 
Kubuntu" without install, first the mouse changes to two balls circling each 
other. Next the dialog goes half transparent and the mouse pointer is gone. It 
won't react to any keyboard input.

Details:
I've downloaded the recent longterm release:
http://cdimage.ubuntu.com/kubuntu/releases/14.04.3/release/kubuntu-14.04.3-desktop-amd64.iso
sha256sum 44cc15a31f9a3a6b583929ce711a5eb76fddb1ba447726f9bb2539d78b7a53bc

I installed it via USB-creator to my USB pen drive and ran the internal
md5sum checks successfully.

On boot I get to the dialog to select the language, that I can switch
back and forth. Also there's a link that can bring up a Konqueror window
(though without entering my WiFi password, it won't connect). In
addition, I can switch to a console via Ctrl+Alt+F1

Once I click the "try Kubuntu"-button, the error occurs. So I klicked it
and while the mouse-cursor balls were still cycling I switched to
console.

Alt+SysReq+1 was not supported
Alt+SysReq+t first didn't do anything, so I tried switching back via 
Ctrl+Alt+F7 and it immediately dumped some cryptic stuff to the console, that 
refreshes about ever 30 seconds only to repeat itself. I'll attach a photo.

BTW: I tried to update the BIOS to no avail (the new BIOS shows exactly
the same behavior on this machine). ubuntu-bug was run on the same
hardware but in a newer Kubuntu 15.04 installed on it's harddrive.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Sep  6 22:02:37 2015
InstallationDate: Installed on 2014-04-12 (512 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.2)
ProcEnviron:
 LANGUAGE=de:en_US:en_GB:fr
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to vivid on 2015-05-04 (125 days ago)

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


** Tags: amd64 apport-bug fonts kubuntu vivid

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1492840/+attachment/4458438/+files/IMG_20150906_214126.jpg

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

Title:
  Softlockup on boot of Kubuntu 14.04-3 Live-ISO

Status in xorg package in Ubuntu:
  New

Bug description:
  Summary:
  Booting a Live-session, I reach the language selection. On click on "try 
Kubuntu" without install, first the mouse changes to two balls circling each 
other. Next the dialog goes half transparent and the mouse pointer is gone. It 
won't react to any keyboard input.

  Details:
  I've downloaded the recent longterm release:
  
http://cdimage.ubuntu.com/kubuntu/releases/14.04.3/release/kubuntu-14.04.3-desktop-amd64.iso
  sha256sum 44cc15a31f9a3a6b583929ce711a5eb76fddb1ba447726f9bb2539d78b7a53bc

  I installed it via USB-creator to my USB pen drive and ran the
  internal md5sum checks successfully.

  On boot I get to the dialog to select the language, that I can switch
  back and forth. Also there's a link that can bring up a Konqueror
  window (though without entering my WiFi password, it won't connect).
  In addition, I can switch to a console via Ctrl+Alt+F1

  Once I click the "try Kubuntu"-button, the error occurs. So I klicked
  it and while the mouse-cursor balls were still cycling I switched to
  console.

  Alt+SysReq+1 was not supported
  Alt+SysReq+t first didn't do anything, so I tried switching back via 
Ctrl+Alt+F7 and it immediately dumped some cryptic stuff to the console, that 
refreshes about ever 30 seconds only to repeat itself. I'll attach a photo.

  BTW: I tried to update the BIOS to no avail (the new BIOS shows
  exactly the same behavior on this machine). ubuntu-bug was run on the
  same hardware but in a newer Kubuntu 15.04 installed on it's
  harddrive.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Sep  6 22:02:37 2015
  InstallationDate: Installed on 2014-04-12 (512 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326.2)
  ProcEnviron:
   LANGUAGE=de:en_US:en_GB:fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to vivid on 2015-05-04 (125 days ago)

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

nvidia driver install log

** Attachment added: "installnv.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458481/+files/installnv.log

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

Xorg.0.log prior to nvidia driver install

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458482/+files/Xorg.0.log

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

lightdm.log prior to nvidia driver install

** Attachment added: "lightdm.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458483/+files/lightdm.log

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

Bit = 1 ID0 ID1 ID2 ID3 ID4 ID5 ID6 ID7 ID8 ID9

Function Dedicated Mic 
PCM In Channel 
Modem Line Codec Support 
Bass and Treble Control 
Simulated Stereo (Mono to Stereo) 
Headphone Out Support 
Loudness (Bass Boost) Support 
18-Bit DAC Resolution 
20-Bit DAC Resolution 
18-Bit ADC Resolution 
20-Bit ADC Resolution 


AD1980 
0 0 0 0 1 0 0 1 0 0

a reset register of real ad1980 return 0x0090 which indicate 20 bit DAC
resolution and Headphone support

but enumerated ad1980 return 0

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in Virtualbox:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 844081]

[Jefa]

Why would anyone oppose adding such a small and useful feature? I don't
understand why this has sat here, unanswered, for four years!

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

Title:
  Unity Greeter - Background of the Unity Greeter should reflect the
  background chosen by the user that is currently selected

Status in accountsservice:
  Confirmed
Status in Ayatana Design:
  Fix Released
Status in Light Display Manager:
  Fix Released
Status in Unity Greeter:
  Fix Released
Status in accountsservice package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Fix Released

Bug description:
  Background of the Unity Greeter should reflect the background chosen
  by the user that is currently selected.

  e.g. the background the user has selected on their desktop should be
  displayed in the greeter.  See the attached animation
  login_screen_v02_WP.mov to understand exactly how the backgrounds
  should crossfade.

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

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

[Desktop-packages] [Bug 1472097] Re: XMir crashes when running with -rootless

[Robert Ancell]

** Changed in: xorg-server (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  XMir crashes when running with -rootless

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Ted has run into problems trying to integrate XMir with Unity8. When
  he starts an app, XMir aborts in compCopyWindow. (Log attached)

  This seems to be because compCopyWindow has been called before
  compConfigNotify (which in turn call compReallocPixmap, and set
  cw->oldx to valid values). This might be an initialisation order
  problem in XMir.

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

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

[Desktop-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

to avoid the driver rename master playback volume to master surround,
you need to specify

ac97->spec.ad18xx.lo_as_master = 1;

only for the enumerated ad1980 codec inside virtualbox



static int patch_ad1888(struct snd_ac97 * ac97)
{
unsigned short misc;

patch_ad1881(ac97);
ac97->build_ops = _ad1888_build_ops;

/*
 * LO can be used as a real line-out on some devices,
 * and we need to revert the front/surround mixer switches
 */
if (ac97->subsystem_vendor == 0x1043 &&
ac97->subsystem_device == 0x1193) /* ASUS A9T laptop */
ac97->spec.ad18xx.lo_as_master = 1;

misc = snd_ac97_read(ac97, AC97_AD_MISC);
/* AD-compatible mode */
/* Stereo mutes enabled */
misc |= AC97_AD198X_MSPLT | AC97_AD198X_AC97NC;
if (!ac97->spec.ad18xx.lo_as_master)
/* Switch FRONT/SURROUND LINE-OUT/HP-OUT default connection */
/* it seems that most vendors connect line-out connector to
 * headphone out of AC'97
 */
misc |= AC97_AD198X_LOSEL | AC97_AD198X_HPSEL;

snd_ac97_write_cache(ac97, AC97_AD_MISC, misc);
ac97->flags |= AC97_STEREO_MUTES;
return 0;
}

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in Virtualbox:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1492655] Re: upower crashed after plugging usb device

[Herminio]

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

** This bug has been marked a duplicate of bug 1305699
   upowerd crashed with SIGSEGV in service_client_free()

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

Title:
  upower crashed after plugging usb device

Status in upower package in Ubuntu:
  New

Bug description:
  I plugged in my iphone into my usb port and got no connection, then I
  plugged it into another usb port and upower crashed. below is the
  dmesg log.

  [  249.000800] traps: upowerd[1710] general protection ip:7ffac40f31cb 
sp:7ffdad8ebeb0 error:0 in libc-2.21.so[7ffac4074000+1c]
  [  250.830414] panel-5-power-m[1753]: segfault at 8 ip 7fe58fe5c6fa sp 
7ffc40ce3778 error 4 in libc-2.21.so[7fe58fdd1000+1c]
  [  255.001463] traps: upowerd[2037] general protection ip:7f11da00f693 
sp:7ffc517d43d0 error:0 in libplist.so.3.0.0[7f11da009000+a000]
  [  255.764318] panel-5-power-m[2040]: segfault at 8 ip 7ff6e0cf76fa sp 
7ffdf90df9d8 error 4 in libc-2.21.so[7ff6e0c6c000+1c]
  [  258.000892] traps: upowerd[2086] general protection ip:7fd25097c1cb 
sp:7ffe045442e0 error:0 in libc-2.21.so[7fd2508fd000+1c]
  [  263.782267] panel-5-power-m[2205]: segfault at 8 ip 7f3086c2f6fa sp 
7ffd43f574e8 error 4 in libc-2.21.so[7f3086ba4000+1c]
  [  266.002118] traps: upowerd[2211] general protection ip:7f23d0f3f1cb 
sp:7ffc1b4a2b10 error:0 in libc-2.21.so[7f23d0ec+1c]
  [  273.784371] panel-5-power-m[2357]: segfault at 8 ip 7fa697e5a6fa sp 
7fff80fb5d98 error 4 in libc-2.21.so[7fa697dcf000+1c]
  [  276.001565] traps: upowerd[2363] general protection ip:7f1591a971cb 
sp:7ffcd9dbdb60 error:0 in libc-2.21.so[7f1591a18000+1c]
  [  276.827205] panel-5-power-m[2401]: segfault at 8 ip 7fc32e4f76fa sp 
7ffea2e4cc38 error 4 in libc-2.21.so[7fc32e46c000+1c]
  [  279.848223] panel-5-power-m[2453]: segfault at 8 ip 7f67caf2a6fa sp 
7ffe2cca8958 error 4 in libc-2.21.so[7f67cae9f000+1c]
  [  284.001686] traps: upowerd[2501] general protection ip:7fd7125011cb 
sp:7ffe31685b20 error:0 in libc-2.21.so[7fd712482000+1c]
  [  287.001308] traps: upowerd[2538] general protection ip:7fa08e0641cb 
sp:7ffe1acc0ab0 error:0 in libc-2.21.so[7fa08dfe5000+1c]
  [  290.000986] traps: upowerd[2620] general protection ip:7f283691b1cb 
sp:7ffc7833ed70 error:0 in libc-2.21.so[7f283689c000+1c]
  [  293.000365] traps: upowerd[2742] general protection ip:7f9610bb91cb 
sp:7fffd83804c0 error:0 in libc-2.21.so[7f9610b3a000+1c]
  [  296.001657] traps: upowerd[2874] general protection ip:7f4c8ca461cb 
sp:7ffed229c480 error:0 in libc-2.21.so[7f4c8c9c7000+1c]
  [  305.001335] traps: upowerd[3308] general protection ip:7f92dd6da1cb 
sp:7ffe62057490 error:0 in libc-2.21.so[7f92dd65b000+1c]
  [  308.001320] traps: upowerd[3384] general protection ip:7fea523a81cb 
sp:7fff3de785a0 error:0 in libc-2.21.so[7fea52329000+1c]
  [  314.001036] traps: upowerd[3475] general protection ip:7fc37c7a61cb 
sp:7ffda5f5e630 error:0 in libc-2.21.so[7fc37c727000+1c]
  [  317.001537] traps: upowerd[3519] general protection ip:7f8da1f911cb 
sp:7ffdc042c440 error:0 in libc-2.21.so[7f8da1f12000+1c]
  [  325.390590] traps: upowerd[3556] general protection ip:7fd75cbb01cb 
sp:7ffddf371cb0 error:0 in libc-2.21.so[7fd75cb31000+1c]
  [  328.000949] traps: upowerd[3886] general protection ip:7f77012161cb 
sp:7fff096428f0 error:0 in libc-2.21.so[7f7701197000+1c]
  [  333.001386] traps: upowerd[4042] general protection ip:7f12bc7351cb 
sp:7ffea69256e0 error:0 in libc-2.21.so[7f12bc6b6000+1c]
  [  336.000552] traps: upowerd[4087] general protection ip:7fa0a39131cb 
sp:7ffd7c666d50 error:0 in libc-2.21.so[7fa0a3894000+1c]
  [  339.001602] traps: upowerd[4209] general protection ip:7f744fd241cb 
sp:7ffe3d033260 error:0 in libc-2.21.so[7f744fca5000+1c]
  [  342.001113] upowerd[4390]: segfault at 0 ip 7faa9e668a1f sp 
7ffeec04c190 error 4 in libplist.so.3.0.0[7faa9e661000+a000]
  [  345.001387] traps: upowerd[4567] general protection ip:7f75ba9de1cb 
sp:7ffe69a21c00 error:0 in libc-2.21.so[7f75ba95f000+1c]
  [  350.001263] traps: upowerd[4642] general protection ip:7fb7050d01cb 
sp:7ffec44a7740 error:0 in libc-2.21.so[7fb705051000+1c]
  [  353.001649] traps: upowerd[4678] general protection ip:7fdceaa911cb 
sp:7ffcf03ce3b0 error:0 in libc-2.21.so[7fdceaa12000+1c]
  [  356.001052] traps: upowerd[4714] general protection ip:7f143c2a31cb 
sp:7ffc7c58d6f0 error:0 in libc-2.21.so[7f143c224000+1c]
  [  359.001678] traps: upowerd[4750] general protection ip:7f27b35371cb 
sp:7ffc4ed225f0 error:0 in libc-2.21.so[7f27b34b8000+1c]
  [  362.001725] traps: upowerd[4798] general protection ip:7fe75e24c1cb 
sp:7ffc21fd27a0 error:0 in libc-2.21.so[7fe75e1cd000+1c]
  [  

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

from boot up with nvidia to black greeter, blind log in to black screen

** Attachment added: "unity7.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458583/+files/unity7.log

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492873] [NEW] nvidiadetector.py: neglects to match on class code 0302 3D Controller

[TJ]

Public bug reported:

Helping a user on IRC where ubuntu-drivers failed to detect

0a:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX
850M] [10de:1391] (rev a2)

Looking at the source-code I noticed that

/usr/lib/python3/dist-
packages/NvidiaDetector/nvidiadetector.py::detection()

is not matching on class 0302 (despite the associated fake entry comment
for debugging suggesting it)

The work-around is to amend the code thus:

sudo sed -i 's/0300/(0300|0302)/' /usr/lib/python3/dist-
packages/NvidiaDetector/nvidiadetector.py

Running ubuntu-drivers now matches the 3D Controller

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: High
 Status: Triaged

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided => High

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

Title:
  nvidiadetector.py: neglects to match on class code 0302 3D Controller

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

Bug description:
  Helping a user on IRC where ubuntu-drivers failed to detect

  0a:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX
  850M] [10de:1391] (rev a2)

  Looking at the source-code I noticed that

  /usr/lib/python3/dist-
  packages/NvidiaDetector/nvidiadetector.py::detection()

  is not matching on class 0302 (despite the associated fake entry
  comment for debugging suggesting it)

  The work-around is to amend the code thus:

  sudo sed -i 's/0300/(0300|0302)/' /usr/lib/python3/dist-
  packages/NvidiaDetector/nvidiadetector.py

  Running ubuntu-drivers now matches the 3D Controller

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

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

[Desktop-packages] [Bug 1492288] Re: fglrx-core 2:15.200-0ubuntu0.5: fglrx-core kernel module failed to build

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1311838
   fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to 
build on 3.15 [/usr/sbin/dkms: line 73: cd: /var/lib/dkms/fglrx/13.350.1/build: 
No such file or directory]

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

Title:
  fglrx-core 2:15.200-0ubuntu0.5: fglrx-core kernel module failed to
  build

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  I am  Install linux 4.2

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-core 2:15.200-0ubuntu0.5
  ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 4.2.0
  Date: Fri Sep  4 09:26:14 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.200, 3.19.0-26-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] 
[1002:67b1] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:228f]
  InstallationDate: Installed on 2015-08-11 (23 days ago)
  InstallationMedia: It
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-USB3
  PackageVersion: 2:15.200-0ubuntu0.5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=fa72e1ae-b42d-4edb-b1d3-693da93fcc58 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.200-0ubuntu0.5: fglrx-core kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FC
  dmi.board.name: GA-880GM-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd03/14/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-USB3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GM-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64+git1509021830.949c32~gd~t
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1~git1509031930.70dbdc~gd~t
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1~git1509031930.70dbdc~gd~t
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.99+git1508200731.0288a4~gd~t
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1508251931.300319~gd~t
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git1508040731.629614~gd~t
  xserver.bootTime: Fri Sep  4 00:06:04 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: fglrx

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

-- 

[Desktop-packages] [Bug 1443767] Re: The installation window was not shown completely with vivid-desktop-amd64-20150408 on hidpi laptop

[Bin Li]

Lars,

 Yes, I agree with your idea, we should adjust the hidpi from a higher
value, is it ok that we change DPI_FALLBACK to 110, or change
HIDPI_LIMIT directly? Thanks!

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

Title:
  The installation window was not shown completely with vivid-desktop-
  amd64-20150408  on hidpi laptop

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in Unity Settings Daemon:
  New
Status in ubiquity package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  1. Burn vivid-desktop-amd64-20150408.iso to USB stick.
  2. Boot from USB stick to install the ubuntu.
  3. The window "Keyboard layout" wasn't shown complete on hidpi laptop.

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

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

[Desktop-packages] [Bug 1491071] Re: Xmir doesn't update the screen size until something is actually rendered

[Robert Ancell]

Hey, you know XMir is on a git branch right?

lp:~xmir-team/xorg-server/+git/xmir

where lp is git+ssh://usern...@git.launchpad.net/

Should be easier to generate diffs - propose merges.

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

Title:
  Xmir doesn't update the screen size until something is actually
  rendered

Status in xorg-server package in Ubuntu:
  New

Bug description:
  In trying to get Compiz working under Xmir in Unity 8 desktop mode, I
  have found that when a Mir window opens and then resizes to whatever
  Unity 8 tells it to, the resize event does not get propagated down
  until another resize event occurs.

  For example, I start up an X app.  The Xmir window opens and is
  resized, but internally, Xmir still reports the full screen size so
  when Compiz starts, it thinks the surface size is the size of the
  physical display.

  I'll include a patch that fixes this and we can discuss if it's a good
  fix.

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

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

[Desktop-packages] [Bug 1491071] Re: Xmir doesn't update the screen size until something is actually rendered

[Robert Ancell]

The patch files in the Ubuntu package are just generated from the git
branch using format-patch. I rebase this branch each time I update the
Ubuntu package.

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

Title:
  Xmir doesn't update the screen size until something is actually
  rendered

Status in xorg-server package in Ubuntu:
  New

Bug description:
  In trying to get Compiz working under Xmir in Unity 8 desktop mode, I
  have found that when a Mir window opens and then resizes to whatever
  Unity 8 tells it to, the resize event does not get propagated down
  until another resize event occurs.

  For example, I start up an X app.  The Xmir window opens and is
  resized, but internally, Xmir still reports the full screen size so
  when Compiz starts, it thinks the surface size is the size of the
  physical display.

  I'll include a patch that fixes this and we can discuss if it's a good
  fix.

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

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

[Desktop-packages] [Bug 1492430] Re: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound at all

[keith lebrun]

I'm confused. This is an Alienware Area 51 desktop box. It has 3 outputs
- Front/Center/Rear. It looks like the referenced patch covers the
Alienware 15 LAPTOP with only built-in speakers. Is there no real
support for this particular configuration?

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

Title:
  [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 15.04
  Release:  15.04

  
  This is a 5.1 surround sound set up. No output from any speaker. Sound 
settings configuration doesn't show proper options for this card - no channel 
info except for analog stereo and S/PDIF outputs where I would expect to see 
information on Front/Rear/Center speaker outputs.

  Output from aplay -l:

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: CA0132 Analog [CA0132 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 1: CA0132 Digital [CA0132 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 1: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  lspci output:

  00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio 
Controller (rev 05)
Subsystem: Dell Device 064c
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: snd_hda_intel

  --
  03:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio 
Controller (rev a1)
Subsystem: NVIDIA Corporation Device 1131
Physical Slot: 6
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: snd_hda_intel

  
  Output from alsa-info.sh can be found at 
http://www.alsa-project.org/db/?f=b64f2a2d9279d19e6a0967202595956db577

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-26.28-lowlatency 3.19.8-ckt4
  Uname: Linux 3.19.0-26-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keith  1905 F pulseaudio
   /dev/snd/controlC1:  keith  1905 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Sep  4 14:24:12 2015
  InstallationDate: Installed on 2015-09-01 (3 days ago)
  InstallationMedia: Ubuntu-Studio 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  keith  1905 F pulseaudio
   /dev/snd/controlC1:  keith  1905 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [Alienware Area-51 R2, Creative CA0132, Green Line Out, Rear] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: A03
  dmi.board.name: 0XJKKD
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.modalias: 
dmi:bvnAlienware:bvrA03:bd07/13/2015:svnAlienware:pnAlienwareArea-51R2:pvr:rvnAlienware:rn0XJKKD:rvrA01:cvnAlienware:ct3:cvr:
  dmi.product.name: Alienware Area-51 R2
  dmi.sys.vendor: Alienware

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

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

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Kostadin Stoilov]

Experiencing this on 14.04 LTS and iPhone 4s with iOS 8.4. Would
appreciate a backport to Trusty. I am also happy to help with testing.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1492766] Re: nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to build

[Daniel van Vugt]

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

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


** This bug has been marked a duplicate of bug 1477593
   nvidia-340-updates 340.76-0ubuntu2: nvidia-340-updates kernel module failed 
to build [FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only 
symbol 'flush_workqueue']

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

Title:
  nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to
  build

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

Bug description:
  Found when upgrading to kernel 4.2 in ubuntu  gnome 14.04.

  Installed following these instructions:

  $ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
  headers-4.2.0-040200_4.2.0-040200.201508301530_all.deb

  $ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
  headers-4.2.0-040200-lowlatency_4.2.0-040200.201508301530_amd64.deb

  $ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
  image-4.2.0-040200-lowlatency_4.2.0-040200.201508301530_amd64.deb.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.125-0ubuntu0.0.2
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  DKMSKernelVersion: 4.2.0-040200-lowlatency
  Date: Sun Sep  6 09:23:26 2015
  InstallationDate: Installed on 2010-05-29 (1926 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  PackageVersion: 304.125-0ubuntu0.0.2
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2014-05-08 (486 days ago)
  modified.conffile..etc.modprobe.d.nvidia.304.hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1492385] Re: Rendering issue when display scaling is set to a value greater than 1

[marmuta]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1283491 so it is being marked as such. Any further
discussion regarding the bug should occur in the other report. Feel free
to continue to report any other bugs you may find.

An updated onboard 1.0.1 for Ubuntu 14.04 is currently in in the
-proposed repository, see Bug #1289592. I've just tested it (again) and
found no major issues with scaling != 1. If you wait a little bit longer
it will probably enter the main repo too.

In any case you are welcome to get the latest version 1.1.2 from our PPA at 
https://launchpad.net/~onboard/+archive/ubuntu/stable
That one has lots of other fixes and should auto-hide when you type with the 
Yoga's keyboard.

** This bug has been marked a duplicate of bug 1283491
   rendering and size issues on high-dpi screen

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

Title:
  Rendering issue when display scaling is set to a value greater than 1

Status in onboard package in Ubuntu:
  New

Bug description:
  Occurs on a Yoga 2 Pro (Intel HD Graphics 4400 @ 3200 X 1800).

  Set All Settings -> Screen Display -> Scale for menu and title
  bars to 2

  Run onboard

  Partial rendering of the top left corner of the keyboard occurs. The
  rest renders as background only leaving the app unusable. Resizing or
  moving the keyboard is also impossible. Does not occur when Scaling is
  set to 1.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep  4 17:26:21 2015
  InstallationDate: Installed on 2015-05-01 (125 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492767] Re: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

[Mélodie]

It had seemed pretty bad, and I was in a wonder how something such as
that can even happen, so I tried to reproduce it by installing the same
ISO/Version in Virtualbox, and could not even reproduce it myself.

There is still the error message at post install, but it does not affect
the GUI in any way. I installed twice in a row in Virtualbox to be sure
of the result and each time after updating, I didn't get the GUI to go
wrong as it happened in that laptop.

So this bug report can be put aside, unless something new comes out with
gdkpixbuf.

Best regards,
Mélodie

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

Title:
  gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Hello,

  I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday (custom
  Bento Openbox), and today, I updated the system (with the console,
  because other issues came first which led me to do a filesystem
  check). Then I started Synaptic, and oops! no GUI, only the borders of
  the window would show. Several other programs were affected and would
  not start (Geany, text editor), or show their content. After tests and
  research it appeared only GTK3 programs were affected. If using a
  theme with GTK2, or move the GTK configuration out of the way, the
  programs would work.

  The upgrade contained the following packages:
  gir1.2-gdkpixbuf-2.0_2.30.7
  libgdk-pixbuf2.0-0_2.30.7
  libgdk-pixbuf2.0-common_2.30.7

  I fixed the issue by booting to the Live USB I had used to install,
  and repackage the programs with dpkg-repack, then reinstalled them
  using "sudo dpkg -i *.deb". (copied from the live usb to the home in
  the install, rebooted and reinstalled there).

  Problem solved for this install, where I have for now blocked the
  update for these three packages.

  At post-install, after I had updated, I had the same message as the people 
who reported that bug:
  https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294

  
  (gtk-update-icon-cache-3.0:29671): 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.
  

  and when trying to do so, the console returned a message stating gdk-
  pixbuf-query-loaders was not installed. (no such package in the repos
  either).

  More information can be found at
  http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html

  where I discussed about this bug and my findings.

  Now I will try to produce this bug again in the Live USB (which has no
  persistence).

  Best regards,
  Mélodie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1492767/+subscriptions

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

[Desktop-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

> I would also guess that it is not likely that Virtual Box is the direct
 cause because the list of work distros runs on the same Virtualbox platform
 that serves the failing distros.

NO, the change of enumerated ac97 codec from stac9200 to ad1980 in
virtualbox is the main cause of the problem


unfortuately enable log by dev_ac97 still not sufficient to produce
useful debug info


you need to recompile alsa driver by adding those dev_info to dump the values 
of ac97 codec registers read/write


the worst thing is the ad1980 in dell imension 8400 did not work in the above 
bug report, 


it is not clear how headphone and line out use/share volume control

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in Virtualbox:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Johan Potgieter]

I get this on Xubuntu 14.04 whenever I connect via wifi to my ios
personal hotspot. Often it does nothing more than ask to send the report
but other times it hangs after a few minutes. I have found it so
disruptive that I am unable to get any work done while connected to my
phone. I will try some of the remedies and hopefully it will sort out my
issue.

I wanted to add this note as I didn't see any mention of this happening
while connecting to a personal hotspot, as is the case with me.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1289592] Re: SRU request for bugfix release (debian.tar.gz for trusty provided)

[marmuta]

I've tested onboard+onboard-data 1.0.1-0ubuntu1 from the -proposed repository 
on a fresh install of current trusty and didn't find any regressions.
Login and unlocking the screen work as before. The keyboard is usable with 
org.gnome.interface scaling-factor != 1 - I've tried 0.5, 1, 2 and 4 in display 
settings and typed with (multi-)touch and mouse devices. Language menu closes 
on second click. Auto-show, word suggestions, transparency, docking, etc. work 
as expected back in 1.0.1.

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

Title:
  SRU request for bugfix release (debian.tar.gz for trusty provided)

Status in onboard package in Ubuntu:
  Fix Released
Status in onboard source package in Trusty:
  Fix Committed
Status in onboard source package in Utopic:
  Won't Fix
Status in onboard source package in Vivid:
  Fix Released

Bug description:
  Hi,

  We have just created a new bugfix micro-release for the version of
  Onboard shipping with Ubuntu trusty and hope that you will be able to
  pick it up.

  IMPACT
  
  It contains the following changes compared to the version currently shipping 
with trusty:

  onboard (1.0.1-0ubuntu1) trusty; urgency=medium

    * Request for sponsorship for new upstream release (LP: #1289592)
    * debian/copyright:
  - Update and refine copyright section
    * debian/patches/add_defaults_for_ubuntu.patch:
  - Add more xembed entries to onboard-defaults.conf
    * Add initial support for org.gnome.interface scaling-factor > 1 (LP 
#1283491)
    * Catch Onboard becoming unresponsive due to invisible dialogs
    * Small fix in the word suggestion line of the layouts
    * Fix loading of desktop backgrounds with non-ascii filenames
    * Fix startup failures in case of no defined locale or non-unicode locales
    * Fix handling of hint file with wrong permissions in /tmp
    * Fix black bars when xembedding
    * Ignore x-offset when xembedding in unity-greeter on small screens
    * Add more entries about embedding to the system defaults example file
    * Don't activate the move button twice on press
    * Assume RGBA support exist without compositing only in unity-greeter
    * Show dialog to enable accessibility also if only word suggestions needs it
    * Close the language menu when the language button is pressed a second time
    * Fix back trace and hangs when using click buttons with python3.2 on 
precise
    * Work around broken introspection of GLib.filename_from_uri() on precise
    * Work around jumpy moves and resizes of keyboard after unhiding by 
auto-show
    * Update window manager quirk selection after name change in gnome-shell
    * Fix a GTK depreciation warning
    * Remove spurious debug output
    * Some code cleanup
    * Update translations

   -- Francesco Fumanti   Fri, 07 Mar 2014
  21:38:09 +0100

  TEST CASE
  
  - Set scaling-factor > 1 and verify that keys are properly sized. Fixes LP: 
#1283491
  - This is a bug-fix micro-release. Install and test for a while to make sure 
of no regressions.

  REGRESSION POTENTIAL
  ---
  - The update contains a few relatively important fixes.
  - Apart the ubuntu-desktop and the xubuntu-desktop metapackages, there is no 
other package depending on it; thus in the worst case of an Onboard breakage, 
it would be limited to Onboard itself.

  Thanks in advance for taking the feature freeze exception request into
  account and feel free to post any questions you might have in this
  thread.

  Cheers,

  Francesco

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

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

[Desktop-packages] [Bug 1492864] [NEW] Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

Public bug reported:

Fresh install of 15.10, image of 09/06, only synaptic installed 
Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

Initial bootup/ login is fine
Installed nvidia-352, install went fine, will attach log
Rebooted to a black greeter screen (heard sound
Logged in blindly, black screen

rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
Result was a login with no compiz, no unity as the OpenGl plugin was not loaded 
nor from some further tests could be.
The only way forward was to remove ~/.config/dconf/user from a tty, then reboot

Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 & 15.04

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: nvidia-prime 0.8.1
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
CurrentDesktop: Unity
Date: Sun Sep  6 20:04:35 2015
InstallationDate: Installed on 2015-09-06 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-prime (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 nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1492864

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1462445] Re: Gtk applications start with blank screen (Clutter 1.22.4 and GtkClutter 1.6.2)

[Sean Davis]

Previously associated bug was resolved but did the fix did not apply to
these applications.  Created a new upstream bug.

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

** Changed in: clutter
   Importance: Critical => Unknown

** Changed in: clutter
   Status: Invalid => Unknown

** Changed in: clutter
 Remote watch: GNOME Bug Tracker #743085 => GNOME Bug Tracker #754640

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

Title:
  Gtk applications start with blank screen (Clutter 1.22.4 and
  GtkClutter 1.6.2)

Status in Clutter:
  Unknown
Status in Mugshot:
  New
Status in parole:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in parole package in Ubuntu:
  Confirmed

Bug description:
  Start parole - get blank 'grey' screen.

  (also apparent with version in https://launchpad.net/~xubuntu-
  dev/+archive/ubuntu/ppa/?field.series_filter=wily -currently
  0.8.0+git-0~898~ubuntu15.10.1 )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: parole 0.8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun  5 17:38:06 2015
  InstallationDate: Installed on 2015-05-12 (23 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512)
  SourcePackage: parole
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

[Christoph Buchner]

I see this too with Steam, only for me the log string is " reporting 6 8 17 
141". Ctrl-Win-D workaround seems to work. 
Any updates on this in the meantime?

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

Title:
  DRI_PRIME with radeon/intel windows do not draw

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.04 and Xorg version 1:7.7+7ubuntu2

  Step to reproduce:
  start "DRI_PRIME=1 steam" (or any other complex 3D program like minecraft)

  What is expected:
  the program should show it's window(s), those should have the same content as 
if started without "DRI_PRIME".

  What actually happens:
  most times the program just shows a "freezed" version of the background the 
window appeared on.

  Additional Informations:
  I have the newest BIOS version.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Mar 11 17:01:13 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.18.0-13-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-7-generic, x86_64: installed
   virtualbox, 4.3.24, 3.19.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1486]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=35d0b52c-aa5e-48d2-9eec-f7a6036f2a56 ro splash drm.rnodes=1 
vt.handoff=7
  SourcePackage: xorg
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.20
  dmi.chassis.asset.tag: CNU0250216
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 048920252A2000122
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Mar 10 10:39:26 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38164 
   vendor AUO
  xserver.version: 2:1.16.2.901-1ubuntu4

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

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

[Desktop-packages] [Bug 1462445] Re: Gtk applications start with blank screen (Clutter 1.22.4 and GtkClutter 1.6.2)

[Sean Davis]

** Also affects: xubuntu-default-settings (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Gtk applications start with blank screen (Clutter 1.22.4 and
  GtkClutter 1.6.2)

Status in Clutter:
  Unknown
Status in Mugshot:
  New
Status in parole:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in parole package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Start parole - get blank 'grey' screen.

  (also apparent with version in https://launchpad.net/~xubuntu-
  dev/+archive/ubuntu/ppa/?field.series_filter=wily -currently
  0.8.0+git-0~898~ubuntu15.10.1 )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: parole 0.8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun  5 17:38:06 2015
  InstallationDate: Installed on 2015-05-12 (23 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512)
  SourcePackage: parole
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1462445] Re: Gtk applications start with blank screen (Clutter 1.22.4 and GtkClutter 1.6.2)

[Bug Watch Updater]

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

** Changed in: clutter
   Importance: Unknown => High

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

Title:
  Gtk applications start with blank screen (Clutter 1.22.4 and
  GtkClutter 1.6.2)

Status in Clutter:
  Confirmed
Status in Mugshot:
  New
Status in parole:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in parole package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  New

Bug description:
  Start parole - get blank 'grey' screen.

  (also apparent with version in https://launchpad.net/~xubuntu-
  dev/+archive/ubuntu/ppa/?field.series_filter=wily -currently
  0.8.0+git-0~898~ubuntu15.10.1 )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: parole 0.8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun  5 17:38:06 2015
  InstallationDate: Installed on 2015-05-12 (23 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512)
  SourcePackage: parole
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

lightdm.log after nvidia install

** Attachment added: "1ldm.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458488/+files/1ldm.log

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

An Xorg crash report is generated, not sure of value, goes to the Db
anyway

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1487168] Re: [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider problem

[Raymond]

you have to specify component audio in your ticket


https://www.virtualbox.org/report/27?sort=version=0=1

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

Title:
  [Emulated AD1980 AC97 inside Virualbox 5.0, playback] volume slider
  problem

Status in Virtualbox:
  New
Status in alsa-driver package in Ubuntu:
  Incomplete
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  Volume Slider is only controlling PCM channel and is not controlling
  Master. In effect, Master is restricting the audio level to the
  default of approximately 45 Percent. In order to raise the Master
  Volume Level, alsamixer is capable of changing Master. Without
  manually raising Master to Max Volume, Volume Slider can only control
  volume from 0-45% which is the default level of Master.

  Description:  Ubuntu Wily Werewolf (development branch)
  Release:  15.10

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gene   1330 F pulseaudio
gene   1922 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Aug 20 13:00:57 2015
  InstallationDate: Installed on 2015-08-19 (1 days ago)
  InstallationMedia: Edubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_Type: Volume slider, or mixer problems
  Title: [ICH - Intel 82801AA-ICH, playback] volume slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Johan Potgieter]

I need to add that I have the latest versions of both libimobiledevice4
and libimobiledevice-utils and I still get this error. I dont get any
errors when connecting to any other wifi router or via ethernet cable.
Any suggestions would be appreciated.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1492835] [NEW] Changing line width of a shape crashes Impress

[Malte S. Stretz]

Public bug reported:

I'm using LibreOffice Impress v5.0.1.2 from the libreoffice-5-0 PPA on
Kubuntu 14.04 (ie. 1:5.0.1~rc2-0ubuntu1~trusty1).

I can reproducibly crash it by

1. Create a new presentation
2. Drawing a shape like an ellipse
3. In the Properties pane, open the Line Width drop down and select another 
width
4. LibreOffice closes without any message

It looks like opening and closing the drop down is enough.

I couldn't find any backtraces or drop downs anywhere. Please advise how
to collect and add any useful data.

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


** Tags: ppa

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

Title:
  Changing line width of a shape crashes Impress

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm using LibreOffice Impress v5.0.1.2 from the libreoffice-5-0 PPA on
  Kubuntu 14.04 (ie. 1:5.0.1~rc2-0ubuntu1~trusty1).

  I can reproducibly crash it by

  1. Create a new presentation
  2. Drawing a shape like an ellipse
  3. In the Properties pane, open the Line Width drop down and select another 
width
  4. LibreOffice closes without any message

  It looks like opening and closing the drop down is enough.

  I couldn't find any backtraces or drop downs anywhere. Please advise
  how to collect and add any useful data.

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

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

[Desktop-packages] [Bug 1484587] Re: CPU frequency management fails to re-engage on resume from suspend

[Doug Smythies]

When a user is using the intel_pstate driver in performance mode, then
yes, prior to Kernel 4.2RC1 the CPU frequency will be typically be stuck
after resume from suspend.

This is not a pm-ultils issue (which is how I stumbled across this bug
report).

To test that the issue is fixed on kernel 4.2, just use primitive
commands and not these higher level utilities (that I neither use or
know anything about). For example use:

grep MHz /proc/cpuinfo

to observe CPU frequencies.

The commit that, I think, fixes this issue is:

commit 6c1e45917dec5e7c99ba8125fd8cc50f6e482a21
Author: Doug Smythies 
Date:   Mon Jun 1 21:12:34 2015 -0700

intel_pstate: Force setting target pstate when required

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

Title:
  CPU frequency management fails to re-engage on resume from suspend

Status in linux package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Behavior:

  CPU frequency management fails to re-engage on resume from suspend. On
  resume, the CPUs are stuck around a single frequency (usually a low
  idle frequency).

  I use indicator-cpufreq for manual governor control. On resume,
  indicator-cpufreq indicates the low frequency state in its live cpu
  performance display in the icon. However, in its governor menu, it
  still shows as in use whichever governor was selected before suspend,
  even though that governor is not actually or properly controlling the
  CPU state.

  Upon manually switching to the unused governor in indicator-cpufreq,
  this behavior resolves, and the newly-chosen governor begins
  performing its duties. I can then immediately switch back to the
  desired (pre-suspend) governor with no issues.

  PM logs appear to show a successful resume of cpu frequency
  management, even though the modules did not actually gain effective
  control of the processor frequencies.

  
  Expected behavior:

  On resume, the CPU frequencies should continue being managed as they
  were before suspend without the need for manual user input.  Also, in
  the event that they do not, an error/warning should appear -- if not
  to the user, then in the pm suspend/resume logs.

  
  Other information that may or may not be relevant:

  On this system, the "powersave" governor is always automatically
  chosen at startup, although not until a minute or so after session
  login. The choice of an alternate governor "performance" from
  indicator-cpufreq is not persistent across reboots. Further, if I
  manually toggle the governors at the beginning of my first session
  after boot, and I settle on "performance", some automated script will
  force it back to "powersave" at the usual time about a minute after
  login. To use the "performance" governor, I must select it after
  waiting an interval following login, and I must always switch to
  powersave and back to performance after each resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   3887 F pulseaudio
   /dev/snd/controlC1:  adam   3887 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 13 11:41:27 2015
  InstallationDate: Installed on 2014-08-10 (368 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: 

[Desktop-packages] [Bug 1456531] Re: LightDM (?) blank/white screen after resume from suspend

[Robert Ancell]

** Package changed: lightdm (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)

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

Title:
  LightDM (?) blank/white screen after resume from suspend

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

Bug description:
  On Xubuntu 15.04, when I suspend the machine and resume afterwards,
  the screen remains completely white/blank. I can move the mouse
  cursor, but I don't see any screen elements. Clicking or wildly
  pressing keys doesn't do anything.

  I can switch to a different console with Ctrl+Alt+F1 and log in, just
  fine.

  For this bug report, I have removed all files from /var/log/lightdm,
  then rebooted, suspended, resumed, and switched to VT1. Then copied
  the /var/log/lightdm files to a different location. See their contents
  attached to this bug report.

  Other parameters:

  - Simply locking and unlocking the screen works, ALTHOUGH I also see
  the white screen there at first, and have to click a mouse button for
  the login form to show up.

  - I'm running a system with a fully encrypted hard-drive and have
  configured LightDM to log me in automatically.

  - System is up-to-date.

  - No experimental packages, although I had an experimental version of
  xserver-xorg-video-intel running, but removed it shortly after.

  - System is a Thinkpad T450s with Intel HD 5500 graphics.

  Hope I didn't forget to mention anything important. If you need more
  information or want me to try something, let me know.

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

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

[Desktop-packages] [Bug 1401646] Re: Shortcuts bug ( When press the "Ctrl + Alt", window Minimized )

[Salehi]

The reboot doesn't solve it to me, I solve it by removing config files
in home directory, in other words, I do this:

$ ls -a | egrep -e '^\.' | xargs -i{} sudo rm -rf '{}'

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

Title:
  Shortcuts bug ( When press the "Ctrl + Alt", window Minimized )

Status in gsettings-desktop-schemas package in Ubuntu:
  Confirmed

Bug description:
  When I press the Ctrl+Alt, The window minimized! I changed the shortcut key 
from "Ctrl+Alt+0" to "Shift+Alt+g" and then, I deal with maximize behavior when 
"Ctrl+Alt" pressed. I try with this command : 
  $ gsettings reset-recursively org.gnome.desktop.wm.keybindings
  But nothing has been changed.
  The attached file is the output of following coammand : 
  $ gsettings list-recursively | grep org.gnome.desktop.wm.keybindings 
1>/tmp/Seveas
  The filename inspired from "Seveas" nickname in the #ubuntu IRC channel, 
Since He/She helped me to overcome this problem :)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gsettings-desktop-schemas 3.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec 11 22:52:05 2014
  InstallationDate: Installed on 2014-10-23 (49 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1401646/+subscriptions

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

[Desktop-packages] [Bug 1491071] Re: Xmir doesn't update the screen size until something is actually rendered

[Robert Ancell]

Yeah, it makes sense to me to just call xmir_output_handle_resize after
getting the mir_event_type_resize. I think we could definitely drop the
damage call as well - this will be done inside xmir_output_handle_resize
anyway.

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

Title:
  Xmir doesn't update the screen size until something is actually
  rendered

Status in xorg-server package in Ubuntu:
  New

Bug description:
  In trying to get Compiz working under Xmir in Unity 8 desktop mode, I
  have found that when a Mir window opens and then resizes to whatever
  Unity 8 tells it to, the resize event does not get propagated down
  until another resize event occurs.

  For example, I start up an X app.  The Xmir window opens and is
  resized, but internally, Xmir still reports the full screen size so
  when Compiz starts, it thinks the surface size is the size of the
  physical display.

  I'll include a patch that fixes this and we can discuss if it's a good
  fix.

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

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

[Desktop-packages] [Bug 1322751] Re: Compiz running on Intel Haswell GPU has 100% CPU usage when computer is locked

[Philipp]

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

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

Title:
  Compiz running on Intel Haswell GPU has 100% CPU usage when computer
  is locked

Status in Compiz:
  New
Status in compiz package in Ubuntu:
  Confirmed

Bug description:
  I have Ubuntu 14.04 installed on a Lenovo X1 Carbon series 2. Whenever
  I lock my screen, compiz's CPU usage goes through the roof and it
  causes the CPU fan to spin up to max speed. I SSH'ed into the machine
  while it was locked to verify that it was indeed the compiz process
  causing the high cpu usage. When I unlock my computer, everything goes
  back to normal.

  I've looked at
  https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/969860, which
  seems related but that is for fglrx. This laptop has an Intel Haswell
  gpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 23 14:01:48 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2218]
  InstallationDate: Installed on 2014-05-15 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20A8S0UU00
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=3bc1f0cb-5a0d-45e6-a19a-ba71b7bc4c84 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GRET36WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20A8S0UU00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 Pro
  dmi.chassis.asset.tag: CS064833
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGRET36WW(1.13):bd03/26/2014:svnLENOVO:pn20A8S0UU00:pvrThinkPadX1Carbon2nd:rvnLENOVO:rn20A8S0UU00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20A8S0UU00
  dmi.product.version: ThinkPad X1 Carbon 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri May 23 10:55:01 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   61457 
   vendor DEL
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1492864] Re: Fails to load nvidia, fails to fallback to intel properly

[Doug McMahon]

Xorg.0 .log after nvidia install

** Attachment added: "1xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458487/+files/1xorg.log

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

Title:
  Fails to load nvidia, fails to fallback to intel properly

Status in nvidia-prime package in Ubuntu:
  New

Bug description:
  Fresh install of 15.10, image of 09/06, only synaptic installed 
  Hardware is  i7-4700MQ CPU, Intel® Haswell Mobile Nvidia GT770m

  Initial bootup/ login is fine
  Installed nvidia-352, install went fine, will attach log
  Rebooted to a black greeter screen (heard sound
  Logged in blindly, black screen

  rebooted, at black greeter screen went to tty, purged nvidia*, rebooted.
  Result was a login with no compiz, no unity as the OpenGl plugin was not 
loaded nor from some further tests could be.
  The only way forward was to remove ~/.config/dconf/user from a tty, then 
reboot

  Same machine runs nvidia driver via nvidia-prime fine in 14.04.3 &
  15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nvidia-prime 0.8.1
  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
  CurrentDesktop: Unity
  Date: Sun Sep  6 20:04:35 2015
  InstallationDate: Installed on 2015-09-06 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150906)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1462445] Re: Gtk applications start with blank screen (Clutter 1.22.4 and GtkClutter 1.6.2)

[Launchpad Bug Tracker]

This bug was fixed in the package xubuntu-default-settings - 15.10.3

---
xubuntu-default-settings (15.10.3) wily; urgency=medium

  * etc/X11/Xsession.d/56xubuntu-session
- Workaround clutter freezing gtk applications (LP: #1462445)
  * etc/xdg/xdg-xubuntu/xfce4/xfconf/xfce-perchannel-xml/parole.xml
- Set parole video sink back to clutter

 -- Sean Davis   Sun, 06 Sep 2015 19:30:35
-0400

** Changed in: xubuntu-default-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  Gtk applications start with blank screen (Clutter 1.22.4 and
  GtkClutter 1.6.2)

Status in Clutter:
  Confirmed
Status in Mugshot:
  New
Status in parole:
  Confirmed
Status in clutter-1.0 package in Ubuntu:
  Confirmed
Status in parole package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Fix Released

Bug description:
  Start parole - get blank 'grey' screen.

  (also apparent with version in https://launchpad.net/~xubuntu-
  dev/+archive/ubuntu/ppa/?field.series_filter=wily -currently
  0.8.0+git-0~898~ubuntu15.10.1 )

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: parole 0.8.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jun  5 17:38:06 2015
  InstallationDate: Installed on 2015-05-12 (23 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512)
  SourcePackage: parole
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492880] [NEW] Xorg crash

[ZhiFeng Hu]

Public bug reported:

[11872.120997] VBoxCrWinCmd[2174]: segfault at 41a2cc20 ip
7fe1c4a8fc7d sp 7fe18293fd30 error 4 in
libc-2.21.so[7fe1c4a56000+1c]


The libc-2.21.so may lead segfault

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
BootLog:
 fsck from util-linux 2.26.2
 /dev/sda1: clean, 954881/60022784 files, 25065933/240077824 blocks
CompizPlugins:
 (gconftool-2:12594): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
 Failed to connect to socket /tmp/dbus-pzcMAEBrj6: 拒绝连接
 获取“/apps/compiz-1/general/screen0/options/active_plugins”的值失败：D-BUS 守护进程没有运行
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Sep  7 11:41:40 2015
DistUpgraded: 2015-08-27 08:58:25,861 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.2, 4.1.6-040106-generic, x86_64: installed
 vboxhost, 5.0.2, 4.2.0-7-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca]
InstallationDate: Installed on 2015-07-14 (54 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
JournalErrors:
 No journal files were found.
 -- No entries --
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=6a047965-f164-44ef-95be-055aa21d3eb9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UdevLog: Error: [Errno 2] 没有那个文件或目录: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-08-27 (11 days ago)
dmi.bios.date: 08/23/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LK
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.:bvr1104:bd08/23/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK: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.1+15.10.20150805-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64+git20150829.508a5f77-0ubuntu0ricotz
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.5~git20150829+10.6.fa342251-0ubuntu0ricotz
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.5~git20150829+10.6.fa342251-0ubuntu0ricotz
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5
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.99+git20150521.d64a13eb-0ubuntu0ricotz
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150826.300319e2-0ubuntu0sarvatt
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20150804.62961456-0ubuntu0sarvatt
xserver.bootTime: Mon Sep  7 11:39:34 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu5

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


** Tags: amd64 apport-bug compiz-0.9 crash third-party-packages ubuntu wily

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [11872.120997] VBoxCrWinCmd[2174]: segfault at 41a2cc20 ip
  7fe1c4a8fc7d sp 7fe18293fd30 error 4 in
  libc-2.21.so[7fe1c4a56000+1c]


  The libc-2.21.so may lead segfault

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda1: clean, 954881/60022784 files, 25065933/240077824 blocks
  CompizPlugins:
   (gconftool-2:12594): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Failed to connect to socket /tmp/dbus-pzcMAEBrj6: 拒绝连接
   获取“/apps/compiz-1/general/screen0/options/active_plugins”的值失败：D-BUS 守护进程没有运行
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  

[Desktop-packages] [Bug 1492568] Re: Add new locale en_ID (Indonesian English)

[Martin Pitt]

Note that this kind of combinatorial inflation should usually not be
added to locales. You can set independent locales for the language and
the region to use in the control panel. E. g. you could choose en_GB or
en_US (depending on the preference) for the language, and id_ID for the
region (date/time, money, paper size, etc.).

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

Title:
  Add new locale en_ID (Indonesian English)

Status in langpack-locales package in Ubuntu:
  Incomplete

Bug description:
  Please see attached submission for a new locale for Indonesian English
  (en_ID).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1492568/+subscriptions

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

[Desktop-packages] [Bug 1489696] Re: black screen when enabling rotation on a gpu screen

[Launchpad Bug Tracker]

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

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

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

Title:
  black screen when enabling rotation on a gpu screen

Status in HWE Next:
  In Progress
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-vivid package in Ubuntu:
  Invalid
Status in xorg-server source package in Vivid:
  Confirmed
Status in xorg-server-lts-vivid source package in Vivid:
  Confirmed

Bug description:
  Running with the proprietary nvidia drivers in an optimus config
  works, but enabling reflection or rotation on the intel screen causes
  a black screen to appear.

  [Impact]
   * Causes a black screen if rotation or reflection is enabled.

  [Test Case]
   * Run xrandr --output SOMEOUTPUT --rotation left
  - Expected: Screen should rotate, or the call should fail.
  - Bad behavior: Succeeds, but causes a black screen.

  [Regression Potential]
   * The affected codepaths have reflection and rotation disabled for gpu 
screens. Another fix could be fixing reflection/rotation, but that will be more 
involved and likely require driver fixes.

  [Other Info]
   * This issue is copied from 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1308515 for vivid 
and wily.

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

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

[Desktop-packages] [Bug 1333158] Re: scaling doesn't affect firefox and thunderbird

[rubo77]

A workaround as mentioned further up here in
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1333158/comments/2

see http://askubuntu.com/a/487033/34298

manually open a new tab about:config in Firefox and search for
layout.css.devPixelsPerPx set this value to 2 or 1.5 as you wish to
adjust the size of the icons

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

Title:
  scaling doesn't affect firefox and thunderbird

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Fix Released
Status in ubufox package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  If you use "Scale for menu and title bars" in the Displays Tab, this
  doesn't affect Firefox.

  please add this to the Unity Desktop Integration:

  about:config in Firefox and search for 
  layout.css.devPixelsPerPx
  set this value to the same scale factor as in unity-control-center

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

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

[Desktop-packages] [Bug 1487553] Re: Compiz freezes entire desktop on Wily

[Fabio Marconi]

Hallo Carla
Today is released a new kernel, please do the upgrade and let's see if it fix.
Is this Wily a fresh installation or an upgrade ?
If it is an upgrade can you try starting an older working kernel ?
If it is a fresh installation would you like to test the latest release of the 
kernel from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/
You can also find suggestions for troubleshooting here:
https://wiki.ubuntu.com/X/Troubleshooting
Best regards

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

Title:
  Compiz freezes entire desktop on Wily

Status in compiz package in Ubuntu:
  New

Bug description:
  On Wily using Google calendar, Facebook Google+ and other Untity Web  Apps 
Compiz freezes the desktop, cannot do anything than reboot from termina 
(CTRL+ALT+F1).
  It also happened using Oracle VirtualBox, but not sure it was the real reason 
for the freeze. 
  My hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Aug 21 18:10:34 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.0, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx: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.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.63-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  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-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Aug 21 13:50:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUVC Camera (046d:081b) KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu3
  xserver.video_driver: nouveau
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu7
  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
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  Package: compiz 

[Desktop-packages] [Bug 1487553] Re: Compiz freezes entire desktop on Wily

[Fabio Marconi]

I read it is a fresh install, sorry:
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.0, 4.1.0-3-generic, x86_64: installed

GraphicsCard:
 NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation Device [10de:0491]

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

Title:
  Compiz freezes entire desktop on Wily

Status in compiz package in Ubuntu:
  New

Bug description:
  On Wily using Google calendar, Facebook Google+ and other Untity Web  Apps 
Compiz freezes the desktop, cannot do anything than reboot from termina 
(CTRL+ALT+F1).
  It also happened using Oracle VirtualBox, but not sure it was the real reason 
for the freeze. 
  My hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Aug 21 18:10:34 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.0, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx: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.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.63-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  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-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Aug 21 13:50:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUVC Camera (046d:081b) KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu3
  xserver.video_driver: nouveau
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu7
  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
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 

[Desktop-packages] [Bug 1492568] Re: Add new locale en_ID (Indonesian English)

[Gary Dean]

It is precisely this kind of combination that leads to all kinds of
inconsistency across systems within the country, or worse, users
defaulting to whatever English the machine was set up for and using
oddball date and time formats, and using inappropriate currency and
decimal setups, leading to confusion.

There is no satisfactory combination of existing locales (eg, en_US
language with id_ID region) that accommodate English language and region
settings.  In the case of decimals, for example, the convention in
Indonesian English is to use periods and not commas, as is the standard
for Indonesian language.

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

Title:
  Add new locale en_ID (Indonesian English)

Status in langpack-locales package in Ubuntu:
  Incomplete

Bug description:
  Please see attached submission for a new locale for Indonesian English
  (en_ID).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1492568/+subscriptions

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

[Desktop-packages] [Bug 1492689] [NEW] blank screen

[SANTHOSH NARAYANAN]

Public bug reported:

all my plugins went off unexpectedly and the screen is blank.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
Uname: Linux 3.16.0-44-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Sep  6 12:45:36 2015
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: fglrx-core, 14.201, 3.16.0-44-generic, i686: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 18) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2015-04-18 (140 days ago)
InstallationMedia: It
MachineType: Gigabyte Technology Co., Ltd. H55M-S2V
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=3e3b6c34-aee8-415b-8813-2fe179a3f405 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: H55M-S2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd09/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2V:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2V:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H55M-S2V
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Sun Sep  6 12:15:43 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPixArt MO1 USB Optical Mouse MOUSE, id 8
 inputPlus More Enterprise LTD. USB-compliant keyboard KEYBOARD, id 9
 inputPlus More Enterprise LTD. USB-compliant keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1420 
 vendor SAM
xserver.version: 2:1.16.0-1ubuntu1.3

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


** Tags: apport-bug compiz-0.9 i386 ubuntu utopic

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

Title:
  blank screen

Status in xorg package in Ubuntu:
  New

Bug description:
  all my plugins went off unexpectedly and the screen is blank.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep  6 12:45:36 2015
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 14.201, 3.16.0-44-generic, i686: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2015-04-18 (140 days ago)
  InstallationMedia: It
  MachineType: Gigabyte Technology Co., Ltd. H55M-S2V
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=3e3b6c34-aee8-415b-8813-2fe179a3f405 ro quiet splash vt.handoff=7
  SourcePackage: 

[Desktop-packages] [Bug 1489696] Re: black screen when enabling rotation on a gpu screen

[Launchpad Bug Tracker]

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

** Changed in: xorg-server-lts-vivid (Ubuntu Vivid)
   Status: New => Confirmed

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

Title:
  black screen when enabling rotation on a gpu screen

Status in HWE Next:
  In Progress
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server-lts-vivid package in Ubuntu:
  Invalid
Status in xorg-server source package in Vivid:
  Confirmed
Status in xorg-server-lts-vivid source package in Vivid:
  Confirmed

Bug description:
  Running with the proprietary nvidia drivers in an optimus config
  works, but enabling reflection or rotation on the intel screen causes
  a black screen to appear.

  [Impact]
   * Causes a black screen if rotation or reflection is enabled.

  [Test Case]
   * Run xrandr --output SOMEOUTPUT --rotation left
  - Expected: Screen should rotate, or the call should fail.
  - Bad behavior: Succeeds, but causes a black screen.

  [Regression Potential]
   * The affected codepaths have reflection and rotation disabled for gpu 
screens. Another fix could be fixing reflection/rotation, but that will be more 
involved and likely require driver fixes.

  [Other Info]
   * This issue is copied from 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1308515 for vivid 
and wily.

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

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

[Desktop-packages] [Bug 1454473] Re: In Ubuntu 15.04, simply moving the mouse via touchpad scrolls the window

[Jose Vacas]

** Also affects: xserver-xorg-input-synaptics
   Importance: Undecided
   Status: New

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

Title:
  In Ubuntu 15.04, simply moving the mouse via touchpad scrolls the
  window

Status in Xserver Xorg Input Synaptics:
  New
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Version: Ubuntu 3.19.0-16.16-generic 3.19.3

  (This is mostly a copy paste from here:
  http://askubuntu.com/questions/617117/in-ubuntu-15-04-simply-moving-
  the-mouse-via-touchpad-scrolls-the-window)

  When I first boot everything works fine. But then something happens
  (not sure what triggers it) and many programs start scrolling just by
  moving the mouse over the window. So far I see this happens in
  Nautilus, Document Reader, Archive Manager, Ubuntu Software Center,
  Meld, and System Monitor (what do they all have in common, GTK?). It
  does NOT happen in web browsers, thunderbird, programs using Mono,
  Java, etc, for some reason.

  To be more specific of the issue: if the mouse starting position is
  over a document in Document Reader, for example, and then I move the
  mouse via touchpad, it'll scroll the document like an anchor, where
  the position of the mouse over the document doesn't change (yet it
  scrolls). I have already tried disabling "two finger scroll", "disable
  while typing", and the "tap to click" options, but they made no
  difference (after the glitchiness starts).

  The other odd case is that in Nautilus, if the mouse starting position
  is over a file or directory, it sometimes selects it instead of
  scrolling. Single-clicking a directory will open the directory (so the
  initial touch acts like a clicks, and letting go acts as the second
  click).

  The only thing I can do to temporarily fix the problem is restart the
  computer. There are no issues when using a mouse.

  Update 2015/05/03: I see how to reproduce it now. It appears to be a
  glitchy two-finger scroll issue. If you scroll any window with two
  fingers a lot, eventually it'll start causing this problem. Try
  various actions with two fingers, like "clicking" with two fingers, or
  scrolling in various directions quickly, etc, and it will start
  happening. It's interesting that it only happens in certain programs
  and not in others, which makes me wonder whether it is really a
  trackpad issue or some framework's issue. I can confirm that this is
  happening on the 15.04 Live CD, so this happens out of the box.

  The only work-around for this issue is to disable two-finger scroll
  (if it's already glitchy you'll need to restart). Not sure if it
  matters, but I'm using the Dell XPS 13 2015 9343.

  Update 2015/05/05: Apparently this bug can still happen even with two-
  finger scroll off, though it's more rare. Again, only certain programs
  have the issue, so it's hard to tell if it's a touchpad issue or
  something else.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-16-generic 3.19.0-16.16
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ephi   1857 F pulseaudio
   /dev/snd/controlC0:  ephi   1857 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 12 22:06:46 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=270ecec3-b78c-4f85-a337-acd54f5e0b0e
  InstallationDate: Installed on 2015-05-01 (12 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 0a5c:216f Broadcom Corp.
   Bus 001 Device 010: ID 1d57:ac01 Xenta Wireless Receiver (Keyboard and Mouse)
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic.efi.signed 
root=UUID=2bf488f3-23aa-4837-8f4d-861be61c94bc ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Desktop-packages] [Bug 1492698] Re: Windows Phone cannot acess phone via MTP

[mati piela]

Added syslog

** Attachment added: "fragment of syslog"
   
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1492698/+attachment/4458180/+files/fragment%20of%20syslog

** Summary changed:

- Windows Phone cannot acess phone via MTP
+ Windows Phone cannot access phone via MTP

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

Title:
  Windows Phone cannot access phone via MTP

Status in libmtp package in Ubuntu:
  New

Bug description:
  Im have two smartphones with windows phone if im connect one smartphone to 
computer and open nautilus i can't access files and view 
  lsusb
  Bus 002 Device 005: ID 0421:06fc Nokia Mobile Phones

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

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

[Desktop-packages] [Bug 1492698] [NEW] Windows Phone cannot access phone via MTP

[mati piela]

Public bug reported:

Im have two smartphones with windows phone if im connect one smartphone to 
computer and open nautilus i can't access files and view 
lsusb
Bus 002 Device 005: ID 0421:06fc Nokia Mobile Phones

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

** Attachment added: "Image nautilus"
   
https://bugs.launchpad.net/bugs/1492698/+attachment/4458179/+files/Zrzut%20ekranu%20z%202015-09-06%2010%3A38%3A55.png

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

Title:
  Windows Phone cannot access phone via MTP

Status in libmtp package in Ubuntu:
  New

Bug description:
  Im have two smartphones with windows phone if im connect one smartphone to 
computer and open nautilus i can't access files and view 
  lsusb
  Bus 002 Device 005: ID 0421:06fc Nokia Mobile Phones

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

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

[Desktop-packages] [Bug 1492682] Re: FGLRX (2:15.200-0ubuntu0.5) OpenGL context memory leak.

[Vidiot_X]

Some background information here.
http://forums.linuxmint.com/viewtopic.php?f=59=204330

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

Title:
  FGLRX  (2:15.200-0ubuntu0.5) OpenGL context memory leak.

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

Bug description:
  This issue is effecting Linux Mint 17.2 KDE Rafaela (Ubuntu 14.04 LTS)

  The 'fglrx' driver set  (2:15.200-0ubuntu0.5) appears to  have a
  memory leak issue when setting the 'Compositing type' in KDE to OpenGL
  2.0/3.1. It will slowly bleed memory until 'xorg' is using gigs of
  memory. This issue does 'not' appear when using the open source driver
  set xserver-xorg-video-ati

  I am unable to isolate the problem but it appears that opening  a
  OpenGL context is part of the issue.

  This also may be related to following 'confirmed' bug report.
  
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1442921?comments=all

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

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

[Desktop-packages] [Bug 1487553] Re: Compiz freezes entire desktop on Wily

[Fabio Marconi]

Also,if you are in accord, you can temporarily workaround the issue installing 
the propretary drivers via:
Software & Updates -> Additional Drivers
so we can be sure that is a nouveau problem.

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

Title:
  Compiz freezes entire desktop on Wily

Status in compiz package in Ubuntu:
  New

Bug description:
  On Wily using Google calendar, Facebook Google+ and other Untity Web  Apps 
Compiz freezes the desktop, cannot do anything than reboot from termina 
(CTRL+ALT+F1).
  It also happened using Oracle VirtualBox, but not sure it was the real reason 
for the freeze. 
  My hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Aug 21 18:10:34 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.0, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx: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.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.63-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  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-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Aug 21 13:50:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUVC Camera (046d:081b) KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu3
  xserver.video_driver: nouveau
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu7
  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
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Tags:  wily wily 

[Desktop-packages] [Bug 1492682] [NEW] FGLRX (2:15.200-0ubuntu0.5) OpenGL context memory leak.

[Vidiot_X]

Public bug reported:

This issue is effecting Linux Mint 17.2 KDE Rafaela (Ubuntu 14.04 LTS)

The 'fglrx' driver set  (2:15.200-0ubuntu0.5) appears to  have a memory
leak issue when setting the 'Compositing type' in KDE to OpenGL 2.0/3.1.
It will slowly bleed memory until 'xorg' is using gigs of memory. This
issue does 'not' appear when using the open source driver set xserver-
xorg-video-ati

I am unable to isolate the problem but it appears that opening  a OpenGL
context is part of the issue.

This also may be related to following 'confirmed' bug report.
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1442921?comments=all

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

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

Title:
  FGLRX  (2:15.200-0ubuntu0.5) OpenGL context memory leak.

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

Bug description:
  This issue is effecting Linux Mint 17.2 KDE Rafaela (Ubuntu 14.04 LTS)

  The 'fglrx' driver set  (2:15.200-0ubuntu0.5) appears to  have a
  memory leak issue when setting the 'Compositing type' in KDE to OpenGL
  2.0/3.1. It will slowly bleed memory until 'xorg' is using gigs of
  memory. This issue does 'not' appear when using the open source driver
  set xserver-xorg-video-ati

  I am unable to isolate the problem but it appears that opening  a
  OpenGL context is part of the issue.

  This also may be related to following 'confirmed' bug report.
  
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1442921?comments=all

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

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

[Desktop-packages] [Bug 1404468] Re: German neo2 keyboard layout: no ALT and SUPER keys

[vak]

Alt-Tab is still not working from time to time in Neo2 :(

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

Title:
  German neo2 keyboard layout: no ALT and SUPER keys

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  Affected version: Ubuntu 14.04.

  When switching to the Neo 2 keyboard layout, I cannot use the ALT or
  SUPER keys at all. To reproduce this bug, do the following:

  - In the keyboard system tray menu, select "Text Entry"
  - Click "+"
  - Select: "Germany (Neo 2)"
  - Close the "Text Entry" configuration
  - In the keyboard system tray menu, (temporarily) select "Germany (Neo 2)" as 
active layout.

  Now, shortcuts like +, +, ... are no longer
  working. The same goes for the shortcuts I tried with .

  Switching to Neo2 by "setxkbmap de neo" has the same result.

  For sake of completeness: There are other bug reports regarding Neo2,
  reporting that Layer4 (Mod4) is not working. In my case, Mod4 seems to
  be working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1404468/+subscriptions

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

[Desktop-packages] [Bug 1492767] [NEW] gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

[Mélodie]

Public bug reported:

Hello,

I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday, and
today, I updated the system (with the console, because other issues came
first which led me to do a filesystem check). Then I started Synaptic,
and oops! no GUI, only the borders of the window would show. Several
other programs were affected and would not start (Geany, text editor),
or show their content. After tests and research it appeared only GTK3
programs were affected. If using a theme with GTK2, or move the GTK
configuration out of the way, the programs would work.

The upgrade contained the following packages:
gir1.2-gdkpixbuf-2.0_2.30.7
libgdk-pixbuf2.0-0_2.30.7
libgdk-pixbuf2.0-common_2.30.7

I fixed the issue by booting to the Live USB I had used to install, and
repackage the programs with dpkg-repack, then reinstalled them using
"sudo dpkg -i *.deb". (copied from the live usb to the home in the
install, rebooted and reinstalled there).

Problem solved for this install, where I have for now blocked the update
for these three packages.

At post-install, after I had updated, I had the same message as the people who 
reported that bug:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294


(gtk-update-icon-cache-3.0:29671): 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.


and when trying to do so, the console returned a message stating gdk-
pixbuf-query-loaders was not installed. (no such package in the repos
either).

More information can be found at
http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html

where I discussed about this bug and my findings.

Now I will try to produce this bug again in the Live USB (which has no
persistence).

Best regards,
Mélodie

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gdkpixbuf

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

Title:
  gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Hello,

  I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday, and
  today, I updated the system (with the console, because other issues
  came first which led me to do a filesystem check). Then I started
  Synaptic, and oops! no GUI, only the borders of the window would show.
  Several other programs were affected and would not start (Geany, text
  editor), or show their content. After tests and research it appeared
  only GTK3 programs were affected. If using a theme with GTK2, or move
  the GTK configuration out of the way, the programs would work.

  The upgrade contained the following packages:
  gir1.2-gdkpixbuf-2.0_2.30.7
  libgdk-pixbuf2.0-0_2.30.7
  libgdk-pixbuf2.0-common_2.30.7

  I fixed the issue by booting to the Live USB I had used to install,
  and repackage the programs with dpkg-repack, then reinstalled them
  using "sudo dpkg -i *.deb". (copied from the live usb to the home in
  the install, rebooted and reinstalled there).

  Problem solved for this install, where I have for now blocked the
  update for these three packages.

  At post-install, after I had updated, I had the same message as the people 
who reported that bug:
  https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294

  
  (gtk-update-icon-cache-3.0:29671): 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.
  

  and when trying to do so, the console returned a message stating gdk-
  pixbuf-query-loaders was not installed. (no such package in the repos
  either).

  More information can be found at
  http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html

  where I discussed about this bug and my findings.

  Now I will try to produce this bug again in the Live USB (which has no
  persistence).

  Best regards,
  Mélodie

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1492767/+subscriptions

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

[Desktop-packages] [Bug 1463598] Re: Chromium 43 fails to use hardware acceleration

[Florian W.]

Hi,

I'm just wondering if WebGL is still disabled in 14.04, even though we
are on chromium 44 now? I wanted to enable WebGL just to see if I could
watch 360° Youtube vids then, and now noticed that it no longer works at
all, apparently due to this Ubuntu change.

I realize that lots of crashes are GPU-related, but IMHO ripping that
feature out of chromium completely is bad, as most chromium GPU features
are blacklisted (by Google) on my AMD system anyway because they tend to
cause problems. If it's too much of an issue, maybe GPU stuff could be
blacklisted for all drivers, and those who would like to use WebGL etc.
could manually override the blacklist in about:flags? That's what I have
done repeatedly in the past, although I'm well aware that any strange
behaviour could be related to disabling the blacklist.

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

Title:
  Chromium 43 fails to use hardware acceleration

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  After installing package chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 
hardware acceleration becomes disabled.
  I had no problem with previous chromium version.

  Console output:

  $ chromium-browser
  [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed 
to launch GPU process.
  [3150:3150:0609/190556:ERROR:url_pattern_set.cc(240)] Invalid url pattern: 
chrome://print/*
  [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed 
to launch GPU process.
  [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed 
to launch GPU process.

  chrome://gpu:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only, hardware acceleration unavailable
  Flash Stage3D: Software only, hardware acceleration unavailable
  Flash Stage3D Baseline profile: Software only, hardware acceleration 
unavailable
  Compositing: Software only, hardware acceleration unavailable
  Multiple Raster Threads: Unavailable
  Rasterization: Software only, hardware acceleration unavailable
  Threaded Rasterization: Unavailable
  Video Decode: Software only, hardware acceleration unavailable
  Video Encode: Software only, hardware acceleration unavailable
  WebGL: Unavailable

  Driver Bug Workarounds
  clear_uniforms_before_first_program_use
  count_all_in_varyings_packing
  disable_chromium_framebuffer_multisample
  disable_ext_occlusion_query
  disable_post_sub_buffers_for_onscreen_surfaces
  scalarize_vec_and_mat_constructor_args

  Problems Detected
  GPU process was unable to boot: GPU access is disabled in chrome://settings.
  Disabled Features: all

  - - -
  Actually GPU access is *not* disabled from settings.

  Workarounds like "--disable-gpu-sandbox" or "LIBGL_DRI3_DISABLE=1"
  didn't helped at all.

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

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

[Desktop-packages] [Bug 1492766] [NEW] nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to build

[Luis_Serrano]

Public bug reported:

Found when upgrading to kernel 4.2 in ubuntu  gnome 14.04.

Installed following these instructions:

$ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
headers-4.2.0-040200_4.2.0-040200.201508301530_all.deb

$ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
headers-4.2.0-040200-lowlatency_4.2.0-040200.201508301530_amd64.deb

$ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
image-4.2.0-040200-lowlatency_4.2.0-040200.201508301530_amd64.deb.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-304 304.125-0ubuntu0.0.2
ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
Uname: Linux 3.13.0-62-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.12
Architecture: amd64
DKMSKernelVersion: 4.2.0-040200-lowlatency
Date: Sun Sep  6 09:23:26 2015
InstallationDate: Installed on 2010-05-29 (1926 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
PackageVersion: 304.125-0ubuntu0.0.2
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: nvidia-graphics-drivers-304
Title: nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to build
UpgradeStatus: Upgraded to trusty on 2014-05-08 (486 days ago)
modified.conffile..etc.modprobe.d.nvidia.304.hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to
  build

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

Bug description:
  Found when upgrading to kernel 4.2 in ubuntu  gnome 14.04.

  Installed following these instructions:

  $ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
  headers-4.2.0-040200_4.2.0-040200.201508301530_all.deb

  $ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
  headers-4.2.0-040200-lowlatency_4.2.0-040200.201508301530_amd64.deb

  $ wget -c kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/linux-
  image-4.2.0-040200-lowlatency_4.2.0-040200.201508301530_amd64.deb.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.125-0ubuntu0.0.2
  ProcVersionSignature: Ubuntu 3.13.0-62.102-generic 3.13.11-ckt24
  Uname: Linux 3.13.0-62-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  DKMSKernelVersion: 4.2.0-040200-lowlatency
  Date: Sun Sep  6 09:23:26 2015
  InstallationDate: Installed on 2010-05-29 (1926 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  PackageVersion: 304.125-0ubuntu0.0.2
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.125-0ubuntu0.0.2: nvidia-304 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2014-05-08 (486 days ago)
  modified.conffile..etc.modprobe.d.nvidia.304.hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1492767] Re: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

[Mélodie]

** Description changed:

  Hello,
  
- I did a fresh install with a Trusty 14.04.3 (x86_64) custom version
- yesterday, and today, I updated the system (with the console, because
- other issues came first which led me to do a filesystem check). Then I
- started Synaptic, and oops! no GUI, only the borders of the window would
- show. Several other programs were affected and would not start (Geany,
- text editor), or show their content. After tests and research it
- appeared only GTK3 programs were affected. If using a theme with GTK2,
- or move the GTK configuration out of the way, the programs would work.
+ I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday, and
+ today, I updated the system (with the console, because other issues came
+ first which led me to do a filesystem check). Then I started Synaptic,
+ and oops! no GUI, only the borders of the window would show. Several
+ other programs were affected and would not start (Geany, text editor),
+ or show their content. After tests and research it appeared only GTK3
+ programs were affected. If using a theme with GTK2, or move the GTK
+ configuration out of the way, the programs would work.
  
  The upgrade contained the following packages:
  gir1.2-gdkpixbuf-2.0_2.30.7
  libgdk-pixbuf2.0-0_2.30.7
  libgdk-pixbuf2.0-common_2.30.7
  
  I fixed the issue by booting to the Live USB I had used to install, and
  repackage the programs with dpkg-repack, then reinstalled them using
  "sudo dpkg -i *.deb". (copied from the live usb to the home in the
  install, rebooted and reinstalled there).
  
  Problem solved for this install, where I have for now blocked the update
  for these three packages.
  
  At post-install, after I had updated, I had the same message as the people 
who reported that bug:
  https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294
  
  
  (gtk-update-icon-cache-3.0:29671): 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
+   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.
  
  
  and when trying to do so, the console returned a message stating gdk-
  pixbuf-query-loaders was not installed. (no such package in the repos
  either).
  
- More information can be found at 
+ More information can be found at
  http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html
  
  where I discussed about this bug and my findings.
  
  Now I will try to produce this bug again in the Live USB (which has no
  persistence).
  
  Best regards,
  Mélodie

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

Title:
  gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Hello,

  I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday, and
  today, I updated the system (with the console, because other issues
  came first which led me to do a filesystem check). Then I started
  Synaptic, and oops! no GUI, only the borders of the window would show.
  Several other programs were affected and would not start (Geany, text
  editor), or show their content. After tests and research it appeared
  only GTK3 programs were affected. If using a theme with GTK2, or move
  the GTK configuration out of the way, the programs would work.

  The upgrade contained the following packages:
  gir1.2-gdkpixbuf-2.0_2.30.7
  libgdk-pixbuf2.0-0_2.30.7
  libgdk-pixbuf2.0-common_2.30.7

  I fixed the issue by booting to the Live USB I had used to install,
  and repackage the programs with dpkg-repack, then reinstalled them
  using "sudo dpkg -i *.deb". (copied from the live usb to the home in
  the install, rebooted and reinstalled there).

  Problem solved for this install, where I have for now blocked the
  update for these three packages.

  At post-install, after I had updated, I had the same message as the people 
who reported that bug:
  https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294

  
  (gtk-update-icon-cache-3.0:29671): 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.
  

  and when trying to do so, the console returned a message stating gdk-
  pixbuf-query-loaders was not installed. (no such package in the repos
  either).

  More 

[Desktop-packages] [Bug 1492737] [NEW] Sync google-glog 0.3.4-0.1 (main) from Debian unstable (main)

[Artur Rona]

Public bug reported:

Please sync google-glog 0.3.4-0.1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Rebuild with new gflags.
  * No change rebuild to get debug symbols on all architectures.
  * No change rebuild to get debug symbols on all architectures.

All changes have been forwarded to Debian by the same uploader.

Changelog entries since current wily version 0.3.4-0ubuntu2:

google-glog (0.3.4-0.1) unstable; urgency=medium

  * Non maintainer upload.
  * New upstream version.
  * Ignore test results (the demangler is not aware of the __cxx11 symbols
in GCC 5's libstdc++). See #792649.
  * Rename libgoogle-glog0 -> libgoogle-glog0v5, follow-up transition
for the libstdc++6 ABI changes.
  * Re-enable optimization. Closes: #749169.

 -- Matthias Klose   Tue, 11 Aug 2015 09:41:28 +0200

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

** Changed in: google-glog (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync google-glog 0.3.4-0.1 (main) from Debian unstable (main)

Status in google-glog package in Ubuntu:
  New

Bug description:
  Please sync google-glog 0.3.4-0.1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Rebuild with new gflags.
* No change rebuild to get debug symbols on all architectures.
* No change rebuild to get debug symbols on all architectures.

  All changes have been forwarded to Debian by the same uploader.

  Changelog entries since current wily version 0.3.4-0ubuntu2:

  google-glog (0.3.4-0.1) unstable; urgency=medium

* Non maintainer upload.
* New upstream version.
* Ignore test results (the demangler is not aware of the __cxx11 symbols
  in GCC 5's libstdc++). See #792649.
* Rename libgoogle-glog0 -> libgoogle-glog0v5, follow-up transition
  for the libstdc++6 ABI changes.
* Re-enable optimization. Closes: #749169.

   -- Matthias Klose   Tue, 11 Aug 2015 09:41:28 +0200

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

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

[Desktop-packages] [Bug 1492753] [NEW] Screen rotation broken in Wily

[Lee Donaghy]

Public bug reported:

Using a Radeon 280x (tahiti).

Rotation previously working in Vivid but not in Wily.
Arch is on xserver-xorg 1.17.2 and rotation is working so maybe a debian bug.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xserver-xorg 1:7.7+7ubuntu4
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
CurrentDesktop: KDE
Date: Sun Sep  6 13:02:16 2015
InstallationDate: Installed on 2015-09-03 (3 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

** Attachment added: "Monitor layout."
   
https://bugs.launchpad.net/bugs/1492753/+attachment/4458263/+files/10-monitor.conf

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

Title:
  Screen rotation broken in Wily

Status in xorg package in Ubuntu:
  New

Bug description:
  Using a Radeon 280x (tahiti).

  Rotation previously working in Vivid but not in Wily.
  Arch is on xserver-xorg 1.17.2 and rotation is working so maybe a debian bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  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
  CurrentDesktop: KDE
  Date: Sun Sep  6 13:02:16 2015
  InstallationDate: Installed on 2015-09-03 (3 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825.1)
  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/1492753/+subscriptions

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

[Desktop-packages] [Bug 1401207] Re: No 'Select-by-word characters' property

[Chris West]

To restore the pre-wily behaviour, you need to use dconf, as per:

https://bugzilla.gnome.org/show_bug.cgi?id=730632#c33

Note that the use of colons there is /crazy/.  Yes, there is :/: in
there.

1) edit -> profile preferences -> the General tab on your profile has its 
Profile ID, e.g. b1dcc9dd-5262-4d8d-a863-c897e6d979b9
2) check you've got the syntax right with:

$ dconf list 
/org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/
foreground-color
visible-name
palette
use-system-font
...

If it returns nothing, you've got it wrong; try again.

3) dconf write
/org/gnome/terminal/legacy/profiles:/:b1dcc9dd-5262-4d8d-a863-c897e6d979b9
/word-char-exceptions '@ms 

[Desktop-packages] [Bug 1325063] Re: Gedit preferences windows is empty

[Tianyu Liu]

For me, this is caused by disabling the plugin "Insert Date and Time".

Thanks to Jens, using "LD_PRELOAD=/usr/lib/libpeas-gtk-1.0.so.0 gedit"
to open Gedit and change Preference to re-enable the plugin solved the
problem.

[Ubuntu 14.04.3 & Gedit 3.12.2]

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

Title:
  Gedit preferences windows is empty

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  When I click the preferences item in menu I get a empty window that is
  just titled preferences. There is nothing in it and if I drag it to a
  bigger size an empty plane appears.

  When starting gedit as root I see the following error in terminal:

  (gedit:13564): Gtk-CRITICAL **: Error building template class
  'GeditPreferencesDialog' for an instance of type
  'GeditPreferencesDialog': Invalid object type `PeasGtkPluginManager'

  (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping:
  assertion 'G_IS_OBJECT (object)' failed

  (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping:
  assertion 'G_IS_OBJECT (object)' failed

  (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping:
  assertion 'G_IS_OBJECT (object)' failed

  ...

  UBUNTU 14.04, xsfc

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

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

[Desktop-packages] [Bug 1492745] [NEW] Xorg crash

[ZhiFeng Hu]

Public bug reported:

i am using ubuntu-bug to report crashes bug of xorg.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.18-0ubuntu9
Architecture: amd64
BootLog:
 Scanning for Btrfs filesystems
 fsck from util-linux 2.26.2
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: Sun Sep  6 19:35:55 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 vboxhost, 5.0.2, 4.1.0-3-generic, x86_64: installed
 vboxhost, 5.0.2, 4.2.0-7-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: QUANTA Computer Inc Device [152d:0873]
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: QUANTA Computer Inc Device [152d:0873]
InstallationDate: Installed on 2015-08-23 (13 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150624)
JournalErrors:
 No journal files were found.
 -- No entries --
MachineType: Hasee QTH6
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-7-generic 
root=UUID=e5cb5ea2-8a5c-4703-acaa-b43e9b7f9ab2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/16/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: SU272
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: HM65
dmi.board.vendor: Hasee
dmi.board.version: TBD
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hasee
dmi.chassis.version: US
dmi.modalias: 
dmi:bvnINSYDE:bvrSU272:bd12/16/2011:svnHasee:pnQTH6:pvr03:rvnHasee:rnHM65:rvrTBD:cvnHasee:ct10:cvrUS:
dmi.product.name: QTH6
dmi.product.version: 03
dmi.sys.vendor: Hasee
version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64+git20150829.508a5f77-0ubuntu0ricotz
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.6.5~git20150829+10.6.fa342251-0ubuntu0ricotz
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.6.5~git20150829+10.6.fa342251-0ubuntu0ricotz
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu5
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.99+git20150521.d64a13eb-0ubuntu0ricotz
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150826.300319e2-0ubuntu0sarvatt
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20150804.62961456-0ubuntu0sarvatt
xserver.bootTime: Sun Sep  6 19:32:26 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)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9964 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu5

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


** Tags: amd64 apport-bug compiz-0.9 crash third-party-packages ubuntu wily

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  i am using ubuntu-bug to report crashes bug of xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   fsck from util-linux 2.26.2
  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: Sun Sep  6 19:35:55 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 5.0.2, 4.1.0-3-generic, x86_64: installed
   vboxhost, 5.0.2, 4.2.0-7-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: QUANTA 

[Desktop-packages] [Bug 1292830] Re: Resuming from sleep makes black borders around windows to appear

[A.J. Ruckman]

This just started happening to me.

I've used Ubuntu 15.04 before, a few months ago, but decided to switch
to Windows. Now when I started using Ubuntu again this began for the
first time.

I'm on a laptop with a 765M, driver version 352.41.

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

Title:
  Resuming from sleep makes black borders around windows to appear

Status in Compiz:
  Confirmed
Status in compiz package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE 
  ***

  HOW TO REPRODUCE

  1. Go to sleep mode.
  2. Resume.

  EXPECTED BEHAVIOUR

  - The computer to resume normally.

  REAL BEHAVIOUR

  - Windows have black borders around them, as seen in the attached
  screen-shot.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION 
  **

  WORK-AROUND

  1. Press the "Ctrl+Alt+F2" key combination (Warning: you will be sent to a 
text console where you won't be able to read this document).
  2. Press "Ctrl+Alt+F7".

  FIX

  - Unspecified.

  REGRESSION POTENTIAL

  - Unspecified.

  
   TECHNICAL INFO 
  

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.gpus.0: Error: [Error 21] It Is a Directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.3-0ubuntu1
  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: Sat Mar 15 12:22:43 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA 
controller])
     Subsystem: Dell Device [1028:0493]
  MachineType: Dell Inc. Latitude E6420
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic 
root=UUID=3af29d5f-e00a-409b-9d57-1ad69dce69d9 ro splash quietSourcePackage: 
compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Mar 11 15:58:58 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.15.0-1ubuntu6

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

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

[Desktop-packages] [Bug 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background

[Andrea Lazzarotto (Lazza)]

I was encountering this bug after enabling the ReplayGain plug-in. I
disabled it and the problem seems to be solved.

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

Title:
  Banshee/Rhythmbox regularly stop playing audio when left on in the
  background

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio source package in Precise:
  Confirmed

Bug description:
  If Banshee or Rhythmbox is left playing in the background they will
  randomly stop playing in the latest builds of Ubuntu 12.04. Starting a
  new piece of music usually fixes the problem. If left to its own
  devices, the music will start playing again at some random time, at
  some random position. This problem exists on both my desktop machine
  (custom built Intel machine) and my laptop (Macbook 5,1). It has been
  happening for several months now.

  I became frustrated enough to load up pulseaudio in debugging mode.
  The log shows that when the music player just finishes playing one
  piece, and tries to start the next piece, you see something like this:

  ---
  ( 335.399|  34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to 
corking
  ( 335.400|   0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: before: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: after: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.400|   0.000) D: [alsa-sink] sink.c: latency = 1643
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on render memblockq.
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on implementor.
  ( 335.400|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.400|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0:  34% 1:  
34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 
dB 1: -28.11 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0:  34% 
1:  34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:   in dB: 0: 
-28.00 dB 1: -28.00 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:  in dB: 
0: -0.11 dB 1: -0.11 dB
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Volume not changing
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes.
  ( 335.402|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: before: 3825
  ( 335.402|   0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to 
vacuum.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: after: 3825
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes.
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.402|   0.000) D: [alsa-sink] sink.c: latency = 1402
  ( 335.402|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.402|   0.000) I: [pulseaudio] sink-input.c: Freeing input 3 
"'zero-project - 05 - Forest of the unicorns' by 'zero-project'"
  ( 335.402|   0.000) D: [pulseaudio] module-stream-restore.c: Not restoring 
device for stream sink-input-by-media-role:music, because already set to 
'alsa_output.pci-_00_1b.0.analog-stereo'.
  ( 335.403|   0.000) D: [pulseaudio] module-intended-roles.c: Not setting 
device for stream Playback Stream, because already set.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring volume 
for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) I: [pulseaudio] module-stream-restore.c: Restoring mute 
state for sink input sink-input-by-media-role:music.
  ( 335.403|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes busy.
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Forcing resampler 'copy', 
because of fixed, identical sample rates.
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Using resampler 'copy'
  ( 335.403|   0.000) I: [pulseaudio] resampler.c: Using float32le as working 
format.
  ( 335.403|   0.000) D: [pulseaudio] memblockq.c: memblockq requested: 
maxlength=33554432, 

[Desktop-packages] [Bug 1246908] Re: ~/.gimp-2.8 directory and everything inside is owned by root

[pabouk]

Try to rename the Gimp directory:

1. stop all the Gimp processes
2. sudo mv "$USER/.gimp-2.8" "$USER/.gimp-2.8-backup"
3. sudo mv ~root/.gimp-2.8 ~root/.gimp-2.8-backup

If after this operation everything works you can remove the
.gimp-2.8-backup directories.

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

Title:
  ~/.gimp-2.8 directory and everything inside is owned by root

Status in gimp package in Ubuntu:
  New

Bug description:
  The ~/.gimp-2.8 directory and everything inside it is owned by user
  root, group root. As a consequence the ordinary user does not have the
  adequate access rights to the personal Gimp files.

  Gimp shows the following messages during start:
  ---
  Failed to open file '/home/vbrozik/.gimp-2.8/controllerrc': open() failed: 
Permission denied

  Unable to open a test swap file.

  To avoid data loss, please check the location and permissions of the swap 
directory defined in your Preferences (currently "/home/vbrozik/.gimp-2.8").
  ---

  The system was installed as Xubuntu 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gimp 2.8.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Thu Oct 31 22:36:56 2013
  ExecutablePath: /usr/bin/gimp-2.8
  InstallationDate: Installed on 2013-09-28 (32 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130902.1)
  MarkForUpload: True
  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/1246908/+subscriptions

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

[Desktop-packages] [Bug 991872] Re: Doesn't notice quickly enough that new Wi-Fi network is available

[mati piela]

Me too 
Im have gnome ubuntu and here no refresh button in wifi select menu

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

Title:
  Doesn't notice quickly enough that new Wi-Fi network is available

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Use  Router
  wifi connect so it autoreconnects to it
  Turn off router..
  After few minutes when not showing that router
  then start router
  and comp doesnt sees router
  disable wifi and enable sometimes connects immidiatly
  this time it didnt immidiatly so im reporting

  In 12.04 it reconnects no matter if i press cancel connect or connect
  if cancel it trys again few minutes later
  in 10.04 it doesnt reconnect if i pressing cancel but connects if network 
works and i press connect but doesnt connect if network doesnt work i press 
connect after 4th time it tryd connecting after i pressed connect- it stops 
asking to connect and doesnt reconnect on getting signal back.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: network-manager 0.8-0ubuntu3.2
  ProcVersionSignature: Ubuntu 2.6.32-41.88-generic 2.6.32.59+drm33.24
  Uname: Linux 2.6.32-41-generic i686
  Architecture: i386
  Date: Mon Apr 30 13:52:26 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 
(20100429.4)
  IpRoute:
   192.168.43.0/24 dev wlan0  proto kernel  scope link  src 192.168.43.27  
metric 2
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   default via 192.168.43.1 dev wlan0  proto static
  Keyfiles: Error: [Errno 2] No such file or directory
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager

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

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

[Desktop-packages] [Bug 1491568] Re: nouveau and thunderbolt tv screen: a lot of glitches and black screen portion

[Le Gluon Du Net]

** Summary changed:

- nouveau and thunerbolt tv screen: a lot of glitches and black screen portion
+ nouveau and thunderbolt tv screen: a lot of glitches and black screen portion

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

Title:
  nouveau and thunderbolt tv screen: a lot of glitches and black screen
  portion

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Hello,

  if I connect my tv screen as a second screen to my Macbook pro, with a
  thunderbolt to hdmi connectic, I obtain a lot of glitches and some
  black screen portions.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep  2 21:45:00 2015
  DistUpgraded: 2015-08-23 23:41:34,547 DEBUG running apport_pkgfailure() 
modemmanager: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 100
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 12) (prog-if 00 [VGA controller])
   NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Apple Inc. Device [106b:00c7]
  InstallationDate: Installed on 2015-08-12 (20 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Apple Inc. MacBookPro6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=1a19efbe-e3c9-4f6a-b4df-f71113a5973b ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to wily on 2015-08-23 (9 days ago)
  dmi.bios.date: 12/09/11
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP61.88Z.0057.B0F.1112091028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F22586C8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro6,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F22586C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP61.88Z.0057.B0F.1112091028:bd12/09/11:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8:
  dmi.product.name: MacBookPro6,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  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-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Sep  2 21:14:33 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)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu3
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1492812] [NEW] package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Thom Fitzgibbon]

Public bug reported:

after the login screen comes up, ubuntu does not start.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-304 304.125-0ubuntu0.0.2
ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
Uname: Linux 3.13.0-63-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.13
Architecture: amd64
Date: Sun Sep  6 13:43:18 2015
DuplicateSignature: package:nvidia-304:304.125-0ubuntu0.0.2:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-07-19 (414 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: nvidia-graphics-drivers-304
Title: package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

Bug description:
  after the login screen comes up, ubuntu does not start.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.125-0ubuntu0.0.2
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Sun Sep  6 13:43:18 2015
  DuplicateSignature: package:nvidia-304:304.125-0ubuntu0.0.2:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-07-19 (414 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-304
  Title: package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1317994] Re: Rhythmbox doesn't sync mtp device correctly

[Bug Watch Updater]

** Changed in: rhythmbox
   Status: Confirmed => Invalid

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

Title:
  Rhythmbox doesn't sync mtp device correctly

Status in Rhythmbox:
  Invalid
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  I have a SONY player NWZ-E443. I also have a favourite playlist, which  I 
want to sync with the player.
  So there is the problem. When I syncing second, third and etc times, 
Rhythmbox deletes 56 files (I do not want why 56 yet) and copies them back.  My 
favourite playlist has 117 songs.

  mike@mike-laptop:~$  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  mike@mike-laptop:~$  apt-cache policy rhythmbox
  rhythmbox:
    Installed: 3.0.2-0ubuntu2
    Candidate:   3.0.2-0ubuntu2
    Table of versions
   *** 3.0.2-0ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   3.0.2-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

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

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

[Desktop-packages] [Bug 1492812] Re: package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

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

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1477575
   package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1

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

Title:
  package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

Bug description:
  after the login screen comes up, ubuntu does not start.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.125-0ubuntu0.0.2
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  Date: Sun Sep  6 13:43:18 2015
  DuplicateSignature: package:nvidia-304:304.125-0ubuntu0.0.2:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-07-19 (414 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-304
  Title: package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1477575] Re: package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.125-0ubuntu0.0.2
  ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-58-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Thu Jul 23 16:29:50 2015
  DuplicateSignature: package:nvidia-304:304.125-0ubuntu0.0.2:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-01-13 (190 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: nvidia-graphics-drivers-304
  Title: package nvidia-304 304.125-0ubuntu0.0.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1492815] [NEW] Black screen on switching users

[Wadelius]

Public bug reported:

I have an Asus UX303LN with Ubuntu 15.04. There are two user accounts,
one administrator and one that is not administrator.

When I switch between users the screen turns black, sometimes the windows the 
user has opened are flashed before it turns black. If I hold the laptop against 
a bright light I can see that the windows are there, but that the back-light is 
completely switched off. When I close the lid and open again, making the laptop 
going into suspend and back, the back-light is on. When coming back from 
suspend I'm greeted by the login screen, but while I write my password it goes 
into suspend again. Pressing space or closing and opening the lid brings up the 
login screen and I can successfully login
Summary:
- Log in user A
- Switch to user B
- Switch back to user A -> Windows that are open flash then black screen
- Close the lid and open again -> login screen
- While writing the password the laptop goes to suspend. Hitting space brings 
is up again.
- Attempt to login -> screen is not black.

I have also found that the user switched to is not critical, as long as the 
switch user screen has been triggered:
- Log in as user A
- Press the cogwheel in the upper right corner, select user B.
- When prompted with user Bs password, change your mind and switch to user A 
again.
- The same black screen behaviour as above.

So it seems that the culprit is something triggered by the switch user
screen, that differs from just locking one account and entering the
password to it.

This or similar issues have been reported before, as far back as 2010 it
seems. I have not found any solution by reading threads, it seems that
sometimes people get lucky and the issue disappears during an upgrade.

To get the touchpad and other stuff working I have as recommended in the 
following thread added a couple of PPAs.
Thread: http://ubuntuforums.org/showthread.php?t=2243162
PPAs:
http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu
http://ppa.launchpad.net/hanipouspilot/focaltech-dkms/ubuntu
Other PPAs to get applications I want:
http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu
http://repository.spotify.com
http://apt.insynchq.com/ubuntu
http://download.virtualbox.org/virtualbox/debian

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Black screen on switching users

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

Bug description:
  I have an Asus UX303LN with Ubuntu 15.04. There are two user accounts,
  one administrator and one that is not administrator.

  When I switch between users the screen turns black, sometimes the windows the 
user has opened are flashed before it turns black. If I hold the laptop against 
a bright light I can see that the windows are there, but that the back-light is 
completely switched off. When I close the lid and open again, making the laptop 
going into suspend and back, the back-light is on. When coming back from 
suspend I'm greeted by the login screen, but while I write my password it goes 
into suspend again. Pressing space or closing and opening the lid brings up the 
login screen and I can successfully login
  Summary:
  - Log in user A
  - Switch to user B
  - Switch back to user A -> Windows that are open flash then black screen
  - Close the lid and open again -> login screen
  - While writing the password the laptop goes to suspend. Hitting space brings 
is up again.
  - Attempt to login -> screen is not black.

  I have also found that the user switched to is not critical, as long as the 
switch user screen has been triggered:
  - Log in as user A
  - Press the cogwheel in the upper right corner, select user B.
  - When prompted with user Bs password, change your mind and switch to user A 
again.
  - The same black screen behaviour as above.

  So it seems that the culprit is something triggered by the switch user
  screen, that differs from just locking one account and entering the
  password to it.

  This or similar issues have been reported before, as far back as 2010
  it seems. I have not found any solution by reading threads, it seems
  that sometimes people get lucky and the issue disappears during an
  upgrade.

  To get the touchpad and other stuff working I have as recommended in the 
following thread added a couple of PPAs.
  Thread: http://ubuntuforums.org/showthread.php?t=2243162
  PPAs:
  http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu
  http://ppa.launchpad.net/hanipouspilot/focaltech-dkms/ubuntu
  Other PPAs to get applications I want:
  http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu
  http://repository.spotify.com
  http://apt.insynchq.com/ubuntu
  http://download.virtualbox.org/virtualbox/debian

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1492820] [NEW] unity greeter does not respect if a screen is in portrait orientation

[Till]

Public bug reported:

Ubuntu 15.04
unity-greeter 15.04.4-0ubuntu1

I have two screens. The main screen is in landscape orientation, the
second screen is in portrait orientation. The unity greeter displays the
wallpaper on the second screen as if the screen was also in landscape
orientation, so it appears 90° rotated.

I would like to have the wallpaper on the second screen rotated
correctly or not displayed at all (just a black screen).

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  unity greeter does not respect if a screen is in portrait orientation

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04
  unity-greeter 15.04.4-0ubuntu1

  I have two screens. The main screen is in landscape orientation, the
  second screen is in portrait orientation. The unity greeter displays
  the wallpaper on the second screen as if the screen was also in
  landscape orientation, so it appears 90° rotated.

  I would like to have the wallpaper on the second screen rotated
  correctly or not displayed at all (just a black screen).

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

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

[Desktop-packages] [Bug 1492698] Re: Windows Phone cannot access phone via MTP

[Enrico]

I got the same problem with my Lumia 520 (Nokia), but my new Lumia 640
(Microsoft) seems to work fine. Could it be a Nokia-related issue?

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

Title:
  Windows Phone cannot access phone via MTP

Status in libmtp package in Ubuntu:
  New

Bug description:
  Im have two smartphones with windows phone if im connect one smartphone to 
computer and open nautilus i can't access files and view 
  lsusb
  Bus 002 Device 005: ID 0421:06fc Nokia Mobile Phones

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

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

[Desktop-packages] [Bug 619632]

[Robert Ancell]

Hi, any feedback on this patch?

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

Title:
  Use gettext for translating user messages

Status in PolicyKit:
  Confirmed
Status in Ubuntu Translations:
  Fix Released
Status in policykit-1 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: policykit-1

  PolicyKit currently requires translations to be in the XML, e.g.:

  Install system color profiles
  Instalovat systémové profily 
barev

  This makes it hard to modify translations after build-time and to
  provide only a set of translations (i.e. a language pack).

  It would be better to have:

  Install system
  color profiles

  And use the standard gettext system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/619632/+subscriptions

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

[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

[Michael Zhdanov]

Just noticed - everything is fine when I connect to 2.4 WiFi on my
router and I have the error when I use 5 GHz. I tried all possible
variants of configuration for my 5 GHz access point - the same error. So
I am using 2.4 GHz now...

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1492805] [NEW] While using the Chrome and Firefox web browsers, Ubuntu will crash and log me out and will not let me log back in without rebooting the computer. This happens qu

[D]

Public bug reported:

While using the Chrome and Firefox web browsers, Ubuntu will crash and
log me out and will not let me log back in without rebooting the
computer.  This happens quite often.  Most often while watching video
content, but also just while navigating through web pages.  I have
reported the issue after reboot countless times.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity-greeter 14.04.11-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
Uname: Linux 3.16.0-48-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
CurrentDesktop: Unity
Date: Sun Sep  6 13:15:11 2015
InstallationDate: Installed on 2015-06-18 (80 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 (20150218.1)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity-greeter
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

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

Title:
  While using the Chrome and Firefox web browsers, Ubuntu will crash and
  log me out and will not let me log back in without rebooting the
  computer.  This happens quite often.  Most often while watching video
  content, but also just while navigating through web pages.  I have
  reported the issue after reboot countless times.

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  While using the Chrome and Firefox web browsers, Ubuntu will crash and
  log me out and will not let me log back in without rebooting the
  computer.  This happens quite often.  Most often while watching video
  content, but also just while navigating through web pages.  I have
  reported the issue after reboot countless times.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-greeter 14.04.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-48-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Sep  6 13:15:11 2015
  InstallationDate: Installed on 2015-06-18 (80 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-greeter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by

[Michael Zhdanov]

The same error for me on Lubuntu 14.04 and Toshiba Tecra Z50-A.

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

Title:
  [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945
  :03:00.0: BSM uCode verification failed at addr ...; wlan0:
  deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1452610] Re: /etc/modprobe.d is not a file

[TJ]

Hit this again today with lightdm spamming the logs.

I'd left the PC for about 45 minutes; came back to a backlit but black
display and no response to input.

I connected via SSH and found lightdm had TWO instances of X running,
one on tty7 and the other on tty8

I could find no clues in any of the logs as to what caused it; no signs
of errors or crashes. the Xorg.1.log for tty8 showed the GPU couldn't
obtain resources and failed (presumably due to tty7 with the first X
instance).

14:43:30 lightdm[1704]: /etc/modprobe.d is not a file
14:43:30 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
14:43:30 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfx
core_conf
14:43:30 lightdm[1704]: /etc/modprobe.d is not a file
14:43:30 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
14:43:30 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfxcore_conf
...
15:25:04 lightdm[1704]: /etc/modprobe.d is not a file
15:25:04 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
15:25:04 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfxcore_conf
15:25:04 lightdm[1704]: /etc/modprobe.d is not a file
15:25:04 lightdm[1704]: message repeated 3 times: [ /etc/modprobe.d is not a 
file]
15:25:04 lightdm[1704]: update-alternatives: error: no alternatives for 
x86_64-linux-gnu_gfxcore_conf

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

Title:
  /etc/modprobe.d is not a file

Status in lightdm package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Triaged

Bug description:
  /var/log/upstart# cat lightdm.log
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  /etc/modprobe.d is not a file
  update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf

  Above looks weird... modprobe.d is a directory & why update-
  alternatives are called?!

  This is lightdm 1.10.5-0ubuntu1

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

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

[Desktop-packages] [Bug 1487553] Re: Compiz freezes entire desktop on Wily

[Carla Sella]

Hello Fabio,
I installed Kernel 4.2.0-996 as you suggested. I will wait a couple of days to 
see what happens and then let you know.
As for the propretary drivers I could try, but I would prefer to solve the 
issue with nouveau as I prefer to use open source drivers.
Anyway if the problem is not solved with Kernel 4.20.-996 I will try them.

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

Title:
  Compiz freezes entire desktop on Wily

Status in compiz package in Ubuntu:
  New

Bug description:
  On Wily using Google calendar, Facebook Google+ and other Untity Web  Apps 
Compiz freezes the desktop, cannot do anything than reboot from termina 
(CTRL+ALT+F1).
  It also happened using Oracle VirtualBox, but not sure it was the real reason 
for the freeze. 
  My hardware: https://gist.github.com/anonymous/3203c7c5a43a509c0f22.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu7
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Aug 21 18:10:34 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.0, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=4b5d483e-4c0c-4013-b27c-0684b9343728 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0803
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx: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.1+15.10.20150805-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.63-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu3
  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-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Fri Aug 21 13:50:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUVC Camera (046d:081b) KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu3
  xserver.video_driver: nouveau
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu7
  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
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.2, 4.1.0-3-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:0491]
  InstallationDate: Installed on 2015-08-16 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150816)
  MachineType: System manufacturer System Product Name
  Package: compiz 1:0.9.12.1+15.10.20150805-0ubuntu1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 

[Desktop-packages] [Bug 1492767] Re: gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

[Mélodie]

** Description changed:

  Hello,
  
- I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday, and
- today, I updated the system (with the console, because other issues came
- first which led me to do a filesystem check). Then I started Synaptic,
- and oops! no GUI, only the borders of the window would show. Several
- other programs were affected and would not start (Geany, text editor),
- or show their content. After tests and research it appeared only GTK3
- programs were affected. If using a theme with GTK2, or move the GTK
- configuration out of the way, the programs would work.
+ I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday (custom
+ Bento Openbox), and today, I updated the system (with the console,
+ because other issues came first which led me to do a filesystem check).
+ Then I started Synaptic, and oops! no GUI, only the borders of the
+ window would show. Several other programs were affected and would not
+ start (Geany, text editor), or show their content. After tests and
+ research it appeared only GTK3 programs were affected. If using a theme
+ with GTK2, or move the GTK configuration out of the way, the programs
+ would work.
  
  The upgrade contained the following packages:
  gir1.2-gdkpixbuf-2.0_2.30.7
  libgdk-pixbuf2.0-0_2.30.7
  libgdk-pixbuf2.0-common_2.30.7
  
  I fixed the issue by booting to the Live USB I had used to install, and
  repackage the programs with dpkg-repack, then reinstalled them using
  "sudo dpkg -i *.deb". (copied from the live usb to the home in the
  install, rebooted and reinstalled there).
  
  Problem solved for this install, where I have for now blocked the update
  for these three packages.
  
  At post-install, after I had updated, I had the same message as the people 
who reported that bug:
  https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294
  
  
  (gtk-update-icon-cache-3.0:29671): 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.
  
  
  and when trying to do so, the console returned a message stating gdk-
  pixbuf-query-loaders was not installed. (no such package in the repos
  either).
  
  More information can be found at
  http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html
  
  where I discussed about this bug and my findings.
  
  Now I will try to produce this bug again in the Live USB (which has no
  persistence).
  
  Best regards,
  Mélodie

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

Title:
  gdk-pixbuf packages update breaks the GUI in Trusty 14.04.3

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Hello,

  I did a fresh install with a Trusty 14.04.3 (x86_64) yesterday (custom
  Bento Openbox), and today, I updated the system (with the console,
  because other issues came first which led me to do a filesystem
  check). Then I started Synaptic, and oops! no GUI, only the borders of
  the window would show. Several other programs were affected and would
  not start (Geany, text editor), or show their content. After tests and
  research it appeared only GTK3 programs were affected. If using a
  theme with GTK2, or move the GTK configuration out of the way, the
  programs would work.

  The upgrade contained the following packages:
  gir1.2-gdkpixbuf-2.0_2.30.7
  libgdk-pixbuf2.0-0_2.30.7
  libgdk-pixbuf2.0-common_2.30.7

  I fixed the issue by booting to the Live USB I had used to install,
  and repackage the programs with dpkg-repack, then reinstalled them
  using "sudo dpkg -i *.deb". (copied from the live usb to the home in
  the install, rebooted and reinstalled there).

  Problem solved for this install, where I have for now blocked the
  update for these three packages.

  At post-install, after I had updated, I had the same message as the people 
who reported that bug:
  https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1282294

  
  (gtk-update-icon-cache-3.0:29671): 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.
  

  and when trying to do so, the console returned a message stating gdk-
  pixbuf-query-loaders was not installed. (no such package in the repos
  either).

  More information can be found at
  http://irclogs.ubuntu.com/2015/09/06/%23ubuntu-bugs.html

  where I 

[Desktop-packages] [Bug 1461645] Re: [Ubuntu 15.10 64bit] Nouveau problems with ( google-chrome-unstable )

[Amit Kucheria]

This hits me on 14.04 as well with an updated google-chrome. So perhaps
this is a google-chrome bug?

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

Title:
  [Ubuntu 15.10 64bit] Nouveau problems with ( google-chrome-unstable )

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

Bug description:
  When Ubuntu 15.10 64bits ( btrfs ) got installed, i want to use 
google-chrome-unstable 45.0.2414.0 (64-bit) on it.
  But i found glitches that affect the whole interface, sometimes the context 
menus

  that's what i found in the terminal after using google-chrome-unstable

  $ google-chrome-unstable
  [9234:9372:0603/190135:ERROR:get_updates_processor.cc(243)] 
PostClientToServerMessage() failed during GetUpdates
  [9234:9261:0603/190136:ERROR:password_syncable_service.cc(165)] Passwords 
datatype error was encountered: There are passwords with identical sync tags in 
the database.
  [9234:9234:0603/190136:ERROR:extension_downloader.cc(694)] Invalid URL: '' 
for extension klfneahoibjkdlonilmnkkncopeiomoc
  nouveau: kernel rejected pushbuf: Argument invalide
  nouveau: ch0: krec 0 pushes 3 bufs 18 relocs 0
  nouveau: ch0: buf  0002 0004 0004 
  nouveau: ch0: buf 0001 002d 0004 0004 
  nouveau: ch0: buf 0002 002b 0002 0002 0002
  nouveau: ch0: buf 0003 0007 0002 0002 0002
  nouveau: ch0: buf 0004 000a 0002 0002 
  nouveau: ch0: buf 0005 000b 0002 0002 
  nouveau: ch0: buf 0006 0008 0002 0002 
  nouveau: ch0: buf 0007 0006 0004  0004
  nouveau: ch0: buf 0008 000e 0002  0002
  nouveau: ch0: buf 0009 005b 0002  0002
  nouveau: ch0: buf 000a 005a 0004 0004 
  nouveau: ch0: buf 000b 000f 0002 0002 0002
  nouveau: ch0: buf 000c 005f 0004 0004 
  nouveau: ch0: buf 000d 005e 0002  0002
  nouveau: ch0: buf 000e 002c 0004 0004 
  nouveau: ch0: buf 000f 002e 0002  0002
  nouveau: ch0: buf 0010 005c 0002  0002
  nouveau: ch0: buf 0011 005d 0002  0002
  nouveau: ch0: psh  074cd4 075858
  nouveau:  0x0004a200
  nouveau:  0x0001
  nouveau:  0x0004a314
  nouveau:  0x05e4
  nouveau:  0x0018a21c
  nouveau:  0x
  nouveau:  0x0040
  nouveau:  0x05e4
  nouveau:  0x00fd
  nouveau:  0x0001
  nouveau:  0x
  nouveau:  0x0008a238
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x0008a30c
  nouveau:  0x2138b000
  nouveau:  0x401f
  nouveau:  0x0004a234
  nouveau:  0x
  nouveau:  0x0010a31c
  nouveau:  0x05e4
  nouveau:  0x00fd
  nouveau:  0x0101
  nouveau:  0x
  nouveau:  0x0004a200
  nouveau:  0x0001
  nouveau:  0x0004a314
  nouveau:  0x004c
  nouveau:  0x0018a21c
  nouveau:  0x
  nouveau:  0x0030
  nouveau:  0x004c
  nouveau:  0x0013
  nouveau:  0x0001
  nouveau:  0x
  nouveau:  0x0008a238
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x0008a30c
  nouveau:  0x20337000
  nouveau:  0x20335000
  nouveau:  0x0004a234
  nouveau:  0x
  nouveau:  0x0010a31c
  nouveau:  0x004c
  nouveau:  0x0013
  nouveau:  0x0101
  nouveau:  0x
  nouveau:  0x0004a200
  nouveau:  0x0001
  nouveau:  0x0004a21c
  nouveau:  0x0001
  nouveau:  0x0008a238
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x0008a30c
  nouveau:  0x206c5000
  nouveau:  0x206c1400
  nouveau:  0x0010a31c
  nouveau:  0x0300
  nouveau:  0x0001
  nouveau:  0x0101
  nouveau:  0x
  nouveau:  0x00088200
  nouveau:  0x00f3
  nouveau:  0x0001
  nouveau:  0x00148214
  nouveau:  0x0004
  nouveau:  0x0001
  nouveau:  0x0001
  nouveau:  0x
  nouveau:  0x206ca100
  nouveau:  0x00088800
  nouveau:  0x
  nouveau:  0x00f3
  nouveau:  0x00288838
  nouveau:  0x0060
  nouveau:  0x0001
  nouveau:  0x
  nouveau:  0x0001
  nouveau:  0x
  nouveau:  0x0001
  nouveau:  0x
  nouveau:  0x0080
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x40608860
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x
  nouveau:  0x
  nouveau:  

[Desktop-packages] [Bug 1463598] Re: Chromium 43 fails to use hardware acceleration

[Jose Mico]

Florian, It was already fixed long ago in 14.04, but you need to enable
it manually:

- Open chrome://settings/
- Go to "Show advanced settings..." -> "System" -> "Use hardware acceleration 
when available"
- Restart chrome
- Check chrome://gpu/

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

Title:
  Chromium 43 fails to use hardware acceleration

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  After installing package chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 
hardware acceleration becomes disabled.
  I had no problem with previous chromium version.

  Console output:

  $ chromium-browser
  [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed 
to launch GPU process.
  [3150:3150:0609/190556:ERROR:url_pattern_set.cc(240)] Invalid url pattern: 
chrome://print/*
  [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed 
to launch GPU process.
  [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed 
to launch GPU process.

  chrome://gpu:

  Graphics Feature Status
  Canvas: Software only, hardware acceleration unavailable
  Flash: Software only, hardware acceleration unavailable
  Flash Stage3D: Software only, hardware acceleration unavailable
  Flash Stage3D Baseline profile: Software only, hardware acceleration 
unavailable
  Compositing: Software only, hardware acceleration unavailable
  Multiple Raster Threads: Unavailable
  Rasterization: Software only, hardware acceleration unavailable
  Threaded Rasterization: Unavailable
  Video Decode: Software only, hardware acceleration unavailable
  Video Encode: Software only, hardware acceleration unavailable
  WebGL: Unavailable

  Driver Bug Workarounds
  clear_uniforms_before_first_program_use
  count_all_in_varyings_packing
  disable_chromium_framebuffer_multisample
  disable_ext_occlusion_query
  disable_post_sub_buffers_for_onscreen_surfaces
  scalarize_vec_and_mat_constructor_args

  Problems Detected
  GPU process was unable to boot: GPU access is disabled in chrome://settings.
  Disabled Features: all

  - - -
  Actually GPU access is *not* disabled from settings.

  Workarounds like "--disable-gpu-sandbox" or "LIBGL_DRI3_DISABLE=1"
  didn't helped at all.

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

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