[Desktop-packages] [Bug 1363150] Re: [FFe] Fcitx input method integration in Unity

[Benjamin Xiao]

This might be off topic, but I think this update caused fcitx to be
installed on my machine so I now have an indicator on my tray. Is this
supposed to be the intended effect or can I safely remove it?

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

Title:
  [FFe] Fcitx input method integration in Unity

Status in Indicator keyboard:
  New
Status in fcitx package in Ubuntu:
  Fix Released
Status in fcitx-qimpanel package in Ubuntu:
  Fix Released
Status in indicator-keyboard package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-settings-daemon package in Ubuntu:
  Fix Released

Bug description:
  Fcitx is being included in main, but Unity lacks support for it in
  various ways:

  - The Text Entry panel in unity-control-center has no effect on Fcitx' engine 
list
  - Per-window source options in Text Entry panel don't affect Fcitx
  - Fcitx engines (specifically for keyboard layout) are not available under 
unity-greeter
  - Fcitx indicator isn't available under the lock screen, only 
indicator-keyboard
  - Keyboard layout switching shortcut behaviour provided by Unity and 
unity-settings-daemon doesn't change Fcitx' current IM
  - Fcitx indicator is missing some options that are normally provided by 
indicator-keyboard
  - Running indicator-keyboard and Fcitx concurrently is redundant as 
indicator-keyboard only works with Xkb layouts and IBus IMs

  Some of the changes we need:

  - Add support for Fcitx input sources to unity-settings-daemon, 
unity-control-center, indicator-keyboard
  - Customize the Fcitx indicator under Unity to show some menu options that 
are available in indicator-keyboard (already merged upstream)
  - Hide indicator-keyboard in the session when Fcitx' indicator is visible
  - Add D-Bus property to Fcitx API for the current IM, so that we can detect 
when the user changes the current IM in the Fcitx indicator, and update the 
current input source accordingly (already merged upstream)
  - Use indicator-keyboard icons for keyboard layouts in Fcitx and 
fcitx-qimpanel when running under Unity

  We have a PPA that includes most of the proposed changes. It is
  available at https://launchpad.net/~fcitx-team/+archive/ubuntu/fcitx-
  transition. It does not hide indicator-keyboard in the session yet, as
  having both indicators visible is helpful for testing purposes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1363150/+subscriptions

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

[Desktop-packages] [Bug 1328678] Re: slash key '/' no longer opens the find box

[Marnus van Niekerk]

Tested and working on Trusty with evince 3.10.3-0ubuntu10.2

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

Title:
  slash key '/' no longer opens the find box

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  - using "/" doesn't start a search which some users are used to

  * Test case
  1. Open a pdf document.
  2. Press the '/' key.

  Expected:
   The find dialogue opens.

  Actual:
   Nothing

  * Regression potential
  the code adds an extra action, shouldn't create any new issue

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 10 22:15:53 2014
  InstallationDate: Installed on 2013-10-25 (228 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
  KernLog:

  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (48 days ago)

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

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

[Desktop-packages] [Bug 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.

[Mark Pereira]

@Gunnar: I think you're right. I do not have a mate-user-guide package. I'll 
have to follow up with the MATE team.
Thanks

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

Title:
  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

Status in yelp package in Ubuntu:
  Incomplete

Bug description:
  after upgrading to 14.10 alpha 2 when i try to launch yelp from
  command or from menu it shows

  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

  even when i try to search it shows the same

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: yelp 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Aug 24 11:53:45 2014
  InstallationDate: Installed on 2012-03-24 (882 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  SourcePackage: yelp
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1328678] Re: slash key '/' no longer opens the find box

[Mathew Hodson]

The package evince was accepted into trusty-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/evince/3.10.3-0ubuntu10.2, and in
the -proposed repository.

Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!

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

Title:
  slash key '/' no longer opens the find box

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  - using "/" doesn't start a search which some users are used to

  * Test case
  1. Open a pdf document.
  2. Press the '/' key.

  Expected:
   The find dialogue opens.

  Actual:
   Nothing

  * Regression potential
  the code adds an extra action, shouldn't create any new issue

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 10 22:15:53 2014
  InstallationDate: Installed on 2013-10-25 (228 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
  KernLog:

  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (48 days ago)

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

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

[Desktop-packages] [Bug 1328678] Re: slash key '/' no longer opens the find box

[Mathew Hodson]

A Trusty task should be opened for this bug to properly track its
status.

The '/' key opens the search menu for me with evince 3.10.3-0ubuntu10.2
from trusty-proposed.

** Tags added: verification-done-trusty

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

Title:
  slash key '/' no longer opens the find box

Status in evince package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  - using "/" doesn't start a search which some users are used to

  * Test case
  1. Open a pdf document.
  2. Press the '/' key.

  Expected:
   The find dialogue opens.

  Actual:
   Nothing

  * Regression potential
  the code adds an extra action, shouldn't create any new issue

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jun 10 22:15:53 2014
  InstallationDate: Installed on 2013-10-25 (228 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64+mac 
(20131016.1)
  KernLog:

  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (48 days ago)

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

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

[Desktop-packages] [Bug 1156879] Re: totem crashed with SIGABRT in __assert_fail_base()

[Launchpad Bug Tracker]

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

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

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

Title:
  totem crashed with SIGABRT in __assert_fail_base()

Status in totem package in Ubuntu:
  Expired

Bug description:
  Crashes when used by firefox to play an MP3 or in context to play video or 
just from the commandline:
  joe@studio1304:~$ totem
  Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading 
configurations from ~/.fonts.conf is deprecated.
  totem: nv04_state_frag.c:248: get_texenv_mode: Assertion `0' failed.
  Aborted (core dumped)

  TNT2 nvidia card
  open driver. (nouveau)

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: totem 3.6.3-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-12.8-lowlatency 3.8.2
  Uname: Linux 3.8.0-12-lowlatency i686
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  Date: Mon Mar 18 14:57:11 2013
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2013-03-13 (5 days ago)
  InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 
(20130312)
  MarkForUpload: True
  ProcCmdline: totem
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   ?? () from /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so
  Title: totem crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic

[Tholl1989]

[Verified test case]
#ubuntu-14.04.1-desktop-amd64 live system (proposed enabled)
*apt-get update && apt-get -y upgrade
*apt-get -s install ubuntu-sdk
Works fine, see attachment

#ubuntu-14.04.2-desktop-amd64 live system (proposed enabled)
*apt-get update && apt-get -y upgrade
*apt-get -s  install ubuntu-sdk
Works fine, see attachment

[Comment]
>From the changelog:
"Allow unrenamed -dev packages to work with the renamed stack."
Works around APT not being able to resolve dependencies with the utopic stack, 
but are Mesa 10.1.3 dev packages a good idea for Mesa 10.3.2? 

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+attachment/4342250/+files/apt.log

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

Title:
  Devel package not installable in 14.04.2 (mesa-lts-utopic

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

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

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1411100] Re: Guest user not removed after guest session ends when using bash as default shell

[Mathew Hodson]

** Tags removed: verification-done-precise
** Tags added: verification-done-utopic

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

Title:
  Guest user not removed after guest session ends when using bash as
  default shell

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh -> bash*

  But since using Bash as default sh is still a "feature" of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Desktop-packages] [Bug 1431128] Re: screen remains blank after waking up from suspend

[TienFu Chen]

This issue seems related to lp:1405349, not sure if it is the same root-
cause.

** Description changed:

  Steps:
- 1. Suspend the computer by pressing the Sleep key
+ 1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here)
  2. Press any key on the keyboard or the Power button to wake the device up
  
  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.
  
  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.
  
  Additional information:
  
  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.
  
  - Please note that this problem does NOT happen when suspending from the
  User Menu or using the Power button and selecting Suspend.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  screen remains blank after waking up from suspend

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here)
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1316090] Re: Unable to drop/ place files and links on second screen in dual screen set up

[Christopher M. Penalver]

Natalia, just to advise, the information that is needed is the apport-
collect requested in
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316090/comments/5 .

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

Title:
  Unable to drop/ place files and links on second screen in dual screen
  set up

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After updating from Xubuntu 13.10 (amd64) to Xubuntu 14.04 LTS (amd64)
  I have encountered a bug with my dual screen set up.

  Running the XOrg screen driver (xserver-xorg-video-nouveau), it is
  possible to place/ drag and drop files and links on my left screen
  desktop. This is also the desktop that contains the system icons (e.g.
  removable drives, rubbish bin).

  However, I I try to drag and drop a file or link on the right screen
  desktop, it will not "stick" and "fly back" to its original location
  on the left screen. Additionally, I noticed that, when dragging the
  file over the troubled desktop, the "placement squares" don't show up.
  They do on the functioning left screen.

  Although I have a NVIDIA Corporation GK107 [GeForce GTX 650] Geforce I
  do run the XOrg driver since it gives me the best results with the
  software I'm using frequently. However, when I tested this during my
  initial install of Trusty, I noticed that I did not encounter this bug
  with the proprietary NVidia 304.117 driver (331.38 did not work for me
  at all). Running the NVidia 304.117 driver, it was possible to drag
  and drop/ place files and links on both screen desktops. Also the
  "placement squares" appeared on both screens when a file was dragged
  over it.

  After returning to the XOrg driver, the problem reoccurred, and
  placement on the right screen was again not possible.

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

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

[Desktop-packages] [Bug 778054] Re: Packages shouldn't depend on the transitional package python-gobject

[Mathew Hodson]

Tested with python-zeitgeist 0.9.14-0ubuntu4.1. Looks good.

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

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

Title:
  Packages shouldn't depend on the transitional package python-gobject

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in desktopcouch package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in gnome-utils package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in wine1.4 package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released
Status in aptdaemon source package in Trusty:
  Fix Released
Status in desktopcouch source package in Trusty:
  Invalid
Status in eglibc source package in Trusty:
  Invalid
Status in gnome-utils source package in Trusty:
  Invalid
Status in libreoffice source package in Trusty:
  Fix Released
Status in openoffice.org source package in Trusty:
  Invalid
Status in system-config-printer source package in Trusty:
  Fix Released
Status in wine1.4 source package in Trusty:
  Invalid
Status in zeitgeist source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  python-zeitgeist depends on python-gobject, which means python-gobject
  cannot be removed from the system. python-gobject is a transitional
  package, and packages should be updated to no longer depend on it.

  [Test Case]

  * Install python-zeitgeist, and verify that python-gobject is not
  installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing python-zeitgeist.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

  ---

  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

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

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

[Desktop-packages] [Bug 1428356] Re: 03f0:2b17 USB HP LaserJet 1020 printer will not print after boot

[Christopher M. Penalver]

chris pollock, to see if this already fixed in Ubuntu, could you please
test http://cdimage.ubuntu.com/daily-live/current/ and advise to the
results (i.e. just a one-liner confirming it's still an issue, or it's
not).

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

Title:
  03f0:2b17 USB HP LaserJet 1020 printer will not print after boot

Status in HP Linux Imaging and Printing:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After a reboot due to cups related package update my HP1020 printer is not 
initialized. This is shown in my syslog:
  Mar  4 15:32:42 localhost kernel: [  178.196280] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:32:42 localhost kernel: [  178.198667] usblp0: removed
  Mar  4 15:32:53 localhost kernel: [  189.196356] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:32:53 localhost kernel: [  189.198743] usblp0: removed
  Mar  4 15:33:04 localhost kernel: [  200.196869] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:33:04 localhost kernel: [  200.199629] usblp0: removed
  Mar  4 15:33:15 localhost kernel: [  211.200586] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17

  This just continues on for hundreds of entries until I unplug and
  replug the printer back in, and power cycle several times. It will
  then eventually print a test page via 'CUPS'.

  Some other information from my syslog:
  Mar  4 15:42:10 localhost kernel: [  746.297929] usblp: can't set desired 
altsetting 0 on interface 0
  Mar  4 15:42:10 localhost kernel: [  746.488804] usb 1-3.5: USB disconnect, 
device number 5
  Mar  4 15:42:14 localhost kernel: [  750.528166] usb 1-3.5: new high-speed 
USB device number 7 using ehci-pci
  Mar  4 15:42:16 localhost udev-configure-printer: remove 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:16 localhost colord: device removed: 
sysfs-Hewlett-Packard-HP_LaserJet_1020
  Mar  4 15:42:23 localhost kernel: [  758.976137] usb 1-3.5: new high-speed 
USB device number 8 using ehci-pci
  Mar  4 15:42:23 localhost kernel: [  759.088384] usb 1-3.5: New USB device 
found, idVendor=03f0, idProduct=2b17
  Mar  4 15:42:23 localhost kernel: [  759.088389] usb 1-3.5: New USB device 
strings: Mfr=1, Product=2, SerialNumber=3
  Mar  4 15:42:23 localhost kernel: [  759.088392] usb 1-3.5: Product: HP 
LaserJet 1020
  Mar  4 15:42:23 localhost kernel: [  759.088394] usb 1-3.5: Manufacturer: 
Hewlett-Packard
  Mar  4 15:42:23 localhost kernel: [  759.088396] usb 1-3.5: SerialNumber: 
JL1F0DC
  Mar  4 15:42:23 localhost kernel: [  759.091958] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:42:23 localhost logger: loading HP Device 001 008
  Mar  4 15:42:23 localhost udev-configure-printer: add 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:23 localhost udev-configure-printer: device devpath is 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3.5
  Mar  4 15:42:23 localhost udev-configure-printer: MFG:Hewlett-Packard MDL:HP 
LaserJet 1020 SERN:- serial:JL1F0DC
  Mar  4 15:42:24 localhost kernel: [  760.148568] usblp0: removed
  Mar  4 15:42:24 localhost kernel: [  760.159830] usblp 1-3.5:1.0: usblp0: USB 
Bidirectional printer dev 8 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
  Mar  4 15:42:24 localhost udev-configure-printer: URI contains USB serial 
number
  Mar  4 15:42:24 localhost udev-configure-printer: URI match: 
usb://HP/LaserJet%201020?serial=JL1F0DC
  Mar  4 15:42:24 localhost udev-configure-printer: SERN field matches USB 
serial number
  Mar  4 15:42:24 localhost udev-configure-printer: URI match: 
hp:/usb/HP_LaserJet_1020?serial=JL1F0DC
  Mar  4 15:42:24 localhost udev-configure-printer: URI of detected printer: 
usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial 
jl1f0dc
  Mar  4 15:42:24 localhost udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201020?serial=JL1F0DC, normalized: laserjet 1020 serial 
jl1f0dc
  Mar  4 15:42:24 localhost udev-configure-printer: Queue 
ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI
  Mar  4 15:42:24 localhost udev-configure-printer: URI of detected printer: 
hp:/usb/HP_LaserJet_1020?serial=JL1F0DC, normalized: laserjet 1020 serial 
jl1f0dc
  Mar  4 15:42:24 localhost udev-configure-printer: Queue 
ipp://localhost:631/printers/HP-LaserJet-1020 has matching device URI
  Mar  4 15:42:26 localhost kernel: [  762.327990] usblp0: removed
  Mar  4 15:42:30 localhost colord: Device added: 
sysfs-Hewlett-Packard-HP_LaserJet_1020

  chris@localhost:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 

[Desktop-packages] [Bug 1431131] [NEW] reporte del error

[juan]

Public bug reported:

si es tana amable de ayudar el problema de mi sistema Ubuntu Gnome que
se envia reporte

muchas gracias

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic i686
ApportVersion: 2.16.2-0ubuntu1
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Mar 11 21:34:59 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.22, 3.18.0-13-generic, i686: installed
 virtualbox, 4.3.22, 3.19.0-7-generic, i686: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e164]
InstallationDate: Installed on 2015-02-26 (14 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha i386 (20150224)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2PT
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=481da314-0604-4481-b3f0-41bdec05dbd9 ro plymouth:debug splash quiet 
drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/05/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FC
dmi.board.name: GA-78LMT-S2PT
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFC:bd11/05/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2PT:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2PT:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-S2PT
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.59-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~rc3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~rc3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Wed Mar 11 18:52:39 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
 inputi2c IR (Pinnacle PCTV) KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.2.901-1ubuntu4
xserver.video_driver: radeon

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


** Tags: apport-bug i386 ubuntu vivid

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

Title:
  reporte del error

Status in xorg package in Ubuntu:
  New

Bug description:
  si es tana amable de ayudar el problema de mi sistema Ubuntu Gnome que
  se envia reporte

  muchas gracias

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Mar 11 21:34:59 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.22, 3.18.0-13-generic, i686: installed
   virtualbox, 4.3.22, 3.19.0-7-generic, i686: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e164]
  InstallationDate: Installed on 2015-02-26 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha i386 (20150224)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2PT
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=481da314-0604-4481-b3f0-41bdec05dbd9 ro plymouth:debug splash quiet 
drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2012
  dmi.bios.vendor: Award Software International, I

[Desktop-packages] [Bug 1431128] Re: screen remains blank after waking up from suspend

[TienFu Chen]

** Description changed:

- TBD
+ Steps:
+ 1. Suspend the computer by pressing the Sleep key
+ 2. Press any key on the keyboard or the Power button to wake the device up
+ 
+ Expected results:
+ 1. The system suspends and the Power button LED blinks
+ 2. The system wakes up and user can log in.
+ 
+ Actual results:
+ 1. The system suspends and the Power button LED blinks (OK)
+ 2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.
+ 
+ Additional information:
+ 
+ - In a few additional occasions, after performing this action several
+ times (pressing the Sleep key to suspend the system, then wake it up),
+ the system freezes at log in screen just before going to suspend mode.
+ It has to be force-stopped and restarted.
+ 
+ - Please note that this problem does NOT happen when suspending from the
+ User Menu or using the Power button and selecting Suspend.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
-  # This is a distribution channel descriptor
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
+  # This is a distribution channel descriptor
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
-  [SeatDefaults]
-  autologin-guest=false
-  autologin-user-timeout=0
-  autologin-session=lightdm-autologin
-  #autologin-user=u
+  [SeatDefaults]
+  autologin-guest=false
+  autologin-user-timeout=0
+  autologin-session=lightdm-autologin
+  #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Title:
  screen remains blank after waking up from suspend

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key(Fn+F2 on the keyboard here)
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1207935] Re: lightdm crashed with SIGSEGV in quit_timeout_cb()

[Robert Ancell]

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

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Fix Committed

** Changed in: lightdm (Ubuntu Precise)
   Importance: Undecided => Medium

** Tags added: verification-done

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

** Changed in: lightdm/1.2
   Status: New => Fix Released

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

** Changed in: lightdm/1.2
Milestone: None => 1.2.11

** Changed in: lightdm/1.2
Milestone: 1.2.11 => 1.2.7

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

Title:
  lightdm crashed with SIGSEGV in quit_timeout_cb()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  ..

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.8-0ubuntu1
  Uname: Linux 3.11.0-031100rc3-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jul 31 00:29:44 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2011-07-23 (738 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
   autologin-user=
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x40e47d:  movl   $0x0,0x20(%rax)
   PC (0x0040e47d) ok
   source "$0x0" ok
   destination "0x20(%rax)" (0xaaca) not located in a known VMA 
region (needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: lightdm crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to saucy on 2013-07-10 (19 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1411100] Re: Guest user not removed after guest session ends when using bash as default shell

[Robert Ancell]

Confirmed script works with bash in trusty-proposed and utopic-proposed

** Tags removed: verification-needed
** Tags added: verification-done-precise verification-done-trusty

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

Title:
  Guest user not removed after guest session ends when using bash as
  default shell

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh -> bash*

  But since using Bash as default sh is still a "feature" of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Desktop-packages] [Bug 1431128] [NEW] screen remains blank after waking up from suspend

[Pierre Equoy]

Public bug reported:

Steps:
1. Suspend the computer by pressing the Sleep key
2. Press any key on the keyboard or the Power button to wake the device up

Expected results:
1. The system suspends and the Power button LED blinks
2. The system wakes up and user can log in.

Actual results:
1. The system suspends and the Power button LED blinks (OK)
2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

Additional information:

- In a few additional occasions, after performing this action several
times (pressing the Sleep key to suspend the system, then wake it up),
the system freezes at log in screen just before going to suspend mode.
It has to be force-stopped and restarted.

- Please note that this problem does NOT happen when suspending from the
User Menu or using the Power button and selecting Suspend.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.4-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Date: Thu Mar 12 11:19:32 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
InstallationDate: Installed on 2015-02-10 (29 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
LightdmConfig:
 [SeatDefaults]
 autologin-guest=false
 autologin-user-timeout=0
 autologin-session=lightdm-autologin
 #autologin-user=u
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: oem-priority/trusty
 Importance: Undecided
 Status: New

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


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

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

Title:
  screen remains blank after waking up from suspend

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Steps:
  1. Suspend the computer by pressing the Sleep key
  2. Press any key on the keyboard or the Power button to wake the device up

  Expected results:
  1. The system suspends and the Power button LED blinks
  2. The system wakes up and user can log in.

  Actual results:
  1. The system suspends and the Power button LED blinks (OK)
  2. The login screen appears and the screen is immediately turned off (NOK). 
User needs to move the mouse or enter a key to turn the screen on.

  Additional information:

  - In a few additional occasions, after performing this action several
  times (pressing the Sleep key to suspend the system, then wake it up),
  the system freezes at log in screen just before going to suspend mode.
  It has to be force-stopped and restarted.

  - Please note that this problem does NOT happen when suspending from
  the User Menu or using the Power button and selecting Suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.4-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Mar 12 11:19:32 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-kylin-trusty-amd64-20150205-2
  InstallationDate: Installed on 2015-02-10 (29 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150205-07:08
  LightdmConfig:
   [SeatDefaults]
   autologin-guest=false
   autologin-user-timeout=0
   autologin-session=lightdm-autologin
   #autologin-user=u
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1431129] [NEW] transmission-gtk speed unstable with large files (10GB+)

[Patrick Fafali Agbokou]

Public bug reported:

When downloading a large file (10GB+), download speed fluctuates drastically 
(rises normally to maximum, suddenly drops down to zero). Before it is asked, 
please note that this does not occur when downloading 1GB- files. Speed 
rremains steady at the maximum. This annoying behaviour only occurs with large 
files.
The upload speed is also affected by the fluctuation.

What was being done
=
Downloading large file

What is expected to happen
==
Download speed steady at maximum

What happened instead
==
Download speed repeatedly drops to 0

Version
===
Transmission-gtk 2.82
Description:Ubuntu 14.04.2 LTS
Release:14.04
Linux archangel 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  transmission-gtk speed unstable with large files (10GB+)

Status in transmission package in Ubuntu:
  New

Bug description:
  When downloading a large file (10GB+), download speed fluctuates drastically 
(rises normally to maximum, suddenly drops down to zero). Before it is asked, 
please note that this does not occur when downloading 1GB- files. Speed 
rremains steady at the maximum. This annoying behaviour only occurs with large 
files.
  The upload speed is also affected by the fluctuation.

  What was being done
  =
  Downloading large file

  What is expected to happen
  ==
  Download speed steady at maximum

  What happened instead
  ==
  Download speed repeatedly drops to 0

  Version
  ===
  Transmission-gtk 2.82
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  Linux archangel 3.13.0-46-generic #77-Ubuntu SMP Mon Mar 2 18:23:39 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

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

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

[Desktop-packages] [Bug 790324] Re: Frame in a webpage not viewed

[Micah Gersten]

Thank you for this report.  This no longer appears to affect Firefox
36.0.1.  If this is now working, no action is required and the report
will expire.  If this is still an issue, please provide steps to
reproduce.

** Changed in: firefox (Ubuntu)
   Status: New => Incomplete

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

Title:
  Frame in a webpage not viewed

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: firefox

  In the website www.intesasanpaolo.com, I can't log in. The frame in
  the upper right corner which asks for code and password doesn't show.
  It works under Firefox4 in Windows XP and 7.

  Ubuntu 11.04, Firefox 4.0.1

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  Architecture: i386
  Date: Mon May 30 20:24:35 2011
  FirefoxPackages:
   firefox 4.0.1+build1+nobinonly-0ubuntu0.11.04.3
   flashplugin-installer 10.3.181.14ubuntu0.11.04.1
   adobe-flashplugin N/A
   icedtea-plugin 1.1~20110420-0ubuntu1
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANGUAGE=it_IT:en
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2011-05-05 (24 days ago)

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

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

[Desktop-packages] [Bug 1431126] [NEW] package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los disparadores han entrado en bucle, abandonando

[Jason Jarquín]

Public bug reported:

I made an upgrade using terminal and the bug traker appeared

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fontconfig 2.11.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
Date: Wed Mar 11 21:11:03 2015
DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:los disparadores han 
entrado en bucle, abandonando
ErrorMessage: los disparadores han entrado en bucle, abandonando
InstallationDate: Installed on 2015-03-12 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
SourcePackage: fontconfig
Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los
  disparadores han entrado en bucle, abandonando

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I made an upgrade using terminal and the bug traker appeared

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fontconfig 2.11.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 11 21:11:03 2015
  DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:los disparadores han 
entrado en bucle, abandonando
  ErrorMessage: los disparadores han entrado en bucle, abandonando
  InstallationDate: Installed on 2015-03-12 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1383321] Re: Support XDG DesktopNames field in session files

[Robert Ancell]

** Tags removed: verification-needed

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

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

[Desktop-packages] [Bug 1431126] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los disparadores han entrado en bucle, abandonando

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los
  disparadores han entrado en bucle, abandonando

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I made an upgrade using terminal and the bug traker appeared

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: fontconfig 2.11.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  Date: Wed Mar 11 21:11:03 2015
  DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:los disparadores han 
entrado en bucle, abandonando
  ErrorMessage: los disparadores han entrado en bucle, abandonando
  InstallationDate: Installed on 2015-03-12 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: los 
disparadores han entrado en bucle, abandonando
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1383321] Re: Support XDG DesktopNames field in session files

[Robert Ancell]

Confirmed fixed in utopic-proposed.

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

[Desktop-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed

[Robert Ancell]

Confirmed fixed in precise-proposed, trusty-proposed and utopic-
proposed.

** Tags removed: verification-needed
** Tags added: ed verification-done-trusty

** Tags removed: ed raring

** Changed in: lightdm (Ubuntu Precise)
   Status: Triaged => Fix Committed

** Tags added: verification-done-precise

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

Title:
  Daemon end of session/greeter pipes not closed

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes and greeters. This means each session/greeter that is 
created leaks two file descriptors eventually leading to the system stopping it 
from creating new pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

[Desktop-packages] [Bug 1069218] Re: users.conf doesn't match users.c

[Robert Ancell]

Confirmed fixed in precise-proposed.

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

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Fix Committed

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

Title:
  users.conf doesn't match users.c

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The default users.conf provided by LightDM mentions a section [UserAccounts]. 
It should be [UserList].

  [Test Case]
  1. Check default installed users.conf
  Expected result:
  Should have a [UserList] section with all items available but disabled.
  Observed result:
  Have a [UserAccounts] section with all items available but disabled.

  [Regression Potential]
  Very low - just changing the default configuration file which has no active 
configuration items.

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

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

[Desktop-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

[Robert Ancell]

Confirmed fixed in precise-proposed.

** Changed in: lightdm (Ubuntu Precise)
   Status: New => Fix Committed

** Tags added: verification-done-precise

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  Fix Committed

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1270410] Re: package tex-common 4.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[barangkau]

** Changed in: tex-common (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package tex-common 4.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Fix Released

Bug description:
  This was generated while doing upgrade to newest ubuntu, upgrader
  stopped unity crashed and I had to cntrl/alt f2 to get a terminal and
  had to "sudo killall dpkg" and then "sudo dpkg --configure -a" several
  times to complete the upgrade to the point it was safe to reboot into
  a stable environment.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 4.04
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sat Jan 18 05:00:25 2014
  DuplicateSignature: package:tex-common:4.04:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-05-07 (986 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 4.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2014-01-18 (0 days ago)

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

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

[Desktop-packages] [Bug 1094114] Re: Disk Usage Analyzer crashes when selecting the About dialog from the menu

[Rolf Leggewie]

Nick, thank you for reporting back.  I will close this ticket as
unreproducible then.  Please continue to report any problem you might
find in the future.

** Changed in: baobab (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Disk Usage Analyzer crashes when selecting the About dialog from the
  menu

Status in baobab package in Ubuntu:
  Invalid

Bug description:
  The Disk Usage Analyzer crashes when selecting the About dialog from
  the menu.

  I am using Ubuntu 12.10 and baobab 3.6.0-0ubuntu1.

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

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

[Desktop-packages] [Bug 124315] Re: Remember+restore window position of applications with WM_WINDOW_ROLE or window title set

[Johnny Develop]

FYI, I'm working on an indicator to store windows placement.

https://github.com/lesion/indicator-placement

please feel free to contribute

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

Title:
  Remember+restore window position of applications with WM_WINDOW_ROLE
  or window title set

Status in One Hundred Papercuts:
  Won't Fix
Status in compiz package in Ubuntu:
  Confirmed
Status in metacity package in Ubuntu:
  Confirmed

Bug description:
  Open firefox or thunderbird.  Move the window.  Quit the application.  Open 
the application again.  The window is back over on the left again.
  The mozilla team leaves window positioning to the window manager on 
unix/linux systems:
  https://bugzilla.mozilla.org/show_bug.cgi?id=31086

  The advanced settings to enable Gnome to remember window positions is not 
available at the place these instructions say they were a year ago:
  http://ubuntuforums.org/archive/index.php/t-36505.html%3C/t-199815.html

  A similar ubuntu bug was reported earlier, but it was about firefox only, and 
it is already marked as having been fixed in Feb., however, I am seeing the 
issue today using Feisty, which was released in April:
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/65841

  One possible workaround is using Devil's Pie: 
http://www.burtonini.com/blog/computers/devilspie
  which requires hand editing xml files and creating pattern matching filter 
rules.

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

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

[Desktop-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed

[Robert Ancell]

** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic

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

Title:
  Daemon end of session/greeter pipes not closed

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Fix Committed
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes and greeters. This means each session/greeter that is 
created leaks two file descriptors eventually leading to the system stopping it 
from creating new pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

[Desktop-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

[Robert Ancell]

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

** Also affects: indicator-keyboard (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu Precise)
   Importance: Undecided => Medium

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released
Status in indicator-keyboard source package in Precise:
  New
Status in lightdm source package in Precise:
  New

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1069218] Re: users.conf doesn't match users.c

[Robert Ancell]

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

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

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

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

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

** Changed in: lightdm (Ubuntu Precise)
   Importance: Undecided => Medium

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

** No longer affects: lightdm (Ubuntu Utopic)

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

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

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

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

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

Title:
  users.conf doesn't match users.c

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  New
Status in lightdm source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  The default users.conf provided by LightDM mentions a section [UserAccounts]. 
It should be [UserList].

  [Test Case]
  1. Check default installed users.conf
  Expected result:
  Should have a [UserList] section with all items available but disabled.
  Observed result:
  Have a [UserAccounts] section with all items available but disabled.

  [Regression Potential]
  Very low - just changing the default configuration file which has no active 
configuration items.

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

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

[Desktop-packages] [Bug 1431068] Re: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build [error: implicit declaration of function ‘__get_cpu_var’]

[Daniel van Vugt]

** Summary changed:

- fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build
+ fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to 
build [error: implicit declaration of function ‘__get_cpu_var’]

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

Title:
  fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed
  to build [error: implicit declaration of function ‘__get_cpu_var’]

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

Bug description:
  I run Ubuntu 14.04.2 LTS Cinnamon desktop x64, just upgraded my linux
  kernel to 3.19, via:

  "cd /tmp/
  +
  wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb
  +
  wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900_3.19.0-031900.201502091451_all.deb
  +
  wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-image-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb
  +
  sudo dpkg -i linux-headers-3.19.0-*.deb linux-image-3.19.0-*.deb
  +
  sudo reboot"

  The problem I have was reported automatically by my system. So far, I
  haven't noticed any malfunctions myself...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates 2:13.350.1-0ubuntu2
  Uname: Linux 3.19.0-031900-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 3.19.0-031900-generic
  Date: Thu Mar 12 01:11:58 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-47-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-updates:2:13.350.1-0ubuntu2:/var/lib/dkms/fglrx-updates/13.350.1/build/2.6.x/firegl_public.c:4733:5:
 error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ee]
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M] 
[1002:6821] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ee]
  InstallationDate: Installed on 2014-08-09 (214 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  LightdmGreeterLog:
   (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
  LightdmGreeterLogOld:
   (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
  MachineType: Dell Inc. Inspiron 3737
  PackageVersion: 2:13.350.1-0ubuntu2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=c18e6c5b-cc8a-40d3-98fe-f9721bd79aab ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0HF1CD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3737:pvrA08:rvnDellInc.:rn0HF1CD:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3737
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-vi

[Desktop-packages] [Bug 1419800] Re: gdm crashed with signal 5 in g_simple_async_result_complete()

[Bug Watch Updater]

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

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

Title:
  gdm crashed with signal 5 in g_simple_async_result_complete()

Status in GDM: The Gnome Display Manager:
  Confirmed
Status in gdm package in Ubuntu:
  New

Bug description:
  Start Ubuntu and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gdm 3.14.1-0ubuntu1
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16-0ubuntu1
  Architecture: amd64
  Date: Mon Feb  9 10:47:57 2015
  ExecutablePath: /usr/sbin/gdm
  InstallationDate: Installed on 2014-09-25 (137 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/sbin/gdm
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
  Signal: 5
  SourcePackage: gdm
  StacktraceTop:
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gdm crashed with signal 5 in g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 797253] Re: gvfsd-ftp crashed with SIGSEGV in g_io_stream_get_input_stream()

[Bug Watch Updater]

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

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

Title:
  gvfsd-ftp crashed with SIGSEGV in g_io_stream_get_input_stream()

Status in GVFS:
  Fix Released
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gvfs

  This appeared in Apport while accessing a remote FTP site.  The FTP
  site required a login (not anonymous FTP).

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: gvfs-backends 1.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CheckboxSubmission: 19c99fb01e1766b0f123883d9be20193
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Wed Jun 15 01:13:18 2011
  ExecutablePath: /usr/lib/gvfs/gvfsd-ftp
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcCmdline: /usr/lib/gvfs/gvfsd-ftp --spawner :1.9 /org/gtk/gvfs/exec_spaw/8
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(cususername, user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f6ef57fc204 :   
mov(%rdi),%rax
   PC (0x7f6ef57fc204) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gvfs
  StacktraceTop:
   g_io_stream_get_input_stream () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: gvfsd-ftp crashed with SIGSEGV in g_io_stream_get_input_stream()
  UpgradeStatus: Upgraded to natty on 2011-05-09 (36 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1391024] Re: The prompt of Password Strength Meter hasn't been translated.

[Aron Xu]

** Changed in: ubuntu-translations
   Status: Fix Committed => Fix Released

** Changed in: ubuntukylin
   Status: Fix Committed => Fix Released

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

Title:
  The prompt of Password Strength Meter hasn't been translated.

Status in Ubuntu Translations:
  Fix Released
Status in Ubuntu Kylin:
  Fix Released
Status in libpwquality package in Ubuntu:
  Fix Released
Status in libpwquality source package in Trusty:
  Fix Released
Status in libpwquality source package in Utopic:
  Fix Released

Bug description:
  * Impact
  the password meter hints from the user account settings are not translated

  * Test case
  - use unity7 with a non english locale
  - System settings->User Accounts->Unlock
  - Click password
  - place the mouse on the Password Strength Meter
  -> the hint should be translated

  * Impact regression
  Shouldn't be one, there is no code change, it's only for launchpad import of 
the template

  ---

  1. System settings->User Accounts->Unlock
  2. Click password
  3. place the mouse on the Password Strength Meter
  Failed- The prompt of Password Strength Meter hasn't been translated.

  Ubuntukylin-14.10-utopic; 32bit ;lenovo

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

-- 
Mailing list: https://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 1430561] Re: hp-plugin crashes with error: Python gobject/dbus may be not installed

[goutam kodu]

There seem to be an issue with the auto installer script . While we take
a look at it can you try manually installing the hplip.

Here are the steps.
1 . Go inside the folder hplip-3.15.2. It should be created at the same 
location where auto installer was run.

change directory  to  hplip-3.15.2

cd   hplip-3.15.2

2.  Run command ./configure --prefix=/usr
3. Run 'make' command.
4. Run 'sudo make install'

This should install hplip in your system
Configure the device and let us know if everything is working.

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

Title:
  hp-plugin crashes with error: Python gobject/dbus may be not installed

Status in HP Linux Imaging and Printing:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in hplip package in Ubuntu:
  Confirmed

Bug description:
  When trying to configure an HP LaserJet P1102w, when running hp-plugin
  I get errors and can not proceed:

  nessita@miro:~$ hp-plugin
  error: Unable to locate models.dat file

  HP Linux Imaging and Printing System (ver. 3.15.2)
  Plugin Download and Install Utility ver. 2.1

  Copyright (c) 2001-15 Hewlett-Packard Development Company, LP
  This software comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to distribute it
  under certain conditions. See COPYING file for more details.

  Checking for network connection...
  Downloading plug-in from: 
  Receiving digital keys: /usr/bin/gpg --homedir /home/nessita/.hplip/.gnupg 
--no-permission-warning --keyserver pgp.mit.edu --recv-keys 0xA59047B9
  Creating directory plugin_tmp
  Verifying archive integrity... All good.
  Uncompressing HPLIP 3.15.2 Plugin Self Extracting 
Archive...
  Error importing HPLIP modules.  Is HPLIP installed?
  error: Python gobject/dbus may be not installed
  error: Plug-in install failed.

  Done.
  nessita@miro:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: hplip 3.15.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar 10 19:23:41 2015
  InstallationDate: Installed on 2014-11-30 (100 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat: device for Laserjet: ipp://NPI2E6620.local:631/printers/Laserjet
  MachineType: LENOVO 3249CTO
  Papersize: letter
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=30425f63-143e-4183-aa37-394415c60a42 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to vivid on 2015-02-09 (29 days ago)
  dmi.bios.date: 10/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET61WW (1.31 )
  dmi.board.name: 3249CTO
  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:bvr6QET61WW(1.31):bd10/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines

[Adam Katz]

Summary of problem (for me):

* ssh host fails with "ssh Agent admitted failure"
* SSH_AUTH_SOCK= ssh host works just fine
* Conclusion:  gnome-keyring can't deal with complex keys

WORKAROUND:

mv $SSH_AUTH_SOCK $SSH_AUTH_SOCK.broken
ssh-agent -a $SSH_AUTH_SOCK

This is a new instance of ssh-agent, so it won't have any keys in it
(despite what seahorse says, since that's tied to the .broken agent).
You'll have to add them via ssh-add.

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

Title:
  ssh Agent admitted failure to sign using the key on big endian
  machines

Status in Seahorse:
  Fix Released
Status in gnome-keyring package in Ubuntu:
  Triaged
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  on hardy (preserved home folder from feisty) i get the following when
  i try to ssh

  Agent admitted failure to sign using the key.
  Permission denied (publickey).

  or with verbose on

  sam@titania:~$ ssh -v oberon
  OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
  debug1: Reading configuration data /home/sam/.ssh/config
  debug1: Applying options for oberon
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: Applying options for *
  debug1: Connecting to ## [##] port ##.
  debug1: Connection established.
  debug1: identity file /home/sam/.ssh/identity type -1
  debug1: identity file /home/sam/.ssh/id_rsa type 1
  debug1: identity file /home/sam/.ssh/id_dsa type -1
  debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 
Debian-5ubuntu0.1
  debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH*
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server->client aes128-cbc hmac-md5 none
  debug1: kex: client->server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: using hostkeyalias: oberon
  debug1: Host 'oberon' is known and matches the RSA host key.
  debug1: Found key in /home/sam/.ssh/known_hosts:1
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: publickey
  debug1: Next authentication method: publickey
  debug1: Offering public key: /home/sam/.ssh/id_rsa
  debug1: Server accepts key: pkalg ssh-rsa blen 277
  Agent admitted failure to sign using the key.
  debug1: Trying private key: /home/sam/.ssh/identity
  debug1: Trying private key: /home/sam/.ssh/id_dsa
  debug1: No more authentication methods to try.
  Permission denied (publickey).

  I tried generating a new key. this worked for a few logons, but then i
  get back to this error.

  I think it is to do with the local key agent. i found that
   SSH_AUTH_SOCK=0 ssh oberon
  works fine.

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

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

[Desktop-packages] [Bug 1341309] Re: [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in Chromium

[GSJ]

Hi,

I had same issue as described above.  I'm happy to report that my problem has 
been fixed by applying following update per
https://bugs.freedesktop.org/show_bug.cgi?id=80568#c99 on the latest kernel 
release.   YMMV.

sudo apt-add-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get dist-upgrade 
dpkg -l libgl1-mesa-dri
sudo reboot


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

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

Title:
  [965gm mesa] TotalBlackCrash_or_IntermittingScreenView, GPU lockup in
  Chromium

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

Bug description:
  Chromiun browsing an italian webmail (libero: inwind.it, libero.it,
  etc. accounts), logon done, using any comand or cheking boxes, system
  crash in a black screeen (some hd activity's left) or start an about 1
  second intermitting screen aspect (few icons, then none, again few
  icons, then none, etc., in the desktop screen aspect). In both case
  hard drastic reboot is necessary.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.13.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  Chipset: i965gm
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Jul 13 15:55:33 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DuplicateSignature: [i965gm] GPU lockup  IPEHR: 0x60020100 Ubuntu 14.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:011f]
 Subsystem: Acer Incorporated [ALI] Device [1025:011f]
  InstallationDate: Installed on 2014-06-02 (40 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Acer Extensa 5620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic 
root=UUID=6f5ce81b-5a89-4c62-b14d-695a51e7c561 ro quiet splash
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libdrm2  2.4.54-1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [i965gm] GPU lockup  IPEHR: 0x60020100
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/15/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.34
  dmi.board.name: Columbia
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd04/15/2008:svnAcer:pnExtensa5620:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5620
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  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-1ubuntu4
  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: Sun Jul 13 16:48:30 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu8

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

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

[Desktop-packages] [Bug 539467] Re: SATA link power management causes disk errors and corruption

[Wurlitzer]

Uninstalling the tlp package resolved this issue for me (Ubuntu 14.04).

Disabling laptop_mode also seemed to help:
echo 0 > /proc/sys/vm/laptop_mode

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

Title:
  SATA link power management causes disk errors and corruption

Status in The Linux Kernel:
  Expired
Status in linux package in Ubuntu:
  Invalid
Status in pm-utils package in Ubuntu:
  Fix Released
Status in pm-utils-powersave-policy package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Won't Fix
Status in pm-utils source package in Lucid:
  Invalid
Status in pm-utils-powersave-policy source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Invalid
Status in pm-utils source package in Maverick:
  Invalid
Status in pm-utils-powersave-policy source package in Maverick:
  Invalid
Status in linux source package in Natty:
  Invalid
Status in pm-utils source package in Natty:
  Fix Released
Status in pm-utils-powersave-policy source package in Natty:
  Invalid

Bug description:
  SRU Justification for pm-utils-powersave-policy:

  Impact: On certain hardware, enabling power saving for the SATA link
  can cause data corruption.

  How Addressed: The proposed branch removes the sata link power policy
  script. This will cause the link to be maintained at the normal power
  usage instead of dropping when the power is removed from the machine.

  Reproduction: On an affected machine, unplug and plug in the power a
  few times. Data corruption will result.

  Regression Potential: Removing the script will cause the SATA link to
  stay fully powered at all times. This may cause an increase in the
  battery usage for some machines. There should be no functionality
  regressions or bugs introduced by this change.

  =

  Using Lucid on my laptop, I see errors like this in dmesg quite
  frequently (every few hours):

  Mar 14 23:00:09 chris-laptop kernel: [42987.460608] ata1.00: exception Emask 
0x10 SAct 0x1 SErr 0x5 action 0xe frozen
  Mar 14 23:00:09 chris-laptop kernel: [42987.460618] ata1.00: irq_stat 
0x0040, PHY RDY changed
  Mar 14 23:00:09 chris-laptop kernel: [42987.460627] ata1: SError: { PHYRdyChg 
CommWake }
  Mar 14 23:00:09 chris-laptop kernel: [42987.460635] ata1.00: failed command: 
READ FPDMA QUEUED
  Mar 14 23:00:09 chris-laptop kernel: [42987.460649] ata1.00: cmd 
60/08:00:97:23:44/00:00:01:00:00/40 tag 0 ncq 4096 in
  Mar 14 23:00:09 chris-laptop kernel: [42987.460652]  res 
40/00:04:97:23:44/00:00:01:00:00/40 Emask 0x10 (ATA bus error)
  Mar 14 23:00:09 chris-laptop kernel: [42987.460669] ata1.00: status: { DRDY }
  Mar 14 23:00:09 chris-laptop kernel: [42987.460681] ata1: hard resetting link
  Mar 14 23:00:09 chris-laptop kernel: [42987.523336] ata2: exception Emask 
0x10 SAct 0x0 SErr 0x5 action 0xe frozen
  Mar 14 23:00:09 chris-laptop kernel: [42987.523346] ata2: irq_stat 
0x0040, PHY RDY changed
  Mar 14 23:00:09 chris-laptop kernel: [42987.523355] ata2: SError: { PHYRdyChg 
CommWake }
  Mar 14 23:00:09 chris-laptop kernel: [42987.523368] ata2: hard resetting link
  Mar 14 23:00:09 chris-laptop kernel: [42988.202586] ata1: SATA link up 3.0 
Gbps (SStatus 123 SControl 300)
  Mar 14 23:00:09 chris-laptop kernel: [42988.205443] ata1.00: configured for 
UDMA/133
  Mar 14 23:00:09 chris-laptop kernel: [42988.205459] ata1: EH complete
  Mar 14 23:00:09 chris-laptop kernel: [42988.280089] ata2: SATA link up 1.5 
Gbps (SStatus 113 SControl 300)
  Mar 14 23:00:09 chris-laptop kernel: [42988.285567] ata2.00: configured for 
UDMA/100
  Mar 14 23:00:09 chris-laptop kernel: [42988.289370] ata2: EH complete

  Every couple of days, this results in data corruption and my
  filesystem being remounted read-only:

  [ 6148.305806] Aborting journal on device sda1-8.
  [ 6148.325011] EXT4-fs error (device sda1): ext4_journal_start_sb: Detected 
aborted journal
  [ 6148.325018] EXT4-fs (sda1): Remounting filesystem read-only
  [ 6148.326702] journal commit I/O error
  [ 6148.330975] EXT4-fs error (device sda1) in ext4_reserve_inode_write: 
Journal has aborted
  [ 6148.462572] __ratelimit: 15 callbacks suppressed

  Those messages generally appear at the end of dmesg after the event,
  just after the "hard resetting link" message. I then have to boot a
  live CD and manually run fsck, as I can no longer boot the laptop.

  This is happening every couple of days generally, although it happened
  3 times in one day last Thursday.

  I did contemplate it being a hardware issue, but I tried running the
  kernel from Karmic for a couple of days, and that worked ok without a
  single error message

  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chr1s  4010 F pulseaudio
   /dev

[Desktop-packages] [Bug 1371091] Re: [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in intel_crtc_wait_for_pending_flips()

[faunris]

** Attachment added: "dmesg by faunris"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1371091/+attachment/4342129/+files/dmesg

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

Title:
  [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in
  intel_crtc_wait_for_pending_flips()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  GPU gets stuck. Frequently after wakeup from sleep, but also during
  normal run.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Thu Sep 18 06:00:32 2014
  DistUpgraded: 2014-09-12 07:00:32,485 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.14, 3.16.0-14-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-08-08 (41 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=8a50e235-2691-4a4a-b587-3bb79f18c59c ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to utopic on 2014-09-12 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Sep 18 06:06:44 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Desktop-packages] [Bug 1371091] Re: [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in intel_crtc_wait_for_pending_flips()

[faunris]

This error was repeated on me a few times with the same situation:
I watched a movie on the site nttp: //kinogo.net in Google Chrome and Xorg 
freezes after about 30 minutes of viewing
My notebook: msi gs 70 2pc (core I7, nvidia gtx 860) 
Ubuntu 14.10 Amd64

syslog:
Mar 12 05:23:54 xxx kernel: [58769.840122] [ cut here ]
Mar 12 05:23:54 xxx kernel: [58769.840188] WARNING: CPU: 0 PID: 1472 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_display.c:3324 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]()
Mar 12 05:23:54 xxx kernel: [58769.840191] Modules linked in: alx mdio ctr ccm 
bbswitch(OE) bnep rfcomm dm_crypt nls_iso8859_1 snd_hda_codec_hdmi 
snd_hda_codec_realtek snd_hda_codec_generic mxm_wmi msi_wmi sparse_keymap 
snd_hda_intel snd_hda_controller intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel arc4 snd_hda_codec kvm snd_hwdep snd_pcm 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_seq_midi 
snd_seq_midi_event aesni_intel snd_rawmidi ath9k aes_x86_64 lrw gf128mul 
glue_helper ath9k_common ablk_helper cryptd ath9k_hw snd_seq joydev ath 
serio_raw ath3k mac80211 btusb bluetooth 6lowpan_iphc snd_seq_device snd_timer 
cfg80211 snd mei_me lpc_ich mei shpchp soundcore wmi mac_hid parport_pc ppdev 
lp parport hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse ahci 
drm libahci video [last unloaded: mdio]
Mar 12 05:23:54 xxx kernel: [58769.840268] CPU: 0 PID: 1472 Comm: Xorg Tainted: 
P   OE 3.16.0-31-generic #41-Ubuntu
Mar 12 05:23:54 xxx kernel: [58769.840272] Hardware name: Micro-Star 
International Co., Ltd. GS70 2PC Stealth/MS-1772, BIOS E1772IMS.10C 10/21/2014
Mar 12 05:23:54 xxx kernel: [58769.840274]  0009 880221677c18 
82782d0b 
Mar 12 05:23:54 xxx kernel: [58769.840280]  880221677c50 8206ff2d 
 880223883000
Mar 12 05:23:54 xxx kernel: [58769.840285]  88021fd98210 8802238eb800 
8802238eb800 880221677c60
Mar 12 05:23:54 xxx kernel: [58769.840290] Call Trace:
Mar 12 05:23:54 xxx kernel: [58769.840303]  [] 
dump_stack+0x45/0x56
Mar 12 05:23:54 xxx kernel: [58769.840312]  [] 
warn_slowpath_common+0x7d/0xa0
Mar 12 05:23:54 xxx kernel: [58769.840318]  [] 
warn_slowpath_null+0x1a/0x20
Mar 12 05:23:54 xxx kernel: [58769.840350]  [] 
intel_crtc_wait_for_pending_flips+0x16c/0x180 [i915]
Mar 12 05:23:54 xxx kernel: [58769.840360]  [] ? 
prepare_to_wait_event+0x100/0x100
Mar 12 05:23:54 xxx kernel: [58769.840391]  [] 
intel_crtc_disable_planes+0x33/0x1c0 [i915]
Mar 12 05:23:54 xxx kernel: [58769.840396]  [] ? 
__ww_mutex_lock+0x1b/0xb0
Mar 12 05:23:54 xxx kernel: [58769.840426]  [] 
haswell_crtc_disable+0x57/0x2d0 [i915]
Mar 12 05:23:54 xxx kernel: [58769.840431]  [] ? 
mutex_lock+0x12/0x30
Mar 12 05:23:54 xxx kernel: [58769.840462]  [] 
intel_crtc_update_dpms+0x67/0xa0 [i915]
Mar 12 05:23:54 xxx kernel: [58769.840494]  [] 
intel_connector_dpms+0x59/0x70 [i915]
Mar 12 05:23:54 xxx kernel: [58769.840524]  [] 
drm_mode_obj_set_property_ioctl+0x399/0x3a0 [drm]
Mar 12 05:23:54 xxx kernel: [58769.840547]  [] 
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
Mar 12 05:23:54 xxx kernel: [58769.840563]  [] 
drm_ioctl+0x1df/0x680 [drm]
Mar 12 05:23:54 xxx kernel: [58769.840572]  [] ? 
brightness_store+0xce/0x100
Mar 12 05:23:54 xxx kernel: [58769.840578]  [] ? 
fsnotify+0x27c/0x350
Mar 12 05:23:54 xxx kernel: [58769.840584]  [] 
do_vfs_ioctl+0x2c8/0x4a0
Mar 12 05:23:54 xxx kernel: [58769.840589]  [] ? 
__sb_end_write+0x31/0x60
Mar 12 05:23:54 xxx kernel: [58769.840594]  [] 
SyS_ioctl+0x81/0xa0
Mar 12 05:23:54 xxx kernel: [58769.840600]  [] 
system_call_fastpath+0x1a/0x1f
Mar 12 05:23:54 xxx kernel: [58769.840603] ---[ end trace 395e59291d098358 ]---
Mar 12 05:24:06 xxx kernel: [58781.198023] Watchdog[14435]: segfault at 0 ip 
7ff20080e476 sp 7ff1f08b66a0 error 6 in chrome[7ff1fc92+5154000]
Mar 12 05:24:16 xxx kernel: [58791.474004] Watchdog[23452]: segfault at 0 ip 
7f7a0fe44476 sp 7f79ffeec6a0 error 6 in chrome[7f7a0bf56000+5154000]

dmesg in attachment
What other information to provide?

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

Title:
  [Dell XPS 13 9333] Xorg crashed with SIGABRT/ WARNING in
  intel_crtc_wait_for_pending_flips()

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  GPU gets stuck. Frequently after wakeup from sleep, but also during
  normal run.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUn

[Desktop-packages] [Bug 396268] Re: Banshee uses too much CPU

[Si Dedman]

Dusting this old thread off, is anyone aware whether the podcast problem
has been fixed?

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

Title:
  Banshee uses too much CPU

Status in Banshee Music Player:
  Confirmed
Status in banshee package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: banshee

  While playing and minimized to the system tray, Banshee uses 65-70%
  CPU and also pushes pulseaudio CPU usage up to around 30%.
  Additionally, when using "next" or "previous" buttons Banshee CPU
  usage goes up to 150%. Importing approximately 6000 songs took over 20
  minutes, although the first 3000 or so only took about 5 minutes.

  System: P4 2.8 Ghz with hyperthreading, 2GB RAM

  Tested with latest Banshee from Jaunty repos and also the Banshee Team
  PPA version.

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

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

[Desktop-packages] [Bug 474514] Re: Banshee very slow when interacting with track lists

[Si Dedman]

Eesh, sorry Chow, I wasn't subscribed to notifications for this! Done
now - run debug script, found a file with an errant tag, edited tag,
saved, waited for CPU to drop, quit banshee, pasted all terminal to text
file, attached.

** Attachment added: "terminal debug output"
   
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/474514/+attachment/4342128/+files/BansheeHighCPU.txt

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

Title:
  Banshee very slow when interacting with track lists

Status in banshee package in Ubuntu:
  Fix Released
Status in sqlite3 package in Ubuntu:
  Invalid
Status in banshee package in Debian:
  Invalid
Status in sqlite3 package in Debian:
  Invalid

Bug description:
  Binary package hint: banshee

  Banshee's great, but since I've added a few more songs it's become
  unbearably slow.

  Scrolling up and down the library is ok, provided it's settled for a
  while, However, whenever a song finishes playing or I rate a track or
  skip a track there's a delay whist 2 of my 8 CPU cores are maxed out.
  The UI takes an age to redraw or respond to clicks. The delay can be
  just half a second, or sometimes around 5. This usually coincides with
  some network activity.

  It makes interacting with the application nearly unbearable. Don't
  want to go back to Rhythmbox, but might have to :(

  I have:
  * Banshee 1.6 Beta 2 (1.5.1)
  * about 5,300 songs in the library
  * Ubuntu 9.10 Karmic 64bit
  * 6Gb of memory and an i7 920 processor

  Banshee extensions running:
  * Audio CD Support
  * Bookmarks
  * Cover Art Fetching
  * DAAP
  * Digital Media Player Support
  * IPod Support
  * Karma Support
  * Mass Storage Media Player Support
  * MTP Media Player Support
  * File System Queue
  * Internet Radio
  * Last.fm Radio & Scrobbling
  * Multimedia Keys
  * Play Queue
  * Importers for Amarok & Rhythmbox
  * Podcasts

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

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

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[nukedathlonman]

Actually looking at my nVidia equipped system, the nVidia packages
installed on it, and my AMD system and the AMD packages installed on it
right now... Thinking about it, shouldn't the AMD driver depend on ocl-
icd-libopencl1 package?  Should the AMD pacakge be broken up into
seperate packages like the nVidia one (which would enable quicker bug
and/or updates to portions of it and such).  Just food for thought.

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

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
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-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Confirmed
Status in fglrx-installer-updates source package in Utopic:
  Confirmed
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/11294

[Desktop-packages] [Bug 601555] Re: Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; skipping entry.

[Bug Watch Updater]

** Changed in: exiv2 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  Error: Directory NikonPreview, entry 0xb3b2 has invalid size
  3115890614*1; skipping entry.

Status in The GNU Image Manipulation Program (GIMP):
  Unknown
Status in exiv2 package in Ubuntu:
  Fix Released
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  Binary package hint: exiv2

  When I start digikam from the command line, it bombs it with
  (thousands?) of messages like:

  [...]
  Warning: Directory NikonPreview, entry 0xb3b2 has unknown Exif (TIFF) type 
46516; setting type size 1.
  Error: Directory NikonPreview, entry 0xb3b2 has invalid size 3115890614*1; 
skipping entry.
  [...]
  Error: Offset of directory NikonPreview, entry 0x00c4 is out of bounds: 
Offset = 0x01010101; truncating the entry
  Warning: Directory NikonPreview, entry 0x0504 has unknown Exif (TIFF) type 
1798; setting type size 1.
  [...]

  According to http://mail.kde.org/pipermail/digikam-
  users/2009-July/007947.html

  It's a problem of libexiv2
  *t

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: libexiv2-6 0.19-1
  ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
  Uname: Linux 2.6.31-21-generic x86_64
  Architecture: amd64
  Date: Sun Jul  4 11:08:10 2010
  ProcEnviron:
   LANGUAGE=de_CH:de
   PATH=(custom, user)
   LANG=de_CH.utf8
   SHELL=/bin/bash
  SourcePackage: exiv2

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

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

[Desktop-packages] [Bug 1427344] Re: cups-browsed crashed with SIGSEGV in timeout_free()

[Till Kamppeter]

Everyone who was able to rreproduce the crash with the old package,
please test with the new package and tell us whether it solves the
problem. Thanks.

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

Title:
  cups-browsed crashed with SIGSEGV in timeout_free()

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  on every boot

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.66-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Mar  2 17:27:28 2015
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2015-01-25 (35 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150125)
  Lpstat: device for HP-Photosmart-C3100-series: 
usb://HP/Photosmart%20C3100%20series?serial=MY6ABC32ND04P9&interface=1
  MachineType: ASUS All Series
  Papersize: a4
  PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 
3.14.6
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=a1f4e400-6d47-4810-8d22-d51139013aa1 ro 
resume=UUID=c756b5d8-0950-4dd7-8532-4932aac06078 quiet splash vga=845
  SegvAnalysis:
   Segfault happened at: 0x7fdf8bc9a15a:movl   $0x1,0xa8(%rax)
   PC (0x7fdf8bc9a15a) ok
   source "$0x1" ok
   destination "0xa8(%rax)" (0x00a8) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1802
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-C
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1802:bd01/28/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[nukedathlonman]

Well, in respect to what I see in the nVidia drivers (nvidia-opencl-
icd-331-updates) and in the AMD drivers, shouldn't there be an enhances
line (Enhances libopencl1) - the AMD driver is afterall providing
enhancements, but in it's base package as opposed to a seperate opencl
pacakge...

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

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
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-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Confirmed
Status in fglrx-installer-updates source package in Utopic:
  Confirmed
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.ne

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[nukedathlonman]

Sorry for pointing that out - I just want to see this fixed right the
first time

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

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
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-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Confirmed
Status in fglrx-installer-updates source package in Utopic:
  Confirmed
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

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

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

[Desktop-packages] [Bug 1431083] Re: soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()

[Apport retracing service]

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

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 #1418551, 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/1431083/+attachment/4342084/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Happened while closing a spreadsheet.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: libreoffice-core 1:4.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Thu Mar 12 00:27:24 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2014-05-05 (310 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc 
file:///home/username/$somefile --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7fbc328f932a <_ZN11Application13GetSolarMutexEv+10>: 
mov0x8(%rax),%rdi
   PC (0x7fbc328f932a) ok
   source "0x8(%rax)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   Application::GetSolarMutex() () from 
/usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
  Title: soffice.bin crashed with SIGSEGV in Application::GetSolarMutex()
  UpgradeStatus: Upgraded to vivid on 2015-03-06 (5 days ago)
  UserGroups: bumblebee cdrom lpadmin plugdev sambashare sudo vboxusers 
wireshark

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

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

[Desktop-packages] [Bug 1159821] Re: Menus of a time set to "12:00:00" are initialised at "00:00:00"

[Bug Watch Updater]

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

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

Title:
  Menus of a time set to "12:00:00" are initialised at "00:00:00"

Status in Shotwell:
  Fix Released
Status in shotwell package in Ubuntu:
  Confirmed

Bug description:
  1. Select any .jpeg file
  2. Photos > Adjust Date and Time...
  3. Set it to "12:00:00" with "24hrs" and click "OK"
  4. Photos > Adjust Date and Time...

  What you should see : the +/- menus should be set at "12:00:00" - "24hrs"
  What you do see : "00:00:00" - "24hrs"

  However, the information recorded seems correct as you see in the left side : 
"Original: 03/25/2013, 12:00:00"
  (see screenshot attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: shotwell 0.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu2
  Architecture: i386
  CasperVersion: 1.330
  Date: Mon Mar 25 14:37:30 2013
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130325)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1431082] Re: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

[Apport retracing service]

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

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 #1431041, 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/1431082/+attachment/4342066/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  cups-browsed crashed with SIGSEGV in g_main_context_dispatch()

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Nouvelle version 13 9 09 : pas de son au démarrage. 
  Bug à mon avis sur l'affichage de ma page météo qui utilise imageMagic  et la 
fabrication de l'écran desktop.
  Je n'utilise pas Unity pour 2 raisons :  Pas de possibilité de déplacer la 
barre des menus vers le bas ou le haut et surtout probième de "couleurs" de la 
video (carte ATI Radeon 4500 series).  L'affichage est très peu contraste et 
devient illisible et très "fade". 
  J'utilise donc Caïro dock avec son module de lumière.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: cups-browsed 1.0.67-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   W [11/Mar/2015:17:29:33 +0100] Notifier for subscription 72 (dbus://) went 
away, retrying!
   W [11/Mar/2015:17:29:33 +0100] Notifier for subscription 74 (dbus://) went 
away, retrying!
   W [11/Mar/2015:17:29:33 +0100] Notifier for subscription 76 (dbus://) went 
away, retrying!
   W [12/Mar/2015:01:07:37 +0100] Notifier for subscription 78 (dbus://) went 
away, retrying!
  Date: Thu Mar 12 01:07:36 2015
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2015-02-28 (11 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  Lpstat: device for HP-Photosmart-C3100-series: 
hp:/usb/Photosmart_C3100_series?serial=MY6ABC531P04P9
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  Papersize: a4
  PpdFiles: HP-Photosmart-C3100-series: HP Photosmart c3100 Series, hpcups 
3.15.2
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic 
root=UUID=a530513c-b7e2-4c21-9a67-dc71aa5547e4 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f44c2d8315a:movl   $0x1,0xa8(%rax)
   PC (0x7f44c2d8315a) ok
   source "$0x1" ok
   destination "0xa8(%rax)" (0x00a8) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups-filters
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.46
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3624
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 18.51
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Pack

[Desktop-packages] [Bug 1429529] Re: Package resolver can't find *-lts-utopic package dependencies, aborts

[Doug McMahon]

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

** This bug has been marked a duplicate of bug 1424466
   Devel package not installable in 14.04.2 (mesa-lts-utopic

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

Title:
  Package resolver can't find *-lts-utopic package dependencies, aborts

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  [Description]
  On Ubuntu 14.04.2 with updated kernel and X stack (LTS Enablement Stacks) 
package resolver fails to find *-lts-utopic package dependencies, aborts.

  [Test case]
  $ sudo apt-get -o debug::pkgproblemresolver=true install qtbase5-dev
  (Log attached as apt.log)

  [Workaround]
  Manually resolve:
  $ sudo apt-get install qtbase5-dev libgles2-mesa-dev-lts-utopic

  Possible catch all solution:
  $ sudo apt-get install .*-dev-lts-utopic

  [Speculation]
  Control file of libgles2-mesa-dev-lts-utopic 10.3.2-0ubuntu1~trusty2 does 
look right imho:
  http://debian-handbook.info/browse/stable/sect.package-meta-information.html

  Guess APT just get overwhelmed by the possibilies and aborts before
  finding the right one.

  Is there some SAT-solver, which could conform? Aptitude's resolver fails, too.
  Could control files be tweaked to make resolving easier?

  [Possible affected packages]
  Possible all packages which have dependencies on *-mesa-dev for which there's 
an updated version in the LTS Enablement Stacks.
  Roughly:
  $ apt-cache rdepends .*-mesa-dev

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

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

[Desktop-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic

[Doug McMahon]

Tested with -proposed enabled a number of apt-get  sims, all looked good. 
freeglut3-dev
libglew-dev
libsdl1.2-dev
libsdl2-dev

So will mark verification-done & dupe related bugs that will be fixed.

There still are a few cases open, one is obscure enough not to warrant a
look? (osmesa is not built in the hwe  mesa), others may need to be
adjusted in the sources (like fglrx-updates, ect.

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

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

Title:
  Devel package not installable in 14.04.2 (mesa-lts-utopic

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

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

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1412036] Re: Korean typing doesn't work

[Gunnar Hjalmarsson]

@Aron: The bug description may not be crystal clear, neither in this bug
report nor the upstream ditto, but I for one can reproduce the problem.
ibus-hangul simply does not work in Utopic and Vivid. Using 14.10 I can
make it work by downgading to ibus-hangul 1.4.2-3 (the trusty version).

** Changed in: ibus-hangul (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  Korean typing doesn't work

Status in IBus:
  Unknown
Status in ibus-hangul package in Ubuntu:
  Triaged

Bug description:
  At the moment I have got "Russian" and "English (UK)" installed on my
  computer. I installed them through "System Settings > Language
  Support". But now I want to add Korean and that is where the problem
  has come up.

  So I go into the "Language Support" settings and click "Install /
  Remove Languages...", I then select "Korean" from the list and click
  "Apply Changes". After the installation has finished I go into the
  Text Entry settings: Text_Entry_GUI.bmp

  And click the little "+" sign. Then I find and add "Korean" from the
  list: Choose_an_input_source_GUI.bmp

  But then when I select "Korean" as the language I want to type as, it
  still stays at English. And not matter what I do, I cannot seem to get
  any other languages working.

  I am running Ubuntu 14.10.

  Package information:

  ibus-hangul:
Installed: 1.4.2+git20140818-1
Candidate: 1.4.2+git20140818-1
Version table:
   *** 1.4.2+git20140818-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[Dan Muresan]

Trusty was affected too by the Conflicts: thing; I've been running
manually-patched fglrx drivers for a while now.

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

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
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-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Confirmed
Status in fglrx-installer-updates source package in Utopic:
  Confirmed
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

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

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

[Desktop-packages] [Bug 1431063] Re: nautilus crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

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 #1295480, 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/1431063/+attachment/4341948/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in g_closure_invoke()

Status in nautilus package in Ubuntu:
  New

Bug description:
  Close and Crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1
  Uname: Linux 3.19.0-8-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 11 20:12:37 2015
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-09-25 (167 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: nautilus -n
  SegvAnalysis:
   Segfault happened at: 0x47aac9:  cmp%rax,(%rdx)
   PC (0x0047aac9) ok
   source "%rax" ok
   destination "(%rdx)" (0x0200) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in g_closure_invoke()
  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/nautilus/+bug/1431063/+subscriptions

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

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

[Apport retracing service]

** Tags removed: need-duplicate-check

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

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

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

Bug description:
  I run Ubuntu 14.04.2 LTS Cinnamon desktop x64, just upgraded my linux
  kernel to 3.19, via:

  "cd /tmp/
  +
  wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb
  +
  wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900_3.19.0-031900.201502091451_all.deb
  +
  wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-image-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb
  +
  sudo dpkg -i linux-headers-3.19.0-*.deb linux-image-3.19.0-*.deb
  +
  sudo reboot"

  The problem I have was reported automatically by my system. So far, I
  haven't noticed any malfunctions myself...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fglrx-updates 2:13.350.1-0ubuntu2
  Uname: Linux 3.19.0-031900-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 3.19.0-031900-generic
  Date: Thu Mar 12 01:11:58 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-47-generic, x86_64: installed
  DuplicateSignature: 
dkms:fglrx-updates:2:13.350.1-0ubuntu2:/var/lib/dkms/fglrx-updates/13.350.1/build/2.6.x/firegl_public.c:4733:5:
 error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ee]
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M] 
[1002:6821] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05ee]
  InstallationDate: Installed on 2014-08-09 (214 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  LightdmGreeterLog:
   (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
  LightdmGreeterLogOld:
   (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
   
   (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: 
assertion 'GTK_IS_CONTAINER (container)' failed
  MachineType: Dell Inc. Inspiron 3737
  PackageVersion: 2:13.350.1-0ubuntu2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=c18e6c5b-cc8a-40d3-98fe-f9721bd79aab ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed 
to build
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0HF1CD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3737:pvrA08:rvnDellInc.:rn0HF1CD:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3737
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Mar 12 01:13:31 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id553

[Desktop-packages] [Bug 1431068] [NEW] fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to build

[Athanassios Strantzalos]

Public bug reported:

I run Ubuntu 14.04.2 LTS Cinnamon desktop x64, just upgraded my linux
kernel to 3.19, via:

"cd /tmp/
+
wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb
+
wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-headers-3.19.0-031900_3.19.0-031900.201502091451_all.deb
+
wget 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/linux-image-3.19.0-031900-generic_3.19.0-031900.201502091451_amd64.deb
+
sudo dpkg -i linux-headers-3.19.0-*.deb linux-image-3.19.0-*.deb
+
sudo reboot"

The problem I have was reported automatically by my system. So far, I
haven't noticed any malfunctions myself...

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx-updates 2:13.350.1-0ubuntu2
Uname: Linux 3.19.0-031900-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSKernelVersion: 3.19.0-031900-generic
Date: Thu Mar 12 01:11:58 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fglrx-updates, 13.350.1, 3.13.0-47-generic, x86_64: installed
DuplicateSignature: 
dkms:fglrx-updates:2:13.350.1-0ubuntu2:/var/lib/dkms/fglrx-updates/13.350.1/build/2.6.x/firegl_public.c:4733:5:
 error: implicit declaration of function ‘__get_cpu_var’ 
[-Werror=implicit-function-declaration]
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05ee]
 Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M] [1002:6821] 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:05ee]
InstallationDate: Installed on 2014-08-09 (214 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
LightdmGreeterLog:
 (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed
 
 (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed
 
 (lightdm-gtk-greeter:2269): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed
LightdmGreeterLogOld:
 (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed
 
 (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed
 
 (lightdm-gtk-greeter:2342): Gtk-CRITICAL **: gtk_container_foreach: assertion 
'GTK_IS_CONTAINER (container)' failed
MachineType: Dell Inc. Inspiron 3737
PackageVersion: 2:13.350.1-0ubuntu2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-031900-generic 
root=UUID=c18e6c5b-cc8a-40d3-98fe-f9721bd79aab ro quiet splash vt.handoff=7
SourcePackage: fglrx-installer-updates
Title: fglrx-updates 2:13.350.1-0ubuntu2: fglrx-updates kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0HF1CD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A08
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3737:pvrA08:rvnDellInc.:rn0HF1CD:rvrA00:cvnDellInc.:ct8:cvrA08:
dmi.product.name: Inspiron 3737
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Mar 12 01:13:31 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5534 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-package third-party-packages trusty ubuntu

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

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

Status in fglrx-install

[Desktop-packages] [Bug 445333] Re: remember password on printing to windows printers does not work

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/gtk+2.0

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Trusty:
  Fix Committed
Status in gtk+3.0 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a "remember password" checkbox, but it keeps asking me when 
printing the next document.

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

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

[Desktop-packages] [Bug 1431058] Re: Stable Release Update to provide possiblity of automatically reporting crashes

[Brian Murray]

** Changed in: apport (Ubuntu)
   Status: New => Invalid

** Changed in: apport (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: apport (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: apport (Ubuntu Trusty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Description changed:

+ [Test Case]
+ ---
+ 1) Install apport-noui
+ 2) Verify /var/lib/apport/autoreport is created
+ 3) sleep 1000 &
+ 4) pkill -11 sleep
+ 5) observe /var/crash/_bin_sleep.crash file
+ 6) wait a wee bit
+ 7) observe /var/crash/_bin_sleep.upload and .uploaded are created
+ 
  The version of apport in Ubuntu 14.04 is missing a few changes that
  would allow users to install apport-noui and allow crash reports to be
  submitted automatically from systems with it installed. The changes are
  the following:
  
-   * debian/apport-noui.upstart: remove early exit (LP: #1235436)
-   * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
-   * data/whoopsie-upload-all: backport utopic version of it
-   * apport-noui: make the package installation automatically enable
- autosubmission, and update the package description accordingly.
- LP: #1351137.
+   * debian/apport-noui.upstart: remove early exit (LP: #1235436)
+   * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
+   * data/whoopsie-upload-all: backport utopic version of it
+   * apport-noui: make the package installation automatically enable
+ autosubmission, and update the package description accordingly.
+ LP: #1351137.
  
  The changes to whoopsie-upload-all can be found in this revision
  (http://bazaar.launchpad.net/~ubuntu-core-
  dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP:
  #1354318.  It would be useful if users of 14.04 could install apport-
  noui and have crash reports automatically submitted for them.

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

Title:
  Stable Release Update to provide possiblity of automatically reporting
  crashes

Status in apport package in Ubuntu:
  Invalid
Status in apport source package in Trusty:
  In Progress

Bug description:
  [Test Case]
  ---
  1) Install apport-noui
  2) Verify /var/lib/apport/autoreport is created
  3) sleep 1000 &
  4) pkill -11 sleep
  5) observe /var/crash/_bin_sleep.crash file
  6) wait a wee bit
  7) observe /var/crash/_bin_sleep.upload and .uploaded are created

  The version of apport in Ubuntu 14.04 is missing a few changes that
  would allow users to install apport-noui and allow crash reports to be
  submitted automatically from systems with it installed. The changes
  are the following:

    * debian/apport-noui.upstart: remove early exit (LP: #1235436)
    * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
    * data/whoopsie-upload-all: backport utopic version of it
    * apport-noui: make the package installation automatically enable
  autosubmission, and update the package description accordingly.
  LP: #1351137.

  The changes to whoopsie-upload-all can be found in this revision
  (http://bazaar.launchpad.net/~ubuntu-core-
  dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP:
  #1354318.  It would be useful if users of 14.04 could install apport-
  noui and have crash reports automatically submitted for them.

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

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

[Desktop-packages] [Bug 1391024] Update Released

[Timo Aaltonen]

The verification of the Stable Release Update for libpwquality 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 libpwquality in Ubuntu.
https://bugs.launchpad.net/bugs/1391024

Title:
  The prompt of Password Strength Meter hasn't been translated.

Status in Ubuntu Translations:
  Fix Committed
Status in Ubuntu Kylin:
  Fix Committed
Status in libpwquality package in Ubuntu:
  Fix Released
Status in libpwquality source package in Trusty:
  Fix Released
Status in libpwquality source package in Utopic:
  Fix Released

Bug description:
  * Impact
  the password meter hints from the user account settings are not translated

  * Test case
  - use unity7 with a non english locale
  - System settings->User Accounts->Unlock
  - Click password
  - place the mouse on the Password Strength Meter
  -> the hint should be translated

  * Impact regression
  Shouldn't be one, there is no code change, it's only for launchpad import of 
the template

  ---

  1. System settings->User Accounts->Unlock
  2. Click password
  3. place the mouse on the Password Strength Meter
  Failed- The prompt of Password Strength Meter hasn't been translated.

  Ubuntukylin-14.10-utopic; 32bit ;lenovo

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

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

[Desktop-packages] [Bug 1391024] Re: The prompt of Password Strength Meter hasn't been translated.

[Launchpad Bug Tracker]

This bug was fixed in the package libpwquality - 1.2.3-1ubuntu1.1

---
libpwquality (1.2.3-1ubuntu1.1) trusty; urgency=medium

  * No change rebuild to get translations imported in launchpad
(lp: #1391024)
 -- Sebastien BacherFri, 06 Feb 2015 15:08:24 +0100

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

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

Title:
  The prompt of Password Strength Meter hasn't been translated.

Status in Ubuntu Translations:
  Fix Committed
Status in Ubuntu Kylin:
  Fix Committed
Status in libpwquality package in Ubuntu:
  Fix Released
Status in libpwquality source package in Trusty:
  Fix Released
Status in libpwquality source package in Utopic:
  Fix Released

Bug description:
  * Impact
  the password meter hints from the user account settings are not translated

  * Test case
  - use unity7 with a non english locale
  - System settings->User Accounts->Unlock
  - Click password
  - place the mouse on the Password Strength Meter
  -> the hint should be translated

  * Impact regression
  Shouldn't be one, there is no code change, it's only for launchpad import of 
the template

  ---

  1. System settings->User Accounts->Unlock
  2. Click password
  3. place the mouse on the Password Strength Meter
  Failed- The prompt of Password Strength Meter hasn't been translated.

  Ubuntukylin-14.10-utopic; 32bit ;lenovo

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

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

[Desktop-packages] [Bug 1391024] Re: The prompt of Password Strength Meter hasn't been translated.

[Launchpad Bug Tracker]

This bug was fixed in the package libpwquality - 1.2.3-1ubuntu1.2

---
libpwquality (1.2.3-1ubuntu1.2) utopic; urgency=medium

  * No change rebuild to get translations imported in launchpad
(lp: #1391024)
 -- Sebastien BacherFri, 06 Feb 2015 15:08:24 +0100

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

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

Title:
  The prompt of Password Strength Meter hasn't been translated.

Status in Ubuntu Translations:
  Fix Committed
Status in Ubuntu Kylin:
  Fix Committed
Status in libpwquality package in Ubuntu:
  Fix Released
Status in libpwquality source package in Trusty:
  Fix Released
Status in libpwquality source package in Utopic:
  Fix Released

Bug description:
  * Impact
  the password meter hints from the user account settings are not translated

  * Test case
  - use unity7 with a non english locale
  - System settings->User Accounts->Unlock
  - Click password
  - place the mouse on the Password Strength Meter
  -> the hint should be translated

  * Impact regression
  Shouldn't be one, there is no code change, it's only for launchpad import of 
the template

  ---

  1. System settings->User Accounts->Unlock
  2. Click password
  3. place the mouse on the Password Strength Meter
  Failed- The prompt of Password Strength Meter hasn't been translated.

  Ubuntukylin-14.10-utopic; 32bit ;lenovo

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

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

[Desktop-packages] [Bug 1431058] [NEW] Stable Release Update to provide possiblity of automatically reporting crashes

[Brian Murray]

Public bug reported:

The version of apport in Ubuntu 14.04 is missing a few changes that
would allow users to install apport-noui and allow crash reports to be
submitted automatically from systems with it installed. The changes are
the following:

  * debian/apport-noui.upstart: remove early exit (LP: #1235436)
  * debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
  * data/whoopsie-upload-all: backport utopic version of it
  * apport-noui: make the package installation automatically enable
autosubmission, and update the package description accordingly.
LP: #1351137.

The changes to whoopsie-upload-all can be found in this revision
(http://bazaar.launchpad.net/~ubuntu-core-
dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP:
#1354318.  It would be useful if users of 14.04 could install apport-
noui and have crash reports automatically submitted for them.

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

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

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

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

Title:
  Stable Release Update to provide possiblity of automatically reporting
  crashes

Status in apport package in Ubuntu:
  New
Status in apport source package in Trusty:
  New

Bug description:
  The version of apport in Ubuntu 14.04 is missing a few changes that
  would allow users to install apport-noui and allow crash reports to be
  submitted automatically from systems with it installed. The changes
  are the following:

* debian/apport-noui.upstart: remove early exit (LP: #1235436)
* debian/apport-noui.dirs: create /var/lib/apport (LP: #1235436)
* data/whoopsie-upload-all: backport utopic version of it
* apport-noui: make the package installation automatically enable
  autosubmission, and update the package description accordingly.
  LP: #1351137.

  The changes to whoopsie-upload-all can be found in this revision
  (http://bazaar.launchpad.net/~ubuntu-core-
  dev/ubuntu/vivid/apport/ubuntu/revision/2351) and they were fixing LP:
  #1354318.  It would be useful if users of 14.04 could install apport-
  noui and have crash reports automatically submitted for them.

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

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

[Desktop-packages] [Bug 1387303] Re: regression: gnome-keyring components can't be disabled anymore

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-keyring - 3.10.1-1ubuntu7.1

---
gnome-keyring (3.10.1-1ubuntu7.1) utopic; urgency=medium

   * Backport changes in user session gnome-keyring jobs up to
 3.14.0-1ubuntu2. (LP: #1387303)
   * Enable gnome-keyring ssh and gpg daemons to appear in "Startup
 Applications".
   * Split gnome-keyring user session job into ssh, gpg, and keyring jobs.
   * Make sure ssh/gpg keyring jobs only start, if not disabled in gui or
 with usptart override.
   * This thus allows to use stock ssh/gpg agents as provided by respective
 upstreams.
 -- Dimitri John LedkovFri, 23 Jan 2015 
19:27:42 +

** Changed in: gnome-keyring (Ubuntu Utopic)
   Status: Fix Committed => Fix Released

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

Title:
  regression: gnome-keyring components can't be disabled anymore

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Trusty:
  Fix Released
Status in gnome-keyring source package in Utopic:
  Fix Released
Status in gnome-keyring source package in Vivid:
  Fix Released

Bug description:
  To disable gnome-keyring ssh agent,
   - disable gnome keyring ssh in startup applications

  To disable gnome-keyring gpg agent,
   - disable gnome keyring gpg in startup applications

  If above are disabled, stock ssh-agent & gpg-agent upstart jobs are
  used instead.

  =
  SRU tests

  By default environment should have SSH & GPG agent variables pointing
  at gnome-keyring provided ones.

  Disabling gpg or ssh gnome keyring desktop files in "Startup
  Applications" upon next login stock gpg/ssh agent's will be used. (No
  gnome-keyring name in the SSH/GPG agent variable values)

  Similarly, disabling upstart jobs for ssh or gpg agent also enables
  stock ssh/gpg agents. (e.g. echo manual > ~/.config/upstart/gnome-
  keyring-ssh.override)

  =

  GNOME Keyring is by default a rather invasive service, which meddles
  with security sensitive processes invasively. This may or may not be
  wise depending on a users situation.

  One particular case is GNOME Keyring's gpg-agent implementation, which
  is incomplete and therefore doesn't support GPG's OpenPGP smartcard
  support. gpg simply fails (with smartcards) when GNOME Keyring is
  impersonating gpg-agent...

  So to be able to use OpenPGP smartcards on Ubuntu, one needs to
  disable GNOME Keyring from impersonating gpg-agent, which for quite
  some time now has been trivial to effectively do:

  echo 'X-GNOME-Autostart-enabled=false' >> /etc/xdg/autostart/gnome-
  keyring-gpg.desktop

  With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this
  seems to have been broken by the addition of:

  /usr/share/upstart/sessions/gnome-keyring.conf

  So it seems the /etc/xdg/autostart/gnome-keyring files are either
  being ignored, or the started process is supplanted by the process
  started by the upstart session config.

  What is unclear to me is what the upstart session configuration is
  supposed to achieve? And if it is meant to supplant the xdg/autostart
  files, those should probably have been removed to prevent them from
  causing any confusion as to how gnome-keyring is started/managed.

  Presuming the upstart session is meant to stay, I would suggest to
  remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent
  confusion as mentioned above. And in my opinion a mechanism should be
  provided so users can control which gnome-keyring components '--
  components=pkcs11,secrets,ssh,gpg' are activated using some
  configuration file in /etc, as files in /usr aren't meant to be user
  edited.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 29 18:14:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-07 (205 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 
2014-04-09T19:49:03.884840

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

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

[Desktop-packages] [Bug 1235915] Re: indicator-keyboard-service crashed with SIGSEGV in xkl_config_rec_get_full_from_server()

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/precise-proposed/lightdm

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

Title:
  indicator-keyboard-service crashed with SIGSEGV in
  xkl_config_rec_get_full_from_server()

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Committed
Status in Light Display Manager 1.4 series:
  Fix Committed
Status in Light Display Manager 1.8 series:
  Fix Committed
Status in indicator-keyboard package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  The bug report details have been generated automatically. I'm not sure if 
this bug happens with lightdm or later on.
  The "System Problem Detected" dialogue box appears about 15 to 20 seconds 
after I've logged in (without me running any apps), so it could be that the 
crash occurs in the lightdm log-in screen but it just takes my system a while 
to collect the bug info?

  Everything appears to work normally after the "System Problem
  Detected" dialogue, so whatever is crashing seems to restart
  gracefully.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 11:15:17 2013
  ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service
  InstallationDate: Installed on 2013-09-28 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard-service --use-gtk 
--use-bamf
  ProcEnviron:
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_GB
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fa5a9482616:mov0x18(%rdx),%rax
   PC (0x7fa5a9482616) ok
   source "0x18(%rdx)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-keyboard
  StacktraceTop:
   ?? () from /usr/lib/libxklavier.so.16
   lightdm_get_layouts () from /usr/lib/liblightdm-gobject-1.so.0
   lightdm_get_layout () from /usr/lib/liblightdm-gobject-1.so.0
   ?? ()
   ?? ()
  Title: indicator-keyboard-service crashed with SIGSEGV in 
lightdm_get_layouts()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic

[Timo Aaltonen]

Hello Doug, or anyone else affected,

Accepted mesa into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/10.1.3-0ubuntu0.4
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

** Package changed: freeglut (Ubuntu) => mesa (Ubuntu)

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

Title:
  Devel package not installable in 14.04.2 (mesa-lts-utopic

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Impact] 
   * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed 
when the lts-utopic stack is used.

  [Test Case]
   * Install the lts-utopic stack.
   * apt-get install ubuntu-sdk
   * Good: you get a whole list of packages to install.
   * Bad: apt-get install fails like pasted in the original bug report.
   * Also test the same without the lts-utopic stack, to make sure there are no 
regressions.

  [Regression Potential] 
   * Low, this has been done for precise before, and mesa packaging has to be 
updated for every LTS release. Unfortunately there are no alternatives. :(

  [Other Info]
   * There's probably an apt bug in here too. Nudging the resolver by 
specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, 
but I didn't find a good way to express this in the depends, and that would 
have to be done for every package.

  [Original bug report]
  Not the first, likely not the last devel to not be installable in 14.04.2 or 
any mesa-lts-utopic install
  Another one is libglew-dev

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

  The following packages have unmet dependencies:
   libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not 
going to be installed
     Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed
   libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going 
to be installed
    Depends: gstreamer1.0-clutter but it is not going to be 
installed
   libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going 
to be installed
  Depends: libcogl15 (>= 1.15.8) but it is not going to be 
installed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: freeglut3-dev (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 22 18:03:30 2015
  InstallationDate: Installed on 2015-02-08 (14 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150203.2)
  SourcePackage: freeglut
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1429771] Re: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned

[Launchpad Bug Tracker]

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

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

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

Title:
  package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade:
  triggers looping, abandoned

Status in gnome-menus package in Ubuntu:
  Confirmed

Bug description:
  During apt-get dist-upgrade, after reboot, this popped out.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: gnome-menus 3.10.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  Date: Mon Mar  9 09:05:09 2015
  DuplicateSignature: package:gnome-menus:3.10.1-0ubuntu5:triggers looping, 
abandoned
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2013-06-20 (626 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  SourcePackage: gnome-menus
  Title: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (483 days ago)

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

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

[Desktop-packages] [Bug 445333] Re: remember password on printing to windows printers does not work

[Timo Aaltonen]

Hello segler, or anyone else affected,

Accepted gtk+2.0 into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+2.0/2.24.23-0ubuntu1.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gtk+2.0 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Trusty:
  Fix Committed
Status in gtk+3.0 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a "remember password" checkbox, but it keeps asking me when 
printing the next document.

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

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

[Desktop-packages] [Bug 1411100] Re: Guest user not removed after guest session ends when using bash as default shell

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/lightdm

** Branch linked: lp:ubuntu/utopic-proposed/lightdm

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

Title:
  Guest user not removed after guest session ends when using bash as
  default shell

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh -> bash*

  But since using Bash as default sh is still a "feature" of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Desktop-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed

[Timo Aaltonen]

Hello rumen, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.5-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

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

Title:
  Daemon end of session/greeter pipes not closed

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes and greeters. This means each session/greeter that is 
created leaks two file descriptors eventually leading to the system stopping it 
from creating new pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

[Desktop-packages] [Bug 778054] Re: Packages shouldn't depend on the transitional package python-gobject

[Timo Aaltonen]

Hello Fred, or anyone else affected,

Accepted zeitgeist into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/zeitgeist/0.9.14-0ubuntu4.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: zeitgeist (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  Packages shouldn't depend on the transitional package python-gobject

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in desktopcouch package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in gnome-utils package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in wine1.4 package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  Fix Released
Status in aptdaemon source package in Trusty:
  Fix Released
Status in desktopcouch source package in Trusty:
  Invalid
Status in eglibc source package in Trusty:
  Invalid
Status in gnome-utils source package in Trusty:
  Invalid
Status in libreoffice source package in Trusty:
  Fix Released
Status in openoffice.org source package in Trusty:
  Invalid
Status in system-config-printer source package in Trusty:
  Fix Released
Status in wine1.4 source package in Trusty:
  Invalid
Status in zeitgeist source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  python-zeitgeist depends on python-gobject, which means python-gobject
  cannot be removed from the system. python-gobject is a transitional
  package, and packages should be updated to no longer depend on it.

  [Test Case]

  * Install python-zeitgeist, and verify that python-gobject is not
  installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing python-zeitgeist.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

  ---

  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

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

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

[Desktop-packages] [Bug 1411100] Please test proposed package

[Timo Aaltonen]

Hello Schlomo, or anyone else affected,

Accepted lightdm into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.10.5-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Guest user not removed after guest session ends when using bash as
  default shell

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh -> bash*

  But since using Bash as default sh is still a "feature" of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Desktop-packages] [Bug 1405794] Re: /usr/share/backgrounds/Water_web_by_Tom_Kijas.jpg has executable permissions set by default.

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-wallpapers - 15.04.0-0ubuntu1

---
ubuntu-wallpapers (15.04.0-0ubuntu1) vivid; urgency=medium

  * Remove +x from Water_web_by_Tom_Kijas (LP: #1405794)
  * Import Vivid wallpapers and create package (LP: #1429011)
  * Update default wallpaper, and add 'alternative' official wallpaper.
  * Update copyright file to account for copyright of default wallpaper and
extend year to 2015.
 -- Iain LaneWed, 11 Mar 2015 16:31:56 +

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

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

Title:
  /usr/share/backgrounds/Water_web_by_Tom_Kijas.jpg has executable
  permissions set by default.

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  /usr/share/backgrounds/Water_web_by_Tom_Kijas.jpg has executable
  permissions set by default. This file is part of the ubuntu-
  wallpapers-trusty_14.04.0.1-0ubuntu1_all package.

  Clearly as a background image/desktop wallpaper this file should not
  have executable privileges. I have checked the file with ClamTk  5.10
  which reports no problems.

  I'm flagging this as a security bug because jpg files can be used as
  an attack vector. But it's likely just a mistake in the packaging of
  the file.

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

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

[Desktop-packages] [Bug 1429011] Re: 15.04 wallpapers package

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-wallpapers - 15.04.0-0ubuntu1

---
ubuntu-wallpapers (15.04.0-0ubuntu1) vivid; urgency=medium

  * Remove +x from Water_web_by_Tom_Kijas (LP: #1405794)
  * Import Vivid wallpapers and create package (LP: #1429011)
  * Update default wallpaper, and add 'alternative' official wallpaper.
  * Update copyright file to account for copyright of default wallpaper and
extend year to 2015.
 -- Iain LaneWed, 11 Mar 2015 16:31:56 +

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  15.04 wallpapers package

Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  This is the bug we'll attach the wallpapers to for the 15.04 release
  ;)

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

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

[Desktop-packages] [Bug 1190344] Re: Daemon end of session/greeter pipes not closed

[Timo Aaltonen]

Hello rumen, or anyone else affected,

Accepted lightdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  Daemon end of session/greeter pipes not closed

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]
  LightDM doesn't close the server side end of the pipes used to communicate 
with session processes and greeters. This means each session/greeter that is 
created leaks two file descriptors eventually leading to the system stopping it 
from creating new pipes.

  [Test Case]
  1. Start LightDM
  2. Check how many pipes are open
  # lsof -p {lightdm_pid} | grep FIFO | wc -l
  3. Create sessions by either cycling between users in Unity Greeter or 
logging in and out
  4. Check how many pipes exist using step 2.
  Expected result:
  No more pipes should be open
  Observed result:
  Many pipes remain open

  [Regression Potential]
  Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

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

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

[Desktop-packages] [Bug 1383321] Re: Support XDG DesktopNames field in session files

[Timo Aaltonen]

Hello Robert, or anyone else affected,

Accepted lightdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

[Desktop-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

[Timo Aaltonen]

Hello Egon, or anyone else affected,

Accepted lightdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags removed: verification-done

** Tags added: verification-needed

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

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in gdm package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in gdm source package in Trusty:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in gdm source package in Utopic:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Committed
Status in gdm package in Debian:
  New

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Desktop-packages] [Bug 1411100] Re: Guest user not removed after guest session ends when using bash as default shell

[Timo Aaltonen]

Hello Schlomo, or anyone else affected,

Accepted lightdm into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lightdm/1.12.3-0ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: verification-needed

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

Title:
  Guest user not removed after guest session ends when using bash as
  default shell

Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Precise:
  Triaged
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Committed

Bug description:
  The /usr/sbin/giest-account script contains a bug which prevents the
  removal of guest accounts:

  $ sudo /usr/sbin/guest-account remove guest-Hhiook
  /usr/sbin/guest-account: line 129: UID: readonly variable

  Maybe this is related to /bin/sh actually beeing a Bash:

  $ ll -d /bin/sh
  lrwxrwxrwx 1 root root 4 Jan  1 01:44 /bin/sh -> bash*

  But since using Bash as default sh is still a "feature" of Ubuntu, all
  scripts should work with both.

  Running the script with dash actually works:

  $ sudo dash /usr/sbin/guest-account remove guest-ZWCtva
  umount: /tmp/guest-ZWCtva: mountpoint not found
  umount: /tmp/guest-ZWCtva: mountpoint not found
  Removing user `guest-ZWCtva' ...
  Warning: group `guest-ZWCtva' has no more members.
  Done.

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

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

[Desktop-packages] [Bug 1393169] Re: [Toshiba Satellite Pro C650] Double mouse cursor

[Gianni Andreoli]

i have an acer v3 571 g, with intel hd 4000 and nvidia 710m, the bug
appear only with intel hd 4000

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

Title:
  [Toshiba Satellite Pro C650] Double mouse cursor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Last up to date Xubuntu 64 bits installed on a laptop

  Since 2 days, the mouse cursor is double with only the left part as
  active and a bar just behing of both arrow (see picture joined).

  I tried to change the theme but no way to go back to a normal mouse
  cursor

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 16 11:12:21 2014
  InstallationDate: Installed on 2013-01-03 (681 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
  InstallationDate: Installed on 2013-01-03 (695 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: TOSHIBA Satellite Pro C650
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Tags:  utopic ubuntu
  Uname: Linux 3.16.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/01/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite Pro C650
  dmi.product.version: PSC09E-00R01YMV
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov 28 08:29:52 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log

[Desktop-packages] [Bug 1383321] Re: Support XDG DesktopNames field in session files

[Timo Aaltonen]

noone tested this on utopic yet?

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

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Committed
Status in lightdm source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  LightDM doesn't support the XDG standard "DesktopNames" field in session 
.desktop files. Instead we only support X-LightDM-DesktopName which was used 
before the standard was set. Newer sessions might expect DesktopNames to work.

  [Test Case]
  1. Install a session which has DesktopNames set in 
/usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity;
  2. Start this session
  Expected result:
  XDG_CURRENT_DESKTOP is set to GNOME:Unity
  Observed result:
  XDG_CURRENT_DESKTOP is not set

  [Regression Potential]
  Low. This feature is only activated if the field is set.

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

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

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

[Michael Markstaller]

Same problem: I'd love a way to permanently disable this whole useless,
closed source Nvidia-crap forever!

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

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

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Triaged

Bug description:
  **WARNING:** This bug has been widely reported and has *many*
  automatic subscribers. Please be considerate.

  **If you need help:** try searching and asking on
  http://discourse.ubuntu.com or http://ubuntuforums.org or contacting a
  nearby user group (see http://loco.ubuntu.com or search for "LUG" in
  your area). Link back to this bug for clarity.

  ---

  This seems to fix it (at least for one version upgrade) for many
  people

  $ sudo dpkg-reconfigure nvidia-331

  after that...

  $ sudo dpkg-reconfigure nvidia-331-uvm

  (some users may be on the versions of these packages suffixed with
  -updates )

  ---

  **If you want to unsubscribe:** see
  https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
  drivers-331-updates/+bug/1268257/+subscribe. You can also change your
  settings so you don't get comments but do get notified when the bug is
  solved - see https://askubuntu.com/questions/576523 for details.

  **If you want to comment:** Please consider if you have something
  meaningful to contribute to the 2500+ people who will get an email.

  **If you are an Ubuntu developer:** thanks for looking into this! :D

  

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

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

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

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

[Desktop-packages] [Bug 1412036] Re: Korean typing doesn't work

[Aron Xu]

Not a bug, please select Hangul as the backend to be able to input
Korean characters.

** Changed in: ibus-hangul (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Korean typing doesn't work

Status in IBus:
  Unknown
Status in ibus-hangul package in Ubuntu:
  Invalid

Bug description:
  At the moment I have got "Russian" and "English (UK)" installed on my
  computer. I installed them through "System Settings > Language
  Support". But now I want to add Korean and that is where the problem
  has come up.

  So I go into the "Language Support" settings and click "Install /
  Remove Languages...", I then select "Korean" from the list and click
  "Apply Changes". After the installation has finished I go into the
  Text Entry settings: Text_Entry_GUI.bmp

  And click the little "+" sign. Then I find and add "Korean" from the
  list: Choose_an_input_source_GUI.bmp

  But then when I select "Korean" as the language I want to type as, it
  still stays at English. And not matter what I do, I cannot seem to get
  any other languages working.

  I am running Ubuntu 14.10.

  Package information:

  ibus-hangul:
Installed: 1.4.2+git20140818-1
Candidate: 1.4.2+git20140818-1
Version table:
   *** 1.4.2+git20140818-1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1393169] Re: [Toshiba Satellite Pro C650] Double mouse cursor

[Christopher M. Penalver]

** Summary changed:

- Double mouse cursor
+ [Toshiba Satellite Pro C650] Double mouse cursor

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

Title:
  [Toshiba Satellite Pro C650] Double mouse cursor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Last up to date Xubuntu 64 bits installed on a laptop

  Since 2 days, the mouse cursor is double with only the left part as
  active and a bar just behing of both arrow (see picture joined).

  I tried to change the theme but no way to go back to a normal mouse
  cursor

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 16 11:12:21 2014
  InstallationDate: Installed on 2013-01-03 (681 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
  InstallationDate: Installed on 2013-01-03 (695 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: TOSHIBA Satellite Pro C650
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Tags:  utopic ubuntu
  Uname: Linux 3.16.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/01/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite Pro C650
  dmi.product.version: PSC09E-00R01YMV
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov 28 08:29:52 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.

[Desktop-packages] [Bug 1300557] Re: Screen resolution no longer works

[Christopher M. Penalver]

Jeroen T. Vermeulen, could you please advise what packages were upgraded
precisely on 2014-04-01 that correlates to this issue?

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

Title:
  Screen resolution no longer works

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My display's native resolution is 2560×1440 pixels.  Prior to, I
  think, Saucy I could only reach this resolution by adding it using
  xrandr, and then calling xrandr on boot/login to select that
  resolution.  The Display preferences did not show any higher options
  than 1920×1200.

  In Saucy, the native resolution just worked, and I could stop using
  xrandr.  It also worked in Trusty in the alpha releases, up to (and I
  think including) beta-1.  But today (this is not an April's fool, is
  it?) I rebooted after an upgrade, and found myself back in 1920×1200.
  Again, the Display preferences list that resolution as the highest
  possible.  But this time, attempts to ‘xrandr --addmode’ my native
  resolution failed.

  The error message wasn't very helpful; I'll try to reproduce it later
  but it throws my display into yet a lower resolution that's hard to
  work with.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:59:00 2014
  DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2013-08-03 (240 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago)
  dmi.bios.date: 05/16/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z87-D3HP
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr  1 09:52:36 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16510
   vendor DEL
  xserver.version: 2:1.15.0-1ubuntu7

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

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

[Desktop-packages] [Bug 1424864] Re: Xorg crash

[Christopher M. Penalver]

Galen Thurber, please see
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1424864/comments/13
.

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Xorg crashing out & back into login manager
  and apport failed
  This problem report is damaged and cannot be processed.

  IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpXYLMdA is
  truncated: expected core file size >= 75243520, found: 6356992.',)

  openConnection: connect: No such file or directory
  cannot connect to brltty at :0
  xfce4-settings-helper: Another instance is already running. Leaving...

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

  (polkit-gnome-authentication-agent-1:9183): 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

  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations
  ERROR: Error querying target relations

  (xfce4-settings-helper:9229): xfce4-settings-helper-WARNING **: Failed to get 
the _NET_NUMBER_OF_DESKTOPS property.
  ** Message: applet now removed from the notification area
  ** Message: using fallback from indicator to GtkStatusIcon
  ** Message: applet now embedded in the notification area
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32:
  assertion `G_IS_FILE_INFO (info)' failed

  (Thunar:9173): GLib-GIO-CRITICAL **: g_file_info_get_attribute_uint32: 
assertion `G_IS_FILE_INFO (info)' failed
  WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-P0TMTU/pkcs11: No 
such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Mon Feb 23 19:14:16 2015
  InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140205)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[Graham Inggs]

@LocutusOfBorg: I don't know for sure that Trusty is affected, but
fglrx-installer has been marked as being affected by this bug since
before Trusty was released.  Also, there are specific reports about
14.04 in duplicate bug LP: #1376587.

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

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
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-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Confirmed
Status in fglrx-installer-updates source package in Utopic:
  Confirmed
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

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

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

[Desktop-packages] [Bug 1393169] Re: Double mouse cursor

[Gianni Andreoli]

the affect every ubuntu 14.04.2 (xubuntu, ubuntu gnome...) distribution
and release

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

Title:
  Double mouse cursor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Last up to date Xubuntu 64 bits installed on a laptop

  Since 2 days, the mouse cursor is double with only the left part as
  active and a bar just behing of both arrow (see picture joined).

  I tried to change the theme but no way to go back to a normal mouse
  cursor

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Nov 16 11:12:21 2014
  InstallationDate: Installed on 2013-01-03 (681 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
 Subsystem: Toshiba America Info Systems Device [1179:fde0]
  InstallationDate: Installed on 2013-01-03 (695 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1659): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to load background: 
Impossible d'ouvrir le fichier « 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg » : Permission 
non accordée
   
   ** (lightdm-gtk-greeter:1641): WARNING **: Failed to read wallpaper: 
/home/christophe/Dropbox/Personnalisation/Fonds d'écran/bleu.jpg
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: TOSHIBA Satellite Pro C650
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=7bc86e4b-720d-4f1c-bb66-a4c08ffc1359 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1
  Tags:  utopic ubuntu
  Uname: Linux 3.16.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/01/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.30:bd07/01/2010:svnTOSHIBA:pnSatelliteProC650:pvrPSC09E-00R01YMV:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite Pro C650
  dmi.product.version: PSC09E-00R01YMV
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Fri Nov 28 08:29:52 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 

[Desktop-packages] [Bug 1430759] Re: Software center does not show up configuration dialogue for applications that needs configuration at install time

[Launchpad Bug Tracker]

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

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

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

Title:
  Software center does not show up configuration dialogue for
  applications that needs configuration at  install time

Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  When I try to install lirc with Ubuntu Software Center, lirc remaining
  unconfigure because here does not show up configuration window for
  lirc package. (same same behavior for another applications that needs
  configuration on install e.g. tvtime)

  This problem does not occur when I try to install lirc from
  commandline with "sudo apt-get install lirc". See screenshot.

  Steps to reproduce (example):

  - Open Ubuntu Software Center
  - Try to install tvtime (or lirc)

  Expected result:

  - An configuration dialogue shown to enter same options, after which
  the changed would be applied.

  Actual result:

  - Software center does not show up configuration dialogue and freezes
  while installing. As results users that use Ubuntu Software Center to
  install this apllication report same bugs:

  https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1374762
  https://bugs.launchpad.net/ubuntu/+source/tvtime/+bug/1428681

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

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

[Desktop-packages] [Bug 1424509] Re: lsclusters claims clusters are not running, when they are under systemd

[Martin Pitt]

That is indeed strange. Yesterday I fixed two bugs (bug 1429734 and
https://launchpad.net/ubuntu/+source/postgresql-common/166bzr2) which
both caused the 9.4-main cluster to not start after package
installation. To make sure it's not that, can you re-try with latest
vivid? (p-common should land within the hour now, it was stuck in
-proposed for a while).

Otherwise, are these clusters *really* running? Check with "ps aux|grep
post"? Can you please give me the output of "systemctl status -l
postgresql@9.4-main.service", and "ls -la /var/run/postgresql/"?

** Changed in: postgresql-common (Ubuntu)
   Status: New => Incomplete

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

Title:
  lsclusters claims clusters are not running, when they are under
  systemd

Status in postgresql-common package in Ubuntu:
  Incomplete

Bug description:
  $ pg_lsclusters 
  Ver Cluster Port Status OwnerData directory   Log file
  9.4 main5432 down   postgres /var/lib/postgresql/9.4/main 
/var/log/postgresql/postgresql-9.4-main.log
  9.4 xnox5433 down   postgres /var/lib/postgresql/9.4/xnox 
/var/log/postgresql/postgresql-9.4-xnox.log

  yet

  $ sudo systemctl list-units 'postgresql*'
  UNITLOAD   ACTIVE SUB DESCRIPTION
  postgresql.service  loaded active exited  PostgreSQL RDBMS
  postgresql@9.4-main.service loaded active running PostgreSQL Cluster 9.4-main
  postgresql@9.4-xnox.service loaded active running PostgreSQL Cluster 9.4-xnox

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: postgresql-common 166bzr1
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  Uname: Linux 3.18.0-9-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb 23 02:57:52 2015
  InstallationDate: Installed on 2013-08-29 (542 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829)
  PackageArchitecture: all
  SourcePackage: postgresql-common
  UpgradeStatus: Upgraded to vivid on 2014-11-16 (98 days ago)

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

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

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[LocutusOfBorg]

Hi Graham,
are you sure trusty is affected? I grabbed today a debian directory and seemed 
not affected, but I might be wrong!
BTW thanks for the proposed mapping hint, it will simplify the overall process 
:-)

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

Title:
  Nvidia and AMD graphics drivers should indicate whether they provide
  libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
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-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Confirmed
Status in fglrx-installer-updates source package in Trusty:
  Confirmed
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Confirmed
Status in fglrx-installer-updates source package in Utopic:
  Confirmed
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

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

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

[Desktop-packages] [Bug 1431012] [NEW] network-manager, "edit connections" + "connect" + "disconnect" functions are disabled

[Kaiser Alexander]

Public bug reported:

Some important functions in network-manager are grayed out: 
* "edit connections" 
* "connect" 
* "disconnect" 

To resolve the problem: 
* When i start "nm-connection-editor" in terminal as normal user it's possible 
to edit all interfaces without any problems. 
* When i start "users-admin" in terminal as normal user, press button "advanced 
settings" and enter my password, then the functions "edit connections" + 
"connect" + "disconnect" are possible to operate and not grayed any more untile 
a reboot! 

I already set my user to user-group "netdev", but nothing happened. 
I tryed to "dpkg-reconfigure network-manager" and "/etc/init.d/network-manager 
restart", but nothing happened. 


"lsb_release -rd": 
Description:Ubuntu 12.04.5 LTS
Release:12.04

"apt-cache policy network-manager": 
network-manager:
  Installiert: 0.9.4.0-0ubuntu4.4.1
  Kandidat:0.9.4.0-0ubuntu4.4.1
  Versionstabelle:
 *** 0.9.4.0-0ubuntu4.4.1 0
500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
100 /var/lib/dpkg/status
 0.9.4.0-0ubuntu3 0
500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages


ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.4.1
ProcVersionSignature: Ubuntu 3.2.0-77.112-generic-pae 3.2.66
Uname: Linux 3.2.0-77-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: i386
Date: Wed Mar 11 20:57:48 2015
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
IpRoute:
 default via 192.168.178.1 dev eth0  proto static 
 169.254.0.0/16 dev eth0  scope link  metric 1000 
 192.168.178.0/24 dev eth0  proto kernel  scope link  src 192.168.178.92  
metric 1
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=de_DE:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2012-11-18T15:36:47
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/1  
 wlan0  802-11-wireless   unavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.4.0connected   enabled   disabled
disabled   enabled disabled

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


** Tags: apport-bug i386 precise

** Attachment added: "Print-Screen"
   
https://bugs.launchpad.net/bugs/1431012/+attachment/4341839/+files/nm-applet_printscreen_01.png

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

Title:
  network-manager, "edit connections" + "connect" + "disconnect"
  functions are disabled

Status in network-manager package in Ubuntu:
  New

Bug description:
  Some important functions in network-manager are grayed out: 
  * "edit connections" 
  * "connect" 
  * "disconnect" 

  To resolve the problem: 
  * When i start "nm-connection-editor" in terminal as normal user it's 
possible to edit all interfaces without any problems. 
  * When i start "users-admin" in terminal as normal user, press button 
"advanced settings" and enter my password, then the functions "edit 
connections" + "connect" + "disconnect" are possible to operate and not grayed 
any more untile a reboot! 

  I already set my user to user-group "netdev", but nothing happened. 
  I tryed to "dpkg-reconfigure network-manager" and 
"/etc/init.d/network-manager restart", but nothing happened. 

  
  "lsb_release -rd": 
  Description:  Ubuntu 12.04.5 LTS
  Release:  12.04
  
  "apt-cache policy network-manager": 
  network-manager:
Installiert: 0.9.4.0-0ubuntu4.4.1
Kandidat:0.9.4.0-0ubuntu4.4.1
Versionstabelle:
   *** 0.9.4.0-0ubuntu4.4.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   0.9.4.0-0ubuntu3 0
  500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu4.4.1
  ProcVersionSignature: Ubuntu 3.2.0-77.112-generic-pae 3.2.66
  Uname: Linux 3.2.0-77-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Wed Mar 11 20:57:48 2015
  Instal

[Desktop-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Tony Espy]

** Attachment added: "NM log messages from network-test-session_20150603_102306"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425987/+attachment/4341813/+files/nmlog-lp1425987.txt

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Tony Espy]

I need some confirmation from Mathieu before I change this bug to
Confirmed and re-title it...

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1425987] Re: Cellular data connection stops after a while

[Tony Espy]

So it looks you indeed have hit #1418077.

This is pretty obvious by looking in the attached nmlog file, and search
for connection '/208150102671184/context1'.  You'll see it get disabled
at 18:41:24 after a bunch of failed attempts ( modem-no-carrier ).  It
gets successfully auto-activated again in +5m.

That said, I also see something else that concerns me.

If you look at the netlog, after '/208150102671184/context1' is
disabled, you'll see NM try a 'context3', 'context5', and 'context1'
again.  The odd thing is that the related IMSI is not '208150102671184'
it's '208103698221268'.   Looking at network-test-session.log ( also
attached ), you'll see that '208150102671184' is the IMSI for ril_0, and
that ril_1 is PIN-locked.   It appears to me that NM may be trying
contexts from other SIM directories it finds in /var/lib/ofono/.

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

Title:
  Cellular data connection stops after a while

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-25 15:06:29
  version version: 122
  version ubuntu: 20150225
  version device: 20150210-95b6a9f
  version custom: 20150225

  Test Case:
  1. Disable Wifi
  2. Verify that a cellular data connection is established
  3. Wait...

  Actual result
  After a while (several minutes) the cellular data connection stops, 
eventually it'll come back but not always.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Thu Feb 26 16:14:14 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2015-02-25 (1 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150225-020204)
  IpRoute:
   
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-25T03:31:54
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.

[Gunnar Hjalmarsson]

@Mark: That sounds like a MATE specific issue, related to an Ubuntu
version where MATE was not an official flavour. Does it exist a mate-
user-guide package, and do you have it installed? Probably you should
ask the MATE team for help.

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

Title:
  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

Status in yelp package in Ubuntu:
  Incomplete

Bug description:
  after upgrading to 14.10 alpha 2 when i try to launch yelp from
  command or from menu it shows

  The URI ‘help:ubuntu-help/index’ does not point to a valid page.

  even when i try to search it shows the same

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: yelp 3.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Aug 24 11:53:45 2014
  InstallationDate: Installed on 2012-03-24 (882 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120324)
  SourcePackage: yelp
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago)

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

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

[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

[Graham Inggs]

@LocutusOfBorg: We don't need to write 'utopic-proposed' anymore,
uploads are automatically mapped.

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

** Also affects: fglrx-installer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-cuda-toolkit (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: starpu-contrib (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: fglrx-installer-updates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-graphics-drivers-304 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-310-updates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-313-updates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-319 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-319-updates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-340 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Also affects: fglrx-installer (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-cuda-toolkit (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: starpu-contrib (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

** Also affects: fglrx-installer-updates (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-graphics-drivers-304 (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-310-updates (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-313-updates (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-319 (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-319-updates (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-340 (Ubuntu Utopic)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Changed in: boinc (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-cuda-toolkit (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-cuda-toolkit (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-310-updates (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-310-updates (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-313-updates (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-313-updates (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-319 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-319 (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu Utopic)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: nvidi

[Desktop-packages] [Bug 221288] from: Cameron Dale

[Cameron Dale]

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


Hi


http://srisivan.com/product.php?chance=ksaqac67zmhdu6x7xaw


Cameron Dale

Sent from my iPhone

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

Title:
  gutsy->hardy bittornado broken

Status in bittornado package in Ubuntu:
  Incomplete

Bug description:
  After upgarding from Gutsy to Hardy, by adjusting sources.list and upgrading 
all packages in Synaptic.
  The commands Bittornado and Bittornado-gui are no longer found.
  A reinstall of the two packages didn't fix the problem.

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

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

[Desktop-packages] [Bug 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze

[Arhiiivs]

Wow! It actually works!
Thanks a lot Tomasz! 
I hope this also helps others wth this problem and also the Ubuntu developers 
to find the reasons behind this error. It has been an issue for a while now...

Greets.

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

Title:
  ubuntu 14.04 after install nvidia binary driver  331.89  black screen
  and freeze

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 14.04 64bit, after install nvidia binary driver
  331.89 from Additional Drivers application then reboot, it shows black
  screen, no login window, I even can't use ctrl+alt+F2 to switch to
  text mode, then I reboot and go to recovery mode, use 'prime-select
  intel' to switch to intel GPU and reboot, everything is fine, but as
  soon as I switch to nvidia GPU, still same issue.

  OS: Ubuntu 14.04 64bit
  Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600
  Desktop: Unity
  Kernel: 3.13.0
  CPU: Intel® Core™ i7-4700MQ

  Thanks!

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

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