[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

2015-08-13 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu23

---
network-manager (0.9.10.0-4ubuntu23) wily; urgency=medium

  [ Tony Espy ]
  * d/p/lp1444162-add-ip6-config-to-nm-ofono-connections.patch: disable
IPv6 for ofono connections (LP: #1444162).

 -- Mathieu Trudel-Lapierre mathieu...@ubuntu.com  Wed, 12 Aug 2015
15:45:38 -0400

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  In Progress

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

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

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


[Desktop-packages] [Bug 1444162] Re: IPv6 default route present on ccmni0, even though no address assigned

2015-08-13 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 0.9.10.0-4ubuntu23

---
network-manager (0.9.10.0-4ubuntu23) wily; urgency=medium

  [ Tony Espy ]
  * d/p/lp1444162-add-ip6-config-to-nm-ofono-connections.patch: disable
IPv6 for ofono connections (LP: #1444162).

 -- Mathieu Trudel-Lapierre mathieu...@ubuntu.com  Wed, 12 Aug 2015
15:45:38 -0400

** Changed in: network-manager (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  IPv6 default route present on ccmni0, even though no address assigned

Status in Canonical System Image:
  New
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  $ system-image-cli -i
  current build number: 171
  device name: m75
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-04-14 22:23:10
  version version: 171

  Upon boot, my v6 routes include a default via ccmni0:
  $ ip -6 route
  fe80::/64 dev wlan0  proto kernel  metric 256 
  default dev ccmni0  proto static  metric 1024 

  Even though there's no v6 address on the device:
  $ ip -6 addr
  1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  10: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000
  inet6 fe80::3abc:1aff:fe18:b68b/64 scope link 
 valid_lft forever preferred_lft forever

  This means that hosts that have v6 addresses are tried to be reached via v6, 
which obviously fails:
   29% [Connecting to ports.ubuntu.com (2001:67c:1360:8001::18)]

  Toggling GSM data loses the default route:

  $ ip -6 route  
  fe80::/64 dev wlan0  proto kernel  metric 256

  And the connection succeeds via v4.

  Attached find a set of logs from network-test-session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu13
  Uname: Linux 3.10.35+ armv7l
  ApportVersion: 2.17-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Tue Apr 14 23:45:11 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-04-14 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150414-020204)
  IpRoute:
   default via 10.2.0.254 dev wlan0  proto static  metric 1024 
   10.0.0.0/8 via 10.2.0.1 dev wlan0  proto dhcp  metric 10 
   10.2.0.0/24 dev wlan0  proto kernel  scope link  src 10.2.0.66
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  SourcePackage: network-manager
  SystemImageInfo:
   current build number: 171
   device name: m75
   channel: ubuntu-touch/vivid-proposed
   last update: 2015-04-14 22:23:10
   version version: 171
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-04-14T04:33:56
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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


[Desktop-packages] [Bug 1482937] Re: split into language packs

2015-08-13 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-getting-started-docs -
3.16.2-1ubuntu1

---
gnome-getting-started-docs (3.16.2-1ubuntu1) wily; urgency=medium

  * Split out packaging into language packs so Ubuntu GNOME can seed
only the english version on the ISO's, and localised pack will
be installed via language-selector (LP: #1482937)

 -- Tim Lunn t...@feathertop.org  Sat, 08 Aug 2015 17:26:45 +1000

** Changed in: gnome-getting-started-docs (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  split into language packs

Status in Ubuntu GNOME:
  New
Status in gnome-getting-started-docs package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  We want to add the gnome getting started user guide to the Ubuntu
  GNOME seed, however since this package includes localized
  video/animations, the current packaging ends up at 120MB which is
  really too big to include in the ISO.

  So will split this up into language packs and only seed the english
  version, and let language-selector handle installation of the
  localized versions.

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

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


[Desktop-packages] [Bug 1484380] [NEW] Xorg regular crash on wily

2015-08-13 Thread Didier Roche
Public bug reported:

After upgrading to wily, I started to get regular random Xorg crash (and
so, session restarting and such). This can happen multiple times a day.
I've retried installing the latest intel driver from the xorg-edgers ppa
as Timo recommended, but the crash is still there.

Attached the stacktrace in gdb.txt

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
BootLog:
 [FAILED] Failed to start LSB: Start NTP daemon.
 See 'systemctl status ntp.service' for details.
 [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
  Starting Light Display Manager...
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Aug 13 08:42:01 2015
DistUpgraded: 2014-10-31 12:06:43,271 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21da]
InstallationDate: Installed on 2012-05-28 (1171 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: LENOVO 4287CTO
ProcEnviron:
 LANGUAGE=fr_FR
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to wily on 2014-10-31 (285 days ago)
dmi.bios.date: 02/14/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET58WW (1.28 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4287CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4287CTO
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.62-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
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+git20150810.4cea8037-0ubuntu0sarvatt
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Thu Aug 13 08:16:24 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728 
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu3

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: New


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

** Attachment added: gdb.txt
   https://bugs.launchpad.net/bugs/1484380/+attachment/4443928/+files/gdb.txt

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

Title:
  Xorg regular crash on wily

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

Bug description:
  After upgrading to wily, I started to get regular random Xorg crash
  (and so, session restarting and such). This can happen multiple times
  a day. I've retried installing the latest intel driver from the xorg-
  edgers ppa as Timo recommended, but the crash is still there.

  Attached the stacktrace in gdb.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64

[Desktop-packages] [Bug 1484389] [NEW] fglrx-updates-core 2:15.200-0ubuntu0.4: fglrx-updates-core kernel module failed to build

2015-08-13 Thread new4u
Public bug reported:

Crash happened during update to vivid lts kernel 3.19.0.26.13

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx-updates-core 2:15.200-0ubuntu0.4
ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
Uname: Linux 3.16.0-46-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: 3.19.0-26-generic
Date: Thu Aug 13 09:17:03 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 
DVI-I/DVI-D/HDMI/DP [174b:e221]
InstallationDate: Installed on 2014-08-25 (352 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: System manufacturer System Product Name
PackageVersion: 2:15.200-0ubuntu0.4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-46-generic 
root=UUID=19977145-9d77-4894-9b5a-b85242f30c7c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu0.4: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2101
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D
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.:bvr2101:bd10/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
modified.conffile..etc.OpenCL.vendors.amdocl64.icd: [deleted]
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.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Aug 13 09:13:45 2015
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 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.16.0-1ubuntu1.2~trusty2
xserver.video_driver: fglrx

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


** Tags: amd64 apport-package compiz-0.9 package-from-proposed trusty ubuntu

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

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

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

Bug description:
  Crash happened during update to vivid lts kernel 3.19.0.26.13

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates-core 2:15.200-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-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: 3.19.0-26-generic
  Date: Thu Aug 13 

[Desktop-packages] [Bug 1364647] Re: [System Settings] Alarm, Calls should always be played (also) in the speakerphone even when a bluetooth or wired headset is used

2015-08-13 Thread Matthew Paul Thomas
I don't know why this was assigned to me again. I'm not involved with
the design of the Clock app, and I've already made a suggestion.

** Changed in: ubuntu-ux
 Assignee: Matthew Paul Thomas (mpt) = (unassigned)

** Summary changed:

- [System Settings] Alarm, Calls should always be played (also) in the 
speakerphone even when a bluetooth or wired headset is used
+ Can't hear clock alarm when headphones are plugged in but not in your ears

** Description changed:

  When a bluetooth or wired headset the phone embedded speakerphone should
  ring anyway as you probably won't wear an headset while sleeping, while
  you prefer keeping your headset connected all the times.
  
  -- SOLUTION --
- Calls and Alarms should *always* be played to the speaker phones, as well as 
in the wired/wireless headset.
+ Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.
+ 
+ (The equivalent for the ringtone is bug 1364647.)

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

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Ubuntu Clock App:
  Incomplete
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1364647.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1364647/+subscriptions

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


[Desktop-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled

2015-08-13 Thread Sebastien Bacher
 Did not fix it for me. I still just see the drop-down options for the
first 3 characters and nothing when more characters are entered.

Can you give some more details
- what's the output of dpkg -l | grep libtimezonemap
- did you restart unity-control-center
- what chars did you enter? does it behave in a consistant way?

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

Title:
  WARNING **: Could not connect to geoname lookup server: Operation was
  cancelled

Status in One Hundred Papercuts:
  Confirmed
Status in libtimezonemap package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Invalid
Status in libtimezonemap source package in Vivid:
  Fix Committed
Status in unity-control-center source package in Vivid:
  Invalid

Bug description:
  * Impact
  the dialog to add location doesn't work in a reliable way

  * Test Case
  open Date  Time panel  Clock
  Enable Time in other locations
  Click Choose Locations...
  Try to add a location, delete the name and type it again, it should work 
every time

  * Regression potential
  The entry to add location should work every time

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

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


[Desktop-packages] [Bug 1484382] [NEW] [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from firefox.desktop

2015-08-13 Thread Anders Kaseorg
Public bug reported:

Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-aurora,
GNOME Shell fails to match running Firefox windows to the Firefox
launcher icon. This is because the Firefox windows report a WM_CLASS of
‘Firefox-dev’, which GNOME Shell by default tries to match against the
basename of the firefox.desktop file (‘firefox’).

This can be fixed by adding ‘StartupWMClass=Firefox-dev’ to
firefox.desktop for the Aurora packages.

(The firefox-trunk package from ppa:ubuntu-mozilla-daily/ppa is not
affected because its WM_CLASS ‘Firefox-trunk’ matches the basename of
firefox-trunk.desktop.)

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

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

Title:
  [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from
  firefox.desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-
  aurora, GNOME Shell fails to match running Firefox windows to the
  Firefox launcher icon. This is because the Firefox windows report a
  WM_CLASS of ‘Firefox-dev’, which GNOME Shell by default tries to match
  against the basename of the firefox.desktop file (‘firefox’).

  This can be fixed by adding ‘StartupWMClass=Firefox-dev’ to
  firefox.desktop for the Aurora packages.

  (The firefox-trunk package from ppa:ubuntu-mozilla-daily/ppa is not
  affected because its WM_CLASS ‘Firefox-trunk’ matches the basename of
  firefox-trunk.desktop.)

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

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


[Desktop-packages] [Bug 1448355] Re: Dependency seems to be python3-aptdaemon.test not python-aptdaemon.test in vivid

2015-08-13 Thread Bruce Pieterse
I have already fixed this (http://bazaar.launchpad.net/~octoquad
/software-center/899878-hardcoded-colors-dark-theme/revision/3325), will
link a branch as soon as I can.

** Changed in: hundredpapercuts
 Assignee: (unassigned) = Bruce Pieterse (octoquad)

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

Title:
  Dependency seems to be python3-aptdaemon.test  not python-
  aptdaemon.test in vivid

Status in One Hundred Papercuts:
  Confirmed
Status in Ubuntu Software Center:
  Confirmed
Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  in README:

  To setup your development environment, you'll need to ensure the following
  extra packages are installed:

  sudo apt-get install xvfb python-coverage python-mock python-aptdaemon.test \
   python-qt4 python-unittest2 python-lxml pep8
  sudo apt-get build-dep software-center

  should probably read

  
  To setup your development environment, you'll need to ensure the following
  extra packages are installed:

  sudo apt-get install xvfb python-coverage python-mock python3-aptdaemon.test \
   python-qt4 python-unittest2 python-lxml pep8
  sudo apt-get build-dep software-center
  

  since that's what's actually available.

  Ubuntu 15.04
  software-center:
    Installed: 13.10-0ubuntu6
    Candidate: 13.10-0ubuntu6

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: software-center 13.10-0ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Apr 24 20:19:20 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (289 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140708)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears

2015-08-13 Thread Sebastien Bacher
bug #1483888 has been reported about the ringtone issue

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: ubuntu-clock-app
   Status: Incomplete = Invalid

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided = High

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

** Changed in: ubuntu-ux
   Status: Triaged = Fix Committed

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

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Canonical System Image:
  New
Status in Ubuntu Clock App:
  Invalid
Status in Ubuntu UX:
  Fix Committed
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1364647.)

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

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


[Desktop-packages] [Bug 1484083] Re: Don't work autologin after update lightdm

2015-08-13 Thread DeadMetaler
** Attachment added: lightdm.log
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1484083/+attachment/4443907/+files/lightdm.log

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

Title:
  Don't work autologin after update lightdm

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Don't work autologin after update lightdm

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.15.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-lowlatency 4.1.3
  Uname: Linux 4.1.0-3-lowlatency x86_64
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 12 14:20:00 2015
  InstallationDate: Installed on 2015-04-23 (110 days ago)
  InstallationMedia:
   
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484372] [NEW] package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

2015-08-13 Thread Alwyn Williams
Public bug reported:

The update tools did not update successfully. This has happened on a few
occasions recently.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gnome-system-tools 3.0.0-3ubuntu4.1
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic i686
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: i386
Date: Thu Aug 13 07:45:59 2015
DuplicateSignature: package:gnome-system-tools:3.0.0-3ubuntu4.1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2010-04-28 (1932 days ago)
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
SourcePackage: gnome-system-tools
Title: package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: Upgraded to trusty on 2014-08-12 (365 days ago)

** Affects: gnome-system-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  The update tools did not update successfully. This has happened on a
  few occasions recently.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-system-tools 3.0.0-3ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  Date: Thu Aug 13 07:45:59 2015
  DuplicateSignature: package:gnome-system-tools:3.0.0-3ubuntu4.1:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2010-04-28 (1932 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  SourcePackage: gnome-system-tools
  Title: package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-08-12 (365 days ago)

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

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


[Desktop-packages] [Bug 1484372] Re: package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting conf

2015-08-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  The update tools did not update successfully. This has happened on a
  few occasions recently.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gnome-system-tools 3.0.0-3ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  Date: Thu Aug 13 07:45:59 2015
  DuplicateSignature: package:gnome-system-tools:3.0.0-3ubuntu4.1:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2010-04-28 (1932 days ago)
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
  SourcePackage: gnome-system-tools
  Title: package gnome-system-tools 3.0.0-3ubuntu4.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: Upgraded to trusty on 2014-08-12 (365 days ago)

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

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


[Desktop-packages] [Bug 1484382] Re: [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from firefox.desktop

2015-08-13 Thread Anders Kaseorg
Or, I guess, it could alternatively be fixed by renaming the Aurora
packages to firefox-dev with a firefox-dev.desktop. That might be closer
to upstream’s expectations: Aurora tries very hard to coexist with
stable Firefox rather than replace it. (It creates its own separate
Firefox profile ‘dev-edition-default’, and switches back to it on every
launch unless you turn off the “Allow Firefox Developer Edition and
Firefox to run at the same time” setting.)

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

Title:
  [firefox-aurora PPA] StartupWMClass=Firefox-dev missing from
  firefox.desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Using the firefox package from ppa:ubuntu-mozilla-daily/firefox-
  aurora, GNOME Shell fails to match running Firefox windows to the
  Firefox launcher icon. This is because the Firefox windows report a
  WM_CLASS of ‘Firefox-dev’, which GNOME Shell by default tries to match
  against the basename of the firefox.desktop file (‘firefox’).

  This can be fixed by adding ‘StartupWMClass=Firefox-dev’ to
  firefox.desktop for the Aurora packages.

  (The firefox-trunk package from ppa:ubuntu-mozilla-daily/ppa is not
  affected because its WM_CLASS ‘Firefox-trunk’ matches the basename of
  firefox-trunk.desktop.)

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

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


[Desktop-packages] [Bug 1484316] Re: Xorg fails to start up

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xorg fails to start up

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

Bug description:
  After updating to vivid proposed, upon reboot Xorg failed to load with
  the proprietary catalyst driver and required a purging of fglrx to
  regain working state. During the time after reboot, the virtual
  console was unable to be accessed and a reboot into recovery mode was
  required to repair the system

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Wed Aug 12 18:54:36 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 7570] 
[1002:675d] (prog-if 00 [VGA controller])
 Subsystem: Pegatron Device [1b0a:90bd]
  InstallationDate: Installed on 2015-08-12 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  PackageVersion: 2:15.200-0ubuntu4.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed 
root=UUID=f7c5e7fd-d8b4-4d05-aad4-68e939fe3b90 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel 
module failed to build
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: 970M Pro3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd01/21/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970MPro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Aug 13 00:57:31 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPlus More Enterprise LTD. USB-compliant keyboard KEYBOARD, id 8
   inputPlus More Enterprise LTD. USB-compliant keyboard KEYBOARD, id 9
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1483888] Re: Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones plugged

2015-08-13 Thread Matthew Paul Thomas
This is a design question for the Phone app, not for pulseaudio. The
Phone app might choose to, for example, play the ringtone just through
headphones for the first two or three seconds, to give you a chance to
answer the call without waking up people nearby; and then switch to
playing through speaker, in case your headphones aren't in your ears.
I'm not saying it should necessarily do that, that's just one
possibility.

Unfortunately, the Phone app spec currently doesn't even mention
ringing. https://goo.gl/0hy3A1 The design for ringing should also
describe what should happen if other audio is playing when the call
arrives.

** Package changed: pulseaudio (Ubuntu) = dialer-app (Ubuntu)

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

Title:
  Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones
  plugged

Status in Canonical System Image:
  New
Status in dialer-app package in Ubuntu:
  New

Bug description:
  Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones are
  plugged.

  This I consider a bug, since user cannot depend on the such a device
  with hearing calls / being woken up in the morning.

  Typical scenario: listening to music/watching movies during the night
  and falling asleep. It already happened several times to me that I did
  not get awakened by the phone in the morning, since headphones were
  plugged into the device and all the sounds could be heard only in
  headphones.

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

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


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

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

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

Bug description:
  Crash happened during update to vivid lts kernel 3.19.0.26.13

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates-core 2:15.200-0ubuntu0.4
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-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: 3.19.0-26-generic
  Date: Thu Aug 13 09:17:03 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB 
GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221]
  InstallationDate: Installed on 2014-08-25 (352 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: System manufacturer System Product Name
  PackageVersion: 2:15.200-0ubuntu0.4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-46-generic 
root=UUID=19977145-9d77-4894-9b5a-b85242f30c7c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu0.4: fglrx-updates-core kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D
  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.:bvr2101:bd10/20/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.OpenCL.vendors.amdocl64.icd: [deleted]
  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.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Aug 13 09:13:45 2015
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   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.16.0-1ubuntu1.2~trusty2
  xserver.video_driver: fglrx

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

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


[Desktop-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears

2015-08-13 Thread Sebastien Bacher
that seems like an important issue, can we get that on the ota7 list?

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

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Canonical System Image:
  New
Status in Ubuntu Clock App:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1364647.)

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

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


[Desktop-packages] [Bug 1364647] Re: Can't hear clock alarm when headphones are plugged in but not in your ears

2015-08-13 Thread Matthew Paul Thomas
The described SOLUTION is not yet in the Clock design spec.
https://goo.gl/A9AlsL

** Changed in: ubuntu-ux
   Status: Fix Committed = Triaged

** Changed in: ubuntu-ux
 Assignee: (unassigned) = James Mulholland (jamesjosephmulholland)

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

Title:
  Can't hear clock alarm when headphones are plugged in but not in your
  ears

Status in Canonical System Image:
  New
Status in Ubuntu Clock App:
  Invalid
Status in Ubuntu UX:
  Triaged
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When a bluetooth or wired headset the phone embedded speakerphone
  should ring anyway as you probably won't wear an headset while
  sleeping, while you prefer keeping your headset connected all the
  times.

  -- SOLUTION --
  Alarms should *always* be played to the speaker phones, as well as in the 
wired/wireless headset.

  (The equivalent for the ringtone is bug 1364647.)

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

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


[Desktop-packages] [Bug 1484352] Re: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build - can't go past login screen when trying to start using kernel 3.19.0-26. 2.19.0-22 still

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to
  build - can't go past login screen when trying to start using kernel
  3.19.0-26. 2.19.0-22 still works

Status in fglrx-installer package in Ubuntu:
  Confirmed

Bug description:
  fglrx-installer seems to be broken. Refuses to install during system
  updates. I am currently working using kernel 3.19.0-22. When I want to
  start 3.19.0-26, I can't seem to go past the login screen. Screen
  blacks out and I get thrown back to login screen

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-22.22-lowlatency 3.19.8-ckt1
  Uname: Linux 3.19.0-22-lowlatency x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.19.0-26-lowlatency
  Date: Thu Aug 13 06:21:29 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: fglrx-core, 15.200, 3.19.0-22-lowlatency, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e194]
  InstallationDate: Installed on 2014-11-28 (257 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H
  PackageVersion: 2:15.200-0ubuntu4.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-lowlatency 
root=UUID=3cb75bea-754b-4936-82d4-83604287f600 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer
  Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2008
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: GA-MA780G-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/30/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA780G-UD3H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Aug 13 05:47:49 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Comfort Curve Keyboard 3000 KEYBOARD, id 8
   inputMicrosoft Comfort Curve Keyboard 3000 KEYBOARD, id 9
   inputMicrosoft Microsoft® Comfort Mouse 4500 KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: fglrx

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

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


[Desktop-packages] [Bug 1464645] Re: Samba shares over gvfs do not respect ACL rules

2015-08-13 Thread Sebastien Bacher
Thanks, the fix is in the current version so closing for the current
serie, I sponsored the trusty sru as well now. Can you provide the
impact/regression potential info on the bug as well?

** Changed in: gvfs (Ubuntu)
   Status: New = Fix Released

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

Title:
  Samba shares over gvfs do not respect ACL rules

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released

Bug description:
  Looks like the SMB backend does not support ACL rules while accessing
  remote shares.

  The scenario looks like this:
  1. LDAP authentication for client  server.
  2. SMB server with a share accessible to a certain ACL group or user.
  3. A user (that should be allowed to access the share: is a member of a 
authorized group or is an authorized ACL user) accesses the share from a client 
using nautilus and smb:// URI.

  Expected result:
  Access is granted to the resource.

  Actual result:
  Permission denied for accessing the resource in question.

  Actual result:
  No sign of ACL rules in the getfacl output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.16.0-39.53~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-39-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 12 13:49:37 2015
  InstallationDate: Installed on 2015-04-13 (59 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Status in libreoffice package in Ubuntu:
  Confirmed

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

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

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


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

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


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


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

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

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


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

2015-08-13 Thread Anna
I have a smilar case as teo1978. - I have a dell laptop with Optimus
technology with both Intel and Nvidia GPU.

Before the upgrade from 331 to 340 I never managed to get the Nvidia GPU
running, so I just used Intel instead. After the upgrade, the Nvidia GPU
was turned on by default but something was wrong with the configuration
in the xorg.conf file. Because of this I got a black screen after
rebooting.

The solution that I linked a few posts up actually has a thorough
explanation of what happened. It shows how to fix the xorg.conf file and
how to prevent ubuntu from changing it back after reboot (it was crucial
for me).

After all that my laptop started to actually use the Nvidia GPU for both
daily use and manually running simulation on GPU.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1399096] Re: Touchpad lost function after switch from guest to user account

2015-08-13 Thread Ara Pulido
** No longer affects: oem-priority

** Also affects: hwe-next
   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/1399096

Title:
  Touchpad lost function after switch from guest to user account

Status in HWE Next:
  New
Status in unity-greeter package in Ubuntu:
  New

Bug description:
  Reproduce steps:
1) Change account to guest by click guest account on the menu.
2) Change account to user again
3) Touchpad lost its function.

  When the touchpad becomes malfunction, there are some messages in
  /var/log/Xorg.0.log

  [   282.908] (WW) synaptics: SynPS/2 Synaptics TouchPad: can't grab event 
device, errno=16
  [   282.940] [dix] couldn't enable device 11
  [   282.940] setversion 1.4 failed: Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-input-synaptics 1.7.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-41.69stella1-generic 3.13.11.10
  Uname: Linux 3.13.0-41-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Dec  4 02:25:41 2014
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-neihu-trusty-amd64-20141125-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  InstallationDate: Installed on 2014-12-04 (0 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20141125-01:45
  Lsusb:
   Bus 001 Device 003: ID 0bda:5776 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-41-generic 
root=UUID=f7c1e040-6471-4e14-9e77-bb406b63fad3 ro quiet splash 
video.use_native_backlight=1 radeon.modeset=0 nouveau.modeset=0 vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.45
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd10/28/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097F12005F1620100:rvnHewlett-Packard:rn2211:rvr86.45:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097F12005F1620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  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.1stella3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Dec  4 02:21:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Desktop-packages] [Bug 1386111] Re: Keyboard shortcuts not working on Ubuntu 14.10 and 15.04

2015-08-13 Thread Juan
I confirm that removing appmenu-qt5 package solves the issue.

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

Title:
  Keyboard shortcuts not working on Ubuntu 14.10 and 15.04

Status in Unity:
  New
Status in eclipse package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in qtbase package in Ubuntu:
  Confirmed
Status in texmaker package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Keyboard shortcuts do not work. E.g. F1 for quick compile, Strg+F for
  searching

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: texmaker 4.3-1
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 27 11:01:56 2014
  InstallationDate: Installed on 2014-04-18 (191 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: texmaker
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (1 days ago)

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

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


[Desktop-packages] [Bug 1195101] Re: package lightdm (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2015-08-13 Thread Gabriele Sani
*** This bug is a duplicate of bug 1109338 ***
https://bugs.launchpad.net/bugs/1109338

Happened to me when tried to purge lightdm

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

Title:
  package lightdm (not installed) failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 1

Status in lightdm package in Ubuntu:
  New

Bug description:
  a

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: lightdm (not installed)
  Uname: Linux 3.10.0-031000rc7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 26 19:41:59 2013
  DuplicateSignature: package:lightdm:(not installed):subprocess installed 
post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  InstallationDate: Installed on 2013-05-22 (36 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130518)
  MarkForUpload: True
  SourcePackage: lightdm
  Title: package lightdm (not installed) failed to install/upgrade: subprocess 
installed post-removal 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/lightdm/+bug/1195101/+subscriptions

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


[Desktop-packages] [Bug 1243056] Re: Master Volume Ignored on Recon3D (CA0132) With Alsamixer/PA

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Master Volume Ignored on Recon3D (CA0132) With Alsamixer/PA

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  It began when I installed gnome-shell from a minimal CD in Ubuntu
  13.10, then I wasn't able to change volume with the volume slider
  which controls ALSA's Master control, but after installing the rest of
  ubuntu-desktop I completely lost sound on my Recon3D.

  I tried installing Ubuntu 13.10 again and still wasn't able to get any
  sound at all as soon as I installed the rest of ubuntu-desktop. I
  decided to go back to Ubuntu 13.04 with a fresh install, but although
  I can get sound with my Recon3D here 100% of the time, I cannot get
  the master volume controls to work.

  You can raise and lower them in alsamixer but they simply won't have
  any effect. Similarly, you can enable/disable some features in
  alsamixer and they won't have any effect, even though before they
  worked fine.

  However, if I switch to HDMI audio, the master control works, so the
  problem is with how alsa ignores various options in my Recon3D

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.12.0-031200rc5-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Tue Oct 22 01:13:56 2013
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1604
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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


[Desktop-packages] [Bug 1484095] Re: xdg-open fails to recognize xfce 4.12

2015-08-13 Thread bgr
*** This bug is a duplicate of bug 1388922 ***
https://bugs.launchpad.net/bugs/1388922

** This bug has been marked a duplicate of bug 1388922
   xdg-open doesn't properly detect Xfce/Xubuntu

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

Title:
  xdg-open fails to recognize xfce 4.12

Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Xubuntu 15.04
  xfce 4.12
  xdg-utils 1.1.0~rc1-2ubuntu10

  I have firefox and chrome installed. Firefox is defined as default in
  xfce settings. When calling a URL with xdg-open it starts chrome.

  A quick look in /usr/bin/xdg-open reveals line 309 in function
  detectDE():

  elif xprop -root _DT_SAVE_MODE 2 /dev/null | grep ' = \xfce4\$'
  /dev/null 21; then DE=xfce;

  
  This doesn't seem to work anymore.

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

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


[Desktop-packages] [Bug 1484365] [NEW] [dysfunction] pressing Tab on the left pane bug

2015-08-13 Thread Ali Rahbar
Public bug reported:

pressing Tab on the left pane starts to opening all the pages
recursively till the last page, and you can't stop it!!!

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

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

Title:
  [dysfunction]  pressing Tab on the left pane bug

Status in evince package in Ubuntu:
  New

Bug description:
  pressing Tab on the left pane starts to opening all the pages
  recursively till the last page, and you can't stop it!!!

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

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


[Desktop-packages] [Bug 1453538] Re: Invisible mouse pointer

2015-08-13 Thread QkiZ
Like I was posting before trick with gsettings not working for me.

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

Title:
  Invisible mouse pointer

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  After system boot on login screen mouse pointer is invisible. I am
  able to click to gadgets but its blind clicking. I dont know where is
  mouse pointer. When I'm switch to virtual console (CTRL+ALT+F1) and
  type

  sudo service lightdm restart

  command LightDM restarts and mouse pointer back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-17.17-lowlatency 3.19.6
  Uname: Linux 3.19.0-17-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 10 14:27:50 2015
  InstallationDate: Installed on 2015-02-13 (85 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  LightdmConfig:
   [SeatDefaults]
   allow-guest = false
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (15 days ago)

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

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


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

2015-08-13 Thread Dom
Public bug reported:

My desktop is what appears to be 16 colours, however the icons and the
browser all appear 32 bit high colour. This happened  after I was forced
to choose to boot into restore mode with the latest kernel, for the
system would not boot in normal mode with the latest kernel. Using a
previous kernel boots up OK, though.

After booting, a manual system update was performed however the
following error message was displayed at the end of the update:

Your system is providing 3D via software rendering rather than hardware 
rendering.  
This is a compatibility mode which should display 3D graphics properly but the 
performance may be very poor.  If the problem you're reporting is related to 
graphics 
performance, your real question may be why X didn't use hardware acceleration 
for your system.

System information

$ uname -a
Linux - 3.19.0-26-lowlatency #27-Ubuntu SMP PREEMPT Tue Jul 28 19:06:58 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-26.27-lowlatency 3.19.8-ckt4
Uname: Linux 3.19.0-26-lowlatency x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 3.19.0-26-generic
Date: Thu Aug 13 21:06:50 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates-core, 15.200: added
 vboxhost, 5.0.0, 3.19.0-23-generic, x86_64: installed
 vboxhost, 5.0.0, 3.19.0-26-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 
6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:1448]
InstallationDate: Installed on 2015-05-01 (103 days ago)
InstallationMedia: It
MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
PackageVersion: 2:15.200-0ubuntu4.1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-lowlatency 
root=UUID=8ae07448-9185-47d4-bb4e-5639e6e41bb3 ro recovery nomodeset
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
Renderer: Software
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.29
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1448
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 65.38
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr048E10242B102:rvnHewlett-Packard:rn1448:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6 Notebook PC
dmi.product.version: 048E10242B102
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Thu Aug 13 20:50:02 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: amd64 apport-package compiz-0.9 corrupt-desktop-graphics 
package-from-proposed ubuntu vivid

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

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

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

Bug description:
  My desktop is what appears to be 16 colours, however the icons and the
  browser all appear 32 bit high colour. This happened  after I was
  forced to choose to boot into restore mode with the latest kernel,
  for the system would not boot in normal mode with the latest kernel.
  Using a previous kernel boots up 

[Desktop-packages] [Bug 1477788] Re: Remove support for external panels

2015-08-13 Thread Sebastien Bacher
https://launchpad.net/ubuntu/+source/deja-dup/34.0-1ubuntu2

** Changed in: deja-dup (Ubuntu)
   Status: Fix Committed = Fix Released

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

Title:
  Remove support for external panels

Status in Ubuntu GNOME:
  New
Status in deja-dup package in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  We have been carrying patches that reimplented support for external
  panels in gnome-control-center, however this is only used by deja-dup
  these days. Rather than continuing to maintain these patches, we are
  dropping this support and will just use the desktop launcher to load
  the standalone deja-dup-preferences.

  This also drops the libgnome-control-center shared library, so deja-
  dup will need to disable build of the g-c-c panel.

  ProblemType: BugDistroRelease: Ubuntu 15.10
  Package: gnome-control-center 1:3.16.2-2ubuntu1~wily3 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 24 10:01:56 2015
  InstallationDate: Installed on 2012-09-23 (1033 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha 
amd64(20120922)SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 34.0-1ubuntu1

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

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


[Desktop-packages] [Bug 1361139] Re: Activating Orca reader through Orca Screen Reader at Dash is not synchronized with Universal Access

2015-08-13 Thread Ara Pulido
** Summary changed:

- Orca Screen Reader operation interface cannot show on screen.
+ Activating Orca reader through Orca Screen Reader at Dash is not 
synchronized with Universal Access

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

Title:
  Activating Orca reader through Orca Screen Reader at Dash is not
  synchronized with Universal Access

Status in OEM Priority Project:
  New
Status in gnome-orca package in Ubuntu:
  Confirmed

Bug description:
  GM and OOBE, then boot into OS.Open Orca Screen Reader,find it's
  operation interface cannot show on screen but voice can output.

  Steps to Reproduce:
  1.GM and OOBE, then boot into OS.
  2.Open Orca Screen Reader.
  3.Find it's operation interface cannot show on screen,voice can output.
  Details please refers to the attachment.

  Could this bug be fixed in one of following ways:
  1. Hide the Orca icon from Dash, so user could not launch it from Dash and 
could only launch it from Universal Access.
  2. Make Orca UI could be shown up if user launch it from Dash, and sync the 
configuration setting with Universal Access.

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

-- 
Mailing list: https://launchpad.net/~desktop-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)

2015-08-13 Thread Sebastien Bacher
sponsored now, it's in the sru queue waiting for review

** Changed in: onboard (Ubuntu Utopic)
   Status: New = Won't Fix

-- 
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:
  New
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 francesco.fuma...@gmx.net  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


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

2015-08-13 Thread Robin
Teo,

the Optimus issue is definitely a *separate bug*, requiring its own 
resolution.

R.

On 13/08/15 14:48, teo1978 wrote:
 Or should we file a separate bug?


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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1368049] Re: SunPinyin user interface for SETUP is English.

2015-08-13 Thread Ara Pulido
** Changed in: oem-priority
   Status: New = Invalid

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

Title:
  SunPinyin user interface for SETUP is English.

Status in OEM Priority Project:
  Invalid
Status in ibus-sunpinyin package in Ubuntu:
  New

Bug description:
  1. Install Ubuntu 14.04 with Simplified Chinese.

  2. Boot into desktop.

  3. SunPinyin user interface for SETUP is English.

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

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


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

2015-08-13 Thread teo1978
Or should we file a separate bug?

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1484365] Re: [dysfunction] pressing Tab on the left pane bug

2015-08-13 Thread Sebastien Bacher
Thank you for your bug report. What version of Ubuntu do you use? Does
it happen on any document? Can you describe the exact steps you use to
trigger the issue?

** Changed in: evince (Ubuntu)
   Importance: Undecided = Low

** Changed in: evince (Ubuntu)
   Status: New = Incomplete

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

Title:
  [dysfunction]  pressing Tab on the left pane bug

Status in evince package in Ubuntu:
  Incomplete

Bug description:
  pressing Tab on the left pane starts to opening all the pages
  recursively till the last page, and you can't stop it!!!

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

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


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

2015-08-13 Thread dino99
hey all users still complaining:

- be sure to have a clean nvidia driver installation: not a system where the 
driver receive upgrades but still with borked settings behind the scene
- so sudo apt-get purge nvidia* is mandatory first, then install the required 
driver

- as the '331' driver is now deprecated, and replaced by the '340' one,
that means the still opened '331' are useless

So this report is closed now; meaning you need to open a new report if
you really need

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty)
   Status: Triaged = Invalid

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty)
   Status: Triaged = Invalid

** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty)
 Assignee: Alberto Milone (albertomilone) = (unassigned)

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty)
 Assignee: Alberto Milone (albertomilone) = (unassigned)

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1361139] Re: Activating Orca reader through Orca Screen Reader at Dash is not synchronized with Universal Access

2015-08-13 Thread Ara Pulido
** Description changed:

- GM and OOBE, then boot into OS.Open Orca Screen Reader,find it's
- operation interface cannot show on screen but voice can output.
+ Steps to reproduce:
  
- Steps to Reproduce:
- 1.GM and OOBE, then boot into OS.
- 2.Open Orca Screen Reader.
- 3.Find it's operation interface cannot show on screen,voice can output.
- Details please refers to the attachment.
+ 1) Open the Dash
+ 2) Search for Orca
+ 3) Start Orca Screen Reader
+ 4) Screen reader starts
+ 5) Open Universal Access
  
- Could this bug be fixed in one of following ways:
- 1. Hide the Orca icon from Dash, so user could not launch it from Dash and 
could only launch it from Universal Access.
- 2. Make Orca UI could be shown up if user launch it from Dash, and sync the 
configuration setting with Universal Access.
+ Expected results:
+ Screen reader option is ON
+ 
+ Actual results:
+ Screen reader option is OFF
+ 
+ Possible solutions could be:
+ 
+ * Remove Orca Screen Reader from the Dash
+ * Or make sure it synchronizes its status correctly

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

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

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

** Changed in: oem-priority
   Importance: Undecided = Medium

** Changed in: oem-priority/wily
   Importance: Undecided = Medium

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

Title:
  Activating Orca reader through Orca Screen Reader at Dash is not
  synchronized with Universal Access

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project wily series:
  Triaged
Status in gnome-orca package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1) Open the Dash
  2) Search for Orca
  3) Start Orca Screen Reader
  4) Screen reader starts
  5) Open Universal Access

  Expected results:
  Screen reader option is ON

  Actual results:
  Screen reader option is OFF

  Possible solutions could be:

  * Remove Orca Screen Reader from the Dash
  * Or make sure it synchronizes its status correctly

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

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


[Desktop-packages] [Bug 1431753] Réponse en cas d'absence

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1476476] Re: battery indicator only sort of reflects actual battery charge

2015-08-13 Thread BlackJohnny
*** This bug is a duplicate of bug 1471913 ***
https://bugs.launchpad.net/bugs/1471913

** This bug has been marked a duplicate of bug 1471913
   [MX4] Battery statistics are incorrect

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

Title:
  battery indicator only sort of reflects actual battery charge

Status in Canonical System Image:
  Confirmed
Status in upower package in Ubuntu:
  New

Bug description:
  On Ubuntu Touch devices, the battery indicator and graph behave in
  strange ways which do not accurately represent the state of the
  phone's battery or power supply.  This may be several bugs, but more
  than one of those can probably be fixed in a single straightforward
  way.

  Attached is a graph showing, at the top, what the battery indicator
  and graph show.  Below, the blue line shows the kernel's voltage value
  from /sys/class/power_supply/battery/voltage_now , and the green line
  shows the actual voltage going in to the phone from a power supply.

  To help make sense of the graph, here are the events which happened during 
the measurement period:
  - I tested bug 1476468, but this part of the graph is cut off to the left.
  - I turned the power supply up to 4.2X V and turned the phone back on.  It 
was not plugged in to USB.
  - At about 0.1 hours I turned the power supply down to 3.1V and waited.
  - At about 0.35 hours the phone turned itself off; I guess I set the input 
power too low.
  - At about 0.45 hours I noticed, turned the power up to 4.3V, and turned the 
phone back on.  After it booted, I turned the power down to 3.3V and waited 
again.
  - Time passed; I was working on other things.
  - At ~2.7 hours, I turned up the power supply to 4.3 V.
  - At ~2.8 hours, I plugged in USB.
  - At ~3.8 hours, the battery indicator noticed, jumped to 85%, and 
retroactively changed the graph from a horizontal line to a diagonal rising 
line.

  One issue is that the user-visible graph lags way behind the power
  supply.  It took about 35 to 60 minutes to notice that the power had
  dropped to a very low level, then plummeted all at once.  Before this,
  it merely declined a few percent.  The kernel's reading also lags a
  bit, but it looks like it may simply have a lowpass filter or
  something on it.  Regardless, the kernel's raw value is much closer to
  reality.

  A second issue is that the user-visible graph and percent do not go up
  when the battery voltage increases.  It refuses to increase the
  estimated charge, ever, unless USB is plugged in.  However, li-ion
  batteries normally recover some voltage after a high-amperage drain
  stops.  So, if you watch videos for half an hour and stop, the charge
  actually recovers and the battery indicator should reflect this.
  Letting the percent go up while it's not plugged in is not an error,
  it's just how the battery works.

  A third (and fourth) issue is that it took about an hour for the
  indicator to show an increased charge even after the USB cable was
  plugged in.  ...  and then despite jumping suddenly from 1% to 85% it
  *retroactively* changed the graph to make it look like the level had
  been increasing the whole time.

  I notice that the kernel sees voltage increases immediately, but
  decreases take a while to settle.  Not ideal, but probably not bad
  either.

  What I propose as a solution: Instead of using the current code to
  estimate a charge percent, we should perhaps translate the kernel's
  voltage value into a percent directly.  At least while unplugged.
  While plugged in, I'm not sure if the kernel has an accurate value
  anywhere.  Using the kernel data directly would give a more accurate
  representation of the battery state, and is not prone to the bizarre
  behaviors reported on the mailing lists (or the corner cases I've
  observed in testing on a modified phone).

  As for translating the kernel voltage into a percent, it simply needs to go 
through a curve correction function.  It should look approximately like one of 
these, depending on the exact battery type:
  http://www.lygte-info.dk/pic/Batteries2011/All18650/Capacity-0.2A.png

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

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


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

2015-08-13 Thread dino99
** Tags removed: utopic
** Tags added: vivid

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

Title:
  nvidia binary driver leaks vram like crazy

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

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

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

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

  However, you can tell that this is caused by some sort of driver leak,
  since if you jump to the fb console with ctl-alt-f1, and then alt-tab
  back to X, the VRAM usage drops dramatically:

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

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

  
  The upshot of this is that, right now, I have to dump to the fb console and 
back before using any OpenGL apps, or they often fail with OpenGL memory 
allocation errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan  9 12:01:56 2015
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

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


[Desktop-packages] [Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close

2015-08-13 Thread Ara Pulido
** Changed in: oem-priority
   Status: New = Triaged

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

** Also affects: unity-settings-daemon (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: unity-settings-daemon (Ubuntu Trusty)
   Status: New = In Progress

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

Title:
  SRU: For skylake system, u-s-d cause a black screen when resume from
  S3 via Lid Close

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project trusty series:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Trusty:
  In Progress

Bug description:
  OEM LP private bug: https://bugs.launchpad.net/bugs/1466441

  Title: Sometimes system turns a black screen when resume from S3 via
  Lid Close

  [Impact]

  Sometimes system turns a black screen when resume from S3 via Lid Close
  It only has cursor on screen but still can switch to tty1.
  Failure rate ~ 1/5

  [Test Case]
  1. install Ubuntu 14.04.2  3.19+ kernel and boot to OS
  2. Close the lid
  3. Open the lid
  4. check the display status

  Expected results: System should resume to the log in screen when open
  the lid

  Actual results:
  System sometimes fails to resume back to the log in screen but blackscreen 
instead.
  (Failure rate~ 1/5)

  [Regression Potential]
  Low. Killing touchscreen mapping after 3 seconds should not affect any other 
input device.

  Details:

  unity-settings-deamon will call xinput --map-to-output 11 eDP1 at 
background,
  and it's being blocked so only cursor will show on screen.

  1. Switch to tty1 when this happen
  2. Login with user account on tty1.
  3. Use DISPLAY=:0 xrandr  on commandline you'll see it's being blocked.

  Since xinput is being blocked for some unknown reason (in gdb it shows
  polling on xcb_connect_to_fd() in XOpenDisplay() ),

  a possible workaround is to set a timeout for xinput in u-s-d.

  === modified file 'plugins/xrandr/gsd-xrandr-manager.c'
  --- plugins/xrandr/gsd-xrandr-manager.c   2014-06-05 11:56:15 +
  +++ plugins/xrandr/gsd-xrandr-manager.c   2015-07-01 08:59:56 +
  @@ -2199,7 +2199,7 @@
   if (gnome_rr_output_info_is_active(output)) {
   g_debug (Mapping touchscreen %d onto output %s,
    device_id, name);
  - sprintf (command, xinput --map-to-output %d %s,
  + sprintf (command, timeout 3s xinput --map-to-output %d %s,
    device_id, name);
   status = system (command);
   }

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

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


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

2015-08-13 Thread teo1978
So, the issue I pointed out is definitely confirmed.

Please, whoever can, change back the status at least for 340-Tursty,
because the fix is partially broken.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1239087]

2015-08-13 Thread Jslaby-h
It's perhaps ready now :).

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

Title:
  Safely remove is not working (or broken) in Gnome Disks

Status in GNOME Disks:
  Fix Released
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in gnome-disk-utility package in Fedora:
  Unknown
Status in gnome-disk-utility package in openSUSE:
  Invalid
Status in oem-workaround-xhci-quirk-dkms package in openSUSE:
  Unknown

Bug description:
  In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD 
(do a spin down).
  In 13.04 this option is missed.

  In 13.10 it is appeared again, but not working as expected:
  +Gnome Disks normally powers off the USB flash (tested on 4 different 
flashes and 2 USB cardreaders).
  - Gnome Disks does not spin down USB HDD (but udisks --detach does)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-disk-utility 3.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 12 13:39:21 2013
  InstallationDate: Installed on 2013-03-06 (219 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130306)
  MarkForUpload: True
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions

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


[Desktop-packages] [Bug 1239087]

2015-08-13 Thread Oneukum
(In reply to Jiri Slaby from comment #12)
 It's perhaps ready now :).

Indeed. Please test KOTD.

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

Title:
  Safely remove is not working (or broken) in Gnome Disks

Status in GNOME Disks:
  Fix Released
Status in udisks:
  Confirmed
Status in gnome-disk-utility package in Ubuntu:
  Fix Released
Status in gnome-disk-utility package in Fedora:
  Unknown
Status in gnome-disk-utility package in openSUSE:
  Invalid
Status in oem-workaround-xhci-quirk-dkms package in openSUSE:
  Unknown

Bug description:
  In 12.04 I was able to safely remove USB-stick (make its LED off) and USB-HDD 
(do a spin down).
  In 13.04 this option is missed.

  In 13.10 it is appeared again, but not working as expected:
  +Gnome Disks normally powers off the USB flash (tested on 4 different 
flashes and 2 USB cardreaders).
  - Gnome Disks does not spin down USB HDD (but udisks --detach does)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-disk-utility 3.8.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Sat Oct 12 13:39:21 2013
  InstallationDate: Installed on 2013-03-06 (219 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130306)
  MarkForUpload: True
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (110 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-disk-utility/+bug/1239087/+subscriptions

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


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

2015-08-13 Thread Ara Pulido
We need some testing results on both Wily and Trusty.

Thanks,
Ara.

** Changed in: oem-priority
   Importance: Undecided = High

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

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

Title:
  novatel: improve probing for Dell branded modems

Status in ModemManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in modemmanager package in Ubuntu:
  New
Status in modemmanager source package in Trusty:
  New

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

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

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

  Could we backport this patch  into trusty? Thanks!

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

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


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

2015-08-13 Thread Alberto Milone
Just to clarify:

1) Do not install the driver unless you want to use it. Uninstalling the
driver will not break your system. By design a driver will be enabled if
you install it. We keep an option to disable the driver but that's only
to be used by gpu-manager (which is part of ubuntu-drivers-common), in
order to support hybrid graphics. That is not meant to be disabled
manually.

2) Optimus is supported by the NVIDIA driver. @teo1978 feel free to file
a separate bug report about the external screen issue.

3) Optimus seems to fail with 340 on some systems, and even with 346 on
others. We moved from the modesetting driver (which NVIDIA recommend
but it's not the only driver that works) to intel because some systems
didn't work (either at all or correctly). On such systems using the
modesetting driver is the only solution. Please file a separate bug
report about this (and file it against ubuntu-drivers-common)

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1484380] Re: Xorg regular crash on wily

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New = Confirmed

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

Title:
  Xorg regular crash on wily

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

Bug description:
  After upgrading to wily, I started to get regular random Xorg crash
  (and so, session restarting and such). This can happen multiple times
  a day. I've retried installing the latest intel driver from the xorg-
  edgers ppa as Timo recommended, but the crash is still there.

  Attached the stacktrace in gdb.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start LSB: Start NTP daemon.
   See 'systemctl status ntp.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 13 08:42:01 2015
  DistUpgraded: 2014-10-31 12:06:43,271 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2012-05-28 (1171 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2014-10-31 (285 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  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+git20150810.4cea8037-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Aug 13 08:16:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu3

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

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


[Desktop-packages] [Bug 1484380] Re: Xorg regular crash on wily

2015-08-13 Thread Stefan Hamminga
Hi,

As of today this started happening to me too, intervals of hours or minutes.
I'm on Kubuntu 15.04, also running xorg-edgers. My hardware is a Surface Pro 3 
i5-5300 (Intel GPU). I'd be happy to supply any logfile that would come in 
handy.

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

Title:
  Xorg regular crash on wily

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

Bug description:
  After upgrading to wily, I started to get regular random Xorg crash
  (and so, session restarting and such). This can happen multiple times
  a day. I've retried installing the latest intel driver from the xorg-
  edgers ppa as Timo recommended, but the crash is still there.

  Attached the stacktrace in gdb.txt

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 
2:2.99.917+git20150810.4cea8037-0ubuntu0sarvatt [origin: unknown]
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start LSB: Start NTP daemon.
   See 'systemctl status ntp.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
Starting Light Display Manager...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 13 08:42:01 2015
  DistUpgraded: 2014-10-31 12:06:43,271 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2012-05-28 (1171 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MachineType: LENOVO 4287CTO
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=a9f4b475-e4ce-45ed-aa33-9b92e52c49b0 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to wily on 2014-10-31 (285 days ago)
  dmi.bios.date: 02/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET58WW (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.1+15.10.20150627.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.62-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1
  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+git20150810.4cea8037-0ubuntu0sarvatt
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Thu Aug 13 08:16:24 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu3

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

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


[Desktop-packages] [Bug 1407867] Re: There are some incorrect button reminder of Software center when using orca screen reader.

2015-08-13 Thread Ara Pulido
** Changed in: oem-priority/trusty
   Status: New = Invalid

** Changed in: orca (Ubuntu)
   Status: New = Invalid

** Changed in: orca (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: oem-priority
   Status: Confirmed = Invalid

** Changed in: software-center
   Status: New = Invalid

** Changed in: software-center (Ubuntu Trusty)
   Status: New = Invalid

** Changed in: software-center (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: orca (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: software-center (Ubuntu)
   Status: New = Invalid

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

Title:
  There are some incorrect button reminder of Software center when using
  orca screen reader.

Status in OEM Priority Project:
  Invalid
Status in OEM Priority Project trusty series:
  Invalid
Status in Ubuntu Software Center:
  Invalid
Status in orca package in Ubuntu:
  Invalid
Status in software-center package in Ubuntu:
  Invalid
Status in orca source package in Trusty:
  Invalid
Status in software-center source package in Trusty:
  Invalid
Status in orca source package in Vivid:
  Invalid
Status in software-center source package in Vivid:
  Invalid

Bug description:
  [Impact]
  Lenovo customer require to fix it.From users experience this function is 
missing after launched some software. There are some incorrect button reminder 
of Software center when using orca screen reader.

  [Test Case]
  1. Boot into the system.
  2. Enable the orca screen reader in the login screen.
  3. Start the software center and click AllSoftware/Installed/History.
  4. Observe the orca screen reader work or not.

  Expected result:
  The screen reader should be reminder the words as label.

  Actual result:
  Only speak Page toggle.

  [Regression Potential]
  N/A

  [Other Info]
  N/A

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

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


[Desktop-packages] [Bug 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close

2015-08-13 Thread Alberto Milone
Another update: yesterday I submitted my new code for a review

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

Title:
  SRU: For skylake system, u-s-d cause a black screen when resume from
  S3 via Lid Close

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project trusty series:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  In Progress
Status in unity-settings-daemon source package in Trusty:
  In Progress

Bug description:
  OEM LP private bug: https://bugs.launchpad.net/bugs/1466441

  Title: Sometimes system turns a black screen when resume from S3 via
  Lid Close

  [Impact]

  Sometimes system turns a black screen when resume from S3 via Lid Close
  It only has cursor on screen but still can switch to tty1.
  Failure rate ~ 1/5

  [Test Case]
  1. install Ubuntu 14.04.2  3.19+ kernel and boot to OS
  2. Close the lid
  3. Open the lid
  4. check the display status

  Expected results: System should resume to the log in screen when open
  the lid

  Actual results:
  System sometimes fails to resume back to the log in screen but blackscreen 
instead.
  (Failure rate~ 1/5)

  [Regression Potential]
  Low. Killing touchscreen mapping after 3 seconds should not affect any other 
input device.

  Details:

  unity-settings-deamon will call xinput --map-to-output 11 eDP1 at 
background,
  and it's being blocked so only cursor will show on screen.

  1. Switch to tty1 when this happen
  2. Login with user account on tty1.
  3. Use DISPLAY=:0 xrandr  on commandline you'll see it's being blocked.

  Since xinput is being blocked for some unknown reason (in gdb it shows
  polling on xcb_connect_to_fd() in XOpenDisplay() ),

  a possible workaround is to set a timeout for xinput in u-s-d.

  === modified file 'plugins/xrandr/gsd-xrandr-manager.c'
  --- plugins/xrandr/gsd-xrandr-manager.c   2014-06-05 11:56:15 +
  +++ plugins/xrandr/gsd-xrandr-manager.c   2015-07-01 08:59:56 +
  @@ -2199,7 +2199,7 @@
   if (gnome_rr_output_info_is_active(output)) {
   g_debug (Mapping touchscreen %d onto output %s,
    device_id, name);
  - sprintf (command, xinput --map-to-output %d %s,
  + sprintf (command, timeout 3s xinput --map-to-output %d %s,
    device_id, name);
   status = system (command);
   }

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

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


[Desktop-packages] [Bug 1430194] Re: totem can't show menu correctly while playing video in fullscreen

2015-08-13 Thread Ara Pulido
** Changed in: oem-priority
   Status: New = Incomplete

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

Title:
  totem can't show menu correctly while playing video in fullscreen

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in totem package in Ubuntu:
  Incomplete

Bug description:
  While playing video in fullscreen, right click should show the menu, but 
totem will flicker the menu instead.
  I can't reproduce this issue with VLC player or chrome playing youtube video.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 15:50:13 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong150206-trusty-amd64-20150214-1
  InstallationDate: Installed on 2015-02-17 (21 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20150214-07:47
  LogAlsaMixer:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1438587] Re: connect button is grey when connecting to Ad-hoc SSID

2015-08-13 Thread Ara Pulido
** Changed in: oem-priority
   Status: New = Incomplete

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

Title:
  connect button is grey when connecting to Ad-hoc SSID

Status in NetworkManager:
  New
Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  First, I created an adhoc network through nm-applet-create new wifi
  network.

  Network Name: 111
  wi-fi security: WEP 128-bit Passphrase
  key: 222

  Then click create button and wait for its ready.

  using another machine to connect to this 111, enter password 222 and
  you can find that the connect button is grey, you can not click it.

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

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


[Desktop-packages] [Bug 1483014] Re: Unity Launcher and Terminal Windows

2015-08-13 Thread Andrea Azzarone
** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: unity
   Importance: Undecided = Medium

** Changed in: unity
Milestone: None = 7.3.3

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

Title:
  Unity Launcher and Terminal Windows

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Using Unity Launcher to bring-up Terminal in order to switch between 6
  terminal windows, clicking (or alt-tabbing) on the item will bring up
  the wrong window. When that happens, the next time you go through the
  selection process and click on the one you want, it will bring the
  window to the foreground, but it will be missing window decoration? or
  window titles, and borders.. etc

  Screenshot provided.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2015-08-13 Thread Adam Colligan
I have tried to recreate this with the following two mainline kernels:

v4.2-rc6-unstable
v4.2.0-999 (201508130157)

However, it is somewhat difficult to compare the behavior apples-to-
apples the way I normally do, as cpupower is not available for those
kernels (no linux-tools packages installed for them).  I would
appreciate any advice on the best way to show the problem's
presence/absence in an objective or definitive way across kernels.

-- 
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:
  New

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: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1478506] Re: Apps change audio output role all the time

2015-08-13 Thread Xavi Garcia
** Branch linked: lp:~xavi-garcia-mena/indicator-sound/lp-1478506-use-
role-volume

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

Title:
  Apps change audio output role all the time

Status in Canonical System Image:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  To reproduce, install the app Maroon in trouble from the app store
  and play it a little with having sound enabled. Press the volume down
  hardware button on the phone. It will temporarily decrease the volume.
  However, whenever a new item comes into the scene, it will be on 100%
  volume again.

  Setting the system volume to 0 should keep everything at 0.

  
  Please note that this app does *not* have any code to set the volume! Also 
this app is one of the upstream Qt QML example demo apps, so this is really how 
QML apps are supposed to work (in other words, it is not a badly implemented 
app, but really an issue in the system)

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

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


[Desktop-packages] [Bug 1484635] [NEW] package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to install/upgrade: försöker skriva över /usr/share/man/man1/bluetooth-wizard.1.gz som ocks

2015-08-13 Thread Per Johansson
Public bug reported:

dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: unity-control-center 15.04.0+15.10.20150813-0ubuntu1
Uname: Linux 4.1.4-040104-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
Date: Thu Aug 13 19:13:56 2015
DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150813-0ubuntu1:försöker skriva 
över /usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
ErrorMessage: försöker skriva över /usr/share/man/man1/bluetooth-wizard.1.gz 
som också finns i paketet gnome-bluetooth 3.8.2.1-0ubuntu12
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu6
SourcePackage: unity-control-center
Title: package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to 
install/upgrade: försöker skriva över 
/usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package gnome3-ppa package-from-proposed 
third-party-packages wily

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

Title:
  package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to
  install/upgrade: försöker skriva över /usr/share/man/man1/bluetooth-
  wizard.1.gz som också finns i paketet gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+15.10.20150813-0ubuntu1
  Uname: Linux 4.1.4-040104-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 19:13:56 2015
  DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150813-0ubuntu1:försöker skriva 
över /usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
  ErrorMessage: försöker skriva över 
/usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to 
install/upgrade: försöker skriva över 
/usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1482393] Re: Network stops working and the only fix is to boot the PC on Windows to fix it

2015-08-13 Thread Brian Murray
** Package changed: ubuntu-release-upgrader (Ubuntu) = network-manager
(Ubuntu)

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

Title:
  Network stops working and the only fix is to boot the PC on Windows to
  fix it

Status in network-manager package in Ubuntu:
  New

Bug description:
  My netwok just randomly stops working sometimes and even restarting
  the networking service or the computer 10 times doesn't help until I
  boot in Windows, then boot in Ubuntu again, cross fingers and hope it
  works.

  This only started after doing a partial upgrade from the 14.04 I
  initially installed to whatever 14.04 I have now, uname -a says this:

  Linux eon 3.16.0-45-generic #60~14.04.1-Ubuntu SMP Fri Jul 24 21:16:23
  UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-release-upgrader-core 1:0.220.7
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Thu Aug  6 23:24:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-10 (208 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484635] Re: package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to install/upgrade: försöker skriva över /usr/share/man/man1/bluetooth-wizard.1.gz som också

2015-08-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to
  install/upgrade: försöker skriva över /usr/share/man/man1/bluetooth-
  wizard.1.gz som också finns i paketet gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+15.10.20150813-0ubuntu1
  Uname: Linux 4.1.4-040104-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 19:13:56 2015
  DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150813-0ubuntu1:försöker skriva 
över /usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
  ErrorMessage: försöker skriva över 
/usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu6
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150813-0ubuntu1 failed to 
install/upgrade: försöker skriva över 
/usr/share/man/man1/bluetooth-wizard.1.gz som också finns i paketet 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen

2015-08-13 Thread Adam Colligan
I'm just updating this to indicate that the problem persists as of the
current state of Ubuntu 15.04.

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

Title:
  static image of desktop and windows displayed instead of lockscreen

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.

  .

  Expectation --

  Given any one of the following actions:
   - (from active desktop session) choosing lock from the Unity Panel power 
menu;
   - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a resume,

  ...the expected result is to display an interactive lockscreen where
  the active user's password can be entered to access the session. On
  this particular machine, which is a touch hybrid, the lockscreen also
  includes the Onboard soft keyboard.

  .

  Observed behavior --

  Instead of the lockscreen, each of these actions triggers the machine
  to display an image of the desktop/window session as it had been near
  the time of the lock or suspend.  The cursor is visible and can be
  moved.  The Unity Panel and Launcher usually appear as normal,
  although sometimes they are missing.

  Nothing happens when the user attempts to interact with the visible
  session by mouse or keyboard input.  Keyboard input will actually be
  fed to the lockscreen's password entry window, however.  So blindly
  typing the password from the zombie GUI session image -- and then
  pressing enter -- will bring up an active, working session.

  TTY session logins are available by the keyboard shortcuts ctrl-
  alt-F[number].  After pulling up one of these login screens (without
  actually logging in), then returning with ctrl-alt-F7, the lockscreen
  appears as expected.

  .

  Regression timeframe:

  I believe this behavior began sometime during January 2015.

  .

  Replication:

  This unexpected behavior takes place almost every time one of the
  listed actions is taken.  During one period of testing on 2015-01-31,
  the bug disappeared for a few rounds of lock and unlock. However, it
  re-appeared shortly thereafter (I believe after the next restart or
  suspend-resume).

  .

  Video attachment:

  A 1-minute video (.webm, no audio) is attached showing one form of
  this bug (simple lock-unlock).  The main feed was taken from a
  smartphone, but the video also includes an inset of what
  SimpleScreenRecorder (SSR) saw during the process.

  On lock, the actual screen became fully black. SSR, by contrast, recorded a 
black screen that included a clock in the top-right.
  On mouse movement, the actual screen displayed the static image of the 
GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen 
appearing.

  .

  Security tag reasoning:

  This bug displays a snapshot of recent  screen contents from a user's
  GUI session even when the user has (actively or indirectly) locked the
  session.  It also prevents a user from turning on the screen to
  command a user switch, go into TTY, etc. without displaying an image
  of her private GUI session.

  .

  Current graphics-related system info:

  OEM: HP Envy x360 15t (convertible hybrid notebook)
  CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400
  OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel
  OpenGL Extensions version: 3.0 Mesa 10.5.0-devel
  OS: Ubuntu 14.10 64-bit
  Kernel: 3.16.0-29 generic
  X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1
  Pixman version: 0.32.4
  Compiz version: 0.9.12

  Please let me know if there is further config information that would
  be helpful.

  .

  Upstream testing:

  This is a production machine. I am willing to test pre-release
  packages provided the testing configurations are easy to revert (such
  as upstream kernels).  I have been burned in the past with broken
  package systems and protracted  config repairs after testing
  experimental graphics and video driver software. But I would still be
  willing give it a shot if there is a simple and reliable process to
  roll back the changes.

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

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


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

2015-08-13 Thread Andy Thornton
Public bug reported:

Software updater crashes installing this package when upgrading kernel
to 3.19.0-26.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
DKMSKernelVersion: 3.19.0-26-generic
Date: Thu Aug 13 12:39:08 2015
InstallationDate: Installed on 2015-06-28 (46 days ago)
InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
PackageVersion: 2:15.200-0ubuntu4.1
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

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

Bug description:
  Software updater crashes installing this package when upgrading kernel
  to 3.19.0-26.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Thu Aug 13 12:39:08 2015
  InstallationDate: Installed on 2015-06-28 (46 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  PackageVersion: 2:15.200-0ubuntu4.1
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484607] [NEW] package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de l

2015-08-13 Thread GP
Public bug reported:

I suppose it is because I manually  (and incorrectly) installed 32 bit
driver for  Epson acculaser C 1100.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: cups-daemon 1.7.5-3ubuntu3.2
ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
Uname: Linux 3.16.0-44-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.5
Architecture: amd64
Date: Tue Aug 11 16:12:03 2015
DpkgHistoryLog:
 Start-Date: 2015-08-11  16:11:46
 Commandline: /usr/sbin/synaptic
 Install: liblqr-1-0:amd64 (0.4.2-1ubuntu1, automatic), libwmf-bin:amd64 
(0.2.8.4-10.3ubuntu1.14.10.1, automatic), python-numpy:amd64 (1.8.2-1ubuntu1, 
automatic), perlmagick:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagickcore5-extra:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), inkscape:amd64 
(0.48.5-2ubuntu1), libgsl0ldbl:amd64 (1.16+dfsg-2, automatic), 
libmagickwand5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), imagemagick:amd64 
(6.7.7.10+dfsg-4ubuntu1, automatic), libgnomevfs2-extra:amd64 (2.24.4-6ubuntu1, 
automatic), libmagickcore5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagick++5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
imagemagick-common:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic)
DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3.2:le paquet est dans un 
état vraiment incohérent; vous devriez  le réinstaller avant de tenter de le 
configurer.
ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  le 
réinstaller avant de tenter de le configurer.
InstallationDate: Installed on 2015-07-04 (40 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
Lpstat: device for EPSON-AL-C1100: 
usb://EPSON/AL-C1100?serial=31PF2PZ19022650913
MachineType: LENOVO 10117
Papersize: a4
PpdFiles: EPSON-AL-C1100: EPSON AL-C1100, ESC/PageS Filter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic.efi.signed 
root=UUID=507dcaf9-8dce-4a45-9d98-fa888e417136 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic.efi.signed 
root=UUID=507dcaf9-8dce-4a45-9d98-fa888e417136 ro quiet splash vt.handoff=7
SourcePackage: cups
Title: package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I7KT32AUS
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 STD or WIN
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT32AUS:bd12/26/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STDorWIN:cvnLENOVO:ct3:cvr:
dmi.product.name: 10117
dmi.product.version: Lenovo H535
dmi.sys.vendor: LENOVO
modified.conffile..etc.init.d.cups: [deleted]

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


** Tags: amd64 apport-package utopic

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

Title:
  package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in cups package in Ubuntu:
  New

Bug description:
  I suppose it is because I manually  (and incorrectly) installed 32 bit
  driver for  Epson acculaser C 1100.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: cups-daemon 1.7.5-3ubuntu3.2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: amd64
  Date: Tue Aug 11 16:12:03 2015
  DpkgHistoryLog:
   Start-Date: 2015-08-11  16:11:46
   Commandline: /usr/sbin/synaptic
   Install: liblqr-1-0:amd64 (0.4.2-1ubuntu1, automatic), libwmf-bin:amd64 
(0.2.8.4-10.3ubuntu1.14.10.1, automatic), python-numpy:amd64 (1.8.2-1ubuntu1, 
automatic), perlmagick:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagickcore5-extra:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), inkscape:amd64 
(0.48.5-2ubuntu1), libgsl0ldbl:amd64 (1.16+dfsg-2, automatic), 
libmagickwand5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), imagemagick:amd64 
(6.7.7.10+dfsg-4ubuntu1, automatic), libgnomevfs2-extra:amd64 (2.24.4-6ubuntu1, 
automatic), libmagickcore5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagick++5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
imagemagick-common:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic)
  DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3.2:le paquet est dans 
un état vraiment incohérent; vous devriez  le réinstaller avant de tenter de le 
configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2015-07-04 (40 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: 

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

2015-08-13 Thread teo1978
 hey all users still complaining:

 - be sure to

No man, if one had a system that was working and properly set up, and
after getting an update it is broken (or something that was correctly
configured gets misconfigured, or any configuration unnecessarily
changed at all), there is a bug.

We aren't supposed to be sure to anything. The updates should make
sure to not screw up a working system.

The bug should NOT be closed, unless a new one is opened for the issue
caused by the fix to this bug.

I am not going to waste my time reconfiguring my system every time a new
update comes out and screws up the settings that I already had to
manually fix.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


[Desktop-packages] [Bug 1484607] Re: package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le

2015-08-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in cups package in Ubuntu:
  New

Bug description:
  I suppose it is because I manually  (and incorrectly) installed 32 bit
  driver for  Epson acculaser C 1100.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: cups-daemon 1.7.5-3ubuntu3.2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: amd64
  Date: Tue Aug 11 16:12:03 2015
  DpkgHistoryLog:
   Start-Date: 2015-08-11  16:11:46
   Commandline: /usr/sbin/synaptic
   Install: liblqr-1-0:amd64 (0.4.2-1ubuntu1, automatic), libwmf-bin:amd64 
(0.2.8.4-10.3ubuntu1.14.10.1, automatic), python-numpy:amd64 (1.8.2-1ubuntu1, 
automatic), perlmagick:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagickcore5-extra:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), inkscape:amd64 
(0.48.5-2ubuntu1), libgsl0ldbl:amd64 (1.16+dfsg-2, automatic), 
libmagickwand5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), imagemagick:amd64 
(6.7.7.10+dfsg-4ubuntu1, automatic), libgnomevfs2-extra:amd64 (2.24.4-6ubuntu1, 
automatic), libmagickcore5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagick++5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
imagemagick-common:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic)
  DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3.2:le paquet est dans 
un état vraiment incohérent; vous devriez  le réinstaller avant de tenter de le 
configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2015-07-04 (40 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: device for EPSON-AL-C1100: 
usb://EPSON/AL-C1100?serial=31PF2PZ19022650913
  MachineType: LENOVO 10117
  Papersize: a4
  PpdFiles: EPSON-AL-C1100: EPSON AL-C1100, ESC/PageS Filter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic.efi.signed 
root=UUID=507dcaf9-8dce-4a45-9d98-fa888e417136 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic.efi.signed 
root=UUID=507dcaf9-8dce-4a45-9d98-fa888e417136 ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT32AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD or WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT32AUS:bd12/26/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STDorWIN:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.init.d.cups: [deleted]

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

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


[Desktop-packages] [Bug 1482393] [NEW] Network stops working and the only fix is to boot the PC on Windows to fix it

2015-08-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My netwok just randomly stops working sometimes and even restarting the
networking service or the computer 10 times doesn't help until I boot in
Windows, then boot in Ubuntu again, cross fingers and hope it works.

This only started after doing a partial upgrade from the 14.04 I
initially installed to whatever 14.04 I have now, uname -a says this:

Linux eon 3.16.0-45-generic #60~14.04.1-Ubuntu SMP Fri Jul 24 21:16:23
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-release-upgrader-core 1:0.220.7
ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
Uname: Linux 3.16.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Thu Aug  6 23:24:54 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-10 (208 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade trusty
-- 
Network stops working and the only fix is to boot the PC on Windows to fix it
https://bugs.launchpad.net/bugs/1482393
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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


[Desktop-packages] [Bug 1484639] [NEW] ibus-pinyin does not use monochrome icons

2015-08-13 Thread Andreas E.
Public bug reported:

Ibus-pinyin is striking out of the panel because it has a bold and
colored icon – different from all other input methods/languages.

Attached is replacement for /usr/share/ibus-pinyin/icons/ibus-pinyin.svg
for dark themes (like Ambiance and others). I don't how it would work
for bright themes (like Radiance and others). Maybe it would better be
solved in the system icon theme (as it is with indicator-keyboard-...svg
)?. Before doing more icons on my own I am waiting for feedback.

version: 1.5.0-3ubunt amd64
Ubuntu: 15.04

** Affects: ibus-pinyin (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: ibus-pinyin.svg
   
https://bugs.launchpad.net/bugs/1484639/+attachment/339/+files/ibus-pinyin.svg

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

Title:
  ibus-pinyin does not use monochrome icons

Status in ibus-pinyin package in Ubuntu:
  New

Bug description:
  Ibus-pinyin is striking out of the panel because it has a bold and
  colored icon – different from all other input methods/languages.

  Attached is replacement for /usr/share/ibus-pinyin/icons/ibus-
  pinyin.svg for dark themes (like Ambiance and others). I don't how it
  would work for bright themes (like Radiance and others). Maybe it
  would better be solved in the system icon theme (as it is with
  indicator-keyboard-...svg )?. Before doing more icons on my own I am
  waiting for feedback.

  version: 1.5.0-3ubunt amd64
  Ubuntu: 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-pinyin/+bug/1484639/+subscriptions

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


[Desktop-packages] [Bug 1483000] Re: please remove opengtl and libqtgtl from 14.10

2015-08-13 Thread Jonathan Riddell
** Changed in: opengtl (Ubuntu)
   Status: New = Fix Released

** Changed in: libqtgtl (Ubuntu)
   Status: New = Fix Released

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

Title:
  please remove opengtl and libqtgtl from 14.10

Status in libqtgtl package in Ubuntu:
  Fix Released
Status in opengtl package in Ubuntu:
  Fix Released

Bug description:
  please remove opengtl and libqtgtl from 14.10, dead upstream, not used
  anymore by calligra.

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

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


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

2015-08-13 Thread teo1978
 Teo,

 the Optimus issue is definitely a *separate bug*, requiring its own
 resolution.

I was not talking about the optimus issue.
I was talking about the fact that the update of the NVidia drivers overwrote 
some system settings that shouldn't have been touched. Before the update, my 
system was set up to not use nVidia drivers; after the update, it was set to 
use them. That's a bug in the update that was released.

I'm not quite sure whether or not that should be considered a separate
issue, because it is an issue directly caused by the fix to this issue.
That is, the fix to this issue caused a bug of its own.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


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

2015-08-13 Thread teo1978
 By design a driver will be enabled if you install it.

However, if it is disable when you UPGRADE the driver, it shouldn't be
reenabled.

 We keep an option to disable the driver but [...] That is not meant to
be disabled manually.

I don't know about now, but at the time I installed the driver, there was a 
nice graphical interface, accessible somewhere from the System Settings menu 
(back when Ubuntu had a menu), where you could choose whether to use NVidia 
proprietary drivers. And I chose not to.
It wasn't some arcane command line that I found out by googling around, it was 
something that was made accessible to a normal user. If things have changed 
since, you must take into account that there are machines still around that 
have been upgraded since those times. I can't remember exactly which Ubuntu 
version that was. It may have been 13.04, or 12.something

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


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

2015-08-13 Thread teo1978
 2) Optimus is supported by the NVIDIA driver.

That's not what NVidia told me. I asked for support and they told me it's 
officially unsupported on Linux.
And what I can tell for sure is that it doesn't work. The screen switching 
issue is well known.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


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

2015-08-13 Thread teo1978
 Uninstalling the driver will not break your system

On another machine, merely *installing* it did break the system. So
forgive me if I'm skeptical that uninstalling it will not break my
system. I take that as a should not.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


Re: [Desktop-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled

2015-08-13 Thread Marcel Beerli
Still not working for me.
I click the + and type Los Angeles or Paris but nothing.

$ dpkg -l | grep libtimezonemap
ii  libtimezonemap-data 0.4.3build1
all  GTK+3 timezone map widget - data files
ii  libtimezonemap1:amd64 0.4.3build1
amd64GTK+3 timezone map widget


Mit freundlichen Grüssen - Best regards

/Marcel Beerli
--
ad...@beerli.org
--

On 13.08.2015 11:10, Sebastien Bacher wrote:
 Did not fix it for me. I still just see the drop-down options for the
 first 3 characters and nothing when more characters are entered.

 Can you give some more details
 - what's the output of dpkg -l | grep libtimezonemap
 - did you restart unity-control-center
 - what chars did you enter? does it behave in a consistant way?


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

Title:
  WARNING **: Could not connect to geoname lookup server: Operation was
  cancelled

Status in One Hundred Papercuts:
  Confirmed
Status in libtimezonemap package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Invalid
Status in libtimezonemap source package in Vivid:
  Fix Committed
Status in unity-control-center source package in Vivid:
  Invalid

Bug description:
  * Impact
  the dialog to add location doesn't work in a reliable way

  * Test Case
  open Date  Time panel  Clock
  Enable Time in other locations
  Click Choose Locations...
  Try to add a location, delete the name and type it again, it should work 
every time

  * Regression potential
  The entry to add location should work every time

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

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


[Desktop-packages] [Bug 1484716] [NEW] package gnome-bluetooth (not installed) failed to install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете

2015-08-13 Thread Валерий
Public bug reported:

package gnome-bluetooth (not installed) failed to install/upgrade:
попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz»,
который уже имеется в пакете unity-control-center
15.04.0+15.10.20150813-0ubuntu1

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: gnome-bluetooth (not installed)
Uname: Linux 4.1.5-040105-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.18-0ubuntu6
AptOrdering:
 gnome-bluetooth: Install
 gnome-bluetooth: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Fri Aug 14 00:51:51 2015
ErrorMessage: попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», 
который уже имеется в пакете unity-control-center 
15.04.0+15.10.20150813-0ubuntu1
InstallationDate: Installed on 2015-06-02 (72 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150601)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: gnome-bluetooth
Title: package gnome-bluetooth (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», который уже 
имеется в пакете unity-control-center 15.04.0+15.10.20150813-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-bluetooth (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 wily

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

Title:
  package gnome-bluetooth (not installed) failed to install/upgrade:
  попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz»,
  который уже имеется в пакете unity-control-center
  15.04.0+15.10.20150813-0ubuntu1

Status in gnome-bluetooth package in Ubuntu:
  New

Bug description:
  package gnome-bluetooth (not installed) failed to install/upgrade:
  попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz»,
  который уже имеется в пакете unity-control-center
  15.04.0+15.10.20150813-0ubuntu1

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: gnome-bluetooth (not installed)
  Uname: Linux 4.1.5-040105-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.18-0ubuntu6
  AptOrdering:
   gnome-bluetooth: Install
   gnome-bluetooth: Configure
   NULL: ConfigurePending
  Architecture: i386
  Date: Fri Aug 14 00:51:51 2015
  ErrorMessage: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
unity-control-center 15.04.0+15.10.20150813-0ubuntu1
  InstallationDate: Installed on 2015-06-02 (72 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150601)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: gnome-bluetooth
  Title: package gnome-bluetooth (not installed) failed to install/upgrade: 
попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», который уже 
имеется в пакете unity-control-center 15.04.0+15.10.20150813-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1482937] Re: split into language packs

2015-08-13 Thread Tim
** Changed in: gnome-getting-started-docs (Ubuntu)
 Assignee: Tim (darkxst) = (unassigned)

** Changed in: ubuntu-gnome
   Status: New = Fix Released

** Changed in: ubuntu-gnome
Milestone: wily-ppa = wily

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

Title:
  split into language packs

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-getting-started-docs package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  We want to add the gnome getting started user guide to the Ubuntu
  GNOME seed, however since this package includes localized
  video/animations, the current packaging ends up at 120MB which is
  really too big to include in the ISO.

  So will split this up into language packs and only seed the english
  version, and let language-selector handle installation of the
  localized versions.

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

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


[Desktop-packages] [Bug 1464645] Re: Samba shares over gvfs do not respect ACL rules

2015-08-13 Thread Brian Murray
** Also affects: gvfs (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: gvfs (Ubuntu Trusty)
   Status: New = Triaged

** Changed in: gvfs (Ubuntu Trusty)
   Importance: Undecided = Low

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

Title:
  Samba shares over gvfs do not respect ACL rules

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Trusty:
  Triaged

Bug description:
  Looks like the SMB backend does not support ACL rules while accessing
  remote shares.

  The scenario looks like this:
  1. LDAP authentication for client  server.
  2. SMB server with a share accessible to a certain ACL group or user.
  3. A user (that should be allowed to access the share: is a member of a 
authorized group or is an authorized ACL user) accesses the share from a client 
using nautilus and smb:// URI.

  Expected result:
  Access is granted to the resource.

  Actual result:
  Permission denied for accessing the resource in question.

  Actual result:
  No sign of ACL rules in the getfacl output.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs 1.20.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.16.0-39.53~14.04.1-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-39-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 12 13:49:37 2015
  InstallationDate: Installed on 2015-04-13 (59 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484658] [NEW] package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is

2015-08-13 Thread Adam
Public bug reported:

Occurred while installing updates through Software Updater.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: unity-control-center 15.04.0+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-0ubuntu6
Architecture: amd64
Date: Thu Aug 13 14:26:31 2015
DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150805-0ubuntu1:trying to 
overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
ErrorMessage: trying to overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', 
which is also in package gnome-bluetooth 3.8.2.1-0ubuntu12
InstallationDate: Installed on 2015-08-13 (0 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150812)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: unity-control-center
Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package package-conflict wily

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

Title:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-
  wizard.1.gz', which is also in package gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  Occurred while installing updates through Software Updater.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+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-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 14:26:31 2015
  DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150805-0ubuntu1:trying to 
overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  ErrorMessage: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  InstallationDate: Installed on 2015-08-13 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150812)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484658] Re: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is a

2015-08-13 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-
  wizard.1.gz', which is also in package gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  Occurred while installing updates through Software Updater.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+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-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 14:26:31 2015
  DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150805-0ubuntu1:trying to 
overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  ErrorMessage: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  InstallationDate: Installed on 2015-08-13 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150812)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484658] Re: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is a

2015-08-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-
  wizard.1.gz', which is also in package gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  Occurred while installing updates through Software Updater.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+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-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 14:26:31 2015
  DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150805-0ubuntu1:trying to 
overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  ErrorMessage: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  InstallationDate: Installed on 2015-08-13 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150812)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2015-08-13 Thread Mathew Hodson
** Tags removed: rls-u-incoming

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

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

Status in tex-common package in Ubuntu:
  Confirmed
Status in tex-common source package in Trusty:
  Confirmed

Bug description:
  While updating from 13.04 to 13.10, I was prompted with a crash
  dialog, then a will automatically revert (?) dialogue...

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.8.0-31.23-lowlatency 3.8.13.8
  Uname: Linux 3.8.0-31-lowlatency x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  8 12:11:33 2013
  DuplicateSignature: package:tex-common:4.04:ErrorMessage: subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationDate: Installed on 2012-06-12 (482 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)

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

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


[Desktop-packages] [Bug 1350334] Re: copy/paste garbage while using mc, due to lack of support of bracketed paste mode

2015-08-13 Thread Eugene San
Backport to Trusty Bracketed paste should be per-terminal patch (LP:
#1350334)


** Patch added: Bracketed paste should be per-terminal
   
https://bugs.launchpad.net/terminator/+bug/1350334/+attachment/431/+files/92-bracketed-paste-per-terminal.patch

** Changed in: terminator
   Status: New = Invalid

** Changed in: vte (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  copy/paste garbage while using mc, due to lack of support of bracketed
  paste mode

Status in Terminator:
  Invalid
Status in vte package in Ubuntu:
  Fix Committed

Bug description:
  Gnome terminator does not support bracketed paste mode introduced by
  xterm to detect between typed-in text and text that is copy-pasted.

  Due to this, copy-pasting text in terminator adds some garbage
  character before and after pasted text.

  This bug occurs on latest version (from bzr).

  Example:

 my_pasted_text

  becomes

0~my_paster_text1~

  This occurs when using Terminator along with Midnight Commander.

  This is a well known bug that has been fixed already in Gnome Terminal.
  Apparently the bug has been fixed in VTE, and as a result on Gnome Terminal.
  See references below for details.

  To trigger the bug, see sequence below, copied from referenced bug
  report:

  1) start gnome-terminal
  2) start mc in that terminal
  3) enter the Ctrl-o subshell
  4) maximise the terminal (in terminator, this is same as doing for instance 
Ctrl-Z to maximize current sub-window)
  5) leave the Ctrl-o subshell (i.e. return to the dir/file list)
  6) copy some text (e.g. some filename)
  7) return back to the Ctrl-o subshell
  8) paste the text

  
  References:
  - xterm bracketed paste mode 
  
http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#Bracketed%20Paste%20Mode
  - original bug report on Midnight Commander
  http://www.midnight-commander.org/ticket/3207
  - Bug fix and patch on VTE
  https://bugzilla.gnome.org/show_bug.cgi?id=729533

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

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


[Desktop-packages] [Bug 1484658] Re: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is a

2015-08-13 Thread habanany
idk

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

Title:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: trying to overwrite '/usr/share/man/man1/bluetooth-
  wizard.1.gz', which is also in package gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  Occurred while installing updates through Software Updater.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+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-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 14:26:31 2015
  DuplicateSignature: 
package:unity-control-center:15.04.0+15.10.20150805-0ubuntu1:trying to 
overwrite '/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  ErrorMessage: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  InstallationDate: Installed on 2015-08-13 (0 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha amd64 (20150812)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: trying to overwrite 
'/usr/share/man/man1/bluetooth-wizard.1.gz', which is also in package 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484702] Re: Chrome Remote Desktop is not working from chromium browser

2015-08-13 Thread Arie Skliarouk
My mistake, it works now, close the bug please. Could be some networking
issue.

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

Title:
  Chrome Remote Desktop is not working from chromium browser

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chrome Remote Desktop is not working from chromium-browser of ubuntu
  14.04 (43.0.2357.130-0ubuntu0.14.04.1.1092) and ubuntu 15.04.

  When I try to connect to remote computer (after entering the one-time
  access code), the CRD shows message Connecting... that stays
  forever.

  Same thing in Google Chrome 44 works properly.

  Bug report on different issue with the same symptoms
  (https://code.google.com/p/chromium/issues/detail?id=434979) has
  comment about someone opening same bug
  (https://code.google.com/p/chromium/issues/detail?id=444982). When I
  try to open it, I get error 403 (Access Denied). Hope is that cromium
  maintainers of Ubuntu do have access to it.

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

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


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

2015-08-13 Thread Robando
Public bug reported:

got the error:

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

after running software update

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.200-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 3.19.0-26-generic
Date: Thu Aug 13 23:46:28 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 
DVI-I/DVI-D/HDMI/DP [174b:e221]
InstallationDate: Installed on 2015-05-22 (83 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
PackageVersion: 2:15.200-0ubuntu4.1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=580bcddf-8b02-4374-8e08-dbe460e6f220 ro noprompt persistent
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: fglrx-installer
Title: fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: 990XA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd02/04/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990XA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri Aug 14 00:16:29 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB OpticalWheel Mouse MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: fglrx

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


** Tags: amd64 apport-package compiz-0.9 package-from-proposed ubuntu vivid

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

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

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  got the error:

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

  after running software update

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Thu Aug 13 23:46:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850] 
[1002:6819] (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1283491] Re: rendering and size issues on high-dpi screen

2015-08-13 Thread Brian Murray
** Also affects: onboard (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: onboard (Ubuntu Trusty)
   Status: New = Triaged

** Changed in: onboard (Ubuntu Trusty)
   Importance: Undecided = High

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

Title:
  rendering and size issues on high-dpi screen

Status in Onboard:
  Fix Released
Status in onboard package in Ubuntu:
  Fix Released
Status in onboard source package in Trusty:
  Triaged

Bug description:
  When the global scaling factor is set to 2, onboard is not usable for
  touch input. In docked mode (bottom half of screen), it draws keys too
  large and most of the onboard UI is not drawn at all. In windowed mode
  (with titlebar and resizeable), the size is correct but it does not
  refresh the rendering.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 22 17:44:03 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1484715] [NEW] package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», который

2015-08-13 Thread Валерий
Public bug reported:

package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-
wizard.1.gz», который уже имеется в пакете gnome-bluetooth
3.8.2.1-0ubuntu12

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: unity-control-center 15.04.0+15.10.20150805-0ubuntu1
Uname: Linux 4.1.5-040105-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.18-0ubuntu6
Architecture: i386
Date: Fri Aug 14 00:42:59 2015
ErrorMessage: попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», 
который уже имеется в пакете gnome-bluetooth 3.8.2.1-0ubuntu12
InstallationDate: Installed on 2015-06-02 (72 days ago)
InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150601)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: unity-control-center
Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
gnome-bluetooth 3.8.2.1-0ubuntu12
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 wily

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

Title:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-
  wizard.1.gz», который уже имеется в пакете gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-
  wizard.1.gz», который уже имеется в пакете gnome-bluetooth
  3.8.2.1-0ubuntu12

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+15.10.20150805-0ubuntu1
  Uname: Linux 4.1.5-040105-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.18-0ubuntu6
  Architecture: i386
  Date: Fri Aug 14 00:42:59 2015
  ErrorMessage: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
gnome-bluetooth 3.8.2.1-0ubuntu12
  InstallationDate: Installed on 2015-06-02 (72 days ago)
  InstallationMedia: Ubuntu 15.10 Wily Werewolf - Alpha i386 (20150601)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2015-08-13 Thread Dennis-k
Public bug reported:

Whenever I try to install it on my system I get this error and then when
I reboot I cant login.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 3.19.0-26-generic
Date: Thu Aug 13 20:42:27 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e210]
MachineType: MSI MS-7917
PackageVersion: 2:15.200-0ubuntu4.1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=7e6cf1f9-29c9-4793-b757-5f54e63de049 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 5 (MS-7917)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.5:bd07/31/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7917
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Thu Aug 13 20:38:15 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: radeon

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


** Tags: amd64 apport-package compiz-0.9 package-from-proposed ubuntu vivid

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

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

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

Bug description:
  Whenever I try to install it on my system I get this error and then
  when I reboot I cant login.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Thu Aug 13 20:42:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e210]
  MachineType: MSI MS-7917
  PackageVersion: 2:15.200-0ubuntu4.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=7e6cf1f9-29c9-4793-b757-5f54e63de049 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.5
  dmi.board.asset.tag: To 

[Desktop-packages] [Bug 1484670] [NEW] package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», который

2015-08-13 Thread rolmops
Public bug reported:

package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-
wizard.1.gz», который уже имеется в пакете gnome-bluetooth
3.8.2.1-0ubuntu12

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: unity-control-center 15.04.0+15.10.20150805-0ubuntu1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.18-0ubuntu6
Architecture: amd64
Date: Thu Aug 13 22:50:38 2015
ErrorMessage: попытка перезаписать «/usr/share/man/man1/bluetooth-wizard.1.gz», 
который уже имеется в пакете gnome-bluetooth 3.8.2.1-0ubuntu12
InstallationDate: Installed on 2015-08-11 (2 days ago)
InstallationMedia:
 
RelatedPackageVersions:
 dpkg 1.18.2ubuntu1
 apt  1.0.9.10ubuntu1
SourcePackage: unity-control-center
Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
gnome-bluetooth 3.8.2.1-0ubuntu12
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package wily

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

Title:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-
  wizard.1.gz», который уже имеется в пакете gnome-bluetooth
  3.8.2.1-0ubuntu12

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

Bug description:
  package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to
  install/upgrade: попытка перезаписать «/usr/share/man/man1/bluetooth-
  wizard.1.gz», который уже имеется в пакете gnome-bluetooth
  3.8.2.1-0ubuntu12

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+15.10.20150805-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.18-0ubuntu6
  Architecture: amd64
  Date: Thu Aug 13 22:50:38 2015
  ErrorMessage: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
gnome-bluetooth 3.8.2.1-0ubuntu12
  InstallationDate: Installed on 2015-08-11 (2 days ago)
  InstallationMedia:
   
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu1
   apt  1.0.9.10ubuntu1
  SourcePackage: unity-control-center
  Title: package unity-control-center 15.04.0+15.10.20150805-0ubuntu1 failed to 
install/upgrade: попытка перезаписать 
«/usr/share/man/man1/bluetooth-wizard.1.gz», который уже имеется в пакете 
gnome-bluetooth 3.8.2.1-0ubuntu12
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1181344] Re: python-keyring timeout on import if started with sudo

2015-08-13 Thread Dmitry Shachnev
** No longer affects: python-secretstorage

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

Title:
  python-keyring timeout on import if started with sudo

Status in GNOME Keyring:
  Confirmed
Status in Salt:
  New
Status in gnome-keyring package in Ubuntu:
  Triaged

Bug description:
  steps to reproduce:
  $ sudo python
  Python 2.7.3 (default, Sep 26 2012, 21:53:58)
  [GCC 4.7.2] on linux2
  Type help, copyright, credits or license for more information.
   import keyring

  this will take ~25 seconds only on Xubuntu. If you do this on Ubuntu
  or Kubuntu (all version 12.10) it will return immediately. Also if you
  import keyring with normal user on Xubuntu it will return immediately.

  It is caused by a dbus call in /usr/share/pyshared/keyring/backend.py 
function SecretServiceKeyring.supported:
  $ sudo python
  Python 2.7.3 (default, Sep 26 2012, 21:53:58)
  [GCC 4.7.2] on linux2
  Type help, copyright, credits or license for more information.
   import dbus
   bus = dbus.SessionBus()
   bus.get_object('org.freedesktop.secrets', '/org/freedesktop/secrets')
  Traceback (most recent call last):
    File stdin, line 1, in module
    File /usr/lib/python2.7/dist-packages/dbus/bus.py, line 241, in get_object
  follow_name_owner_changes=follow_name_owner_changes)
    File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 248, in 
__init__
  self._named_service = conn.activate_name_owner(bus_name)
    File /usr/lib/python2.7/dist-packages/dbus/bus.py, line 180, in 
activate_name_owner
  self.start_service_by_name(bus_name)
    File /usr/lib/python2.7/dist-packages/dbus/bus.py, line 278, in 
start_service_by_name
  'su', (bus_name, flags)))
    File /usr/lib/python2.7/dist-packages/dbus/connection.py, line 651, in 
call_blocking
  message, timeout)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2015-08-13 Thread Alberto Salvia Novella
** Changed in: pm-utils (Ubuntu)
   Status: New = Confirmed

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

** Changed in: pm-utils (Ubuntu)
   Importance: Undecided = High

-- 
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: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2015-08-13 Thread xatr0z
The low framerate and flickering mouse disappear on 15.04 by:
- installing nonfree drivers: 
http://support.displaylink.com/knowledgebase/articles/615714#ubuntu
- systemctl start displaylink. Autostart: 
http://www.displaylink.org/forum/showpost.php?p=78036postcount=2

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I Restore
  previous settings, after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2015-08-13 Thread Robert Hooker
*** This bug is a duplicate of bug 1479913 ***
https://bugs.launchpad.net/bugs/1479913

** This bug has been marked a duplicate of bug 1479913
   fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build 
[FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 
'pci_ignore_hotplug']

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

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

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

Bug description:
  Software updater crashes installing this package when upgrading kernel
  to 3.19.0-26.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Thu Aug 13 12:39:08 2015
  InstallationDate: Installed on 2015-06-28 (46 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1)
  PackageVersion: 2:15.200-0ubuntu4.1
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2015-08-13 Thread teo1978
@lbertomilone please see https://bugs.launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-340/+bug/1483388 and mark its importance as
critical (prevents boot) as soon as possible.

Also feel free to correct anything that may be wrong in the report.

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

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

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

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

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

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


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

2015-08-13 Thread Robert Hooker
*** This bug is a duplicate of bug 1479913 ***
https://bugs.launchpad.net/bugs/1479913

** This bug has been marked a duplicate of bug 1479913
   fglrx-core 2:15.200-0ubuntu4.1: fglrx-core kernel module failed to build 
[FATAL: modpost: GPL-incompatible module fglrx.ko uses GPL-only symbol 
'pci_ignore_hotplug']

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

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

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

Bug description:
  Whenever I try to install it on my system I get this error and then
  when I reboot I cant login.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fglrx-updates-core 2:15.200-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.19.0-26-generic
  Date: Thu Aug 13 20:42:27 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e210]
  MachineType: MSI MS-7917
  PackageVersion: 2:15.200-0ubuntu4.1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic 
root=UUID=7e6cf1f9-29c9-4793-b757-5f54e63de049 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates-core 2:15.200-0ubuntu4.1: fglrx-updates-core kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.5:bd07/31/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Thu Aug 13 20:38:15 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.1-0ubuntu3
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1484684] [NEW] [Inspiron 3542, Generic 0000 ID 0, Digital Out, HDMI] Pulseaudio fails to detect card

2015-08-13 Thread Milan
Public bug reported:

I had no sound after upgrading ubuntu 12.04 LTS using sudo apt-get
upgrade. In the window Sound settings there is no device through which
sound can be played. Alsamixer says that this sound device does not have
any controls.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: pulseaudio 1:1.1-0ubuntu15.4
ProcVersionSignature: Ubuntu 3.5.0-61.90-generic 3.5.7.33
Uname: Linux 3.5.0-61-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
AplayDevices:
  List of PLAYBACK Hardware Devices 
 card 1: PCH [HDA Intel PCH], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.9
Architecture: amd64
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 1: PCH [HDA Intel PCH], device 0: HDA Generic [HDA Generic]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  milan  2536 F pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7a14000 irq 60'
   Mixer name   : 'Generic  ID 0'
   Components   : 'HDA:,80860101,0010'
   Controls  : 0
   Simple ctrls  : 0
Card0.Amixer.values:
 
Card1.Amixer.info:
 Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 60'
   Mixer name   : 'Realtek ID 255'
   Components   : 'HDA:10ec0255,10280652,0012'
   Controls  : 4
   Simple ctrls  : 3
Date: Thu Aug 13 22:24:57 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20130203-13:50
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel
Symptom_Jack: Digital Out, HDMI
Title: [Inspiron 3542, Generic  ID 0, Digital Out, HDMI] Pulseaudio fails 
to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/27/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0926J6
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0926J6:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 3542
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  [Inspiron 3542, Generic  ID 0, Digital Out, HDMI] Pulseaudio fails
  to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I had no sound after upgrading ubuntu 12.04 LTS using sudo apt-get
  upgrade. In the window Sound settings there is no device through which
  sound can be played. Alsamixer says that this sound device does not
  have any controls.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: pulseaudio 1:1.1-0ubuntu15.4
  ProcVersionSignature: Ubuntu 3.5.0-61.90-generic 3.5.7.33
  Uname: Linux 3.5.0-61-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu17.9
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  milan  2536 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7a14000 irq 60'
 Mixer name : 'Generic  ID 0'
 Components : 'HDA:,80860101,0010'
 Controls  : 0
 Simple ctrls  : 0
  Card0.Amixer.values:
   
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7a1 irq 60'
 Mixer name : 'Realtek ID 255'
 Components : 'HDA:10ec0255,10280652,0012'
 Controls  : 4
 Simple ctrls  : 3
  Date: Thu Aug 13 22:24:57 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  InstallationMedia: Ubuntu 12.04 Precise - Build 

[Desktop-packages] [Bug 1481832] Re: VA-API implementation for gallium missing

2015-08-13 Thread Alberto Salvia Novella
** Changed in: mesa (Ubuntu)
   Importance: Undecided = High

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

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include gallium_drv_video.so which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that gallium_drv_video.so binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary gallium_drv_video.so might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

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

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


[Desktop-packages] [Bug 1484702] [NEW] Chrome Remote Desktop is not working from chromium browser

2015-08-13 Thread Arie Skliarouk
Public bug reported:

Chrome Remote Desktop is not working from chromium-browser of ubuntu
14.04 (43.0.2357.130-0ubuntu0.14.04.1.1092) and ubuntu 15.04.

When I try to connect to remote computer (after entering the one-time
access code), the CRD shows message Connecting... that stays forever.

Same thing in Google Chrome 44 works properly.

Bug report on different issue with the same symptoms
(https://code.google.com/p/chromium/issues/detail?id=434979) has comment
about someone opening same bug
(https://code.google.com/p/chromium/issues/detail?id=444982). When I try
to open it, I get error 403 (Access Denied). Hope is that cromium
maintainers of Ubuntu do have access to it.

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

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

Title:
  Chrome Remote Desktop is not working from chromium browser

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Chrome Remote Desktop is not working from chromium-browser of ubuntu
  14.04 (43.0.2357.130-0ubuntu0.14.04.1.1092) and ubuntu 15.04.

  When I try to connect to remote computer (after entering the one-time
  access code), the CRD shows message Connecting... that stays
  forever.

  Same thing in Google Chrome 44 works properly.

  Bug report on different issue with the same symptoms
  (https://code.google.com/p/chromium/issues/detail?id=434979) has
  comment about someone opening same bug
  (https://code.google.com/p/chromium/issues/detail?id=444982). When I
  try to open it, I get error 403 (Access Denied). Hope is that cromium
  maintainers of Ubuntu do have access to it.

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

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


[Desktop-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic

2015-08-13 Thread Tuomas Lähteenmäki
all x86 dev packages are broken.

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

Title:
  Devel package not installable in 14.04.2 (mesa-lts-utopic

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Trusty:
  Fix Released

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

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

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1380561] Re: Unknown variable 'ansA' when editing the result after converting to hexadecimal

2015-08-13 Thread Alberto Salvia Novella
** Changed in: gnome-calculator (Ubuntu)
   Importance: Undecided = Medium

** Also affects: gnome-calculator
   Importance: Undecided
   Status: New

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

** Changed in: hundredpapercuts
   Status: New = Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided = Medium

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

Title:
  Unknown variable 'ansA' when editing the result after converting to
  hexadecimal

Status in GNOME Calculator:
  New
Status in One Hundred Papercuts:
  Confirmed
Status in gnome-calculator package in Ubuntu:
  Confirmed

Bug description:
  Version: 1:3.10.2-0ubuntu1.2

  I want to edit a result in hexadecimal:

  [Test Case]
  - open gnome-calculator
  - choose Programming mode
  - choose Decimal and enter a decimal number then press Enter
  - choose Hexadecimal to convert the number to hex
  - add A or any hexadecimal number A-F to the result and press Enter
  - you'll see Unknown variable 'ansA' where A is what you appended to the 
result

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

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


  1   2   >