date:20140907

you can file a bug report by typing the following command:

ubuntu-bug fglrx (or fglrx-updates, according to the package you're
using).

This will attach most of the relevant logs.

-- 
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 Committed

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.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version:

[Desktop-packages] [Bug 1330037] Re: upower 0.99 transition

** Branch linked: lp:~charlesk/indicator-power/lp-1330037-add-
upower-099-support

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

Title:
  upower 0.99 transition

Status in “cairo-dock-plug-ins” package in Ubuntu:
  Fix Released
Status in “gnome-applets” package in Ubuntu:
  Invalid
Status in “gnome-control-center” package in Ubuntu:
  In Progress
Status in “gnome-packagekit” package in Ubuntu:
  Fix Released
Status in “gnome-power-manager” package in Ubuntu:
  In Progress
Status in “gnome-session” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-shell” package in Ubuntu:
  In Progress
Status in “indicator-power” package in Ubuntu:
  Triaged
Status in “kde-workspace” package in Ubuntu:
  Fix Released
Status in “mate-applets” package in Ubuntu:
  Fix Released
Status in “mate-power-manager” package in Ubuntu:
  Fix Released
Status in “mate-session-manager” package in Ubuntu:
  Fix Released
Status in “mutter” package in Ubuntu:
  In Progress
Status in “powerd” package in Ubuntu:
  New
Status in “python-dbusmock” package in Ubuntu:
  Fix Released
Status in “razorqt” package in Ubuntu:
  New
Status in “sugar-0.96” package in Ubuntu:
  New
Status in “sugar-0.98” package in Ubuntu:
  New
Status in “telepathy-mission-control-5” package in Ubuntu:
  Fix Released
Status in “tracker” package in Ubuntu:
  Fix Committed
Status in “ubuntu-system-settings” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “upower” package in Ubuntu:
  In Progress
Status in “xfce4-power-manager” package in Ubuntu:
  Fix Committed
Status in “xfce4-session” package in Ubuntu:
  Fix Released
Status in “xfce4-settings” package in Ubuntu:
  In Progress
Status in “xfce4-systemload-plugin” package in Ubuntu:
  Fix Committed
Status in “wmbattery” package in Debian:
  Fix Released

Bug description:
  upower 0.99 needs uploading for gnome 3.12. This bug tracks the
  transition.

  A transition is required as some features were removed and the SONAME
  was changed

  Some packages are staged in
  https://launchpad.net/~noskcaj/+archive/upower/+packages

  wmbattery and sugar will probably need removing. If a package only
  needs a rebuild, mark it fix commited, if something else is needed, in
  progress.

  cairo-dock-plug-ins: needs rebuilding
  gnome-applets - patch at bgo:730588
  gnome-shell - ready, just need to drop upower revert.
  gnome-control-center: WIP
  gnome-packagekit: Upower dropped from newest upstream release. Merge from 
debian
  gnome-power-manager: Fixed in newest upstream release. Merge from debian 
experimental
  gnome-session: Done in ppa, needs patches from git or new upstream release
  gnome-settings-daemon: 3.12 is ready out of the box, however that also 
requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is 
mostly working, however had to cherry-pick quite a few patches and may just be 
better to backport 3.12 power plugin. (considering g-s-d patches will be 
temporary, but u-s-d not so)
  kde: works fine with systemd, suspend broken with upstart
  mate: all mate packages need rebuilding
  python-dbusmock: lp:1324791
  sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We 
should remove this from the archive till the next upstream release
  telepathy-mission-control-5: Debian has dropped upower support, needs merging
  wmbattery: needs removal. orphaned upstream/debian and doesn't work with new 
kernals
  xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding
  xfce4-session: patch is upstream, needs work to apply with our current 
patchset
  xfce4-settings: Patch from upstream in ppa
  xfce4-systemload-plugin: needs rebuild

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions

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

Will the above workarounds allow me to use my external monitor again? My
monitor is connected via VGA. I had the same symptoms as the OP, and I
tried the suggestions above and I can now log in but I can no longer
detect my external monitor. In what order should I: purge Nvidia, purge
Nvidia-prime/Nvidia-settings, install the Ubuntu-commons/Nvidia-commons
.deb files, re-install Nvidia-prime, re-install Nvidia drivers?

I am using Ubuntu 14.04 with a ThinkPad W520, and Nvidia Prime.

I'm not sure if this is the right location for my question, but I have a
post [here](http://askubuntu.com/questions/521354/multiple-monitors-and-
nvidia-optimus-not-working-after-apt-get-update).  Any suggestions are
welcome.

-- 
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 1366602] Re: compiz crashed with SIGSEGV in g_closure_invoke()

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

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 #1366351, 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/1366602/+attachment/4198021/+files/CoreDump.gz

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

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

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

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

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

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

** 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/1366602

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
   attempting to create developer platform

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-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: Sun Sep  7 14:42:44 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  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: Toshiba America Info Systems Device [1179:ff11]
 Subsystem: Toshiba America Info Systems Device [1179:ff11]
  InstallationDate: Installed on 2014-08-31 (7 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140719)
  MachineType: TOSHIBA Satellite L500
  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-13-generic 
root=UUID=44315abb-f6d7-4724-885c-a50e4aec342a ro quiet splash
  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 cdrom dip lpadmin plugdev sambashare sudo
  XorgLogOld:
   
  dmi.bios.date: 12/15/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.50
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.50:bd12/15/2009:svnTOSHIBA:pnSatelliteL500:pvrPSLU0U-0HD039:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite L500
  dmi.product.version: PSLU0U-0HD039
  dmi.sys.vendor: TOSHIBA
  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: lib

[Desktop-packages] [Bug 1333962] Re: [Lenovo ThinkPad W530] Unsynchronised rendering on secondary displays

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Lenovo ThinkPad W530] Unsynchronised rendering on secondary displays

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  When attaching a secondary display, any activity on the second display
  is displayed after a lag. This includes, typing, cursor movement, or
  anything else.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  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.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jun 24 12:53:37 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K1000M] [10de:0ffc] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:21f5]
  InstallationDate: Installed on 2014-04-21 (63 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 2436CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=ba40989a-c581-489b-bcc4-c159c39d42a2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jun 24 11:09:19 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)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16561 
   vendor LEN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1338266] Re: Random Freeze Intel Gen7 14.04

[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Random Freeze Intel Gen7 14.04

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Expired

Bug description:
  VGA compatible controller: Intel Corporation ValleyView Gen7 (rev 0c)

  X freezes solid on Fluxbox, Gnome, KDE, XFCE ..ETC

  It does not leave any kind of Error Logs and I have no clue as to why.
  I have tried both 32bit and 64bit versions of the 14.04 version of the
  OS. This error is also preasant in Mint along with other variants of
  Ubuntu.

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

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

[Desktop-packages] [Bug 1366661] [NEW] Xorg freeze

2014-09-07 Thread Luiz

Public bug reported:

My system freezes always while i am playing cs source dust2 map. The
system shutdown and a see a message in logs: nvidia has fallen off bus.

I search for another relevant information without success.

I am using kernel 3.10.54 with nvidia 331.89 proprietary driver.

Some people said nouveau doesnt has a crash like that, so maybe it is
the only solution...

Any help is welcome.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
Uname: Linux 3.10.54 x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Sep  8 00:37:22 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation GF114M [GeForce GTX 580M] [10de:1211] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer Device [1558:5102]
InstallationDate: Installed on 2014-06-14 (85 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: CLEVO P150HMx
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.54 
root=UUID=727896fd-6717-4299-ad41-e259af78a16f ro quiet debug 
intel_pstate=disable pcie_aspm=default pcie_pme=nomsi acpi.debug_layer=0x2 
acpi.debug_level=0x pci=nocrs
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: P150HMx
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: CLEVO
dmi.chassis.version: Not Applicable
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnCLEVO:pnP150HMx:pvrNotApplicable:rvnCLEVO:rnP150HMx:rvrNotApplicable:cvnCLEVO:ct10:cvrNotApplicable:
dmi.product.name: P150HMx
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO
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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
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 N/A
xserver.bootTime: Mon Sep  8 00:30:25 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: amd64 apport-bug compiz-0.9 freeze possible-manual-nvidia-install 
trusty ubuntu

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

Title:
  Xorg freeze

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My system freezes always while i am playing cs source dust2 map. The
  system shutdown and a see a message in logs: nvidia has fallen off
  bus.

  I search for another relevant information without success.

  I am using kernel 3.10.54 with nvidia 331.89 proprietary driver.

  Some people said nouveau doesnt has a crash like that, so maybe it is
  the only solution...

  Any help is welcome.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  Uname: Linux 3.10.54 x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.89  Tue Jul  1 13:30:18 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd

[Desktop-packages] [Bug 1366642] Re: Resume laptop sometimes shows no lock screen, sometimes lock screen with no text input.

2014-09-07 Thread Robert Ancell

** Package changed: lightdm (Ubuntu) => unity (Ubuntu)

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

Title:
  Resume laptop sometimes shows no lock screen, sometimes lock screen
  with no text input.

Status in “unity” package in Ubuntu:
  New

Bug description:
  Resuming on 14.04 sometimes fails to show the lock screen, rarely it
  may show the lock screen but have no input to type the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  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.3
  Architecture: amd64
  Date: Sat Sep  6 22:05:56 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (287 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (140 days ago)

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

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

[Desktop-packages] [Bug 1362963] Re: findsmb command is missing from smbclient package

2014-09-07 Thread Luke Yelavich

** Package changed: at-spi2-core (Ubuntu) => samba (Ubuntu)

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

Title:
  findsmb command is missing from smbclient package

Status in “samba” package in Ubuntu:
  New

Bug description:
  [Note: I cannot report this using apport-bug as that command is
  currently failing on this system.]

  The findsmb command is missing from the package:  smbclient 2.4.1.6
  +dfsg-1ubuntu2.14.04.3

  Note that the manual page is included, but the command itself is
  missing.

  There is also some confusing regarding the documentation.  Here is the
  manpage for the trusty distribution:

  http://manpages.ubuntu.com/manpages/trusty/man1/findsmb.1.html

  Notice that it indicates that this command is included in  
smbclient_4.1.3+dfsg-2ubuntu5_i386
  Is this correct notation?  Are the 64-bit packages not documented, or is this 
another bug?

  The findsmb command is supposed to be a perl script so it should really be 
package independent.
  Can the file be downloaded from some location?

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

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

[Desktop-packages] [Bug 1366648] [NEW] package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade: paquetes en conflicto - no se instalará libreoffice-core

2014-09-07 Thread RADIONAUTA

Public bug reported:

repeatedly over  and over... appears this error

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libreoffice-core 1:3.5.7-0ubuntu5
ProcVersionSignature: Ubuntu 3.5.0-52.78~precise1-generic 3.5.7.33
Uname: Linux 3.5.0-52-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
Date: Sun Sep  7 21:43:32 2014
DuplicateSignature: package:libreoffice-core:1:3.5.7-0ubuntu5:paquetes en 
conflicto - no se instalará libreoffice-core
ErrorMessage: paquetes en conflicto - no se instalará libreoffice-core
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
MarkForUpload: True
SourcePackage: libreoffice
Title: package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade: 
paquetes en conflicto - no se instalará libreoffice-core
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 precise

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

Title:
  package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade:
  paquetes en conflicto - no se instalará libreoffice-core

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  repeatedly over  and over... appears this error

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-core 1:3.5.7-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-52.78~precise1-generic 3.5.7.33
  Uname: Linux 3.5.0-52-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Sun Sep  7 21:43:32 2014
  DuplicateSignature: package:libreoffice-core:1:3.5.7-0ubuntu5:paquetes en 
conflicto - no se instalará libreoffice-core
  ErrorMessage: paquetes en conflicto - no se instalará libreoffice-core
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade: 
paquetes en conflicto - no se instalará libreoffice-core
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1366648] Re: package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade: paquetes en conflicto - no se instalará libreoffice-core

** Tags removed: need-duplicate-check

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

Title:
  package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade:
  paquetes en conflicto - no se instalará libreoffice-core

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  repeatedly over  and over... appears this error

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-core 1:3.5.7-0ubuntu5
  ProcVersionSignature: Ubuntu 3.5.0-52.78~precise1-generic 3.5.7.33
  Uname: Linux 3.5.0-52-generic i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Sun Sep  7 21:43:32 2014
  DuplicateSignature: package:libreoffice-core:1:3.5.7-0ubuntu5:paquetes en 
conflicto - no se instalará libreoffice-core
  ErrorMessage: paquetes en conflicto - no se instalará libreoffice-core
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MarkForUpload: True
  SourcePackage: libreoffice
  Title: package libreoffice-core 1:3.5.7-0ubuntu5 failed to install/upgrade: 
paquetes en conflicto - no se instalará libreoffice-core
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot

2014-09-07 Thread MikeyB

Looks like this also affects my configuration:
http://askubuntu.com/q/520051/9083

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

Title:
  bridge_ignore_without_connections.patch breaks NM created bridge at
  boot

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

Bug description:
  I've created a bridge with network-manager-gnome, the bridge slave
  physical device is eth0. After a reboot the bridge is brought up, but
  eth0 isn't attached.

  First test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical 
device is eth0 and remove all other connections. After a reboot the bridge is 
brought up, but eth0 isn't attached. When I open 
/etc/NetworkManager/NetworkManager.conf and save it without any modification, 
eth0 is instantly added to my bridge. Strange!

  Second test-case:
  Created a bridge with network-manager-gnome with the bridge slave physical 
device is eth0. Disable the "autoconnect" of the default wired network. After a 
reboot the bridge is brought up, but eth0 isn't  attached. Instead eth0 is 
brought up and full configured.

  After compiling and testing different upstream versions, i could track
  the problem down to bridge_ignore_without_connections.patch.  A
  network-manager package without this specific patch, brings my bridge
  up at boot and adds eth0 to the bridge in both test-cases.

  I've checked the behaviour on my ubuntu 13.10 box with network-manager
  (0.9.8.0-0ubuntu22)  and the trusty version network-manager
  (0.9.8.8-0ubuntu1) .

  Till now i couldn't  encounter any sideeffects of removing this patch
  with the bridge created by libvirt.

  Regards
  Mathias Kresin

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

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

[Desktop-packages] [Bug 1366642] [NEW] Resume laptop sometimes shows no lock screen, sometimes lock screen with no text input.

2014-09-07 Thread NoBugs!

Public bug reported:

Resuming on 14.04 sometimes fails to show the lock screen, rarely it may
show the lock screen but have no input to type the password.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.1-0ubuntu1
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.3
Architecture: amd64
Date: Sat Sep  6 22:05:56 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-11-23 (287 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to trusty on 2014-04-19 (140 days ago)

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

Title:
  Resume laptop sometimes shows no lock screen, sometimes lock screen
  with no text input.

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Resuming on 14.04 sometimes fails to show the lock screen, rarely it
  may show the lock screen but have no input to type the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  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.3
  Architecture: amd64
  Date: Sat Sep  6 22:05:56 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-11-23 (287 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (140 days ago)

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

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

[Desktop-packages] [Bug 1366284] Re: Failed to issue method call: Unit nvidia-prime.service failed to load: No such file or directory.

2014-09-07 Thread Daniel van Vugt

** Summary changed:

- Unit nvidia-prime.service failed to load: No such file or directory
+ Failed to issue method call: Unit nvidia-prime.service failed to load: No 
such file or directory.

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

Title:
  Failed to issue method call: Unit nvidia-prime.service failed to load:
  No such file or directory.

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

Bug description:
  Utopic i386 with gtx 750 and q9550 (no builtin gpu here) using
  systemd-boot

  Follow up lp:1365336 nvidia-331 package

  error about nvidia-prime at build time:

  oem@u32:~$ sudo apt-get install --reinstall nvidia-331
  [sudo] password for oem:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/27,7 MB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 216738 files and directories currently installed.)
  Preparing to unpack .../nvidia-331_331.89-0ubuntu3_i386.deb ...
  Removing all DKMS Modules
  Done.
  Unpacking nvidia-331 (331.89-0ubuntu3) over (331.89-0ubuntu3) ...
  Processing triggers for man-db (2.6.7.1-1) ...
  Processing triggers for ureadahead (0.100.0-16) ...
  Setting up nvidia-prime (0.6.6) ...
  Failed to issue method call: Unit nvidia-prime.service failed to load: No 
such file or directory.
  invoke-rc.d: initscript nvidia-prime, action "start" failed.
  dpkg: error processing package nvidia-prime (--configure):
   subprocess installed post-installation script returned error exit status 6
  Setting up nvidia-331 (331.89-0ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  INFO:Enable nvidia-331
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here
  DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude
  Loading new nvidia-331-331.89 DKMS files...
  Building only for 3.16.0-13-generic
  Building for architecture i686
  Building initial module for 3.16.0-13-generic
  Done.

  nvidia_331:
  Running module version sanity check.
   - Original module
     - No original module exists within this kernel
   - Installation
     - Installing to /lib/modules/3.16.0-13-generic/updates/dkms/

  depmod

  DKMS: install completed.
  Processing triggers for initramfs-tools (0.103ubuntu8) ...
  update-initramfs: Generating /boot/initrd.img-3.16.0-13-generic
  Errors were encountered while processing:
   nvidia-prime
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Sep  6 10:52:02 2014
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

  Note: uninstalling the faulty nvidia-prime package does not let
  booting with nvidia (jockey fails to find nvidia driver) and then
  'nouveau' is used

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

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

[Desktop-packages] [Bug 1275042] Re: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC

Launchpad has imported 11 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=72877.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

On 2013-12-19T11:25:43+00:00 Christian Zigotzky wrote:

Hi all,

I've tried Mesa 9.2.2-1 and 10.0.0-1 on Debian Sid and Lubuntu 13.10.
Unfortunately both have issued false colors in games. They appear to be
ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc.

Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem.

The transitional solution is to install the old Mesa 8.0.X with "Force
Version" with the Synaptic package manager on new distributions.

Hardware:

AmigaOne X1000 (Nemo)
PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU
"Xena" 500MHz XMOS XS1-L2 124
8GB DDR2 SDRAM
HIS Radeon HD 6870, 1 GB RAM
OCZ600MXSP 600 Switching power supply
RTL 8139/8139C/8139C+ network card
TSSTcorp CDDVDW SH-224BB dvd drive
ATA ST2000DM001-9YN1 SEAGATE HD
ATA ESA 3SF1240GB HD

More information:

http://en.wikipedia.org/wiki/AmigaOne_X1000
http://www.supertuxkart-amiga.de/amiga/x1000.html

Rgds,
Christian

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/0

On 2013-12-19T19:47:53+00:00 Curaga wrote:

More specifically, this bug is about BGRA vertex colors,
GL_EXT_vertex_array_bgra, seen in SuperTuxKart math level for example.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/1

On 2013-12-20T03:21:07+00:00 Michel-daenzer wrote:

This is probably due to commit 2151d893fbd4a4be092098170e2fbca8c35797a5
('gallium: Fix llvmpipe on big-endian machines'). The r600g driver needs
to be adapted for the changed PIPE_FORMAT_* semantics.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/2

On 2013-12-30T18:02:30+00:00 Christian Zigotzky wrote:

(In reply to comment #2)
> This is probably due to commit 2151d893fbd4a4be092098170e2fbca8c35797a5
> ('gallium: Fix llvmpipe on big-endian machines'). The r600g driver needs to
> be adapted for the changed PIPE_FORMAT_* semantics.

I don't know if I have correct understand your answer. Is the bug fixed?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/3

On 2014-01-06T09:18:43+00:00 Michel-daenzer wrote:

(In reply to comment #3)
> Is the bug fixed?

Not yet. To fix it, the r600g driver needs to be adapted to changes in
the way the Gallium3D infrastructure deals with big endian hosts.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/4

On 2014-01-06T11:30:53+00:00 Christian Zigotzky wrote:

(In reply to comment #4)
> (In reply to comment #3)
> > Is the bug fixed?
> 
> Not yet. To fix it, the r600g driver needs to be adapted to changes in the
> way the Gallium3D infrastructure deals with big endian hosts.

Hi Michel,

Thanks a lot for your answer. :-) We had a problem with wrong colors in
SuperTuxKart 0.8 last year. The Irrlicht guys have released a little
hack for Irrlicht on Linux PPC
(http://irrlicht.sourceforge.net/forum/viewtopic.php?f=7&t=48577). They
told me that is a driver bug, and that workaround costs performance and
RAM. Unfortunately this workaround isn't suitable for Mesa 9.2 and
higher. At this time we have to install Mesa 9.1.X and lower on new
Linux distributions like Lubuntu 13.10, Debian Sid etc. It would be nice
to solve this issue because we don't need the workaround in the future.

All the best,

Christian

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/5

On 2014-01-06T21:06:42+00:00 Christian Zigotzky wrote:

Created attachment 91561
Lubuntu 13.10 PowerPC (Kernel 3.13-rc7) with the old Mesa 8.0.2

Lubuntu 13.10 PowerPC (Kernel 3.13-rc7) with the old Mesa 8.0.2. 3D
acceleration works well in the fullscreen mode.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/6

On 2014-01-06T22:39:08+00:00 Christian Zigotzky wrote:

Created attachment 91566
glxgears has wrong colors with Mesa 10.0.1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1275042/comments/7

On 2014-02-02T12:07:35+00:00 Christian Zigotzky wrote:

Hi All,

I've installed Mesa 10.0.2 on Debian Sid

[Desktop-packages] [Bug 1366260] Re: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

2014-09-07 Thread João Roberto Lamberti

Ao atualizar o Kernel no Terminal apareceu a seguinte mensagem "Error!
Bad return status for module build on kernel: 3.16.2-031602-lowlatency
(i686)"

** Attachment added: ""Error! Bad return status for module build on kernel: 
3.16.2-031602-lowlatency (i686)""
   
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1366260/+attachment/4198194/+files/%2522Error%21%20Bad%20return%20status%20for%20module%20build%20on%20kernel%3A%203.16.2-031602-lowlatency%20%28i686%29%2522

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

Title:
  fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

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

Bug description:
  Ao fazer atualização do Kernel apareceu a seguinte mensagem "Error!
  Bad return status for module build on kernel: 3.16.2-031602-lowlatency
  (i686)"

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:13.350.1-0ubuntu2
  Uname: Linux 3.16.1-031601-lowlatency i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.16.2-031602-generic
  Date: Sat Sep  6 00:53:45 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.350.1: added
   vboxhost, 4.3.14, 3.16.1-031601-generic, i686: installed
   vboxhost, 4.3.14, 3.16.1-031601-lowlatency, i686: installed
   vboxhost, 4.3.14, 3.16.2-031602-generic, i686: installed
   vboxhost, 4.3.14, 3.16.2-031602-lowlatency, i686: installed
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Device [1019:2267]
  InstallationDate: Installed on 2014-06-01 (96 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: POSITIVO POS-EINM10CB
  PackageVersion: 2:13.350.1-0ubuntu2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.1-031601-lowlatency 
root=UUID=c4f21686-6e48-46f5-aee6-46518cdf05b2 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  Title: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.vendor: Desenvolvida para Positivo Informatica SA
  dmi.bios.version: 080015
  dmi.board.name: POS-EINM10CB
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: SIM
  dmi.chassis.type: 3
  dmi.chassis.vendor: POSITIVO
  dmi.modalias: 
dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr080015:bd06/09/2011:svnPOSITIVO:pnPOS-EINM10CB:pvr0906_SIM:rvnPositivoInformaticaSA:rnPOS-EINM10CB:rvrSIM:cvnPOSITIVO:ct3:cvr:
  dmi.product.name: POS-EINM10CB
  dmi.product.version: 0906_SIM
  dmi.sys.vendor: POSITIVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.56+git20140801.5d835797-0ubuntu0sarvatt~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.4.0~git20140904.3dbf55c1-0ubuntu0sarvatt~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.4.0~git20140904.3dbf55c1-0ubuntu0sarvatt~trusty
  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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914+git20140904.aa10f480-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty
  xserver.bootTime: Sat Sep  6 00:14:41 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:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
http

[Desktop-packages] [Bug 1366641] [NEW] Bitcoin Support in Currency Format field (Calc)

Public bug reported:

Given that the world now has a standard international currency
(Bitcoin), it's probably about time that Libreoffice Calc support as
part of its

To reproduce:
Create new spreadsheet
enter number into a cell
right click on cell
Format Cells
Category ->Currency
Format: 
Currently set to the default to your locale, which is reasonable, however there 
is no option under

CAD $ English (Canada)

for

BTC ฿ English (Canada)

as there probably should be by this point.  Decimal points should
probably be 4, up to a maximum of 8.

I did some digging and found there was a directory of locales at
i18npool/source/localedata/data/ which seems to be where currency data
is stored but since I can't build from source it's difficult to really
get a full understanding of what's actually happening.

  

  BTC
  ฿
  BTC
  Bitcoin
  8

  

may need to be inserted into all locales, as Bitcoin is an international
currency it should be an option in all locales.

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

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

Title:
  Bitcoin Support in Currency Format field (Calc)

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Given that the world now has a standard international currency
  (Bitcoin), it's probably about time that Libreoffice Calc support as
  part of its

  To reproduce:
  Create new spreadsheet
  enter number into a cell
  right click on cell
  Format Cells
  Category ->Currency
  Format: 
  Currently set to the default to your locale, which is reasonable, however 
there is no option under

  CAD $ English (Canada)

  for

  BTC ฿ English (Canada)

  as there probably should be by this point.  Decimal points should
  probably be 4, up to a maximum of 8.

  I did some digging and found there was a directory of locales at
  i18npool/source/localedata/data/ which seems to be where currency data
  is stored but since I can't build from source it's difficult to really
  get a full understanding of what's actually happening.


  
BTC
฿
BTC
Bitcoin
8
  


  may need to be inserted into all locales, as Bitcoin is an
  international currency it should be an option in all locales.

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

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

[Desktop-packages] [Bug 1366637] [NEW] Synaptics' Precision Touchpad misdected as PS/2

2014-09-07 Thread Patrick Carlock

Public bug reported:

Ubuntu 14.04.1 LTS  (64-bit)
version 1.7.4-0ubuntu1
It's an Acer Aspire E 11 (E3-111-C0WA), which should have Synaptics' "Microsoft 
Precision TouchPad".
September 5th: The touchpad worked upon installation, but lost all 
functionality after I installed the updates and rebooted.

I updated gpointing-device-settings through Synaptic.  Although I recall
that this wasn't always so, currently there are touchpad settings in
Mouse & Touchpad, but still no functionality.


cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio2/input0
S: Sysfs=/devices/platform/i8042/serio2/input/input10
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=5
B: EV=b
B: KEY=e520 61 0 0 0 0
B: ABS=66080001103

The terminal gives no response to
cat /proc/bus/input/devices > ~/devices


xinput --list
SynPS/2 Synaptics TouchPad  id=12   [slave  pointer 
 (2)]


cat /var/log/Xorg.0.log | grep -i synaptics
[16.692] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/event5)
[16.692] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev 
touchpad catchall"
[16.693] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad 
catchall"
[16.693] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default 
clickpad buttons"
[16.693] (II) LoadModule: "synaptics"
[16.693] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[16.693] (II) Module synaptics: vendor="X.Org Foundation"
[16.693] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics 
TouchPad'
[16.693] (**) SynPS/2 Synaptics TouchPad: always reports core events
[16.712] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 
5662 (res 0)
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 
4728 (res 0)
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 
15
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double 
triple
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[16.712] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[16.712] (**) SynPS/2 Synaptics TouchPad: always reports core events
[16.732] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics 
TouchPad" (type: TOUCHPAD, id 12)
[16.732] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is 
now constant deceleration 2.5
[16.732] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is 
now 1.75
[16.732] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is 
now 0.037
[16.732] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration 
scheme 1
[16.732] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[16.732] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[16.732] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[16.732] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[16.733] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad 
(/dev/input/mouse0)
[16.733] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass 
"touchpad ignore duplicates"

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

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

Title:
  Synaptics' Precision Touchpad misdected as PS/2

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

Bug description:
  Ubuntu 14.04.1 LTS  (64-bit)
  version 1.7.4-0ubuntu1
  It's an Acer Aspire E 11 (E3-111-C0WA), which should have Synaptics' 
"Microsoft Precision TouchPad".
  September 5th: The touchpad worked upon installation, but lost all 
functionality after I installed the updates and rebooted.

  I updated gpointing-device-settings through Synaptic.  Although I
  recall that this wasn't always so, currently there are touchpad
  settings in Mouse & Touchpad, but still no functionality.

  
  cat /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio2/input0
S: Sysfs=/devices/platform/i8042/serio2/input/input10
U: Uniq=
H: Handlers=mouse0 event5 
B: PROP=5
B: EV=b
B: KEY=e520 61 0 0 0 0
B: ABS=66080001103

  The terminal gives no response to
cat /proc/bus/input/devices > ~/devices

  
  xinput --list
SynPS/2 Synaptics TouchPad

[Desktop-packages] [Bug 1366634] [NEW] multiple podcast add causes crash

2014-09-07 Thread Brian Sipos

Public bug reported:

On a fresh install, when attempting to add all of my desired podcasts:
1. Open rhythmbox
2. Select podcasts side-tab
3. Click "Add" tool button and follow procedure to properly add the podcast 
feed.
4. Click "Add" tool button a second time, the program crashes.

If I close and re-open rhythmbox between steps #3 and #4 then no crash
occurs, i.e. it's only when adding more than one podcast per rhythmbox
session. I am comfortable getting stack traces, etc. as needed on this.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rhythmbox 3.0.2-0ubuntu2
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.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep  7 20:25:23 2014
InstallationDate: Installed on 2014-09-05 (2 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: rhythmbox
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  multiple podcast add causes crash

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  On a fresh install, when attempting to add all of my desired podcasts:
  1. Open rhythmbox
  2. Select podcasts side-tab
  3. Click "Add" tool button and follow procedure to properly add the podcast 
feed.
  4. Click "Add" tool button a second time, the program crashes.

  If I close and re-open rhythmbox between steps #3 and #4 then no crash
  occurs, i.e. it's only when adding more than one podcast per rhythmbox
  session. I am comfortable getting stack traces, etc. as needed on
  this.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: rhythmbox 3.0.2-0ubuntu2
  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.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  7 20:25:23 2014
  InstallationDate: Installed on 2014-09-05 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  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/1366634/+subscriptions

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

[Desktop-packages] [Bug 1348251] Re: please make use of pam_tally2 for Touch login and screenunlock

** Branch linked: lp:lightdm/1.10

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

Title:
  please make use of pam_tally2 for Touch login and screenunlock

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “ubuntu-touch-session” package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Touch will soon have/now has the ability to set a PIN/password
  for the user. If the password is set, we should provide some
  protection against brute force password guessing since many users will
  choose to use PINs rather than proper passwords. This is required for
  devices for RTM, but not for the traditional Ubuntu desktop.

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

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

[Desktop-packages] [Bug 1366633] Re: FTBFS sources.ver: No such file or directory

same result with:

1) ran autoconf
2) tried to run 'make'

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

Title:
  FTBFS sources.ver: No such file or directory

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  1) ran autoconf
  2) ran configure
  3) tried to run 'make'
  result:

  themusicgod1@Darwin:~/libreoffice/libreoffice-4.3.1~rc2$ make
  bash: /home/themusicgod1/libreoffice/libreoffice-4.3.1~rc2/sources.ver: No 
such file or directory
  Makefile:193: *** Error while retrieving $lo_sources_ver from 
/home/themusicgod1/libreoffice/libreoffice-4.3.1~rc2/sources.ver.  Stop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep  7 20:11:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (60 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 134738] Re: Cisco - Misc Video Camera pastes icon in opposite direction of what is shown

** Changed in: dia
   Status: Confirmed => Fix Released

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

Title:
  Cisco - Misc Video Camera pastes icon in opposite direction of what is
  shown

Status in Dia - Diagram Tool:
  Fix Released
Status in “dia” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: dia
  1) lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy dia
  dia:
    Installed: 0.97.2-15ubuntu1
    Candidate: 0.97.2-15ubuntu1
    Version table:
   *** 0.97.2-15ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen in a new diagram is on the left hand
  side click the drop down box (by default notes Flowchart) and change
  this to Cisco - Misc > scroll down to where it is a video camera with
  the lens pointing right > click this icon > click in the main diagram
  area and the icon should be pasted with the lens pointing to the
  right.

  4) What happens instead is it pastes a camera with the lens pointing
  to the left.

  First identified in Dia version 0.96.1.

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

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

[Desktop-packages] [Bug 1366633] [NEW] FTBFS sources.ver: No such file or directory

Public bug reported:

1) ran autoconf
2) ran configure
3) tried to run 'make'
result:

themusicgod1@Darwin:~/libreoffice/libreoffice-4.3.1~rc2$ make
bash: /home/themusicgod1/libreoffice/libreoffice-4.3.1~rc2/sources.ver: No such 
file or directory
Makefile:193: *** Error while retrieving $lo_sources_ver from 
/home/themusicgod1/libreoffice/libreoffice-4.3.1~rc2/sources.ver.  Stop.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep  7 20:11:18 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-09 (60 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  FTBFS sources.ver: No such file or directory

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  1) ran autoconf
  2) ran configure
  3) tried to run 'make'
  result:

  themusicgod1@Darwin:~/libreoffice/libreoffice-4.3.1~rc2$ make
  bash: /home/themusicgod1/libreoffice/libreoffice-4.3.1~rc2/sources.ver: No 
such file or directory
  Makefile:193: *** Error while retrieving $lo_sources_ver from 
/home/themusicgod1/libreoffice/libreoffice-4.3.1~rc2/sources.ver.  Stop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep  7 20:11:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (60 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1354341] Re: 14.10 Wallpapers package

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

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Confirmed

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

Title:
  14.10 Wallpapers package

Status in “ubuntu-wallpapers” package in Ubuntu:
  Confirmed

Bug description:
  This is the bug we'll attach the wallpapers to for the 14.10 release!

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

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

[Desktop-packages] [Bug 1348251] Re: please make use of pam_tally2 for Touch login and screenunlock

2014-09-07 Thread Robert Ancell

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

** Changed in: lightdm/1.10
   Status: New => Fix Committed

** Changed in: lightdm/1.10
Milestone: None => 1.10.2

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

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

Title:
  please make use of pam_tally2 for Touch login and screenunlock

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “ubuntu-touch-session” package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Touch will soon have/now has the ability to set a PIN/password
  for the user. If the password is set, we should provide some
  protection against brute force password guessing since many users will
  choose to use PINs rather than proper passwords. This is required for
  devices for RTM, but not for the traditional Ubuntu desktop.

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

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

[Desktop-packages] [Bug 1366631] [NEW] FTBFS configure: error: could not find function 'krb5_sendauth'

Public bug reported:

1) apt-src install libreoffice
2) run autogen script:

...
checking Python.h presence... yes
checking for Python.h... yes
checking for correct python library version... ok
checking whether to build the MariaDB/MySQL Connector extension... no
checking which hsqldb to use... internal
checking whether hsqldb should be built with JDBC 4.1... yes
checking PostgreSQL C interface... checking for library containing com_err... 
-lcom_err
checking for library containing krb5_sendauth... no
configure: error: could not find function 'krb5_sendauth' required for Kerberos 
5
Error running configure at ./autogen.sh line 257.
themusicgod1@Darwin:~/libreoffice/libreoffice-4.3.1~rc2$ 

installing libkrb5-dev and you don't get this error, autogen.sh succeeds

ie libkrb5-dev seems to be required by libreoffice, but apt-src does not
install it as a dependency.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Sep  7 18:12:56 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-09 (60 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  FTBFS configure: error: could not find function 'krb5_sendauth'

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  1) apt-src install libreoffice
  2) run autogen script:

  ...
  checking Python.h presence... yes
  checking for Python.h... yes
  checking for correct python library version... ok
  checking whether to build the MariaDB/MySQL Connector extension... no
  checking which hsqldb to use... internal
  checking whether hsqldb should be built with JDBC 4.1... yes
  checking PostgreSQL C interface... checking for library containing com_err... 
-lcom_err
  checking for library containing krb5_sendauth... no
  configure: error: could not find function 'krb5_sendauth' required for 
Kerberos 5
  Error running configure at ./autogen.sh line 257.
  themusicgod1@Darwin:~/libreoffice/libreoffice-4.3.1~rc2$ 

  installing libkrb5-dev and you don't get this error, autogen.sh
  succeeds

  ie libkrb5-dev seems to be required by libreoffice, but apt-src does
  not install it as a dependency.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Sep  7 18:12:56 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-09 (60 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140708)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-09-07 Thread Chris Page

This doesn't ever seem to be going away. Why not just add 334 to the
standard repo.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

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

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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

[Desktop-packages] [Bug 305927] Re: gedit leaks memory

** Changed in: gedit
   Status: New => Confirmed

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

Title:
  gedit leaks memory

Status in Light-Weight Text Editor for Gnome:
  Confirmed
Status in “gedit” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gedit

  It seems gedit doesn't release the memory used to open a file when
  closing it making it so use ridiculous space in ram for little files
  if you opened a big file and closed it. Strangely gnome system monitor
  reports a lower memory use under the processes tab, but reports the
  used ram in the resources tab and top actually gives the high amounts
  of used ram.

  To try this:
  1- open gedit
  2- open top
  3- notice the ram use: 19393 weltall   20   0 38980  19m  10m S0  0.7   
0:00.79 gedit   
  4- get a big file to open (mysql dumps are the best to try. I've tried with a 
~50 mb dump)
  5- you will notice an higher ram use, for sure > 300mb to open a 50mb file is 
a bit excessive but this is still an optimization issue which goes beyond this 
bug report: 19393 weltall   20   0  342m 305m  12m S2 10.1   3:02.14 gedit 
  6- close the tab which had the file
  7- check again top no changes in ram use: 19393 weltall   20   0  342m 305m  
12m S0 10.1   3:02.85 gedit
  this is definitely a memory leak or a bad ram retaining for future use 
implementation
  8- try to reopen the file, gedit will take the same time to parse the file, 
but the increase of ram use is more little: 19393 weltall   20   0  381m 345m  
12m S0 11.4   6:01.23 gedit
  9- close the file again the ram use doesn't change again

  other gnome applications have similar leak issues like nautilus which
  after some days takes more than 300mb like nothing and closing windows
  doesn't release ram so maybe the problem might reside in underlying
  libraries.

  It seems applications like geany actually releases correctly the ram
  but i didn't investigate if they use similar libraries

  i'm using ubuntu intrepid with all the updates from normal repositories 
(altough this bug has been present since various releases)
  Description:  Ubuntu 8.10
  Release:  8.10

  gedit:
Installed: 2.24.2-0ubuntu1
Candidate: 2.24.2-0ubuntu1
Version table:
   *** 2.24.2-0ubuntu1 0
  500 http://it.archive.ubuntu.com intrepid-updates/main Packages
  100 /var/lib/dpkg/status
   2.24.0-0ubuntu1 0
  500 http://it.archive.ubuntu.com intrepid/main Packages

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

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

[Desktop-packages] [Bug 1051442] Re: Rhythmbox doesn't subscribe when called with iptc url

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

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

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

Title:
  Rhythmbox doesn't subscribe when called with iptc url

Status in “rhythmbox” package in Ubuntu:
  Confirmed

Bug description:
  Rhythmbox no longer subscribes to a url when called with an
  itpc://urlofpodcast link.

  I selected subscribe from tunesviewer, it searched for itpc://url as
  the name of the podcast, instead of subscribing to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: rhythmbox 2.97-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sat Sep 15 16:23:11 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago)

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

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

[Desktop-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2014-09-07 Thread dimgl

Anyone have any luck with this? This is driving me crazy and I don't
want to have a brick on my computer. I have the Sound Blaster Z and I'm
running Ubuntu 14.04.

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in The Linux Kernel:
  Confirmed
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Desktop-packages] [Bug 505278] Re: ssh-add -D deleting all identities does not work. Also, why are all identities auto-added?

2014-09-07 Thread Nathan Neulinger

For those that are winding up at this bug report from searches looking
to resolve the problem - regardless of platform, here's a quick "fix":

  * Move the keys out of ~/.ssh
  * gnome-keyring-daemon -r -d

It's certainly not an actual fix, but will at least resolve the
immediate annoyance.

More info here:

https://wiki.archlinux.org/index.php/GNOME_Keyring

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

Title:
  ssh-add -D deleting all identities does not work. Also, why are all
  identities auto-added?

Status in GNOME keyring services:
  New
Status in Portable OpenSSH:
  Fix Released
Status in “gnome-keyring” package in Ubuntu:
  Confirmed
Status in “openssh” package in Ubuntu:
  Invalid

Bug description:
  ssh-add -D seems to NOT remove my identities, even though it says it
  did.

  Also, why are all possible identities auto-added right away (on
  start?)

  
  rafal@lcwood(22:11:48)~$ ssh-add -l
  8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-rafal@lcwood (RSA)
  8192 d8:f9:52:6d:d7:44:e2:fe:7d:72:78:f4:09:f7:4a:82 
lcac_rafal_2_geovoucher_vm-rafal@aclc (RSA)
  8192 1c:de:80:66:b2:c0:59:ff:03:61:58:43:ea:f5:b0:58 rafalsvn-rafal@lcwood 
(RSA)
  8192 1b:7b:5b:a5:bf:40:7c:50:48:6f:5a:9b:f5:b3:43:1b rafaladmin-rafal@lcwood 
(RSA)

  
  rafal@lcwood(22:11:50)~$ ssh-add -D
  All identities removed.

  
  rafal@lcwood(22:11:51)~$ ssh-add -l
  8192 d1:50:43:64:52:7d:a0:61:ad:e2:bb:17:35:0d:7f:7d rafal1-rafal@lcwood (RSA)
  8192 d8:f9:52:6d:d7:44:e2:fe:7d:72:78:f4:09:f7:4a:82 
lcac_rafal_2_geovoucher_vm-rafal@aclc (RSA)
  8192 1c:de:80:66:b2:c0:59:ff:03:61:58:43:ea:f5:b0:58 rafalsvn-rafal@lcwood 
(RSA)
  8192 1b:7b:5b:a5:bf:40:7c:50:48:6f:5a:9b:f5:b3:43:1b rafaladmin-rafal@lcwood 
(RSA)
  rafal@lcwood(22:11:53)~$ apport-bug ssh-ad

  ProblemType: Bug
  Architecture: amd64
  Date: Sat Jan  9 22:12:25 2010
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: ssh (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: openssh
  Uname: Linux 2.6.31-16-generic x86_64

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

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

[Desktop-packages] [Bug 1355141] Re: ibus-anthy does not work on Utopic

** Changed in: ibus-anthy (Debian)
   Status: New => Fix Released

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

Title:
  ibus-anthy does not work on Utopic

Status in IBus Japanese Anthy engine:
  Unknown
Status in “ibus-anthy” package in Ubuntu:
  Triaged
Status in “ibus-anthy” package in Debian:
  Fix Released

Bug description:
  ibus-anthy 1.5.5 does not work due to python compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus-anthy/+bug/1355141/+subscriptions

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

I have also tried it in utopic and I have the same issue

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

If you mean 1:0.2.91.7, yes, and the issue was still present.

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

Does the driver in trusty-proposed work for you (as per LP: #1310489) ?

-- 
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 1274726] Re: Rhythmbox "Control" menu states that Control-Space controls play/pause, but actually Control-P is the shortcut

2014-09-07 Thread Neptilo

Nope. Still not fixed in version 3.0.2.

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

Title:
  Rhythmbox "Control" menu states that Control-Space controls
  play/pause, but actually Control-P is the shortcut

Status in The Rhythmbox Music Management Application:
  Invalid
Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  The keyboard shortcut for play/pause is documented in the help system
  of rhythmbox 2.99.1 as being CTRL+Spacebar (which is what I'm used
  to), but it doesn't work. Playing a song, then hitting CTRL+Space does
  not pause it, it just seems to toggle the highlighting of the current
  track down in the tracks pane. Can we please restore the behavior of
  CTRL+Spacebar?

  In Rhythmbox 3.0.2 the shorcut Control-P is what is being used for
  this functionality, but Control-space is still being mentioned in the
  "Control" menu.

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

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

[Desktop-packages] [Bug 1366612] [NEW] PCI/internal sound card not detected

2014-09-07 Thread Robbie Srivastava

Public bug reported:

I have no sound in my laptop since I had installed Ubuntu 14.04 LTS.

Recently, while going through the ubuntu forum to seek solution for it I
used the command:

aplay -l

output was:

aplay: device_list:268: no soundcards found...

Pls help...

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.3
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Mon Sep  8 01:40:59 2014
InstallationDate: Installed on 2014-06-28 (70 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not 
responding.
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2008
dmi.bios.vendor: Acer
dmi.bios.version: v1.3627
dmi.board.name: Mono
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrv1.3627:bd02/04/2008:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 4520
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

** 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/1366612

Title:
  PCI/internal sound card not detected

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

Bug description:
  I have no sound in my laptop since I had installed Ubuntu 14.04 LTS.

  Recently, while going through the ubuntu forum to seek solution for it
  I used the command:

  aplay -l

  output was:

  aplay: device_list:268: no soundcards found...

  Pls help...

  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.3
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Sep  8 01:40:59 2014
  InstallationDate: Installed on 2014-06-28 (70 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3627
  dmi.board.name: Mono
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3627:bd02/04/2008:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 4520
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Desktop-packages] [Bug 1310988] Re: Visual garbage in gutter between screens (multiple monitors)

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

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

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

Title:
  Visual garbage in gutter between screens (multiple monitors)

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I see visible garbage in gutter area between screens (using multiple
  monitors of different height).

  It is not visible on screenshot (Screenshot from 2014-04-22
  12:45:02.png), but actually visible on screen of second monitor
  (Screenshot from 2014-04-22 12:45:02.png).

  There is gutter area between screens, I don't know if it's feature or
  bug, but second monitor shows part of first monitor's image. Width of
  gutter is a few pixels. In upper area of gutter, where there's no
  corresponding parts of first screen's image, there is visible garbage.

  (illustration: garbage.png)

  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
  .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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  CurrentDmesg:
   [   37.916943] init: plymouth-upstart-bridge main process (1406) terminated 
with status 1
   [   37.916958] init: plymouth-upstart-bridge main process ended, respawning
   [  138.769241] systemd-hostnamed[2509]: Warning: nss-myhostname is not 
installed. Changing the local hostname might make it unresolveable. Please 
install nss-myhostname!
   [  254.578106] usb 2-1.2: USB disconnect, device number 3
  Date: Tue Apr 22 12:47:52 2014
  DistUpgraded: 2014-04-18 14:17:57,332 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 
4530/4570/545v] [1002:9553] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21bb]
  InstallationDate: Installed on 2013-10-23 (181 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1424): WARNING **: Failed to load user background: 
Failed to open file '/usr/share/xfce4/backdrops/xubuntu-wallpaper.png': No such 
file or directory
   
   ** (lightdm-gtk-greeter:1424): WARNING **: Failed to load user image: Failed 
to open file '/home/kolen/.face': No such file or directory
  MachineType: LENOVO 4403RP2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1caa7d75-3528-4d6a-a5b2-696009d4b990 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (3 days ago)
  dmi.bios.date: 12/08/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 81ET60WW (1.36 )
  dmi.board.name: 4403RP2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr81ET60WW(1.36):bd12/08/2011:svnLENOVO:pn4403RP2:pvrThinkPadL412:rvnLENOVO:rn4403RP2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4403RP2
  dmi.product.version: ThinkPad L412
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  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 Apr 22 12:43:15 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1286878] Re: Doesn't scale well on a hidpi display

2014-09-07 Thread Owais Lone

I was wrong. It has nothing to do with suspend-resume. Lightdm scales
properly right after I login to Unity. Logging into the unity session
and locing the screen shows properly scaled lightdm.

Is there a way to set the DPI for lightdm somewhere so it scales on
first boot as well?

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

Title:
  Doesn't scale well on a hidpi display

Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  unity-greeter does not scale on hidpi diplays like the rest of unity
  does in trusty.

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

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

[Desktop-packages] [Bug 1366603] [NEW] Sync pango1.0 1.36.7-1 (main) from Debian unstable (main)

2014-09-07 Thread Rico Tzschichholz

Public bug reported:

Please sync pango1.0 1.36.7-1 (main) from Debian unstable (main)

Changelog entries since current utopic version 1.36.6-1:

pango1.0 (1.36.7-1) unstable; urgency=medium

  * New upstream release.
  * Add build-dependency on fonts-cantarell to avoid test failure.
- We rely on gnome-core pulling this in for us in normal operations.
  * Run wrap-and-sort

 -- Andreas Henriksson   Sat, 06 Sep 2014 09:57:33
-0700

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Sync pango1.0 1.36.7-1 (main) from Debian unstable (main)

Status in “pango1.0” package in Ubuntu:
  New

Bug description:
  Please sync pango1.0 1.36.7-1 (main) from Debian unstable (main)

  Changelog entries since current utopic version 1.36.6-1:

  pango1.0 (1.36.7-1) unstable; urgency=medium

* New upstream release.
* Add build-dependency on fonts-cantarell to avoid test failure.
  - We rely on gnome-core pulling this in for us in normal operations.
* Run wrap-and-sort

   -- Andreas Henriksson   Sat, 06 Sep 2014 09:57:33
  -0700

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

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

[Desktop-packages] [Bug 1286878] Re: Doesn't scale well on a hidpi display

2014-09-07 Thread Owais Lone

LightDM scales perfectly on my MBPro after I resume from suspend.
However, it does not scale at all on first boot. If I close the lib of
the laptop once and open it, Unity greeter waits for me in full HiDPI
glory.

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

Title:
  Doesn't scale well on a hidpi display

Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  unity-greeter does not scale on hidpi diplays like the rest of unity
  does in trusty.

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

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

[Desktop-packages] [Bug 1286878] Re: Doesn't scale well on a hidpi display

2014-09-07 Thread Owais Lone

BTW I'm running 14.10 with all packages upgraded

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

Title:
  Doesn't scale well on a hidpi display

Status in “unity-greeter” package in Ubuntu:
  Triaged

Bug description:
  unity-greeter does not scale on hidpi diplays like the rest of unity
  does in trusty.

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

Hi Alberto. So as of now, there is no workaround apart from using the
default driver or reverting to 12.04?  Also, is this where I should
report this bug: https://bugs.launchpad.net/fglrx  ?

Is there any other information that I should specify when filing the bug
or just give them the basics of the problem and take it from there?

Thanks again for spending so much time on this. 
Abhijit

-- 
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 Committed

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.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh in

[Desktop-packages] [Bug 270185] Re: sane-find-scanner sees scanner, scanimage -L does not

2014-09-07 Thread Gilles Schintgen

Sorry, I've finally found the issue on my system: /etc/sane.d/snapscan.conf had 
the wrong permissions. (But that's my fault, not Ubuntu's!)
Running "SANE_DEBUG_SNAPSCAN=128 scanimage -L" put me on the right track. 
("configuration file not found")

Please ignore my previous comment.

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

Title:
  sane-find-scanner sees scanner, scanimage -L does not

Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  sane-find-scanner returns "found USB scanner (vendor=0x04b8, product=0x0130) 
at libusb:001:004
  .

  scanimage -L returns "No scanners were identified"

  this occurs in Ubuntu 8.04, with all patches.
  xsane 0.995-1ubuntu1 is installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/270185/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

@Abhijit: as I suspected, your problem is not being caused by the gpu-
manager but it's probably a bug in the fglrx driver. You might want to
file a separate bug report against the fglrx package.

-- 
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 Committed

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.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.

[Desktop-packages] [Bug 270185] Re: sane-find-scanner sees scanner, scanimage -L does not

2014-09-07 Thread Gilles Schintgen

I'm also affected by this bug:
Epson Perfection 3490 Photo

as regular user (member of "scanner" group):
$ sane-find-scanner
[...]
could not open USB device 0x1d6b/0x0002 at 010:001: Access denied (insufficient 
permissions)
found USB scanner (vendor=0x04b8 [EPSON], product=0x0122 [EPSON Scanner]) at 
libusb:001:002
could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient 
permissions)
[...]
$ scanimage -L

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

$ls -l /dev/bus/usb/001/002
crw-rw-r--+ 1 root root 189, 1 Sep  7 21:15 /dev/bus/usb/001/002
Does this device correspond to my scanner?. Shouldn't it be owned by the 
scanner group? (But changing group ownership to scanner doesn't fix the 
scanimage -L issue.)

Before the update to 14.04, scanning worked just fine. It's a
regression.

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

Title:
  sane-find-scanner sees scanner, scanimage -L does not

Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  sane-find-scanner returns "found USB scanner (vendor=0x04b8, product=0x0130) 
at libusb:001:004
  .

  scanimage -L returns "No scanners were identified"

  this occurs in Ubuntu 8.04, with all patches.
  xsane 0.995-1ubuntu1 is installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/270185/+subscriptions

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

[Desktop-packages] [Bug 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work

2014-09-07 Thread Nicolás

What can I do? Kailang Yang doesn't answer. I've sent 2 mails but he
never answers.

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

Title:
  [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work

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

Bug description:
  I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 
4-pin jack (for mic and headset). When i plug a 4-pin headset only output is 
detected while input remains the same (it still using the integrated computer 
mic).
  Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous 
versions.
  EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas3548 F pulseaudio
   /dev/snd/pcmC0D0p:   nicolas3548 F...m pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-07-16 (17 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/21/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.18
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571G
  dmi.board.vendor: Acer
  dmi.board.version: V2.18
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.18
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18:
  dmi.product.name: Aspire V5-571G
  dmi.product.version: V2.18
  dmi.sys.vendor: Acer

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

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

[Desktop-packages] [Bug 1366593] Re: [HDA-Intel - HDA Intel, playback] Playback problem

2014-09-07 Thread xray

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => xray (xray-pro)

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

Title:
  [HDA-Intel - HDA Intel, playback] Playback problem

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

Bug description:
  firefox no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julebenutzer   1957 F pulseaudio
   /dev/snd/pcmC0D1p:   julebenutzer   1957 F...m pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Sep  7 20:54:05 2014
  InstallationDate: Installed on 2014-09-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Internes Audio - HDA Intel
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 18CN37WW(V2.10)
  dmi.board.name: NITU1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr18CN37WW(V2.10):bd09/18/2009:svnLENOVO:pn2958:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 2958
  dmi.product.version: Lenovo G550
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1366593] [NEW] [HDA-Intel - HDA Intel, playback] Playback problem

2014-09-07 Thread xray

Public bug reported:

firefox no sound

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  julebenutzer   1957 F pulseaudio
 /dev/snd/pcmC0D1p:   julebenutzer   1957 F...m pulseaudio
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Sun Sep  7 20:54:05 2014
InstallationDate: Installed on 2014-09-02 (5 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Internes Audio - HDA Intel
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HDA Intel, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 18CN37WW(V2.10)
dmi.board.name: NITU1
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnLENOVO:bvr18CN37WW(V2.10):bd09/18/2009:svnLENOVO:pn2958:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 2958
dmi.product.version: Lenovo G550
dmi.sys.vendor: LENOVO

** 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/1366593

Title:
  [HDA-Intel - HDA Intel, playback] Playback problem

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

Bug description:
  firefox no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julebenutzer   1957 F pulseaudio
   /dev/snd/pcmC0D1p:   julebenutzer   1957 F...m pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Sep  7 20:54:05 2014
  InstallationDate: Installed on 2014-09-02 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Internes Audio - HDA Intel
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Only some of outputs are working
  Title: [HDA-Intel - HDA Intel, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 18CN37WW(V2.10)
  dmi.board.name: NITU1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr18CN37WW(V2.10):bd09/18/2009:svnLENOVO:pn2958:pvrLenovoG550:rvnLENOVO:rnNITU1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: 2958
  dmi.product.version: Lenovo G550
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1275042] Re: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC

2014-09-07 Thread Oibaf

** Bug watch added: freedesktop.org Bugzilla #72877
   https://bugs.freedesktop.org/show_bug.cgi?id=72877

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=72877
   Importance: Unknown
   Status: Unknown

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

Title:
  Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC

Status in Mesa:
  Unknown
Status in “mesa” package in Ubuntu:
  New

Bug description:
  Hi all,

  I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and
  on Lubuntu 14.04. Unfortunately all have issued false colors in games.
  They appear to be ABGR instead of RGBA, thus blue becomes green, red
  becomes alpha etc.

  Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem.

  The transitional solution is to install the old Mesa 8.0.X with "Force
  Version" with the Synaptic package manager on new distributions.

  We had a problem with wrong colors in SuperTuxKart 0.8 last year. The
  Irrlicht guys have released a little hack for Irrlicht on Linux PPC
  (http://irrlicht.sourceforge.net/forum/viewtopic.php?f=7&t=48577).
  They told me that is a driver bug, and that workaround costs
  performance and RAM. Unfortunately this workaround isn't suitable for
  Mesa 9.2 and higher. At this time we have to install Mesa 9.1.X and
  lower on new Linux distributions like Lubuntu 13.10, Lubuntu 14.04,
  Debian Sid etc. It would be nice to solve this issue because we don't
  need the workaround in the future.

  Hardware:

  AmigaOne X1000 (Nemo)
  PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU
  "Xena" 500MHz XMOS XS1-L2 124
  8GB DDR2 SDRAM
  HIS Radeon HD 6870, 1 GB RAM
  OCZ600MXSP 600 Switching power supply
  RTL 8139/8139C/8139C+ network card
  TSSTcorp CDDVDW SH-224BB dvd drive
  ATA ST2000DM001-9YN1 SEAGATE HD
  ATA ESA 3SF1240GB HD

  More information:

  http://en.wikipedia.org/wiki/AmigaOne_X1000
  http://www.supertuxkart-amiga.de/amiga/x1000.html

  Rgds,
  Christian

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

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

Thank you, then we need to investigate which of the modifications caused
the regression.

-- 
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 36812]

2014-09-07 Thread Wettstae

Allowing arbitrary sequences to decide which action to take would
certainly be powerful, but quite some effort, also for specification
(think about multiple matching sequences).

In comment #117 I suggested an extension to the specification that is
restricted to the enhancement request at hand.  But even this change
would need a protocol bump. This is where this proposal is stuck.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in GNOME Control Center:
  Unknown
Status in X.Org X server:
  In Progress
Status in “control-center” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

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

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

[Desktop-packages] [Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

2014-09-07 Thread Cavsfan

I got this again today on Utopic when 3.16.0-14-generic was installed.
Although when I deleted the 3.16.0-12-generic kernel the 
/lib/modules/3.16.0-12-generic/updates/dkms/nvidia_331.ko was deleted so it was 
installed even though it had gotten the error when it was installed.

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

Title:
  nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module
  failed to build, with no obvious error [objdump: '... .tmp_nv.o': No
  such file]

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

Bug description:
  Nvidia kernel module failed to build on kernel 3.13.0-2
  Yesterday when the new kernel was pushed, the dkms process failed.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-2-generic
  Date: Sun Jan 12 01:28:35 2014
  InstallationDate: Installed on 2013-11-03 (69 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageVersion: 331.20-0ubuntu9
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.20-0ubuntu9: nvidia-331-updates kernel module 
failed to build
  UpgradeStatus: Upgraded to trusty on 2013-12-29 (13 days ago)

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

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

[Desktop-packages] [Bug 1366585] [NEW] boot trop petit

2014-09-07 Thread Debrandt

Public bug reported:

Bonjour
impossible de faire les mise a jour place sur la partion insuffisante.
je ne parvient pas à redimmenssionné le partion boot comment 
faire. j'ai essayer avec le disque d'installation sans resultat et aussi 
avec gparted.
merci

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-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: Sun Sep  7 19:47:24 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:34fc]
InstallationDate: Installed on 2014-06-17 (82 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 001 Device 004: ID 125f: A-DATA Technology Co., Ltd. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader
 Bus 002 Device 003: ID 046d:c52e Logitech, Inc. 
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-34-generic 
root=/dev/mapper/ubuntu--vg-root ro vesafb.invalid=1 splash 
plymouth:debug=1=1=1=1 quiet nopat
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/19/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.60
dmi.board.name: N68C-S UCC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.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: Sun Sep  7 18:42:31 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, 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.1-0ubuntu2.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  boot trop petit

Status in “xorg” package in Ubuntu:
  New

Bug description:
  Bonjour
  impossible de faire les mise a jour place sur la partion insuffisante.
  je ne parvient pas à redimmenssionné le partion boot comment 
  faire. j'ai essayer avec le disque d'installation sans resultat et aussi 
  avec gparted.
  merci

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-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: Sun Sep  7 19:47:24 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebug

[Desktop-packages] [Bug 1366583] [NEW] Active windows looses focus after returning from HUD if another "Always on top" window is present

2014-09-07 Thread Rohan Deshmukh

Public bug reported:

Active window looses focus after returning from HUD if "Always on top"
window like VLC is already running. The focus is given to VLC instead of
the window on which HUD was invoke.

How to reproduce?
1. Open vlc and set it always on top
2. Open nautilus, try to rename a file using hud
3. As soon as rename option is pressed on hud, nautilus looses its focus and 
the focus is given to VLC.
4. To rename I have to re-select nautilus

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
Date: Sun Sep  7 23:05:07 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 i915-3.15-3.13, 0.01, 3.13.0-19-generic, x86_64: installed
 i915-3.15-3.13, 0.01, 3.13.0-24-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c652]
InstallationDate: Installed on 2014-04-13 (146 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 0ac8:c349 Z-Star Microelectronics Corp. 
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=4a883016-3392-4731-824d-ac87981ccaef ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P03RAC
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP300E5X-A04IN
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP03RAC:bd05/07/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP300E5X-A04IN:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 300E4C/300E5C/300E7C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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
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.911-0intel1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Sep  7 22:23:30 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5539 
 vendor CMO
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  Active windows looses focus after returning from HUD if another
  "Always on top" window is present

Status in “unity” package in Ubuntu:
  New

Bug description:
  Active window looses focus after returning from HUD if "Always on top"
  window like VLC is already running. The focus is given to VLC instead
  of the window on which HUD was invoke.

  How to reproduce?
  1. Open vlc and set it always on top
  2. Open nautilus, try to rename a file using hud
  3. As soon as rename option is pressed on hud, nautilus looses its focus and 
the focus is given to VLC.
  4. To rename I have to re-select nautilus

  ProblemType: Bug
  DistroRelease: Ub

[Desktop-packages] [Bug 983220] Re: subpixel rendering doesn't respect screen rotation

2014-09-07 Thread Rafael de Pelegrini Soares

I confirm that this still is an issue with ubuntu 14.04.

If I select RGBA for subpixel I get blurry fonts when the screen in
inverted. This is not an issue if I select grayscale for subpixel.

I can run further tests if needed.

All the best.

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

Title:
  subpixel rendering doesn't respect screen rotation

Status in “freetype” package in Ubuntu:
  New
Status in “wayland” package in Ubuntu:
  New

Bug description:
  1) Open gnome-terminal
  2) xrandr --output default --rotate inverted
  2) Open another gnome-terminal

  In both the original and the new terminal, text has red and blue
  "shadows" caused by subpixel rendering that doesn't match up to the
  inverted pixel layout resulting from the screen being flipped 180
  degrees.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libfreetype6 2.4.8-1ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  Date: Mon Apr 16 11:34:06 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: freetype
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 956618]

2014-09-07 Thread J-mccranie

When I blanked out the description of the mailing list, then it would
send to the list again.

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

Title:
  Nickname not over-riding names in email address

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  New

Bug description:
  From what I have read in the support forum the nickname should take
  priority in the search for an email address in the to: field. It does
  not appear to work any more.

  Example:

  One friend's address is Mark. The other is
  James. Both are in my address book with Mark
  entered as the nickname of m...@.com  and James as nickname for
  james.m...@.com.

  If I type james in the To: field I get james.mark as a first entry in
  the list of available addresses.

  If I type mark I get the same address again, when I would prefer the
  first optional address to be m...@.com

  Reason it is needed:
  I am trying to avoid sending emails meant for m...@.com to James.mark 
because I do not notice in time that I have defaulted to the first entry in the 
list of available addresses.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 10.0.2+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20
  Uname: Linux 3.0.0-16-generic-pae i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  BuildID: 20120216123548
  Date: Fri Mar 16 00:31:06 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 956618]

2014-09-07 Thread J-mccranie

Now I can't send to a list!

Has something changed within the last few days?  I have a mailing list
for a weekly club, and each week I send out a notice.  I used to be able
to type the start of the name and it would send the email to the list.
Now it says that it is not a valid email address because it is not of
the form user@host, so it doesn't send it to the list.  I couldn't
figure out any way to send to the list.

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

Title:
  Nickname not over-riding names in email address

Status in Mozilla Thunderbird Mail and News:
  Confirmed
Status in “thunderbird” package in Ubuntu:
  New

Bug description:
  From what I have read in the support forum the nickname should take
  priority in the search for an email address in the to: field. It does
  not appear to work any more.

  Example:

  One friend's address is Mark. The other is
  James. Both are in my address book with Mark
  entered as the nickname of m...@.com  and James as nickname for
  james.m...@.com.

  If I type james in the To: field I get james.mark as a first entry in
  the list of available addresses.

  If I type mark I get the same address again, when I would prefer the
  first optional address to be m...@.com

  Reason it is needed:
  I am trying to avoid sending emails meant for m...@.com to James.mark 
because I do not notice in time that I have defaulted to the first entry in the 
list of available addresses.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 10.0.2+build1-0ubuntu0.11.10.1
  ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20
  Uname: Linux 3.0.0-16-generic-pae i686
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  BuildID: 20120216123548
  Date: Fri Mar 16 00:31:06 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 217300]

2014-09-07 Thread Markhkamp

In response to claims of Chrome's superior password management, I just
lived through a use case where keeping the browser's passwords decoupled
from the system is much easier to work with.

Short version: Changing Linux distros broke Chromium's access to my
saved passwords. Please don't introduce such a fragile dependency in
Firefox. I don't want to be locked in to my current OS just to keep
using the same cross-platform browser.


Long version:

I had been using Chromium on Chakra Linux for a few years. Chakra is a
"half-rolling" distro built around KDE, so it gets the latest KDE stuff
faster than most other distros. Then I lived somewhere with metered
Internet access for a couple months, so I switched to Firefox, using the
lazy tab loading on start-up to reduce bandwidth use.

(off topic: It was really annoying manually importing passwords to
Firefox since it doesn't have the feature. I miss Chrome's process-per-
tab model that keeps the rest of the browser fast when one tab is busy.
At least NoScript mostly keeps tabs from getting too busy in the first
place. Also Firefox's Tree Style Tab add-on makes it much easier to keep
a zillion tabs organized.)

Now that I'm living somewhere with unmetered Internet again, I've
decided it's about time to do some distro-hopping and see how things
have changed. Switching between various distros and desktop
environments/window managers, Firefox has consistently given me access
to my passwords via the master password, even when Firefox's version got
shuffled back and forth.

Eventually, I ended up settling on OpenSUSE 13.1 using KDE, but
apparently with a slightly older and incompatible version of kwallet. I
just opened Chromium for the first time since July. Since all my log-ins
have expired, it wants to access saved passwords. However, despite using
the same browser and desktop environment I had been in July, with both
within a year of the other, Chromium cannot access my saved passwords.
I'm stuck with kwallet giving me an "Error code -4: Unsupported file
format revision" message. So much for Chromium. Maybe it'll work again
on OpenSUSE 13.2 in a couple months?

I guess I'll use Chromium for all the complicated "web 2.0" stuff that
Firefox's single process chokes on. Firefox still seems best for not
randomly losing abilities and for being widely extensible.

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

Title:
  Seahorse integration

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: firefox

  
  The Seahorse SSH integration totally rocks!
  Would it be possible to integrate Firefox with Seahorse to manage web site 
passwords or the Firefox master password?

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

Hi guys

The first method (modifying boot parameters) did not work, so went for
the recovery mode. Copied off the Xorg.o.log and xorg.conf and have have
attached the the two files here.

The xorg.conf attached here is the one generated according to Alberto's
instruction at #52 and subsequently Uwe's at #57.

Thanks
Abhijit 

** Attachment added: "files4.zip"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4197884/+files/files4.zip

-- 
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 Committed

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.h

[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system

Sorry the zip above doesn't have xorg.conf. Here it is.

** Attachment added: "xorg.conf"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4197885/+files/xorg.conf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/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 Committed

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.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Pa

[Desktop-packages] [Bug 1342497] Re: Adding CP400 printer gives "client-error-not-possible" error

2014-09-07 Thread Merle Hall

And I finally worked through the other steps to get an error_log (though
the CUPS interface still says it's "Not found"), which I've attached.

I was working trying to get a print from about 11:00 to 11:19 in the
log.

Thanks!

** Attachment added: "error_log"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1342497/+attachment/4197882/+files/error_log

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

Title:
  Adding CP400 printer gives "client-error-not-possible" error

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 LTS

  cups:
Installed: 1.7.2-0ubuntu1
Candidate: 1.7.2-0ubuntu1
Version table:
   *** 1.7.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  system-config-printer-gnome: /usr/share/system-config-printer/system-
  config-printer.py

  Appears to find the drivers and gets to the New Printer page.  Hitting
  Apply button gives:

  CUPS Server Error: There was an error during the CUPS operation:
  'client-error-not-possible'.

  Once it created a greyed out printer icon with what looked like a
  vertical = sign over it.  Every other time, it simply gives the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jul 15 21:46:50 2014
  Lpstat:
   device for Canon-CP400: ///dev/null
   device for HP_LaserJet_P1006: hp:/usb/HP_LaserJet_P1006?serial=AB0NM85
   device for PDF: cups-pdf:/
  MachineType: System76, Inc. Ratel Performance
  Papersize: letter
  PpdFiles:
   PDF: Generic CUPS-PDF Printer
   HP_LaserJet_P1006: HP LaserJet p1006, hpcups 3.14.3, requires proprietary 
plugin
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=fe71734f-4e7d-490e-b08a-446c29db9788 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to trusty on 2014-07-04 (11 days ago)
  dmi.bios.date: 07/01/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0507
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87I-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: MB-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76. Inc.
  dmi.chassis.version: Desktop
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0507:bd07/01/2013:svnSystem76,Inc.:pnRatelPerformance:pvrratp2:rvnASUSTeKCOMPUTERINC.:rnH87I-PLUS:rvrRevX.0x:cvnSystem76.Inc.:ct3:cvrDesktop:
  dmi.product.name: Ratel Performance
  dmi.product.version: ratp2
  dmi.sys.vendor: System76, Inc.

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

-- 
Mailing list: https://launchpad.net/~desktop-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-07 Thread Ingo Bürk

@Fabio I can confirm that

sudo dpkg -i ubuntu-drivers-common_0.2.91.5_amd64.deb nvidia-
common_0.2.91.5_amd64.deb

still seems to work (nvidia driver is successfully loaded). I tried 
ubuntu-drivers-common_0.2.91.5 before and it didn't work, so I guess it's 
because I also downgraded nvidia-common_0.2.91.5 this time.
I agree, the problem seems to be in the diff 
ubuntu-drivers-common_0.2.91.5..ubuntu-drivers-common_0.2.91.6

-- 
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 1355141] Re: ibus-anthy does not work on Utopic

** Branch linked: lp:debian/ibus-anthy

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

Title:
  ibus-anthy does not work on Utopic

Status in IBus Japanese Anthy engine:
  Unknown
Status in “ibus-anthy” package in Ubuntu:
  Triaged
Status in “ibus-anthy” package in Debian:
  New

Bug description:
  ibus-anthy 1.5.5 does not work due to python compatibility.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus-anthy/+bug/1355141/+subscriptions

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

[Desktop-packages] [Bug 1212601] Re: nautilus crashed with SIGSEGV in discovered_cb()

** Tags added: utopic

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

Title:
  nautilus crashed with SIGSEGV in discovered_cb()

Status in “totem” package in Ubuntu:
  Confirmed

Bug description:
  On startup

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: totem 3.8.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4
  Uname: Linux 3.11.0-1-generic x86_64
  ApportVersion: 2.12-0ubuntu3
  Architecture: amd64
  Date: Tue Aug 13 22:45:30 2013
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1371828403
  InstallationDate: Installed on 2013-07-20 (24 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: nautilus -n
  ProcCwd: /home/mathieu
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f11e95729fa:mov(%rcx),%rdi
   PC (0x7f11e95729fa) ok
   source "(%rcx)" (0x) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to saucy on 2013-07-20 (24 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1366565] Re: nautilus crashed with SIGSEGV in ffi_call_unix64()

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

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 #1212601, 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/1366565/+attachment/4197874/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1212601
   nautilus crashed with SIGSEGV in discovered_cb()

** 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 totem in Ubuntu.
https://bugs.launchpad.net/bugs/1366565

Title:
  nautilus crashed with SIGSEGV in ffi_call_unix64()

Status in “totem” package in Ubuntu:
  New

Bug description:
  during extended browsing of a smb share with > 10,000 entries in the
  root directory

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: totem 3.10.1-1ubuntu6
  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
  CurrentDesktop: Unity
  Date: Sun Sep  7 17:54:05 2014
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2014-02-22 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140222)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8820089b9a:mov(%rcx),%rdi
   PC (0x7f8820089b9a) ok
   source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1364173]

2014-09-07 Thread Vdragon

I found out that kdm runs /etc/kde4/kdm/Xsession using user's default shell.
http://i.imgur.com/xyiJ1b8.jpg

It is not sane as in Xsession(5) manpage notes:
/etc/X11/Xsession  is  a Bourne shell (sh(1)) script which is run when an X 
Window System session is begun by startx(1) or a display manager such as  
xdm(1).

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

Title:
  Xsession sourced scripts shouldn't be run using user's default shell

Status in KDE Base Workspace:
  New
Status in “kde-workspace” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  Recently I encountered a problem that my input method malfunctions
  because the environmental variables are wrongly set(which is, fully
  configured using im-config), after hours of debugging I found that
  it's Z-shell(my current default shell)'s bug that prematurely quits
  before the Xsession.d im-config input method configure script
  completes.

  The problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) 
**shouldn't** be run in Z-shell.  Patching /etc/kde4/kdm/Xsession # invoke 
global X session script. code from
  . /etc/X11/Xsession
  to
  /etc/X11/Xsession

  workarounded the issue (however I have no idea why).  Switching to
  other display managers instead of KDM worked also)

  Reproducible: Always

  Steps to Reproduce:
  Currently there's no simple reproduce method as another software(zsh)'s bug 
involved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1364173/+subscriptions

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

[Desktop-packages] [Bug 36812]

2014-09-07 Thread Adam Purkrt

xkb should be extended to be able to recognize a sequence of key presses
and key releases and fire action upon it. Again, this would be an
extension, not a violation of current standard.

Currently, the group switching is defined in
/usr/share/X11/xkb/symbols/group with parts like

partial modifier_keys
xkb_symbols "lalt_lshift_toggle" {
virtual_modifiers Alt;
key  {
symbols[Group1] = [ NoSymbol, ISO_Next_Group ],
virtualMods= Alt
};
key  {
type[Group1]="PC_ALT_LEVEL2",
symbols[Group1] = [ Shift_L, ISO_Next_Group ]
};
};

The following is what this part of the file would look like after
appropiate changes in xkb code:

xkb_sequences "lalt_lshift_toggle" {
sequence { keydown , keydown , keyup  } = ISO_Next_Group;
sequence { keydown , keydown , keyup  } = ISO_Next_Group;
}


For this to work
1) http://www.x.org/docs/XKB/XKBproto.pdf need to be extended with a small 
chapter
2) http://cgit.freedesktop.org/xorg/xserver/tree/xkb - code the run time check 
for sequences; changes to xkm format required
3) http://cgit.freedesktop.org/xorg/app/xkbcomp/tree/ - code the parsing of 
"xkb_sequences", "keydown", and "keyup" keywords


At least this is my impression after a day of investigation. I know this seems 
like unnecessarily big change compared to Ilya's patch. But, basically, that is 
what I mean by "clean solution". Unfortunatelly, it is more of a "dream 
solution", since I feel I will hardly be able to code this..

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in GNOME Control Center:
  Unknown
Status in X.Org X server:
  In Progress
Status in “control-center” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

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

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

[Desktop-packages] [Bug 373680] Re: network-manager fails periodically , on backgound networks scan?

2014-09-07 Thread danielo

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => danielo (danielort2012)

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

Title:
  network-manager fails periodically , on backgound networks scan?

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” source package in Lucid:
  Triaged
Status in “network-manager” source package in Maverick:
  Fix Released
Status in “network-manager” package in Fedora:
  Invalid

Bug description:
  Binary package hint: network-manager

  1) The release
  Ubuntu version:Ubuntu 9.04   Jaunty  Release: 9.04   64 BITS 

  2) The version of the package you are using
  Package affected :   network-manager  0.7.1~rc4.1.cf199a964-0ubuntu2

  
  3) What you expected to happen
   Estable connection.
   If I kill NetworkManager and connect manually to the network using iwconfig 
, the problem dissapear.

  4)What happened instead

  Frecuently signal gets interrupted, but not complety disconnected.  
  I guess it is related with the background network scanning but not sure.  I 
can notice while copying files on local network, watchins streaming movies or 
with the ping command.  
  Approximatly each 90-120 seconds ,  a 5-8 seconds lag is generated.

  
   -->  Hardware : 
  Dell Wireless card 1515 
  Atheros  AR928X chipset  

#lspci  | grep Atheros
 06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
Network Adapter (PCI-Express) (rev 01)

  -->  Drivers :   
  Im not sure.   Clean Ubuntu 9.04  installation  detected my card,  but could 
not connect to networks until I installed  
linux-backports-modules-jaunty-generic  .

#$ lsmod | grep ath9k
 ath9k 311092  0 
 lbm_cw_mac80211   259000  1 ath9k
 led_class  13064  1 ath9k
 lbm_cw_cfg8021185048  2 ath9k,lbm_cw_mac80211


  More information:
  ---

  ->>If I kill NetworkManager and connect manually to the network using
  iwconfig , THE PROBLEM DISAPPEAR.

  #ping 192.168.0.1   ( my gateway )
  64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.75 ms
  64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.82 ms
  64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1.46 ms
  64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1.60 ms
  64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=6802 ms  **Here it is the 
problem
  64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=5803 ms
  64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=4803 ms
  64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=3803 ms
  64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=2803 ms
  64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1803 ms
  64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=803 ms
  64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1.72 ms
  64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=1.69 ms
  64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=1.72 ms **  Everything 
keep normal, but afther 90-120 seconds, the 8 seconds lag happens again, and 
always like that. 

  
  #tail -n0 -f /var/log/syslog

  NetworkManager:  [1241785845.002524] periodic_update(): Roamed from 
BSSID 00:80:5A:4B:89:43 (rosquilla) to (none) ((none)) 
  May  8 14:30:46 xps kernel: [ 2896.176696] wlan0: beacon loss from AP 
88015e8cfac0 - sending probe request
  May  8 14:30:51 xps NetworkManager:  [1241785851.001653] 
periodic_update(): Roamed from BSSID (none) ((none)) to 00:80:5A:4B:89:43 
(rosquilla) 
  May  8 14:32:45 xps NetworkManager:  [1241785965.004390] 
periodic_update(): Roamed from BSSID 00:80:5A:4B:89:43 (rosquilla) to (none) 
((none)) 
  May  8 14:32:46 xps kernel: [ 3016.169028] wlan0: beacon loss from AP 
88015e8cfac0 - sending probe request
  May  8 14:32:51 xps NetworkManager:  [1241785971.001949] 
periodic_update(): Roamed from BSSID (none) ((none)) to 00:80:5A:4B:89:43 
(rosquilla) 

  
  * Note :  The delay with the ping command  and the syslog events  happen at 
same time.

  If i can add any adicional info please tell me what commands to writte
  or a link with some help and i will post it.

  
  (Is my first bug report, if im forgetting to add something or not reporting  
properly please tell me )

  Thanks in advanced.

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

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

[Desktop-packages] [Bug 1366560] [NEW] FFe: Please upgrade GIMP to version 2.8.14

2014-09-07 Thread Thomas Hotz

Public bug reported:

This is a bug-fix update that fixes many bugs.

>From the changelog:


Overview of Changes from GIMP 2.8.12 to GIMP 2.8.14
===


General:

 - Fix libtool versioning (forgot to bump gimp_interface_age)


Overview of Changes from GIMP 2.8.10 to GIMP 2.8.12
===


Core:

 - OSX: Fix migration code for old GIMP directories
 - Fix brush sizes when used from plug-ins
 - Windows: Allow to Explorer-open files with UTF-8 characters in the filename
 - Make XCF loading more robust against broken files


GUI:

 - Make sure the widget direction matches the GUI language
 - Remove the option to disable the warning when closing a modified image
 - Fix canvas overlay widgets (like the text options) for tablets
 - Make DND work between images in one dockable


Libgimp:

 - Make gimp_image_get_name() return the string used for the image title


Plug-ins:

 - Make script-fu-server more secure by listening to 127.0.0.1 by
   default and add a warning about changing that IP. This breaks the
   procedure's API, but for security reasons.
 - Bring back proper script-fu translations


General:

 - Massively clean up and fix the OSX build and bundle
 - Add Jenkins tutorial
 - Documentation updates
 - Bug fixes
 - Translation updates

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: gimp 2.8.10-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: Sun Sep  7 17:29:51 2014
InstallationDate: Installed on 2014-08-07 (31 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140806)
ProcEnviron:
 LANGUAGE=de_AT:de
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
SourcePackage: gimp
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug utopic

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

Title:
  FFe: Please upgrade GIMP to version 2.8.14

Status in “gimp” package in Ubuntu:
  New

Bug description:
  This is a bug-fix update that fixes many bugs.

  From the changelog:

  
  Overview of Changes from GIMP 2.8.12 to GIMP 2.8.14
  ===

  
  General:

   - Fix libtool versioning (forgot to bump gimp_interface_age)

  
  Overview of Changes from GIMP 2.8.10 to GIMP 2.8.12
  ===

  
  Core:

   - OSX: Fix migration code for old GIMP directories
   - Fix brush sizes when used from plug-ins
   - Windows: Allow to Explorer-open files with UTF-8 characters in the filename
   - Make XCF loading more robust against broken files

  
  GUI:

   - Make sure the widget direction matches the GUI language
   - Remove the option to disable the warning when closing a modified image
   - Fix canvas overlay widgets (like the text options) for tablets
   - Make DND work between images in one dockable

  
  Libgimp:

   - Make gimp_image_get_name() return the string used for the image
  title

  
  Plug-ins:

   - Make script-fu-server more secure by listening to 127.0.0.1 by
 default and add a warning about changing that IP. This breaks the
 procedure's API, but for security reasons.
   - Bring back proper script-fu translations

  
  General:

   - Massively clean up and fix the OSX build and bundle
   - Add Jenkins tutorial
   - Documentation updates
   - Bug fixes
   - Translation updates

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gimp 2.8.10-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: Sun Sep  7 17:29:51 2014
  InstallationDate: Installed on 2014-08-07 (31 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140806)
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gimp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1366555] Re: nautilus crashed with SIGABRT in g_assertion_message()

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

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 #1191449, 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/1366555/+attachment/4197842/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1366555

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  crash by click on flash-disk property menu

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  7 19:05:15 2014
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2013-06-08 (455 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  ProcCmdline: nautilus -n
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to utopic on 2014-08-24 (13 days ago)
  UserGroups: adm autopilot cdrom debian-tor dip lpadmin plugdev sambashare 
sudo vboxusers wireshark

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

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

[Desktop-packages] [Bug 1366556] [NEW] PPC: libgl1-mesa-dri doesn't provide 3D acceleration

2014-09-07 Thread Christian Zigotzky

Public bug reported:

Hi,

libgl1-mesa-dri doesn't provide 3D acceleration.

Package: libgl1-mesa-dri 10.2.6-1ubuntu3 (Lubuntu 14.10 beta PowerPC)
System specification: http://www.xenosoft.de/pastebin_AmigaOne_X1000
Tested graphics cards: AMD CYPRESS, and AMD BARTS

Preliminary solution: http://forum.hyperion-
entertainment.biz/viewtopic.php?f=35&t=2614

LIBGL_DEBUG=verbose glxinfo

name of display: :0
libGL: screen 0 does not appear to be DRI3 capable
libGL: pci id for fd 4: 1002:6738, driver r600
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r600_dri.so
libGL: driver does not expose __driDriverGetExtensions_r600(): 
/usr/lib/powerpc-linux-gnu/dri/r600_dri.so: undefined symbol: 
__driDriverGetExtensions_r600
libGL: Can't open configuration file /home/christian/.drirc: No such file or 
directory.
libGL: Can't open configuration file /home/christian/.drirc: No such file or 
directory.
libGL error: failed to load driver: r600
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so
libGL: Can't open configuration file /home/christian/.drirc: No such file or 
directory.
libGL error: failed to load driver: swrast
Error: couldn't find RGB GLX visual or fbconfig

dmesg | grep radeon

[0.620345] [drm] radeon kernel modesetting enabled.
[0.789281] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[0.789296] radeon :01:00.0: GTT: 1024M 0x4000 - 
0x7FFF
[0.789440] [drm] radeon: 1024M of VRAM memory ready
[0.789448] [drm] radeon: 1024M of GTT memory ready.
[0.820700] radeon :01:00.0: WB enabled
[0.820712] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x4c00 and cpu addr 0xc00276ab2c00
[0.820728] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x4c0c and cpu addr 0xc00276ab2c0c
[0.834239] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00072118 and cpu addr 0xd800901b2118
[0.834318] radeon :01:00.0: radeon: using MSI.
[0.834362] [drm] radeon: irq initialized.
[1.191354] [drm] radeon: power management initialized
[1.561110] radeon :01:00.0: fb0: radeondrmfb frame buffer device
[1.561516] radeon :01:00.0: registered panic notifier
[1.561844] [drm] Initialized radeon 2.36.0 20080528 for :01:00.0 on 
minor 0

dmesg | grep drm

[0.620278] [drm] Initialized drm 1.1.0 20060810
[0.620345] [drm] radeon kernel modesetting enabled.
[0.620786] [drm] initializing kernel modesetting (BARTS 0x1002:0x6738 
0x1682:0x3107).
[0.620806] [drm] register mmio base: 0xA002
[0.620812] [drm] register mmio size: 131072
[0.789305] [drm] Detected VRAM RAM=1024M, BAR=256M
[0.789312] [drm] RAM width 256bits DDR
[0.789440] [drm] radeon: 1024M of VRAM memory ready
[0.789448] [drm] radeon: 1024M of GTT memory ready.
[0.789472] [drm] Loading BARTS Microcode
[0.789566] [drm] GART: num cpu pages 262144, num gpu pages 262144
[0.820556] [drm] PCIE GART of 1024M enabled (table at 
0x00273000).
[0.834254] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[0.834261] [drm] Driver supports precise vblank timestamp query.
[0.834362] [drm] radeon: irq initialized.
[0.851016] [drm] ring test on 0 succeeded in 3 usecs
[0.851092] [drm] ring test on 3 succeeded in 2 usecs
[1.036506] [drm] ring test on 5 succeeded in 2 usecs
[1.036518] [drm] UVD initialized successfully.
[1.036876] [drm] Enabling audio 0 support
[1.036938] [drm] ib test on ring 0 succeeded in 0 usecs
[1.036995] [drm] ib test on ring 3 succeeded in 0 usecs
[1.187983] [drm] ib test on ring 5 succeeded
[1.190274] [drm] Radeon Display Connectors
[1.190283] [drm] Connector 0:
[1.190289] [drm]   DP-1
[1.190293] [drm]   HPD4
[1.190300] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 
0x643c 0x643c
[1.190307] [drm]   Encoders:
[1.190312] [drm] DFP1: INTERNAL_UNIPHY2
[1.190318] [drm] Connector 1:
[1.190323] [drm]   DP-2
[1.190327] [drm]   HPD5
[1.190333] [drm]   DDC: 0x6440 0x6440 0x6444 0x6444 0x6448 0x6448 
0x644c 0x644c
[1.190341] [drm]   Encoders:
[1.190345] [drm] DFP2: INTERNAL_UNIPHY2
[1.190351] [drm] Connector 2:
[1.190356] [drm]   HDMI-A-1
[1.190360] [drm]   HPD3
[1.190367] [drm]   DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 
0x646c 0x646c
[1.190374] [drm]   Encoders:
[1.190379] [drm] DFP3: INTERNAL_UNIPHY1
[1.190384] [drm] Connector 3:
[1.190389] [drm]   DVI-D-1

[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system

@Abhijit: you can use pastebinit to upload text files from the command
line:

Install pastebinit:
sudo apt-get install pastebinit

Upload the files:
pastebinit /var/log/Xorg.0.log

pastebinit /etc/X11/xorg.conf

Post the links that pastebinit will give you.

-- 
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 Committed

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.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  d

[Desktop-packages] [Bug 1306550] Re: Wrong mouse-coordinates in the window after minimize/maximize of after return from fullscreen

2014-09-07 Thread Vishal

I also experinced this bug in ubuntu 14.04.

I noticed that pointer gets normal when i click the side unity side-bar.

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

Title:
  Wrong mouse-coordinates in the window after minimize/maximize of after
  return from  fullscreen

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  After I minimize/maximize an application the handling of local window-
  coordinate sometimes will be broken.  The actual position of the mouse
  pointer in the window is lower the the position of the cursor on the
  screen (about the window title height or unity panel height). Most of
  time it happens with firefox (after fullscreen flash-video)  but also
  with other apps.

  I have same problem in previous versions of Ubuntu, if the "window
  placement" plugin was disabled. In this case the plugin is active.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-17ubuntu2)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-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
  Date: Fri Apr 11 13:08:34 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-23-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-23-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. P8H77-I Motherboard [1043:84ca]
   NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:3552]
  InstallationDate: Installed on 2014-03-16 (25 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic 
root=UUID=645bd371-661d-491f-b23a-23e25ba4c5a3 ro quiet
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
   Identifier "Default Card 1"
   BusID "PCI:1@0:0:0"
   EndSection
  dmi.bios.date: 09/17/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0709
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B75-V
  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.:bvr0709:bd09/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-V: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.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Apr 11 12:51:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

-- 
Mailing list: https://launchpad.

[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system

2014-09-07 Thread Uwe Cappeller

Hi Abhijit,

don't reinstall Ubuntu!

When your maschine start to boot stop it with ESC to modify the boot option to 
go into the boot menu. 
Enter the first line and push 'e'. This will enable you to  modify the boot 
parameter.
There is a line looking like this:
linux ... ro quiet splash $vt_handoff
'' means that there are some additional commands. 
enter before or after 'quiet splash' 'nomodeset' . It should look like below:
linux ... ro quiet splash nomodeset $vt_handoff
Reboot now

Another method is to go from boot menu into recover mode and recover the
xorg file as described from there.

Even if the x-server doesn't start you should be able to start a
terminal again with Ctrl+Alt+F1. Now you are able to recover the old
xorg.conf by

1. sudo rm xorg.conf
2. mv xorg.conf.backup xorg.conf
3. reboot

Please try and let me know if you managed to do so.

Best Regards,
Uwe

-- 
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 Committed

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-Packar

[Desktop-packages] [Bug 1309054] Re: huawei E355 usb router not working properly in xubuntu 14.04

2014-09-07 Thread Frank

Thread on this topic concerning Ubuntu and Linux Mint:

Huawei E355 USB router wrongly installed as modem
http://forums.linuxmint.com/viewtopic.php?f=53&t=148990

I am also affected by this bug.

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

Title:
  huawei E355 usb router not working properly in xubuntu 14.04

Status in “modemmanager” package in Ubuntu:
  Confirmed
Status in “modemmanager” package in Arch Linux:
  New
Status in “modemmanager” package in Debian:
  New

Bug description:
  huawei E355 is a USB router (1x Ethernet-over-USB, 5 x WLAN) [1].

  with ubuntu 12.04.3 LTS (3.8 series of kernel), it was recognised and
  worked properly by default. a connection was created under the 'wired
  connection' option just by plugging the device into the machine.
  however, since then it never worked properly. in (x)ubuntu 13.10, an
  alternative worked [2,3]; which unfortunately stopped working in
  xubuntu 14.04.

  expected behaviour: one connection under wired connection and one
  under wifi connection should be available. ubuntu 12.04.3 LTS, ubuntu
  13.04 performed in expected manner.

  present behaviour:  only wifi hotspot generated by the router could be
  used. the ethernet over usb function is totally unavailable in
  (x)ubuntu 14.04.

  possible reason: cdc_ncm kernel was changed beyond 3.8 series but the
  changes  was not considered in the modem manager. in [2,3], the
  provided solution was based on deactivating the changes made in the
  cdc_ncm beyond 3.8 kernel series.

  [1] -> http://www.huaweidevice.co.in/Products/MobileBroadband/E355.php
  [2] -> http://forums.linuxmint.com/viewtopic.php?f=53&t=148990
  [3] -> 
http://forum.ubuntuusers.de/topic/huawei-e355-als-kabelnetzwerk-einbinden-wwan0-/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: modemmanager 1.0.0-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 17 19:44:36 2014
  InstallationDate: Installed on 2014-04-16 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

@Uwe: Thanks! You are right, it has now regenerated the xorg.conf.

However, now a different problem. After the reboot, it gave me a black
screen with a mouse pointer (which looked like a cross) and nothing
else. I can't even go to the command line with a Ctrl+Alt+F1 anymore.
All it gives is a dead black screen with nothing on it if I press that
key combo.

Don't know how to extract the xorg.conf and Xorg.0.log files anymore
without reinstalling Ubuntu. Any ideas what's the next thing to be done?

Abhijit

-- 
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 Committed

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-b4

[Desktop-packages] [Bug 1326760] Re: Click Google Chrome's minimize button, Chrome accidental image

2014-09-07 Thread Alexey

this trouble exists on Lubuntu.. how to fix?

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

Title:
  Click Google Chrome's minimize button, Chrome accidental image

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

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  $ lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  $ LANG=C apt-cache policy nvidia-331
  nvidia-331:
Installed: 331.38-0ubuntu7
Candidate: 331.38-0ubuntu7
Version table:
   *** 331.38-0ubuntu7 0
  500 http://ftp.jaist.ac.jp/pub/Linux/ubuntu/ trusty/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  I was Installed Google Chrome (not Chromium) from Google web site.
  Run Google Chrome.
  Click minimize button, Chrome is minimize.

  4) What happened instead
  Click minimize button Chrome is minimize BUT Chrome accidental image still 
existing.

  
  Is this Graphics Driver's bug ?
  Another machine have not Nvidia Graphics doesn't reproduce this issue.

  $ lspci -v | grep -i nvidia
  01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 0915
Kernel driver in use: nvidia
  01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
Subsystem: NVIDIA Corporation Device 0915

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  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: default
  Date: Thu Jun  5 20:24:32 2014
  InstallationDate: Installed on 2014-06-03 (1 days ago)
  InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
  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/1326760/+subscriptions

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

[Desktop-packages] [Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language

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

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

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

Title:
  Lock screen uses last active window's language instead of default
  keyboard language

Status in Unity:
  New
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Lock screen (gnome-screensaver) uses last active window's language
  (keyboard layout) instead of default keyboard language.

  Steps to reproduce this bug:
  1. In the system Text Entry settings:
1a. add two or more languages to the input sources list, e.g. English (as 
first and default) and Russian (as second);
1b. Set hotkeys to switch sources (e.g. Ctrl+Shift or CapsLock).
1c. Select "Allow different sources for each window" radio button.
1d. Select "New windows use the default source" radio button.
  2. Run any application (e.g. gedit) and switch keyboard to second input 
language (Russian).
  3. Lock the screen (Ctrl+Alt+L) or just wait idle time.
  4. See what language set by default for password input in the lock screen.

  Expected: lock screen uses first input language (English) by default.
  What happened instead: lock screen uses last active window's language 
(Russian).

  Ubuntu versions affected: Ubuntu 13.10, Ubuntu 14.04 (daily builds)
  gnome-screensaver versions: 3.6.1-0ubuntu7, 3.6.1-0ubuntu9

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

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

[Desktop-packages] [Bug 1354067] Re: Auto-Login service for GMail accounts gives "Applications can no longer access online account" error

2014-09-07 Thread Coeur Noir

I don't use Evolution on my PC's but thunderbird (with add-ons to sync
lighting with google agendas and contacts)

And my thunderbird's still run ok despite of the bug.

I can confirm the bug is still there even after fresh install of ubuntu
14.04.

Even if Calendar + Contacts services are disabled.

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

Title:
  Auto-Login service for GMail accounts gives "Applications can no
  longer access online account" error

Status in “account-plugins” package in Ubuntu:
  Confirmed
Status in “friends” package in Ubuntu:
  Invalid

Bug description:
  The auto-login service for GMail accounts gives "Applications can no
  longer access online accounts" error everytime it attempts to connect.
  It also cannot sustain connections for other online services
  (facebook, yahoo, etc.) and requires me to grant access to the
  services again and again. I can confirm my passwords are correct.

  Also, granting access to yahoo mail and facebook works flawlessly, but
  the GMail 'Grant Access' interface is buggy, and just doesn't work.
  On entering password and clicking 'Done' it brings back the same
  screen, as though nothing happened. Over and over again. If you click
  cancel a few times, it brings you back to the screen with the list of
  online accounts, while it attempts to connect to the services, in
  vain. Also, overall the friends service is buggy. It doesn't show me
  notifications from facebook, nor has it synced events from my google
  calenders. I cannot tell you when this problem started exactly,
  neither can i guess what might have caused the problem. If you need
  some log files, please tell me, i'll upload them asap. I don't have
  accounts in many of the services listed there, so i might not be able
  to help you with other services. I really hope there's a solution to
  this, because its always lovely to see a well polished desktop
  environment :)

  I use Ubuntu 14.04 LTS (Trusty Tahr)

  Version of 'friends' package installed:
  0.2.0+14.04.20140217.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Aug  7 20:47:49 2014
  InstallationDate: Installed on 2014-04-20 (108 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: friends
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

I don't use Evolution on my PC's but thunderbird (with add-ons to sync
lighting with google agendas and contacts)

And my thunderbird's still run ok despite of the bug.

I can confirm the bug is still there even after fresh install of ubuntu
14.04.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to account-plugins 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:
  Confirmed
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

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 463078] Re: Dia export to Cairo PNG causes mangled text fonts

2014-09-07 Thread Christopher M. Penalver

Rorschach, then you are experiencing a different problem then the one scoped to 
this report. Please file a new report via a terminal and please feel free to 
subscribe me to it:
ubuntu-bug dia

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

Title:
  Dia export to Cairo PNG causes mangled text fonts

Status in “dia” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: dia

  Description:Ubuntu 9.10
  Release:9.10

  dia 0.97-2
  dia-common 0.97-2
  dia-libs 0.97-2
  libcairo2 1.8.8-2ubuntu1
  libfreetype6 2.3.9-5
  libpango1.0-0 1.26.0-1
  libpango1.0-common 1.26.0-1

  
  Method to demonstrate: load the file "text.dia" then export to PNG using 
Cairo and export to PNG using Pixbuf -- the character layout has a strange gap 
in the Cairo output. Note that output PNG files are also attached to this bug 
report, and this problem happens with various other more complex dia outputs as 
well as this simple example.

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

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

[Desktop-packages] [Bug 984801] Re: Thunderbird 11 has stupidly high idle CPU usage

2014-09-07 Thread Carlos Paiva

I had the same problem, and I overlooked the most simple case - look at
the Activity Manager (Tools->Activity Manager) and find out that
Thunderbird was synching my complete imap email account with the local
machine!

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

Title:
  Thunderbird 11 has stupidly high idle CPU usage

Status in “thunderbird” package in Ubuntu:
  Invalid

Bug description:
  Running Ubuntu 10.04 LTS 32-bit and today I got the upgrade from
  Thunderbird 3.6.X to 11.0.1 and noticed it is using a stupid amount of
  CPU time when apparently idle. On my quad-core AMD machine it is
  taking typically 30-50% CPU when doing nothing, and this is much the
  same when minimised, as shown by 'top'

  top - 12:50:00 up  1:59,  4 users,  load average: 1.27, 0.99, 1.03
  Tasks: 230 total,   3 running, 226 sleeping,   0 stopped,   1 zombie
  Cpu(s): 12.2%us,  1.4%sy,  0.0%ni, 82.5%id,  3.9%wa,  0.1%hi,  0.0%si,  0.0%st
  Mem:   2706608k total,  2621568k used,85040k free,   148192k buffers
  Swap:0k total,0k used,0k free,  1612160k cached

PID USER  PR  NI  VIRT  RES  SHR S %CPU %MEMTIME+  COMMAND  

   
  20049 paul  20   0  478m 157m  33m R   46  6.0   0:57.14 thunderbird-bin  

   
  19759 paul  20   0  270m 195m  18m S4  7.4   1:07.00 opera

   
   3918 paul  20   0  165m  24m  12m S1  0.9   1:25.70 chromium-browse  

   
  19215 paul  20   0  2652 1340  984 S1  0.0   0:21.85 htop 

   
   1317 root  20   0  152m  98m  13m S1  3.7   8:20.29 Xorg 

   
   4422 paul  20   0 49096  13m 9.8m S0  0.5   1:22.72 gnome-terminal   

   
  20165 paul  20   0  2544 1272  912 R0  0.0   0:00.06 top  

   
  1 root  20   0  2808 1664 1168 S0  0.1   0:00.56 init 

   
  2 root  20   0 000 S0  0.0   0:00.00 kthreadd 

   
  3 root  RT   0 000 S0  0.0   0:00.11 migration/0  

  This is APPALLING for anyone on a laptop where power consumption (and
  hence battery life) is directly related to CPU use!

  What is Thunderbird doing with all of the CPU cycles?

  I tried running it in safe mode, and have already disabled any plugins
  but to no improvement. I also tried running it via strace and it spews
  out a lot of system calls even when idle, most oddly are blocks like
  this:

  clock_gettime(CLOCK_MONOTONIC, {6787, 22357603}) = 0
  clock_gettime(CLOCK_MONOTONIC, {6787, 22435200}) = 0
  gettimeofday({1334749406, 311330}, NULL) = 0
  gettimeofday({1334749406, 311537}, NULL) = 0
  gettimeofday({1334749406, 311670}, NULL) = 0
  futex(0xb75eb5c8, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xb75eb5c4, {FUTEX_OP_SET, 0, 
FUTEX_OP_CMP_GT, 1}) = 1
  open("/home/paul/.thunderbird/3c38dt95.default/session.json", 
O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0664) = 56
  write(56, "{\"rev\":0,\"windows\":[{\"type\":\"3pa"..., 396) = 396
  close(56)   = 0
  gettimeofday({1334749406, 314673}, NULL) = 0
  clock_gettime(CLOCK_MONOTONIC, {6787, 26165961}) = 0
  clock_gettime(CLOCK_MONOTONIC, {6787, 26256350}) = 0
  clock_gettime(CLOCK_MONOTONIC, {6787, 26329526}) = 0
  gettimeofday({1334749406, 315949}, NULL) = 0
  gettimeofday({1334749406, 316354}, NULL) = 0
  gettimeofday({1334749406, 316908}, NULL) = 0
  gettimeofday({1334749406, 317088}, NULL) = 0

  Notice it is calling gettimeofday() every 100us or so! Looks like
  someone should be using usleep() or similar time-wasting methods when
  nothing is happening :(

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

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

[Desktop-packages] [Bug 1365902] Re: fglrx (not installed): fglrx kernel module failed to build

2014-09-07 Thread Daniel Letzeisen

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

You cannot install the AMD legacy Catalyst/fglrx on Ubuntu 14.04/Trusty.
AMD has not updated its legacy driver for modern versions of the kernel
or Xserver, and Canonical cannot fix it since it is closed source.

Your best option is the open-source radeon driver, which is installed
and used by default.

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Won't Fix

** This bug has been marked a duplicate of bug 1058040
   fglrx-installer not working with AMD Radeon/Mobility Radeon HD 2000-4000 
cards in Quantal+

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

Title:
  fglrx (not installed): fglrx kernel module failed to build

Status in “fglrx-installer” package in Ubuntu:
  Won't Fix

Bug description:
  Trying to install the fglrx_8.970-0ubuntu1_i386.deb generated by amd-
  driver-installer-catalyst-13.1-legacy-linux-x86.x86_64.run

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:8.970-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSBuildLog:
   DKMS make.log for fglrx-8.970 for kernel 3.13.0-35-generic (i686)
   vendredi 5 septembre 2014, 10:32:38 (UTC+0200)
   AMD kernel module generator version 2.1
   kernel includes at /lib/modules/3.13.0-35-generic/build/include not found or 
incomplete
   file: /lib/modules/3.13.0-35-generic/build/include/linux/version.h
  DKMSKernelVersion: 3.13.0-35-generic
  Date: Fri Sep  5 10:32:42 2014
  DistUpgraded: 2014-08-12 02:59:00,201 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 8.970: added
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650] 
[1002:9498] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:026e]
  InstallationDate: Installed on 2011-06-30 (1162 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: System manufacturer System Product Name
  PackageVersion: (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=89e3746f-a36f-489f-bd1f-39fe0af73581 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  Title: fglrx (not installed): fglrx kernel module failed to build
  UpgradeStatus: Upgraded to trusty on 2014-08-12 (24 days ago)
  dmi.bios.date: 11/19/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0406
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 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.:bvr0406:bd11/19/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-SE:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  make.log:
   DKMS make.log for fglrx-8.970 for kernel 3.13.0-35-generic (i686)
   vendredi 5 septembre 2014, 10:32:38 (UTC+0200)
   AMD kernel module generator version 2.1
   kernel includes at /lib/modules/3.13.0-35-generic/build/include not found or 
incomplete
   file: /lib/modules/3.13.0-35-generic/build/include/linux/version.h
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Sep  5 09:40:18 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.ve

[Desktop-packages] [Bug 1366260] Re: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

2014-09-07 Thread Daniel Letzeisen

You do not have an AMD/ATI GPU (graphics card). It does not make sense
to install fglrx or nvidia drivers.

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

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

Title:
  fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build

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

Bug description:
  Ao fazer atualização do Kernel apareceu a seguinte mensagem "Error!
  Bad return status for module build on kernel: 3.16.2-031602-lowlatency
  (i686)"

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx 2:13.350.1-0ubuntu2
  Uname: Linux 3.16.1-031601-lowlatency i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DKMSKernelVersion: 3.16.2-031602-generic
  Date: Sat Sep  6 00:53:45 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.350.1: added
   vboxhost, 4.3.14, 3.16.1-031601-generic, i686: installed
   vboxhost, 4.3.14, 3.16.1-031601-lowlatency, i686: installed
   vboxhost, 4.3.14, 3.16.2-031602-generic, i686: installed
   vboxhost, 4.3.14, 3.16.2-031602-lowlatency, i686: installed
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Device [1019:2267]
  InstallationDate: Installed on 2014-06-01 (96 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: POSITIVO POS-EINM10CB
  PackageVersion: 2:13.350.1-0ubuntu2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.1-031601-lowlatency 
root=UUID=c4f21686-6e48-46f5-aee6-46518cdf05b2 ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  Title: fglrx 2:13.350.1-0ubuntu2: fglrx kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2011
  dmi.bios.vendor: Desenvolvida para Positivo Informatica SA
  dmi.bios.version: 080015
  dmi.board.name: POS-EINM10CB
  dmi.board.vendor: Positivo Informatica SA
  dmi.board.version: SIM
  dmi.chassis.type: 3
  dmi.chassis.vendor: POSITIVO
  dmi.modalias: 
dmi:bvnDesenvolvidaparaPositivoInformaticaSA:bvr080015:bd06/09/2011:svnPOSITIVO:pnPOS-EINM10CB:pvr0906_SIM:rvnPositivoInformaticaSA:rnPOS-EINM10CB:rvrSIM:cvnPOSITIVO:ct3:cvr:
  dmi.product.name: POS-EINM10CB
  dmi.product.version: 0906_SIM
  dmi.sys.vendor: POSITIVO
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.56+git20140801.5d835797-0ubuntu0sarvatt~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.4.0~git20140904.3dbf55c1-0ubuntu0sarvatt~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.4.0~git20140904.3dbf55c1-0ubuntu0sarvatt~trusty
  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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914+git20140904.aa10f480-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty
  xserver.bootTime: Sat Sep  6 00:14:41 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:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Desktop-packages] [Bug 1289991] Re: Libre office Writer displays in wrong workspace

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

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

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

Title:
  Libre office Writer displays in wrong workspace

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  I have a strange issue with Libre Office

  I have my Libre running in the Workspace 2, with multiple documents
  and spreadsheets. There switching between them works fine. But if I
  swich to Workspace 1, where I have my web browser running, I see all
  the Writer instances in the application switcher panel. Also, if I
  want to Alt+Tab to next program while in Workspace 1, I see all the
  Writer instances in the Switcher dialog listed before the applications
  that are in Workspace 1. And then have to press Alt+Tab repeatedly to
  get into the window which I want. If I Alt+Tab to a Writer window,
  nothing happens.

  This is annoying, since my web browsing workspace get cluttered with
  useless Writer instances, which should show only in worskpace 2.

  I'm using Gnome CLASSIC

  Libre Office Version: 4.1.3.2
  Build ID: 410m0(Build:2)
  Ubuntu 13.10
  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-08 (280 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  Package: libreoffice 1:4.1.3-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Tags:  saucy
  Uname: Linux 3.11.0-19-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2014-03-06 (70 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 828893] Re: left mouse button ignored

2014-09-07 Thread Matthias Homann

I also seem to have this bug on Ubuntu 12.04 since the upgrade to HWE
Trusty and on Lubuntu 14.04. I also see this bug if my Bluetooth mouse
is configured. As soon as I remove my Bluetooth mouse from the
configuration left key works agains with other USB mouses and the
touchpad.

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

Title:
  left mouse button ignored

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Fix Released

Bug description:
  After a random amount of time, the left mouse button gets ignored, regardless 
of where one tries to click. The other mouse buttons still work. It does not 
seem to be connected to any particular application.  I never saw the problem in 
10.04 or 10.10, but it happens nearly daily in 11.04.  (both 32- and 64-bit)
  I suspect it could be caused by the system failing to notice a key/button 
release and so try to get out if it by pressing all the keyboard modifier keys 
and all mouse buttons one by one.   Doing so sometimes helps, other times a 
reboot is needed to get the left mouse button back.
  As a test, I started "xev" while the system was affected by the bug. It gives 
ButtonPress and ButtonRelease events for most mouse buttons, but no event is 
generated when pressing the left button.
  I don't think it is a hardware problem as I've seen it on two computers with 
different mice.
  There is a discussion thread devoted to the issue too:  
http://ubuntuforums.org/showthread.php?t=1750236

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: unity 3.8.16-0ubuntu1~natty1
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,snap,move,imgpng,gnomecompat,vpswitch,regex,mousepoll,place,resize,unitymtgrabhandles,session,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell]
  Date: Thu Aug 18 18:06:51 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=sv_SE.UTF-8
   LC_MESSAGES=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  Architecture: amd64
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  NonfreeKernelModules: nvidia
  Package: xserver-xorg-input-evdev 1:2.6.0-1ubuntu12
  PackageArchitecture: amd64
  ProcEnviron:
   LANGUAGE=en_US:en
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Tags:  natty running-unity ubuntu
  Uname: Linux 2.6.38-11-generic x86_64
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  --- 
  Architecture: i386
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  NonfreeKernelModules: nvidia
  Package: xserver-xorg-input-evdev 1:2.6.0-1ubuntu12
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=en_US:en
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Tags:  natty running-unity ubuntu
  Uname: Linux 2.6.38-11-generic i686
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

2014-09-07 Thread Uwe Cappeller

@Abhijit: The xorg.conf will only regenerated if you have deleted or
renamed the previous version of it. Otherwise the change will be skipped
by system.

Do the following:

1. 'sudo mv xorg.conf xorg.conf.backup' (Don't reboot after it go directly to 
the next step!) 
2. 'sudo aticonfig --adapter=all --initial'
3. Reboot and go on as Alberto described

but i guess that after rebootimg the system the xorg.conf generated by
by aticonfig will be overwritten again.

@Alberto: Thank you for the fix. As soon as it is issued I will load
from backport and test it .

Best Regards,
Uwe

-- 
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 Committed

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

[Desktop-packages] [Bug 1038479] Re: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a while

2014-09-07 Thread Степан

Hi. 
The same problem with Acer TravelMate 8572G - Conexant CX20585

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

Title:
  [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a
  while

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

Bug description:
  Restart will fix the issue, but sound always quits from internal
  speaker. Headphones work always.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bernie 1838 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc060 irq 44'
 Mixer name : 'Intel CougarPoint HDMI'
 Components : 'HDA:14f15069,1179fc50,00100302 
HDA:80862805,1179fc50,0010'
 Controls  : 24
 Simple ctrls  : 11
  Date: Sat Aug 18 11:18:34 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [Satellite L755, Conexant CX20585, Speaker, Internal] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr2.20:bd07/13/2011:svnTOSHIBA:pnSatelliteL755:pvrPSK1WU-05N004:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite L755
  dmi.product.version: PSK1WU-05N004
  dmi.sys.vendor: TOSHIBA

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

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

[Desktop-packages] [Bug 1366519] [NEW] Incredibly slow editing of documents when connected to network

2014-09-07 Thread Jason Bassett

Public bug reported:

When editing a document using LibreOffice, the system locks up after
every update typed.  Lock up can be up to 30 seconds before control is
returned to the user.   I have found that this takes place even on
documents located on the same physical machine, not just network hosted
documents.

Problem does not occur if I disconnect form the SSHFS drive.

I can understand potential delay when editing a remote document but the
connection to an SSHFS file server is affecting editing of locally held
documents too.

Description:Ubuntu 14.04.1 LTS
Release:14.04
libreoffice-writer:  Installed: 1:4.2.6.3-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libreoffice-core 1:4.2.6.3-0ubuntu1
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.3
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Sep  7 12:15:10 2014
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2014-05-08 (121 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Incredibly slow editing of documents when connected to network

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  When editing a document using LibreOffice, the system locks up after
  every update typed.  Lock up can be up to 30 seconds before control is
  returned to the user.   I have found that this takes place even on
  documents located on the same physical machine, not just network
  hosted documents.

  Problem does not occur if I disconnect form the SSHFS drive.

  I can understand potential delay when editing a remote document but
  the connection to an SSHFS file server is affecting editing of locally
  held documents too.

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  libreoffice-writer:  Installed: 1:4.2.6.3-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-core 1:4.2.6.3-0ubuntu1
  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.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Sep  7 12:15:10 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-05-08 (121 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

Thanks Alberto. I followed the above instructions and tried regenerating
the xorg.conf. But it's giving the following message:

Found fglrx primary device section
Found fglrx primary device section
Unable to find any supported Screen sections

The resulting xorg.conf looks the same as before (its not the longer
version). I have rebooted the machine, but its stuck at black screen. I
am attaching the Xorg.0.log and the xorg.conf here.

I could potentially reinstall and apply the above nogpumanager
modification and let you know how it goes. Let me know how to proceed.

I can only echo Uwe's sentiment above. Really appreciate all your help.
Abhijit

** Attachment added: "files3.zip"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4197717/+files/files3.zip

--
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 Committed

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]
Instal

[Desktop-packages] [Bug 1357064] Re: package postgresql-9.1 9.1.14-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2014-09-07 Thread Knimmet

I have exactly the same problem after upgrading my ubuntu version (12.04 LTS).
I'm in a solution urgent.

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

Title:
  package postgresql-9.1 9.1.14-0ubuntu0.12.04 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in “postgresql-9.1” package in Ubuntu:
  Confirmed

Bug description:
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
libossp-uuid16
  Use 'apt-get autoremove' to remove them.
  The following extra packages will be installed:
postgresql-common
  Suggested packages:
oidentd ident-server locales-all
  The following NEW packages will be installed:
postgresql-9.1 postgresql-common
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/4,419 kB of archives.
  After this operation, 11.7 MB of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Preconfiguring packages ...
  Selecting previously unselected package postgresql-common.
  (Reading database ... 260208 files and directories currently installed.)
  Unpacking postgresql-common (from .../postgresql-common_129ubuntu1_all.deb) 
...
  Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by 
postgresql-common'
  Selecting previously unselected package postgresql-9.1.
  Unpacking postgresql-9.1 (from 
.../postgresql-9.1_9.1.14-0ubuntu0.12.04_i386.deb) ...
  Processing triggers for ureadahead ...
  Processing triggers for man-db ...
  Setting up postgresql-common (129ubuntu1) ...
  Building PostgreSQL dictionaries from installed myspell/hunspell packages...
en_us
   * Starting PostgreSQL 9.1 database server   [ OK 
] 
  Setting up postgresql-9.1 (9.1.14-0ubuntu0.12.04) ...
  Creating new cluster (configuration: /etc/postgresql/9.1/main, data: 
/var/lib/postgresql/9.1/main)...
  Moving configuration file /var/lib/postgresql/9.1/main/postgresql.conf to 
/etc/postgresql/9.1/main...
  Moving configuration file /var/lib/postgresql/9.1/main/pg_hba.conf to 
/etc/postgresql/9.1/main...
  Moving configuration file /var/lib/postgresql/9.1/main/pg_ident.conf to 
/etc/postgresql/9.1/main...
  Configuring postgresql.conf to use port 5432...
  update-alternatives: using /usr/share/postgresql/9.1/man/man1/postmaster.1.gz 
to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode.
   * Starting PostgreSQL 9.1 database server
   * The PostgreSQL server failed to start. Please check the log output.
   
[fail]
  invoke-rc.d: initscript postgresql, action "start" failed.
  dpkg: error processing postgresql-9.1 (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   postgresql-9.1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.14-0ubuntu0.12.04
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
  Uname: Linux 3.2.0-67-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering: postgresql-9.1: Configure
  Architecture: i386
  Date: Fri Aug 15 01:48:54 2014
  DuplicateSignature: package:postgresql-9.1:9.1.14-0ubuntu0.12.04:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.14-0ubuntu0.12.04 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1357064/+subscriptions

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

[Desktop-packages] [Bug 1357064] Re: package postgresql-9.1 9.1.14-0ubuntu0.12.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** Changed in: postgresql-9.1 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package postgresql-9.1 9.1.14-0ubuntu0.12.04 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in “postgresql-9.1” package in Ubuntu:
  Confirmed

Bug description:
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following package was automatically installed and is no longer required:
libossp-uuid16
  Use 'apt-get autoremove' to remove them.
  The following extra packages will be installed:
postgresql-common
  Suggested packages:
oidentd ident-server locales-all
  The following NEW packages will be installed:
postgresql-9.1 postgresql-common
  0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/4,419 kB of archives.
  After this operation, 11.7 MB of additional disk space will be used.
  Do you want to continue [Y/n]? y
  Preconfiguring packages ...
  Selecting previously unselected package postgresql-common.
  (Reading database ... 260208 files and directories currently installed.)
  Unpacking postgresql-common (from .../postgresql-common_129ubuntu1_all.deb) 
...
  Adding 'diversion of /usr/bin/pg_config to /usr/bin/pg_config.libpq-dev by 
postgresql-common'
  Selecting previously unselected package postgresql-9.1.
  Unpacking postgresql-9.1 (from 
.../postgresql-9.1_9.1.14-0ubuntu0.12.04_i386.deb) ...
  Processing triggers for ureadahead ...
  Processing triggers for man-db ...
  Setting up postgresql-common (129ubuntu1) ...
  Building PostgreSQL dictionaries from installed myspell/hunspell packages...
en_us
   * Starting PostgreSQL 9.1 database server   [ OK 
] 
  Setting up postgresql-9.1 (9.1.14-0ubuntu0.12.04) ...
  Creating new cluster (configuration: /etc/postgresql/9.1/main, data: 
/var/lib/postgresql/9.1/main)...
  Moving configuration file /var/lib/postgresql/9.1/main/postgresql.conf to 
/etc/postgresql/9.1/main...
  Moving configuration file /var/lib/postgresql/9.1/main/pg_hba.conf to 
/etc/postgresql/9.1/main...
  Moving configuration file /var/lib/postgresql/9.1/main/pg_ident.conf to 
/etc/postgresql/9.1/main...
  Configuring postgresql.conf to use port 5432...
  update-alternatives: using /usr/share/postgresql/9.1/man/man1/postmaster.1.gz 
to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode.
   * Starting PostgreSQL 9.1 database server
   * The PostgreSQL server failed to start. Please check the log output.
   
[fail]
  invoke-rc.d: initscript postgresql, action "start" failed.
  dpkg: error processing postgresql-9.1 (--configure):
   subprocess installed post-installation script returned error exit status 1
  No apport report written because MaxReports is reached already
Errors were 
encountered while processing:
   postgresql-9.1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.14-0ubuntu0.12.04
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic-pae 3.2.60
  Uname: Linux 3.2.0-67-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering: postgresql-9.1: Configure
  Architecture: i386
  Date: Fri Aug 15 01:48:54 2014
  DuplicateSignature: package:postgresql-9.1:9.1.14-0ubuntu0.12.04:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.14-0ubuntu0.12.04 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-9.1/+bug/1357064/+subscriptions

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

[Desktop-packages] [Bug 1366505] [NEW] $ ubuntu-bug ubuntu-bug fails

2014-09-07 Thread anatoly techtonik

Public bug reported:

$ ubuntu-bug ubuntu-bug
dpkg-query: no packages found matching ubuntu-bug
$ ubuntu-bug `which ubuntu-bug`

I almost forgot what original bug with `ubuntu-bug`
was about when I hit this one.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.3
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
NonfreeKernelModules: nvidia
ApportLog:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CrashReports:
 640:1000:122:85632:2014-09-04 13:58:36.715115547 +0300:2014-09-04 
13:59:35.47197 
+0300:/var/crash/_usr_share_software-center_software-center.1000.crash
 600:111:122:0:2014-09-04 13:59:37.599117257 +0300:2014-09-04 
13:59:37.599117257 
+0300:/var/crash/_usr_share_software-center_software-center.1000.uploaded
 664:1000:122:0:2014-09-04 13:59:34.387117169 +0300:2014-09-04 
13:59:34.387117169 
+0300:/var/crash/_usr_share_software-center_software-center.1000.upload
CurrentDesktop: Unity
Date: Sun Sep  7 13:16:15 2014
InstallationDate: Installed on 2012-03-12 (908 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to trusty on 2014-04-18 (141 days ago)

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

Title:
  $ ubuntu-bug ubuntu-bug fails

Status in “apport” package in Ubuntu:
  New

Bug description:
  $ ubuntu-bug ubuntu-bug
  dpkg-query: no packages found matching ubuntu-bug
  $ ubuntu-bug `which ubuntu-bug`

  I almost forgot what original bug with `ubuntu-bug`
  was about when I hit this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.3
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  NonfreeKernelModules: nvidia
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CrashReports:
   640:1000:122:85632:2014-09-04 13:58:36.715115547 +0300:2014-09-04 
13:59:35.47197 
+0300:/var/crash/_usr_share_software-center_software-center.1000.crash
   600:111:122:0:2014-09-04 13:59:37.599117257 +0300:2014-09-04 
13:59:37.599117257 
+0300:/var/crash/_usr_share_software-center_software-center.1000.uploaded
   664:1000:122:0:2014-09-04 13:59:34.387117169 +0300:2014-09-04 
13:59:34.387117169 
+0300:/var/crash/_usr_share_software-center_software-center.1000.upload
  CurrentDesktop: Unity
  Date: Sun Sep  7 13:16:15 2014
  InstallationDate: Installed on 2012-03-12 (908 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (141 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-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] Re: xorg.conf overwritten by booting system

@Uwe: ok, the fix that I committed today should solve your problem. I'll
backport it soon.

-- 
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 Committed

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.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version:

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

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1365695/+attachment/4197703/+files/Xorg.0.log.old

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