[Desktop-packages] [Bug 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder

2014-08-05 Thread Iain Lane
I uploaded evolution and evolution-data-server to trusty-proposed.
They're waiting for review from the stable release update team. Watch
this bug to know when you can test out the fix.

Thanks for your feedback.

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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail  Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  In Progress
Status in “evolution-data-server” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before  not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
   PC (0x7f88ad21b520) ok
   source 0x18(%r14) (0x0468) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
   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: evolution crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1295994] Re: Unable to use Printscreen Button on Ubuntu 14.04 in GNOME Shell

2014-08-05 Thread JANARDHAN H L
I do have a same problem with HP Pavillion g6 2313ax

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

Title:
  Unable to use Printscreen Button on Ubuntu 14.04 in GNOME Shell

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

Bug description:
  Hi, I am trying Ubuntu 14.04 and I noticed that Printscreen button
  doesn't work. I had no problems in 13.10. If I run gnome-screenshot,
  or gnome-screenshot -a  in a Terminal it says Unable to use GNOME
  Shell's builtin screenshot interface, resorting to fallback X11.I
  noticed that the function works if custom shortcuts are set. Can
  anyone help? Thanks

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

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


[Desktop-packages] [Bug 1350425] Re: Ubuntu 14.04 ACR38 card reader. Says card is not found in java applet

2014-08-05 Thread Mosipo
ic. but this card is working with Windows OS. 
Ok. thanks anyways. )))

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

Title:
  Ubuntu 14.04 ACR38 card reader. Says card is not found in java
  applet

Status in “pcsc-lite” package in Ubuntu:
  New

Bug description:
  ACR38 card reader is not working. Assume that I have wrong driver
  installed.

  tm@Compaq-HP-6510b:~$ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  tm@Compaq-HP-6510b:~$ java -version
  java version 1.8.0_11
  Java(TM) SE Runtime Environment (build 1.8.0_11-b12)
  Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode)

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

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


[Desktop-packages] [Bug 976638] Re: pkexec does not find any authentication agent

2014-08-05 Thread Guy
*** This bug is a duplicate of bug 1347272 ***
https://bugs.launchpad.net/bugs/1347272

Hi,

Just to say that it's steel the same after an upgrade 12.04.4  14.04.1
:

(polkit-gnome-authentication-agent-1:1810): GLib-CRITICAL **:
g_variant_new_string: assertion 'string != NULL' failed

(polkit-gnome-authentication-agent-1:1810): polkit-gnome-1-WARNING **:
Failed to register client:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SessionManager was not provided by any .service files

Sorry if it's the wrong place to comment.

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

Title:
  pkexec does not find any authentication agent

Status in System policy:
  Confirmed
Status in “policykit-1” package in Ubuntu:
  Triaged

Bug description:
  I am using xubuntu, but I am pretty sure that other variants are
  affected too.

  My problem started with being unable to start synaptic from the menu.
  So far, I have found out that synaptic is started with pkexec.

  When I test starting
  pkexec /usr/sbin/synaptic
  in a terminal, it asks for the password in text mode.

  With another test
  pkexec --disable-internal-agent /usr/sbin/synaptic
  in the terminal, it says it has not found any authentication agent.

  I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the 
PC's and the laptop.
  Comparing the /etc directory trees of the PC's showed many differences, but I 
could not find anything suspicious about the polycikit configuration.

  For the moment, using gksu instead of pkexec is a workaround.

  Thanks and Regards,
  Markus

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: policykit-1 0.104-1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  8 17:05:34 2012
  InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 
(20120330)
  ProcEnviron:
   LANGUAGE=de_DE:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/976638/+subscriptions

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


[Desktop-packages] [Bug 1308895] Re: Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in Ubuntu's /lib/udev/r

2014-08-05 Thread Jan Nekvasil
Debian's usb-modeswitch_2.2.0+repack0-1_amd64.deb and usb-modeswitch-
data_20140529-1_all.deb from https://packages.debian.org/sid/amd64/usb-
modeswitch/download and https://packages.debian.org/sid/amd64/usb-
modeswitch-data/download fixed it for me for Huawei E3531s - 2.

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

Title:
  Please merge usb-modeswitch from Debian unstable - Huawei E3531 does
  not automatically switches to modem mode (no udev rules for this modem
  in Ubuntu's /lib/udev/rules.d)

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  The operating system does not see the modem  maybe because usb-
  modeswitch not automatically switches the device mode the modem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 11:34:11 2014
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415)
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1308895] Re: Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in Ubuntu's /lib/udev/r

2014-08-05 Thread Lars Melin
@ Saurabh Sharma

12d1:1506 is a usb id for E3531s after it has been mode switched so 
usb_modeswitch has done what it should do.
I think your problem is either linux driver related or NetworkManager related 
so please provide the output from:
lsusb -v -d 12d1:1506

It will show how the interfaces are intended to be used and which
driver(s) should be used.

You can also do:

cat /proc/bus/usb/devices

which will show which drivers have already bound to the interfaces.

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

Title:
  Please merge usb-modeswitch from Debian unstable - Huawei E3531 does
  not automatically switches to modem mode (no udev rules for this modem
  in Ubuntu's /lib/udev/rules.d)

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  The operating system does not see the modem  maybe because usb-
  modeswitch not automatically switches the device mode the modem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 11:34:11 2014
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415)
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1348613] Re: Attach file shortcut (Shift+Ctrl+A) not working if no CAPS lock

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

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

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

Title:
  Attach file shortcut (Shift+Ctrl+A) not working if no CAPS lock

Status in “thunderbird” package in Ubuntu:
  Confirmed

Bug description:
  Since I updated to Thunderbird 31.0 on my Ubuntu 14.04 computer, the
  attach file to email shortcut (Shift+Ctrl+A) doesn't work if CAPS
  lock is disabled (it just select all such as Ctrl+A).

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

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


[Desktop-packages] [Bug 1322925] Re: copy paste not working in Ubuntu 14.04 nautilus

2014-08-05 Thread Dan
I confirm this very annoying bug in Ubuntu 14.04. Nautilus (Files)
became unusable. Copy and paste stop working (no matter how you want to
access them, e.g. shortcuts, menu) after an undetermined period of time
since starting the application. I am using Ctrl+T to split the window
but I can not confirm it is related to it or not. Nautilus (Files) is
the most used application in Ubuntu and copy/paste files is the most
common action. We badly need this solved.

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

Title:
  copy paste not working in Ubuntu 14.04 nautilus

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  The title says it.

  Since upgrade to 14.04, copy / cut / paste of files among various
  folders I have write rights on does not work most of the times.

  Using the terminal to copy / move does work normally.

  
  nautilus:
Installed: 1:3.10.1-0ubuntu9.1
Candidate: 1:3.10.1-0ubuntu9.1
Version table:
   *** 1:3.10.1-0ubuntu9.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

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

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


[Desktop-packages] [Bug 1352752] [NEW] Xorg crash when using rdesktop

2014-08-05 Thread Fridtjof Busse
Public bug reported:

After the upgrade to 14.04, Xorg crashes when using rdesktop and throws me back 
to the login screen.
Crash happens a few seconds after logging in to the remote RDP system.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Aug  5 09:42:25 2014
DistUpgraded: 2014-08-04 09:44:10,092 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:04ad]
MachineType: Dell Inc. OptiPlex 790
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=8575d8b5-9f19-4a99-98c6-af17db3e1cd2 ro nosplash quiet splash 
vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to trusty on 2014-08-04 (0 days ago)
dmi.bios.date: 09/10/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0HY9JP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Aug  5 09:41:51 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   61461 
 vendor DEL
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 crash 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/1352752

Title:
  Xorg crash when using rdesktop

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After the upgrade to 14.04, Xorg crashes when using rdesktop and throws me 
back to the login screen.
  Crash happens a few seconds after logging in to the remote RDP system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug  5 09:42:25 2014
  DistUpgraded: 2014-08-04 09:44:10,092 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ad]
  MachineType: Dell Inc. OptiPlex 790
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=8575d8b5-9f19-4a99-98c6-af17db3e1cd2 ro nosplash quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to trusty on 2014-08-04 (0 days ago)
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 

[Desktop-packages] [Bug 1314787] Re: Memory leak

2014-08-05 Thread GVS
And I have the same issue on my Toshiba C650D w/ 3 GB and AMD Radeon
6350.  Being that it is an older laptop and has only 3 GB memory, I have
to either restart or kill and restart Xorg many times a day.  Terrible,
and soon to be a deal breaker for Xubuntu if a fix is not released very
soon.

This started with installing Trusty over 12.04.

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

Title:
  Memory leak

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  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.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 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:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: 

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

2014-08-05 Thread Greg Tippitt
I agree that this bug should be a higher priority.  I have a cluster
built on Quad CPU SuperMicro H8QME2 motherboards with hex-core Opteron
CPUs .  With 12.04LTS, the motherboard ATI graphics worked fine as the
machines are BOINC number crunchers.  The motherboards also have NVIDIA
Telsa GPU co-processor boards for GPU number crunching, which I have not
been able to get working for several weeks  since upgrading to 14.04LTS.
They all worked fine with 12.04 LTS, but this new feature of 14.04 LTS
is absurd.

I could not figure out what was happening the xorg.conf files.  I have
to load the NVIVIDA drivers for  CUDA/OPENCL  processing to work, but
needed the display to be active on the motherboard ATI graphics , as
these  Telsa cards are strictly for crunching and have no display output
capability.  This new feature kept forcing the systems to try to
display to a screen attached to the TESLA cards.

If the problem can't be fixed easily, an simple work-around for users
should be provided until the problem can be fixed.

Greg

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  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: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  

[Desktop-packages] [Bug 1352752] Re: Xorg crash when using rdesktop

2014-08-05 Thread Fridtjof Busse
Updating to the latest Intel drivers from [1] appears to have solved the 
problem.
[1] 
https://01.org/linuxgraphics/downloads/2014/intelr-graphics-installer-1.0.6-linux

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

Title:
  Xorg crash when using rdesktop

Status in “xorg” package in Ubuntu:
  New

Bug description:
  After the upgrade to 14.04, Xorg crashes when using rdesktop and throws me 
back to the login screen.
  Crash happens a few seconds after logging in to the remote RDP system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug  5 09:42:25 2014
  DistUpgraded: 2014-08-04 09:44:10,092 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.14, 3.13.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ad]
  MachineType: Dell Inc. OptiPlex 790
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=8575d8b5-9f19-4a99-98c6-af17db3e1cd2 ro nosplash quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to trusty on 2014-08-04 (0 days ago)
  dmi.bios.date: 09/10/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/10/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Aug  5 09:41:51 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   61461 
   vendor DEL
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Desktop-packages] [Bug 1249513] Re: [xmir] System graphics slow majorily after logout/login

2014-08-05 Thread Daniel van Vugt
Not sure what isn't relevant. Setting to incomplete while we can't
reproduce the problem, and/or see if it reoccurs for David.

** Tags added: performance

** Changed in: compiz
   Status: Invalid = Incomplete

** Changed in: mir
   Status: Triaged = Incomplete

** Changed in: unity
   Status: Invalid = Incomplete

** Changed in: xmir
   Status: Triaged = Incomplete

** Changed in: compiz (Ubuntu)
   Status: Invalid = Incomplete

** Changed in: mir (Ubuntu)
   Status: Triaged = Incomplete

** Changed in: unity (Ubuntu)
   Status: Invalid = Incomplete

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

Title:
  [xmir] System graphics slow majorily after logout/login

Status in Compiz:
  Incomplete
Status in Mir:
  Incomplete
Status in Unity:
  Incomplete
Status in XMir:
  Incomplete
Status in “compiz” package in Ubuntu:
  Incomplete
Status in “mir” package in Ubuntu:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 13.10 with the system compositor repos enabled and
  so I believe I have 0.0.15 installed. Logging out and choosing another
  user from the login screen (or the same previous login name) will
  render the system pretty useless. Drawing of graphics seems to be slow
  when this happens. One major issue is trying to click on the icons on
  the side bar. It opens very slow but then quickly wants to retract
  again. Bringing up programs takes an extremely long time after logging
  out/logging in. closing out or minimizing programs causes almost a
  frame by frame close out.

  The system I am using is a Compaq DC5100 computer with Intel 910GL Graphics. 
This, again, only happens after logging out and then right back in...then the 
problems start. Let me know if you need me to run any other tests.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  DistroRelease: Ubuntu 13.10
  GraphicsCard:
   Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] 
(rev 04) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:300d]
  InstallationDate: Installed on 2013-10-19 (22 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MarkForUpload: True
  Package: unity-system-compositor 0.0.1+13.10.20131015-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy
  Uname: Linux 3.11.0-13-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  version.libdrm: libdrm2 2.4.46-1
  version.lightdm: lightdm 1.8.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

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

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


[Desktop-packages] [Bug 1351903] Re: network-manager-gnome 0.9.8.8-0ubuntu4.3 or associated libraries cause HUGE memory usage on wlan0

2014-08-05 Thread GVS
After much messing around I have discovered that this is actually a Xorg
bug (Bug #1314787 ).

However, the issue is greatly exacerbated by the Network-manager-gnome
0.9.8.8-0ubuntu4.3 update.  Prior to the update, the issue was not
salient.  After the update Xorg runs the system out of memory several
times per day.  Noticiable immediatly after starting 'net usage.

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

Title:
   network-manager-gnome 0.9.8.8-0ubuntu4.3  or associated libraries
  cause HUGE memory usage on wlan0

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

Bug description:
  Network-manager-gnome 0.9.8.8-0ubuntu4.3  associated libraries cause
  HUGE memory usage on wlan0.

  Usage of wlan0 by any net app causes resident memory consumption by
  NMG to grow until all system memory is used and system becomes
  unresponsive.  This takes several hours, but is consistent and
  unavoidable.

  Reverting to previous version of NMG (0.9.8.8-0ubuntu4.2) eliminates
  the issue and NMG functions as expected.

  Xubuntu 14.04 LTS up-to-date AMD64
  Toshiba C650D Laptop w/ Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n 
WiFi Adapter

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

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


[Desktop-packages] [Bug 1351616] Re: Ubuntu 14.04: multi-touch screen can cause desktop to unlock

2014-08-05 Thread Timo Aaltonen
Do you have all updates installed? I had, so it was not a stock in
that sense.. I see no crashes, nothing in Xorg log either.

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

Title:
  Ubuntu 14.04: multi-touch screen can cause desktop to unlock

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce on a laptop with a multitouch screen (in my case, a
  Lenovo X1 Carbon Gen 2):

  1. Lock the desktop.
  2. Start lightly tapping away on the laptop screen and triggering various 
bogus multitouch events.
  3. The Xorg issue reported in 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1121379 
will eventually trigger and gnome-session will crash
  4. You are able to view the unlocked desktop, and have limited keyboard/mouse 
access to the desktop.

  The issue seems to be similar to
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308572 , which
  is marked fixed, but it looks like in the event of a crash the screen
  can still become unlocked.

  Relevant logs:
  == /var/log/auth.log ==
  Aug  2 09:14:10 SOMEHOST compiz: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
director
  y
  Aug  2 09:14:10 SOMEHOST compiz: PAM adding faulty module: pam_kwallet.so
  Aug  2 09:14:10 SOMEHOST compiz: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user SOMEUSER

  == /var/log/syslog ==
  Aug  2 09:14:24 SOMEHOST gnome-session[2065]: WARNING: App 'compiz.desktop' 
respawning too quickly
  Aug  2 09:14:24 SOMEHOST gnome-session[2065]: WARNING: App 'compiz.desktop' 
exited with code 1
  Aug  2 09:14:24 SOMEHOST gnome-session[2065]: WARNING: App 'compiz.desktop' 
respawning too quickly

  == /var/log/Xorg.0.log ==
  [   445.600] (EE) Backtrace:
  [   445.600] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f6921bd8c78]
  [   445.600] (EE) 1: /usr/bin/X (0x7f6921a3+0x7d3e7) [0x7f6921aad3e7]
  [   445.600] (EE) 2: /usr/bin/X (0x7f6921a3+0x138845) [0x7f6921b68845]
  [   445.600] (EE) 3: /usr/bin/X (0x7f6921a3+0x138357) [0x7f6921b68357]
  [   445.600] (EE) 4: /usr/bin/X (0x7f6921a3+0x13afa2) [0x7f6921b6afa2]
  [   445.601] (EE) 5: /usr/bin/X (0x7f6921a3+0x15c1d4) [0x7f6921b8c1d4]
  [   445.601] (EE) 6: /usr/bin/X (mieqProcessDeviceEvent+0x1cd) 
[0x7f6921bbb0cd]
  [   445.601] (EE) 7: /usr/bin/X (mieqProcessInputEvents+0xf7) [0x7f6921bbb1e7]
  [   445.601] (EE) 8: /usr/bin/X (ProcessInputEvents+0x9) [0x7f6921ac2fe9]
  [   445.601] (EE) 9: /usr/bin/X (0x7f6921a3+0x55802) [0x7f6921a85802]
  [   445.601] (EE) 10: /usr/bin/X (0x7f6921a3+0x5994a) [0x7f6921a8994a]
  [   445.601] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f691f56cec5]
  [   445.601] (EE) 12: /usr/bin/X (0x7f6921a3+0x44e7e) [0x7f6921a74e7e]
  [   445.601] (EE)
  [   445.724] (EE) BUG: triggered 'if (!(event-device_event.flags  (1  
5)))'
  [   445.724] (EE) BUG: ../../dix/touch.c:644 in TouchConvertToPointerEvent()
  [   445.724] (EE) Non-emulating touch event
  [   445.725] (EE)
  [   445.725] (EE) Backtrace:
  [   445.725] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f6921bd8c78]
  [   445.725] (EE) 1: /usr/bin/X (0x7f6921a3+0x7d3e7) [0x7f6921aad3e7]
  [   445.725] (EE) 2: /usr/bin/X (0x7f6921a3+0x138845) [0x7f6921b68845]
  [   445.725] (EE) 3: /usr/bin/X (0x7f6921a3+0x138357) [0x7f6921b68357]
  [   445.725] (EE) 4: /usr/bin/X (0x7f6921a3+0x13afa2) [0x7f6921b6afa2]
  [   445.726] (EE) 5: /usr/bin/X (0x7f6921a3+0x15c1d4) [0x7f6921b8c1d4]
  [   445.726] (EE) 6: /usr/bin/X (mieqProcessDeviceEvent+0x1cd) 
[0x7f6921bbb0cd]
  [   445.726] (EE) 7: /usr/bin/X (mieqProcessInputEvents+0xf7) [0x7f6921bbb1e7]
  [   445.726] (EE) 8: /usr/bin/X (ProcessInputEvents+0x9) [0x7f6921ac2fe9]
  [   445.726] (EE) 9: /usr/bin/X (0x7f6921a3+0x558c6) [0x7f6921a858c6]
  [   445.726] (EE) 10: /usr/bin/X (0x7f6921a3+0x5994a) [0x7f6921a8994a]
  [   445.726] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f691f56cec5]
  [   445.726] (EE) 12: /usr/bin/X (0x7f6921a3+0x44e7e) [0x7f6921a74e7e]
  [   445.727] (EE)
  [   450.837] (II) AIGLX: Suspending AIGLX clients for VT switch

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

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


[Desktop-packages] [Bug 1314787] Re: Memory leak

2014-08-05 Thread GVS
@Nipul Gandhi

Based on the date of your comment, I ask if you noticed the memory leak
exacerbated after the recent Network-manager-gnome 0.9.8.8-0ubuntu4.3
update from Network-manager-gnome 0.9.8.8-0ubuntu4.2?

After the above NMG  update, on my system, Xorg uses up all memory
several times a day; prior to the update it was once a day or once every
two days.  I have filed a NWG bug (bug #1351903) regarding this.

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

Title:
  Memory leak

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  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.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 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:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open 

[Desktop-packages] [Bug 1277245] Re: nvidia prime causing mouse and screen to freeze

2014-08-05 Thread Hendrik Knackstedt
*** This bug is a duplicate of bug 1220426 ***
https://bugs.launchpad.net/bugs/1220426

** This bug has been marked a duplicate of bug 1220426
   [nvidia-prime]Freeze while using touchpad

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

Title:
  nvidia prime causing mouse and screen to freeze

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

Bug description:
  I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of 6th 
Feb. 64bit. 
  After installing nvidia-prime and nvidia-331, i can see frequent mouse 
freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. Only 
way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back by 
unloading and loading the psmouse module

  modprobe -r psmouse.

  lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 18)
  01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] 
(rev a2)

  
  uname -a
  Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION=Ubuntu Trusty Tahr (development branch)

  This issue does not occur while running the opensource driver.

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

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


[Desktop-packages] [Bug 1245666] Re: Pidgin is creating zombies with 13.10

2014-08-05 Thread Ivan
Problem remains in 14.04

Ivan

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

Title:
  Pidgin is creating zombies with 13.10

Status in “pidgin” package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Kubuntu 13.10 pidgin is constantly creating new
  zombies.

  E.g. after an uptime of roughly 4 hours:
  $ ps aux | grep Z
  USER   PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
  cm2589  0.0  0.0  0 0 ?Z17:46   0:00 [pidgin] 
defunct
  cm3045  0.0  0.0  0 0 ?Z17:47   0:00 [pidgin] 
defunct
  cm3106  0.0  0.0  0 0 ?Z17:48   0:00 [pidgin] 
defunct
  cm3236  0.0  0.0  0 0 ?Z17:50   0:00 [pidgin] 
defunct
  cm5760  0.0  0.0  0 0 ?Z17:54   0:00 [pidgin] 
defunct
  cm5788  0.0  0.0  0 0 ?Z18:02   0:00 [pidgin] 
defunct
  cm6405  0.0  0.0  0 0 ?Z18:12   0:00 [pidgin] 
defunct
  cm6501  0.0  0.0  0 0 ?Z18:22   0:00 [pidgin] 
defunct
  cm6519  0.0  0.0  0 0 ?Z18:32   0:00 [pidgin] 
defunct
  cm6543  0.0  0.0  0 0 ?Z18:42   0:00 [pidgin] 
defunct
  cm6580  0.0  0.0  0 0 ?Z18:52   0:00 [pidgin] 
defunct
  cm6619  0.0  0.0  0 0 ?Z19:02   0:00 [pidgin] 
defunct
  cm6645  0.0  0.0  0 0 ?Z19:12   0:00 [pidgin] 
defunct
  cm6672  0.0  0.0  0 0 ?Z19:22   0:00 [pidgin] 
defunct
  cm6691  0.0  0.0  0 0 ?Z19:32   0:00 [pidgin] 
defunct
  cm6757  0.0  0.0  0 0 ?Z19:42   0:00 [pidgin] 
defunct
  cm6846  0.0  0.0  0 0 ?Z19:52   0:00 [pidgin] 
defunct
  cm6869  0.0  0.0  0 0 ?Z20:01   0:00 [pidgin] 
defunct
  cm6889  0.0  0.0  0 0 ?Z20:11   0:00 [pidgin] 
defunct
  cm6914  0.0  0.0  0 0 ?Z20:21   0:00 [pidgin] 
defunct
  cm6931  0.0  0.0  0 0 ?Z20:31   0:00 [pidgin] 
defunct
  cm6948  0.0  0.0  0 0 ?Z20:41   0:00 [pidgin] 
defunct
  cm6972  0.0  0.0  0 0 ?Z20:51   0:00 [pidgin] 
defunct
  cm6992  0.0  0.0  0 0 ?Z21:01   0:00 [pidgin] 
defunct
  cm7015  0.0  0.0  0 0 ?Z21:11   0:00 [pidgin] 
defunct
  cm7036  0.0  0.0  0 0 ?Z21:20   0:00 [pidgin] 
defunct
  cm7121  0.0  0.0  0 0 ?Z21:30   0:00 [pidgin] 
defunct
  cm7223  0.0  0.0  10984   940 pts/0S+   21:38   0:00 grep 
--color=auto Z

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

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


[Desktop-packages] [Bug 1338404] Re: bbswitch: fails to find ACPI handle for discrete card

2014-08-05 Thread Andreas C. Osowski
@atterdag:
On the W520 I also ran into this issue. After removing the pci=noacpi kernel 
parameters required to boot the discrete device bumblebee works again.
Maybe other NVIDIA cards also required this in the past?

- Andreas

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

Title:
  bbswitch: fails to find ACPI handle for discrete card

Status in “bbswitch” package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I have a GeForce 9600 GT discrete card providing a third monitor on my
  14.04 Trusty system. The first two monitors are connected to the
  onboard Intel i7-3770 HD graphics.

  This is a contiunation of launchpad bug #1310023, where Alberto Milone
  wrote:

  
  @Hamish: that is a problem with bbswitch:

  [ 17.706791] bbswitch: cannot find ACPI handle for VGA device :01:00.0
  [ 17.706792] bbswitch: No discrete VGA device found

  Please file a bug report against bbswitch.
  

  You can find full debug logs in ticket #1310023, but briefly,

  bbswitch-dkms package version 0.7-2ubuntu1

  dmesg:
  
  [   17.693825] bbswitch: version 0.7
  [   17.693830] bbswitch: Found integrated VGA device :00:02.0: 
\_SB_.PCI0.GFX0
  [   17.693844] bbswitch: cannot find ACPI handle for VGA device :01:00.0
  [   17.693845] bbswitch: No discrete VGA device found
  [   17.706786] bbswitch: version 0.7
  [   17.706789] bbswitch: Found integrated VGA device :00:02.0: 
\_SB_.PCI0.GFX0
  [   17.706791] bbswitch: cannot find ACPI handle for VGA device :01:00.0
  [   17.706792] bbswitch: No discrete VGA device found
  

  $ lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09)
  01:00.0 VGA compatible controller: NVIDIA Corporation G94 [GeForce 9600 GT] 
(rev a1)

  
  fyi as per the previous ticket I upgraded ubuntu-drivers-common to version 
1:0.2.91.6 from trusty-proposed, but as in comment 23 there the same cannot 
find ACPI handle was present in dmesg before upgrading that package.

  
  The machine is dual boot with Windows 7, on the Windows side of things the 
three monitor setup works fine.

  
  ?

  thanks,
  Hamish

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

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


[Desktop-packages] [Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.

2014-08-05 Thread Shih-Yuan Lee
** Also affects: unity-settings-daemon
   Importance: Undecided
   Status: New

** Tags added: brightness trusty

** Tags added: broadwell haswell

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

Title:
  gnome-rr: Adjust the minimum brightness level when the maximum = 100.

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

Bug description:
  If the maximum brightness is equal to or bigger than 100, it has higher
  possibility that zero is off. So adjusting the minimum brightness to 1
  to avoid the problem.

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

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

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

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

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

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


[Desktop-packages] [Bug 1352495] Re: [HDA-Intel - HDA Intel PCH, recording] Clipped audio output added to mic recording when docked

2014-08-05 Thread agoodm
Please link to a tutorial for generating the verbose log file?

Mic switching between the ports seems to work fine, but when both
devices are plugged into the dock a distorted representation of what is
playing through the output device is mixed with the mic audio.

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Clipped audio output added to
  mic recording when docked

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Hi,

  I have a Lenovo X220 with an mini dock series 3 plus.  Ever since I
  have been using Ubuntu (originally 12.04 and more recently a clean
  14.04 install) I have issues with recording sound from the docking
  station.

  To elaborate plugging the devices in as follows works as expected:
  Mic into docking base
  Headset into laptops headset socket (a combined headset/mic socket)

  However when I connect both the headphones and the mic to the docking
  base a garbled representation of the output audio is mixed with the
  otherwise good quality input.

  I have tried to demonstrate this during the bug report process.  I had
  music playing during the sound recording tests.  During the first test
  the music playback stopped on its own and good quality sound was
  recorded.  During the second test music resumed and I talked over it
  at the end...  Hopefully this helps clarify my explanation.

  Alan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alan   2596 F pulseaudio
   /dev/snd/controlC0:  alan   2596 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug  4 18:52:04 2014
  InstallationDate: Installed on 2014-07-27 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: LifeCam Studio - Microsoft® LifeCam Studio(TM)
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: High background noise, or volume is too low
  Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET65WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET65WW(1.35):bd10/03/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Desktop-packages] [Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.

2014-08-05 Thread Launchpad Bug Tracker
** Branch linked: lp:~fourdollars/ubuntu/trusty/unity-settings-
daemon/1340544

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

Title:
  gnome-rr: Adjust the minimum brightness level when the maximum = 100.

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

Bug description:
  If the maximum brightness is equal to or bigger than 100, it has higher
  possibility that zero is off. So adjusting the minimum brightness to avoid 
the problem.

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

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

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

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

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

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


[Desktop-packages] [Bug 1176899] Re: apport-bug crashes

2014-08-05 Thread Martin Pitt
** No longer affects: apport

** Package changed: apport (Ubuntu) = python-qt4 (Ubuntu)

** Summary changed:

- apport-bug crashes
+ QTimerInfoList::updateCurrentTime crashes with SIGABRT

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

Title:
  QTimerInfoList::updateCurrentTime crashes with SIGABRT

Status in “python-qt4” package in Ubuntu:
  New

Bug description:
  Apport-bug crashes when it tries to collect crash data.

  Application: python3 (1.0)
  KDE Platform Version: 4.10.2
  Qt Version: 4.8.4
  Operating System: Linux 3.2.0-35-generic i686
  Distribution: Ubuntu 13.04

  
  The crash can be reproduced every time.

  -- Backtrace:
  Application: Apport KDE (python3.3), signal: Aborted
  Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
  [Current thread is 1 (Thread 0xb773b900 (LWP 4652))]

  Thread 2 (Thread 0xb60b6b40 (LWP 5579)):
  #0  0x00f89416 in __kernel_vsyscall ()
  #1  0x0065c8e2 in clock_gettime () from /lib/i386-linux-gnu/libc.so.6
  #2  0x010500d5 in do_gettime (frac=0xb60b5fe0, sec=0xb60b5fd8) at 
tools/qelapsedtimer_unix.cpp:123
  #3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
  #4  0x0113780e in QTimerInfoList::updateCurrentTime 
(this=this@entry=0xb300aaf4) at kernel/qeventdispatcher_unix.cpp:354
  #5  0x01137b9a in QTimerInfoList::timerWait (this=0xb300aaf4, tm=...) at 
kernel/qeventdispatcher_unix.cpp:461
  #6  0x01136373 in timerSourcePrepareHelper (src=optimized out, 
timeout=0xb60b610c) at kernel/qeventdispatcher_glib.cpp:136
  #7  0x0113640d in timerSourcePrepare (source=0xb300aac0, timeout=0xb60b610c) 
at kernel/qeventdispatcher_glib.cpp:169
  #8  0x046bad21 in g_main_context_prepare () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #9  0x046bb5cf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #10 0x046bb831 in g_main_context_iteration () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #11 0x01136c3f in QEventDispatcherGlib::processEvents (this=0xb300b8c8, 
flags=...) at kernel/qeventdispatcher_glib.cpp:426
  #12 0x011033ec in QEventLoop::processEvents (this=this@entry=0xb60b62a8, 
flags=...) at kernel/qeventloop.cpp:149
  #13 0x011036e1 in QEventLoop::exec (this=this@entry=0xb60b62a8, flags=...) at 
kernel/qeventloop.cpp:204
  #14 0x00feefec in QThread::exec (this=this@entry=0xa056558) at 
thread/qthread.cpp:542
  #15 0x010e2f2d in QInotifyFileSystemWatcherEngine::run (this=0xa056558) at 
io/qfilesystemwatcher_inotify.cpp:256
  #16 0x00ff1b18 in QThreadPrivate::start (arg=0xa056558) at 
thread/qthread_unix.cpp:338
  #17 0x00250d78 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
  #18 0x006493de in clone () from /lib/i386-linux-gnu/libc.so.6

  Thread 1 (Thread 0xb773b900 (LWP 4652)):
  [KCrash Handler]
  #7  0x00f89416 in __kernel_vsyscall ()
  #8  0x00586b1f in raise () from /lib/i386-linux-gnu/libc.so.6
  #9  0x0058a0b3 in abort () from /lib/i386-linux-gnu/libc.so.6
  #10 0x0057f877 in ?? () from /lib/i386-linux-gnu/libc.so.6
  #11 0x0057f927 in __assert_fail () from /lib/i386-linux-gnu/libc.so.6
  #12 0x095b744f in _XAllocID (dpy=0x9f06d68) at ../../src/xcb_io.c:528
  #13 0x003a417a in XRenderCreatePicture (dpy=0x9f06d68, drawable=197132349, 
format=0x9f15900, valuemask=0, attributes=0x0) at ../../src/Picture.c:90
  #14 0x01d634a4 in QX11PixmapData::x11ConvertToDefaultDepth (this=0xa381928) 
at image/qpixmap_x11.cpp:2255
  #15 0x01d0f396 in QWidgetPrivate::setWindowIcon_sys (this=0xa37d450, 
forceReset=forceReset@entry=false) at kernel/qwidget_x11.cpp:1545
  #16 0x01cb64b7 in QWidget::create (this=this@entry=0x9dd9760, 
window=window@entry=0, initializeWindow=initializeWindow@entry=true, 
destroyOldWindow=destroyOldWindow@entry=true) at kernel/qwidget.cpp:1545
  #17 0x01cb32a8 in QWidgetPrivate::createWinId (this=0xa37d450, 
winid=winid@entry=0) at kernel/qwidget.cpp:2578
  #18 0x01cb6c8c in QWidget::winId (this=this@entry=0x9dd9760) at 
kernel/qwidget.cpp:2536
  #19 0x0272500a in KDialog::setPlainCaption (this=this@entry=0x9dd9760, 
caption=...) at ../../kdeui/dialogs/kdialog.cpp:493
  #20 0x027242d0 in KDialogPrivate::init (this=this@entry=0xa37d5c8, 
q=q@entry=0x9dd9760) at ../../kdeui/dialogs/kdialog.cpp:181
  #21 0x027244c7 in KDialog::KDialog (this=0x9dd9760, parent=0x0, flags=...) at 
../../kdeui/dialogs/kdialog.cpp:192
  #22 0x02737fe6 in informationListWId (options=..., dontShowAgainName=..., 
caption=..., strlist=..., text=..., parent_id=0) at 
../../kdeui/dialogs/kmessagebox.cpp:987
  #23 KMessageBox::informationListWId (parent_id=0, text=..., strlist=..., 
caption=..., dontShowAgainName=..., options=...) at 
../../kdeui/dialogs/kmessagebox.cpp:979
  #24 0x0273831b in KMessageBox::informationList (parent=parent@entry=0x0, 
text=..., strlist=..., caption=..., dontShowAgainName=..., options=...) at 
../../kdeui/dialogs/kmessagebox.cpp:976
  #25 0x0273837e in KMessageBox::information (parent=0x0, 

[Desktop-packages] [Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.

2014-08-05 Thread Shih-Yuan Lee
** Description changed:

  If the maximum brightness is equal to or bigger than 100, it has higher
- possibility that zero is off. So adjusting the minimum brightness to 1
- to avoid the problem.
+ possibility that zero is off. So adjusting the minimum brightness to avoid 
the problem.
  
  Quotes from
  http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt
  
  This property controls the brightness on laptop panels and equivalent
   displays with a backlight controller. The driver specific maximum
   value MUST turn the backlight to full brightness, 1 SHOULD turn the
   backlight to minimum brightness, 0 SHOULD turn the backlight off.
  
  Quotes from http://msdn.microsoft.com/en-
  us/library/windows/hardware/ff569755(v=vs.85).aspx
  
  Brightness levels are represented as single-byte values in the range
   from zero to 100 where zero is off and 100 is the maximum brightness
   that a laptop computer supports. Every laptop computer must report a
   maximum brightness level of 100; however, a laptop computer is not
   required to support a level of zero. The only requirement for values
   from zero to 100 is that larger values must represent higher brightness
   levels.

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

Title:
  gnome-rr: Adjust the minimum brightness level when the maximum = 100.

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

Bug description:
  If the maximum brightness is equal to or bigger than 100, it has higher
  possibility that zero is off. So adjusting the minimum brightness to avoid 
the problem.

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

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

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

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

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

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


[Desktop-packages] [Bug 23267] Re: Default Hebrew fonts in Firefox are unreadable, ugly

2014-08-05 Thread Oded Arbel
@wissotzky: still I would prefer an out of the box solution.

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

Title:
  Default Hebrew fonts in Firefox are unreadable, ugly

Status in Ubuntu:
  Confirmed
Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  The default Hebrew fonts in firefox are unreadable and ugly,
  The default can be easily changed. suggestion:
  using the Hebrew font package Culmus, already in ubuntu,

  firefox settings:

  Proportional: Sans Serif Size(pixels) 16
  Serif   : FreeSans
  Sans-serif  : FreeSans
  Monospace   : Monospace  Size(pixels) 12

  Those values are based on feedback from a local (and the main) LUG
  www.whatsup.org.il

  Thanks in advance!
  (as a side note: most of the israeli users of FOSS seems to prefer english UI 
-
  changing the values only for 
  the locale will be - in ,my opinion - insufficient)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-08-05 Thread David Barth
Thanks for the feedback on this issue. I think that it confirms the bug.

We're quite busy with the Phone/RTM release though, so it may take us a
few weeks before we get back to that problem with a fix.

-- 
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 “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:
  [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 1304581] Re: Insecure directory in $ENV{PATH} while running with -T switch at /usr/bin/pg_ctlcluster line 255

2014-08-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1110181 ***
https://bugs.launchpad.net/bugs/1110181

** Summary changed:

- package postgresql-9.1 9.1.12-0ubuntu0.13.10 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
+ Insecure directory in $ENV{PATH} while running with -T switch at 
/usr/bin/pg_ctlcluster line 255

** Package changed: postgresql-9.1 (Ubuntu) = postgresql-common
(Ubuntu)

** This bug has been marked a duplicate of bug 1110181
   package postgresql-9.1 9.1.4-0ubuntu12.04 failed to install/upgrade: 
Insecure directory in $ENV{PATH} while running with -T switch at 
/usr/bin/pg_ctlcluster line 255

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

Title:
  Insecure directory in $ENV{PATH} while running with -T switch at
  /usr/bin/pg_ctlcluster line 255

Status in “postgresql-common” package in Ubuntu:
  New

Bug description:
  This package don't let me use apt-get in any way, this stops the
  proces

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: postgresql-9.1 9.1.12-0ubuntu0.13.10
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  AptOrdering:
   postgresql-9.1: Install
   postgresql-9.1: Configure
   postgresql-contrib-9.1: Configure
  Architecture: i386
  Date: Tue Apr  8 12:54:32 2014
  DpkgHistoryLog:
   Start-Date: 2014-04-08  12:54:22
   Commandline: apt-get -f install
   Upgrade: postgresql-9.1:i386 (9.1.12-0ubuntu0.13.10, 9.1.13-0ubuntu0.13.10)
  DuplicateSignature: package:postgresql-9.1:9.1.12-0ubuntu0.13.10:el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2012-11-23 (500 days ago)
  InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.12-0ubuntu0.13.10 failed to 
install/upgrade: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  UpgradeStatus: Upgraded to saucy on 2014-01-30 (67 days ago)

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

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


[Desktop-packages] [Bug 1305711] Re: package postgresql-9.1 9.1.11-0ubuntu0.13.04 failed to install/upgrade: tentative de remplacement de « /usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz », qui

2014-08-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1043449 ***
https://bugs.launchpad.net/bugs/1043449

** This bug has been marked a duplicate of bug 1043449
   package postgresql-client-9.1 9.1.5-1 failed to install/upgrade: trying to 
overwrite '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is 
also in package postgresql-9.1 9.1.5-0ubuntu12.04

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

Title:
  package postgresql-9.1 9.1.11-0ubuntu0.13.04 failed to
  install/upgrade: tentative de remplacement de «
  /usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz », qui
  appartient aussi au paquet postgresql-client-9.1 9.1.11-0ubuntu0.13.04

Status in “postgresql-9.1” package in Ubuntu:
  New

Bug description:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: postgresql-9.1 9.1.11-0ubuntu0.13.04
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic i686
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: i386
  Date: Thu Apr 10 10:53:28 2014
  DuplicateSignature: package:postgresql-9.1:9.1.11-0ubuntu0.13.04:tentative de 
remplacement de « /usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz », qui 
appartient aussi au paquet postgresql-client-9.1 9.1.11-0ubuntu0.13.04
  ErrorMessage: tentative de remplacement de « 
/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz », qui appartient aussi 
au paquet postgresql-client-9.1 9.1.11-0ubuntu0.13.04
  InstallationDate: Installed on 2013-11-04 (156 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.11-0ubuntu0.13.04 failed to 
install/upgrade: tentative de remplacement de « 
/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz », qui appartient aussi 
au paquet postgresql-client-9.1 9.1.11-0ubuntu0.13.04
  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/1305711/+subscriptions

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


[Desktop-packages] [Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.

2014-08-05 Thread Shih-Yuan Lee
I revised my patches to make the brightness minimum level more consistent than 
previous implementation.
Now it needs to patch gnome-desktop3, gnome-settings-daemon and 
unity-settings-daemon.
I will update my patches to the upstream bug afterward.

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

Title:
  gnome-rr: Adjust the minimum brightness level when the maximum = 100.

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

Bug description:
  If the maximum brightness is equal to or bigger than 100, it has higher
  possibility that zero is off. So adjusting the minimum brightness to avoid 
the problem.

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

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

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

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

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

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


[Desktop-packages] [Bug 1293596] [NEW] package postgresql-client-9.3 9.3.3-1bzr2 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurüc

2014-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This problem occured due an upgrade from 12.04LTS to 14.04LTS.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: postgresql-client-9.3 9.3.3-1bzr2
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
Uname: Linux 3.2.0-60-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Mon Mar 17 14:58:14 2014
DuplicateSignature: package:postgresql-client-9.3:9.3.3-1bzr2:ErrorMessage: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
ErrorMessage: ErrorMessage: Unterprozess installiertes post-installation-Skript 
gab den Fehlerwert 2 zurück
InstallationDate: Installed on 2012-12-27 (444 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 
(20120424.1)
SourcePackage: postgresql-9.3
Title: package postgresql-client-9.3 9.3.3-1bzr2 failed to install/upgrade: 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
UpgradeStatus: Upgraded to trusty on 2014-03-17 (0 days ago)

** Affects: postgresql-common (Ubuntu)
 Importance: Undecided
 Status: Triaged


** Tags: amd64 apport-package trusty
-- 
package postgresql-client-9.3 9.3.3-1bzr2 failed to install/upgrade: 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
https://bugs.launchpad.net/bugs/1293596
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to postgresql-common in Ubuntu.

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


[Desktop-packages] [Bug 1313588] Re: package postgresql-9.1 9.1.13-0ubuntu0.12.04 failed to install/upgrade: tentata sovrascrittura di /usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz presente

2014-08-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1270597 ***
https://bugs.launchpad.net/bugs/1270597

** This bug has been marked a duplicate of bug 1270597
   package postgresql-client-9.3 9.3.2-1ubuntu1 failed to upgrade: alternative 
pg_basebackup.1.gz can't be slave of psql.1.gz

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

Title:
  package postgresql-9.1 9.1.13-0ubuntu0.12.04 failed to
  install/upgrade: tentata sovrascrittura di
  /usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz presente anche
  nel pacchetto postgresql-client-9.1 9.1.12-0ubuntu0.13.10

Status in “postgresql-9.1” package in Ubuntu:
  New

Bug description:
  borg@borg:~$ sudo gedit /etc/apt/sources.list
  [sudo] password for borg: 

  (gedit:15604): IBUS-WARNING **: The owner of
  /home/borg/.config/ibus/bus is not root!

  (gedit:15604): Gtk-WARNING **: Calling Inhibit failed:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  (gedit:15604): Gtk-WARNING **: Calling Inhibit failed: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  borg@borg:~$ sudo gedit /etc/apt/sources.list

  (gedit:15687): IBUS-WARNING **: The owner of
  /home/borg/.config/ibus/bus is not root!

  (gedit:15687): Gtk-WARNING **: Calling Inhibit failed:
  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SessionManager was not provided by any .service files

  (gedit:15687): Gtk-WARNING **: Calling Inhibit failed: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  borg@borg:~$ sudo apt-get update
  Ign http://it.archive.ubuntu.com precise InRelease
  Ign http://it.archive.ubuntu.com precise-updates InRelease
 
  Ign http://archive.canonical.com trusty InRelease 
 
  Scaricamento di:1 http://it.archive.ubuntu.com precise Release.gpg [198 B]
 
  Scaricamento di:2 http://it.archive.ubuntu.com precise-updates Release.gpg 
[198 B]
  Trovato http://archive.canonical.com trusty Release.gpg   
 
  Scaricamento di:3 http://it.archive.ubuntu.com precise Release [49,6 kB]  
 
  Trovato http://archive.canonical.com trusty Release   
 
  Scaricamento di:4 http://it.archive.ubuntu.com precise-updates Release [49,6 
kB]
  Ign http://security.ubuntu.com precise-security InRelease 
 
  Scaricamento di:5 http://it.archive.ubuntu.com precise/main Sources [934 kB]  
 
  Trovato http://archive.canonical.com trusty/partner i386 Packages 
 
  Scaricamento di:6 http://security.ubuntu.com precise-security Release.gpg 
[198 B]
  Scaricamento di:7 http://security.ubuntu.com precise-security Release [49,6 
kB]
  Scaricamento di:8 http://it.archive.ubuntu.com precise/universe Sources [5019 
kB]
  Scaricamento di:9 http://security.ubuntu.com precise-security/main Sources 
[103 kB]
  Ign http://archive.canonical.com trusty/partner Translation-it_IT 
 
  Ign http://archive.canonical.com trusty/partner Translation-it
 
  Ign http://archive.canonical.com trusty/partner Translation-en
 
  Scaricamento di:10 http://security.ubuntu.com precise-security/universe 
Sources [30,9 kB]
  Scaricamento di:11 http://security.ubuntu.com precise-security/restricted 
Sources [2494 B]
  Scaricamento di:12 http://security.ubuntu.com precise-security/multiverse 
Sources [1797 B]
  Scaricamento di:13 http://security.ubuntu.com precise-security/main i386 
Packages [405 kB]
  Scaricamento di:14 http://security.ubuntu.com precise-security/universe i386 
Packages [96,6 kB]
  Scaricamento di:15 http://it.archive.ubuntu.com precise/restricted Sources 
[5470 B]
  Scaricamento di:16 http://it.archive.ubuntu.com precise/multiverse Sources 
[155 kB]
  Scaricamento di:17 http://it.archive.ubuntu.com precise/main i386 Packages 
[1274 kB]
  Scaricamento di:18 http://security.ubuntu.com precise-security/restricted 
i386 Packages [4620 B]
  Scaricamento di:19 http://security.ubuntu.com precise-security/multiverse 
i386 Packages [2649 B]
  Scaricamento di:20 http://it.archive.ubuntu.com precise/universe i386 
Packages [4796 kB]
  Scaricamento di:21 http://security.ubuntu.com precise-security/main 
Translation-en [177 kB]
  Scaricamento di:22 http://security.ubuntu.com precise-security/multiverse 
Translation-en [1299 B]
  Scaricamento di:23 http://security.ubuntu.com precise-security/restricted 
Translation-en [1253 B]
  Scaricamento di:24 http://security.ubuntu.com precise-security/universe 
Translation-en [56,7 kB]
  Scaricamento di:25 http://it.archive.ubuntu.com precise/restricted i386 
Packages [8431 B]
  Scaricamento di:26 http://it.archive.ubuntu.com 

[Desktop-packages] [Bug 1093241] Re: can't install new software, seems to be because: package postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade: trying to overwrite '/usr/share/postgresql/9.1/

2014-08-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1270597 ***
https://bugs.launchpad.net/bugs/1270597

** This bug is no longer a duplicate of bug 1089674
   package postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade: trying to 
overwrite '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is 
also in package postgresql-client-9.1 9.1.6-1~precise2
** This bug has been marked a duplicate of bug 1270597
   package postgresql-client-9.3 9.3.2-1ubuntu1 failed to upgrade: alternative 
pg_basebackup.1.gz can't be slave of psql.1.gz

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

Title:
  can't install new software, seems to be because: package
  postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade: trying to
  overwrite '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz',
  which is also in package postgresql-client-9.1 9.1.6-1~precise2

Status in “postgresql-9.1” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  Can't install new software, something seems to be wrong with postgres

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.6-1~precise2
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15.1
  Architecture: amd64
  Date: Fri Dec 21 07:26:53 2012
  DuplicateSignature:
   Unpacking replacement postgresql-9.1 ...
   dpkg: error processing 
/var/cache/apt/archives/postgresql-9.1_9.1.7-0ubuntu12.04_amd64.deb (--unpack):
trying to overwrite 
'/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is also in 
package postgresql-client-9.1 9.1.6-1~precise2
  ErrorMessage: trying to overwrite 
'/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is also in 
package postgresql-client-9.1 9.1.6-1~precise2
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade: 
trying to overwrite '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', 
which is also in package postgresql-client-9.1 9.1.6-1~precise2
  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/1093241/+subscriptions

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


[Desktop-packages] [Bug 1089674] Re: package postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade: trying to overwrite '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is also in pa

2014-08-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1270597 ***
https://bugs.launchpad.net/bugs/1270597

** This bug has been marked a duplicate of bug 1270597
   package postgresql-client-9.3 9.3.2-1ubuntu1 failed to upgrade: alternative 
pg_basebackup.1.gz can't be slave of psql.1.gz

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

Title:
  package postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade:
  trying to overwrite
  '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is also
  in package postgresql-client-9.1 9.1.6-1~precise2

Status in “postgresql-9.1” package in Ubuntu:
  Confirmed

Bug description:
  Error occured during the running of 'apt-get upgrade' after running
  'apt-get update'

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.6-1~precise2
  ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34
  Uname: Linux 3.2.0-35-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17
  Architecture: amd64
  Date: Thu Dec 13 09:42:54 2012
  DuplicateSignature:
   Unpacking replacement postgresql-9.1 ...
   dpkg: error processing 
/var/cache/apt/archives/postgresql-9.1_9.1.7-0ubuntu12.04_amd64.deb (--unpack):
trying to overwrite 
'/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is also in 
package postgresql-client-9.1 9.1.6-1~precise2
  ErrorMessage: trying to overwrite 
'/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', which is also in 
package postgresql-client-9.1 9.1.6-1~precise2
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.6-1~precise2 failed to install/upgrade: 
trying to overwrite '/usr/share/postgresql/9.1/man/man1/pg_basebackup.1.gz', 
which is also in package postgresql-client-9.1 9.1.6-1~precise2
  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/1089674/+subscriptions

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


[Desktop-packages] [Bug 1352805] [NEW] please merge ibus from debian

2014-08-05 Thread LocutusOfBorg
Public bug reported:

Would be nice to have at least 1.5.8 for utopic, because of the many fixes in 
the new release
debdiff attached

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

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

Title:
  please merge ibus from debian

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Would be nice to have at least 1.5.8 for utopic, because of the many fixes in 
the new release
  debdiff attached

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

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


[Desktop-packages] [Bug 1352805] Re: please merge ibus from debian

2014-08-05 Thread LocutusOfBorg
** Attachment added: debdiff
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1352805/+attachment/4170206/+files/debdiff

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

Title:
  please merge ibus from debian

Status in “ibus” package in Ubuntu:
  New

Bug description:
  Would be nice to have at least 1.5.8 for utopic, because of the many fixes in 
the new release
  debdiff attached

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

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


[Desktop-packages] [Bug 1323064] Re: package postgresql-9.1 9.1.11-0ubuntu0.12.04 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2014-08-05 Thread Martin Pitt
*** This bug is a duplicate of bug 1110181 ***
https://bugs.launchpad.net/bugs/1110181

** This bug has been marked a duplicate of bug 1110181
   package postgresql-9.1 9.1.4-0ubuntu12.04 failed to install/upgrade: 
Insecure directory in $ENV{PATH} while running with -T switch at 
/usr/bin/pg_ctlcluster line 255

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

Title:
  package postgresql-9.1 9.1.11-0ubuntu0.12.04 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in “postgresql-9.1” package in Ubuntu:
  New

Bug description:
  I don't know anything about the bug, but it keeps poping up.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.11-0ubuntu0.12.04
  ProcVersionSignature: Ubuntu 3.8.0-39.58~precise1-generic 3.8.13.20
  Uname: Linux 3.8.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sat May 24 10:20:03 2014
  DuplicateSignature: package:postgresql-9.1:9.1.11-0ubuntu0.12.04:subprocess 
new pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.11-0ubuntu0.12.04 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1303095] Re: package postgresql-9.1 9.1.12-0ubuntu0.12.04 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2014-08-05 Thread Martin Pitt
 Error: Could not create log file
/var/log/postgresql/postgresql-9.1-main.log

Please give me the output of

  sudo ls -ld /var/log /var/log/postgresql
  sudo ls -l /var/log/postgresql/

Thanks!

** Changed in: postgresql-9.1 (Ubuntu)
   Status: Confirmed = Incomplete

** Summary changed:

- package postgresql-9.1 9.1.12-0ubuntu0.12.04 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 1
+ failed to install/upgrade: Could not create log file 
/var/log/postgresql/postgresql-9.1-main.log

** Package changed: postgresql-9.1 (Ubuntu) = postgresql-common
(Ubuntu)

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

Title:
  failed to install/upgrade: Could not create log file
  /var/log/postgresql/postgresql-9.1-main.log

Status in “postgresql-common” package in Ubuntu:
  Incomplete

Bug description:
  package postgresql-9.1 9.1.12-0ubuntu0.12.04 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: postgresql-9.1 9.1.12-0ubuntu0.12.04
  ProcVersionSignature: Ubuntu 3.8.0-38.56~precise1-generic 3.8.13.19
  Uname: Linux 3.8.0-38-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  AptOrdering:
   postgresql-9.1: Install
   postgresql-9.1: Configure
   postgresql-contrib-9.1: Configure
  Architecture: amd64
  Date: Sat Apr  5 18:44:54 2014
  DpkgHistoryLog:
   Start-Date: 2014-04-05  18:44:50
   Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.54'
   Upgrade: postgresql-9.1:amd64 (9.1.12-0ubuntu0.12.04, 9.1.13-0ubuntu0.12.04)
  DuplicateSignature: package:postgresql-9.1:9.1.12-0ubuntu0.12.04:subprocess 
new pre-removal script returned error exit status 1
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  MarkForUpload: True
  SourcePackage: postgresql-9.1
  Title: package postgresql-9.1 9.1.12-0ubuntu0.12.04 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1312530] Re: Use of uninitialized value $info{pgdata} in -d at /usr/bin/pg_ctlcluster line 354

2014-08-05 Thread Martin Pitt
** Summary changed:

- package postgresql-9.1 9.1.11-0ubuntu0.13.10 failed to install/upgrade: 
подпроцесс новый сценарий pre-removal возвратил код ошибки 1
+ Use of uninitialized value $info{pgdata} in -d at /usr/bin/pg_ctlcluster 
line 354

** Package changed: postgresql-9.1 (Ubuntu) = postgresql-common
(Ubuntu)

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

Title:
  Use of uninitialized value $info{pgdata} in -d at
  /usr/bin/pg_ctlcluster line 354

Status in “postgresql-common” package in Ubuntu:
  New

Bug description:
  sudo apt-get upgrade
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  Пакеты, которые будут оставлены в неизменном виде:
linux-headers-lowlatency linux-image-lowlatency linux-lowlatency
  Пакеты, которые будут обновлены:
chromium-codecs-ffmpeg-extra google-chrome-stable linux-libc-dev
postgresql-9.1 postgresql-client-9.1
  обновлено 5, установлено 0 новых пакетов, для удаления отмечено 0 пакетов, и 
3 пакетов не обновлено.
  Необходимо скачать 50,1 MB/53,3 MB архивов.
  После данной операции, объём занятого дискового пространства уменьшится на 
552 kB.
  Хотите продолжить [Д/н]? y
  Получено:1 http://dl.google.com/linux/chrome/deb/ stable/main 
google-chrome-stable amd64 34.0.1847.132-1 [48,3 MB]
  Получено:2 http://archive.ubuntu.com/ubuntu/ saucy-updates/universe 
chromium-codecs-ffmpeg-extra amd64 34.0.1847.116-0ubuntu~1.13.10.0~pkg991 [868 
kB]
  Получено:3 http://archive.ubuntu.com/ubuntu/ saucy-updates/main 
linux-libc-dev amd64 3.11.0-20.34 [963 kB]
  Получено 50,1 MБ за 1мин 55с (435 kБ/c)   
 
  (Чтение базы данных … на данный момент установлено 358538 файлов и каталогов.)
  Подготовка к замене пакета chromium-codecs-ffmpeg-extra 
33.0.1750.152-0ubuntu0.13.10.1~pkg984.1 (используется файл 
…/chromium-codecs-ffmpeg-extra_34.0.1847.116-0ubuntu~1.13.10.0~pkg991_amd64.deb)
 …
  Распаковывается замена для пакета chromium-codecs-ffmpeg-extra …
  Подготовка к замене пакета google-chrome-stable 34.0.1847.116-1 (используется 
файл …/google-chrome-stable_34.0.1847.132-1_amd64.deb) …
  Распаковывается замена для пакета google-chrome-stable …
  Подготовка к замене пакета linux-libc-dev:amd64 3.11.0-19.33 (используется 
файл …/linux-libc-dev_3.11.0-20.34_amd64.deb) …
  Распаковывается замена для пакета linux-libc-dev:amd64 …
  Подготовка к замене пакета postgresql-9.1 9.1.11-0ubuntu0.13.10 (используется 
файл …/postgresql-9.1_9.1.13-0ubuntu0.13.10_amd64.deb) …
   * Stopping PostgreSQL 9.1 database server
   * Use of uninitialized value $info{pgdata} in -d at /usr/bin/pg_ctlcluster 
line 354.
  Use of uninitialized value $info{pgdata} in concatenation (.) or string at 
/usr/bin/pg_ctlcluster line 355.
  Error:  is not accessible or does not exist
   
[fail]
  invoke-rc.d: initscript postgresql, action stop failed.
  dpkg: предупреждение: подпроцесс старый сценарий pre-removal возвратил код 
ошибки 1
  dpkg: попытка использовать сценарий из нового пакета …
   * Stopping PostgreSQL 9.1 database server
   * Use of uninitialized value $info{pgdata} in -d at /usr/bin/pg_ctlcluster 
line 354.
  Use of uninitialized value $info{pgdata} in concatenation (.) or string at 
/usr/bin/pg_ctlcluster line 355.
  Error:  is not accessible or does not exist
   
[fail]
  invoke-rc.d: initscript postgresql, action stop failed.
  dpkg: ошибка при обработке параметра 
/var/cache/apt/archives/postgresql-9.1_9.1.13-0ubuntu0.13.10_amd64.deb 
(--unpack):
   подпроцесс новый сценарий pre-removal возвратил код ошибки 1
  dpkg: рассматривается перевод postgresql-9.1 в ненастроенное состояние, 
который был бы сломан установка postgresql-client-9.1 …
  dpkg: да, postgresql-9.1 будет переведён в ненастроенное состояние (сломан 
из-за postgresql-client-9.1)
  Подготовка к замене пакета postgresql-client-9.1 9.1.11-0ubuntu0.13.10 
(используется файл …/postgresql-client-9.1_9.1.13-0ubuntu0.13.10_amd64.deb) …
  Деконфигурация postgresql-9.1 …
   * Stopping PostgreSQL 9.1 database server
   * Use of uninitialized value $info{pgdata} in -d at /usr/bin/pg_ctlcluster 
line 354.
  Use of uninitialized value $info{pgdata} in concatenation (.) or string at 
/usr/bin/pg_ctlcluster line 355.
  Error:  is not accessible or does not exist
   
[fail]
  invoke-rc.d: initscript postgresql, action stop failed.
  dpkg: ошибка при обработке параметра 
/var/cache/apt/archives/postgresql-client-9.1_9.1.13-0ubuntu0.13.10_amd64.deb 
(--unpack):
   подпроцесс установлен сценарий 

[Desktop-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font

2014-08-05 Thread Iain Lane
It was because I had $LANGUAGE set. Now it's--

laney@iota LANG=zh_TW.UTF-8 fc-match -s sans-serif | head -5
DroidSansFallbackFull.ttf: Droid Sans Regular
DroidSans.ttf: Droid Sans Regular
DroidNaskh-Regular.ttf: Droid Sans Regular
DroidSansEthiopic-Regular.ttf: Droid Sans Regular
DroidSansHebrew-Regular.ttf: Droid Sans Regular

is that right? If not, what should it be?

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

Title:
  Configuration of the Droid Sans Fallback font

Status in “fonts-android” package in Ubuntu:
  In Progress
Status in “language-selector” package in Ubuntu:
  In Progress
Status in “fonts-android” source package in Trusty:
  Triaged
Status in “language-selector” source package in Trusty:
  Triaged

Bug description:
  There are currently several open issues related to the use of Droid
  Sans Fallback for rendering Chinese content:

  * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid
Sans fonts
https://launchpad.net/bugs/1334495

  * Droid Sans no longer preferred font for Chinese
https://launchpad.net/bugs/1335482

  * Chinese in Ubuntu Touch should use Heiti style sans serif font
https://launchpad.net/bugs/1346766

  Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a
  bunch of fonts, of which only one is needed for Chinese. In an attempt
  to sort things out I have built the fonts-android source package in my
  PPA with the DroidSansFallbackFull.ttf font broken out to a separate
  binary package named fonts-droid-cjk. The PPA also includes a version
  of language-selector where the changes in version 0.129.2 have been
  reverted.

  To test it in Trusty, you should:

  * Uninstall the fonts-droid package

  * Install fonts-droid-cjk and language-selector-common from my PPA
at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test

  My own tests indicate that the change to language-selector due to bug
  #1335482 was a step in the wrong direction. With
  DroidSansFallbackFull.ttf as the only installed font from the Droid
  Sans family, you get rid of possible confusion that might have
  resulted in the issue reported in that bug.

  $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5
  DroidSansFallbackFull.ttf: Droid Sans Fallback Regular
  uming.ttc: AR PL UMing CN Light
  uming.ttc: AR PL UMing HK Light
  ukai.ttc: AR PL UKai CN Book
  DejaVuSans.ttf: DejaVu Sans Book

  Also, if we would take this route, it might be easier to fix a
  configuration that makes Droid Sans Fallback work well with qt apps.
  (This is pure theory/hope so far.)

  Looking forward to your comments.

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

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


[Desktop-packages] [Bug 1020043] Re: show postmaster stderr on startup failure

2014-08-05 Thread Martin Pitt
** No longer affects: postgresql-9.1 (Ubuntu)

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

Title:
  show postmaster stderr on startup failure

Status in “postgresql-common” package in Ubuntu:
  Triaged

Bug description:
  The following output can be observed under various configurations (for
  example: disk full, but there are other conditions )

  /etc/init.d/postgresql start
   * Starting PostgreSQL 9.1 database server
   * The PostgreSQL server failed to start. Please check the log output.
 ...fail!

  
  Now, take the case were the disk is full, this means that there isn't any log 
output, which means that the error message is extremely bad. 

  To make things worse, IIRC, the Ubuntu scripts throw away stderr which
  means that even if postgresql returns a correct error message, that it
  is simply thrown away by default.

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

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


[Desktop-packages] [Bug 1056869] Re: Make libpq multi-arch capable

2014-08-05 Thread Martin Pitt
Fixed in utopic.

** Package changed: postgresql-9.1 (Ubuntu) = postgresql-9.4 (Ubuntu)

** Changed in: postgresql-9.4 (Ubuntu)
   Status: Triaged = Fix Released

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

Title:
  Make libpq multi-arch capable

Status in “postgresql-9.4” package in Ubuntu:
  Fix Released
Status in “postgresql-9.1” package in Debian:
  Fix Released

Bug description:
  This cameup whilst system upgrade.Upgrade FROM 11 10 TO 12.04

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libpq5 9.1.6-0ubuntu12.04
  ProcVersionSignature: Ubuntu 3.0.0-25.41-generic 3.0.40
  Uname: Linux 3.0.0-25-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Wed Sep 26 08:32:59 2012
  DuplicateSignature:
   Unpacking libusb-0.1-4:i386 (from .../libusb-0.1-4_2%3a0.1.12-20_i386.deb) 
...
   Selecting previously unselected package perl-base:i386.
   dpkg: error processing 
/var/cache/apt/archives/perl-base_5.14.2-6ubuntu2.1_i386.deb (--unpack):
perl-base:i386 5.14.2-6ubuntu2.1 (Multi-Arch: no) is not co-installable 
with perl-base:amd64 5.14.2-6ubuntu2.1 (Multi-Arch: no) which is currently 
installed
  ErrorMessage: libpq5:i386 9.1.6-0ubuntu12.04 (Multi-Arch
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: postgresql-9.1
  Title: package libpq5 9.1.6-0ubuntu12.04 failed to install/upgrade: 
libpq5:i386 9.1.6-0ubuntu12.04 (Multi-Arch
  UpgradeStatus: Upgraded to precise on 2012-09-25 (0 days ago)

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

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


[Desktop-packages] [Bug 1351262] Re: precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~)'

2014-08-05 Thread Jean-Baptiste Lallement
** Changed in: xorg-lts-transitional (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  precise alternate installations fail with unmet deps due to the
  conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (=
  0~)'

Status in “xorg-lts-transitional” package in Ubuntu:
  New

Bug description:
  Precise alternate preseeded installations fail with unmet deps due to
  the following:

  Jul 31 08:54:29 in-target: The following information may help to resolve the 
situation:
  Jul 31 08:54:29 in-target: 
  Jul 31 08:54:29 in-target: The following packages have unmet dependencies:
  Jul 31 08:54:29 in-target:  libgl1-mesa-dri-lts-trusty : Conflicts: 
libgl1-mesa-dri
  Jul 31 08:54:29 in-target:  libgl1-mesa-glx : Conflicts: libgl1
  Jul 31 08:54:29 in-target:  libgl1-mesa-glx-lts-trusty : Conflicts: libgl1
  Jul 31 08:54:29 in-target:   Conflicts: 
libgl1-mesa-glx
  Jul 31 08:54:29 in-target:  libglapi-mesa-lts-trusty : Conflicts: 
libglapi-mesa
  Jul 31 08:54:29 in-target:  xserver-xorg-lts-trusty : Conflicts: 
libgl1-mesa-dri (= 0~)
  Jul 31 08:54:29 in-target:Conflicts: 
libgl1-mesa-glx (= 0~)
  Jul 31 08:54:29 in-target:Conflicts: 
libglapi-mesa (= 0~)
  Jul 31 08:54:29 in-target: E
  Jul 31 08:54:29 in-target: : 
  Jul 31 08:54:29 in-target: Unable to correct problems, you have held broken 
packages.

  The d-i installs based on iso were broken until 20140731 due to kernel 
version mismatch between the archive and d-i. Therefore it's proving  very hard 
to find from our side when this was introduced. 
  This issue impacts both amd64 and i386 installations and the failing 
preseeded install logs can be found:

  https://jenkins.qa.ubuntu.com/job/precise-alternate-i386_default/
  https://jenkins.qa.ubuntu.com/job/precise-alternate-amd64_default/

  The installer syslog is attached.

  The preseed being used for this install is:
  
http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-precise/view/head:/preseeds-common/base

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

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


[Desktop-packages] [Bug 1293596] Re: package postgresql-client-9.3 9.3.3-1bzr2 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

2014-08-05 Thread Martin Pitt
Thanks! Fixed in bzr.

** Package changed: postgresql-9.3 (Ubuntu) = postgresql-common
(Ubuntu)

** Changed in: postgresql-common (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: postgresql-common (Ubuntu)
   Status: Triaged = Fix Committed

** Summary changed:

- package postgresql-client-9.3 9.3.3-1bzr2 failed to install/upgrade: 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
+ update-alternatives parsing failure under non-English locales

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

Title:
  update-alternatives parsing failure under non-English locales

Status in “postgresql-common” package in Ubuntu:
  Fix Committed

Bug description:
  This problem occured due an upgrade from 12.04LTS to 14.04LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: postgresql-client-9.3 9.3.3-1bzr2
  ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
  Uname: Linux 3.2.0-60-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 17 14:58:14 2014
  DuplicateSignature: package:postgresql-client-9.3:9.3.3-1bzr2:ErrorMessage: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
  ErrorMessage: ErrorMessage: Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 2 zurück
  InstallationDate: Installed on 2012-12-27 (444 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 
(20120424.1)
  SourcePackage: postgresql-9.3
  Title: package postgresql-client-9.3 9.3.3-1bzr2 failed to install/upgrade: 
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
  UpgradeStatus: Upgraded to trusty on 2014-03-17 (0 days ago)

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

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


[Desktop-packages] [Bug 1352809] [NEW] /usr/bin/lp on Trusty using -h option doesn't work as expected

2014-08-05 Thread Michael Cunningham
Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
- About Ubuntu

Description:Ubuntu 14.04 LTS
Release:14.04
Codename:   trusty


2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center

cups-client:
  Installed: 1.7.2-0ubuntu1.1

3) What you expected to happen

When using lp -h to send a print job to a printer, I expected to the job
to be sent to the printer and to override any env variables set or conf
file setting

4) What happened instead

To summarise the behaviour I'm seeing

1) with CUPS_SERVER env variable unset and no ServerName set in 
/etc/cups/client.conf, we see that using lp -h with hostnames gives us error 
lp: Error - add '/version=1.1' to server name.
Using IPs sends the job to the printer as expected.

2) with CUPS_SERVER env variable set using hostname with/without port
and no ServerName set in /etc/cups/client.conf, we see that the only
time it sends a job is when an IP and port are used. Otherwise it seems
to error. I believe it's using the env variable, even though -h is being
used.

3) with CUPS_SERVER env variable set using IP address with/without port
and no ServerName set in /etc/cups/client.conf we see that the job is
always sent using lp -h but it is always sent to the value in env
variable, thus ignoring the command line.

===

with CUPS_SERVER env variable unset and no ServerName option set in
/etc/cups/client.conf

$ lp test2.txt
lp: Error - scheduler not responding. (expected as no server is set or 
specified)

Using hostname
$ lp -h server1:631 test2.txt
lp: Error - add '/version=1.1' to server name.

$ lp -h server1 test2.txt
lp: Error - add '/version=1.1' to server name.

Using IP address
$ lp -h 192.168.254.8 test2.txt
request id is PDF-54 (1 file(s))

$ lp -h 192.168.254.8:631 test2.txt
request id is PDF-55 (1 file(s))

===

With CUPS_SERVER env variable *set CUPS_SERVER=server1

$ lp test2.txt
lp: Error - add '/version=1.1' to server name.

Using hostname
$ lp -h server1 test2.txt
lp: Error - add '/version=1.1' to server name.

$ lp -h server1:631 test2.txt
lp: Error - add '/version=1.1' to server name.

Using IP address
$ lp -h 192.168.254.8 test2.txt
lp: Error - add '/version=1.1' to server name.

$ lp -h 192.168.254.8:631 test2.txt
request id is PDF-56 (1 file(s))

===

With CUPS_SERVER env variable *set CUPS_SERVER=server:631

Same results as above

===

With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8:631

$ lp -h 555.555.555.555 test2.txt
request id is PDF-66 (1 file(s))

===

With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8

Same results as above

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

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

Title:
  /usr/bin/lp on Trusty using -h option doesn't work as expected

Status in “cups” package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System - About Ubuntu

  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  cups-client:
Installed: 1.7.2-0ubuntu1.1

  3) What you expected to happen

  When using lp -h to send a print job to a printer, I expected to the
  job to be sent to the printer and to override any env variables set or
  conf file setting

  4) What happened instead

  To summarise the behaviour I'm seeing

  1) with CUPS_SERVER env variable unset and no ServerName set in 
/etc/cups/client.conf, we see that using lp -h with hostnames gives us error 
lp: Error - add '/version=1.1' to server name.
  Using IPs sends the job to the printer as expected.

  2) with CUPS_SERVER env variable set using hostname with/without port
  and no ServerName set in /etc/cups/client.conf, we see that the only
  time it sends a job is when an IP and port are used. Otherwise it
  seems to error. I believe it's using the env variable, even though -h
  is being used.

  3) with CUPS_SERVER env variable set using IP address with/without
  port and no ServerName set in /etc/cups/client.conf we see that the
  job is always sent using lp -h but it is always sent to the value in
  env variable, thus ignoring the command line.

  ===

  with CUPS_SERVER env variable unset and no ServerName option set in
  /etc/cups/client.conf

  $ lp test2.txt
  lp: Error - scheduler not responding. (expected as no server is set or 
specified)

  Using hostname
  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  request id is PDF-54 (1 file(s))

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-55 (1 

[Desktop-packages] [Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.

2014-08-05 Thread Shih-Yuan Lee
** Bug watch added: GNOME Bug Tracker #734267
   https://bugzilla.gnome.org/show_bug.cgi?id=734267

** Also affects: gnome-settings-daemon via
   https://bugzilla.gnome.org/show_bug.cgi?id=734267
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-rr: Adjust the minimum brightness level when the maximum = 100.

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

Bug description:
  If the maximum brightness is equal to or bigger than 100, it has higher
  possibility that zero is off. So adjusting the minimum brightness to avoid 
the problem.

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

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

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

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

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

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


[Desktop-packages] [Bug 1329227] Re: pg_createcluster crashes when a username or group is specified that contains digits

2014-08-05 Thread Martin Pitt
Thanks! Applied in bzr.

** Changed in: postgresql-common (Ubuntu)
   Status: New = Fix Committed

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

Title:
  pg_createcluster crashes when a username or group is specified that
  contains digits

Status in “postgresql-common” package in Ubuntu:
  Fix Committed

Bug description:
  pg_createcluster accepts options --user and --group to specify under
  which credentials a new database cluster should be created. According
  to the manual page, one may specify either a name or a UID/GID (as
  digits).

  The implementation, however, tests whether there is a digit in the
  given string, not whether the entire string consists of digits. This
  causes problems for me: I have a development system where each
  developer creates databases and such per ticket. Users and groups are
  created for this purpose, named ticketNNN where NNN is the number of
  the ticket that the developer has been given to implement or bug fix.
  But pg_createcluster does not like these user and group names, for
  example ticket123: it thinks I specified a UID/GID instead of a
  name, and does the wrong thing. It crashes later on when tries to use
  the string as a number. This is what it says on my Precise system
  specifically:

  Argument ticket123 isn't numeric in getpwuid at 
/usr/share/postgresql-common/PgCommon.pm line 790.
  Argument ticket123 isn't numeric in scalar assignment at 
/usr/share/postgresql-common/PgCommon.pm line 796.
  Argument ticket123 isn't numeric in numeric ne (!=) at 
/usr/share/postgresql-common/PgCommon.pm line 799.

  This is because the test on line 237 of pg_createcluster:
  $owneruid = (getpwnam $owneruid)[2] unless $owneruid =~ /\d+/;
  is testing the wrong thing. I think it should read:
  $owneruid = (getpwnam $owneruid)[2] unless $owneruid =~ /^\d+$/;

  The same happens a few lines down with the group name.

  My Ubuntu version information:
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  I'm using postgresql-common version 129ubuntu1.

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

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


[Desktop-packages] [Bug 1330055] Re: /usr/bin/psql misinterprets cluster version in ~/.postgresqlrc

2014-08-05 Thread Martin Pitt
** Changed in: postgresql-common (Ubuntu)
   Status: New = Triaged

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

Title:
  /usr/bin/psql misinterprets cluster version in ~/.postgresqlrc

Status in “postgresql-common” package in Ubuntu:
  Triaged

Bug description:
  I've just upgraded a client from precise to trusty. As part of that
  upgrade, postgresql-client-9.1 was uninstalled and replaced with
  postgresql-client-9.3. This broke the psql client's access to
  databases that are listed in ~/.postgresqlrc as running version 9.1.
  If I run

  psql dbname

  I now get the following error:

  Error: /home/username/.postgresqlrc line 2: version 9.1 does not exist

  The relevant line of /home/username/.postgresqlrc looks like this:

  9.1dbhost:5432  dbname

  This is correct according to the documentation: the postgresqlrc(5)
  man page describes the VERSION column as The major PostgreSQL version
  *of the cluster to connect to* (emphasis mine). Note also the comment
  in /usr/share/postgresql-common/pg_wrapper that says:

  # for psql we always want the latest version, as this is backwards compatible
  # to every major version that that we support

  Unfortunately the flow of control never reaches that point in the
  code; user_cluster_map() (in PgCommon.pm) calls version_exists(9.1)
  and throws an error because *on the client* there is only version 9.3.
  The check is erroneous since it assumes that the client and the server
  have the same versions of PostgreSQL installed.

  I could lie to the wrapper and claim that the database cluster runs
  version 9.3, were it not for the fact that /home/username is on a
  network share and the same file needs to work for both precise and
  trusty (and wheezy) clients.

  This report is about Ubuntu 14.04 LTS, with version 154 of postgresql-
  client-common. I haven't researched whether any other releases are
  affected.

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

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


[Desktop-packages] [Bug 999191] Re: 10de:0421 X crashes with gnome-session: Fatal IO error 11

2014-08-05 Thread Christopher M. Penalver
somekool, thank you for your comment. Unfortunately, this bug report is not 
scoped to you, or your problem. So your hardware and problem may be tracked, 
could you please file a new report with Ubuntu by executing the following in a 
terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: 
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

Title:
  10de:0421 X crashes with gnome-session: Fatal IO error 11

Status in X.Org X server:
  New
Status in “nvidia-graphics-drivers” package in Ubuntu:
  Incomplete

Bug description:
  It started happening after upgrading to ubuntu 12.04. Several times a
  day, the gnome session crashes and drops me to GDM. This happens with
  Unity and gnome shell.

  Part of the syslog output:
  May 14 17:17:01  CRON[15229]: (root) CMD (   cd /  run-parts --report 
/etc/cron.hourly)
  May 14 17:23:20  gnome-session[11249]: Gdk-WARNING: gnome-session: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :2.#012
  May 14 17:23:20  acpid: client 11075[0:0] has disconnected
  May 14 17:23:20  acpid: client 11075[0:0] has disconnected
  May 14 17:23:20  acpid: client connected from 15281[0:0]
  May 14 17:23:20  acpid: 1 client rule loaded
  May 14 17:23:20  acpid: client connected from 15281[0:0]
  May 14 17:23:20  acpid: 1 client rule loaded

  WORKAROUND: Use unity-2d.

  WORKAROUND: Use nouveau drivers instead of nvidia.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic 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  295.40  Thu Apr  5 21:37:00 
PDT 2012
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,grid,imgpng,move,regex,snap,vpswitch,place,mousepoll,resize,wall,session,gnomecompat,unitymtgrabhandles,animation,fade,workarounds,expo,scale,unityshell]
  CompositorRunning: None
  Date: Mon May 14 17:29:32 2012
  DistUpgraded: 2012-05-02 17:37:43,892 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   blcr, 0.8.2: added
   nvidia-current, 295.40, 3.0.0-19-generic, x86_64: installed
   nvidia-current, 295.40, 3.2.0-24-generic, x86_64: installed
   virtualbox, 4.1.12, 3.0.0-19-generic, x86_64: installed
   virtualbox, 4.1.12, 3.2.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation G86 [GeForce 8500 GT] [10de:0421] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8264]
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  JockeyStatus:
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Enabled, In use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Disabled, Not in use)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=5ede402c-7f88-41a4-84ba-195045035b34 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to precise on 2012-05-02 (11 days ago)
  dmi.bios.date: 12/18/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SOX5810J.86A.3044.2008.1218.1457
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DX58SO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE29331-501
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSOX5810J.86A.3044.2008.1218.1457:bd12/18/2008:svn:pn:pvr:rvnIntelCorporation:rnDX58SO:rvrAAE29331-501:cvn:ct2:cvr:
  version.compiz: compiz 1:0.9.7.8-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu35
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Desktop-packages] [Bug 1340544] Re: gnome-rr: Adjust the minimum brightness level when the maximum = 100.

2014-08-05 Thread Bug Watch Updater
** Changed in: gnome-settings-daemon
   Status: Unknown = New

** Changed in: gnome-settings-daemon
   Importance: Unknown = Medium

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

Title:
  gnome-rr: Adjust the minimum brightness level when the maximum = 100.

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

Bug description:
  If the maximum brightness is equal to or bigger than 100, it has higher
  possibility that zero is off. So adjusting the minimum brightness to avoid 
the problem.

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

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

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

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

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

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


[Desktop-packages] [Bug 1033533] Re: Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with SW rendering

2014-08-05 Thread Adolfo Jayme
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Milestone: quantal-updates = None

** No longer affects: xserver-xorg-video-nouveau (Ubuntu Quantal)

** No longer affects: xserver-xorg-video-nouveau (Ubuntu Raring)

** Changed in: xserver-xorg-video-nouveau (Ubuntu Trusty)
   Status: Confirmed = Triaged

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

Title:
  Xorg crashed with SIGABRT: exaMemcpyBox with src=0x0 on nouveau with
  SW rendering

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged
Status in “xserver-xorg-video-nouveau” source package in Trusty:
  Triaged

Bug description:
  [Errors Bucket]
  
https://errors.ubuntu.com/bucket/?id=/usr/bin/Xorg:6:memcpy:exaMemcpyBox:exaCopyDirty:exaCopyDirtyToSys:exaPrepareAccessReg_mixed

  Crash doing memcpy in EXA on nouveau, with software rendering
  activated.

  #8  signal handler called
  No symbol table info available.
  #9  __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:72
  No locals.
  #10 0x7f570e63684e in memcpy (__len=23, __src=0x0, __dest=0x7f5713877100) 
at /usr/include/x86_64-linux-gnu/bits/string3.h:52
  No locals.
  #11 exaMemcpyBox (pbox=pbox@entry=0x7fffef000de0, src=0x0, src_pitch=64, 
dst=0x7f5713877100 , dst_pitch=24, pPixmap=error reading variable: Unhandled 
dwarf expression opcode 0xfa) at ../../exa/exa_migration_classic.c:59
  i = 16
  cpp = optimized out
  bytes = 23
  #12 0x7f570e636d03 in exaCopyDirty (migrate=migrate@entry=0x7fffef000e40, 
pValidDst=0x7f5713dc3e40, pValidSrc=0x7f5713dc3e50, transfer=0x7f570f28b7f0 
nouveau_exa_download_from_screen, fallback_index=fallback_index@entry=1, 
sync=0x7f570e635780 exaWaitSync) at ../../exa/exa_migration_classic.c:240
  pPixmap = 0x7f5713dc3da0
  pExaPixmap = 0x7f5713dc3e00
  damage = optimized out
  CopyReg = {extents = {x1 = 0, y1 = 0, x2 = 23, y2 = 16}, data = 0x0}
  save_use_gpu_copy = 1
  save_pitch = 64
  pBox = 0x7fffef000de0
  nbox = 1
  access_prepared = 1
  need_sync = 0
  #13 0x7f570e636f32 in exaCopyDirtyToSys 
(migrate=migrate@entry=0x7fffef000e40) at ../../exa/exa_migration_classic.c:285
  pPixmap = optimized out
  pExaScr = 0x7f5713877100
  pExaPixmap = 0x0
  #14 0x7f570e63951a in exaPrepareAccessReg_mixed (pPixmap=0x7f5713dc3da0, 
index=optimized out, pReg=0x0) at ../../exa/exa_migration_mixed.c:254
  as_dst = 1
  pixmaps = {{as_dst = 0, as_src = 1, pPix = 0x7f5713dc3da0, pReg = 
0x0}}
  pExaPixmap = 0x7f5713dc3e00
  has_gpu_copy = optimized out
  success = optimized out

  [Original Report]
  The crash report started immediately after login.

  ProblemType: CrashDistroRelease: Ubuntu 12.10
  Package: xserver-xorg-core 2:1.12.99.902-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
  Uname: Linux 3.5.0-8-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.4-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  Date: Sun Aug  5 14:46:44 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.18, 3.5.0-6-generic, x86_64: installed
   virtualbox, 4.1.18, 3.5.0-8-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 400] [10de:03d2] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: NVIDIA Corporation Device [10de:cb84]
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120519)
  Lsusb:
   Bus 001 Device 002: ID 18ec:3399 Arkmicro Technologies Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  ProcCmdline: /usr/bin/X :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 
-novtswitch -background none
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-8-generic 
root=UUID=a80eff25-65c3-4db0-adad-31d8ea95823b ro quiet splash vt.handoff=7
  Renderer: Software
  Signal: 6SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 09/22/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: NF-MCP61
  dmi.chassis.type: 3
  dmi.modalias: 

[Desktop-packages] [Bug 1319870] Re: Removable media is being mounted randomly in multiseat systems

2014-08-05 Thread Martin Pitt
This is fixed in utopic, udisks2 uses logind now.

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

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

Title:
  Removable media is being mounted randomly in multiseat systems

Status in “udisks2” package in Ubuntu:
  Fix Released

Bug description:
  Due to lack of full systemd-logind integration in current udisks2
  package, automounting of removable media in multiseat setups is not
  respecting seat hierarchy. All seats try to mount it at the same time,
  resulting in a race condition. However, the expected behaviour is that
  only the right seat (i.e. the seat whose USB port the removable media
  is plugged in) should be able to mount it.

  To solve this problem, just rebuild package udisks2 with additional
  build-dependencies libsystemd-login-dev and libsystemd-daemon-dev.

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

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


[Desktop-packages] [Bug 1325729] [NEW] apport NUMBER view-report option causes ProblemType python crash

2014-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

While instructed to send some apport data for another bug, apport
crashed when I tried to view the report.

% dpkg -l apport

apport   2.14.1-0ubuntu3.2

% apport-collect 1325713

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
dpkg-query: no packages found matching linux
.

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (408.2 KB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): V
Traceback (most recent call last):
  File /usr/bin/apport-cli, line 370, in module
if not app.run_argv():
  File /usr/lib/python2.7/dist-packages/apport/ui.py, line 652, in run_argv
return self.run_update_report()
  File /usr/lib/python2.7/dist-packages/apport/ui.py, line 568, in 
run_update_report
response = self.ui_present_report_details(allowed_to_report)
  File /usr/bin/apport-cli, line 209, in ui_present_report_details
self.collect_info()
  File /usr/lib/python2.7/dist-packages/apport/ui.py, line 966, in 
collect_info
if self.report['ProblemType'] == 'Crash':
  File /usr/lib/python2.7/UserDict.py, line 23, in __getitem__
raise KeyError(key)
KeyError: 'ProblemType'

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

-- 
apport NUMBER view-report option causes ProblemType python crash
https://bugs.launchpad.net/bugs/1325729
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to apport in Ubuntu.

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


[Desktop-packages] [Bug 1352821] [NEW] 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

2014-08-05 Thread bala
Public bug reported:

Hi,

Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi
working fine. pls help to provide the solution

Vendor ID : 0489:e078
Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 

Regds,
Bala S

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

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

Title:
  0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

Status in “udisks2” package in Ubuntu:
  New

Bug description:
  Hi,

  Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi
  working fine. pls help to provide the solution

  Vendor ID : 0489:e078
  Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 

  Regds,
  Bala S

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

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


[Desktop-packages] [Bug 1327371] Re: package python3-gi 3.4.0-1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 134

2014-08-05 Thread Martin Pitt
This is coming from dh_python3's autogenerated pyclean call:

Preparing to replace python3-gi 3.4.0-1 (using 
.../python3-gi_3.4.0-1ubuntu0.1_amd64.deb) ...
Fatal Python error: Py_Initialize: Unable to get the locale encoding
EOFError: EOF read where not expected

Can you please give the output of locale?

** Package changed: pygobject (Ubuntu) = python3.4 (Ubuntu)

** Changed in: python3.4 (Ubuntu)
   Status: New = Incomplete

** Summary changed:

- package python3-gi 3.4.0-1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 134
+ package python3-gi 3.4.0-1 failed to install/upgrade: pyclean: Py_Initialize: 
Unable to get the locale encoding

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

Title:
  package python3-gi 3.4.0-1 failed to install/upgrade: pyclean:
  Py_Initialize: Unable to get the locale encoding

Status in “python3.4” package in Ubuntu:
  Incomplete

Bug description:
  occur on openning the software centre

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: python3-gi 3.4.0-1ubuntu0.1
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Thu Jun  5 18:53:22 2014
  ErrorMessage: subprocess new pre-removal script returned error exit status 134
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  SourcePackage: pygobject
  Title: package python3-gi 3.4.0-1 failed to install/upgrade: subprocess new 
pre-removal script returned error exit status 134
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1327371/+subscriptions

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


[Desktop-packages] [Bug 1352821] Re: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

2014-08-05 Thread bala
Hi,

LSPCI and LSUSB details attached .


Regds,
Bala S 

** Attachment added: lcpsi.jpg
   
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1352821/+attachment/4170212/+files/lcpsi.jpg

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

Title:
  0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

Status in “udisks2” package in Ubuntu:
  New

Bug description:
  Hi,

  Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi
  working fine. pls help to provide the solution

  Vendor ID : 0489:e078
  Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 

  Regds,
  Bala S

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

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


[Desktop-packages] [Bug 1281588] Re: Disk standby timer is broken

2014-08-05 Thread Martin Pitt
** Changed in: udisks2 (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  Disk standby timer is broken

Status in abstraction for enumerating and managing block devices:
  Confirmed
Status in “udisks2” package in Ubuntu:
  Triaged

Bug description:
  udisks' / gnome-disk-utility's support for the drive standby timer is
  broken.  If the standby timer is set to at least 10 minutes ( which is
  the minimum on many drives ), every 10 minutes udisks tries to update
  the smart status of the drive, which resets the standby timer.

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

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


[Desktop-packages] [Bug 1352821] Re: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

2014-08-05 Thread Martin Pitt
** Package changed: udisks2 (Ubuntu) = bluez (Ubuntu)

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

Title:
  0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

Status in “bluez” package in Ubuntu:
  New

Bug description:
  Hi,

  Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi
  working fine. pls help to provide the solution

  Vendor ID : 0489:e078
  Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 

  Regds,
  Bala S

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

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


[Desktop-packages] [Bug 1319105] Re: Cisco AM10 no longer switches mode

2014-08-05 Thread Lars Melin
This may be a conflict with the storage driver, does it make any
difference if you remove the hashmark in front of  the
#SetStorageDelay=4

line of /etc/usb_modeswitch.conf ?

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

Title:
  Cisco AM10 no longer switches mode

Status in “usb-modeswitch” package in Ubuntu:
  New

Bug description:
  My Cisco AM10 valet connector WiFi adaptor

  This worked under Saucy but broke when I upgraded to Trusty.  I've
  attached usb_modeswitch.log obtained from turning debugging on.

  From before the upgrade, I didn't ever run in debugging mode but
  syslog entries looked like:

  syslog.7.gz:May  7 10:08:34 nyantiger usb_modeswitch: switching device 
1307:1169 on 003/025
  syslog.7.gz:May  7 10:08:36 nyantiger usb_modeswitch: switched to 13b1:0031 
on 003/025

  Now there's just:

  syslog:May 13 10:37:24 nyantiger usb_modeswitch: switch device
  1307:1169 on 003/010

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue May 13 12:02:54 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (100 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to trusty on 2014-05-13 (0 days ago)
  mtime.conffile..etc.usb.modeswitch.conf: 2014-05-13T11:51:17.900534

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

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


[Desktop-packages] [Bug 1325729] Re: apport NUMBER view-report option causes ProblemType python crash

2014-08-05 Thread Martin Pitt
Fixed in trunk r2831.

** Project changed: apport = apport (Ubuntu)

** Changed in: apport (Ubuntu)
   Status: New = Fix Committed

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

Title:
  apport NUMBER view-report option causes ProblemType python crash

Status in “apport” package in Ubuntu:
  Fix Committed

Bug description:
  While instructed to send some apport data for another bug, apport
  crashed when I tried to view the report.

  % dpkg -l apport

  apport   2.14.1-0ubuntu3.2

  % apport-collect 1325713

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  dpkg-query: no packages found matching linux
  .

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (408.2 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): V
  Traceback (most recent call last):
File /usr/bin/apport-cli, line 370, in module
  if not app.run_argv():
File /usr/lib/python2.7/dist-packages/apport/ui.py, line 652, in run_argv
  return self.run_update_report()
File /usr/lib/python2.7/dist-packages/apport/ui.py, line 568, in 
run_update_report
  response = self.ui_present_report_details(allowed_to_report)
File /usr/bin/apport-cli, line 209, in ui_present_report_details
  self.collect_info()
File /usr/lib/python2.7/dist-packages/apport/ui.py, line 966, in 
collect_info
  if self.report['ProblemType'] == 'Crash':
File /usr/lib/python2.7/UserDict.py, line 23, in __getitem__
  raise KeyError(key)
  KeyError: 'ProblemType'

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

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


[Desktop-packages] [Bug 1313334] Re: Error Message: Unable to mount webConnect MG

2014-08-05 Thread Martin Pitt
What you see there sounds like the fake CD drive that 3G/4G sticks tend
to behave like until usb-modeswitch puts them into proper modem mode.
That CD drive usually has windows drivers, so it's totally useless and
unnessary under Ubuntu.

** Changed in: udisks2 (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  Error Message: Unable to mount webConnect MG

Status in “udisks2” package in Ubuntu:
  Invalid

Bug description:
  This is the error message:
  Unable to mount webConnect MG

  Error mounting /dev/sr1 at /media/felicia/webConnect Mg: Command-line `mount 
-t iso9660 -o 
uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500
 /dev/sr1 /media/felicia/webConnect Mg' exited with non-zero exit status 
32: mount: block device /dev/sr1 is write-protected, mounting read-only
  mount: special device /dev/sr1 does not exist

  Yes, it does mount but I don't understand why I keep getting the error
  message.

  The device is a 4G Rocket from T-Mobile for broadband access. It
  intermittently disconnects the broadband connection and I'm wondering
  if this is related to the error message above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udisks2 2.1.3-1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 27 09:01:25 2014
  HotplugNewDevices: /dev/sdb
  HotplugNewMounts: /dev/sr1 /media/felicia/webConnect\040Mg iso9660 
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500 
0 0
  InstallationDate: Installed on 2014-04-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. X55U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=6e30bde6-6b06-4b41-a7ef-90bec98a8300 ro quiet splash vt.handoff=7
  SourcePackage: udisks2
  Symptom: storage
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X55U.423
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X55U
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X55U
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Desktop-packages] [Bug 1352809] Re: /usr/bin/lp on Trusty using -h option doesn't work as expected

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

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

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

Title:
  /usr/bin/lp on Trusty using -h option doesn't work as expected

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System - About Ubuntu

  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  cups-client:
Installed: 1.7.2-0ubuntu1.1

  3) What you expected to happen

  When using lp -h to send a print job to a printer, I expected to the
  job to be sent to the printer and to override any env variables set or
  conf file setting

  4) What happened instead

  To summarise the behaviour I'm seeing

  1) with CUPS_SERVER env variable unset and no ServerName set in 
/etc/cups/client.conf, we see that using lp -h with hostnames gives us error 
lp: Error - add '/version=1.1' to server name.
  Using IPs sends the job to the printer as expected.

  2) with CUPS_SERVER env variable set using hostname with/without port
  and no ServerName set in /etc/cups/client.conf, we see that the only
  time it sends a job is when an IP and port are used. Otherwise it
  seems to error. I believe it's using the env variable, even though -h
  is being used.

  3) with CUPS_SERVER env variable set using IP address with/without
  port and no ServerName set in /etc/cups/client.conf we see that the
  job is always sent using lp -h but it is always sent to the value in
  env variable, thus ignoring the command line.

  ===

  with CUPS_SERVER env variable unset and no ServerName option set in
  /etc/cups/client.conf

  $ lp test2.txt
  lp: Error - scheduler not responding. (expected as no server is set or 
specified)

  Using hostname
  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  request id is PDF-54 (1 file(s))

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-55 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server1

  $ lp test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using hostname
  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-56 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server:631

  Same results as above

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8:631

  $ lp -h 555.555.555.555 test2.txt
  request id is PDF-66 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8

  Same results as above

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

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


[Desktop-packages] [Bug 1314787] Re: Memory leak

2014-08-05 Thread Timo Aaltonen
** Package changed: xorg (Ubuntu) = fglrx-installer (Ubuntu)

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

Title:
  Memory leak

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

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  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.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 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:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  

[Desktop-packages] [Bug 1351555] Re: Webapps don't integrating in Unity

2014-08-05 Thread David Barth
The bug is about functional issues wrt unity integation APIs. The
webapps do now open in their dedicated container in 14.04 LTS.

** Changed in: libunity-webapps (Ubuntu)
   Importance: Undecided = High

** Changed in: libunity-webapps
   Importance: Undecided = High

** Changed in: libunity-webapps
   Status: New = Confirmed

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

Title:
  Webapps don't integrating in Unity

Status in WebApps: libunity:
  Confirmed
Status in “libunity-webapps” package in Ubuntu:
  Confirmed

Bug description:
  Such list of tested webapps aren't making any Unity integration since 14.04:
  YouTube; vkcom; YandexMusic; GMail; lastfm

  Althoug they are working in 13.10 as expected.

  They no more openning in default browser, but they do in webbrowser-app, even 
when installed by default browser.
  It's both correct for firefox, chromium and opera(other user says)

  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  Codename: trusty

  Firefox version: 31.0

  Chromium version: Chromium 34.0.1847.116 Ubuntu 14.04 aura

  Opera: ???

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug  2 10:58:47 2014
  ExecutablePath: /usr/lib/libunity-webapps/unity-webapps-service
  SourcePackage: libunity-webapps
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libunity-webapps/+bug/1351555/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-08-05 Thread Timo Aaltonen
** No longer affects: xorg (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/1310489

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  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: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  

[Desktop-packages] [Bug 1296418] Re: Sandisk Sansa Clip Sport not defined.

2014-08-05 Thread Martin Pitt
Added upstream, thanks! http://cgit.freedesktop.org/media-player-
info/commit/?id=7bcf392c

** Changed in: media-player-info (Ubuntu)
   Status: New = Fix Committed

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

Title:
  Sandisk Sansa Clip Sport not defined.

Status in “media-player-info” package in Ubuntu:
  Fix Committed

Bug description:
  I would have submitted this upstream, but I don't have a bugzilla account.
  Output from udevadm info is attached.

  Maker: Sandisk
  Name: Sansa Clip Sport
  Supported formats: MP3, WMA (NO DRM), AAC, Ogg Vorbis, WAV, FLAC, and Audible 
(DRM only)
  Playlist formats: m3u
  Folder structure: /Audible/, /Audiobooks/, /Music/, and /Podcasts/.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: media-player-info 21-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Mar 23 16:08:33 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-22 (29 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140221)
  PackageArchitecture: all
  SourcePackage: media-player-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/media-player-info/+bug/1296418/+subscriptions

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


[Desktop-packages] [Bug 1351262] Re: precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~)'

2014-08-05 Thread Jean-Baptiste Lallement
Confirmed with ubuntu alternate 20140805

** Changed in: xorg-lts-transitional (Ubuntu)
   Status: New = Confirmed

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

Title:
  precise alternate installations fail with unmet deps due to the
  conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (=
  0~)'

Status in “xorg-lts-transitional” package in Ubuntu:
  Confirmed

Bug description:
  Precise alternate preseeded installations fail with unmet deps due to
  the following:

  Jul 31 08:54:29 in-target: The following information may help to resolve the 
situation:
  Jul 31 08:54:29 in-target: 
  Jul 31 08:54:29 in-target: The following packages have unmet dependencies:
  Jul 31 08:54:29 in-target:  libgl1-mesa-dri-lts-trusty : Conflicts: 
libgl1-mesa-dri
  Jul 31 08:54:29 in-target:  libgl1-mesa-glx : Conflicts: libgl1
  Jul 31 08:54:29 in-target:  libgl1-mesa-glx-lts-trusty : Conflicts: libgl1
  Jul 31 08:54:29 in-target:   Conflicts: 
libgl1-mesa-glx
  Jul 31 08:54:29 in-target:  libglapi-mesa-lts-trusty : Conflicts: 
libglapi-mesa
  Jul 31 08:54:29 in-target:  xserver-xorg-lts-trusty : Conflicts: 
libgl1-mesa-dri (= 0~)
  Jul 31 08:54:29 in-target:Conflicts: 
libgl1-mesa-glx (= 0~)
  Jul 31 08:54:29 in-target:Conflicts: 
libglapi-mesa (= 0~)
  Jul 31 08:54:29 in-target: E
  Jul 31 08:54:29 in-target: : 
  Jul 31 08:54:29 in-target: Unable to correct problems, you have held broken 
packages.

  The d-i installs based on iso were broken until 20140731 due to kernel 
version mismatch between the archive and d-i. Therefore it's proving  very hard 
to find from our side when this was introduced. 
  This issue impacts both amd64 and i386 installations and the failing 
preseeded install logs can be found:

  https://jenkins.qa.ubuntu.com/job/precise-alternate-i386_default/
  https://jenkins.qa.ubuntu.com/job/precise-alternate-amd64_default/

  The installer syslog is attached.

  The preseed being used for this install is:
  
http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-precise/view/head:/preseeds-common/base

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

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


[Desktop-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted

2014-08-05 Thread aminebend
** Changed in: accountsservice (Ubuntu)
 Assignee: (unassigned) = aminebend (alg-amine)

** Changed in: accountsservice (Ubuntu Precise)
 Assignee: (unassigned) = aminebend (alg-amine)

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

Title:
  segfault in accounts-daemon when logging in / gdm crash if user
  account is added or deleted

Status in “accountsservice” package in Ubuntu:
  Fix Released
Status in “accountsservice” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  libaccountsservice contains a double free which under certain circumstances 
will cause accounts-daemon to segfault, and under other circumstances will 
cause gdm to segfault when a user account is added or removed.

  [Test case]
  In a precise machine with kerberos authentication, adding a new user via 
sudo adduser test will cause an X session running under GDM to crash with a 
segfault.

  Once the patch is applied, running the same command line should not
  affect a running X session.  For the test to have value, the session
  needs to have been started after the new accountsservice packages were
  installed.

  [Possible regressions]
  This is just one line removing a double free that has been applied upstream 
for 16 months, so the code itself should be fine.  To be certain that 
everything is alright, not only gdm but also lightdm should be tested.

  [Original description]
  I noticed this in my logs. It's not obviously broken anything, but segfaults 
are bad so I thought it worth reporting.

  May 25 14:16:16 e102475-lin gdm-session-worker[2198]: 
AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so 
language not saved
  May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: 
segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in 
libc-2.15.so[7f$
  M
  ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  Package: accountsservice 0.6.15-2ubuntu9
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Tags: precise third-party-packages
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago)
  UserGroups: adm fuse sbuild sudo

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

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


[Desktop-packages] [Bug 1352495] Re: [HDA-Intel - HDA Intel PCH, recording] Clipped audio output added to mic recording when docked

2014-08-05 Thread Raymond
https://wiki.ubuntu.com/PulseAudio/Log

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

Title:
  [HDA-Intel - HDA Intel PCH, recording] Clipped audio output added to
  mic recording when docked

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Hi,

  I have a Lenovo X220 with an mini dock series 3 plus.  Ever since I
  have been using Ubuntu (originally 12.04 and more recently a clean
  14.04 install) I have issues with recording sound from the docking
  station.

  To elaborate plugging the devices in as follows works as expected:
  Mic into docking base
  Headset into laptops headset socket (a combined headset/mic socket)

  However when I connect both the headphones and the mic to the docking
  base a garbled representation of the output audio is mixed with the
  otherwise good quality input.

  I have tried to demonstrate this during the bug report process.  I had
  music playing during the sound recording tests.  During the first test
  the music playback stopped on its own and good quality sound was
  recorded.  During the second test music resumed and I talked over it
  at the end...  Hopefully this helps clarify my explanation.

  Alan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alan   2596 F pulseaudio
   /dev/snd/controlC0:  alan   2596 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Aug  4 18:52:04 2014
  InstallationDate: Installed on 2014-07-27 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: LifeCam Studio - Microsoft® LifeCam Studio(TM)
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: High background noise, or volume is too low
  Title: [HDA-Intel - HDA Intel PCH, recording] Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET65WW (1.35 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4287CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET65WW(1.35):bd10/03/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4287CTO
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


Re: [Desktop-packages] [Bug 1313334] Re: Error Message: Unable to mount webConnect MG

2014-08-05 Thread Felicia
Thank you for the update. Yes, I do get an icon that looks like a CD for
the stick. Is there a way to prevent the fake CD drive behavior?


On Tue, Aug 5, 2014 at 6:49 AM, Martin Pitt martin.p...@ubuntu.com wrote:

 What you see there sounds like the fake CD drive that 3G/4G sticks tend
 to behave like until usb-modeswitch puts them into proper modem mode.
 That CD drive usually has windows drivers, so it's totally useless and
 unnessary under Ubuntu.

 ** Changed in: udisks2 (Ubuntu)
Status: Confirmed = Invalid

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1313334

 Title:
   Error Message: Unable to mount webConnect MG

 Status in “udisks2” package in Ubuntu:
   Invalid

 Bug description:
   This is the error message:
   Unable to mount webConnect MG

   Error mounting /dev/sr1 at /media/felicia/webConnect Mg: Command-line
 `mount -t iso9660 -o
 uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500
 /dev/sr1 /media/felicia/webConnect Mg' exited with non-zero exit status
 32: mount: block device /dev/sr1 is write-protected, mounting read-only
   mount: special device /dev/sr1 does not exist

   Yes, it does mount but I don't understand why I keep getting the error
   message.

   The device is a 4G Rocket from T-Mobile for broadband access. It
   intermittently disconnects the broadband connection and I'm wondering
   if this is related to the error message above.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: udisks2 2.1.3-1
   ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
   Uname: Linux 3.13.0-24-generic x86_64
   ApportVersion: 2.14.1-0ubuntu3
   Architecture: amd64
   CurrentDesktop: Unity
   Date: Sun Apr 27 09:01:25 2014
   HotplugNewDevices: /dev/sdb
   HotplugNewMounts: /dev/sr1 /media/felicia/webConnect\040Mg iso9660
 ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500
 0 0
   InstallationDate: Installed on 2014-04-26 (0 days ago)
   InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64
 (20140417)
   MachineType: ASUSTeK COMPUTER INC. X55U
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
 root=UUID=6e30bde6-6b06-4b41-a7ef-90bec98a8300 ro quiet splash vt.handoff=7
   SourcePackage: udisks2
   Symptom: storage
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 08/06/2013
   dmi.bios.vendor: American Megatrends Inc.
   dmi.bios.version: X55U.423
   dmi.board.asset.tag: ATN12345678901234567
   dmi.board.name: X55U
   dmi.board.vendor: ASUSTeK COMPUTER INC.
   dmi.board.version: 1.0
   dmi.chassis.asset.tag: No Asset Tag
   dmi.chassis.type: 10
   dmi.chassis.vendor: ASUSTeK COMPUTER INC.
   dmi.chassis.version: 1.0
   dmi.modalias:
 dmi:bvnAmericanMegatrendsInc.:bvrX55U.423:bd08/06/2013:svnASUSTeKCOMPUTERINC.:pnX55U:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX55U:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
   dmi.product.name: X55U
   dmi.product.version: 1.0
   dmi.sys.vendor: ASUSTeK COMPUTER INC.

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1313334/+subscriptions



-- 


*Felicia James http://www.NotesToMySister.com*

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

Title:
  Error Message: Unable to mount webConnect MG

Status in “udisks2” package in Ubuntu:
  Invalid

Bug description:
  This is the error message:
  Unable to mount webConnect MG

  Error mounting /dev/sr1 at /media/felicia/webConnect Mg: Command-line `mount 
-t iso9660 -o 
uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500
 /dev/sr1 /media/felicia/webConnect Mg' exited with non-zero exit status 
32: mount: block device /dev/sr1 is write-protected, mounting read-only
  mount: special device /dev/sr1 does not exist

  Yes, it does mount but I don't understand why I keep getting the error
  message.

  The device is a 4G Rocket from T-Mobile for broadband access. It
  intermittently disconnects the broadband connection and I'm wondering
  if this is related to the error message above.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udisks2 2.1.3-1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 27 09:01:25 2014
  HotplugNewDevices: /dev/sdb
  HotplugNewMounts: /dev/sr1 /media/felicia/webConnect\040Mg iso9660 
ro,nosuid,nodev,relatime,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500 
0 0
  InstallationDate: Installed on 2014-04-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. X55U
  ProcKernelCmdLine: 

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

2014-08-05 Thread Maarten Lankhorst
** Changed in: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

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

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  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: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to 

[Desktop-packages] [Bug 1314787] Re: Memory leak

2014-08-05 Thread Maarten Lankhorst
If you get a worser problem with the updated network-manager-gnome, does
killing nm-applet free some of the leaked memory?

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

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

Title:
  Memory leak

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

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  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.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 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:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 

[Desktop-packages] [Bug 1351814] Re: manager crash: GLib-GObject-CRITICAL (ubutu 13)

2014-08-05 Thread Marius B. Kotsbak
Unfortunately Ubuntu 13.10 has reached end of life at 2014-07-17. You
should upgrade to 14.04 LTS and try again and then post a new error
message if the problem still persists.

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

Title:
  manager crash: GLib-GObject-CRITICAL (ubutu 13)

Status in Modem Manager Gui:
  Confirmed
Status in “modem-manager-gui” package in Ubuntu:
  Incomplete
Status in “modemmanager” package in Ubuntu:
  Invalid

Bug description:
  When I insert my modem (huawei e153u) the aplication is closed:

  The error on console:

  Module applicable: Modem Manager = 0.6.0/Wader (modmm_mm06.so)
  Module applicable: pppd = 2.4.5 (modcm_pppd245.so)
  Connection manager: pppd = 2.4.5
  Modem manager: Modem Manager = 0.6.0/Wader
  Device: huawei, E153, 11.609.18.00.279 [3] [44af59d16429bca0c4a77be00627e2d3]

  (modem-manager-gui:8350): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
  Device successfully opened
  Segmentation fault at address: 0x8
  Stack trace:
  1. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d]
  2. /lib/x86_64-linux-gnu/libc.so.6(+0xb8b5d) [0x7f597f77db5d]
  3. /lib/x86_64-linux-gnu/libc.so.6(strftime_l+0x16) [0x7f597f77f9a6]
  4. modem-manager-gui() [0x41b9e7]
  5. modem-manager-gui() [0x41f372]
  6. modem-manager-gui() [0x41f4f3]
  7. modem-manager-gui() [0x423abd]
  8. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x138) 
[0x7f59803c5188]
  9. /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x21b1d) [0x7f59803d6b1d]

  I use ubuntu 13.10

  thanks and sorry for my english.

  PD: the first time it works fine, but I restart the computer and not work 
more :/.
  --- 
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-06-02 (427 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  Package: modem-manager-gui 0.0.16-2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Tags:  saucy
  Uname: Linux 3.11.0-26-generic x86_64
  UpgradeStatus: Upgraded to saucy on 2014-08-01 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/modem-manager-gui/+bug/1351814/+subscriptions

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


Re: [Desktop-packages] [Bug 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder

2014-08-05 Thread Steve O
Thank you to all involved I appreciate the attention. Evolution is a big
part of my professional work flow

Cheers
On Aug 5, 2014 2:01 AM, Iain Lane i...@orangesquash.org.uk wrote:

 I uploaded evolution and evolution-data-server to trusty-proposed.
 They're waiting for review from the stable release update team. Watch
 this bug to know when you can test out the fix.

 Thanks for your feedback.

 --
 You received this bug notification because you are subscribed to a
 duplicate bug report (1297823).
 https://bugs.launchpad.net/bugs/1293144

 Title:
   evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
   creating new folder

 Status in The Evolution Mail  Calendaring Tool:
   Fix Released
 Status in “evolution” package in Ubuntu:
   Fix Released
 Status in “evolution-data-server” package in Ubuntu:
   Fix Released
 Status in “evolution” source package in Trusty:
   In Progress
 Status in “evolution-data-server” source package in Trusty:
   In Progress

 Bug description:
   [ Description ]

   (from upstream bug report, might not happen for everyone)

   - Open evolution
   - Go to mail view
   - Try to create a new folder

   Check evo crashes before  not after.

   I've also cherry-picked some related patches to make the created
   folder be displayed correctly. Check it doesn't have an expander.

   [ Development fix ]

   Same patches (disconnect the signals)

   [ Regression potential ]

   Check that folders are created and displayed properly, including cases
   that previously worked.

   [ Original description ]

   When I creates a new folder in Gmail the app closes.

   ProblemType: Crash
   DistroRelease: Ubuntu 14.04
   Package: evolution 3.10.4-0ubuntu1
   ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
   Uname: Linux 3.13.0-17-generic x86_64
   NonfreeKernelModules: wl
   ApportVersion: 2.13.3-0ubuntu1
   Architecture: amd64
   CrashCounter: 1
   CurrentDesktop: GNOME
   Date: Sun Mar 16 12:21:08 2014
   ExecutablePath: /usr/bin/evolution
   InstallationDate: Installed on 2014-03-13 (2 days ago)
   InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64
 (20140313)
   ProcCmdline: evolution
   SegvAnalysis:
Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
PC (0x7f88ad21b520) ok
source 0x18(%r14) (0x0468) not located in a known VMA region
 (needed readable region)!
destination %rdi ok
   SegvReason: reading NULL VMA
   Signal: 11
   SourcePackage: evolution
   StacktraceTop:
?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
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: evolution crashed with SIGSEGV in g_closure_invoke()
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

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


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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail  Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  In Progress
Status in “evolution-data-server” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before  not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov

[Desktop-packages] [Bug 1234634] Re: Data does not re-enable loss of reception

2014-08-05 Thread Martti Piirainen
I tested this on mako HW, image 172, with a WCDMA network simulator
(Anritsu MD8470A) where I can switch the simulated basestation on and
off. At least in this simulated scenario, the data connection always
comes back.

Some commented output from the monitor-ofono test script:
# base station out of reach
{NetworkRegistration} [/ril_0] Strength = 0
{ConnectionManager} [/ril_0] Attached = False
{ConnectionManager} [/ril_0] Bearer = none
{NetworkRegistration} [/ril_0] Status = searching
{NetworkOperator} [/ril_0/operator/00101] Status = available
{NetworkRegistration} [/ril_0] Name = 
{NetworkRegistration} [/ril_0] Status = searching
# data connection stops
{ConnectionContext} [/ril_0/context1] Settings = {}
{ConnectionContext} [/ril_0/context1] Active = False
{RadioSettings} [/ril_0] FastDormancy = True
{RadioSettings} [/ril_0] FastDormancy = False
{ConnectionManager} [/ril_0] Attached = True
{ConnectionManager} [/ril_0] Bearer = hspa
# base station is active again
{NetworkRegistration} [/ril_0] Status = registered
{NetworkRegistration} [/ril_0] Technology = umts
{NetworkRegistration} [/ril_0] LocationAreaCode = 128
{NetworkRegistration} [/ril_0] CellId = 0
{NetworkOperator} [/ril_0/operator/00101] Status = current
{NetworkRegistration} [/ril_0] Name = ANRITSU (Test PLMN 1-1)
{NetworkRegistration} [/ril_0] MobileCountryCode = 001
{NetworkRegistration} [/ril_0] MobileNetworkCode = 01
{NetworkRegistration} [/ril_0] Status = registered
{NetworkRegistration} [/ril_0] Strength = 0
{NetworkRegistration} [/ril_0] Strength = 67
# data context is active again
{ConnectionContext} [/ril_0/context1] Settings = { Address = 192.168.1.1, 
DomainNameServers = 192.168.1.2 192.168.1.2, Gateway = 192.168.1.2, Method = 
static, Interface = rmnet_usb0, Netmask = 255.255.255.0 }
{ConnectionContext} [/ril_0/context1] Active = True

Not necessarily 100% the same as real field testing, though.

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

Title:
  Data does not re-enable loss of reception

Status in “network-manager” package in Ubuntu:
  New
Status in “ofono” package in Ubuntu:
  Incomplete

Bug description:
  If i drive through an area that does not coverage with my mobile
  provider, when i re-enter an area that does have coverage my data
  connection/3G does not reconnect automatically. There is nothing i can
  do from the phone to re-enable it except reboot it, which in the long
  run is less than desirable operation.

  This has happened consistently from V72-V78 of the software.

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

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


[Desktop-packages] [Bug 1314787] Re: Memory leak

2014-08-05 Thread GVS
No, it does not release any of the memory used by Xorg, just the memory
used by NMG.  One can exit all open apps, and even kill many processes
and Xorg retains the leaked memory.

There is definitely some relation between the latest NMG update and the
Xorg memory leak.  I have since backracked to Network-manager-gnome
0.9.8.8-0ubuntu4.2 simply to have a usable system for more than a few
hours.

Note:  The memory leak, both before and after the NMG update begins as
soon as any network activity through either eth0 or wlan0 is initiated.
Prior to this any leak is minimal; after it, the leak is extreme.  Using
as app such as Glances etc., you can actually watch the megabytes leak
away every 2 - 5 seconds.

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

Title:
  Memory leak

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

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  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.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 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 

[Desktop-packages] [Bug 1314787] Re: Memory leak

2014-08-05 Thread GVS
To be clear (which the above was not):

The extreme memory leakage mentioned in the last paragraph above is of
course, AFTER the NMG update.  However, the leak before the NMG update
is still initiated by activity through the network interfaces, it is
just not anywhere near as extreme.

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

Title:
  Memory leak

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

Bug description:
  I upgraded my PC from Ubuntu 13.10 to 14.04 (released one). After
  upgrade I found the PC slows down soon even without apps running on
  it. When checking with system monitor I found all the physical memory
  was full and the swap file was in use (which never happened with
  13.10). I restarted the PC and left it alone. After six hours memory
  consumption of xorg went from original 250MB to 1,3GB. I guess there
  is a memory leak in the process.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr 30 23:05:47 2014
  DistUpgraded: 2014-04-26 21:44:20,660 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.11.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Device [1787:2291]
  InstallationDate: Installed on 2013-10-29 (183 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-20-generic 
root=UUID=a4de809d-e263-4318-8bf0-1bd1422076e3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (4 days ago)
  dmi.bios.date: 09/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N78 SE
  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.:bvr1105:bd09/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Apr 30 22:53:24 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:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   

[Desktop-packages] [Bug 1352450] [NEW] apport-retrace should indicate that -s and -o don't work together

2014-08-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

If you use apport-retrace with the -s switch (Write the new stack traces
to stdout instead of putting them back into the report) with the -o
switch (Write modified report to given file instead of changing the
original report) the -s switch will take precedence and the modified
report will not be created.  If you don't know this it can be quite
confusing as you'll end up looking for the report you passed with the -o
option and wonder where it went.

Either apport-retrace should warn you that -s takes precedence or it
should write to stdout and the given file.

** Affects: apport (Ubuntu)
 Importance: Low
 Status: Fix Committed

-- 
apport-retrace should indicate that -s and -o don't work together
https://bugs.launchpad.net/bugs/1352450
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to apport in Ubuntu.

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


[Desktop-packages] [Bug 1352450] Re: apport-retrace should indicate that -s and -o don't work together

2014-08-05 Thread Martin Pitt
Fixed in trunk r2833.

** Project changed: apport = apport (Ubuntu)

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

** Changed in: apport (Ubuntu)
   Status: New = Fix Committed

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  apport-retrace should indicate that -s and -o don't work together

Status in “apport” package in Ubuntu:
  Fix Committed

Bug description:
  If you use apport-retrace with the -s switch (Write the new stack
  traces to stdout instead of putting them back into the report) with
  the -o switch (Write modified report to given file instead of changing
  the original report) the -s switch will take precedence and the
  modified report will not be created.  If you don't know this it can be
  quite confusing as you'll end up looking for the report you passed
  with the -o option and wonder where it went.

  Either apport-retrace should warn you that -s takes precedence or it
  should write to stdout and the given file.

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

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


[Desktop-packages] [Bug 1352889] [NEW] Some Unity Autopilot tests are failing with constructor returned NULL

2014-08-05 Thread Christopher Townsend
Public bug reported:

Recently, some Unity 7 Autoppilot tests have begun failing with a
constructor returned NULL error.  The log indicates that the call to
Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
/dist-packages/autopilot/process/_bamf.py on line 334.

** Affects: autopilot
 Importance: Undecided
 Status: New

** Affects: unity
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: Confirmed

** Affects: autopilot-legacy (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: unity (Ubuntu)
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: Confirmed

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

** Summary changed:

- Some Unity Autopilot tests are failing with constructor returned NULL'
+ Some Unity Autopilot tests are failing with constructor returned NULL

** Description changed:

  Recently, some Unity 7 Autoppilot tests have begun failing with a
- constructor returned NULL' error.  The log indicates that the call to
+ constructor returned NULL error.  The log indicates that the call to
  Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
  /dist-packages/autopilot/process/_bamf.py on line 334.

** Changed in: unity
   Status: New = Confirmed

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

** Changed in: unity
   Importance: Undecided = High

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

** Changed in: unity
 Assignee: (unassigned) = Christopher Townsend (townsend)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) = Christopher Townsend (townsend)

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

Title:
  Some Unity Autopilot tests are failing with constructor returned
  NULL

Status in Autopilot:
  New
Status in Unity:
  Confirmed
Status in “autopilot-legacy” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Recently, some Unity 7 Autoppilot tests have begun failing with a
  constructor returned NULL error.  The log indicates that the call to
  Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
  /dist-packages/autopilot/process/_bamf.py on line 334.

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

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


[Desktop-packages] [Bug 1352889] Re: Some Unity Autopilot tests are failing with constructor returned NULL

2014-08-05 Thread Christopher Townsend
** Also affects: autopilot
   Importance: Undecided
   Status: New

** Also affects: autopilot-legacy (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Some Unity Autopilot tests are failing with constructor returned
  NULL

Status in Autopilot:
  In Progress
Status in Unity:
  Invalid
Status in “autopilot-legacy” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Recently, some Unity 7 Autoppilot tests have begun failing with a
  constructor returned NULL error.  The log indicates that the call to
  Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
  /dist-packages/autopilot/process/_bamf.py on line 334.

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

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


[Desktop-packages] [Bug 1352895] [NEW] Unity dash doesn't preview PDF if user Home is not in /home

2014-08-05 Thread Fabrizio Narni
Public bug reported:

Test case
===
1. Not having your Home directory under /home (in my case is under /encrypted)
2. Preview a PDF for Unity dash
3. Unity dash can't load the preview
Screenshot attached.

If the Home directory is in /home, everything works fine.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Aug  5 15:24:50 2014
InstallationDate: Installed on 2014-07-28 (8 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: Schermata da 2014-08-05 15:27:37.png
   
https://bugs.launchpad.net/bugs/1352895/+attachment/4170299/+files/Schermata%20da%202014-08-05%2015%3A27%3A37.png

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

Title:
  Unity dash doesn't preview PDF if user Home is not in /home

Status in “unity” package in Ubuntu:
  New

Bug description:
  Test case
  ===
  1. Not having your Home directory under /home (in my case is under /encrypted)
  2. Preview a PDF for Unity dash
  3. Unity dash can't load the preview
  Screenshot attached.

  If the Home directory is in /home, everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Aug  5 15:24:50 2014
  InstallationDate: Installed on 2014-07-28 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1352889] Re: Some Unity Autopilot tests are failing with constructor returned NULL

2014-08-05 Thread Christopher Townsend
** Changed in: unity
   Status: Confirmed = Invalid

** Changed in: autopilot
   Status: New = In Progress

** Changed in: autopilot-legacy (Ubuntu)
   Status: New = In Progress

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

** Changed in: autopilot
   Importance: Undecided = Critical

** Changed in: unity
   Importance: High = Critical

** Changed in: autopilot-legacy (Ubuntu)
   Importance: Undecided = Critical

** Changed in: unity (Ubuntu)
   Importance: High = Critical

** Description changed:

  Recently, some Unity 7 Autoppilot tests have begun failing with a
  constructor returned NULL error.  The log indicates that the call to
  Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
  /dist-packages/autopilot/process/_bamf.py on line 334.
+ 
+ This is causing close to 20 AP failures and is one issue blocking the
+ release of Unity.

** Changed in: unity
 Assignee: Christopher Townsend (townsend) = (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: Christopher Townsend (townsend) = (unassigned)

** Changed in: autopilot
 Assignee: (unassigned) = Christopher Townsend (townsend)

** Changed in: autopilot-legacy (Ubuntu)
 Assignee: (unassigned) = Christopher Townsend (townsend)

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

Title:
  Some Unity Autopilot tests are failing with constructor returned
  NULL

Status in Autopilot:
  In Progress
Status in Unity:
  Invalid
Status in “autopilot-legacy” package in Ubuntu:
  In Progress
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Recently, some Unity 7 Autoppilot tests have begun failing with a
  constructor returned NULL error.  The log indicates that the call to
  Gio.DesktopAppInfo.new(desktop_file) is failing in /usr/lib/python2.7
  /dist-packages/autopilot/process/_bamf.py on line 334.

  This is causing close to 20 AP failures and is one issue blocking the
  release of Unity.

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

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


[Desktop-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted

2014-08-05 Thread Ryan Tandy
** Changed in: accountsservice (Ubuntu)
 Assignee: aminebend (alg-amine) = (unassigned)

** Changed in: accountsservice (Ubuntu Precise)
 Assignee: aminebend (alg-amine) = (unassigned)

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

Title:
  segfault in accounts-daemon when logging in / gdm crash if user
  account is added or deleted

Status in “accountsservice” package in Ubuntu:
  Fix Released
Status in “accountsservice” source package in Precise:
  Fix Released

Bug description:
  [Impact]
  libaccountsservice contains a double free which under certain circumstances 
will cause accounts-daemon to segfault, and under other circumstances will 
cause gdm to segfault when a user account is added or removed.

  [Test case]
  In a precise machine with kerberos authentication, adding a new user via 
sudo adduser test will cause an X session running under GDM to crash with a 
segfault.

  Once the patch is applied, running the same command line should not
  affect a running X session.  For the test to have value, the session
  needs to have been started after the new accountsservice packages were
  installed.

  [Possible regressions]
  This is just one line removing a double free that has been applied upstream 
for 16 months, so the code itself should be fine.  To be certain that 
everything is alright, not only gdm but also lightdm should be tested.

  [Original description]
  I noticed this in my logs. It's not obviously broken anything, but segfaults 
are bad so I thought it worth reporting.

  May 25 14:16:16 e102475-lin gdm-session-worker[2198]: 
AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so 
language not saved
  May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: 
segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in 
libc-2.15.so[7f$
  M
  ---
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  Package: accountsservice 0.6.15-2ubuntu9
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Tags: precise third-party-packages
  Uname: Linux 3.2.0-24-generic x86_64
  UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago)
  UserGroups: adm fuse sbuild sudo

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

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


[Desktop-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.

2014-08-05 Thread pabouk
The behaviour is much better after patching but for example in VMware
Workstation (or Player) some problems persist:

When the keyboard is grabbed (mouse is in the window of a VM with VMware
Tools) and the keys (Super or Alt) are pressed nothing happens in Unity
as expected. But when the keyboard is ungrabbed (mouse leaves the
window) shortly after the keypress Unity behaves as if the key was
pressed again.

Test case:
1. In VMware Workstation (or Player) start a VM with VMware Tools installed.
2. Move the mouse cursor inside the window of the VM.
3. Press Super or Alt.
4. In less than 2 seconds move the mouse cursor outside of the window.
5. Nothing should happen in Unity but Unity actually behaves as if the key 
(Super or Alt) was pressed again.

It seems that there is a timeout for this behaviour. When the keyboard
is ungrabbed after more than approximately 3 seconds then nothing
happens in Unity as expected.

Alternative test case (does not require VMware Tools but is not so annoying.):
1. In VMware Workstation (or Player) start a VM.
2. Grab the keyboard in the VM (Ctrl+G or mouse click).
3. Press Alt. (Super does not demonstrate this problem completely in this 
variant.)
4. In less than 2 seconds ungrab the kyboard by pressing Ctrl+Alt.
5. Nothing should happen in Unity but Unity actually behaves as if the key 
(Alt) was pressed again. (With Super Dash only flashes shortly.)

...but since this problem does not show up when the VM is in full screen
mode then it seems that the bugfix in Unity behaves correctly as
described in this case.

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

Title:
  Unity/compiz intercepts Super and Alt keypresses from grabbed windows
  like VMs.

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Triaged
Status in Compiz Core:
  Triaged
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  Fix Released
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Confirmed
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  After upgrading from Maverick to Natty, I can no longer use the Super 
(windows) key in Virtual Machine Manager. Previously, as long as I had the 
Virtual Machine Manager console window in the foreground, I could press the 
Super key and the start menu would pop up. Since upgrading to Natty, this no 
longer works, and the search box appears in the upper left.

  Also see bug #934921

  [Test Case]
  (1) Install virtualbox or virt-manager and qemu-system, create and boot a 
virtual machine
  (2) while in the virtual machine (and it should grab the keyboard), press the 
Super key
  Expected Result: the super key acts inside the VM (check by install unity on 
it or using xev)
  Buggy Result: the super key acts in the host and the Unity Dash is displayed

  [regression Potential]This patch plays with key grabs and ungrabs:
  the most likely potential for regression is (a) the existing grabs
  continue and no fix obtains or (2) the grab is not resumed when
  returning control from the VM and the Super key does not invoke the
  Unity Dash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/741869/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-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-08-05 Thread Alberto Milone
** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: Confirmed = In Progress

-- 
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:
  In Progress

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  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: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot 

[Desktop-packages] [Bug 1295837] Re: keyboard doesnt work after hibernation lockscreen

2014-08-05 Thread Stefan H.
The bug I'm seeing must be
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1349128 . Not 100%
sure whether it is exactly the same as the initial reporter's here so I
won't mark it as a duplicate myself.

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

Title:
  keyboard doesnt work after hibernation lockscreen

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  when i open the lid to my laptop the keybaord doesnt work in the
  lockscreen unless i go up to the power cog and go to switch account
  then i can log back in just fine it only happens when my laptop lid
  has been shut for more then 5 mins... This is for ubuntu 14.04

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

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


[Desktop-packages] [Bug 1319105] Re: Cisco AM10 no longer switches mode

2014-08-05 Thread Jody McIntyre
I uncommented that line.  Still broken; same symptoms.

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

Title:
  Cisco AM10 no longer switches mode

Status in “usb-modeswitch” package in Ubuntu:
  New

Bug description:
  My Cisco AM10 valet connector WiFi adaptor

  This worked under Saucy but broke when I upgraded to Trusty.  I've
  attached usb_modeswitch.log obtained from turning debugging on.

  From before the upgrade, I didn't ever run in debugging mode but
  syslog entries looked like:

  syslog.7.gz:May  7 10:08:34 nyantiger usb_modeswitch: switching device 
1307:1169 on 003/025
  syslog.7.gz:May  7 10:08:36 nyantiger usb_modeswitch: switched to 13b1:0031 
on 003/025

  Now there's just:

  syslog:May 13 10:37:24 nyantiger usb_modeswitch: switch device
  1307:1169 on 003/010

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue May 13 12:02:54 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (100 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to trusty on 2014-05-13 (0 days ago)
  mtime.conffile..etc.usb.modeswitch.conf: 2014-05-13T11:51:17.900534

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

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


[Desktop-packages] [Bug 1246683] Re: Middle button does not work for scrolling

2014-08-05 Thread HumanPlayer2
Benjamin Xiao, I just ried the script from T-send's post on my Carbon X1 
(Ubuntu Gnome, 14.04), and that made the trackpad buttons normal -- and gave me 
middle click to scroll! Yay!
Thank you T_send, and dalcde, and of course esrevinu!

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

Title:
  Middle button does not work for scrolling

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Incomplete

Bug description:
  With my Lenovo T440s laptop the Trackpad/Trackpoint laptop scrolling
  does not work when pressing middle button + moving the Trackpoint.
  evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/
  ). Middle button itself works fine for middle clicks just no
  scrolling.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  Uname: Linux 3.12.0-031200rc7-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct 31 12:36:14 2013
  InstallationDate: Installed on 2013-10-17 (13 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  MarkForUpload: True
  SourcePackage: xserver-xorg-input-evdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+subscriptions

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


[Desktop-packages] [Bug 1349128] Re: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators)

2014-08-05 Thread Christopher Townsend
** Changed in: unity (Ubuntu Trusty)
   Status: Confirmed = Fix Released

** Changed in: unity (Ubuntu)
   Status: Fix Released = In Progress

** Changed in: unity (Ubuntu Trusty)
   Importance: Undecided = Critical

** Changed in: unity (Ubuntu)
   Importance: High = Critical

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

Title:
  Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it
  back to the underlying window (until using indicators)

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress
Status in “unity” source package in Trusty:
  Fix Released

Bug description:
  After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on
  Trusty, the lockscreen sometimes fails to take the keyboard focus away
  from Chrome.

  This might happen if there's a text selection in Chrome, and also when
  resuming after suspend.

  It doesn't always happen, as this is a race condition, but it's easy
  to reproduce by selecting the location bar in Chrome and then locking
  the screen.

  Workaround: click on any indicator in the upper right corner, and
  close the menu. After that, keyboard input is sent to the lockscreen
  again.

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

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


[Desktop-packages] [Bug 1345992] Re: Xetex doesn't support SmallCaps when using system fonts

2014-08-05 Thread Evan Langlois
RESOLVED: When the TexGyre fonts install, they install a million
different formats.  Xetex will pick up the wrong ones.  I managed to
move the right one and get it working.  Some consistency would be nice,
but thats Linux's onme major flaw ... the wonderful thing about
standards is there are so many to choose from.


** Changed in: texlive-base (Ubuntu)
   Status: New = Invalid

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

Title:
  Xetex doesn't support SmallCaps when using system fonts

Status in “texlive-base” package in Ubuntu:
  Invalid

Bug description:
  OK, I mostly have tested this with the TexGyre fonts since they have
  TeX versions.  I've verified that the fonts have SmallCaps information
  in them (actually an OTF font, not TT, but this happens with TT, too).
  I can use the smallcaps from LibreOffice, Scribus, and the LuaTeX
  backend (except for 1 font that I've been tweaking that LuaTeX can't
  find and everything else can or I'd use LuaTeX).

  1 - When LyX's Document Settings-Fonts-Use Non-TeX Fonts is
  unchecked, I can set the given TeX fonts and SmallCaps is rendered
  correctly.

  2 - I check the same box and select the same fonts (Yes, I know it
  will now read the OTF and not the TEX files, but as I said, the
  information is present), and the SmallCaps goes away.  FontForge shows
  the information for smallcaps.

  3 - Checked with other fonts as well, and the only thing that works
  with the box checked when running XeTeX is setting the font to
  Default and I'm not sure which font its using.  LuaTeX will support
  SmallCaps on most of my fonts, including the same ones XeTeX fails on.

  I'm guessing the bug is in Xetex but I really have no clue.  Like I
  said, the fonts work everywhere else.

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

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


[Desktop-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font

2014-08-05 Thread Gunnar Hjalmarsson
Well, you get DroidSansFallbackFull.ttf first, which is good. That's
what I got previously too (see comment #10 of bug #1335482), and it was
the intention with

https://launchpad.net/ubuntu/+source/language-selector/0.129.2

However, after having tried various things back and forth, I don't get
that result any longer. Instead I get:

$ dpkg-query -W fonts-droid language-selector-common
fonts-droid 1:4.3-3ubuntu1
language-selector-common0.129.2
$ LANG=zh_TW.UTF-8 fc-match -s sans-serif | head -5
DroidSans.ttf: Droid Sans Regular
uming.ttc: AR PL UMing TW Light
uming.ttc: AR PL UMing HK Light
ukai.ttc: AR PL UKai TW Book
DejaVuSans.ttf: DejaVu Sans Book

I.e. approximately the same result as Cheng-Chia Tseng reported in
comment #9 of bug #1335482. And that's not good, since it leads to AR
PL UMing TW being used to render traditional Chinese contents instead
of Droid Sans Fallback.

So the result of the current configuration is unpredictable, and I'm
pretty sure by now that the culprit which causes this unpredictability
is 65-droid-sans-fonts.conf. The pending merge proposals should fix
that.

I also think that the merge proposals will both fix bug #1334495 and
make it possible to use fonts-droid in the phone.

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

Title:
  Configuration of the Droid Sans Fallback font

Status in “fonts-android” package in Ubuntu:
  In Progress
Status in “language-selector” package in Ubuntu:
  In Progress
Status in “fonts-android” source package in Trusty:
  Triaged
Status in “language-selector” source package in Trusty:
  Triaged

Bug description:
  There are currently several open issues related to the use of Droid
  Sans Fallback for rendering Chinese content:

  * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid
Sans fonts
https://launchpad.net/bugs/1334495

  * Droid Sans no longer preferred font for Chinese
https://launchpad.net/bugs/1335482

  * Chinese in Ubuntu Touch should use Heiti style sans serif font
https://launchpad.net/bugs/1346766

  Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a
  bunch of fonts, of which only one is needed for Chinese. In an attempt
  to sort things out I have built the fonts-android source package in my
  PPA with the DroidSansFallbackFull.ttf font broken out to a separate
  binary package named fonts-droid-cjk. The PPA also includes a version
  of language-selector where the changes in version 0.129.2 have been
  reverted.

  To test it in Trusty, you should:

  * Uninstall the fonts-droid package

  * Install fonts-droid-cjk and language-selector-common from my PPA
at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test

  My own tests indicate that the change to language-selector due to bug
  #1335482 was a step in the wrong direction. With
  DroidSansFallbackFull.ttf as the only installed font from the Droid
  Sans family, you get rid of possible confusion that might have
  resulted in the issue reported in that bug.

  $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5
  DroidSansFallbackFull.ttf: Droid Sans Fallback Regular
  uming.ttc: AR PL UMing CN Light
  uming.ttc: AR PL UMing HK Light
  ukai.ttc: AR PL UKai CN Book
  DejaVuSans.ttf: DejaVu Sans Book

  Also, if we would take this route, it might be easier to fix a
  configuration that makes Droid Sans Fallback work well with qt apps.
  (This is pure theory/hope so far.)

  Looking forward to your comments.

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

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


[Desktop-packages] [Bug 1352951] [NEW] nautilus crashed with SIGSEGV in g_slice_alloc()

2014-08-05 Thread Joel Pelaez Jorge
Public bug reported:

Nautilus crash when only download a torrent, no copying, deleting or
moving files.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu9.3
Uname: Linux 3.6.11 x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug  5 10:14:18 2014
ExecutablePath: /usr/bin/nautilus
ExecutableTimestamp: 1405434801
GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 
'permissions', 'octal_permissions', 'owner', 'mime_type', 'where']
InstallationDate: Installed on 2014-07-30 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
ProcCmdline: nautilus -n
ProcCwd: /home/joel
SegvAnalysis:
 Segfault happened at: 0x7fa82174c297 g_slice_alloc+167:  mov
(%rbx),%rax
 PC (0x7fa82174c297) ok
 source (%rbx) (0x00842552) not located in a known VMA region (needed 
readable region)!
 destination %rax ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_slice_alloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace trusty

** Information type changed from Private to Public

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

Title:
  nautilus crashed with SIGSEGV in g_slice_alloc()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Nautilus crash when only download a torrent, no copying, deleting or
  moving files.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  Uname: Linux 3.6.11 x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  5 10:14:18 2014
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1405434801
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 
'permissions', 'octal_permissions', 'owner', 'mime_type', 'where']
  InstallationDate: Installed on 2014-07-30 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  ProcCmdline: nautilus -n
  ProcCwd: /home/joel
  SegvAnalysis:
   Segfault happened at: 0x7fa82174c297 g_slice_alloc+167:mov
(%rbx),%rax
   PC (0x7fa82174c297) ok
   source (%rbx) (0x00842552) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_slice_alloc()
  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/nautilus/+bug/1352951/+subscriptions

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


[Desktop-packages] [Bug 1352963] [NEW] Evince incorrectly reports password-protected pdf

2014-08-05 Thread Thijs van Dijk
Public bug reported:

Steps to reproduce:
1) Download this PDF: 
https://secure.ikea.com/ms/nl_NL/TnC/IKEA-webwinkel-voorwaarden.pdf
2) Open it in evince.

If you try the same in acrobat reader (I only tried it on windows), it
opens just fine. So either this file isn't encrypted at all but evince
merely says it is, or, for reasons beyond my comprehension, the file is
encrypted, but the password is somehow embedded in the document itself.

Either way, the end result is a broken user experience for ubuntuers.

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

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

Title:
  Evince incorrectly reports password-protected pdf

Status in “evince” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1) Download this PDF: 
https://secure.ikea.com/ms/nl_NL/TnC/IKEA-webwinkel-voorwaarden.pdf
  2) Open it in evince.

  If you try the same in acrobat reader (I only tried it on windows), it
  opens just fine. So either this file isn't encrypted at all but evince
  merely says it is, or, for reasons beyond my comprehension, the file
  is encrypted, but the password is somehow embedded in the document
  itself.

  Either way, the end result is a broken user experience for ubuntuers.

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

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


[Desktop-packages] [Bug 1352971] [NEW] gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node: Assertion `data' failed.

2014-08-05 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gvfs-backends 1.20.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
AssertionMessage: gvfsd-afc: plist.c:194: plist_copy_node: Assertion `data' 
failed.
CurrentDesktop: Unity
Date: Tue Aug  5 17:33:46 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-afc
ExecutableTimestamp: 1406290678
InstallationDate: Installed on 2013-06-05 (426 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
ProcCwd: /
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 __assert_fail_base (fmt=0x7f5a97e648b0 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x7f5a982ce721 data, 
file=file@entry=0x7f5a982ce748 plist.c, line=line@entry=194, 
function=function@entry=0x7f5a982cead0 plist_copy_node) at assert.c:92
 __GI___assert_fail (assertion=0x7f5a982ce721 data, file=0x7f5a982ce748 
plist.c, line=194, function=0x7f5a982cead0 plist_copy_node) at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
Title: gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node: 
Assertion `data' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace third-party-packages utopic

** Information type changed from Private to Public

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

Title:
  gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node:
  Assertion `data' failed.

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gvfs-backends 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: gvfsd-afc: plist.c:194: plist_copy_node: Assertion `data' 
failed.
  CurrentDesktop: Unity
  Date: Tue Aug  5 17:33:46 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-afc
  ExecutableTimestamp: 1406290678
  InstallationDate: Installed on 2013-06-05 (426 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
  ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
  ProcCwd: /
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   __assert_fail_base (fmt=0x7f5a97e648b0 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x7f5a982ce721 data, 
file=file@entry=0x7f5a982ce748 plist.c, line=line@entry=194, 
function=function@entry=0x7f5a982cead0 plist_copy_node) at assert.c:92
   __GI___assert_fail (assertion=0x7f5a982ce721 data, file=0x7f5a982ce748 
plist.c, line=194, function=0x7f5a982cead0 plist_copy_node) at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
  Title: gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node: 
Assertion `data' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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


[Desktop-packages] [Bug 1352951] Re: nautilus crashed with SIGSEGV in g_slice_alloc()

2014-08-05 Thread Apport retracing service
*** This bug is a duplicate of bug 1161468 ***
https://bugs.launchpad.net/bugs/1161468

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 #1161468, 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/1352951/+attachment/4170386/+files/CoreDump.gz

** Attachment removed: Disassembly.txt
   
https://bugs.launchpad.net/bugs/1352951/+attachment/4170388/+files/Disassembly.txt

** Attachment removed: ProcMaps.txt
   
https://bugs.launchpad.net/bugs/1352951/+attachment/4170390/+files/ProcMaps.txt

** Attachment removed: ProcStatus.txt
   
https://bugs.launchpad.net/bugs/1352951/+attachment/4170391/+files/ProcStatus.txt

** Attachment removed: Registers.txt
   
https://bugs.launchpad.net/bugs/1352951/+attachment/4170392/+files/Registers.txt

** Attachment removed: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1352951/+attachment/4170393/+files/Stacktrace.txt

** Attachment removed: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1352951/+attachment/4170394/+files/ThreadStacktrace.txt

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

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

Title:
  nautilus crashed with SIGSEGV in g_slice_alloc()

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Nautilus crash when only download a torrent, no copying, deleting or
  moving files.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.3
  Uname: Linux 3.6.11 x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  5 10:14:18 2014
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1405434801
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'group', 
'permissions', 'octal_permissions', 'owner', 'mime_type', 'where']
  InstallationDate: Installed on 2014-07-30 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  ProcCmdline: nautilus -n
  ProcCwd: /home/joel
  SegvAnalysis:
   Segfault happened at: 0x7fa82174c297 g_slice_alloc+167:mov
(%rbx),%rax
   PC (0x7fa82174c297) ok
   source (%rbx) (0x00842552) not located in a known VMA region (needed 
readable region)!
   destination %rax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_type_create_instance () 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_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_slice_alloc()
  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/nautilus/+bug/1352951/+subscriptions

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


[Desktop-packages] [Bug 1352968] [NEW] upowerd crashed with SIGABRT in __assert_fail_base()

2014-08-05 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: upower 0.9.23-2ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
Date: Tue Aug  5 17:33:36 2014
ExecutablePath: /usr/lib/upower/upowerd
InstallationDate: Installed on 2013-06-05 (426 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:
 
Signal: 6
SourcePackage: upower
StacktraceTop:
 __assert_fail_base (fmt=0x7fe92e5da8b0 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x7fe92e826721 data, 
file=file@entry=0x7fe92e826748 plist.c, line=line@entry=194, 
function=function@entry=0x7fe92e826ad0 plist_copy_node) at assert.c:92
 __GI___assert_fail (assertion=0x7fe92e826721 data, file=0x7fe92e826748 
plist.c, line=194, function=0x7fe92e826ad0 plist_copy_node) at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
Title: upowerd crashed with SIGABRT in __assert_fail_base()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash need-amd64-retrace utopic

** Information type changed from Private to Public

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

Title:
  upowerd crashed with SIGABRT in __assert_fail_base()

Status in “upower” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Date: Tue Aug  5 17:33:36 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2013-06-05 (426 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  Signal: 6
  SourcePackage: upower
  StacktraceTop:
   __assert_fail_base (fmt=0x7fe92e5da8b0 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x7fe92e826721 data, 
file=file@entry=0x7fe92e826748 plist.c, line=line@entry=194, 
function=function@entry=0x7fe92e826ad0 plist_copy_node) at assert.c:92
   __GI___assert_fail (assertion=0x7fe92e826721 data, file=0x7fe92e826748 
plist.c, line=194, function=0x7fe92e826ad0 plist_copy_node) at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
  Title: upowerd crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1246683] Re: Middle button does not work for scrolling

2014-08-05 Thread Daniel Philipp
The script works for me too (T400s, Ubuntu 14.04), thanks T_send :))) I
tried a lot of other stuff to get it to work, nothing seemed to be
fixing the problem.

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

Title:
  Middle button does not work for scrolling

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Incomplete

Bug description:
  With my Lenovo T440s laptop the Trackpad/Trackpoint laptop scrolling
  does not work when pressing middle button + moving the Trackpoint.
  evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/
  ). Middle button itself works fine for middle clicks just no
  scrolling.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  Uname: Linux 3.12.0-031200rc7-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct 31 12:36:14 2013
  InstallationDate: Installed on 2013-10-17 (13 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  MarkForUpload: True
  SourcePackage: xserver-xorg-input-evdev
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+subscriptions

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


[Desktop-packages] [Bug 1247736] Update Released

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

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

Title:
  [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd

Status in “nvidia-cuda-toolkit” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “ocl-icd” package in Ubuntu:
  Invalid
Status in “nvidia-cuda-toolkit” source package in Trusty:
  Invalid
Status in “nvidia-graphics-drivers-304” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Fix Released
Status in “nvidia-graphics-drivers-340” source package in Trusty:
  Invalid
Status in “ocl-icd” source package in Trusty:
  Invalid

Bug description:
  [Impact]
  Users with proprietary Nvidia graphics drivers are unable to co-install CUDA 
and OpenCL applications.
  The patches in comment #21 and #22 backport the fix from Utopic and resolve 
this issue by allowing nvidia-opencl-icd-* (Nvidia's OpenCL ICD) to be 
co-installed with ocl-icd-libopencl1 (the generic OpenCL ICD loader).

  [SRU Verification Test Case #1]
  sudo apt-get remove nvidia-opencl-icd-* nvidia-libopencl1-* ocl-icd-ibopencl1

  sudo apt-get install nvidia-opencl-icd-331

  With the 331.38-0ubuntu7 drivers, the Nvidia OpenCL ICD will be
  installed without any dependencies.

  With the 331.38-0ubuntu7.1 drivers, ocl-icd-libopencl1 will be
  installed as a dependency:

  The following extra packages will be installed:
ocl-icd-libopencl1
  Suggested packages:
opencl-icd
  The following NEW packages will be installed:
nvidia-opencl-icd-331 ocl-icd-libopencl1

  Repeat the above for nvidia-opencl-icd-331-updates.

  [SRU Verification Test Case #2]
  sudo apt-get install nvidia-opencl-icd-331
  OR
  sudo apt-get install nvidia-opencl-icd-331-updates
  (does not require an Nvidia graphics card)

  sudo apt-get install beignet
  (an alternate OpenCL ICD)

  With the 331.38-0ubuntu7 drivers, the Nvidia OpenCL ICD will be
  removed:

  The following packages will be REMOVED:
    nvidia-opencl-icd-331
  The following NEW packages will be installed:
    beignet
  0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.

  With the 331.38-0ubuntu7.1 drivers, beignet and nvidia-opencl-icd-331
  (or nvidia-opencl-icd-331-updates) can be co-installed.

  [Test Case]
  sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates 
(does not require an Nvidia graphics card)
  sudo apt-get install python-pycuda
  sudo apt-get install python-pyopencl

  This will result in the error message below.

  The following packages have unmet dependencies:
   python-pyopencl : Depends: libopencl-1.1-1
     Depends: libopencl-1.2-1
     Depends: ocl-icd-libopencl1 but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

  A similar conflict exists between wine and nvidia-cuda-toolkit.

  sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates 
(does not require an Nvidia graphics card)
  sudo apt-get install wine
  sudo apt-get install nvidia-cuda-toolkit

  This will result in a warning similar to the one below.

  The following extra packages will be installed:
    nvidia-libopencl1-331 nvidia-opencl-dev
  The following packages will be REMOVED:
    ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64
    wine1.6-i386:i386
  The following NEW packages will be installed:
    nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev

  [Regression Potential]
  This fix only affects the relationships between packages and should not 
introduce any new bugs.  However, since packages that were previously difficult 
to install together will now be co-installable, new bugs in those packages may 
be exposed.

  [Other Info]
  It is possible to work around this issue by first installing the CUDA 
application, then installing ocl-icd-opencl-dev, and finally installing the 

[Desktop-packages] [Bug 1247736] Re: [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd

2014-08-05 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-331-updates -
331.38-0ubuntu7.1

---
nvidia-graphics-drivers-331-updates (331.38-0ubuntu7.1) trusty; urgency=medium

  * Backport the followings changes from 331.38-0ubuntu8 in Utopic to make
packages using CUDA and OpenCL co-installable:
- debian/templates/control.in, package nvidia-opencl-icd-*:
  - Remove breaks/replaces on opencl-icd (LP: #1247736).
  - Depend on ocl-icd-libopencl1 | nvidia-libopencl1-*.
 -- Graham Inggs gra...@nerve.org.za   Sun, 08 Jun 2014 11:59:01 +0200

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  [SRU] nvidia-opencl-icd-* should not conflicts/replaces on opencl-icd

Status in “nvidia-cuda-toolkit” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “ocl-icd” package in Ubuntu:
  Invalid
Status in “nvidia-cuda-toolkit” source package in Trusty:
  Invalid
Status in “nvidia-graphics-drivers-304” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Fix Released
Status in “nvidia-graphics-drivers-340” source package in Trusty:
  Invalid
Status in “ocl-icd” source package in Trusty:
  Invalid

Bug description:
  [Impact]
  Users with proprietary Nvidia graphics drivers are unable to co-install CUDA 
and OpenCL applications.
  The patches in comment #21 and #22 backport the fix from Utopic and resolve 
this issue by allowing nvidia-opencl-icd-* (Nvidia's OpenCL ICD) to be 
co-installed with ocl-icd-libopencl1 (the generic OpenCL ICD loader).

  [SRU Verification Test Case #1]
  sudo apt-get remove nvidia-opencl-icd-* nvidia-libopencl1-* ocl-icd-ibopencl1

  sudo apt-get install nvidia-opencl-icd-331

  With the 331.38-0ubuntu7 drivers, the Nvidia OpenCL ICD will be
  installed without any dependencies.

  With the 331.38-0ubuntu7.1 drivers, ocl-icd-libopencl1 will be
  installed as a dependency:

  The following extra packages will be installed:
ocl-icd-libopencl1
  Suggested packages:
opencl-icd
  The following NEW packages will be installed:
nvidia-opencl-icd-331 ocl-icd-libopencl1

  Repeat the above for nvidia-opencl-icd-331-updates.

  [SRU Verification Test Case #2]
  sudo apt-get install nvidia-opencl-icd-331
  OR
  sudo apt-get install nvidia-opencl-icd-331-updates
  (does not require an Nvidia graphics card)

  sudo apt-get install beignet
  (an alternate OpenCL ICD)

  With the 331.38-0ubuntu7 drivers, the Nvidia OpenCL ICD will be
  removed:

  The following packages will be REMOVED:
    nvidia-opencl-icd-331
  The following NEW packages will be installed:
    beignet
  0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.

  With the 331.38-0ubuntu7.1 drivers, beignet and nvidia-opencl-icd-331
  (or nvidia-opencl-icd-331-updates) can be co-installed.

  [Test Case]
  sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates 
(does not require an Nvidia graphics card)
  sudo apt-get install python-pycuda
  sudo apt-get install python-pyopencl

  This will result in the error message below.

  The following packages have unmet dependencies:
   python-pyopencl : Depends: libopencl-1.1-1
     Depends: libopencl-1.2-1
     Depends: ocl-icd-libopencl1 but it is not going to be 
installed
  E: Unable to correct problems, you have held broken packages.

  A similar conflict exists between wine and nvidia-cuda-toolkit.

  sudo apt-get install nvidia-331 or sudo apt-get install nvidia-331-updates 
(does not require an Nvidia graphics card)
  sudo apt-get install wine
  sudo apt-get install nvidia-cuda-toolkit

  This will result in a warning similar to the one below.

  The following extra packages will be installed:
    nvidia-libopencl1-331 nvidia-opencl-dev
  The following packages will be REMOVED:
    ocl-icd-libopencl1 ocl-icd-libopencl1:i386 wine wine1.6 wine1.6-amd64
    wine1.6-i386:i386
  The following NEW packages will be installed:
    nvidia-cuda-toolkit nvidia-libopencl1-331 nvidia-opencl-dev

  [Regression Potential]
  This fix only affects the relationships between packages and should not 
introduce any new bugs.  However, since packages that were previously difficult 
to install together will now be co-installable, new bugs in 

[Desktop-packages] [Bug 1352969] [NEW] gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node: Assertion `data' failed.

2014-08-05 Thread Till Kamppeter
Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gvfs-backends 1.20.2-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
AssertionMessage: gvfsd-afc: plist.c:194: plist_copy_node: Assertion `data' 
failed.
CurrentDesktop: Unity
Date: Tue Aug  5 17:33:46 2014
ExecutablePath: /usr/lib/gvfs/gvfsd-afc
InstallationDate: Installed on 2013-06-05 (426 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
Signal: 6
SourcePackage: gvfs
StacktraceTop:
 __assert_fail_base (fmt=0x7f5a97e648b0 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x7f5a982ce721 data, 
file=file@entry=0x7f5a982ce748 plist.c, line=line@entry=194, 
function=function@entry=0x7f5a982cead0 plist_copy_node) at assert.c:92
 __GI___assert_fail (assertion=0x7f5a982ce721 data, file=0x7f5a982ce748 
plist.c, line=194, function=0x7f5a982cead0 plist_copy_node) at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
Title: gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node: 
Assertion `data' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash need-amd64-retrace third-party-packages utopic

** Information type changed from Private to Public

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

Title:
  gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node:
  Assertion `data' failed.

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gvfs-backends 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: gvfsd-afc: plist.c:194: plist_copy_node: Assertion `data' 
failed.
  CurrentDesktop: Unity
  Date: Tue Aug  5 17:33:46 2014
  ExecutablePath: /usr/lib/gvfs/gvfsd-afc
  InstallationDate: Installed on 2013-06-05 (426 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605)
  ProcCmdline: /usr/lib/gvfs/gvfsd-afc --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
  Signal: 6
  SourcePackage: gvfs
  StacktraceTop:
   __assert_fail_base (fmt=0x7f5a97e648b0 %s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n, assertion=assertion@entry=0x7f5a982ce721 data, 
file=file@entry=0x7f5a982ce748 plist.c, line=line@entry=194, 
function=function@entry=0x7f5a982cead0 plist_copy_node) at assert.c:92
   __GI___assert_fail (assertion=0x7f5a982ce721 data, file=0x7f5a982ce748 
plist.c, line=194, function=0x7f5a982cead0 plist_copy_node) at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   plist_copy () from /usr/lib/x86_64-linux-gnu/libplist.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4
  Title: gvfsd-afc assert failure: gvfsd-afc: plist.c:194: plist_copy_node: 
Assertion `data' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

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

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


  1   2   3   >