[Desktop-packages] [Bug 1370890] [NEW] nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

2014-09-17 Thread dino99
Public bug reported:

Got an error while installing the kernel 3.16.0.16, the make.log warns
about:


WARNING: could not find /var/lib/dkms/nvidia-331/331.89/build/.nv-kernel.o.cmd 
for /var/lib/dkms/nvidia-331/331.89/build/nv-kernel.o


ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
DKMSKernelVersion: 3.16.0-16-generic
Date: Thu Sep 18 08:13:51 2014
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 utopic

** Attachment added: "make.log"
   https://bugs.launchpad.net/bugs/1370890/+attachment/4207088/+files/make.log

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Got an error while installing the kernel 3.16.0.16, the make.log warns
  about:

  
  WARNING: could not find 
/var/lib/dkms/nvidia-331/331.89/build/.nv-kernel.o.cmd for 
/var/lib/dkms/nvidia-331/331.89/build/nv-kernel.o
  

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  DKMSKernelVersion: 3.16.0-16-generic
  Date: Thu Sep 18 08:13:51 2014
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming

2014-09-17 Thread Ken VanDine
** Changed in: qml-box2d (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

** Changed in: bacon2d (Ubuntu)
   Importance: Undecided => Low

** Changed in: bacon2d (Ubuntu)
   Status: New => Triaged

** Changed in: bacon2d (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: content-hub (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  Rename QML modules to follow qml-module-foo naming

Status in “accounts-qml-module” package in Ubuntu:
  New
Status in “address-book-app” package in Ubuntu:
  New
Status in “bacon2d” package in Ubuntu:
  Triaged
Status in “clickmanager-plugin” package in Ubuntu:
  New
Status in “content-hub” package in Ubuntu:
  New
Status in “cordova-ubuntu” package in Ubuntu:
  New
Status in “dee-qt” package in Ubuntu:
  New
Status in “gsettings-qt” package in Ubuntu:
  New
Status in “history-service” package in Ubuntu:
  New
Status in “libhud-qt” package in Ubuntu:
  Won't Fix
Status in “libqofono” package in Ubuntu:
  New
Status in “libusermetrics” package in Ubuntu:
  New
Status in “mediascanner2” package in Ubuntu:
  New
Status in “poppler-qml-plugin” package in Ubuntu:
  New
Status in “qml-box2d” package in Ubuntu:
  New
Status in “qml-friends” package in Ubuntu:
  New
Status in “qt3d-opensource-src” package in Ubuntu:
  New
Status in “qtconnectivity-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtgrilo” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  New
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtpim-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtquickcontrols-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsensors-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsystems-opensource-src” package in Ubuntu:
  Fix Released
Status in “reminders-app” package in Ubuntu:
  New
Status in “solid” package in Ubuntu:
  New
Status in “sync-monitor” package in Ubuntu:
  New
Status in “telephony-service” package in Ubuntu:
  Triaged
Status in “thumbnailer” package in Ubuntu:
  New
Status in “u1db-qt” package in Ubuntu:
  New
Status in “ubuntu-download-manager” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-settings-components” package in Ubuntu:
  New
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  New
Status in “ubuntu-ui-extras” package in Ubuntu:
  New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
  New
Status in “ubuntuone-credentials” package in Ubuntu:
  New
Status in “unity-action-api” package in Ubuntu:
  Triaged
Status in “unity-notifications” package in Ubuntu:
  New
Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  The package names of QML modules should be of the format qml-
  module-{$modulename}[version], a transition that was started during Qt
  5.3 preparation in Ubuntu. For example this could be qml-module-
  qtquick-localstorage or qml-module-qtsysteminfo for non versioned
  modules, and qml-module-ubuntu-webthing0.3 for versioned/co-
  installable modules.

  Further details in Debian e-mail:
  http://lists.alioth.debian.org/pipermail/pkg-kde-
  talk/2014-March/001889.html

  For Ubuntu, transitional packages should be put in place for smooth 
distribution upgrades, since we're shipping with the old names in previous 
Ubuntus. An example of that is at 
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
 - in other words:
  - Make the old package a transitional oldlibs package that depends on the new 
package
  - Add Breaks/Replaces to the new package for the old non-transitional 
packages (be careful about the version number specification)
  - Keep Multi-Arch: same and Architecture: any for the transitional package
  - Write "QML module" instead of "QML plugin"
  - Rename also the *.install files

  ---
  One more example on naming:

  For example, the "test" (qtdeclarative5-test-plugin) in the old
  qtdeclarative5-style package naming became "qttest" (qml-module-
  qttest) in the new naming since the path is actually under
  /usr/lib/*/qt5/qml/QtTest/

  qml-module-qtquick-xmllistmodel has path
  /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have
  more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be
  qml-module-ubuntu-connectivity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+subscriptions

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

[Desktop-packages] [Bug 1370864] [NEW] Display gets messed upon undocking

2014-09-17 Thread Vadim Peretokin
Public bug reported:

Sometimes when I undock the laptop, the display gets messed up (see
attached screenshot). Restarting Unity doesn't help, it stays the same.
Mouse clicks are also off their location when this happens.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
Uname: Linux 3.17.0-031700rc3-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Sep 18 15:41:12 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:198f]
 Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (rev 
ff) (prog-if ff)
InstallationDate: Installed on 2014-06-26 (83 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ZBook 14
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.0-031700rc3-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/29/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.11
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.54
dmi.chassis.asset.tag: CNU424B3ZZ
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.11:bd04/29/2014:svnHewlett-Packard:pnHPZBook14:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 14
dmi.product.version: A3009DD10303
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.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.911-0intel1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Sep 18 14:38:14 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors: Screen 1 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: fglrx

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


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

** Attachment added: "Screenshot from 2014-09-18 14:37:22.png"
   
https://bugs.launchpad.net/bugs/1370864/+attachment/4207046/+files/Screenshot%20from%202014-09-18%2014%3A37%3A22.png

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

Title:
  Display gets messed upon undocking

Status in “unity” package in Ubuntu:
  New

Bug description:
  Sometimes when I undock the laptop, the display gets messed up (see
  attached screenshot). Restarting Unity doesn't help, it stays the
  same. Mouse clicks are also off their location when this happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  Uname: Linux 3.17.0-031700rc3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 18 15:41:12 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:198f]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] 
(rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-06-26 (83 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ZBook 14
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.17.0-031700rc3-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: un

[Desktop-packages] [Bug 1370859] Re: Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)

2014-09-17 Thread dino99
** Attachment added: "make.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1370859/+attachment/4207041/+files/make.log

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

Title:
  Error! Bad return status for module build on kernel: 3.16.0-16-generic
  (x86_64)

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Installing a new kernel 3.16.0.16 from a running gnome-shell session
  using the kernel 3.16.014, i'm getting:

  
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-generic 
/boot/vmlinuz-3.16.0-16-generic
  Error! Bad return status for module build on kernel: 3.16.0-16-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
  *

  As apport also fails to report that issue (it simply does nothing, it
  even does not start and does not warns either), i'm joining the crash
  file and make.log for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 18 07:13:23 2014
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370859] [NEW] Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)

2014-09-17 Thread dino99
Public bug reported:

Installing a new kernel 3.16.0.16 from a running gnome-shell session
using the kernel 3.16.014, i'm getting:


Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-16-generic 
/boot/vmlinuz-3.16.0-16-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-generic 
/boot/vmlinuz-3.16.0-16-generic
Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)
Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
*

As apport also fails to report that issue (it simply does nothing, it
even does not start and does not warns either), i'm joining the crash
file and make.log for details.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 18 07:13:23 2014
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages utopic

** Attachment added: "nvidia-331.0.crash"
   
https://bugs.launchpad.net/bugs/1370859/+attachment/4207038/+files/nvidia-331.0.crash

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

Title:
  Error! Bad return status for module build on kernel: 3.16.0-16-generic
  (x86_64)

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Installing a new kernel 3.16.0.16 from a running gnome-shell session
  using the kernel 3.16.014, i'm getting:

  
  Examining /etc/kernel/postinst.d.
  run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 
3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic
  run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-generic 
/boot/vmlinuz-3.16.0-16-generic
  Error! Bad return status for module build on kernel: 3.16.0-16-generic 
(x86_64)
  Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
  *

  As apport also fails to report that issue (it simply does nothing, it
  even does not start and does not warns either), i'm joining the crash
  file and make.log for details.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 18 07:13:23 2014
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 933209] Re: No sound after startup (audio device shown as Dummy Output)

2014-09-17 Thread no!chance
After upgrade to Ubuntu14.04 the sound device is broken. There is only a
dummy output available. Ubuntu12.04 worked fine.

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

Title:
  No sound after startup (audio device shown as Dummy Output)

Status in “alsa-driver” package in Ubuntu:
  Invalid
Status in “dbus” package in Ubuntu:
  Confirmed

Bug description:
  (testing from the ubuntu audio dev ppa)

  Running sudo alsa force-reload (or sudo killall pulseaudio) seems to
  be current workaround to get it to work

  hardware info (when sound is working):
  Code:
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
   Subsystem: Dell Device 02bb
   Flags: bus master, fast devsel, latency 0, IRQ 48
   Memory at f650 (64-bit, non-prefetchable) [size=16K]
   Capabilities: 
   Kernel driver in use: snd_hda_intel
   Kernel modules: snd-hda-intel
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf650 irq 49'
     Mixer name : 'IDT 92HD81B1C5'
     Components : 'HDA:111d76d5,102802bb,00100402'
     Controls  : 17
     Simple ctrls  : 9
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  Package: alsa-driver (not installed)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_SG.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
  Tags:  precise
  Uname: Linux 3.2.0-16-generic x86_64
  UpgradeStatus: Upgraded to precise on 2012-02-06 (10 days ago)
  UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare
  dmi.bios.date: 12/17/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0T052J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd12/17/2009:svnDellInc.:pnVostro1320:pvrNull:rvnDellInc.:rn0T052J:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro 1320
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1370852] Re: Scans all user accounts when not required

2014-09-17 Thread Robert Ancell
This has occurred since LightDM 1.9.8

** Branch linked: lp:~robert-ancell/lightdm/dont-scan-all-users

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

Title:
  Scans all user accounts when not required

Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.10 series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged

Bug description:
  On startup LightDM gets the list of users in the shared data code.
  This causes all the user properties to be loaded, in the case of not
  using accounts service all the .dmrc files are accessed.

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

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


[Desktop-packages] [Bug 1249208] Re: Avoid conflicting Space shortcut with g-s-d

2014-09-17 Thread Neal McBurnett
By overriding the upstream default of super-space to fix something for
one desktop, you've broken emacs, eclipse, NetBeans, and many others
that use ctrl-space on every other desktop it seems.  See bug 1278569.

Please fix this properly in Trusty, which is after all a Long Term
Support system, hardly fit for a "transitional solution".

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

Title:
  Avoid conflicting Space shortcut with g-s-d

Status in “ibus” package in Ubuntu:
  Fix Released
Status in “ibus” source package in Saucy:
  Triaged

Bug description:
  [Impact]
  Now we are using Space as the shortcut of switching IME forward, and 
the shortcut is handled twice: first in g-s-d and then in ibus. This leads to a 
conflict and the shortcut does not really work.

  [Test Case]
  Old behavior:
  Press Space does not have any effect of changing the IME forward.

  Expected behavior:
  After installing the updated package, user removes ibus configuration files 
in ~/.config/ibus and ~/.cache/ibus, and re-login to the system, Space 
should work for people who are using Unity or GNOME Shell.

  [Regression Potential]
  IBus may still push notification message about Space as the shortcut 
for users of other desktop, but the shortcut in effect would be Space 
when there is no other program grabbing the key press (like what g-s-d does).

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

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


[Desktop-packages] [Bug 1370852] [NEW] Scans all user accounts when not required

2014-09-17 Thread Robert Ancell
Public bug reported:

On startup LightDM gets the list of users in the shared data code. This
causes all the user properties to be loaded, in the case of not using
accounts service all the .dmrc files are accessed.

** Affects: lightdm
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Triaged

** Affects: lightdm/1.10
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Triaged

** Affects: lightdm (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Triaged

** Affects: lightdm (Ubuntu Trusty)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Triaged

** Affects: lightdm (Ubuntu Utopic)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Triaged

** Also affects: lightdm/1.10
   Importance: Undecided
   Status: New

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

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

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

** Changed in: lightdm (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: lightdm (Ubuntu Utopic)
   Importance: Undecided => High

** Changed in: lightdm/1.10
   Importance: Undecided => High

** Changed in: lightdm
   Importance: Undecided => High

** Changed in: lightdm
   Status: New => Triaged

** Changed in: lightdm/1.10
   Status: New => Triaged

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

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

** Changed in: lightdm
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm (Ubuntu Trusty)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm (Ubuntu Utopic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: lightdm/1.10
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Scans all user accounts when not required

Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.10 series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged

Bug description:
  On startup LightDM gets the list of users in the shared data code.
  This causes all the user properties to be loaded, in the case of not
  using accounts service all the .dmrc files are accessed.

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

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


[Desktop-packages] [Bug 1278569] Re: ibus breaks emacs and eclipse control-space keybinding

2014-09-17 Thread Neal McBurnett
Re: #20 - it looks like it is upstream that changed to super+space, not Debian:
 https://github.com/ibus/ibus/releases

1.5.3: Release 1.5.3  Takao Fujiwara fujiwarat released this on Jul 26,
2013  This version changes the default hotkey from Control + space
to Super + space. You can customize the hotkey with ibus-setup.

The code changes (to more than just the xml file, Jorge) are here:

Defalut triggers key is changed to space. · f3d80dc · ibus/ibus
 https://github.com/ibus/ibus/commit/f3d80dc026853c1024cdf6bda31b1496939cb095

So Ubuntu is overriding upstream!  Why?

Aha - it is patched back to ctrl-space in patches/ibus-xx-ctrl-
space.patch as a "transitional solution in trusty" because of this bug
in gnome-settings-daemon I guess:

Bug #1249208 “Avoid conflicting Space shortcut with g-s-d...” : Bugs : 
“ibus” package : Ubuntu
 https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1249208

Trusty LTS is not a release to be doing transitional solutions in

This bug among other things has caused me to lose data in emacs, because
set-mark-command doesn't work from ctrl-space like it has for what,
decades?  And my fingers expect it to continue to work that way.  I set
the mark and delete the region as a muscle macro.  Very dangerous.

This needs to work right for all the desktops, rather than breaking it
for everything except one desktop.

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

Title:
  ibus breaks emacs and eclipse control-space keybinding

Status in “ibus” package in Ubuntu:
  Triaged

Bug description:
  Installing ibus 1.5.5-1ubuntu1 breaks Emacs 24's control-space
  keybinding.  I generally have that bound to a custom lisp function,
  but by default (e.g. starting with `emacs -Q`) it is bound to set-
  mark-command.  After doing a dist-upgrade in Trusty which installs
  ibus 1.5.5-1ubuntu1, emacs no longer even sees the control-space key
  chord.  My guess is that ibus is consuming this event, preventing
  emacs from seeing it.  This is a critical regression that makes emacs
  almost unusable.

  By process of elimination, I've narrowed it down to one of these 4
  binary packages.

  gir1.2-ibus-1.0
  ibus
  ibus-gtk
  ibus-gtk3

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ibus 1.5.5-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 10 15:15:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-06 (66 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1294311] Re: Compiz process continuously uses too much cpu.

2014-09-17 Thread Xi
*** This bug is a duplicate of bug 1268146 ***
https://bugs.launchpad.net/bugs/1268146

I have the same problem with Kalle (jessica-2) 
When using second monitor the compiz and Xorg processes eating too much CPU

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

Title:
  Compiz process continuously uses too much cpu.

Status in Compiz:
  New
Status in “compiz” package in Ubuntu:
  Triaged

Bug description:
  cpu = AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
  ram = 6GB

  uname -r
  Linux 3.13.0-17-generic #37-Ubuntu SMP Mon Mar 10 21:44:01 UTC 2014 x86_64 
x86_64 x86_64 GNU/Linux

  lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  apt-cache policy compiz
  compiz:
Instaŀlat: 1:0.9.11+14.04.20140310-0ubuntu1
Candidat:  1:0.9.11+14.04.20140310-0ubuntu1
Taula de versió:
   *** 1:0.9.11+14.04.20140310-0ubuntu1 0
  500 http://es.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Compiz proces is always using too much cpu. 

  Some examples:
  - When I use ALT+F2 and I type something compiz uses 170% cpu.
  - When I use ALT+TAB compiz uses 120% cpu.
  - While I'm writing this text compiz is using 30% cpu
  - My system running only a terminal with top but compiz using 12% cpu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11+14.04.20140310-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Mar 18 20:01:47 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   NVIDIA Corporation G72 [GeForce 7200 GS / 7300 SE] [10de:01d3] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. Device [19da:5001]
  InstallationDate: Installed on 2014-03-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7369
  ProcEnviron:
   LANGUAGE=ca
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-17-generic 
root=UUID=65b6b4ee-5d53-4762-8b40-e5d13e0035c3 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.9
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7369
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.9:bd03/17/2009:svnMSI:pnMS-7369:pvr1.0:rvnMSI:rnMS-7369:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7369
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Mar 18 19:55:32 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu7
  xserver.video_driver: nouveau

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

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

[Desktop-packages] [Bug 1026046] Re: Missing support for thumb resting on bottom of clickpad

2014-09-17 Thread onggie
Just found this solution for me  so I can reset my finger on the
touchpad

sudo modprobe -r psmouse
sudo modprobe psmouse proto=imps

Though it seems like I need to run this after every reboot. So I create
a config file in /etc/modprobe.d with the following;

options psmouse proto=imps

But after I restart, it reverts again.

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

Title:
  Missing support for thumb resting on bottom of clickpad

Status in xf86-input-synaptics:
  Unknown
Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-input-synaptics” source package in Precise:
  Confirmed
Status in “xserver-xorg-input-synaptics” package in Debian:
  New

Bug description:
  When using the trackpad on the MacBook Pro In Mac OS X it is possible to have 
the thumb resting (ready to click) on the bottom part of the touchpad while 
moving the mouse pointer around with your index or middle finger. 
  Likewise it is also possible to use two finger scrolling with the index and 
middle finger on the upper part on the track pad while resting the thumb on the 
lower part of the trackpad.

  This behaviour is not currently supported with the synaptics driver in
  12.04. It wil register a two finger scroll when the thumb is resting
  in the bottom part and index finger moves around in the upper part.

  I have tried playing aroud with the setting AreaBottomEdge that
  disables all motion on the bottom part of the touchpad. Unfortunately
  when this setting is enabled it still detects a finger in the area, so
  it wil register a two finger scroll like before.

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

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


[Desktop-packages] [Bug 1363070] Re: USB Mouse cursor jumps and buttons get deactivated with two PS/2 devices connected

2014-09-17 Thread Carl Ponder
Here's some info that actually makes sense, it says that the wheel-mice
use a 4-byte protocol and the Touchpad uses a 3-byte protocol. This
could explain how the driver could get confused. Anyone comment?

http://blogs.msdn.com/b/oldnewthing/archive/2004/09/17/230839.aspx

Yeah, this is a Windows-affiliated website, but the electronics sounds like an 
OS-independent issue.
One question is whether the problem re-occurs the first time that you 
inadvertantly touch the Touchpad.

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

Title:
  USB Mouse cursor jumps and buttons get deactivated with two PS/2
  devices connected

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This happens when two PS/2 devices are connected at the same time and a USB 
mouse is primarily used (eg using a Laptop with a PS/2 touchpad with an 
external USB mouse)
  Symptoms: after a while (can be 10 minutes or 1 hour) the mouse cursor starts 
randomly to jump (mostly down) and up and then the mouse buttons get 
deactivated (clicking does not have any effect). In that case, moving the mouse 
marks the underlying text (thus imitating a continuous left-click). This 
malbehaviour can be temporarily stopped when shortly using one PS/2 device. 
After a while the same symptoms reappear.

  Setup:
  Dell D430 docked to a Dell D/dock PD01x. The second PS/2 device is an 
(switched off) Logitech TrackMan Live! (infrared mouse connected via a PS/2 
receiver). 
  This bug appears under 12.04 LTS Unity and 14.04 with Xfce, KDE or Unity 
(always using the latest kernels). Using KDE the bug appears more often than 
when using XFCE.

  To resolve the issue:
  disconnect the external Trackman Live PS/2 device from the docking station.

  This bug drove me crazy. Only by accident I disconnected the Trackman
  and since then my USB mouse works well again. I verified that the bug
  reappears as soon as I connect the TrackMan again and I used different
  USB mice (as I thought that it might be a USB problem). It did not
  happen under Windows, so it is not hardware related.

  If this bug is going to be followed up I can test with a normal PS/2
  mouse (instead of the TrackMan Live) if the same bug happens or would
  be happy to provide logging data.

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

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


[Desktop-packages] [Bug 1363070] Re: USB Mouse cursor jumps and buttons get deactivated with two PS/2 devices connected

2014-09-17 Thread Carl Ponder
I have a Dell Latitude E6500.
I'd seen this problem with my 3-button IBM USB mouse, but it went away when I 
upgraded from Ubuntu 10.04 to 12.04.
I have another external IBM USB mouse, this one with a wheel, and am still 
seeing the problem.
So far I can temporarily stop the problem by un-plugging & re-plugging the 
mouse; I can also temporarily stop the problem with the command

xinput set-prop 13 "Device Enabled" 0

One thing to note is that the temporary fix works even if the device number 
DOES NOT match the AlpsPS/2 ALPS DualPoint TouchPad. I don't believe the issue 
is a conflict between the two devices for this reason.
I think that the mouse-driver is getting into some crudded-up state that gets 
reset when I unplug/replug the device or if I run the above "xinput" command.
My best guess is that Ubuntu has real drivers for some mice and uses a buggy 
default-driver for anything else, and 12.04 included a driver for my first 
mouse but not my second mouse. Can anyone at Ubuntu confirm this? Or give us a 
better explanation?

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

Title:
  USB Mouse cursor jumps and buttons get deactivated with two PS/2
  devices connected

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This happens when two PS/2 devices are connected at the same time and a USB 
mouse is primarily used (eg using a Laptop with a PS/2 touchpad with an 
external USB mouse)
  Symptoms: after a while (can be 10 minutes or 1 hour) the mouse cursor starts 
randomly to jump (mostly down) and up and then the mouse buttons get 
deactivated (clicking does not have any effect). In that case, moving the mouse 
marks the underlying text (thus imitating a continuous left-click). This 
malbehaviour can be temporarily stopped when shortly using one PS/2 device. 
After a while the same symptoms reappear.

  Setup:
  Dell D430 docked to a Dell D/dock PD01x. The second PS/2 device is an 
(switched off) Logitech TrackMan Live! (infrared mouse connected via a PS/2 
receiver). 
  This bug appears under 12.04 LTS Unity and 14.04 with Xfce, KDE or Unity 
(always using the latest kernels). Using KDE the bug appears more often than 
when using XFCE.

  To resolve the issue:
  disconnect the external Trackman Live PS/2 device from the docking station.

  This bug drove me crazy. Only by accident I disconnected the Trackman
  and since then my USB mouse works well again. I verified that the bug
  reappears as soon as I connect the TrackMan again and I used different
  USB mice (as I thought that it might be a USB problem). It did not
  happen under Windows, so it is not hardware related.

  If this bug is going to be followed up I can test with a normal PS/2
  mouse (instead of the TrackMan Live) if the same bug happens or would
  be happy to provide logging data.

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

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


[Desktop-packages] [Bug 1340544] Re: gnome-rr: Normalize the minimum brightness level.

2014-09-17 Thread Shih-Yuan Lee
I found this issue is fixed in Linux kernel.
Please see 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6dda730e55f412a6dfb181cae6784822ba463847.

** Changed in: unity-settings-daemon
   Status: Incomplete => Invalid

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  gnome-rr: Normalize the minimum brightness level.

Status in GNOME Desktop Common Files:
  New
Status in Gnome Settings Daemon:
  Fix Released
Status in Unity Settings Daemon:
  Invalid
Status in “gnome-desktop3” package in Ubuntu:
  Invalid

Bug description:
  This patch is aimed to normalize the minimum brightness level for 20
  brightness steps used in gnome-settings-daemon and bring a better and
  consistent user experience for the brigtness control in
  gnome-settings-daemon and gnome-control-center.

  For example, most Intel Haswell/Broadwell UMA laptops have the same 937
  value as their maximum brightness level on Linux kernel 3.16 by default.

  By this patch, the minimum brightness level will be changed to 17
  because 937 / 20 == 46 and 937 % 46 == 17, and 17 is a reasonable and
  visible brightness level as the minimum brightness level on these laptops.
  If we set 0 to /sys/class/backlight/intel_backlight/brightness, it makes
  the screen off.
  If we set 1 to /sys/class/backlight/intel_backlight/brightness, the
  screen becomes hard to see the content.
  So 17 is a better brightness level.

  This patch should not affect existing ACPI brightness control especially
  for those laptops having the maximum brightness level under 20.

  This also avoided the screen off when using the minimum brightness
  level under some condition.

  Quotes from
  http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt

  "This property controls the brightness on laptop panels and equivalent
   displays with a backlight controller. The driver specific maximum
   value MUST turn the backlight to full brightness, 1 SHOULD turn the
   backlight to minimum brightness, 0 SHOULD turn the backlight off."

  Quotes from http://msdn.microsoft.com/en-
  us/library/windows/hardware/ff569755(v=vs.85).aspx

  "Brightness levels are represented as single-byte values in the range
   from zero to 100 where zero is off and 100 is the maximum brightness
   that a laptop computer supports. Every laptop computer must report a
   maximum brightness level of 100; however, a laptop computer is not
   required to support a level of zero. The only requirement for values
   from zero to 100 is that larger values must represent higher brightness
   levels."

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

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


[Desktop-packages] [Bug 1370814] Re: Xorg crashed with SIGABRT in xf86DeleteScreen()

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1353926 ***
https://bugs.launchpad.net/bugs/1353926

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1353926
   Xorg on haswell freezes on high load, restart attempts fail

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in xf86DeleteScreen()

Status in “xorg-server” package in Ubuntu:
  New

Bug description:
  Nothing, I just logged into newly installed ubuntu and saw the report
  dialog.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep 18 10:03:58 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:131d]
  InstallationDate: Installed on 2014-09-17 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140916)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b40a Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550LA
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/drivers/intel_drv.so
   xf86DeleteScreen ()
   InitOutput ()
   ?? ()
   __libc_start_main (main=0x7f0d687b7680, argc=11, argv=0x7fff7da878c8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff7da878b8) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in xf86DeleteScreen()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550LA.509
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550LA.509:bd06/26/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libg

[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread sohel
@Alberto Milone
I never installed bumblebee, mine is a clean/default ubuntu 14.04 installation. 
I wonder how bumblebee shows up in log. None of bumblebee's binaries also shows 
on terminal.

nogpumanager did not work

please let me know if any other solution

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1350369] Re: [Upstream] soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()

2014-09-17 Thread Christopher M. Penalver
** Summary changed:

- soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()
+ [Upstream] soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()

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

Title:
  [Upstream] soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  Was trying to reproduce this bug:
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/64295 I've
  caused an outright crash.

  Open document
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/64295/+attachment/18400/+files/20061006_final_pres_handout.odt

  1. Put cursor at box under "Joe Selects Option A"
  1. Edit -> Select All (which should select the whole table)
  2. Copy
  3. Put cursor at box under "Joe Selects Option A"
  4. Paste
  5. Undo
  6. Paste
  7. Undo (note how items are left)
  8. Paste
  9. Undo (crashes)

  The cursor might also move around during the above.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: libreoffice-core 1:4.2.4-0ubuntu4
  Uname: Linux 3.16.0-999-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 30 10:07:36 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-04-27 (93 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer 
/tmp/20061006_final_pres_handout.odt --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7f9664eeccaa <_SaveBox::CreateNew(SwTable&, 
SwTableLine&, _SaveTable&)+74>:  mov0x18(%rax),%r15
   PC (0x7f9664eeccaa) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%r15" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   _SaveBox::CreateNew (this=0x2bf5b20, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/inc/swtable.hxx:417
   _SaveBox::CreateNew (this=0x29fda30, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1369
   _SaveBox::CreateNew (this=0x220b6e0, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1369
   _SaveBox::CreateNew (this=0x29f7360, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1369
   _SaveLine::CreateNew (this=0x2be65c0, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1196
  Title: soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()
  UpgradeStatus: Upgraded to utopic on 2014-07-20 (9 days ago)
  UserGroups: adm cdrom debian-tor dip disk libvirtd lpadmin plugdev sambashare 
sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1350369/+subscriptions

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


[Desktop-packages] [Bug 366963] Re: nautilus "open with" property no longer available for folders

2014-09-17 Thread José Alburquerque
The workaround that I found is using the nautilus-actions package.  It
makes it possible to define actions to take for  files that match a
specific criteria (even folders).  When a file is right clicked, if it
matches a predefined criteria, the specified action will appear under a
menu called "Nautilus-Actions actions" in the popup menu.  This is the
closest to the original functioning that I've been able to find.

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

Title:
  nautilus "open with" property no longer available for folders

Status in Nautilus:
  Won't Fix
Status in “nautilus” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: nautilus

  After upgrading to ubuntu 9.04 (amd64), nautilus "open with" property
  is no longer available for folders.

  How to reproduce: 
  - open a nautilus window
  - right click on any folder icon and choose properties
  - observe that there is no longer a tab called "Open With"

  All previous ubuntu versions had this property tab so I think this is
  a bug.

  I need the "Open With" property tab to be able to delete entries in
  Nautilus' "Open With" context menu.

  For example, I use nautilus' context menu to open (associate) a media
  folder with my music player (audacious), so that the player plays all
  the music files in that folder. Similarly with photograph folders and
  so on.

  With Jaunty, there is no way I can find to remove any of the "Open
  With" entries in nautilus context menu for Folders. Note that the
  "Open With" property tab still works fine for regular files; the only
  problem now is with folders.

  Please give us back the "Open With" property for folders!

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

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


[Desktop-packages] [Bug 1370780] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1370281 ***
https://bugs.launchpad.net/bugs/1370281

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  This happens when I login to my computer. Running Utopic with the
  latest packages. Please contact me if you need additional information.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Sep 17 19:20:06 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.16: added
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] 
(prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2010]
  InstallationDate: Installed on 2012-09-16 (731 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  MachineType: BIOSTAR Group A770E3
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-29-generic 
root=/dev/mapper/ubuntu-root ro quiet splash radeon.dpm=1 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom debian-tor dip libvirtd lpadmin plugdev 
sambashare sudo vboxusers
  dmi.bios.date: 04/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A770E3
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd04/21/2010:svnBIOSTARGroup:pnA770E3:pvr:rvnBIOSTARGroup:rnA770E3:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.name: A770E3
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56+git1409171830.ae8edc~gd~u
  version.libgl1-mesa-dri: libgl1-mesa-dr

[Desktop-packages] [Bug 1370765] [NEW] I have problems with audio sw music . I usegarden despite using Jack and qsinth for probrammi that require them[EasyNote MH36, Realtek ALC272, Speaker, Internal]

2014-09-17 Thread gian luca
Public bug reported:

used the sw version is 4.14 lts

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gian   1810 F pulseaudio
CurrentDesktop: Unity
Date: Thu Sep 18 01:04:10 2014
InstallationDate: Installed on 2014-05-13 (127 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=it
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Audio interno - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gian   1810 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [EasyNote MH36, Realtek ALC272, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to trusty on 2014-07-29 (50 days ago)
dmi.bios.date: 12/22/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: PBPE2L0N.P07
dmi.board.name: PE2L
dmi.board.vendor: PACKARD BELL BV
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: PACKARD BELL BV
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrPBPE2L0N.P07:bd12/22/2008:svnPACKARDBELLBV:pnEasyNoteMH36:pvrPC36Q01406:rvnPACKARDBELLBV:rnPE2L:rvr:cvnPACKARDBELLBV:ct1:cvrN/A:
dmi.product.name: EasyNote MH36
dmi.product.version: PC36Q01406
dmi.sys.vendor: PACKARD BELL BV

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


** Tags: apport-bug i386 trusty

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

Title:
  I have problems with audio sw music . I usegarden despite using Jack
  and qsinth for probrammi that require them[EasyNote MH36, Realtek
  ALC272, Speaker, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  used the sw version is 4.14 lts

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gian   1810 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Sep 18 01:04:10 2014
  InstallationDate: Installed on 2014-05-13 (127 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Audio interno - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gian   1810 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [EasyNote MH36, Realtek ALC272, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-07-29 (50 days ago)
  dmi.bios.date: 12/22/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: PBPE2L0N.P07
  dmi.board.name: PE2L
  dmi.board.vendor: PACKARD BELL BV
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: PACKARD BELL BV
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrPBPE2L0N.P07:bd12/22/2008:svnPACKARDBELLBV:pnEasyNoteMH36:pvrPC36Q01406:rvnPACKARDBELLBV:rnPE2L:rvr:cvnPACKARDBELLBV:ct1:cvrN/A:
  dmi.product.name: EasyNote MH36
  dmi.product.version: PC36Q01406
  dmi.sys.vendor: PACKARD BELL BV

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

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


[Desktop-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

2014-09-17 Thread Alan Pope ʕ•͡ᴥ•ʔ
I'm getting this on my intel based X220 when running this game demo:-

http://www.imake-games.com/nubs-adventure/

To reproduce download 
http://www.imake-games.com/nubs/earlyBuilds/NubsAdventureEarlyAccess.jar.zip
Unzip it then run it with 

java -jar NubsAdventureEarlyAccess.jar

The game graphics are corrupted (as seen in the attached screenshot) and
I get the same "_xgeWireToEvent: Unknown extension 148, this should
never happen." error in the terminal. Easily reproduced, doesn't happen
on nVidia based desktop

** Attachment added: "Screenshot from 2014-09-17 23:52:58.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1369113/+attachment/4206854/+files/Screenshot%20from%202014-09-17%2023%3A52%3A58.png

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852

[Desktop-packages] [Bug 1370758] Re: Sound settings lost after suspend

2014-09-17 Thread Yanpas
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Sound settings lost after suspend

Status in “pavucontrol” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  My dedault mic is usb camera. But after suspend default microphone is
  becoming empty IN in motherboard. Is there any other sound settings
  app for Xubuntu?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pavucontrol 2.0-2
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Sep 18 02:50:27 2014
  InstallationDate: Installed on 2014-08-17 (31 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  SourcePackage: pavucontrol
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370175] Re: Libav security fixes Sept 2014

2014-09-17 Thread Seth Arnold
Massimiliano, this bug is to track a libav update. If you wish to report
a problem please start a new bug with "ubuntu-bug xorg".

Thanks

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

Title:
  Libav security fixes Sept 2014

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libav” source package in Precise:
  Fix Released
Status in “libav” source package in Trusty:
  Confirmed
Status in “libav” source package in Utopic:
  Confirmed

Bug description:
  Libav 9.17 and 0.8.16 are out, and fix "a number of critical
  functional and security issues (many of which have CVE identifiers
  assigned)"

  http://www.libav.org/news.html

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

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


[Desktop-packages] [Bug 1370175] Re: Libav security fixes Sept 2014

2014-09-17 Thread massimiliano
my notebook's touchpad doesn't work after installing Ubuntu 12.04.5 LTS.
I have a notebook hp 250.

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

Title:
  Libav security fixes Sept 2014

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libav” source package in Precise:
  Fix Released
Status in “libav” source package in Trusty:
  Confirmed
Status in “libav” source package in Utopic:
  Confirmed

Bug description:
  Libav 9.17 and 0.8.16 are out, and fix "a number of critical
  functional and security issues (many of which have CVE identifiers
  assigned)"

  http://www.libav.org/news.html

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

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


[Desktop-packages] [Bug 1362321] Re: color management patch breaks PPD updating via web-interface in CUPS 1.7

2014-09-17 Thread Launchpad Bug Tracker
This bug was fixed in the package cups - 1.7.5-2

---
cups (1.7.5-2) unstable; urgency=medium


  [ Helge Kreutzmann ]
  * Update German man page (1537t)

  [ Till Kamppeter ]
  * Updated color management extension patch to the newest version from Joseph
Simon, especially to fix PPD updates via the web interface (LP: #1362321).

  [ Didier Raboud ]
  * Replace the RedHat patch restoring the access to cupsd.conf and logfiles
with upstream's

 -- Didier Raboud   Wed, 17 Sep 2014 13:37:01 +0200

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

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

Title:
  color management patch breaks PPD updating via web-interface in CUPS
  1.7

Status in “cups” package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:

  1. Build CUPS 1.7.x with color-management-extension.patch as it is provided 
by current utopic build.  
  Alternatively: install daily build of Utopic server.

  2. Add a printer
  3. Try changing printer's driver (PPD) via web interface to a different PPD. 

  CUPS says that printer was updated successfully, but printer won't
  change its PPD. You will also notice a forgotten /tmp/temp.ppd file
  on your filesystem.

  Removing this patch fixes the problem.

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

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


[Desktop-packages] [Bug 1329044] Re: Window is not reducible to a reasonable size since 14.04 64-bit

2014-09-17 Thread Christian
Can confirm this on frshly installed Xubuntu, tried with 1:3.10.2-0ubuntu3.1 
and 1:3.12.3-0ubuntu1
It looks ugly at best and changing the gsettings value to a sensible width has 
no effect (and gets set back to 1127 after start).

** Changed in: gnome-sudoku (Ubuntu)
   Status: New => Confirmed

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

Title:
  Window is not reducible to a reasonable size since 14.04 64-bit

Status in “gnome-sudoku” package in Ubuntu:
  Confirmed

Bug description:
  The Sudoku window appears too big, and is not resizeable, at least on my 
german Ubuntu version.
  This is a regression against 12.04.

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

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


[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup

2014-09-17 Thread Mathew Hodson
** Tags removed: ubuntu

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

Title:
  Touchscreen controls both screens in dual-monitor setup

Status in Gnome Settings Daemon:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project trusty series:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” source package in Trusty:
  Confirmed
Status in “unity-settings-daemon” source package in Trusty:
  Fix Released

Bug description:
  SRU Request:

  Laptops and all-in-one systems with touchscreens don't currently map
  the touch input device onto the internal display. As a result, when
  the screen changes (e.g. the main output is rotated or an external
  output is connected), the touch input device maps onto the entire
  screen, regardless of the only relevant area, thus making the
  touchscreen completely useless.

  [Impact]
   * The touchscreen becomes unusable if an external output is connected or if 
the main output is rotated.

  [Test Case]
   * Either plug in an external monitor or rotate the internal monitor
  - Expected: the touchscreen should respond to touch as usual.
  - Bad behavior: the touchscreen is unusable and responds by selecting 
areas other than the one the user actually selects.

  [Regression Potential]
   * Low, it only affects the main touchscreen (tablets or multiple 
touchscreens are not supported) and it only adds a feature that is currently 
missing.

  [Other Info]
   * N/A

  ---

  My laptop has a touchscreen. It works fine in 14.04 until I plug in an
  external monitor. When using an external monitor, input from the
  touchscreen is remapped so that the touchscreen provides input to both
  monitors. The result is that there is no longer a 1:1 correspondence
  between moving your finger and the cursor. This is confusing and
  difficult to use.

  A touchscreen is a direct input device (vs an indirect one like a
  mouse/touchpad); input from the touchscreen should be bound to the
  physical display that it's attached to.

  To reproduce:
  1) On a computer with a touchscreen, use the touchscreen to move a window 
around, including to the edges of the screen. Note that the window moves 
exactly with your finger.
  2) Plug in an external monitor
  3) Try the same actions as in step 1

  Expected results:
  The touchscreen continues to operate as in step 1, allowing you to manipulate 
items on the display that contains the touchscreen. The touchscreen does not 
interact with windows, etc on the external monitor

  Actual results:
  The touchscreen is remapped across both displays. The result is that touch 
events no longer happen 'under the finger'. Assuming the two displays are the 
same size and resolution, moving your finger 1cm will cause the window or other 
objects to move 2cm onscreen. It becomes impossible to use the touchscreen to 
interact with widgets (menus, buttons, etc).

  This is described in couple places:
  
http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system
  
http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xinput 1.6.1-1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: 
[core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar  3 14:41:14 2014
  DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, 
x86_64: installed
   virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed
   virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2013-12-02 (90 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Bina

[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Fabio
I tried again in my main partition and it works (just seems to take few
seconds longer under the plymouth screen).


** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+attachment/4206790/+files/Xorg.0.log

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Fabio
** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+attachment/4206791/+files/gpu-manager.log

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1309488] Re: [HP EliteBook 8760w, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

2014-09-17 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/1309488

Title:
  [HP EliteBook 8760w, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Although I see in volume control that there is some kind of audio
  ouput, I don't here anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  frank  2797 F pulseaudio
   /dev/snd/pcmC1D3p:   frank  2797 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Fri Apr 18 13:50:22 2014
  InstallationDate: Installed on 2014-03-19 (29 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Turks/Whistler HDMI Audio [Radeon HD 6000 Series] - HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [HP EliteBook 8760w, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (0 days ago)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SAD Ver. F.42
  dmi.board.name: 1630
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3C
  dmi.chassis.asset.tag: CNU1350J01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SADVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8760w:pvrA0001C02:rvnHewlett-Packard:rn1630:rvrKBCVersion01.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8760w
  dmi.product.version: A0001C02
  dmi.sys.vendor: Hewlett-Packard

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

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


[Desktop-packages] [Bug 1370721] Re: compiz crashed after start (reboot)

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1370281 ***
https://bugs.launchpad.net/bugs/1370281

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed after start (reboot)

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Due to missing the "alternate installer" 14.10 was installed with
  Lubuntu and is currently converted into Ubuntu/Unity.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Sep 17 23:22:39 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:024d]
 Subsystem: Dell Device [1028:024d]
  InstallationDate: Installed on 2014-09-17 (0 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140731.3)
  MachineType: Dell Inc. Latitude E4300
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_AT:de
   XDG_RUNTIME_DIR=
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic 
root=/dev/mapper/R13VolGrp-System ro rootflags=subvol=@ quiet splash 
vt.handoff=7
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/27/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0D217R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd09/27/2011:svnDellInc.:pnLatitudeE4300:pvr:rvnDellInc.:rn0D217R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E4300
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Sep 17 23:22:07 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17921 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1

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

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


[Desktop-packages] [Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M

2014-09-17 Thread giacof
** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+attachment/4206786/+files/gpu-manager.log

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

Title:
  nvidia prime broken: kserver crash with Quadro K1100M

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  uname -a
  Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  apt-cache policy nvidia-331 nvidia-prime
  nvidia-331:
Installato: 331.38-0ubuntu7.1
Candidato:  331.38-0ubuntu7.1
Tabella versione:
   *** 331.38-0ubuntu7.1 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   331.38-0ubuntu7 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 
Packages
  nvidia-prime:
Installato: 0.6.2
Candidato:  0.6.2
Tabella versione:
   *** 0.6.2 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  cat /var/log/prime-supported.log
  Requires offloading

  lspci -v
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0
  Capabilities: 

  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode])
  Flags: bus master, fast devsel, latency 0
  Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
  I/O behind bridge: e000-efff
  Memory behind bridge: f300-f40f
  Prefetchable memory behind bridge: d000-e1ff
  Capabilities: 
  Kernel driver in use: pcieport

  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 255
  Memory at f540 (64-bit, non-prefetchable) [size=4M]
  Memory at c000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  Expansion ROM at  [disabled]
  Capabilities: 

  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 52
  Memory at f7734000 (64-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel

  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04) (prog-if 30 [XHCI])
  Subsystem: Dell Device 05cc
  Flags: bus master, medium devsel, latency 0, IRQ 47
  Memory at f772 (64-bit, non-prefetchable) [size=64K]
  Capabilities: 
  Kernel driver in use: xhci_hcd

  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 49
  Memory at f774 (64-bit, non-prefetchable) [size=16]
  Capabilities: 
  Kernel driver in use: mei_me

  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 
(rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 50
  Memory at f770 (32-bit, non-prefetchable) [size=128K]
  Memory at f773d000 (32-bit, non-prefetchable) [size=4K]
  I/O ports at f080 [disabled] [size=32]
  Capabilities: 
  Kernel driver in use: e1000e

  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04) (prog-if 20 [EHCI])
  Subsystem: Dell Device 05cc
  Flags: bus master, medium devsel, latency 0, IRQ 16
  Memory at f773c000 (32-bit, non-prefetchable) [size=1K]
  Capabilities: 
  Kernel driver in use: ehci-pci

  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 51
  Memory at f773 (64-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d4) (prog-if 00 [Normal decode])
  Flags: bus master, fast devsel, latency 0
  Bus: primary=00, secondary=02, subordinate=02,

[Desktop-packages] [Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M

2014-09-17 Thread giacof
** Attachment added: "x-0-greeter.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+attachment/4206787/+files/x-0-greeter.log

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

Title:
  nvidia prime broken: kserver crash with Quadro K1100M

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  uname -a
  Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  apt-cache policy nvidia-331 nvidia-prime
  nvidia-331:
Installato: 331.38-0ubuntu7.1
Candidato:  331.38-0ubuntu7.1
Tabella versione:
   *** 331.38-0ubuntu7.1 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   331.38-0ubuntu7 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 
Packages
  nvidia-prime:
Installato: 0.6.2
Candidato:  0.6.2
Tabella versione:
   *** 0.6.2 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  cat /var/log/prime-supported.log
  Requires offloading

  lspci -v
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0
  Capabilities: 

  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode])
  Flags: bus master, fast devsel, latency 0
  Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
  I/O behind bridge: e000-efff
  Memory behind bridge: f300-f40f
  Prefetchable memory behind bridge: d000-e1ff
  Capabilities: 
  Kernel driver in use: pcieport

  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 255
  Memory at f540 (64-bit, non-prefetchable) [size=4M]
  Memory at c000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  Expansion ROM at  [disabled]
  Capabilities: 

  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 52
  Memory at f7734000 (64-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel

  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04) (prog-if 30 [XHCI])
  Subsystem: Dell Device 05cc
  Flags: bus master, medium devsel, latency 0, IRQ 47
  Memory at f772 (64-bit, non-prefetchable) [size=64K]
  Capabilities: 
  Kernel driver in use: xhci_hcd

  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 49
  Memory at f774 (64-bit, non-prefetchable) [size=16]
  Capabilities: 
  Kernel driver in use: mei_me

  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 
(rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 50
  Memory at f770 (32-bit, non-prefetchable) [size=128K]
  Memory at f773d000 (32-bit, non-prefetchable) [size=4K]
  I/O ports at f080 [disabled] [size=32]
  Capabilities: 
  Kernel driver in use: e1000e

  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04) (prog-if 20 [EHCI])
  Subsystem: Dell Device 05cc
  Flags: bus master, medium devsel, latency 0, IRQ 16
  Memory at f773c000 (32-bit, non-prefetchable) [size=1K]
  Capabilities: 
  Kernel driver in use: ehci-pci

  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 51
  Memory at f773 (64-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d4) (prog-if 00 [Normal decode])
  Flags: bus master, fast devsel, latency 0
  Bus: primary=00, secondary=02, subordinate=02,

[Desktop-packages] [Bug 1370725] [NEW] nvidia prime broken: kserver crash with Quadro K1100M

2014-09-17 Thread giacof
Public bug reported:

lsb_release -rd
Description:Ubuntu 14.04.1 LTS
Release:14.04

uname -a
Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 
x86_64 x86_64 GNU/Linux

apt-cache policy nvidia-331 nvidia-prime
nvidia-331:
  Installato: 331.38-0ubuntu7.1
  Candidato:  331.38-0ubuntu7.1
  Tabella versione:
 *** 331.38-0ubuntu7.1 0
500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
100 /var/lib/dpkg/status
 331.38-0ubuntu7 0
500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 
Packages
nvidia-prime:
  Installato: 0.6.2
  Candidato:  0.6.2
  Tabella versione:
 *** 0.6.2 0
500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

cat /var/log/prime-supported.log
Requires offloading

lspci -v
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
Subsystem: Dell Device 05cc
Flags: bus master, fast devsel, latency 0
Capabilities: 

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: e000-efff
Memory behind bridge: f300-f40f
Prefetchable memory behind bridge: d000-e1ff
Capabilities: 
Kernel driver in use: pcieport

00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
Subsystem: Dell Device 05cc
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at f540 (64-bit, non-prefetchable) [size=4M]
Memory at c000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at  [disabled]
Capabilities: 

00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
HD Audio Controller (rev 06)
Subsystem: Dell Device 05cc
Flags: bus master, fast devsel, latency 0, IRQ 52
Memory at f7734000 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel

00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04) (prog-if 30 [XHCI])
Subsystem: Dell Device 05cc
Flags: bus master, medium devsel, latency 0, IRQ 47
Memory at f772 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: xhci_hcd

00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Dell Device 05cc
Flags: bus master, fast devsel, latency 0, IRQ 49
Memory at f774 (64-bit, non-prefetchable) [size=16]
Capabilities: 
Kernel driver in use: mei_me

00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM (rev 
04)
Subsystem: Dell Device 05cc
Flags: bus master, fast devsel, latency 0, IRQ 50
Memory at f770 (32-bit, non-prefetchable) [size=128K]
Memory at f773d000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f080 [disabled] [size=32]
Capabilities: 
Kernel driver in use: e1000e

00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04) (prog-if 20 [EHCI])
Subsystem: Dell Device 05cc
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f773c000 (32-bit, non-prefetchable) [size=1K]
Capabilities: 
Kernel driver in use: ehci-pci

00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
Subsystem: Dell Device 05cc
Flags: bus master, fast devsel, latency 0, IRQ 51
Memory at f773 (64-bit, non-prefetchable) [size=16K]
Capabilities: 
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d4) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
I/O behind bridge: 2000-2fff
Memory behind bridge: bf20-bf3f
Prefetchable memory behind bridge: bf40-bf5f
Capabilities: 
Kernel driver in use: pcieport

00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d4) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=07, sec-latency=0
I/O behind bridge: d000-dfff
Memory behind bridge: f480-f53f
Pref

[Desktop-packages] [Bug 1370725] Re: nvidia prime broken: kserver crash with Quadro K1100M

2014-09-17 Thread giacof
** Attachment added: "x-0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1370725/+attachment/4206788/+files/x-0.log

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

Title:
  nvidia prime broken: kserver crash with Quadro K1100M

Status in “nvidia-prime” package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  uname -a
  Linux Work 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  apt-cache policy nvidia-331 nvidia-prime
  nvidia-331:
Installato: 331.38-0ubuntu7.1
Candidato:  331.38-0ubuntu7.1
Tabella versione:
   *** 331.38-0ubuntu7.1 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   331.38-0ubuntu7 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/restricted amd64 
Packages
  nvidia-prime:
Installato: 0.6.2
Candidato:  0.6.2
Tabella versione:
   *** 0.6.2 0
  500 http://it.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  cat /var/log/prime-supported.log
  Requires offloading

  lspci -v
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0
  Capabilities: 

  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06) (prog-if 00 [Normal decode])
  Flags: bus master, fast devsel, latency 0
  Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
  I/O behind bridge: e000-efff
  Memory behind bridge: f300-f40f
  Prefetchable memory behind bridge: d000-e1ff
  Capabilities: 
  Kernel driver in use: pcieport

  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller])
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 255
  Memory at f540 (64-bit, non-prefetchable) [size=4M]
  Memory at c000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  Expansion ROM at  [disabled]
  Capabilities: 

  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 52
  Memory at f7734000 (64-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel

  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 04) (prog-if 30 [XHCI])
  Subsystem: Dell Device 05cc
  Flags: bus master, medium devsel, latency 0, IRQ 47
  Memory at f772 (64-bit, non-prefetchable) [size=64K]
  Capabilities: 
  Kernel driver in use: xhci_hcd

  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 49
  Memory at f774 (64-bit, non-prefetchable) [size=16]
  Capabilities: 
  Kernel driver in use: mei_me

  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-LM 
(rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 50
  Memory at f770 (32-bit, non-prefetchable) [size=128K]
  Memory at f773d000 (32-bit, non-prefetchable) [size=4K]
  I/O ports at f080 [disabled] [size=32]
  Capabilities: 
  Kernel driver in use: e1000e

  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 04) (prog-if 20 [EHCI])
  Subsystem: Dell Device 05cc
  Flags: bus master, medium devsel, latency 0, IRQ 16
  Memory at f773c000 (32-bit, non-prefetchable) [size=1K]
  Capabilities: 
  Kernel driver in use: ehci-pci

  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 04)
  Subsystem: Dell Device 05cc
  Flags: bus master, fast devsel, latency 0, IRQ 51
  Memory at f773 (64-bit, non-prefetchable) [size=16K]
  Capabilities: 
  Kernel driver in use: snd_hda_intel

  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d4) (prog-if 00 [Normal decode])
  Flags: bus master, fast devsel, latency 0
  Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
 

[Desktop-packages] [Bug 1368020] Re: package fglrx-core 2:14.201-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2014-09-17 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/1368020

Title:
  package fglrx-core 2:14.201-0ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in “fglrx-installer” package in Ubuntu:
  Confirmed

Bug description:
  Keeps timing out during install.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: fglrx-core 2:14.201-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Wed Sep 10 23:01:24 2014
  DuplicateSignature: package:fglrx-core:2:14.201-0ubuntu1:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2014-09-03 (7 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta1 amd64 (20140828)
  SourcePackage: fglrx-installer
  Title: package fglrx-core 2:14.201-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370720] [NEW] unity-settings-daemon can deadlock if a modeset fails

2014-09-17 Thread Aaron Plattner
Public bug reported:

The system I used to reproduce this bug was a laptop with two display
devices (one DisplayPort, one DVI) connected to a docking station.

Dock the laptop.  unity-settings-manager triggers a display change to
extended mode.  Then, undock the laptop.  The following sequence of
events triggers a deadlock:

1. The system generates an ACPI event that video.ko turns into a display change 
hotkey press.
2. Something sees the display change hotkey event and calls 
unity-settings-manager via dbus.
3. The X driver sees the DVI monitor go away and updates the RandR 
configuration.
4. unity-settings-manager enters handle_fn_f7() and calls 
gnome_rr_screen_refresh().
5. gnome_rr_screen_refresh() sees that the configuration changed and calls the 
callbacks.
6. The X driver sees the DP monitor go away and updates the RandR configuration.
7. on_randr_event() tries to reconfigure the desktop with the DVI monitor 
disabled and the DP monitor enabled.
8. The RandR SetCrtcConfig call fails because it's trying to set a mode on a 
disconnected output.
9. apply_configuration() calls error_message(), which tries to pop up a dialog 
box.

Step #9 deadlocks because gnome_rr_screen_refresh() called XGrabServer()
in step #5.

Upstream gnome-settings-daemon fixed this with commit 
0f7cbfed5e5e76824e057ce9c570fad66ba001c6.
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0f7cbfed5e5e76824e057ce9c570fad66ba001c6

This change cherry-picks cleanly to unity-settings-daemon.

(as an aside, the video.ko display change hotkey events are entirely
pointless and probably deserve their own bug)

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  unity-settings-daemon can deadlock  if a modeset fails

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

Bug description:
  The system I used to reproduce this bug was a laptop with two display
  devices (one DisplayPort, one DVI) connected to a docking station.

  Dock the laptop.  unity-settings-manager triggers a display change to
  extended mode.  Then, undock the laptop.  The following sequence of
  events triggers a deadlock:

  1. The system generates an ACPI event that video.ko turns into a display 
change hotkey press.
  2. Something sees the display change hotkey event and calls 
unity-settings-manager via dbus.
  3. The X driver sees the DVI monitor go away and updates the RandR 
configuration.
  4. unity-settings-manager enters handle_fn_f7() and calls 
gnome_rr_screen_refresh().
  5. gnome_rr_screen_refresh() sees that the configuration changed and calls 
the callbacks.
  6. The X driver sees the DP monitor go away and updates the RandR 
configuration.
  7. on_randr_event() tries to reconfigure the desktop with the DVI monitor 
disabled and the DP monitor enabled.
  8. The RandR SetCrtcConfig call fails because it's trying to set a mode on a 
disconnected output.
  9. apply_configuration() calls error_message(), which tries to pop up a 
dialog box.

  Step #9 deadlocks because gnome_rr_screen_refresh() called
  XGrabServer() in step #5.

  Upstream gnome-settings-daemon fixed this with commit 
0f7cbfed5e5e76824e057ce9c570fad66ba001c6.
  
https://git.gnome.org/browse/gnome-settings-daemon/commit/?id=0f7cbfed5e5e76824e057ce9c570fad66ba001c6

  This change cherry-picks cleanly to unity-settings-daemon.

  (as an aside, the video.ko display change hotkey events are entirely
  pointless and probably deserve their own bug)

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

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


[Desktop-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation

2014-09-17 Thread Jamie Strandboge
** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Changed in: linux (Ubuntu)
   Importance: Critical => High

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

Title:
  [FFe] apparmor abstract, anonymous and netlink socket mediation

Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “isc-dhcp” package in Ubuntu:
  Fix Released
Status in “libvirt” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  In Progress
Status in “rsyslog” package in Ubuntu:
  Fix Released
Status in “tlsdate” package in Ubuntu:
  Fix Released

Bug description:
  Background: kernel and apparmor userspace updates to support abstract,
  anonymous and fine-grained netlink socket mediation. These packages
  are listed in one bug because they are related, but the FFes may be
  granted and the uploads may happen at different times.

  = apparmor userspace =
  Summary:
  This feature freeze exception is requested for abstract, anonymous and 
fine-grained netlink socket for apparmor userspace. When used with a compatible 
kernel, 'unix' and 'network netlink' rules are supported. When used without a 
compatible apparmor userspace (eg, on a trusty system with an utopic backport 
kernel), abstract, anonymous and fine-grained netlink socket mediation is not 
enforced (ie, you can use this userspace with an old kernel without any issues).

  Testing:
  * 14.10 system with current kernels lacking abstract, anonymous and 
fine-grained netlink socket mediation (non-Touch):
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE 
(exploratory manual testing, lxc, libvirt, etc)
  * 14.10 system kernel capable of supporting abstract, anonymous and 
fine-grained netlink socket mediation (non-Touch):
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS 
(includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc)
   * Verify everything in 
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE 
(except juju since it doesn't have policy itself)

  Justification:
  This feature is required to support comprehensive application confinement on 
Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest 
isolation which is fundamental to Ubuntu on Server/Cloud. This feature also 
adds a welcome improvement to administrators wishing to further protect their 
systems.

  Extra information:
  While the apparmor userspace and kernel changes to support abstract, 
anonymous and fine-grained netlink socket can happen at different times, the 
apparmor userspace upload must correspond with uploads for packages that ship 
AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages 
outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles 
have been tested to either work without modification to the policy or updated 
and tested to work with updated policy. Common rules will be added to the 
apparmor base abstraction such that most packages shipping apparmor policy will 
not require updating. These updates will be prepared, tested and published en 
masse via a silo ppa.

  = linux =
  Summary:
  This feature freeze exception is requested for abstract, anonymous and 
fine-grained netlink socket via apparmor in the kernel. When used with a 
compatible apparmor userspace, 'unix' and 'network netlink' rules are 
supported. When used without a compatible apparmor userspace (eg, on a trusty 
system with an utopic backport kernel), abstract, anonymous and fine-grained 
netlink socket mediation is not enforced (ie, you can use this kernel with an 
old userspace without any issues).

  Testing:
  * 14.04 system with backported kernel: TODO
   * test-apparmor.py: TODO (runs extensive tests (upstream and distro))
   * exploratory manual testing: TODO (networking, aa-enforce with firefox, 
firefox works, apparmor blocks access, etc)
   * aa-status: TODO
   * lxc: TODO (containers can be created, started, shutdown)
   * libvirt: TODO (VMs started via openstack, and test-libvirt.py from QRT 
passes all tests)
  * 14.10 system (non-Touch) with updated kernel:
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS 
(includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, 
etc)
  * 14.10 system (Touch) with updated kernel:
   * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS 
(includes click-apparmor, apparmor-easyprof-ubuntu, exploratory manual testing, 
etc)

  Justification:
  This feature is required to support comprehensive application confinement on 
Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest 
isolation which is fundamental to Ubuntu on Server/Cloud. This feature also 
a

[Desktop-packages] [Bug 1370709] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1370281 ***
https://bugs.launchpad.net/bugs/1370281

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  Upon start up this error was received before any other screen was
  shown to me including the ability to use the mouse or hear any system
  sounds.

  servant@The-Goddess:~$ lsb_release -rd
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

  servant@The-Goddess:~$ apt-cache policy compiz
  compiz:
Installed: 1:0.9.12+14.10.20140812-0ubuntu1
Candidate: 1:0.9.12+14.10.20140812-0ubuntu1
Version table:
   *** 1:0.9.12+14.10.20140812-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [   26.903562] systemd-logind[854]: Failed to start user service: Unknown 
unit: user@1000.service
   [   26.907680] systemd-logind[854]: New session c1 of user servant.
   [   26.907709] systemd-logind[854]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
   [   54.274607] show_signal_msg: 18 callbacks suppressed
   [   54.274613] compiz[1669]: segfault at 0 ip   (null) sp 
7fffa4a06728 error 14 in compiz[40+3000]
  Date: Wed Sep 17 17:00:28 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistUpgraded: 2014-09-17 16:59:08,782 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0504]
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron N5050
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=fde4ad50-344b-4e7f-b322-5bf18ffb521b ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmi

[Desktop-packages] [Bug 1354068] Re: /usr/bin/unity8:11:std::function:SlotWrapper:core::Signal:core::dbus::Signal:operator

2014-09-17 Thread Pat McGowan
** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided => Critical

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: media-player (Ubuntu)
   Status: New => Invalid

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

Title:
  
/usr/bin/unity8:11:std::function:SlotWrapper:core::Signal:core::dbus::Signal:operator

Status in Mir:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  New
Status in “media-player” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.00+14.10.20140805-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8c88c781c702b88274b020e223d66d63e2d34a33
  contains more details.

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

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


[Desktop-packages] [Bug 1132215] Re: rhythmbox crashes when syncing library to ipod

2014-09-17 Thread tatsu tatsu
Same here.

Ubuntu 14.04, iphone 3

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

Title:
  rhythmbox crashes when syncing library to ipod

Status in “rhythmbox” package in Ubuntu:
  Fix Released

Bug description:
  Rhythmbox crashes when I try to sync my music with my ipod 5th gen (w/
  video).  I'm running the development release of 13.04, looking for
  bugs and whatnot.  I did not have this problem before with any other
  version of rhythmbox or Ubuntu.

  The error generated is:

  (rhythmbox:4117): GLib-GObject-WARNING **: g_object_set_valist: construct 
property "encoding-target" for object `RBTrackTransferBatch' can't be set after 
construction
  Segmentation fault (core dumped)


  rhythmbox 2.98-0ubuntu3
  Ubuntu 13.04 raring ringtail

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: rhythmbox 2.98-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-7.14-generic 3.8.0
  Uname: Linux 3.8.0-7-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  Date: Sat Feb 23 13:53:50 2013
  InstallationDate: Installed on 2013-02-10 (12 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130210)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370692] [NEW] microphone does not work

2014-09-17 Thread strk
Public bug reported:

I can't get internal microphone of a laptop to receive audio

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf]
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  strk   3715 F pulseaudio
 /dev/snd/controlC0:  strk   3715 F pulseaudio
Date: Wed Sep 17 21:56:44 2014
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to trusty on 2014-08-04 (44 days ago)
dmi.bios.date: 12/12/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: Tag 12345
dmi.board.name: W740SU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: Galago UltraPro
dmi.product.version: galu1
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  microphone does not work

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  I can't get internal microphone of a laptop to receive audio

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-input-internal-mic.conf]
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  strk   3715 F pulseaudio
   /dev/snd/controlC0:  strk   3715 F pulseaudio
  Date: Wed Sep 17 21:56:44 2014
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to trusty on 2014-08-04 (44 days ago)
  dmi.bios.date: 12/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 529479] Re: Quadrapassel - ClutterGLX-CRITICAL error

2014-09-17 Thread Bug Watch Updater
** Changed in: gnome-games
   Status: New => Expired

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

Title:
  Quadrapassel - ClutterGLX-CRITICAL error

Status in GNOME Games:
  Expired
Status in “gnome-games” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-games

  When running quadrapassel from terminal a critical error is displayed.
  Qua version 2.29.6. Lucid kernel 2.6.32-14-generic #20-Ubuntu SMP Sat
  Feb 20 05:18:19 UTC 2010 x86_64 GNU/Linux. Using Nvidia 195.36.03
  display driver.

  Opened Applications-Accessories-Terminal and entered
  $ quadrapassel
  (quadrapassel:2024): ClutterGLX-CRITICAL **: Unable to make the stage window 
0x420002d the current GLX drawable
  (quadrapassel:2024): ClutterGLX-CRITICAL **: Unable to make the stage window 
0x420004a the current GLX drawable

  Quadrapassel opens as expected. Terminal error not expected. I can
  then start a new game via Game-New.

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

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


[Desktop-packages] [Bug 692668] Re: nonsense behaviour when dragging the "+" sign next to a folder

2014-09-17 Thread Hans Joachim Desserud
Ok, marking this as Fix released then. :)

"It wouldn't have occurred to me to look for a setting" It didn't occur
to me either, I only randomly stumbled across it when looking for
something else in the settings.

** Changed in: nautilus (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  nonsense behaviour when dragging the "+" sign next to a folder

Status in “nautilus” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: nautilus

  Steps to reproduce:

  1 Open Nautilus and put it in list view.

  2 Suppose you have 3 folders: A, B and C

  3 Click once on folder A to _select_ it

  4 Click on the [+] sign on the left of folder B (as if you wanted to
  expand it) and don't release the mouse button

  5 Drag it somewhere, for example into folder C, and drop it.

  Expected result: NOTHING should happen. Dragging the [+] sign makes no
  sense. It shouldn't even give you any visual feedback that you are
  doing something, like when you try to drag a button. An other, less
  correct but acceptable behaviour, would be that you would be dragging
  folder B, the one whose [+] sign you have clicked and dragged.

  Observed result: folder A, not B (not the one whose [+] sign you have
  dragged, but the one that was previously selected when you clicked on
  the completely unrelated [+] sign) is moved into where you drop, in
  this case into C.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nautilus 1:2.30.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
  Uname: Linux 2.6.32-26-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Mon Dec 20 18:47:05 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: nautilus

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

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


[Desktop-packages] [Bug 1272716] Re: Undo doesn't work: gnome-sudoku crashed with TypeError in set_value(): unorderable types: int() < NoneType()

2014-09-17 Thread Alberto Salvia Novella
** Changed in: gnome-sudoku (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  Undo doesn't work: gnome-sudoku crashed with TypeError in set_value():
  unorderable types: int() < NoneType()

Status in “gnome-sudoku” package in Ubuntu:
  Fix Released
Status in “gnome-sudoku” source package in Trusty:
  Fix Released

Bug description:
  Impact:
  using "undo" sometime hits an error

  Test Case:
  - run gnome-sudoku
  - start an easy game
  - enter a number somewhere
  - click on undo

  -> it should undo and not trigger an error dialog

  Regression potential:
  check that undo keeps working correctly

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

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


[Desktop-packages] [Bug 1370668] [NEW] Lightning 3.3.1.1 for Thunderbird 31.1.1 does not connect to exchange server (NS_ERROR_XPC_CI_RETURNED_FAILURE )

2014-09-17 Thread Stefan Hoeche
Public bug reported:

Lightning 3.3.1.1 from xul-ext-lightning for Thunderbird 31.1.1 does not
connect to MS Exchange servers. Error message is

An error was encountered preparing the calendar located at [calendar
address] for use. It will not be available.

[Exception... "Component returned failure code: 0x80570015
(NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]"  nsresult:
"0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)"  location: "JS frame ::
resource://calendar/modules/calUtils.jsm ->
file:///usr/lib/thunderbird/extensions/[snip]/calendar-
js/calCalendarManager.js :: cmgr_createCalendar :: line 441"  data: no]

Tried installing previous 3.3 and 3.2 Lightning versions manually, all
leading to the same error message.

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

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

Title:
  Lightning 3.3.1.1 for Thunderbird 31.1.1 does not connect to exchange
  server (NS_ERROR_XPC_CI_RETURNED_FAILURE )

Status in “thunderbird” package in Ubuntu:
  New

Bug description:
  Lightning 3.3.1.1 from xul-ext-lightning for Thunderbird 31.1.1 does
  not connect to MS Exchange servers. Error message is

  An error was encountered preparing the calendar located at [calendar
  address] for use. It will not be available.

  [Exception... "Component returned failure code: 0x80570015
  (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]"
  nsresult: "0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)"  location:
  "JS frame :: resource://calendar/modules/calUtils.jsm ->
  file:///usr/lib/thunderbird/extensions/[snip]/calendar-
  js/calCalendarManager.js :: cmgr_createCalendar :: line 441"  data:
  no]

  Tried installing previous 3.3 and 3.2 Lightning versions manually, all
  leading to the same error message.

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

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


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

2014-09-17 Thread Mathew Hodson
Those packages are dependencies, but it does not depend on them being
the exact same version as evolution-data-server, which seems to be
intentional.

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

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

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

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released
Status in “account-plugins” source package in Trusty:
  Fix Released
Status in “evolution-data-server” source package in Trusty:
  Fix Committed
Status in “signon-plugin-oauth2” source package in Trusty:
  Fix Released

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

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

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


  Old description
  ===

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

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

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

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

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


[Desktop-packages] [Bug 1370648] Re: update-software-center crashed with AttributeError in __getattr__(): When using gi.repository you must not import static modules like "gobject". Please change all

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1367017 ***
https://bugs.launchpad.net/bugs/1367017

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

** Tags removed: need-duplicate-check

** Changed in: software-center (Ubuntu)
   Importance: Undecided => Medium

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

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

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

** Information type changed from Private to Public

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

Title:
  update-software-center crashed with AttributeError in __getattr__():
  When using gi.repository you must not import static modules like
  "gobject". Please change all occurrences of "import gobject" to "from
  gi.repository import GObject". See:
  https://bugzilla.gnome.org/show_bug.cgi?id=709183

Status in “software-center” package in Ubuntu:
  New

Bug description:
  After upgrade to 14.10

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Wed Sep 17 19:09:13 2014
  ExecutablePath: /usr/share/software-center/update-software-center
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/sbin/update-software-center --triggered 
/usr/share/locale-langpack
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/sbin/update-software-center', '--triggered', 
'/usr/share/locale-langpack']
  SourcePackage: software-center
  Title: update-software-center crashed with AttributeError in __getattr__(): 
When using gi.repository you must not import static modules like "gobject". 
Please change all occurrences of "import gobject" to "from gi.repository import 
GObject". See: https://bugzilla.gnome.org/show_bug.cgi?id=709183
  UpgradeStatus: Upgraded to utopic on 2014-09-17 (0 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1301776] Re: Update manager is really small and not resizeable

2014-09-17 Thread Arnaud Thevenet
Another workaround that may help find the reason of the bug : 
in the non-resizable window, click on Settings, that will open "Software and 
Updates" window.
After closing this window, the software updater window will be resizable.

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

Title:
  Update manager is really small and not resizeable

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  In Progress
Status in “compiz” source package in Trusty:
  Triaged
Status in “unity” source package in Trusty:
  Triaged

Bug description:
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  : "The Updates
  Available window should be manually resizable only when it is in this
  expanded state."

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

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


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

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 1338492 ***
https://bugs.launchpad.net/bugs/1338492

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

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

Bug description:
  When switching from Intel to Nvidia on my Optimus laptop (Asus Zenbook
  UX32VD) on logout Xorg crashed.

  
  Also, I am experiencing spontaneous freezes when using Nvidia GPU - display 
rendering can be resumed when switching from X11 to virtual terminal and back. 
Apparently I can still perform all actions but my screen keeps displaying the 
same from the point it freezes.
  The second bug appears to be this: 
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1220426 but it 
probably does not affect this crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] je adresářem: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.9.1 (Ubuntu 4.9.1-14ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Wed Sep 17 18:59:53 2014
  DistUpgraded: 2014-09-01 07:53:46,252 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1507]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 620M [1043:1507]
  InstallationDate: Installed on 2014-08-04 (44 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=22fda0b5-d94f-4ee6-97a8-40ee537b5002 ro quiet splash
  Signal: 6
  SourcePackage: nvidia-graphics-drivers
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   ?? ()
   __libc_start_main (main=0x7fafa2577680, argc=11, argv=0x7fff01b407f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff01b407e8) at libc-start.c:287
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to utopic on 2014-09-01 (16 days ago)
  UserGroups:
   
  dmi.bios.date: 01/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX32VD.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX32VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
 

[Desktop-packages] [Bug 1370627] Re: pptp crashed with SIGSEGV

2014-09-17 Thread Apport retracing service
*** This bug is a duplicate of bug 205684 ***
https://bugs.launchpad.net/bugs/205684

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  pptp crashed with SIGSEGV

Status in “pptp-linux” package in Ubuntu:
  New

Bug description:
  ,

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: pptp-linux 1.7.2-7
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Tue Sep 16 21:15:28 2014
  ExecutablePath: /usr/sbin/pptp
  ProcCmdline: /usr/sbin/pptp 140.177.205.151 --nolaunchpppd --loglevel 0 
--logstring nm-pptp-service-8271
  ProcEnviron:
   LANGUAGE=es_AR
   TERM=linux
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x405a32:  mov(%rdx,%rcx,8),%rsi
   PC (0x00405a32) ok
   source "(%rdx,%rcx,8)" (0x7fff387d7400) not located in a known VMA region 
(needed readable region)!
   destination "%rsi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: pptp-linux
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: pptp crashed with SIGSEGV
  UpgradeStatus: Upgraded to utopic on 2013-02-05 (588 days ago)
  UserGroups:

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

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


[Desktop-packages] [Bug 1369843] Re: First Time Launch/Setup: Clicking "Online Accts" Does Nothing

2014-09-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-contacts (Ubuntu)
   Status: New => Confirmed

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

Title:
  First Time Launch/Setup: Clicking "Online Accts" Does Nothing

Status in “gnome-contacts” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I am a novice Linux user playing around with Ubuntu.  I first
  installed 14.04 and then upgraded to 14.10 but have observed the same
  problem with gnome-contacts on both.  I added Google to my online
  accounts list and it seemed to work.  I launched gnome-contacts
  ("Contacts" on Ubuntu) and it opened a window with two buttons:
  "Online Accounts" or "Use Local Address Book".  Of course I want to
  use my online accounts.  But no matter how much I click this button
  nothing happens.  The button is responsive--it depresses/shades when I
  click it.  But then nothing happens.

  Clicking "Use Local Address Book" does work.  But of course that
  doesn't get me to my Google contact list.  What tests can I perform to
  further diagnose this problem?

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

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


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

2014-09-17 Thread Franko Burolo
Thank you, Alberto!
Interestingly, the packages Mathew listed were NOT upgraded along with 
evolution-data-server. I upgraded them just now, and it seems to work fine now.
Would it be a good idea to specify those dependencies in the 
evolution-data-server package? Should I change the tag to "verification-done" 
now? :-)

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

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

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released
Status in “account-plugins” source package in Trusty:
  Fix Released
Status in “evolution-data-server” source package in Trusty:
  Fix Committed
Status in “signon-plugin-oauth2” source package in Trusty:
  Fix Released

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

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

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


  Old description
  ===

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

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

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

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

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


[Desktop-packages] [Bug 1090288] Re: The locale file for en_ZA appears to have an error

2014-09-17 Thread Gunnar Hjalmarsson
** Tags added: patch

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

Title:
  The locale file for en_ZA appears to have an error

Status in “langpack-locales” package in Ubuntu:
  In Progress

Bug description:
  I suspect there is a problem with the locale for South Africa. The
  locale file for en_ZA located in /usr/share/i18n/locales has the
  following settings:

  LC_Monetary
  .

  % "."
  mon_decimal_point   ""

  % ","
  mon_thousands_sep   ""
  mon_grouping3;3
  positive_sign   ""
  

  
  LC_NUMERIC
  % "."
  decimal_point   ""

  % ","
  thousands_sep   ""
  grouping3;3
  END LC_NUMERIC

  
  - Unicode character  is for a comma "," and not a full stop "." It 
should be 
  - Unicode character  is for a non-breaking space " " and not a comma 
"," . If it's meant to be a comma it should be 

  South Africa is on the metric system and uses a "." for decimal
  places. The above issue results in the regional settings having a
  comma in the decimal place and causes a number of errors when trying
  to use other software packages.

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

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


[Desktop-packages] [Bug 1090288] Re: The locale file for en_ZA appears to have an error

2014-09-17 Thread Gunnar Hjalmarsson
** Patch added: "drop-en_ZA-patch.patch"
   
https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1090288/+attachment/4206477/+files/drop-en_ZA-patch.patch

** Changed in: langpack-locales (Ubuntu)
   Importance: Undecided => Medium

** Changed in: langpack-locales (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: langpack-locales (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  The locale file for en_ZA appears to have an error

Status in “langpack-locales” package in Ubuntu:
  In Progress

Bug description:
  I suspect there is a problem with the locale for South Africa. The
  locale file for en_ZA located in /usr/share/i18n/locales has the
  following settings:

  LC_Monetary
  .

  % "."
  mon_decimal_point   ""

  % ","
  mon_thousands_sep   ""
  mon_grouping3;3
  positive_sign   ""
  

  
  LC_NUMERIC
  % "."
  decimal_point   ""

  % ","
  thousands_sep   ""
  grouping3;3
  END LC_NUMERIC

  
  - Unicode character  is for a comma "," and not a full stop "." It 
should be 
  - Unicode character  is for a non-breaking space " " and not a comma 
"," . If it's meant to be a comma it should be 

  South Africa is on the metric system and uses a "." for decimal
  places. The above issue results in the regional settings having a
  comma in the decimal place and causes a number of errors when trying
  to use other software packages.

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

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


[Desktop-packages] [Bug 1311881] Re: dual screen ubuntu 14.04, second screen only partially displaying desktop

2014-09-17 Thread Grzegorz Cieslewski
I had simmilar issue.  I deisabled the gpu-manager.conf, deleted old
xorg.conf, used aticonfig --initial to create a new config file, logged
in and used amdcccle to make final adjustments.

I dont really understand this but it seems that there is some problem
with randr.

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

Title:
  dual screen ubuntu 14.04, second screen only partially displaying
  desktop

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  The second screen on my 2 monitor Ubuntu 14.04 setup is only partially 
showing any of the desktop.
  The primary screen is a 22" 1680*1050 and the secondary screen is 1920*1200.
  The primary screen has a complete and true 1680*1050 desktop, but the 
secondary screen only shows 1" of the 1920*1200 screen down the left vertical.
  The rest of the desktop is obscured under some "black window", with only the 
mouse being displayed as it travels through that screen.

  Any windows or items below that black area, can be interacted with,
  and the mouse indicates their presence with resize/minimise and other
  hints, but they do not display over the black area.

  The system was working perfectly fine in 13.10 and this issue only
  occurred after I upgraded to 14.04 and, faced with a "failed to start
  session" bug on the login screen, resorted to an "apt-get install
  ubuntu-desktop" to get my desktop up and running.

  My graphics card is an ATI Radeon HD 6670 and my monitors are Samsung
  Syncmaster 2232bw (22") and Dell UM2412M.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 23 21:51:03 2014
  DistUpgraded: 2014-04-23 18:43:48,762 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:0443]
  InstallationDate: Installed on 2012-09-24 (576 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1aff935b-13e8-475e-a845-3d816a582db2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (0 days ago)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1103
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1103:bd03/23/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 23 22:38:29 2014
  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/fg

[Desktop-packages] [Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04

2014-09-17 Thread Daniel Bünzli
Same problem with certified DELL PowerEdge T320
(http://www.ubuntu.com/certification/hardware/201210-12063/)

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

Title:
  matrox g200eR2 is unclaimed in 14.04

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  On a certified Dell PowerEdge T620 server
  (http://www.ubuntu.com/certification/hardware/201207-11426/)

  The matrox video card is not recognised:
  lspci | grep VGA
  0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2

  lshw -C display
*-display UNCLAIMED 
 description: VGA compatible controller
 product: G200eR2
 vendor: Matrox Electronics Systems Ltd.
 physical id: 0
 bus info: pci@:0a:00.0
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: pm vga_controller bus_master cap_list
 configuration: latency=64 maxlatency=32 mingnt=16
 resources: memory:d800-d8ff memory:deffc000-deff 
memory:de00-de7f

  Thus xserver is not hardver accelerated.

  Also /dev/dri and /dev/dri/card0 is missing.

  kernel module mga is not loaded, although if i manually load by modprobe it 
works fine
  modprobe mga
  lsmod | grep mga
  mga40811  0 
  drm   302817  1 mga

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

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


[Desktop-packages] [Bug 1158432] Re: On graphical login, Network Manager window gets in the way

2014-09-17 Thread Phil Hord
I think it's important for the developer to consider some aspects of
this bug separately.

1. Wifi auth window pops up and steals focus before user is logged in. 
It is frustrating to begin typing my password and to have my keyboard focus 
swiped away so my hidden password is now hopelessly split across two 
different
windows.

2. Wifi auth window _keeps_ focus from the Ubuntu login window until it
is dismissed.

I think the first one is an annoying bug, but it might be easy to
dismiss as "medium".  But the second one is sometimes serious or
critical.

Consider that the login prompt appears on the display where the mouse
appears.  On a multi-monitor setup, this is critical because some
monitors may not be usable yet.  If I can't see my login screen, I have
learned that I can just move my mouse so it is on the primary display
and the login prompt will appear.  But the WiFi password window does not
have this logic.  When it steals focus from the login prompt, I can move
the mouse all I want, and the login prompt will appear or disappear from
my primary display.  But until I cancel the wifi popup window, I cannot
type my password to login.  If the wifi popup appeared on some unusable
monitor, I cannot see the window to dismiss it.

In my case my 2nd monitor is in portrait orientation so my display
properties have it rotated.  But this rotation does not take effect
until after I log in.  So when I get the popup window, my mouse on the
2nd display is rotated 90 degrees and the popup is quite difficult to
dismiss.

I can imagine this is a serious accessibility issue for users who have
other challenges seeing their display or using a mouse or keyboard as
efficiently as you do.

Please fix this.  It has been with us for so long.

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

Title:
  On graphical login, Network Manager window gets in the way

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  New in 13.04, on a laptop with wifi (in addition to being wired), when
  the login gui comes up on boot-up, I can no longer simply type in my
  password to log in.

  This is because a wifi authentication window pops up, asking for a
  password for my wifi connection.  Worse, it does not let me get the
  focus back to the log in screen or anywhere else: I have to explicitly
  click "cancel ".

  After I log in, the wifi password is not needed, since the Manager has
  stored it and connects automatically, using its stored password.

  It may be nice to be able to access the network before logging in, but
  that option should not interrupt my log-in process, and certainly not
  block it!

  Moreover, given that my machine is also connected to wired ethernet
  (by DHCP, no password), it is hardly a high priority to get wifi
  going.

  This problem exists on both of my laptops (very different hardware).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: network-manager 0.9.8.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3
  Uname: Linux 3.8.0-13-generic x86_64
  ApportVersion: 2.9.2-0ubuntu1
  Architecture: amd64
  Date: Thu Mar 21 13:47:50 2013
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-18 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
  IpRoute:
   default via 132.206.112.1 dev eth0  proto static 
   132.206.112.0/26 dev eth0  proto kernel  scope link  src 132.206.112.10  
metric 1 
   142.157.168.0/23 dev wlan0  proto kernel  scope link  src 142.157.168.8  
metric 9 
   169.254.0.0/16 dev eth0  scope link  metric 1000
  MarkForUpload: True
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-03-19T18:52:07.457464
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   IHSP  3985ff88-5770-4938-8133-23b8ded92641   
802-3-ethernet1363888105   Thu 21 Mar 2013 01:48:25 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/2
   DHCP  aec2f3e7-cdaa-46ff-b51d-401084613817   
802-3-ethernet0never  no
no /org/freedesktop/NetworkManager/Settings/1
   wpa.mcgill.ca 4ce783b2-6946-417e-ac7c-eb6984d01f15   
802-11-wireless   1363888105   Thu 21 Mar 2013 01:48:25 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE 

[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Alberto Milone
@Fabio: there's no trace of my change in either log. You don't seem to
have passed  the "gpumanager_modesetting" boot parameter (I can't see it
in either Xorg log). Maybe you forgot to update grub?

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1359304] Re: draw can't start if impress is removed

2014-09-17 Thread Bryan Quigley
Since it's been fixed in Utopic I'm marking it as such.   This doesn't
look like it would qualify for an SRU to 14.04.

It may still be fixed in 14.04 if a major release exception is granted
for LibreOffice (and then we'll backport a major version back).

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

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

Title:
  draw can't start if impress is removed

Status in “libreoffice” package in Ubuntu:
  Fix Released

Bug description:
  LibreOffice Draw doesn't work if LibreOffice Impress is removed.
  Somewhat related to
  https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/313173
  which was marked as a wontfix but this is more severe as Impress isn't
  currently marked as a dependency of Draw.

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

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


[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Fabio
This was probably created when I tried to launch startx from console

** Attachment added: "Xorg.1.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+attachment/4206459/+files/Xorg.1.log

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval

2014-09-17 Thread Ricardo Salveti
The question here is more to what is the desired behaviour when playing
DTMF tones.

It needs to be an alert, as on silent mode you don't want it to play,
but any alert at this moment will trigger the ducking effect described
by the bug.

Do we want it to duck or to cork? Cork would be even more confusing
imho.

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

Title:
  With music playing, pressing the dialpad keys reduces the volume for
  an odd interval

Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “tone-generator” package in Ubuntu:
  Confirmed

Bug description:
  1. play a track
  2. open dialer-app and press the keypad

  What happens:
  The sound music turns down for a few seconds and then gets back to normal 
automatically.

  While the above feels like a good idea, it need refinement. In its
  current condition it rather feels broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:45:21 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Fabio
@Alberto:
it has still the same problem


** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+attachment/4206458/+files/Xorg.0.log

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Fabio
** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+attachment/4206460/+files/gpu-manager.log

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval

2014-09-17 Thread Ricardo Salveti
So from IRC it's more about the lack of a fading effect when ducking the
sound. There's also an issue that the dtmf tone takes a while to
disappear after playing the sound, and for that I added a bugtask for
tone generator.

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

** Changed in: tone-generator (Ubuntu)
   Status: New => Confirmed

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

** Changed in: tone-generator (Ubuntu)
   Importance: Undecided => Medium

** Changed in: tone-generator (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

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

Title:
  With music playing, pressing the dialpad keys reduces the volume for
  an odd interval

Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “tone-generator” package in Ubuntu:
  Confirmed

Bug description:
  1. play a track
  2. open dialer-app and press the keypad

  What happens:
  The sound music turns down for a few seconds and then gets back to normal 
automatically.

  While the above feels like a good idea, it need refinement. In its
  current condition it rather feels broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:45:21 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval

2014-09-17 Thread Omer Akram
As talked on IRC, I was expecting it to fade-out and fade-in instead of
doing that instantly. And also it would have been good if the interval
in which the sound comes back to its normal value was reduced as in
android devices.

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

Title:
  With music playing, pressing the dialpad keys reduces the volume for
  an odd interval

Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “tone-generator” package in Ubuntu:
  Confirmed

Bug description:
  1. play a track
  2. open dialer-app and press the keypad

  What happens:
  The sound music turns down for a few seconds and then gets back to normal 
automatically.

  While the above feels like a good idea, it need refinement. In its
  current condition it rather feels broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:45:21 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval

2014-09-17 Thread Ricardo Salveti
We could later on have a separated role for dtmf, that would not be
affected by corking and not by ducking, but that is currently not
possible as it'd break the silent mode use case.

Once we're able to group roles, and separate behaviour with volume, we
can get this fixed, but post RTM.

** Also affects: tone-generator (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  With music playing, pressing the dialpad keys reduces the volume for
  an odd interval

Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “tone-generator” package in Ubuntu:
  Confirmed

Bug description:
  1. play a track
  2. open dialer-app and press the keypad

  What happens:
  The sound music turns down for a few seconds and then gets back to normal 
automatically.

  While the above feels like a good idea, it need refinement. In its
  current condition it rather feels broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:45:21 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1334053] Re: Cannot copy/paste files/directories anymore

2014-09-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Cannot copy/paste files/directories anymore

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  I'm allowed to copy, and the paste action appears in the right-click
  menu, but pressing it does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 25 09:06:44 2014
  GsettingsChanges:
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'date_modified', 'RabbitVCS::age_column', 
'RabbitVCS::author_column']"
   b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 
'RabbitVCS::age_column', 'RabbitVCS::author_column', 
'RabbitVCS::revision_column', 'RabbitVCS::status_column', 'date_accessed']"
  InstallationDate: Installed on 2013-08-15 (312 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (64 days ago)

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

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


[Desktop-packages] [Bug 1310489] Update Released

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

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  Fix Released

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  

  == SRU Request ==

  There is a regression in the gpu-manager that causes it to revert user
  changes right before the first reboot after enabling the fglrx driver
  or the nvidia driver on a system with hybrid graphics (Intel+AMD or
  Intel+NVIDIA). This causes the gpu-manager to remove the current
  xorg.conf and to switch to Mesa.

  [Impact]
   * This regression makes it almost impossible to use binary drivers on 
systems with hybrid graphics.

  [Test Case]
   * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs.

   * Make sure that the gpu-manager is not disabled (only necessary if
  you disabled it manually).

   * Remove all fglrx and nvidia drivers (keep the nvidia-common and the 
nvidia-prime packages):
     sudo apt-get --purge remove nvidia-331
     sudo apt-get --purge remove nvidia-331
     sudo apt-get --purge remove fglrx
     sudo apt-get --purge remove fglrx-updates

   * Install ubuntu-drivers-common from trusty-proposed.

   * Restart the system.

   * Install the binary driver (either fglrx or nvidia, according to the 
available discrete GPU), reboot, and check that the binary driver is enabled 
(attach your /var/log/gpu-manager.log)
  - Expected: the (AMD or NVIDIA) discrete GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
discrete GPU is not used, despite the fact that the system was configured 
properly.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  -

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error --> "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]" but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Apr 21 08:43:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1985]
     Subsystem: Hewlett-Packard Company Device [103c:1985]
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.hand

[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system

2014-09-17 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.2.91.7

---
ubuntu-drivers-common (1:0.2.91.7) trusty-proposed; urgency=medium

  * gpu-manager.c, gpu-manager.py:
- Add support for testing core alternatives. This will be needed
  by fglrx.
- Fix a regression that caused the gpu-manager to switch to mesa
  after enabling fglrx on hybrid systems (LP: #1310489). Also
  add a test case so that we don't regress in the future.
- Check that either fglrx or nvidia is set in xorg.conf when
  xorg.conf is needed.
- Check if kernel modules are blacklisted before choosing the
  driver (LP: #1310489).
- Enable only GPUs with open drivers that have connected outputs.
  Attaching to GPUs that have no connected outputs would result
  in a black screen.
- Allow RandR offloading even without bbswitch (LP: #1349282).
- Fall back to mesa when failing to enable prime.
- Do not try to enable prime if the nvidia driver is older than
  331.
- Do not abort if the settings for prime cannot be found.
  Try to create the file before failing.
 -- Alberto MiloneFri, 29 Aug 2014 11:29:55 
+0200

** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  Fix Released

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  

  == SRU Request ==

  There is a regression in the gpu-manager that causes it to revert user
  changes right before the first reboot after enabling the fglrx driver
  or the nvidia driver on a system with hybrid graphics (Intel+AMD or
  Intel+NVIDIA). This causes the gpu-manager to remove the current
  xorg.conf and to switch to Mesa.

  [Impact]
   * This regression makes it almost impossible to use binary drivers on 
systems with hybrid graphics.

  [Test Case]
   * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs.

   * Make sure that the gpu-manager is not disabled (only necessary if
  you disabled it manually).

   * Remove all fglrx and nvidia drivers (keep the nvidia-common and the 
nvidia-prime packages):
     sudo apt-get --purge remove nvidia-331
     sudo apt-get --purge remove nvidia-331
     sudo apt-get --purge remove fglrx
     sudo apt-get --purge remove fglrx-updates

   * Install ubuntu-drivers-common from trusty-proposed.

   * Restart the system.

   * Install the binary driver (either fglrx or nvidia, according to the 
available discrete GPU), reboot, and check that the binary driver is enabled 
(attach your /var/log/gpu-manager.log)
  - Expected: the (AMD or NVIDIA) discrete GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
discrete GPU is not used, despite the fact that the system was configured 
properly.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  -

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error --> "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]" but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop

[Desktop-packages] [Bug 1349282] Re: The gpu-manager should allow RandR offloading without bbswitch

2014-09-17 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-drivers-common - 1:0.2.91.7

---
ubuntu-drivers-common (1:0.2.91.7) trusty-proposed; urgency=medium

  * gpu-manager.c, gpu-manager.py:
- Add support for testing core alternatives. This will be needed
  by fglrx.
- Fix a regression that caused the gpu-manager to switch to mesa
  after enabling fglrx on hybrid systems (LP: #1310489). Also
  add a test case so that we don't regress in the future.
- Check that either fglrx or nvidia is set in xorg.conf when
  xorg.conf is needed.
- Check if kernel modules are blacklisted before choosing the
  driver (LP: #1310489).
- Enable only GPUs with open drivers that have connected outputs.
  Attaching to GPUs that have no connected outputs would result
  in a black screen.
- Allow RandR offloading even without bbswitch (LP: #1349282).
- Fall back to mesa when failing to enable prime.
- Do not try to enable prime if the nvidia driver is older than
  331.
- Do not abort if the settings for prime cannot be found.
  Try to create the file before failing.
 -- Alberto MiloneFri, 29 Aug 2014 11:29:55 
+0200

** Changed in: ubuntu-drivers-common (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  The gpu-manager should allow RandR offloading without bbswitch

Status in “nvidia-settings” package in Ubuntu:
  Triaged
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “nvidia-settings” source package in Trusty:
  Triaged
Status in “ubuntu-drivers-common” source package in Trusty:
  Fix Released

Bug description:
  SRU Request

  While bbswitch may fail on some hybrid systems (e.g. on the desktop or
  when the bbswitch module fails to build), this is not a good reason to
  prevent the system from offloading rendering to the NVIDIA GPU.

  [Impact]
   * This problem makes it impossible to use the NVIDIA GPU on hybrid systems 
with Intel+NVIDIA GPUs when bbswitch is not available (i.e. when it fails to 
load).

  [Test Case]
   * Make sure to be using a hybrid system with Intel+NVIDIA GPUs.
   
   * Check that bbswitch is not available. You can do so by posting output of 
the following command:
 test -e /proc/acpi/bbswitch && echo true || echo false
 
   * Make sure that the gpu-manager is not disabled (only necessary if you 
disabled it manually).

   * Install ubuntu-drivers-common from trusty-proposed.

   * Remove all fglrx and nvidia drivers (keep the nvidia-common and the 
nvidia-prime packages):
 sudo apt-get --purge remove nvidia-331
 sudo apt-get --purge remove nvidia-331
 sudo apt-get --purge remove fglrx
 sudo apt-get --purge remove fglrx-updates

   * Restart the system.

   * Install the nvidia binary driver, reboot, and check that the binary driver 
is enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA discrete GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
discrete GPU is not used, despite the fact that the system was configured 
properly.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  ---

  The gpu-manager should allow RandR offloading without bbswitch. This
  would allow desktop systems to make use of offloading even when
  bbswitch is not supported.

  Also, nvidia-settings should not complain in such scenarios. See
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1310023/comments/70

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

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


[Desktop-packages] [Bug 1349282] Update Released

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

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

Title:
  The gpu-manager should allow RandR offloading without bbswitch

Status in “nvidia-settings” package in Ubuntu:
  Triaged
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “nvidia-settings” source package in Trusty:
  Triaged
Status in “ubuntu-drivers-common” source package in Trusty:
  Fix Released

Bug description:
  SRU Request

  While bbswitch may fail on some hybrid systems (e.g. on the desktop or
  when the bbswitch module fails to build), this is not a good reason to
  prevent the system from offloading rendering to the NVIDIA GPU.

  [Impact]
   * This problem makes it impossible to use the NVIDIA GPU on hybrid systems 
with Intel+NVIDIA GPUs when bbswitch is not available (i.e. when it fails to 
load).

  [Test Case]
   * Make sure to be using a hybrid system with Intel+NVIDIA GPUs.
   
   * Check that bbswitch is not available. You can do so by posting output of 
the following command:
 test -e /proc/acpi/bbswitch && echo true || echo false
 
   * Make sure that the gpu-manager is not disabled (only necessary if you 
disabled it manually).

   * Install ubuntu-drivers-common from trusty-proposed.

   * Remove all fglrx and nvidia drivers (keep the nvidia-common and the 
nvidia-prime packages):
 sudo apt-get --purge remove nvidia-331
 sudo apt-get --purge remove nvidia-331
 sudo apt-get --purge remove fglrx
 sudo apt-get --purge remove fglrx-updates

   * Restart the system.

   * Install the nvidia binary driver, reboot, and check that the binary driver 
is enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA discrete GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
discrete GPU is not used, despite the fact that the system was configured 
properly.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  ---

  The gpu-manager should allow RandR offloading without bbswitch. This
  would allow desktop systems to make use of offloading even when
  bbswitch is not supported.

  Also, nvidia-settings should not complain in such scenarios. See
  https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
  common/+bug/1310023/comments/70

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

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


[Desktop-packages] [Bug 1369708] Re: nvidiia drivers

2014-09-17 Thread Filip Sohajek
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the 
problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks! 

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

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

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

Title:
  nvidiia drivers

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Rather large problem with trying to use my NVIDIA GEFORCE 310 WITH
  CUDA, FORCED A COMPLETE REINSTALL OF 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep 15 15:46:03 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation Device [104d:907a]
  InstallationDate: Installed on 2014-09-15 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Sony Corporation VPCF132FX
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=be267841-0829-4d21-9fff-3fb2c660ae78 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0180Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0180Y9:bd09/03/2010:svnSonyCorporation:pnVPCF132FX:pvrC607BXFG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCF132FX
  dmi.product.version: C607BXFG
  dmi.sys.vendor: Sony Corporation
  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.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Sep 15 13:40:05 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: nouveau

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

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


[Desktop-packages] [Bug 1370234] Re: freshly installed and full of error's log

2014-09-17 Thread Filip Sohajek
*** This bug is a duplicate of bug 1370236 ***
https://bugs.launchpad.net/bugs/1370236

** This bug has been marked a duplicate of bug 1370236
   freshly installed and full of error's log

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

Title:
  freshly installed and full of error's log

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Well, I wish you all the best with this diagnostic, not my cup of tea.
  I'm just a chemist.

  
  franzz@franzzmachine:~$ sudo xdiagnose
  Création du fichier de configuration GRUB…
  Attention : Définir GRUB_TIMEOUT à une valeur non nulle si 
GRUB_HIDDEN_TIMEOUT est définie n’est plus possible.
  Image Linux trouvée : /boot/vmlinuz-3.13.0-35-generic
  Image mémoire initiale trouvée : /boot/initrd.img-3.13.0-35-generic
  Image Linux trouvée : /boot/vmlinuz-3.13.0-24-generic
  Image mémoire initiale trouvée : /boot/initrd.img-3.13.0-24-generic
  Adding boot menu entry for EFI firmware configuration
  fait
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.13.0-35-generic (buildd@panlong) (gcc version 
4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 
(Ubuntu 3.13.0-35.62-generic 3.13.11.6)
  [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=3651cf0f-bddd-4783-ae51-2b4aa3d712f7 ro quiet splash vt.handoff=7
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x00087fff] usable
  [0.00] BIOS-e820: [mem 0x00088000-0x000b] reserved
  [0.00] BIOS-e820: [mem 0x0010-0x1fff] usable
  [0.00] BIOS-e820: [mem 0x2000-0x201f] reserved
  [0.00] BIOS-e820: [mem 0x2020-0x3a0befff] usable
  [0.00] BIOS-e820: [mem 0x3a0bf000-0x3aebefff] reserved
  [0.00] BIOS-e820: [mem 0x3aebf000-0x3afbefff] ACPI NVS
  [0.00] BIOS-e820: [mem 0x3afbf000-0x3affefff] ACPI 
data
  [0.00] BIOS-e820: [mem 0x3afff000-0x3aff] usable
  [0.00] BIOS-e820: [mem 0x3b00-0x3f9f] reserved
  [0.00] BIOS-e820: [mem 0xf000-0xf3ff] reserved
  [0.00] BIOS-e820: [mem 0xfeb0-0xfeb03fff] reserved
  [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
  [0.00] BIOS-e820: [mem 0xfed1-0xfed19fff] reserved
  [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
  [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
  [0.00] BIOS-e820: [mem 0xffd8-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001bf5f] usable
  [0.00] e820: update [mem 0x2f9ef018-0x2f9ff057] usable ==> usable
  [0.00] e820: update [mem 0x2f9d1018-0x2f9ee457] usable ==> usable
  [0.00] extended physical RAM map:
  [0.00] reserve setup_data: [mem 
0x-0x00087fff] usable
  [0.00] reserve setup_data: [mem 
0x00088000-0x000b] reserved
  [0.00] reserve setup_data: [mem 
0x0010-0x1fff] usable
  [0.00] reserve setup_data: [mem 
0x2000-0x201f] reserved
  [0.00] reserve setup_data: [mem 
0x2020-0x2f9d1017] usable
  [0.00] reserve setup_data: [mem 
0x2f9d1018-0x2f9ee457] usable
  [0.00] reserve setup_data: [mem 
0x2f9ee458-0x2f9ef017] usable
  [0.00] reserve setup_data: [mem 
0x2f9ef018-0x2f9ff057] usable
  [0.00] reserve setup_data: [mem 
0x2f9ff058-0x3a0befff] usable
  [0.00] reserve setup_data: [mem 
0x3a0bf000-0x3aebefff] reserved
  [0.00] reserve setup_data: [mem 
0x3aebf000-0x3afbefff] ACPI NVS
  [0.00] reserve setup_data: [mem 
0x3afbf000-0x3affefff] ACPI data
  [0.00] reserve setup_data: [mem 
0x3afff000-0x3aff] usable
  [0.00] reserve setup_data: [mem 
0x3b00-0x3f9f] reserved
  [0.00] reserve setup_data: [mem 
0xf000-0xf3ff] reserved
  [0.00] reserve setup_data: [mem 
0xfeb0-0xfeb03fff] reserved
  [0.00] reserve setup_data:

[Desktop-packages] [Bug 1370236] Re: freshly installed and full of error's log

2014-09-17 Thread Filip Sohajek
** Changed in: xorg (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/254635

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

Title:
  freshly installed and full of error's log

Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  Well, I wish you all the best with this diagnostic, not my cup of tea.
  I'm just a chemist.

  
  franzz@franzzmachine:~$ sudo xdiagnose
  Création du fichier de configuration GRUB…
  Attention : Définir GRUB_TIMEOUT à une valeur non nulle si 
GRUB_HIDDEN_TIMEOUT est définie n’est plus possible.
  Image Linux trouvée : /boot/vmlinuz-3.13.0-35-generic
  Image mémoire initiale trouvée : /boot/initrd.img-3.13.0-35-generic
  Image Linux trouvée : /boot/vmlinuz-3.13.0-24-generic
  Image mémoire initiale trouvée : /boot/initrd.img-3.13.0-24-generic
  Adding boot menu entry for EFI firmware configuration
  fait

  (firefox:12411): dconf-CRITICAL **: unable to create file 
'/home/franzz/.cache/dconf/user': Permission non accordée.  dconf will not work 
properly.

  I just re-install the all systeme (not the first time and not the last
  , I guess) the only configuration I recuped is linked to mozilla
  (bookmarks only if not wrong). And exept files( documents,music,movies
  no .config), I didn't restaure from a back-up to avoid miss-
  configurations done previously. I won't re-explain about crazy rookie
  like me. Probably a bad use or config. or blended DB... done by me,
  not Ubuntu faulty. But in case off..

  I thanks you for your help and  i really appreciate the quality of
  your participation to keep me faithfull into Linux and Ubuntu.

  My Best Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Sep 16 21:58:59 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:18fe]
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion Sleekbook 15
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed 
root=UUID=3651cf0f-bddd-4783-ae51-2b4aa3d712f7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18FE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 82.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd02/08/2013:svnHewlett-Packard:pnHPPavilionSleekbook15:pvr088A1135590320100:rvnHewlett-Packard:rn18FE:rvr82.27:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Sleekbook 15
  dmi.product.version: 088A1135590320100
  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.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Sep 16 17:51:29 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5547 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.1

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

--

[Desktop-packages] [Bug 1370245] Re: wpa_supplicant version 2.2 available

2014-09-17 Thread Filip Sohajek
** Package changed: wpa (Ubuntu) => wpasupplicant (Ubuntu)

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

Title:
  wpa_supplicant version 2.2 available

Status in “wpasupplicant” package in Ubuntu:
  New

Bug description:
  Currently version 2.1 is still the version slated to be shipped with
  utopic. It seems from http://w1.fi/wpa_supplicant/ that wpa_supplicant
  version 2.2 was released in 2014-06. Is it possible for 2.2 to be
  packaged?

  Thanks!

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

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


[Desktop-packages] [Bug 1335942] Re: nvidia-331-updates-dev (and nvidia-331-dev) not istalling required includes

2014-09-17 Thread Graham Inggs
The fix has been released in Utopic and will be backported to Trusty
soon.

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

Title:
  nvidia-331-updates-dev (and nvidia-331-dev) not istalling required
  includes

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have initially open a question and it was suggested to me to open a
  bug report. I am trying to install the include files for OpenGL
  development with the nvidia 331 driver but the packages nvidia-331-dev
  and nvidia-331-updates-dev just do not carry those files under Trusty
  (they did under Precise Pangolin). It is therefore impossible to
  develop OpenGL applications.

  Please see below the original email for a more detailed explanation.

  Thank you so much for your efforts !

  Andrea


  
  Hi

  I am new to Linux system administration. I am trying to install the
  header files for OpenGL development from NVIDIA.

  I have installed nvidia-331-updates-dev , the documentation of this
  pacakge for Precise Pangolin lists the foillowing files:

  /usr/include/nvidia-331-updates/CL/cl.h
  /usr/include/nvidia-331-updates/CL/cl_gl.h
  /usr/include/nvidia-331-updates/CL/cl_platform.h
  /usr/include/nvidia-331-updates/GL/gl.h
  /usr/include/nvidia-331-updates/GL/glext.h
  /usr/include/nvidia-331-updates/GL/glx.h
  /usr/include/nvidia-331-updates/GL/glxext.h
  /usr/include/nvidia-331-updates/cuda/cuda.h
  /usr/include/nvidia-331-updates/cuda/cudaGL.h
  /usr/include/nvidia-331-updates/cuda/cudaVDPAU.h
  /usr/share/doc/nvidia-331-updates-dev/changelog.Debian.gz
  /usr/share/doc/nvidia-331-updates-dev/copyright
  /usr/share/doc/nvidia-331-updates-dev/include

  (see http://packages.ubuntu.com/precise-updates/i386/nvidia-331
  -updates-dev/filelist)

  which include for example GL/gl.h

  the documentation of Trusty lists only

  /usr/share/doc/nvidia-331-updates-dev/changelog.Debian.gz
  /usr/share/doc/nvidia-331-updates-dev/copyright
  /usr/share/doc/nvidia-331-updates-dev/include

  (see http://packages.ubuntu.com/trusty/amd64/nvidia-331-updates-
  dev/filelist)

  what is the correct why under Trusty to install the reguired includes
  files, as under precise Pangolin ?

  Thank you so much for your kind attention !

  Best Regards,

  Andrea

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

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


[Desktop-packages] [Bug 1370091] Re: With music playing, pressing the dialpad keys reduces the volume for an odd interval

2014-09-17 Thread Omer Akram
** Package changed: media-hub (Ubuntu) => pulseaudio (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/1370091

Title:
  With music playing, pressing the dialpad keys reduces the volume for
  an odd interval

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  1. play a track
  2. open dialer-app and press the keypad

  What happens:
  The sound music turns down for a few seconds and then gets back to normal 
automatically.

  While the above feels like a good idea, it need refinement. In its
  current condition it rather feels broken.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Tue Sep 16 19:45:21 2014
  InstallationDate: Installed on 2014-09-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
  SourcePackage: media-hub
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1370091] [NEW] With music playing, pressing the dialpad keys reduces the volume for an odd interval

2014-09-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

1. play a track
2. open dialer-app and press the keypad

What happens:
The sound music turns down for a few seconds and then gets back to normal 
automatically.

While the above feels like a good idea, it need refinement. In its
current condition it rather feels broken.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: media-hub 2.0.0+14.10.20140910.2-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.7-0ubuntu2
Architecture: armhf
Date: Tue Sep 16 19:45:21 2014
InstallationDate: Installed on 2014-09-16 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140916-020205)
SourcePackage: media-hub
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug armhf qa-touch utopic
-- 
With music playing, pressing the dialpad keys reduces the volume for an odd 
interval
https://bugs.launchpad.net/bugs/1370091
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio 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 1350369] Re: soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()

2014-09-17 Thread C de-Avillez
Marking triaged, bug has been confirmed upstream, and no other visible
action is needed as far as triaging is concerned.

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

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

Title:
  soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  Was trying to reproduce this bug:
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/64295 I've
  caused an outright crash.

  Open document
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/64295/+attachment/18400/+files/20061006_final_pres_handout.odt

  1. Put cursor at box under "Joe Selects Option A"
  1. Edit -> Select All (which should select the whole table)
  2. Copy
  3. Put cursor at box under "Joe Selects Option A"
  4. Paste
  5. Undo
  6. Paste
  7. Undo (note how items are left)
  8. Paste
  9. Undo (crashes)

  The cursor might also move around during the above.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: libreoffice-core 1:4.2.4-0ubuntu4
  Uname: Linux 3.16.0-999-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 30 10:07:36 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-04-27 (93 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer 
/tmp/20061006_final_pres_handout.odt --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7f9664eeccaa <_SaveBox::CreateNew(SwTable&, 
SwTableLine&, _SaveTable&)+74>:  mov0x18(%rax),%r15
   PC (0x7f9664eeccaa) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%r15" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   _SaveBox::CreateNew (this=0x2bf5b20, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/inc/swtable.hxx:417
   _SaveBox::CreateNew (this=0x29fda30, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1369
   _SaveBox::CreateNew (this=0x220b6e0, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1369
   _SaveBox::CreateNew (this=0x29f7360, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1369
   _SaveLine::CreateNew (this=0x2be65c0, rTbl=..., rParent=..., rSTbl=...) at 
/build/buildd/libreoffice-4.2.4/sw/source/core/undo/untbl.cxx:1196
  Title: soffice.bin crashed with SIGSEGV in _SaveBox::CreateNew()
  UpgradeStatus: Upgraded to utopic on 2014-07-20 (9 days ago)
  UserGroups: adm cdrom debian-tor dip disk libvirtd lpadmin plugdev sambashare 
sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1350369/+subscriptions

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


[Desktop-packages] [Bug 1369547] Re: MX328 printing freezing at the middle of the printing process

2014-09-17 Thread Till Kamppeter
Thank you for testing, we will include the fix soon.

** Changed in: cups (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  MX328 printing freezing at the middle of the printing process

Status in “cups” package in Ubuntu:
  Triaged

Bug description:
  The driver recognized as Canon MX320 series. Printing works as I click print 
but freezes at the middle of the process, even when trying with print test 
page. My printer led shows it is printing but the machine actually freezed.
  I am using libgutenprintui2-1_5.2.10-3_amd64 and kernel version 
3.16.2-031602-generic by the way.

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

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


[Desktop-packages] [Bug 1370516] Re: Canon MX328 Printing freezed after a few minutes

2014-09-17 Thread Till Kamppeter
*** This bug is a duplicate of bug 1369547 ***
https://bugs.launchpad.net/bugs/1369547

** This bug has been marked a duplicate of bug 1369547
   MX328 printing freezing at the middle of the printing process

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

Title:
  Canon MX328 Printing freezed after a few minutes

Status in “cups” package in Ubuntu:
  New

Bug description:
  Canon MX328 Printing freezed after a few minutes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.17.0-031700rc5-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Wed Sep 17 21:21:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-15 (33 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  Lpstat:
   device for Canon-MX320-series: 
usb://Canon/MX320%20series?serial=169A97&interface=1
   device for test: ///dev/null
  MachineType: MSI MS-7918
  Papersize: letter
  PpdFiles: Canon-MX320-series: Canon MX320 series - CUPS+Gutenprint v5.2.10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700rc5-generic 
root=UUID=ab29f07b-8853-44ef-8aa6-c5b72f1a4b24 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 3 (MS-7918)
  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.:bvrV2.3:bd07/24/2014:svnMSI:pnMS-7918:pvr1.0:rvnMSI:rnZ97GAMING3(MS-7918):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7918
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Desktop-packages] [Bug 1369742] Re: Please add the new ce_RU locale

2014-09-17 Thread Launchpad Bug Tracker
This bug was fixed in the package langpack-locales - 2.13+git20120306-15

---
langpack-locales (2.13+git20120306-15) utopic; urgency=low

  * debian/patches/ubuntu-ce_RU-new_locale.patch:
Addition of the ce_RU locale (LP: #1369742).
 -- Gunnar HjalmarssonMon, 15 Sep 2014 23:22:00 +0200

** Changed in: langpack-locales (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Please add the new ce_RU locale

Status in The GNU C Library:
  Unknown
Status in “langpack-locales” package in Ubuntu:
  Fix Released

Bug description:
  This is a step in making Chechen a language that can be selected in
  Ubuntu.

  Related message at the ubuntu-translators mailing list:
  
https://lists.ubuntu.com/archives/ubuntu-translators/2014-September/006665.html

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

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


[Desktop-packages] [Bug 667752] Re: Non-embedded standard fonts in PDF files are not displayed/rendered correctly

2014-09-17 Thread corax
This problem is still here in Ubuntu 14.04 LTS ... and it has become a serious 
matter.
More and more of my own customers are switching to Ubuntu, which is a positive 
thing IMO.  But with the increasing use of online web-services to handle 
billing, document exchanges and online-shopping ... more and more streaming-PDF 
files are being created on-the-fly as everyone is expected to be able to read 
that particular format.  But when people can't read the amount due on an 
invoice or the delivery-date on a webshopping receipt, because the 
font-rendering of the pre-installed document viewer in Ubuntu won't display 
them correctly (or sometimes not at all), it really becomes highly inconvenient 
for both regular users as well as more experienced user.  The Adobe Reader 
installation package is no longer available in ubuntu 14.04's standard 
repositories, which was a go-to option for the more experienced user.
SO BUCKLE UP PEOPLE, let's see if we can't fix this issue.  And hopefully 
before we use a couple of gigabytes on the web in forum- and chatlogs about the 
subject of creating temporary fixes and work-arounds of such a basic thing.

best of luck to all

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

Title:
  Non-embedded standard fonts in PDF files are not displayed/rendered
  correctly

Status in Evince document viewer:
  Unknown
Status in libcairo  -  cairo vector graphics library:
  Confirmed
Status in “cairo” package in Ubuntu:
  Confirmed
Status in “evince” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: evince

  1)
  Natty:
  lsb_release -rd
  Description:  Ubuntu Natty (development branch)
  Release:  11.04

  Maverick:
  lsb_release -rd
  Description: Ubuntu 10.10
  Release: 10.10

  Lucid:
  Ubuntu 10.04 Lucid Lynx (amd64)

  2)
  Natty:
  apt-cache policy acroread
  acroread:
Installed: 9.4.2-0natty1
Candidate: 9.4.2-0natty1
Version table:
   *** 9.4.2-0natty1 0
  500 http://archive.canonical.com/ubuntu/ natty/partner i386 Packages 
100 /var/lib/dpkg/status

  apt-cache policy evince
  evince:
Installed: 2.32.0-0ubuntu12.1
Candidate: 2.32.0-0ubuntu12.1
Version table:
   *** 2.32.0-0ubuntu12.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   2.32.0-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  apt-cache policy libcairo2
  libcairo2:
Installed: 1.10.2-2ubuntu2
Candidate: 1.10.2-2ubuntu2
Version table:
   *** 1.10.2-2ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 100 
/var/lib/dpkg/status

  Maverick:
  apt-cache policy evince
  evince:
    Installed: 2.32.0-0ubuntu1
    Candidate: 2.32.0-0ubuntu1
    Version table:
   *** 2.32.0-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages
  100 /var/lib/dpkg/status

  apt-cache policy libcairo2
  libcairo2:
    Installed: 1.10.0-1ubuntu3
    Candidate: 1.10.0-1ubuntu3
    Version table:
   *** 1.10.0-1ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.10.0-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ maverick/main i386 Packages

  apt-cache policy acroread
  acroread:
    Installed: 9.4-1maverick1
    Candidate: 9.4-1maverick1
    Version table:
   *** 9.4-1maverick1 0
  500 http://archive.canonical.com/ubuntu/ maverick/partner i386 
Packages
  100 /var/lib/dpkg/status

  3) When viewing PDF attachment "PDF sample for Evince", which has font
  "Times Roman" or "Helvetica", the text looks different in Evince in
  comparison to Adobe Reader.

  4) What is expected is that it looks the same in both.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: evince 2.30.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  Architecture: amd64
  Date: Thu Oct 28 13:51:21 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 
(20100419.1)
  ProcEnviron:
   LANG=en_DK.utf8
   SHELL=/bin/bash
  SourcePackage: evince

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

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


[Desktop-packages] [Bug 1335942] Re: nvidia-331-updates-dev (and nvidia-331-dev) not istalling required includes

2014-09-17 Thread Usr42
Hi,

  "status: In Progress -> Fix Released" for nvidia-graphics-drivers-331
does not mean that the problem is solved in package nvidia-331-updates-
dev, or?

Thanks a lot for your time working on it :-)

Stephan

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

Title:
  nvidia-331-updates-dev (and nvidia-331-dev) not istalling required
  includes

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  I have initially open a question and it was suggested to me to open a
  bug report. I am trying to install the include files for OpenGL
  development with the nvidia 331 driver but the packages nvidia-331-dev
  and nvidia-331-updates-dev just do not carry those files under Trusty
  (they did under Precise Pangolin). It is therefore impossible to
  develop OpenGL applications.

  Please see below the original email for a more detailed explanation.

  Thank you so much for your efforts !

  Andrea


  
  Hi

  I am new to Linux system administration. I am trying to install the
  header files for OpenGL development from NVIDIA.

  I have installed nvidia-331-updates-dev , the documentation of this
  pacakge for Precise Pangolin lists the foillowing files:

  /usr/include/nvidia-331-updates/CL/cl.h
  /usr/include/nvidia-331-updates/CL/cl_gl.h
  /usr/include/nvidia-331-updates/CL/cl_platform.h
  /usr/include/nvidia-331-updates/GL/gl.h
  /usr/include/nvidia-331-updates/GL/glext.h
  /usr/include/nvidia-331-updates/GL/glx.h
  /usr/include/nvidia-331-updates/GL/glxext.h
  /usr/include/nvidia-331-updates/cuda/cuda.h
  /usr/include/nvidia-331-updates/cuda/cudaGL.h
  /usr/include/nvidia-331-updates/cuda/cudaVDPAU.h
  /usr/share/doc/nvidia-331-updates-dev/changelog.Debian.gz
  /usr/share/doc/nvidia-331-updates-dev/copyright
  /usr/share/doc/nvidia-331-updates-dev/include

  (see http://packages.ubuntu.com/precise-updates/i386/nvidia-331
  -updates-dev/filelist)

  which include for example GL/gl.h

  the documentation of Trusty lists only

  /usr/share/doc/nvidia-331-updates-dev/changelog.Debian.gz
  /usr/share/doc/nvidia-331-updates-dev/copyright
  /usr/share/doc/nvidia-331-updates-dev/include

  (see http://packages.ubuntu.com/trusty/amd64/nvidia-331-updates-
  dev/filelist)

  what is the correct why under Trusty to install the reguired includes
  files, as under precise Pangolin ?

  Thank you so much for your kind attention !

  Best Regards,

  Andrea

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

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


[Desktop-packages] [Bug 1358602] Re: guteprint lack epson pm 3000c print filter

2014-09-17 Thread TinBay
yes I can add the printer. I used gimp-guteprint and I can see the
status monitor.

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

Title:
  guteprint lack epson pm 3000c print filter

Status in “gutenprint” package in Ubuntu:
  Incomplete

Bug description:
  guteprint lack epson pm 3000c print filter
  E [13/Aug/2014:08:13:51 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory
  E [13/Aug/2014:08:13:51 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory
  E [13/Aug/2014:08:13:51 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/Generic CMYK Profile.icc" not available: No 
such file or directory
  E [13/Aug/2014:08:13:51 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory
  E [13/Aug/2014:08:16:51 +0800] [Job 4] Unable to send data to printer.
  E [13/Aug/2014:08:21:55 +0800] [Job 4] Stopping unresponsive job.
  E [13/Aug/2014:08:22:05 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory
  E [13/Aug/2014:09:01:42 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory
  E [13/Aug/2014:09:01:42 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory
  E [13/Aug/2014:09:01:42 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/Generic CMYK Profile.icc" not available: No 
such file or directory
  E [13/Aug/2014:09:29:07 +0800] PM-3000C: File 
"/System/Library/ColorSync/Profiles/sRGB Profile.icc" not available: No such 
file or directory

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

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


[Desktop-packages] [Bug 1369547] Re: MX328 printing freezing at the middle of the printing process

2014-09-17 Thread TinBay
Seems adding these two lines below to /usr/share/cups/usb/org.cups.usb-quirks  
solved my problem.
# Canon MX320
0x04A9 0x1736 unidir

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

Title:
  MX328 printing freezing at the middle of the printing process

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  The driver recognized as Canon MX320 series. Printing works as I click print 
but freezes at the middle of the process, even when trying with print test 
page. My printer led shows it is printing but the machine actually freezed.
  I am using libgutenprintui2-1_5.2.10-3_amd64 and kernel version 
3.16.2-031602-generic by the way.

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

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


[Desktop-packages] [Bug 1369547] Re: MX328 printing freezing at the middle of the printing process

2014-09-17 Thread TinBay
Really a odd fix, thank you for pointing it out.

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

Title:
  MX328 printing freezing at the middle of the printing process

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  The driver recognized as Canon MX320 series. Printing works as I click print 
but freezes at the middle of the process, even when trying with print test 
page. My printer led shows it is printing but the machine actually freezed.
  I am using libgutenprintui2-1_5.2.10-3_amd64 and kernel version 
3.16.2-031602-generic by the way.

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

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


[Desktop-packages] [Bug 1369547] Re: MX328 printing freezing at the middle of the printing process

2014-09-17 Thread TinBay
Hello Till Kampeter, I used the automatic bug filling command, the additional 
info is in the link below.
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1370516

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

Title:
  MX328 printing freezing at the middle of the printing process

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  The driver recognized as Canon MX320 series. Printing works as I click print 
but freezes at the middle of the process, even when trying with print test 
page. My printer led shows it is printing but the machine actually freezed.
  I am using libgutenprintui2-1_5.2.10-3_amd64 and kernel version 
3.16.2-031602-generic by the way.

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

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


[Desktop-packages] [Bug 865885] Re: Implement proper clipboard in wayland

2014-09-17 Thread Walker Gusmão
@pyrates Here: http://wayland.freedesktop.org/docs/html/sect-Protocol-
data-sharing.html

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

Title:
  Implement proper clipboard in wayland

Status in Wayland Display Manager:
  Fix Released
Status in “wayland” package in Ubuntu:
  Fix Released

Bug description:
  Well the bug to implement a proper clipboard in xorg has just been set
  to invalid:

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

  So since wayland is replacing xorg, might as well implement a proper
  clipboard.  Please do not follow the path xorg did to implement it.
  Normal users do not want a selection based clipboard.  It's confusing
  for them and if some app wants it, then that app alone can implement
  it.  This way those who need it can get it and the rest of us can go
  about without worrying that when I highlight something, I haven't just
  lost what was copied using ctrl+c.

  Here's a rant on it:

  http://elliotth.blogspot.com/2008/08/desktop-linux-suckage-
  clipboard.html

  And here's a very simple implementation:

  1.  When copying text, copy it directly to the clipboard so that it is there 
even if the application is closed.
  2.  No more selection based copy.  If an app wants it, it can implement it.  
Putty does that on windows and so does mirc.  But it shouldn't be forced upon 
apps if they don't intend to use it.
  3.  When copying something to the clipboard and it is not text, the app must 
specify what kind of data it is so that if it can be used in another app if 
that app says it is compatible with it.  Otherwise when that happens, nothing 
gets pasted if the app says it is not expecting that data type.
  4.  Wayland will monitor when an application wants to exit that has data in 
the clipboard that is above a certain size.  If it is above a certain size, 
when that application wants to exit, then it will ask if the user wants to 
clear the clipboard before the application exits.  This way the application 
developer doesn't have to worry about implementing this, the OS takes care of 
it.
  5.  When copying data to the clipboard, it will report what application it 
came from storing the full path.  This way the above can be done.
  6.  When copying data from the file system, it will be stored in a separate 
clipboard.  It will store the path to the file/directory it is set to copy and 
not the actual copy as that could get very large.
  7.  Finally when copying data to the clipboard, it will indicate if the data 
is to be copied or cut.  If cut, then when it is pasted, it will delete the 
original copy.  If it is copied, it will simply paste it to the place you 
pasted it to from the clipboard.

  I think this is a good start.  As I said, x and now xorg refused to do
  this, so may as well put it in wayland.

  If not, I'll see this being complained about 30 years down the line
  with people asking why wasn't this implemented?

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

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


[Desktop-packages] [Bug 1370175] Re: Libav security fixes Sept 2014

2014-09-17 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/precise-security/libav

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

Title:
  Libav security fixes Sept 2014

Status in “libav” package in Ubuntu:
  Confirmed
Status in “libav” source package in Precise:
  Fix Released
Status in “libav” source package in Trusty:
  Confirmed
Status in “libav” source package in Utopic:
  Confirmed

Bug description:
  Libav 9.17 and 0.8.16 are out, and fix "a number of critical
  functional and security issues (many of which have CVE identifiers
  assigned)"

  http://www.libav.org/news.html

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

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


[Desktop-packages] [Bug 1370516] [NEW] Canon MX328 Printing freezed after a few minutes

2014-09-17 Thread TinBay
Public bug reported:

Canon MX328 Printing freezed after a few minutes

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cups 1.7.2-0ubuntu1.2
ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
Uname: Linux 3.17.0-031700rc5-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CupsErrorLog:
 
CurrentDesktop: XFCE
Date: Wed Sep 17 21:21:49 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-15 (33 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
Lpstat:
 device for Canon-MX320-series: 
usb://Canon/MX320%20series?serial=169A97&interface=1
 device for test: ///dev/null
MachineType: MSI MS-7918
Papersize: letter
PpdFiles: Canon-MX320-series: Canon MX320 series - CUPS+Gutenprint v5.2.10
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700rc5-generic 
root=UUID=ab29f07b-8853-44ef-8aa6-c5b72f1a4b24 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 3 (MS-7918)
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.:bvrV2.3:bd07/24/2014:svnMSI:pnMS-7918:pvr1.0:rvnMSI:rnZ97GAMING3(MS-7918):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7918
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


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

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

Title:
  Canon MX328 Printing freezed after a few minutes

Status in “cups” package in Ubuntu:
  New

Bug description:
  Canon MX328 Printing freezed after a few minutes

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.17.0-031700rc5-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: XFCE
  Date: Wed Sep 17 21:21:49 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-15 (33 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  Lpstat:
   device for Canon-MX320-series: 
usb://Canon/MX320%20series?serial=169A97&interface=1
   device for test: ///dev/null
  MachineType: MSI MS-7918
  Papersize: letter
  PpdFiles: Canon-MX320-series: Canon MX320 series - CUPS+Gutenprint v5.2.10
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700rc5-generic 
root=UUID=ab29f07b-8853-44ef-8aa6-c5b72f1a4b24 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 3 (MS-7918)
  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.:bvrV2.3:bd07/24/2014:svnMSI:pnMS-7918:pvr1.0:rvnMSI:rnZ97GAMING3(MS-7918):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7918
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


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

2014-09-17 Thread RealBezo
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1370505/+attachment/4206302/+files/ProcEnviron.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/1370505

Title:
  lubuntu 14.04 backlight maximum or minimum on lenovo laptop

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

Bug description:
  Hello, i had and have and will this problem on every laptop and with
  every version of ubuntu and  its derivatives.

  I installed lubuntu 14.04 on IBM lenovo laptop with intel graphic card
  and my backlight could be changed with function keys but it goes
  either to maximum or minimum.

  it is similar to my bug previous bug report 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990932
  but this time i can change it before and after login but as i said either to 
max or min ...

  i tried couple of things to solve the problem via trial and error:
  - edited grub conf file and changed "acpi_backlight=legacy" line to 
""acpi_backlight=vendor"  
  -  i created a file /usr/share/X11/xorg.conf.d/20-intel.conf   here and 
edited it like this:

  Section "Device"
  Identifier  "card0"
  Driver  "intel"
  Option  "Backlight" #  "intel_backlight"
  BusID   "PCI:0:2:0"
  EndSection

  (i tried both of "Backlight" and  "intel_backlight" options)

  -and when i start the xubuntu power manager and try  to set backlight
  (which is installed in lubuntu) i can see  the backlight widget on the
  screen but it doesn't effect anything, still backlight goes to max or
  min, but the widget's animation cannot go further than one step, it
  stucks on the first step.

  - i tried to change the value of brightness file under the directory 
/sys/class/backlight/ideapad
  but sudo does not work here, it says permission denied, but when i read the 
value of actual_brightness file i can see 0 or 10 ( of course just these)

  First of all i don't think this is related to kernel, and i don't
  wanna try upstream kernel. I think it is related to xserver package
  and ubuntu acpi management and many configurations file in ubuntu that
  i don't know exactly how many are and where they are...

  Thanks in advance
  --- 
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-03-10 (190 days ago)
  InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20140225)
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Tags:  trusty
  Uname: Linux 3.13.0-35-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Desktop-packages] [Bug 1370505] Re: lubuntu 14.04 backlight maximum or minimum on lenovo laptop

2014-09-17 Thread RealBezo
apport information

** Tags added: apport-collected trusty

** Description changed:

  Hello, i had and have and will this problem on every laptop and with
  every version of ubuntu and  its derivatives.
  
  I installed lubuntu 14.04 on IBM lenovo laptop with intel graphic card
  and my backlight could be changed with function keys but it goes either
  to maximum or minimum.
  
  it is similar to my bug previous bug report 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990932
  but this time i can change it before and after login but as i said either to 
max or min ...
  
  i tried couple of things to solve the problem via trial and error:
  - edited grub conf file and changed "acpi_backlight=legacy" line to 
""acpi_backlight=vendor"  
  -  i created a file /usr/share/X11/xorg.conf.d/20-intel.conf   here and 
edited it like this:
  
  Section "Device"
  Identifier  "card0"
  Driver  "intel"
  Option  "Backlight" #  "intel_backlight"
  BusID   "PCI:0:2:0"
  EndSection
  
  (i tried both of "Backlight" and  "intel_backlight" options)
  
  -and when i start the xubuntu power manager and try  to set backlight
  (which is installed in lubuntu) i can see  the backlight widget on the
  screen but it doesn't effect anything, still backlight goes to max or
  min, but the widget's animation cannot go further than one step, it
  stucks on the first step.
  
  - i tried to change the value of brightness file under the directory 
/sys/class/backlight/ideapad
  but sudo does not work here, it says permission denied, but when i read the 
value of actual_brightness file i can see 0 or 10 ( of course just these)
  
  First of all i don't think this is related to kernel, and i don't wanna
  try upstream kernel. I think it is related to xserver package and ubuntu
  acpi management and many configurations file in ubuntu that i don't know
  exactly how many are and where they are...
  
  Thanks in advance
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.4
+ Architecture: i386
+ CurrentDesktop: LXDE
+ DistroRelease: Ubuntu 14.04
+ InstallationDate: Installed on 2014-03-10 (190 days ago)
+ InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20140225)
+ Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
+ PackageArchitecture: i386
+ ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
+ Tags:  trusty
+ Uname: Linux 3.13.0-35-generic i686
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1370505/+attachment/4206301/+files/Dependencies.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/1370505

Title:
  lubuntu 14.04 backlight maximum or minimum on lenovo laptop

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

Bug description:
  Hello, i had and have and will this problem on every laptop and with
  every version of ubuntu and  its derivatives.

  I installed lubuntu 14.04 on IBM lenovo laptop with intel graphic card
  and my backlight could be changed with function keys but it goes
  either to maximum or minimum.

  it is similar to my bug previous bug report 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990932
  but this time i can change it before and after login but as i said either to 
max or min ...

  i tried couple of things to solve the problem via trial and error:
  - edited grub conf file and changed "acpi_backlight=legacy" line to 
""acpi_backlight=vendor"  
  -  i created a file /usr/share/X11/xorg.conf.d/20-intel.conf   here and 
edited it like this:

  Section "Device"
  Identifier  "card0"
  Driver  "intel"
  Option  "Backlight" #  "intel_backlight"
  BusID   "PCI:0:2:0"
  EndSection

  (i tried both of "Backlight" and  "intel_backlight" options)

  -and when i start the xubuntu power manager and try  to set backlight
  (which is installed in lubuntu) i can see  the backlight widget on the
  screen but it doesn't effect anything, still backlight goes to max or
  min, but the widget's animation cannot go further than one step, it
  stucks on the first step.

  - i tried to change the value of brightness file under the directory 
/sys/class/backlight/ideapad
  but sudo does not work here, it says permission denied, but when i read the 
value of actual_brightness file i can see 0 or 10 ( of course just these)

  First of all i don't think this is related to kernel, and i don't
  wanna try upstream kernel. I think it is related to xserver package
  and ubuntu acpi management and many configurations file in ubuntu that
  i don't know exactly how many are and where they are...

  Thanks in advance
  --- 
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationD

[Desktop-packages] [Bug 1370505] [NEW] lubuntu 14.04 backlight maximum or minimum on lenovo laptop

2014-09-17 Thread RealBezo
Public bug reported:

Hello, i had and have and will this problem on every laptop and with
every version of ubuntu and  its derivatives.

I installed lubuntu 14.04 on IBM lenovo laptop with intel graphic card
and my backlight could be changed with function keys but it goes either
to maximum or minimum.

it is similar to my bug previous bug report 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990932
but this time i can change it before and after login but as i said either to 
max or min ...

i tried couple of things to solve the problem via trial and error:
- edited grub conf file and changed "acpi_backlight=legacy" line to 
""acpi_backlight=vendor"  
-  i created a file /usr/share/X11/xorg.conf.d/20-intel.conf   here and edited 
it like this:

Section "Device"
Identifier  "card0"
Driver  "intel"
Option  "Backlight" #  "intel_backlight"
BusID   "PCI:0:2:0"
EndSection

(i tried both of "Backlight" and  "intel_backlight" options)

-and when i start the xubuntu power manager and try  to set backlight
(which is installed in lubuntu) i can see  the backlight widget on the
screen but it doesn't effect anything, still backlight goes to max or
min, but the widget's animation cannot go further than one step, it
stucks on the first step.

- i tried to change the value of brightness file under the directory 
/sys/class/backlight/ideapad
but sudo does not work here, it says permission denied, but when i read the 
value of actual_brightness file i can see 0 or 10 ( of course just these)

First of all i don't think this is related to kernel, and i don't wanna
try upstream kernel. I think it is related to xserver package and ubuntu
acpi management and many configurations file in ubuntu that i don't know
exactly how many are and where they are...

Thanks in advance

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: backlight

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

Title:
  lubuntu 14.04 backlight maximum or minimum on lenovo laptop

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

Bug description:
  Hello, i had and have and will this problem on every laptop and with
  every version of ubuntu and  its derivatives.

  I installed lubuntu 14.04 on IBM lenovo laptop with intel graphic card
  and my backlight could be changed with function keys but it goes
  either to maximum or minimum.

  it is similar to my bug previous bug report 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/990932
  but this time i can change it before and after login but as i said either to 
max or min ...

  i tried couple of things to solve the problem via trial and error:
  - edited grub conf file and changed "acpi_backlight=legacy" line to 
""acpi_backlight=vendor"  
  -  i created a file /usr/share/X11/xorg.conf.d/20-intel.conf   here and 
edited it like this:

  Section "Device"
  Identifier  "card0"
  Driver  "intel"
  Option  "Backlight" #  "intel_backlight"
  BusID   "PCI:0:2:0"
  EndSection

  (i tried both of "Backlight" and  "intel_backlight" options)

  -and when i start the xubuntu power manager and try  to set backlight
  (which is installed in lubuntu) i can see  the backlight widget on the
  screen but it doesn't effect anything, still backlight goes to max or
  min, but the widget's animation cannot go further than one step, it
  stucks on the first step.

  - i tried to change the value of brightness file under the directory 
/sys/class/backlight/ideapad
  but sudo does not work here, it says permission denied, but when i read the 
value of actual_brightness file i can see 0 or 10 ( of course just these)

  First of all i don't think this is related to kernel, and i don't
  wanna try upstream kernel. I think it is related to xserver package
  and ubuntu acpi management and many configurations file in ubuntu that
  i don't know exactly how many are and where they are...

  Thanks in advance

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

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


[Desktop-packages] [Bug 1090288] Re: The locale file for en_ZA appears to have an error

2014-09-17 Thread Gunnar Hjalmarsson
Martin Pitts comment on IRC:
http://irclogs.ubuntu.com/2014/09/15/%23ubuntu-desktop.html#t14:41

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

Title:
  The locale file for en_ZA appears to have an error

Status in “langpack-locales” package in Ubuntu:
  Confirmed

Bug description:
  I suspect there is a problem with the locale for South Africa. The
  locale file for en_ZA located in /usr/share/i18n/locales has the
  following settings:

  LC_Monetary
  .

  % "."
  mon_decimal_point   ""

  % ","
  mon_thousands_sep   ""
  mon_grouping3;3
  positive_sign   ""
  

  
  LC_NUMERIC
  % "."
  decimal_point   ""

  % ","
  thousands_sep   ""
  grouping3;3
  END LC_NUMERIC

  
  - Unicode character  is for a comma "," and not a full stop "." It 
should be 
  - Unicode character  is for a non-breaking space " " and not a comma 
"," . If it's meant to be a comma it should be 

  South Africa is on the metric system and uses a "." for decimal
  places. The above issue results in the regional settings having a
  comma in the decimal place and causes a number of errors when trying
  to use other software packages.

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

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


[Desktop-packages] [Bug 362359] Re: Focus gets stuck to a window - impossible to select other windows

2014-09-17 Thread dronus
Also happens to me on 12.04 in Gnome Classic Mode from time to time.
Happens to plugged devices or integrated touchpads too.

Using the context menu click and left clicks in some wild fashion may
release the stuck focus, but no clear picture what event exactly
releases the stuck focus.

Triggering of the problem maybe involves wheel scrolling events or
conetxt menu usage in some unusual combination.

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

Title:
  Focus gets stuck to a window - impossible to select other windows

Status in “xorg-server” package in Ubuntu:
  Fix Released

Bug description:
  Alright, terribly annoying bug that gets me to reboot several times a
  day, but very hard to understand how to trigger it.

  What happens: after some time of usage, you get "stuck" in a window. Idem 
est, you can not select another window. 
  You can still click, select and drag in the window that has the focus, but 
clicking on other windows, or on the panel, just doesn't work.

  Notes:
  - With window I don't mean "application window". For example it can only be 
the page view in firefox, and  you won't be able to click the buttons or the 
URL field. It can also be the main text window in xchat, and you wont be able 
to click in the user list or to change the chatroom.
  - The click seems to be grabbed by the window having the focus, even if you 
click outside of it. For example, using xchat, if the main text window has 
focus, clicking and dragging in the user list will actually select text in the 
main text window.
  - Using xev, it seems that clics do not get passed to the correct window at 
all (nothing received)
  - I have no idea what triggers this as sometimes it will trigger alone - pc 
works, I leave it for an hour, I come back, the problem is triggered
  - Curious effect now: dragging and dropping to another window gives focus to 
the window, and seems to be the only way to do so. For example if in firefox 
the main page view window has the focus and I cant click the buttons, drag and 
dropping text to the buttons gives the focus to the buttons, and I can't clic 
the page view window anymore. Drag and dropping a button to the page view 
window gives it its focus back

  
  Additional info: 
  * Compiz disabled
  * Intel graphic card
  * Ubuntu jaunty - latest patches
  * Using a laptop, with an USB mouse

  HAL, xserver, I have no idea where to file this bug into. I hope it will be 
fixed before the release, it is really terribly annoying :s 
  Please tell me if there is any other detail I can provide.

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

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


[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update

2014-09-17 Thread Dimitrios Kanoulas
@Alberto:
> sudo apt-get purge nvidia*
> sudo apt-get install nvidia-331
> sudo apt-get install nvidia-331-updates
> sudo apt-get install nvidia-331-updates-dev

seems to be working now!  My only problem is that version of nvidia
broke the dual monitor system (NVIDIA setting show the monitor X Screen
0 (No Scanout) and does not detect any other monitor that is connected).

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

Title:
  No longer able to use GUI after update

Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Until yesterday the 14.04 install on this Thinkpad T530 (nvidia
  Optimus) with nvidia-331 drivers worked just fine, including excellent
  multi-monitor behavior. Yesterday the set of packages below [1] was
  updated. I shut down, booted this morning and found out that I was not
  shown the lightdm login screen: I was stuck at the purple screen that
  precedes it (into which I enter my disk encryption password).

  Now the funny thing is that I could hear the lightdm startup sound and
  could actually login by typing my password (disk activity and started
  processes verify I am actually logged in), but I can't see anything:
  I'm still stuck at the puple screen.

  Uninstalling the nvidia drivers solved the problem: I'm typing this in
  a browser window using the nouveau drivers.

  I atttempted switching to nvidia-304, but that doesn't work either.
  Using those drivers I am shown the lightdm login screen, but after
  logging in I'm stuck with a screen showing only the background image.
  Nothing else is available, no keyboard or mouse trickery will reveal
  any menu, dialog or terminal to gain access.

  Since nouveau doesn't support a multi-monitor setup, it would be great
  if I someone could tell me how to get the nvidia drivers working
  again.

  Some things I noticed:
  - .xsession-errors reported 'Xlib:  extension "GLX" missing on display ":0"'
  - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied'

  [1] The packages that were updated:

  Start-Date: 2014-09-03  15:07:38
  Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 
(0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 
(0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 
0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 
0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 
(204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 
204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), 
libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), 
xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), 
libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 
(7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1)
  End-Date: 2014-09-03  15:08:06

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-current-updates (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  4 22:07:11 2014
  SourcePackage: nvidia-graphics-drivers-304-updates
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago)

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

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


[Desktop-packages] [Bug 570876] Re: Quadrapassel window is empty when compiz is enabled

2014-09-17 Thread Bug Watch Updater
** Changed in: gnome-games
   Status: New => Expired

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

Title:
  Quadrapassel window is empty when compiz is enabled

Status in GNOME Games:
  Expired
Status in “gnome-games” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-games

  Quadrapassel window is empty with regular flashing graphics when
  compiz is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: quadrapassel 1:2.30.0-0ubuntu6
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  CheckboxSubmission: 87995579fa318483ccc4ab7f6ee116a1
  CheckboxSystem: 9a8dfd7f83677f101ab201cb214a9227
  Date: Tue Apr 27 20:20:11 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406)
  ProcEnviron:
   LANG=es_ES.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-games

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

-- 
Mailing list: https://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   >