[Desktop-packages] [Bug 1392201] [NEW] disk encryption does not allow to enter password at boot

[Michael Zimmermann]

Public bug reported:

The boot screen shows the password field, bit no input is possible.
Powering off and starting in text mode allows the password input. This
happenedafter upgrade to 14.10 in a VirtualBox environment.

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Package changed: unity-control-center (Ubuntu) => ubuntu

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

Title:
  disk encryption does not allow to enter password at boot

Status in Ubuntu:
  New

Bug description:
  The boot screen shows the password field, bit no input is possible.
  Powering off and starting in text mode allows the password input. This
  happenedafter upgrade to 14.10 in a VirtualBox environment.

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

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

[Desktop-packages] [Bug 1392198] [NEW] unity-control center does not start after upgrade to unicorn

[Michael Zimmermann]

Public bug reported:

michaelz@michaelz-XPS-12-9Q23:~$ unity-control-center

(unity-control-center:6132): Gdk-ERROR **: The program 'unity-control-center' 
received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 206 error_code 11 request_code 149 (unknown) minor_code 2)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)
michaelz@michaelz-XPS-12-9Q23:~$

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu2
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: Unity
Date: Thu Nov 13 08:42:12 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-12-10 (703 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to utopic on 2014-11-11 (2 days ago)
usr_lib_unity-control-center: deja-dup 32.0-0ubuntu1

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


** Tags: amd64 apport-bug utopic

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

Title:
  unity-control center does not start after upgrade to unicorn

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

Bug description:
  michaelz@michaelz-XPS-12-9Q23:~$ unity-control-center

  (unity-control-center:6132): Gdk-ERROR **: The program 'unity-control-center' 
received an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 206 error_code 11 request_code 149 (unknown) minor_code 2)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/Breakpoint ausgelöst (Speicherabzug geschrieben)
  michaelz@michaelz-XPS-12-9Q23:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu2
  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: Unity
  Date: Thu Nov 13 08:42:12 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-12-10 (703 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to utopic on 2014-11-11 (2 days ago)
  usr_lib_unity-control-center: deja-dup 32.0-0ubuntu1

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

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

[Desktop-packages] [Bug 1373776] Re: internal panel brightness set to 0 when switching back to internal-only mode

[Anthony Wong]

** Also affects: hwe-next/trusty
   Importance: Undecided
   Status: New

** Changed in: hwe-next
   Status: New => Fix Released

** Changed in: hwe-next/trusty
   Status: New => Fix Released

** Changed in: hwe-next
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: hwe-next/trusty
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  internal panel brightness set to 0 when switching back to internal-
  only mode

Status in HWE Next Project:
  Fix Released
Status in HWE Next trusty series:
  Fix Released
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-intel” source package in Trusty:
  Fix Released

Bug description:
  [Impact]

  the brightness of the internal panel can get set to the lowest value
  when going through the display modes and back to internal-only mode

  this is fixed in a later upstream release, but that can't be
  backported so a distro patch is needed

  [Test case]

  use the laptop hotkey to switch between modes until you get a blank
  internal panel

  [Regression potential]

  slim, the patch is simple enough

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

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

[Desktop-packages] [Bug 1372868] Re: The "Restore Behaviour Settings" function doesn't work for "Add show desktop icon to the launcher"

[Anthony Wong]

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

** Changed in: ubuntukylin
   Importance: Undecided => Medium

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

Title:
  The "Restore Behaviour Settings" function doesn't work for "Add show
  desktop icon to the launcher"

Status in Ubuntu Kylin:
  New
Status in “unity-control-center” package in Ubuntu:
  New

Bug description:
  The "Restore Behaviour Settings" function doesn't work for "Add show
  desktop icon to the launcher".

  Steps:
  1. Enter into System settings-->Appearance-->Behaviour
  2. Change the setting of Add show desktop icon to the launcher
  3. Click the Restore Behaviour Settings
  4. Check the status of Add show desktop icon to the launcher
  -->Failed. The status of Add show desktop icon to the launcher didn't change

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu Kylin Utopic 14.10 

  系统设置-外观--行为--“恢复默认行为”按钮不起作用

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

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

[Desktop-packages] [Bug 1389099] Re: microphone mute icon support

[Ara Pulido]

Is this fixed in Vivid?

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

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

Title:
  microphone mute icon support

Status in OEM Priority Project:
  Incomplete
Status in OEM Priority Project trusty series:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “unity-settings-daemon” source package in Trusty:
  New

Bug description:
  When we press mic mute key(XF86AudioMicMute, in some HP's notebook,
  it's Fn+F8), the notification shows sound mute icon, not mic mute
  icon. To simulate XF86AudioMicMute, you can run "xdotool key
  XF86AudioMicMute".

  My investigation:
  In the file: gsd-media-keys-manager.c, there's no icons[] array for mic mute, 
there're only volume_icons, brightness_icons, kb_backlight_icons. We should add 
detection functions for mic volume.

  Also we need icon files for mic volume. File name should be something
  like notification-audio-input-microphone-low-zero, notification-audio-
  input-microphone-high and located in /usr/share/notify-
  osd/icons/gnome/scalable/status (offered by notify-osd-icons package).

  Packages:
  unity-settings-daemon_14.04.0+14.04.20140414-0ubuntu1_amd64.deb

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

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

[Desktop-packages] [Bug 1306513] Re: 计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Ubuntu Kylin live session

[shijing]

the language package was not update in 1504 dailybuild iso .
version number is 20141020

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

Title:
  计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under
  Ubuntu Kylin live session

Status in Ubuntu Translations:
  New
Status in Ubuntu Kylin:
  Fix Committed
Status in “gnome-calculator” package in Ubuntu:
  Fix Released

Bug description:
  系统测试版本：UK14.04-Daily-0410-i386
  计算器-编辑&帮助下拉框汉化不全。

  gnome-calculator menu is not translated under Kylin live session

  see screenshots

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

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

[Desktop-packages] [Bug 1306513] Re: 计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Ubuntu Kylin live session

[shijing]

in the latest dailybuild iso (2014.11.12) is not translated!

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

Title:
  计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under
  Ubuntu Kylin live session

Status in Ubuntu Translations:
  New
Status in Ubuntu Kylin:
  Fix Committed
Status in “gnome-calculator” package in Ubuntu:
  Fix Released

Bug description:
  系统测试版本：UK14.04-Daily-0410-i386
  计算器-编辑&帮助下拉框汉化不全。

  gnome-calculator menu is not translated under Kylin live session

  see screenshots

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

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

[Desktop-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

[Lorn Potter]

modem interface...

Is there anyway to edit comments?

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

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  In Progress
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “ofono” package in Ubuntu:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

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

[Desktop-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

[Lorn Potter]

According to dbus-monitor, the mode interface keeps failing:

signal sender=:1.8 -> dest=(null destination) serial=1635 
path=/org/freedesktop/NetworkManager/Devices/1; 
interface=org.freedesktop.NetworkManager.Device; member=StateChanged
   uint32 120
   uint32 40
   uint32 0
signal sender=:1.8 -> dest=(null destination) serial=1636 
path=/org/freedesktop/NetworkManager/Devices/1; 
interface=org.freedesktop.NetworkManager.Device.Modem; member=PropertiesChanged
   array [
  dict entry(
 string "State"
 variant uint32 120
  )
  dict entry(
 string "StateReason"
 variant struct {
   uint32 120
   uint32 0
}
  )
   ]

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

Title:
  [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu

Status in Platform API:
  In Progress
Status in The Savilerow project:
  New
Status in “network-manager” package in Ubuntu:
  Incomplete
Status in “ofono” package in Ubuntu:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  In Progress

Bug description:
  scope images load fine in wifi, but not on hsdpa even when there is
  good connectivity and browsing works well. Results are return, but
  images do not load.

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions

-- 
Mailing list: https://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 1390994] Re: Lost ability to print duplex

[octalman]

As I stated in my report, my HP 8600 Printer has a duplexer unit. 
Requests for double-sided printing (from Ubuntu) worked properly until a 
recent Ubuntu upgrade.

The duplexer works properly in local manual mode, just as it did before.

The problem I'm reporting is that it appears that something in Ubuntu 
has changed that now causes the double-sided option to be disregarded.  
Print jobs run normally, but disregard requests for two-sided printing; 
pages print sindge-sided only.

The print interface menu display has been changed (and not necessarily 
for the better).  The GUI display shows double-sided printing to be 
enabled with long-edge option, as its predecessor did before, but 
double-sided printing never occurs, though I have requested numerous 
such jobs.

At the time I write this, there are only two lines in the cups error 
log, each one stating:

Unknown directive BrowseAddress on line 26 of /etc/cups/cups.conf

less reports that there is no such file as /etc/cups/cups.conf (and, 
yes, I used sudo)

Wilbur Killebrew

On 11/10/2014 01:07 PM, Pascal De Vuyst wrote:
> Does your printer have a duplex unit or are you using some kind of
> manual duplex mode (print the odd pages, then the paper gets put back
> into the input tray and the even pages get printed)?
>
> Can your follow the instructions of the sections "CUPS error_log",
> "Capturing print job data", and "Getting the data which would go to the
> printer" on https://wiki.ubuntu.com/DebuggingPrintingProblems. Can you
> also attach the file(s) which you tried to print? Please do this for all
> situations with problems (LibreOffice, evince, ...).
>
> Do not pack the obtained file together and do not compress them. Please
> attach them one by one. This will make it easier for the readers


> of this
> bug report to handle them.
>
> ** Changed in: cups (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Lost ability to print duplex

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  A recent update (about a week or two ago) has resulted in my HP 8600
  printer no longer printing double-sided.  All the configuration
  information appears to be unchanged, but pages are not printed double-
  sided, when requested.  The duplexer works properly in local mode.

  My configuration is:  Ubuntu 14.04 (up-to-date), HP Pavilion dv6 with
  AMD quad-core processor.  I have been running Ubuntu on this machine
  for about 27 months.  I successfully upgraded from 12.04 to 14.04 last
  summer.  The 8600 printer has been in use for about two years.

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

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

[Desktop-packages] [Bug 1389099] Re: microphone mute icon support

[Ara Pulido]

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

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

Title:
  microphone mute icon support

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  New
Status in “unity-settings-daemon” source package in Trusty:
  New

Bug description:
  When we press mic mute key(XF86AudioMicMute, in some HP's notebook,
  it's Fn+F8), the notification shows sound mute icon, not mic mute
  icon. To simulate XF86AudioMicMute, you can run "xdotool key
  XF86AudioMicMute".

  My investigation:
  In the file: gsd-media-keys-manager.c, there's no icons[] array for mic mute, 
there're only volume_icons, brightness_icons, kb_backlight_icons. We should add 
detection functions for mic volume.

  Also we need icon files for mic volume. File name should be something
  like notification-audio-input-microphone-low-zero, notification-audio-
  input-microphone-high and located in /usr/share/notify-
  osd/icons/gnome/scalable/status (offered by notify-osd-icons package).

  Packages:
  unity-settings-daemon_14.04.0+14.04.20140414-0ubuntu1_amd64.deb

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

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

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

[Justinphuddleston]

Public bug reported:

I was just trying to use a proprietary driver, and it gives this error.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.16.0-24-generic
Date: Thu Nov 13 00:00:46 2014
InstallationDate: Installed on 2014-11-13 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package utopic

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

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

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

Bug description:
  I was just trying to use a proprietary driver, and it gives this
  error.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-24-generic
  Date: Thu Nov 13 00:00:46 2014
  InstallationDate: Installed on 2014-11-13 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1306513] Re: 计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Ubuntu Kylin live session

[shijing]

this bug was fix in trusty 1404.1dailybuild in 2014.1112

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

Title:
  计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under
  Ubuntu Kylin live session

Status in Ubuntu Translations:
  New
Status in Ubuntu Kylin:
  Fix Committed
Status in “gnome-calculator” package in Ubuntu:
  Fix Released

Bug description:
  系统测试版本：UK14.04-Daily-0410-i386
  计算器-编辑&帮助下拉框汉化不全。

  gnome-calculator menu is not translated under Kylin live session

  see screenshots

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

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

[Desktop-packages] [Bug 1310551] Re: NVIDIA proprietary driver 331.38 from package nvidia-331 on Xubuntu 14.04 causes display to hang

[Dmitriy]

Hi, I have same issue on MSI CX61 2OD with Nvidia Geforce 740M, Ubuntu
14.04 64 bits, driver 331.38 (both tested and updates versions). Display
hangs randomly when video is set to use Nvidia GPU, but it works fine
when switched to Intel GPU.

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

Title:
  NVIDIA proprietary driver 331.38 from package nvidia-331 on Xubuntu
  14.04 causes display to hang

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

Bug description:
  On 14.04 I am getting an issue on my Thinkpad T520 where running the
  "proprietary,tested" 331.38 driver causes my display to hang. It seems
  to stay that way until I switch to tty6 with ctrl+alt+f6 and then back
  to tty7 which has the display, this causes it to un-hang. This then
  happens back and forth. I am not sure but it might be triggered by
  clicking things, opening windows and such. The problem disappears when
  switching back to the open source driver.

  Should I try an even newer driver from nvidia, or is there any more
  information you need for troubleshooting?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Apr 21 12:29:36 2014
  InstallationDate: Installed on 2014-03-18 (33 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

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

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

[Desktop-packages] [Bug 1357681] Re: System tray icons for Owncloud, Insync and Dropbox disapear after reboot

[Launchpad Bug Tracker]

[Expired for Unity because there has been no activity for 60 days.]

** Changed in: unity
   Status: Incomplete => Expired

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

Title:
  System tray icons for Owncloud, Insync and Dropbox disapear after
  reboot

Status in Unity:
  Expired
Status in “unity” package in Ubuntu:
  Expired

Bug description:
  I have used 3 clients for file synchronization: Owncloud Client,
  Dropbox and Insync. Apparently the bug applies to all of the
  applications.

  Within the last 2-3 months the icons for the the applications have
  started to disappear from the system tray after a reboot. The icons
  doesn't reappear when (re)launching the applications from dash or
  terminal. However if I run "killall owncloud; owncloud" the icon for
  owncloud (re)appears. The icons for  Dropbox and Insync also
  (re)appears when using "killall" before launching.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 16 11:33:31 2014
  DistUpgraded: 2014-02-21 20:58:31,099 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-01-15 (212 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=0a466d6e-f0bc-4c34-bcc1-9649cb723803 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-21 (175 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Aug 16 09:12:00 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1357681] Re: System tray icons for Owncloud, Insync and Dropbox disapear after reboot

[Launchpad Bug Tracker]

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

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

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

Title:
  System tray icons for Owncloud, Insync and Dropbox disapear after
  reboot

Status in Unity:
  Expired
Status in “unity” package in Ubuntu:
  Expired

Bug description:
  I have used 3 clients for file synchronization: Owncloud Client,
  Dropbox and Insync. Apparently the bug applies to all of the
  applications.

  Within the last 2-3 months the icons for the the applications have
  started to disappear from the system tray after a reboot. The icons
  doesn't reappear when (re)launching the applications from dash or
  terminal. However if I run "killall owncloud; owncloud" the icon for
  owncloud (re)appears. The icons for  Dropbox and Insync also
  (re)appears when using "killall" before launching.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 16 11:33:31 2014
  DistUpgraded: 2014-02-21 20:58:31,099 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-01-15 (212 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=0a466d6e-f0bc-4c34-bcc1-9649cb723803 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-02-21 (175 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Aug 16 09:12:00 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1386120] Re: evince and evince-thumbnailer stuck with high cpu load

[Launchpad Bug Tracker]

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

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

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

Title:
  evince and evince-thumbnailer stuck with high cpu load

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Both evince and evince-thumbnailer get stuck with high CPU load when
  trying to open a DVI file with embedded EPS images. The DVI is output
  from latex. Very annoying as evince-thumbnailer is triggered
  automatically in the background every time the DVI file changes.

  This is a regression as it was working fine just two days ago with
  14.04 before the update.

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

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

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

[Desktop-packages] [Bug 30378] Re: Joystick activity does not stop the screensaver

[Forest]

I wrote a program called joystickwake to work around this problem until display 
servers learn that joysticks are input devices. If you happen to be running 
Ubuntu Trusty, you can install it from my PPA:
https://launchpad.net/~foresto/+archive/ubuntu/toys

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

Title:
  Joystick activity does not stop the screensaver

Status in GNOME Screensaver:
  Invalid
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed
Status in “xscreensaver” package in Ubuntu:
  Confirmed

Bug description:
  While playing games entirely with the joystick the screensaver is
  activated every few minutes.

  Input activity from a joystick should have the same results as
  activity from the mouse or keyboard.

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

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

[Desktop-packages] [Bug 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background

[Colin Weaver]

I can confirm this bug under Ubuntu 14.10 64-bit (Unity), Rhythumbox
3.0.3 .

Syslog shows just the one relevant entry that matches up with the time
of occurrence.

Nov 13 11:11:58 aubnerap06183l pulseaudio[2434]: [alsa-sink-92HD81B1X5
Analog] protocol-native.c: Failed to push data into queue

Pattern is always the same. Rhythmbox minimised playing a longish
playlist. Get a few tracks in, and it will play a fraction of a second
of a new track then halt.  Clicking play/pause won't re-start playback,
but moving the slider back to the beginning of the track will. Often I
will go for a while without it happening, but once it does it seems to
then occur again on nearly every new track.

I've experienced the same under Ubuntu 14.04, and before that on 12.04
going back as far as my initial Ubuntu install in mid 2012. Behavior
hasn't altered at all over the last 2 years.

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

Title:
  Banshee/Rhythmbox regularly stop playing audio when left on in the
  background

Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “pulseaudio” source package in Precise:
  Confirmed

Bug description:
  If Banshee or Rhythmbox is left playing in the background they will
  randomly stop playing in the latest builds of Ubuntu 12.04. Starting a
  new piece of music usually fixes the problem. If left to its own
  devices, the music will start playing again at some random time, at
  some random position. This problem exists on both my desktop machine
  (custom built Intel machine) and my laptop (Macbook 5,1). It has been
  happening for several months now.

  I became frustrated enough to load up pulseaudio in debugging mode.
  The log shows that when the music player just finishes playing one
  piece, and tries to start the next piece, you see something like this:

  ---
  ( 335.399|  34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to 
corking
  ( 335.400|   0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: before: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: after: 3705
  ( 335.400|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes.
  ( 335.400|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.400|   0.000) D: [alsa-sink] sink.c: latency = 1643
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on render memblockq.
  ( 335.400|   0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes 
on implementor.
  ( 335.400|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.400|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0:  34% 1:  
34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 
dB 1: -28.11 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0:  34% 
1:  34%
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:   in dB: 0: 
-28.00 dB 1: -28.00 dB
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 
0: 100% 1: 100% (accurate-enough=yes)
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c:  in dB: 
0: -0.11 dB 1: -0.11 dB
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Volume not changing
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 
bytes.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes.
  ( 335.402|   0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink 
alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: before: 3825
  ( 335.402|   0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to 
vacuum.
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: after: 3825
  ( 335.402|   0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes.
  ( 335.402|   0.000) D: [alsa-sink] sink.c: Processing rewind...
  ( 335.402|   0.000) D: [alsa-sink] sink.c: latency = 1402
  ( 335.402|   0.000) D: [alsa-sink] source.c: Processing rewind...
  ( 335.402|   0.000) I: [pulseaudio] sink-input.c: Freeing input 3 
"'zero-project - 05 - Forest of the unicorns' by 'zero-project'"
  ( 335.402|   0.000) D: [pulseaudio] module-stream-restore.c: Not restoring 
device for stream sink-input-by-media-role:music, because already set to 
'alsa_output.pci-_00_1b.0.analog-stereo'.
  ( 335.403|   0.000) D: [pulseaudio] module-intended-roles.c: Not setting 
device for stream Playback Stream, because already set.
  ( 

[Desktop-packages] [Bug 1391243] Re: [utopic] libg1-mesa-dev doesn't create any libGL.so link

[Daniel van Vugt]

Sorry, not confirmed yet. I was only testing trusty and vivid. Neither
of them have the bug at least.

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

Title:
  [utopic] libg1-mesa-dev doesn't create  any libGL.so link

Status in “mesa” package in Ubuntu:
  New

Bug description:
  Package version installed: 10.3.0-0ubuntu3
  Ubuntu release: Utopic (normal upgrade from Trusty)

  Trying to build OpenGL-depending program I run ./configure script
  which tries to invoke «glBegin» with gcc and -lGL, and it fails.

  I have both libgl1-mesa-{dev,dri,glx} and fglrx-updates{,-dev} installed, and 
only manual symlinking helps.
  Alhough I wanted fglrx libGL.so.1.2 symlinked, none is being symlinked, so 
it's bad in its current state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dev 10.3.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  BootLog: * Starting Deluge BitTorrent Daemon deluged
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Nov 10 19:40:31 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 14.201, 3.16.0-23-generic, i686: installed
   fglrx-updates-core, 14.201, 3.16.0-25-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:fa34]
     Subsystem: Toshiba America Info Systems Device [1179:fa34]
  InstallationDate: Installed on 2013-10-30 (376 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  LightdmGreeterLog: ** (lightdm-gtk-greeter:6257): WARNING **: Failed to load 
user image: Failed to open file '/home/reslayer/.face': No such file or 
directory
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:5685): WARNING **: Failed to 
load user image: Failed to open file '/home/reslayer/.face': No such file or 
directory
  MachineType: TOSHIBA Satellite C50D-A-K8K
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PT10AN
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd05/22/2013:svnTOSHIBA:pnSatelliteC50D-A-K8K:pvrPSCH2R-00700JRU:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C50D-A-K8K
  dmi.product.version: PSCH2R-00700JRU
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 28 04:22:34 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1391243] Re: [utopic] libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link

[Daniel van Vugt]

Confirmed on utopic. But vivid does not have the bug (file is installed
correctly).

** Summary changed:

- libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link
+ [utopic] libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link

** Summary changed:

- [utopic] libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link
+ [utopic] libg1-mesa-dev doesn't create  any libGL.so link

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

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

Title:
  [utopic] libg1-mesa-dev doesn't create  any libGL.so link

Status in “mesa” package in Ubuntu:
  New

Bug description:
  Package version installed: 10.3.0-0ubuntu3
  Ubuntu release: Utopic (normal upgrade from Trusty)

  Trying to build OpenGL-depending program I run ./configure script
  which tries to invoke «glBegin» with gcc and -lGL, and it fails.

  I have both libgl1-mesa-{dev,dri,glx} and fglrx-updates{,-dev} installed, and 
only manual symlinking helps.
  Alhough I wanted fglrx libGL.so.1.2 symlinked, none is being symlinked, so 
it's bad in its current state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-dev 10.3.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic i686
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  BootLog: * Starting Deluge BitTorrent Daemon deluged
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Nov 10 19:40:31 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 14.201, 3.16.0-23-generic, i686: installed
   fglrx-updates-core, 14.201, 3.16.0-25-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832] 
(prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems Device [1179:fa34]
     Subsystem: Toshiba America Info Systems Device [1179:fa34]
  InstallationDate: Installed on 2013-10-30 (376 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  LightdmGreeterLog: ** (lightdm-gtk-greeter:6257): WARNING **: Failed to load 
user image: Failed to open file '/home/reslayer/.face': No such file or 
directory
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:5685): WARNING **: Failed to 
load user image: Failed to open file '/home/reslayer/.face': No such file or 
directory
  MachineType: TOSHIBA Satellite C50D-A-K8K
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: PT10AN
  dmi.board.vendor: AMD
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.10:bd05/22/2013:svnTOSHIBA:pnSatelliteC50D-A-K8K:pvrPSCH2R-00700JRU:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C50D-A-K8K
  dmi.product.version: PSCH2R-00700JRU
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Oct 28 04:22:34 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1392118] Re: two graphics adapter for the notebook

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  two graphics adapter for the notebook

Status in “xorg” package in Ubuntu:
  New

Bug description:
  dv6 notebook 3190sl (HP) there are two graphics adapters (AMD) , the
  first discrete ( HD5xxx Series) , the second for energy saving (
  HD4xxx Series) ...

  The problem is that you can not use the discrete GPU , the GPU uses
  only ever HD4xxx energy saving

  
  is there a way to activate the first discrete graphics card and make it the 
default ?

  
  P.S.: there are no options in the bios.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Nov 13 01:07:23 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1440]
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:1440]
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcEnviron:
   LANGUAGE=it
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=9ce14554-fd5d-491c-8dc9-7a20db4be669 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.28
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1440
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 67.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.28:bd04/11/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn1440:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058B11242B1020100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Nov 12 23:10:56 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 884122] Re: xclock -digital shows seconds but redraws on the minute

[Robert Buccigrossi]

At least on 12.04 and later there is an "-update" option to set the
number of seconds for updating.  Therefore digital works fine when you
run:

xclock -digital -update 1

So while the default of 60 seconds is odd in digital mode, it works as
described in the man pages.

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

Title:
  xclock -digital shows seconds but redraws on the minute

Status in “x11-apps” package in Ubuntu:
  New

Bug description:
  i.e., on start it will show, e.g. "Mon 31 Oct 2011 09:17:15 GMT"
  (en_GB format), and stay that way for 45 seconds, then show "Mon 31
  Oct 2011 09:18:00 GMT" for a minute, etc.

  It redraws to show the correct time, including seconds, when the
  window is resized.  Window manager is Unity, version as of oneric-
  updates: 4.24.0-0ubuntu2b1 0.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: x11-apps 7.6+4ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: b0d31efda01870980e2e5a89390b685c
  CheckboxSystem: 6ce041aeed0a2c17b3343b66d157175d
  Date: Mon Oct 31 09:11:52 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/zsh
  SourcePackage: x11-apps
  UpgradeStatus: Upgraded to oneiric on 2011-05-03 (181 days ago)

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

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

[Desktop-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces

[Robert Ancell]

** Description changed:

- There doesn't seem to be any obvious way to force LightDM's VNC server
- to listen on only specified interfaces, most notably localhost. This
- creates a security issue, as the best and most secure way to access a
- VNC server is through an SSH tunnel where the client will only connect
- to its localhost on a particular port having all connections through the
- tunnel to the server's localhost port.
+ [Impact]
+ The XDMCP and VNC servers in LightDM allow connections on any network 
interface. It is desirable for these to be limited to a particular interface to 
limit who can connect (i.e. only allow local connections on 127.0.0.1).
  
- If there is a proper way to do this or some sort of work-around, I would
- be very interested in how to do so. As of right now, this makes
- LightDM's VNC server unusable for me.
+ [Test Case]
+ 1. Enable the VNC server in LightDM in lightdm.conf:
+ [VNCServer]
+ enabled=true
+ listen-address=127.0.0.1
+ 2. Start LightDM
+ With this setup you should only be able to make a local connection.
+ 
+ [Regression potential]
+ Low. If the option is not set LightDM has the old behaviour.

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

Title:
  VNC / XDMCP server cannot be configured to listen on specific
  interfaces

Status in Light Display Manager:
  In Progress
Status in Light Display Manager 1.10 series:
  In Progress
Status in Light Display Manager 1.12 series:
  In Progress
Status in Light Display Manager 1.2 series:
  In Progress
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Triaged

Bug description:
  [Impact]
  The XDMCP and VNC servers in LightDM allow connections on any network 
interface. It is desirable for these to be limited to a particular interface to 
limit who can connect (i.e. only allow local connections on 127.0.0.1).

  [Test Case]
  1. Enable the VNC server in LightDM in lightdm.conf:
  [VNCServer]
  enabled=true
  listen-address=127.0.0.1
  2. Start LightDM
  With this setup you should only be able to make a local connection.

  [Regression potential]
  Low. If the option is not set LightDM has the old behaviour.

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

-- 
Mailing list: https://launchpad.net/~desktop-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: lightdm is leaking FDs -fix

[Robert Ancell]

** Description changed:

- Description of problem:
- Each time the greeter starts the number of open FDs increase. After each 
login and logout cycle the number of open FDs is increased. Which over time 
leads to impossible logins and the message in /var/log/messages is:
+ [Impact]
+ LightDM doesn't close the server side end of the pipes used to communicate 
with session processes. This means each session that is created leaks two file 
descriptors eventually leading to the system stopping it from creating new 
pipes.
  
- Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipe to communicate with session process: To...en files
- Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files
- Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files
+ [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
  
- 
- Tested on:
- Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
- 
- Steps to Reproduce:
- 
- 1. login on a console and find the pid of main lightdm process then:
- # lsof -p {lightdm_pid} |grep FIFO |wc -l
- 26
- 
- 2. switch to X console and login through lightdm and then logout
- 
- 3. go back on comsole
- # lsof -p {lightdm_pid} |grep FIFO |wc -l
- 32
- 
- Here is a patch that fixes the issue. It may have several lines offset
- because we use modified lightdm but it is good for the original version
- too.
- 
- regards,
- Rumen
+ [Regression Potential]
+ Low. Fix is to close pipes when finished with them. Tested with regression 
tests.

-- 
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:
  lightdm is leaking FDs -fix

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:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
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. This means each session 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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces

[Robert Ancell]

** Changed in: lightdm
   Status: Fix Released => Triaged

** Changed in: lightdm
Milestone: 1.13.0 => 1.13.1

** Changed in: lightdm/1.10
Milestone: 1.10.4 => 1.10.5

** Changed in: lightdm/1.12
Milestone: 1.12.2 => 1.12.3

** Changed in: lightdm/1.2
Milestone: 1.2.9 => 1.2.10

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

** Changed in: lightdm/1.10
   Status: Fix Released => In Progress

** Changed in: lightdm/1.12
   Status: Fix Released => In Progress

** Changed in: lightdm
   Status: Triaged => In Progress

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

Title:
  VNC / XDMCP server cannot be configured to listen on specific
  interfaces

Status in Light Display Manager:
  In Progress
Status in Light Display Manager 1.10 series:
  In Progress
Status in Light Display Manager 1.12 series:
  In Progress
Status in Light Display Manager 1.2 series:
  In Progress
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Triaged

Bug description:
  There doesn't seem to be any obvious way to force LightDM's VNC server
  to listen on only specified interfaces, most notably localhost. This
  creates a security issue, as the best and most secure way to access a
  VNC server is through an SSH tunnel where the client will only connect
  to its localhost on a particular port having all connections through
  the tunnel to the server's localhost port.

  If there is a proper way to do this or some sort of work-around, I
  would be very interested in how to do so. As of right now, this makes
  LightDM's VNC server unusable for me.

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

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

[Desktop-packages] [Bug 1364911] Re: Support globbing in seat config sections

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.13.0-0ubuntu1

---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Fix pipe file descriptor leak for each session login / authentication
  (LP: #1190344)
- Use correct syntax for DesktopNames key in session files (LP: #1383321)
- Match seat configuration with globbing (LP: #1364911)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Disable log message when AccountsService users change (LP: #1376357)
- Update AppArmor scripts, requires AppArmor 2.9
- Update tests to run better on servers
  * debian/config-error-dialog.sh:
- Show warning dialog instead of interrupted login if syntax error in
  ~/.profile etc (LP: #678421)
 -- Robert AncellThu, 13 Nov 2014 11:08:17 
+1300

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

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

Title:
  Support globbing in seat config sections

Status in Light Display Manager:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released

Bug description:
  Add support for simple globbing in seat config sections.

  Example: if a config section [Seat:seatFoo*] is available in
  lightdm.conf, it will match any seat name starting with "seatFoo",
  like "seatFooBar", "seatFooBaz", etc.

  In particular, [Seat:seat*] will match any seat added from logind
  (including seat0), and [Seat:*] will match any seat (including those
  eventually added from other mechanisms than logind), just as
  [SeatDefaults] currently does.

  It was already merged into trunk in revision 2040, but has been
  reverted in revision 2042 due to some unexpected problem, so I'm
  opnening this bug report to keep track of changes.

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

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

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.13.0-0ubuntu1

---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Fix pipe file descriptor leak for each session login / authentication
  (LP: #1190344)
- Use correct syntax for DesktopNames key in session files (LP: #1383321)
- Match seat configuration with globbing (LP: #1364911)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Disable log message when AccountsService users change (LP: #1376357)
- Update AppArmor scripts, requires AppArmor 2.9
- Update tests to run better on servers
  * debian/config-error-dialog.sh:
- Show warning dialog instead of interrupted login if syntax error in
  ~/.profile etc (LP: #678421)
 -- Robert AncellThu, 13 Nov 2014 11:08:17 
+1300

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

-- 
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:
  In Progress
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  In Progress

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 1190344] Re: lightdm is leaking FDs -fix

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.13.0-0ubuntu1

---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Fix pipe file descriptor leak for each session login / authentication
  (LP: #1190344)
- Use correct syntax for DesktopNames key in session files (LP: #1383321)
- Match seat configuration with globbing (LP: #1364911)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Disable log message when AccountsService users change (LP: #1376357)
- Update AppArmor scripts, requires AppArmor 2.9
- Update tests to run better on servers
  * debian/config-error-dialog.sh:
- Show warning dialog instead of interrupted login if syntax error in
  ~/.profile etc (LP: #678421)
 -- Robert AncellThu, 13 Nov 2014 11:08:17 
+1300

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

-- 
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:
  lightdm is leaking FDs -fix

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:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  Description of problem:
  Each time the greeter starts the number of open FDs increase. After each 
login and logout cycle the number of open FDs is increased. Which over time 
leads to impossible logins and the message in /var/log/messages is:

  Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipe to communicate with session process: To...en files
  Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files
  Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files

  
  Tested on:
  Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0

  Steps to Reproduce:

  1. login on a console and find the pid of main lightdm process then:
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  26

  2. switch to X console and login through lightdm and then logout

  3. go back on comsole
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  32

  Here is a patch that fixes the issue. It may have several lines offset
  because we use modified lightdm but it is good for the original
  version too.

  regards,
  Rumen

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

[Launchpad Bug Tracker]

This bug was fixed in the package lightdm - 1.13.0-0ubuntu1

---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium

  * New upstream release:
- Fix crash when having configuration keys defined in multiple places
  (LP: #1377373)
- Fix pipe file descriptor leak for each session login / authentication
  (LP: #1190344)
- Use correct syntax for DesktopNames key in session files (LP: #1383321)
- Match seat configuration with globbing (LP: #1364911)
- Allow user switching in multi-seat until bug stopping greeter showing on
  logout is fixed
- Disable log message when AccountsService users change (LP: #1376357)
- Update AppArmor scripts, requires AppArmor 2.9
- Update tests to run better on servers
  * debian/config-error-dialog.sh:
- Show warning dialog instead of interrupted login if syntax error in
  ~/.profile etc (LP: #678421)
 -- Robert AncellThu, 13 Nov 2014 11:08:17 
+1300

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

-- 
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 Committed
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 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites

[kovinet]

I am also experiencing this issue couple of times every day. Music in
background keeps on playing and I can move mouse pointer, but everything
else on screen is frozen. Usually if I wait around 30 seconds or if I
switch to tty1 and back to tty7 it also usually solves the problem. Also
I should note that when I press Ctrl+Alt+1 there is couple of second
delay before showing the terminal.

I am using dual monitor setup and integrated Intel graphics chip:

#lspci -v | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])

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

Title:
  Ubuntu 14.04 random screen freeze while Normal OS activites

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  same symptom described in https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1184451

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 09:21:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:044d]
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:044d]
  InstallationDate: Installed on 2014-04-27 (3 days ago)
  InstallationMedia: Ubuntu-Kylin 14.04 LTS "Trusty Tahr" - Release amd64 
(20140417.1)
  MachineType: Dell Inc. Vostro 3400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RXV7H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3400
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2

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

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

[Desktop-packages] [Bug 1389858] Re: Libreoffice calc 4.2.7-0ubuntu1 not updating references after sort

[Björn Michaelsen]

for reference:
http://support2.microsoft.com/kb/40401

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

Title:
  Libreoffice calc 4.2.7-0ubuntu1 not updating references after sort

Status in “libreoffice” package in Ubuntu:
  Triaged

Bug description:
  Update to LibreOffice 4.2.7 is causing incorrect sort behaviour in
  Calc.

  As initially reported here:

  
http://www.reddit.com/r/Ubuntu/comments/2le7qu/libreoffice_calc_update_a_few_hours_ago_is_buggy/

  Attached is sample Calc document. To reproduce, highlight B6 to E14,
  select Sort and sort by Column D, see that column E didn't get sorted.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  5 15:49:03 2014
  InstallationDate: Installed on 2013-11-26 (344 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to utopic on 2014-10-08 (27 days ago)

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

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

[Desktop-packages] [Bug 314147] Re: [Upstream] Calc can't load a *.wb3 file

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: New => Confirmed

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

Title:
  [Upstream] Calc can't load a *.wb3 file

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Unknown
Status in “gnumeric” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Won't Fix
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:Ubuntu 11.04
  Release:11.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen using LibreOffice Calc via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/314147/+attachment/434865/+files/CAR08.wb3
  && localc -nologo CAR08.wb3

  is the file opens.

  4) What happens instead is it fails silently.

  WORKAROUND: Convert the file using Gnumeric's ssconvert and open in
  LibreOffice via the Terminal:

  ssconvert CAR08.wb3 CAR08.ods && localc -nologo CAR08.ods

  WORKAROUND: Use Gnumeric.

  apt-cache policy gnumeric
  gnumeric:
Installed: 1.10.13-1ubuntu1
Candidate: 1.10.13-1ubuntu1
Version table:
   *** 1.10.13-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  Original Reporter Comments: Opening a *.wp3 file crashes
  OOspreadsheet. reloading says it fixes the file, but nothing is on the
  screen. reloading the file causes same to crash again. OO 2.4.1 for
  ubuntu.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  Package: openoffice.org-core 1:2.4.1-11ubuntu2.1
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.27-9-generic i686

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

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

[Desktop-packages] [Bug 1392105] Re: Emerald crashes and Ubuntu cannot determine package or source package name

[Hai NGUYEN VAN]

** Description changed:

  Hello,
  
  I am currently using Ubuntu 12.04 LTS with Compiz 0.9.7.12 and Emerald
  0.9.5 under GNOME 2 Classic (via gnome-session-fallback package) with
  "Elegant Brit Emerald 1.0.2" theme. However, it appears that Emerald
- window decorator is not stable at all and regularly crashes and Ubuntu
- is not able to display any crash report. It claims to be impossible to
- determine package or source package name (as shown in attachment).
+ window decorator is not stable at all and regularly crashes and
+ Ubuntu/Apport is not able to display any crash report. It claims to be
+ impossible to determine package or source package name (as shown in
+ attachment).
  
  Kind regards,

** Tags added: apport

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

Title:
  Emerald crashes and Ubuntu cannot determine package or source package
  name

Status in “emerald” package in Ubuntu:
  New

Bug description:
  Hello,

  I am currently using Ubuntu 12.04 LTS with Compiz 0.9.7.12 and Emerald
  0.9.5 under GNOME 2 Classic (via gnome-session-fallback package) with
  "Elegant Brit Emerald 1.0.2" theme. However, it appears that Emerald
  window decorator is not stable at all and regularly crashes and
  Ubuntu/Apport is not able to display any crash report. It claims to be
  impossible to determine package or source package name (as shown in
  attachment).

  Kind regards,

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

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

[Desktop-packages] [Bug 1392108] [NEW] Sync ibus-m17n 1.3.4-4 (main) from Debian unstable (main)

[Jackson Doak]

Public bug reported:

Please sync ibus-m17n 1.3.4-4 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Use dh_autotools-dev to update config.{sub,guess} for AArch64.
Fixed in debian

Changelog entries since current vivid version 1.3.4-3ubuntu1:

ibus-m17n (1.3.4-4) unstable; urgency=medium

  * Team upload.
  * Build with dh-autoreconf.  Closes: #727265
  * Fix build with clang. Closes: #743129

 -- Osamu Aoki   Mon, 27 Oct 2014 00:04:33 +0900

** Affects: ibus-m17n (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: ibus-m17n (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync ibus-m17n 1.3.4-4 (main) from Debian unstable (main)

Status in “ibus-m17n” package in Ubuntu:
  New

Bug description:
  Please sync ibus-m17n 1.3.4-4 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Use dh_autotools-dev to update config.{sub,guess} for AArch64.
  Fixed in debian

  Changelog entries since current vivid version 1.3.4-3ubuntu1:

  ibus-m17n (1.3.4-4) unstable; urgency=medium

* Team upload.
* Build with dh-autoreconf.  Closes: #727265
* Fix build with clang. Closes: #743129

   -- Osamu Aoki   Mon, 27 Oct 2014 00:04:33 +0900

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

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

[Desktop-packages] [Bug 314147]

[Christopher M. Penalver]

This was initially reported downstream 5 years ago, as noted in the See
Also: at the top of this report ->
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/314147 , and
as I've confirmed this now twice, once downstream, and now again here by
reporting it, I've marked this New as outlined in
https://wiki.documentfoundation.org/QA/BSA/BugReport_Details#Initial_state
(which doesn't require a member of QA confirming a bug to mark it New).

Despite this, as I'm now formally a member of QA
https://wiki.documentfoundation.org/QA/Team , I've gone ahead and placed
myself as the QA contact if you would have further questions regarding
the scope of this report.

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

Title:
  [Upstream] Calc can't load a *.wb3 file

Status in LibreOffice Productivity Suite:
  Confirmed
Status in The OpenOffice.org Suite:
  Unknown
Status in “gnumeric” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Won't Fix
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:Ubuntu 11.04
  Release:11.04

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen using LibreOffice Calc via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/314147/+attachment/434865/+files/CAR08.wb3
  && localc -nologo CAR08.wb3

  is the file opens.

  4) What happens instead is it fails silently.

  WORKAROUND: Convert the file using Gnumeric's ssconvert and open in
  LibreOffice via the Terminal:

  ssconvert CAR08.wb3 CAR08.ods && localc -nologo CAR08.ods

  WORKAROUND: Use Gnumeric.

  apt-cache policy gnumeric
  gnumeric:
Installed: 1.10.13-1ubuntu1
Candidate: 1.10.13-1ubuntu1
Version table:
   *** 1.10.13-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
  100 /var/lib/dpkg/status

  Original Reporter Comments: Opening a *.wp3 file crashes
  OOspreadsheet. reloading says it fixes the file, but nothing is on the
  screen. reloading the file causes same to crash again. OO 2.4.1 for
  ubuntu.

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 8.10
  Package: openoffice.org-core 1:2.4.1-11ubuntu2.1
  ProcEnviron:
   
PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: openoffice.org
  Uname: Linux 2.6.27-9-generic i686

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

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

[Desktop-packages] [Bug 1081590] Re: could not determine source package name

[Hai NGUYEN VAN]

** Also affects: apport
   Importance: Undecided
   Status: New

** No longer affects: apport

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

Title:
  could not determine source package name

Status in “apport” package in Ubuntu:
  New
Status in “cups” package in Ubuntu:
  New

Bug description:
  When I open/switch on HP printer PSC 750 to print I get an error
  message and a request to send a report, which I accept.

  The following message is then displayed

  "Could not determine the package or source package name."

  
  This happens every time I try to print from Internet or Libre office 
programmes.

  I therefore do not know if the bug gets reported or the error report
  message is just terminated because of lack of information gleaned from
  my system.

  What should I do?

  Printing itself does not appear to be affected.  Problem only occurs
  in 12.04.  It was not a problem in 10.04

  Regards
  Rodger

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

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

[Desktop-packages] [Bug 1392105] [NEW] Emerald crashes and Ubuntu cannot determine package or source package name

[Hai NGUYEN VAN]

Public bug reported:

Hello,

I am currently using Ubuntu 12.04 LTS with Compiz 0.9.7.12 and Emerald
0.9.5 under GNOME 2 Classic (via gnome-session-fallback package) with
"Elegant Brit Emerald 1.0.2" theme. However, it appears that Emerald
window decorator is not stable at all and regularly crashes and
Ubuntu/Apport is not able to display any crash report. It claims to be
impossible to determine package or source package name (as shown in
attachment).

Kind regards,

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


** Tags: apport

** Attachment added: "emerald_impossible_to_report_crash.png"
   
https://bugs.launchpad.net/bugs/1392105/+attachment/4259581/+files/emerald_impossible_to_report_crash.png

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

Title:
  Emerald crashes and Ubuntu cannot determine package or source package
  name

Status in “emerald” package in Ubuntu:
  New

Bug description:
  Hello,

  I am currently using Ubuntu 12.04 LTS with Compiz 0.9.7.12 and Emerald
  0.9.5 under GNOME 2 Classic (via gnome-session-fallback package) with
  "Elegant Brit Emerald 1.0.2" theme. However, it appears that Emerald
  window decorator is not stable at all and regularly crashes and
  Ubuntu/Apport is not able to display any crash report. It claims to be
  impossible to determine package or source package name (as shown in
  attachment).

  Kind regards,

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

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

[Desktop-packages] [Bug 1366165] Re: No hybrid GPU and this error appears: Failed to spawn hybrid-gfx main process: unable to execute: No such file or directory

[exit_jones]

also a Dell Studio XPS 9100 (with an Intel i7-930 quadcore) and an
Nvidia GeForce 9800 GT, upgraded today from 12.04 --> 14.04

at the end of dmesg from startup:
[   17.577900] init: Failed to spawn hybrid-gfx main process: unable to 
execute: No such file or directory
[   17.769747] init: gdm main process (1182) killed by TERM signal

here's some info on the video card:
root@desktop-of-my-boss:/var/log# lspci -knns 03:00.0
03:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92 [GeForce 9800 
GT] [10de:0605] (rev a2)
Subsystem: XFX Pine Group Inc. Device [1682:2372]
Kernel driver in use: nvidia

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

Title:
  No hybrid GPU and this error appears: Failed to spawn hybrid-gfx main
  process: unable to execute: No such file or directory

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

Bug description:
  I have an nVidia 9800GT GPU and a Core 2 Duo CPU. Still, I get errors
  during startup:

  32.281097] init: Failed to spawn hybrid-gfx main process: unable to
  execute: No such file or director

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-drivers-common 1:0.2.91.6
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Fri Sep  5 18:31:30 2014
  InstallationDate: Installed on 2012-03-26 (892 days ago)
  InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to trusty on 2014-07-20 (47 days ago)

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

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

[Desktop-packages] [Bug 1011120] Re: Desktop Cube: Unity's top panel shadow gets deformed also and rendered on the desktop cube instead of sticking with the top panel when the cube gets activated

[Amr Ibrahim]

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

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

Title:
  Desktop Cube: Unity's top panel shadow gets deformed also and rendered
  on the desktop cube instead of sticking with the top panel when the
  cube gets activated

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  The shadow of the main Unity panel on top should stay untouched, like the 
panel does, when using the desktop cube, instead of being rendered onto the 
cube.
  The situation gets even worse visually when "Cube Reflection and Deformation" 
is used additionally, because now the shadow does not deform with the cube, but 
stays in the same position of the original cube.

  Ubuntu 12.04, Compiz 0.9.7.8-0ubuntu1vvpreproposed2

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

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

[Desktop-packages] [Bug 1043627] Re: [SRU] Add XIM Support to Nux

[Amr Ibrahim]

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

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

Title:
  [SRU] Add XIM Support to Nux

Status in Nux:
  Fix Released
Status in Nux 2.0 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Committed
Status in “nux” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Fix Released
Status in “nux” source package in Quantal:
  Won't Fix
Status in “unity” source package in Quantal:
  Won't Fix
Status in “nux” source package in Raring:
  Confirmed
Status in “unity” source package in Raring:
  Fix Committed

Bug description:
  [Impact]

  As 12.04 is an LTS, many users decide to stay with that version until
  the next LTS version is available. Many of those users require
  different input methods to comfortably input characters in their
  language. We do support IBus for some of the languages, but others are
  still using XIM as the input framework. Those users cannot input in
  their language using their standard input methods. This means using
  the Dash and HUD is much more troublesome or even impossible in normal
  cases.

  We think that even though it is essentially a new feature, it can be thought 
that the lack of support for non-IBus additional input methods is a bug in a 
way.
  It is a big change, but with proper testing, we would ensure that the 
addition does not introduce any new regressions.

  This addition would make many MANY users happy, which can be seen at
  least by the number of affected people in LP: #983254.

  Also, the change is needed by OEM. It is a big change, but it's
  crucial for CJK - Kyrlin has voiced the proposition to use fctix as
  the default input method, which _needs_ XIM support in Nux and Unity.

  [Test Case]

  1. Install fctix-pinyin
  2. Run im-config and enable fctix as the default IM
  3. Reboot your machine
  4. Open the dash and input non-latin characters using fctix
     -> Non latin characters (Chinese in this case) should appear on screen.

  [Regression Potential]

  In an impossible scenariu, broken IBus input or input in overall in Nux input 
fields.
  The good thing about the XIM support is that it's rather isolated, so 
potential breakage of the XIM code won't impact normal Nux workflow. Just XIM 
input might not work.

  The author of the code, Brandon, also mentions that new regression
  potential is low as the XIM code is not being used by default. As XIM
  is not the default, when IBus is present - without explicitly setting
  XIM in im-config, the XIM parts are not even accessed.

  [Other Info]

  The same functionality is already available in the newer Unity
  releases.

  Original description:

  Right now the only input method (IM) that works with Unity/Nux is
  IBus. This means anyone who uses a different IM would have to switch
  to IBus in order to type in their language.

  This is something that needs to be fixed and will make Unity/Nux
  friendlier to those who use different IMs. If you do not use an IM
  then this will not affect you.

  XIM was the very first IM framework for the X window system, which
  means most IMs are supported by it.

  A List of IMs that will be supported by this branch (There could be more):
  http://en.wikipedia.org/wiki/List_of_input_methods_for_UNIX_platforms

  All of those under XIM will now work in Unity and Nux with this
  branch.

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

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

[Desktop-packages] [Bug 1034616] Re: [Regression] Lowering window by middle click doesn't switch focus to raised window

[Amr Ibrahim]

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

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

Title:
  [Regression] Lowering window by middle click doesn't switch focus to
  raised window

Status in Compiz:
  Fix Released
Status in Compiz 0.9.9 series:
  Fix Committed
Status in Unity:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Middle mouse click on title bar will lower window; but it does not
  switch the focus to the window which was raised above it.

  1) Open a gedit app window
  2) Open a calc app
  3) Middle click the mouse on the calculator title bar.

  It should lower the calculator and raise the gedit window as well as
  switch the focus to gedit. But it doesnt switch the focus.

  See also:
  autopilot run 
unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works

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

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

[Desktop-packages] [Bug 1181367] Re: Alt+Tab switches between incorrect windows after some time of activity

[Amr Ibrahim]

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

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

Title:
  Alt+Tab switches between incorrect windows after some time of activity

Status in Unity:
  Fix Released
Status in Unity 7.0 series:
  Fix Committed
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Raring:
  Fix Released

Bug description:
  [Impact]

  Due to overflow, alt+tab between the same application becomes
  impossible]

  [Test Case]

  1) Keep two windows of an app (say terminal) opened for some time, and another
 window of a different app
  2) Focus one window terminal keeping the other terminal window below it
  3) Press Alt+Tab

  Expected behavior
  4) The other terminal window is focused

  Actual behavior:
  4) Other opened application is selected instead.

  [Regression Potential]

  Low, types extended from int to long long. The code affected is the
  alt tab functionality.

  

  Due to an overflow, after some time of activity it's impossible to
  alt+tab between two windows of the same application.

  1) Keep two windows of an app (say terminal) opened for some time, and another
     window of a different app
  2) Focus one window terminal keeping the other terminal window below it
  3) Press Alt+Tab

  Expected behavior
  4) The other terminal window is focused

  Actual behavior:
  4) Other opened application is selected instead.

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

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

[Desktop-packages] [Bug 1059759] Re: Clicking on Workspace Switcher icon when the expo is showing, not always closes it

[Amr Ibrahim]

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

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

Title:
  Clicking on Workspace Switcher icon when the expo is showing, not
  always closes it

Status in Unity:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Especially in multimonitor:

  1) Click on the workspace switcher icon
  2) The expo is shown
  3) Click again on the workspace switcher icon

  Expected result:
  4) The expo is hidden

  Actual result:
  4) Expo is not hidden always (repeat this for all the monitors)

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

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

[Desktop-packages] [Bug 1059601] Re: [dash] Rendering flaw of ghost icons when a preview is open.

[Amr Ibrahim]

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

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

Title:
  [dash] Rendering flaw of ghost icons when a preview is open.

Status in Unity:
  Fix Released
Status in Unity 6.0 series:
  Triaged
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  See the icon in the top-left corner of the attached screenshot.

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

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

[Desktop-packages] [Bug 1062316] Re: Glow border for selected window in scale mode does not draw correctly on the top corners

[Amr Ibrahim]

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

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

Title:
  Glow border for selected window in scale mode does not draw correctly
  on the top corners

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  See the attached screenshot: the glow is not correctly applied to the
  top corners

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

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

[Desktop-packages] [Bug 1046125] Re: Decoration in spread windows should use the system font

[Amr Ibrahim]

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

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

Title:
  Decoration in spread windows should use the system font

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  As title says.

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

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

[Desktop-packages] [Bug 1319941] Re: libreoffice draw / impress crash if user service publishing is disabled in avahi

[Kees Cook]

** Also affects: libreoffice (Ubuntu Vivid)
   Importance: High
 Assignee: Björn Michaelsen (bjoern-michaelsen)
   Status: Confirmed

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

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

** Changed in: libreoffice (Ubuntu Trusty)
 Assignee: (unassigned) => Björn Michaelsen (bjoern-michaelsen)

** Tags added: regression-release

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

Title:
  libreoffice draw / impress crash if user service publishing is
  disabled in avahi

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “libreoffice” source package in Trusty:
  Confirmed
Status in “libreoffice” source package in Vivid:
  Confirmed
Status in “libreoffice” package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Impress and Draw will not work (Crash) with Avahi enabled, but user/all 
publishing disabled.
   * The fix is basically some check before free, and return earlier if failing.

  [Test Case]

   * Restart avahi daemon with either disable-user-service-publishing=yes or 
disable-publishing=yes.  This will cause the crash.
   * Patch was also tested with avahi on, making sure it publishes and with 
avahi just to make sure a new bug was not introduced.

  [Regression Potential]

   * If a regression occurs it would be avahi specific and should only affect 
Impress and Draw.  It will be less likely to manifest in an outright crash now.
   * I was unable to test actually using a remote control. (but the avahi 
service was published which is the only part my fix touches.

  [Other Info]
  Avahi is NOT enabled in Upstream LibreOffice builds (so don't try to test 
them for this bug) although pushing to have source fix included in 4.2.x and 
4.3.x anyways
  Master Upstream fix (TB4.4): 
http://cgit.freedesktop.org/libreoffice/core/commit/?id=3c57701cf0a169bd8d1893d1b2271d48b8072147
  Proposed 4.3: https://gerrit.libreoffice.org/#/c/10816/
  Proposed 4.2: 
http://cgit.freedesktop.org/libreoffice/core/commit/?h=libreoffice-4-2&id=8de2e9b4bc53e6c097897142bad223c100d36292

  Both loimpress and lodraw fail to start with an error message related
  to avahi:

  $ loimpress
  avahi_entry_group_new() failed: Not permitted
  soffice.bin: client.c:626: avahi_client_free: Assertion `client' failed.

  $ ps ax | grep avahi
   7617 pts/0S+ 0:00 grep --color=auto avahi
  21356 ?S  0:07 avahi-daemon: running [hostname.local]
  21380 ?S  0:00 avahi-daemon: chroot helper

  This is the backtrace of the crash:

  $ cat gdbtrace.log
  warning: Currently logging to gdbtrace.log.  Turn the logging off and on to 
make the new setting effective.
  warning: Unable to find libthread_db matching inferior's thread library, 
thread debugging will not be available.

  Program received signal SIGABRT, Aborted.
  0x741f2f79 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
  56../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
  #0  0x741f2f79 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
  #1  0x741f6388 in __GI_abort () at abort.c:89
  #2  0x741ebe36 in __assert_fail_base (fmt=0x7433d718 "%s%s%s:%u: 
%s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fffe95b6919 
"client", file=file@entry=0x7fffe95b6910 "client.c", line=line@entry=626, 
function=function@entry=0x7fffe95b6fe0 "avahi_client_free") at assert.c:92
  #3  0x741ebee2 in __GI___assert_fail (assertion=0x7fffe95b6919 
"client", file=0x7fffe95b6910 "client.c", line=626, function=0x7fffe95b6fe0 
"avahi_client_free") at assert.c:101
  #4  0x7fffe95af06b in avahi_client_free () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  #5  0x7fffbac7c40c in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #6  0x7fffbac7c678 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #7  0x7fffe95aec2c in ?? () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  #8  0x7fffe95af3aa in avahi_client_new () from 
/usr/lib/x86_64-linux-gnu/libavahi-client.so.3
  #9  0x7fffbac7c8a5 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #10 0x7fffbac7d195 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #11 0x7fffbac7d30b in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #12 0x7fffbac74756 in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #13 0x7fffbaa12b9b in ?? () from 
/usr/lib/libreoffice/program/../program/libsdlo.so
  #14 0x7fffbab83bc0 in sd_component_getFactory () from 
/usr/lib/libreoffice/program/../program/libsdlo.so

  This is on trusty.

  libreoffice-impress 1:4.2.3~rc3-0ub

[Desktop-packages] [Bug 1117500] Re: test-unit needs to be ported to gtest

[Amr Ibrahim]

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

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

Title:
  test-unit needs to be ported to gtest

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Test-unit uses glib testing framework. It needs to be ported to gtest
  (google test).

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

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

[Desktop-packages] [Bug 1097991] Re: Port to new barrier event API

[Amr Ibrahim]

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

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

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

Title:
  Port to new barrier event API

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Raring:
  Fix Released

Bug description:
  The pointer barrier event API we've patched in to libXfixes has moved
  upstream in Xserver 1.14. However, the API has changed.

  The barrier events and pointer release API is now in the input lib,
  libXi as of version 1.6.99.1 . It should be reasonably easy to port to
  the new API: Peter Hutterer's blog post¹ describes how to use it. The
  main differences are that you need to add the barrier event mask to
  the XI event mask, rather than window event mask, and that it now uses
  generic events, so you need to allocate the event data before using it
  and free the event data after using it XGetEventData/XFreeEventData.

  ¹: http://who-t.blogspot.com.au/2012/12/whats-new-in-xi-23-pointer-
  barrier.html

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

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

[Desktop-packages] [Bug 1283453] Re: window spread with too narrow titlebars on hig-dpi screen

[Amr Ibrahim]

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

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

Title:
  window spread with too narrow titlebars on hig-dpi screen

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Titlebars are currently cropped and don't completely display the text
  in spread mode, if the global scaling factor is set to 2.

  org.gnome.desktop.interface.scaling-factor = 2
  org.gnome.desktop.interface.text-scaling-factor = 1.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140220-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat Feb 22 15:04:07 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1207669] Re: [MIR] Need binary package included in main.

[Amr Ibrahim]

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

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

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

Title:
  [MIR] Need binary package included in main.

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  This source package is already in main, but in preparation for
  https://bugs.launchpad.net/bugs/1206268 I will need binary package
  unity-autopilot included in main as well.

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

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

[Desktop-packages] [Bug 1162886] Re: test-gtest [ FAILED ] TestIconLoader.TestGetManyIcons - segfaults at times.

[Amr Ibrahim]

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

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

Title:
  test-gtest [  FAILED  ] TestIconLoader.TestGetManyIcons - segfaults at
  times.

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Stack trace: http://paste.ubuntu.com/5668678/
  Full stack trace: http://paste.ubuntu.com/5668696/

  Run: ./test-gtest --gtest_filter=*GetManyIcons*

  It also passes at times as well.

  *Update*
  I also just got this while restarting unity...so this seems a bit more 
serious then a failing unit test:
  http://paste.ubuntu.com/5667999/

  I got it after doing a compiz --replace ccp, then opening the
  dash...though I can't reproduce it :(.

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

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

[Desktop-packages] [Bug 1171733] Re: Cannot connect to OS X (Regression)

[Jordi Mallach]

According to the Debian changelog, this was fixed in 1.0.0+git20140913-2
and 1.0.0+git20140930 upstream. However I still get the described
behaviour.

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

Title:
  Cannot connect to OS X (Regression)

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  When trying to connect to OS X hosts I get the following message -

  Unknown authentication scheme from VNC server: 30, 35

  Uninstalling remmina and then installing the version from 12.04 fixes
  the problem.

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

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

[Desktop-packages] [Bug 864037] Re: workspace switcher zoom failure with multiple monitors

[Amr Ibrahim]

** Changed in: unity (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  workspace switcher zoom failure with multiple monitors

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Oneiric:
  Fix Released

Bug description:
  SRU TEST CASE:
  1. connect an external display to your system
  2. click workspace switcher
  3. notice all the graphical problems on the screen
  4. now install Unity from oneiric-proposed
  5. Notice everything is working as it with single display

  =Original Report=

  When my laptop is not connected to an external monitor and I click the
  Workspace Switcher, the "zoom out" effect to show all workspaces works
  properly. When I connect a monitor to my DisplayPort output and click
  Workspace Switcher, the laptop's built-in monitor shows a messed-up
  background (see attachment) and the external monitor shows no
  background.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.20.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,snap,grid,mousepoll,compiztoolbox,resize,imgpng,wall,unitymtgrabhandles,regex,gnomecompat,place,vpswitch,move,animation,workarounds,expo,session,ezoom,fade,scale,unityshell]
  CompositorRunning: compiz
  Date: Sat Oct  1 07:38:07 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 12) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:172a]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2)
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlIdent:
   Socket 0:
     product info: "RICOH", "Bay8Controller", "", ""
     manfid: 0x, 0x
     function: 254 (unknown)
  PccardctlStatus:
   Socket 0:
     3.3V 16-bit PC Card
     Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcEnviron:
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=26780926-1f18-4056-ae79-bf1656287393 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.02
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.02:bd12/22/2009:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.29:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites

[gumkins]

I'm experiencing the same issue but I'm able to move mouse pointer.

>From time to time I'm switching between single and dual-monitor
configuration on my laptop with dual video (Lenovo V580) and I'm
observing alike screen freezing which takes about half of minute.

I/O led does not show heavy activity and it looks like background
processes are working (at least music is playing).

# lspci -v | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 645M] 
(rev ff) (prog-if ff)

Video Driver: "NVIDIA binary driver - version 331.38 from nvidia-331
(proprietary, tested)"

PRIME Profile settings - Intel (Power Saving Mode)

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

Title:
  Ubuntu 14.04 random screen freeze while Normal OS activites

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  same symptom described in https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1184451

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 09:21:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:044d]
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:044d]
  InstallationDate: Installed on 2014-04-27 (3 days ago)
  InstallationMedia: Ubuntu-Kylin 14.04 LTS "Trusty Tahr" - Release amd64 
(20140417.1)
  MachineType: Dell Inc. Vostro 3400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RXV7H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3400
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2

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

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

[Robert Ancell]

I've removed the tasks on LightDM (the project) as the fixes for this
were all in debian/.

** No longer affects: lightdm/1.12

** No longer affects: lightdm/1.10

** No longer affects: 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/678421

Title:
  Error message for a faulty ~/.profile script

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  In Progress

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 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

[Ivan R.]

Unbelievable, it's still present in 14.10 and nobody takes care after
years. Now "triaged".

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

Title:
  DPMS support broken, fails to wake up the monitor after putting it to
  sleep

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

Bug description:
  Also affects nvidia-graphics-drivers-319

  The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
  but with Nvidia instead of AMD/ATI drivers.

  HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
  display

  Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
  Only a restart of the Xserver will bring back the display at that point.

  A cycle of
  xset dpms force off; sleep 30; xset dpms force on
  will leave the display dark.

  At the moment I help myself by not allowing DPMS to switch off the display:
  neuffer@charion:~$ xset dpms 0 0 0

  neuffer@charion:~$ xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel

[Alberto Salvia Novella]

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

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

Title:
  [AV200 - Xonar STX, recording] Microphone is not working on frontpanel

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Microphone is not working on frontpanel of my soundcard Asus Xonar
  Essence STX. In windows it works normally.

  Ubuntu 13.04 x64

  Tested on the latest kernel 3.9-rc8

  With 3.8.0 kernel problem is the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.9.0-030900rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simplehuman   2394 F pulseaudio
   /dev/snd/pcmC0D0c:   simplehuman   2394 F...m pulseaudio
   /dev/snd/controlC1:  simplehuman   2394 F pulseaudio
  Date: Mon Apr 22 15:06:32 2013
  InstallationDate: Installed on 2013-02-14 (67 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed
  Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia
  Symptom_Type: None of the above
  Title: [AV200 - Xonar STX, recording] Recording problem
  UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago)
  dmi.bios.date: 08/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: SABERTOOTH X58
  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.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1376760] Re: after a screen rotation we get a double mouse pointer

[Alberto Salvia Novella]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided => High

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

Title:
  after a screen rotation we get a double mouse pointer

Status in X.org xf86-video-intel:
  Fix Released
Status in “xserver-xorg-video-intel” package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu version 14.10
  after a screen rotation when we come back to normal rotation our mouse 
pointer is doubled: the old
  rotated one and the actual one.
  This bug was already reported in: 
https://bugs.freedesktop.org/show_bug.cgi?id=81886
  with a complete solution.
  I checked that code compiled for 14.10 does not contain the fix in file:
  src/sna/sna_display.c

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3
  Uname: Linux 3.17.0-031700rc7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Oct  2 16:35:59 2014
  DistUpgraded: 2014-09-23 12:09:08,269 DEBUG disabling apt cron job (0o755)
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-11-14 (322 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 2191
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700rc7-generic 
root=UUID=42f32e25-c311-4811-9c71-19fd8ef53c6d ro quiet acpi_backlight=vendor
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to utopic on 2014-09-23 (9 days ago)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 66CN54WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Yoga 13
  dmi.modalias: 
dmi:bvnLENOVO:bvr66CN54WW:bd01/21/2013:svnLENOVO:pn2191:pvrLenovoIdeaPadYoga13:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadYoga13:
  dmi.product.name: 2191
  dmi.product.version: Lenovo IdeaPad Yoga 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  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~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Oct  2 12:37:20 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 864 
   vendor LGD
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Robert Ancell]

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

-- 
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 Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.12 series:
  Fix Committed
Status in “gdm” package in Ubuntu:
  In Progress
Status in “lightdm” package in Ubuntu:
  In Progress
Status in “gdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Trusty:
  In Progress
Status in “gdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Utopic:
  In Progress

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 1365054] Re: package brltty 5.0-2ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alberto Salvia Novella]

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

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

Title:
  package brltty 5.0-2ubuntu3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in “brltty” package in Ubuntu:
  Confirmed

Bug description:
  /usr/bin/dpkg returned an error code (1)

  upgrade from 14.04 to 14.10

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: brltty 5.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  AptOrdering: brltty: Configure
  Architecture: i386
  Date: Wed Sep  3 12:06:13 2014
  DuplicateSignature: package:brltty:5.0-2ubuntu3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-08-13 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: brltty
  Title: package brltty 5.0-2ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-09-03 (0 days ago)

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

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

[Desktop-packages] [Bug 1366709] Re: please enable opencl

[Alberto Salvia Novella]

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

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

Title:
  please enable opencl

Status in “mesa” package in Ubuntu:
  Confirmed

Bug description:
  [This is the same as bug #1319835, since I cannot reopen it]

  Please enable OpenCL in mesa package which is already available in
  debian package and was disabled in 10.1.0-1ubuntu1.

  Previuos bug was closed as Won't Fix since there were no software using it:
  > I don't think there's a point to opencl at the moment, as soon as something 
in the archive really needs it feel free to reopen it.

  Here is a list of Ubuntu source package using it (the list may be incomplete):
  bfgminer
  clinfo
  erlang-cl
  libreoffice-calc
  pyopencl
  pyrit-opencl
  pyviennacl
  starpu
  starpu-contrib
  wine1.6

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

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

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

[Alberto Salvia Novella]

** Changed in: fglrx-installer-updates (Ubuntu)
   Importance: Undecided => High

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

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

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

Bug description:
  tried to run upgrades

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: fglrx-updates-core 2:14.201-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  AptOrdering:
   fglrx-updates-core: Configure
   fglrx-updates: Configure
  Architecture: amd64
  Date: Tue Sep 16 17:18:24 2014
  DpkgTerminalLog:
   Setting up fglrx-updates-core (2:14.201-0ubuntu1) ...
   update-alternatives: error: alternative x86_64-linux-gnu_fglrx_modconf can't 
be slave of x86_64-linux-gnu_gfxcore_conf: it is a slave of 
x86_64-linux-gnu_gl_conf
   dpkg: error processing package fglrx-updates-core (--configure):
subprocess installed post-installation script returned error exit status 2
  DuplicateSignature: package:fglrx-updates-core:2:14.201-0ubuntu1:subprocess 
installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2014-09-02 (14 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta1 amd64 (20140828)
  SourcePackage: fglrx-installer-updates
  Title: package fglrx-updates-core 2:14.201-0ubuntu1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Changed in: lightdm/1.12
   Status: Fix Committed => Fix Released

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

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

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 1379446] Re: gnome-control-center.real crashed with SIGSEGV in gtk_lock_button_set_permission()

[Alberto Salvia Novella]

** Changed in: deja-dup (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome-control-center.real crashed with SIGSEGV in
  gtk_lock_button_set_permission()

Status in Ubuntu GNOME:
  Fix Released
Status in “deja-dup” package in Ubuntu:
  Confirmed

Bug description:
  g-c-c 3.14 crashes when loading the Backup panel
  (This also affects 3.12 in utopic)

  ProblemType: CrashDistroRelease: Ubuntu 14.10
  Package: gnome-control-center 1:3.14.0-1ubuntu1~utopic1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Oct  9 19:30:35 2014
  ExecutablePath: /usr/bin/gnome-control-center.real
  InstallationDate: Installed on 2014-09-19 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140917)
  ProcCmdline: /usr/bin/gnome-control-center.real --overview
  SegvAnalysis:
   Segfault happened at: 0x7faac2be3743 :
cmp%rax,(%rdx)
   PC (0x7faac2be3743) ok
   source "%rax" ok
   destination "(%rdx)" (0x6a65643a706c6568) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11SourcePackage: gnome-control-center
  StacktraceTop:
   gtk_lock_button_set_permission () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center.real crashed with SIGSEGV in 
gtk_lock_button_set_permission()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  usr_lib_gnome-control-center: deja-dup 32.0-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-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: lightdm is leaking FDs -fix

[Robert Ancell]

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

** Changed in: lightdm/1.12
   Status: Triaged => Fix Released

** Changed in: lightdm/1.10
   Status: Triaged => Fix Released

** Changed in: lightdm
   Status: Triaged => Fix Released

-- 
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:
  lightdm is leaking FDs -fix

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:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Triaged
Status in Fedora:
  Unknown

Bug description:
  Description of problem:
  Each time the greeter starts the number of open FDs increase. After each 
login and logout cycle the number of open FDs is increased. Which over time 
leads to impossible logins and the message in /var/log/messages is:

  Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipe to communicate with session process: To...en files
  Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files
  Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files

  
  Tested on:
  Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0

  Steps to Reproduce:

  1. login on a console and find the pid of main lightdm process then:
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  26

  2. switch to X console and login through lightdm and then logout

  3. go back on comsole
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  32

  Here is a patch that fixes the issue. It may have several lines offset
  because we use modified lightdm but it is good for the original
  version too.

  regards,
  Rumen

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 1364911] Re: Support globbing in seat config sections

[Robert Ancell]

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

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

Title:
  Support globbing in seat config sections

Status in Light Display Manager:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Committed

Bug description:
  Add support for simple globbing in seat config sections.

  Example: if a config section [Seat:seatFoo*] is available in
  lightdm.conf, it will match any seat name starting with "seatFoo",
  like "seatFooBar", "seatFooBaz", etc.

  In particular, [Seat:seat*] will match any seat added from logind
  (including seat0), and [Seat:*] will match any seat (including those
  eventually added from other mechanisms than logind), just as
  [SeatDefaults] currently does.

  It was already merged into trunk in revision 2040, but has been
  reverted in revision 2042 due to some unexpected problem, so I'm
  opnening this bug report to keep track of changes.

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

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

[Desktop-packages] [Bug 1377373] Re: Variables defined twice in config files lead to crash

[Robert Ancell]

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

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

Title:
  Variables defined twice in config files lead to crash

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:
  In Progress
Status in “lightdm” source package in Utopic:
  Fix Released
Status in “lightdm” package in Debian:
  Fix Released

Bug description:
  [Impact]
  Having the same configuration variable defined in two places causes LightDM 
to a double free and potentially crash.

  [Test Case]
  1. Install two configuration files in /etc/lightdm/lightdm.conf.d which both 
define the same variable.
  2. Run LightDM
  Expected result:
  LightDM runs correctly.
  Observed result:
  LightDM double frees a variable (seen with valgrind) and can crash.

  [Regression Potential]
  Low. The fix is not to double free the variable.

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

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

[Desktop-packages] [Bug 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces

[Robert Ancell]

** Changed in: lightdm/1.10
   Status: Triaged => Fix Released

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

** Changed in: lightdm/1.12
   Status: Triaged => Fix Released

** Changed in: lightdm
   Status: Triaged => Fix Released

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

Title:
  VNC / XDMCP server cannot be configured to listen on specific
  interfaces

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:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Triaged

Bug description:
  There doesn't seem to be any obvious way to force LightDM's VNC server
  to listen on only specified interfaces, most notably localhost. This
  creates a security issue, as the best and most secure way to access a
  VNC server is through an SSH tunnel where the client will only connect
  to its localhost on a particular port having all connections through
  the tunnel to the server's localhost port.

  If there is a proper way to do this or some sort of work-around, I
  would be very interested in how to do so. As of right now, this makes
  LightDM's VNC server unusable for me.

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

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

[Desktop-packages] [Bug 1376357] Re: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

[Robert Ancell]

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

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

Title:
  lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Won't Fix
Status in Light Display Manager 1.12 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released

Bug description:
  I was trying to figure out where excessive file system writes were
  coming from on the ubuntu phone (to try to reduce flash writes and hence 
reduce power
  consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the 
same debug message written to every every 300 seconds:

  tail -f /var/log/lightdm/lightdm.log
  [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed
  [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed

  while this isn't much of a message, it still is causing file system
  writes every 5 minutes for the same debug message. Is this necessary?
  The fact that it is the same message about the same account and that
  it occurs every 300 seconds make me wonder if we can cull this
  particular piece of repeated logging.

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

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

[Desktop-packages] [Bug 1382563] Re: Cant install proprietary drivers/fglrx

[Alberto Salvia Novella]

** Changed in: fglrx-installer (Ubuntu)
   Importance: Undecided => High

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

Title:
  Cant install proprietary drivers/fglrx

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

Bug description:
  I have been trying to install proprietary ati drivers from amd website
  but every time I reboot system it boots into black screen after which
  I have to purge them.

  Second problem arises when I try to install fglrx from Ubuntu repos
  through terminal which doesnt allow me to install drivers without
  removing wine/playonlinux.Now I am stuck with open-source ones

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: fglrx (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Oct 17 15:32:15 2014
  DistUpgraded: 2014-09-30 13:15:49,778 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.18, 3.16.0-22-generic, x86_64: installed
   vboxhost, 4.3.18, 3.16.0-23-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Redwood PRO [Radeon HD 
5550/5570/5630/6510/6610/7570] [1002:68d9] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:035c]
  InstallationDate: Installed on 2014-09-30 (17 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: System manufacturer P5K
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=bd037ede-2437-4379-ae70-faebef6105e9 ro quiet splash
  SourcePackage: fglrx-installer
  UpgradeStatus: Upgraded to utopic on 2014-09-30 (17 days ago)
  dmi.bios.date: 02/25/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1005
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5K
  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.:bvr1005:bd02/25/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5K
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git1409301830.00847f~gd~u
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.4~git1410170730.e1d363~gd~u
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.4~git1410170730.e1d363~gd~u
  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.5.99+git1410150730.636a63~gd~u
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git1410161932.6b98f1~gd~u
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git1410050730.762b22~gd~u
  xserver.bootTime: Fri Oct 17 15:14:26 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputRazer DeathAdder MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1392065] Re: grub

[Seth Arnold]

Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.

Submitting the bug about the proper source package is essential. For
help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally,
in the report please include:

1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> 
About Ubuntu.
2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by 
checking in Synaptic.
3) What happened and what you expected to happen.

The Ubuntu community has also created debugging procedures for a wide
variety of packages at https://wiki.ubuntu.com/DebuggingProcedures .
Following the debugging instructions for the affected package will make
your bug report much more complete. Thanks!


** Information type changed from Private Security to Public

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

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

Title:
  grub

Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  grub error and I cannot log without the live CD. Trying ot repair
  through the live CD.

  Help me! Please

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CasperVersion: 1.340
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 12 21:26:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7592]
  LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
  MachineType: MSI MS-7592
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V26.6
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G41M-S01 (MS-7592)
  dmi.board.vendor: MSI
  dmi.board.version: 5.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 5.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV26.6:bd03/02/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-S01(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0:
  dmi.product.name: MS-7592
  dmi.product.version: 5.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Nov 12 21:03:22 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5906 
   vendor AOC
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1307792] Re: Packages nvidia-libopencl1-* should provide libopencl-1.1-1

[Alberto Salvia Novella]

** Changed in: nvidia-cuda-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Packages nvidia-libopencl1-* should provide libopencl-1.1-1

Status in “nvidia-cuda-toolkit” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed
Status in “nvidia-cuda-toolkit” package in Debian:
  Fix Released

Bug description:
  The nvidia-opencl-dev package depends on nvidia-libopencl1-331 |
  nvidia-libopencl1-331-updates. This dependency is too strict as
  nvidia-libopencl1-334 and nvidia-libopencl1-337 will also satisfy it.
  There should be a virtual dependency (libopencl1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-cuda-toolkit/+bug/1307792/+subscriptions

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

[Desktop-packages] [Bug 1368168] Re: package fglrx-core (not installed) failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2

[Alberto Salvia Novella]

** Changed in: fglrx-installer (Ubuntu)
   Importance: Undecided => High

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

Title:
  package fglrx-core (not installed) failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 2

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

Bug description:
  during apt-upgrade dpkg return an error on upgrading fglrx :

  update-alternatives reports bad gl conf

  (fresh ubuntu-gnome 14.10 beta 1 install)

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: fglrx-core (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Sep 11 12:28:01 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.16.0-14-generic, x86_64: installed
   fglrx-updates-core, 14.201, 3.16.0-14-generic, x86_64: installed
  DuplicateSignature: package:fglrx-core:(not installed):le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 2
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 2
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / 
R9 280X] [1002:6798] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Tahiti XTL [Radeon R9 280X DirectCU II 
TOP] [1043:3006]
  InstallationDate: Installed on 2014-09-08 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140826)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=7cc8a237-7b49-4025-9d12-b6d70626d0da ro quiet splash vt.handoff=7
  SourcePackage: fglrx-installer
  Title: package fglrx-core (not installed) failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH Z87
  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.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHZ87:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.fglrx-installer: fglrx-installer N/A
  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.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Sep 11 11:04:42 2014
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: 
No such file or directory]
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu9
  xserver.video_driver: fglrx

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

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

[Desktop-packages] [Bug 1306363] Re: Session-Saver Plugin Missing from gedit-plugins

[Alberto Salvia Novella]

** Changed in: gedit-plugins (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Session-Saver Plugin Missing from gedit-plugins

Status in Gedit Developer Plugins:
  New
Status in “gedit-plugins” package in Ubuntu:
  Confirmed

Bug description:
  I open a lot of tabs in gedit, so saving each one of them is
  cumbersome if I need to reboot or want to continue a project the next
  day.

  The session-saver plugin addresses this need, but no longer seems to
  be included in the gedit-plugins package in Ubuntu 14.04.

  How can we get that added back?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gedit-plugins 3.10.1-1ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 10 23:49:58 2014
  InstallationDate: Installed on 2014-04-03 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  SourcePackage: gedit-plugins
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1383863] Re: Choosing colors from palette crash

[Kendzi]

Bug #1323815 looks very similar...

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

Title:
  Choosing colors from palette crash

Status in “inkscape” package in Ubuntu:
  New

Bug description:
  I try to chose color for drawed lines. I do it by moving mouse under
  color palette at the bottom of inkscape window and right clicking on
  color and the from pop-up menu I chose "Set fill". It is working few
  times but after that it stops. Right clicking on palette don't work
  pop-up menu don't appear at all. After next few attempt inkscape
  generate error message as shown in attachment. I try to use inkscape
  version 0.48.4 r9939. After restart the problem repeats. It is not
  possible to use Inkscape for me without choosing colors.

  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 21 21:10:31 2014
  InstallationDate: Installed on 2013-07-12 (465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to trusty on 2014-05-20 (153 days ago)

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

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

[Desktop-packages] [Bug 1354046] Re: no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up

[Alberto Salvia Novella]

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  no 3d acceleration with error [drm:intel_dp_start_link_train] *ERROR*
  too many full retries, give up

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

Bug description:
  Description:
  3D games, video (especially flash) makes computer unresponsive. The problem 
has been present since upgrade to Utopic, but have recently become worse, maybe 
 because of error message

  [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up

  which appears in all terminals.

  How to reproduce:
  Start a 1080p video. e.g. Note that the video is not run from an encrypted 
folder.
  Or watch a video on youtube.
  Reproducable for new users as well, so not related to /home/$USER

  What happens:
  Usage on all four CPUs on my DELL XPS 13 DEVELOPER EDITION will be between 
30% and 100%.

  What I expected:
  Expected same 3D performance as on Thrusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
    * Setting up X socket directories...   
  [ OK ]
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Aug  7 17:03:51 2014
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.12, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.12, 3.13.0-27-generic, x86_64: installed
   vboxhost, 4.3.12, 3.13.0-29-generic, x86_64: installed
   vboxhost, 4.3.12, 3.16.0-5-generic, x86_64: installed
   vboxhost, 4.3.12, 3.16.0-6-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:058b]
  InstallationDate: Installed on 2013-08-27 (345 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  MachineType: Dell Inc. Dell System XPS L322X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=221de9c1-f10a-4be4-9273-5c12864c8680 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  SystemImageInfo: Error: [Errno 2] No such file or directory: 
'system-image-cli'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0PJHXN
  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.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1b1
  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 
10.0.0-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Aug  7 16:54:59 2014
  xserver.configfile: default
  xserver.errors:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu9

[Desktop-packages] [Bug 1392083] [NEW] Black screen after boot screen - fglrx new installed and fixed

[Ben]

Public bug reported:

black screen problem. fglrx (proprietär) new installed and fixed. But
very long booting time now.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 12 23:05:46 2014
DistUpgraded: 2014-11-11 21:54:08,837 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 alsa-hda, 0.201303211238~precise1, 3.2.0-70-generic, x86_64: installed
 alsa-hda, 0.201303211238~precise1, 3.2.0-72-generic, x86_64: installed
 fglrx, 13.350.1, 3.13.0-40-generic, x86_64: installed
 vboxhost, 4.2.26, 3.13.0-40-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e214]
InstallationDate: Installed on 2012-05-28 (898 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=00b01f55-6329-416f-a706-a487895773ab ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-11-11 (1 days ago)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: 990FX Extreme3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2
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.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Nov 12 21:26:03 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors: AIGLX error: failed to open 
/usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.2
xserver.video_driver: fglrx

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


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

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

Title:
  Black screen after boot screen - fglrx new installed and fixed

Status in “xorg” package in Ubuntu:
  New

Bug description:
  black screen problem. fglrx (proprietär) new installed and fixed. But
  very long booting time now.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 12 23:05:46 2014
  DistUpgraded: 2014-11-11 21:54:08,837 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  Dkms

[Desktop-packages] [Bug 1383863] Re: Choosing colors from palette crash

[Kendzi]

Really no one care?

I run Inskape from console. When that bug happen this error is printed:

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive:
assertion 'GTK_IS_WIDGET (widget)' failed

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive:
assertion 'GTK_IS_WIDGET (widget)' failed

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive:
assertion 'GTK_IS_WIDGET (widget)' failed

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive:
assertion 'GTK_IS_WIDGET (widget)' failed

(inkscape:5264): GLib-GObject-WARNING **: invalid unclassed pointer in
cast to 'GtkContainer'

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_container_foreach: assertion
'GTK_IS_CONTAINER (container)' failed

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_widget_show_all: assertion
'GTK_IS_WIDGET (widget)' failed

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_widget_set_sensitive:
assertion 'GTK_IS_WIDGET (widget)' failed

(inkscape:5264): GLib-GObject-WARNING **: invalid unclassed pointer in
cast to 'GtkMenu'

(inkscape:5264): Gtk-CRITICAL **: IA__gtk_menu_popup: assertion
'GTK_IS_MENU (menu)' failed

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

Title:
  Choosing colors from palette crash

Status in “inkscape” package in Ubuntu:
  New

Bug description:
  I try to chose color for drawed lines. I do it by moving mouse under
  color palette at the bottom of inkscape window and right clicking on
  color and the from pop-up menu I chose "Set fill". It is working few
  times but after that it stops. Right clicking on palette don't work
  pop-up menu don't appear at all. After next few attempt inkscape
  generate error message as shown in attachment. I try to use inkscape
  version 0.48.4 r9939. After restart the problem repeats. It is not
  possible to use Inkscape for me without choosing colors.

  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 21 21:10:31 2014
  InstallationDate: Installed on 2013-07-12 (465 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: inkscape
  UpgradeStatus: Upgraded to trusty on 2014-05-20 (153 days ago)

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

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

[Desktop-packages] [Bug 1312255] Re: [systemd] nvidia-prime package needs systemd unit or init.d script

[Alberto Salvia Novella]

** Changed in: nvidia-prime (Ubuntu)
   Importance: Undecided => High

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

Title:
  [systemd] nvidia-prime package needs systemd unit or init.d script

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

Bug description:
  With systemd as pid 1

  nvidia-prime package is pulled as a dependency of nvidia-331-updates package.
  When I tried to install the nvidia-331-updates package it gave me an error of 
installation on nvidia-prime due to

  "initctl: Unable to connect to Upstart: Failed to connect to socket
  /com/ubuntu/upstart: Connection refused"

  The full terminal stdout is

  Setting up nvidia-prime (0.6.2) ...
  initctl: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused
  invoke-rc.d: unknown initscript, /etc/init.d/nvidia-prime not found.
  dpkg: error processing package nvidia-prime (--configure):
  subprocess installed post-installation script returned error exit status 100

  and at the end

  Errors were encountered while processing:
   nvidia-prime
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  This problem didn't prevent the nvidia-331-updates package from being
  installed. Nvidia driver installed properly and have worked as it
  should after a reboot, but the nvidia-prime "didn't make it".

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 24 18:37:04 2014
  InstallationDate: Installed on 2014-03-24 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1332848] Re: upowerd crashed with SIGABRT in __assert_fail_base()

[Alberto Salvia Novella]

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

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

Title:
  upowerd crashed with SIGABRT in __assert_fail_base()

Status in “libimobiledevice” package in Ubuntu:
  Confirmed
Status in “upower” package in Ubuntu:
  Confirmed

Bug description:
  error right after login

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: upower 0.9.23-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: i386
  Date: Wed Jun 18 18:21:27 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-05-21 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  Signal: 6
  SourcePackage: upower
  StacktraceTop:
   __assert_fail_base (fmt=0xb73bab94 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0xb740baa1 "data", 
file=file@entry=0xb740bac9 "plist.c", line=line@entry=194, 
function=function@entry=0xb740bdcb "plist_copy_node") at assert.c:92
   __GI___assert_fail (assertion=0xb740baa1 "data", file=0xb740bac9 "plist.c", 
line=194, function=0xb740bdcb "plist_copy_node") at assert.c:101
   ?? () from /usr/lib/i386-linux-gnu/libplist.so.2
   plist_copy () from /usr/lib/i386-linux-gnu/libplist.so.2
   ?? () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
  Title: upowerd crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1095534] Re: Remmina remote desktop client goes fullscreen on the wrong display

[Alberto Salvia Novella]

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

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

Title:
  Remmina remote desktop client goes fullscreen on the wrong display

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  When the fullscreen button on the toolbar is used with multiple
  displays enabled, Remmina maximizes on a random display rather than on
  the display where it is placed.

  To replicate on a computer with multiple displays:

  1. Launch Remmina.
  2. Connect to a computer using RDP protocol.
  3. Click the full screen button.

  The application flips over to the other display and goes full screen.

  4. Restore the application.
  5. Drag it back to the display where you want it.
  6. Click the full screen button again.

  The application flips over to the other display and goes full screen.

  The expectation is that the application should stay on the display
  where I put it or it should offer an option to allow me to specify the
  screen I want it on.

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

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

[Desktop-packages] [Bug 1058365] Re: Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN

[Alberto Salvia Novella]

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

** Changed in: empathy (Ubuntu)
   Importance: High => Medium

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

Title:
  Empathy (telepathy-sofiasip) cannot connect to SIP server via VPN

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Hi, All!

  I am on Ubuntu 12.04 amd64 and I connect to my office network using Cisco VPN 
(network-manager-vpnc). The problem is that Empathy (with telepathy-sofiasip 
installed) cannot connect to a SIP-server inside VPN (while e.g., Ekiga can).
  Some traces taken with Wireshark show up that Empathy sends packages into the 
VPN tunnel with properly resolved destination IP-address but with wrong source 
IP-address (eth0 instead of tun0).

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

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

[Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep

[Alberto Salvia Novella]

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
   Importance: Undecided => Critical

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

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

Title:
  DPMS support broken, fails to wake up the monitor after putting it to
  sleep

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

Bug description:
  Also affects nvidia-graphics-drivers-319

  The effect is identical to 
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
  but with Nvidia instead of AMD/ATI drivers.

  HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
  display

  Once the display shuts off, it will not be woken up anymore and the screen 
stays dark.
  Only a restart of the Xserver will bring back the display at that point.

  A cycle of
  xset dpms force off; sleep 30; xset dpms force on
  will leave the display dark.

  At the moment I help myself by not allowing DPMS to switch off the display:
  neuffer@charion:~$ xset dpms 0 0 0

  neuffer@charion:~$ xset -q -d :0.0
  Keyboard Control:
    auto repeat:  onkey click percent:  0LED mask:  
    XKB indicators:
  00: Caps Lock:   off01: Num Lock:off02: Scroll Lock: off
  03: Compose: off04: Kana:off05: Sleep:   off
  06: Suspend: off07: Mute:off08: Misc:off
  09: Mail:off10: Charging:off11: Shift Lock:  off
  12: Group 2: off13: Mouse Keys:  off
    auto repeat delay:  500repeat rate:  20
    auto repeating keys:  00ffdbbf
  fadfffefffed
  9fff
  fff7
    bell percent:  50bell pitch:  400bell duration:  100
  Pointer Control:
    acceleration:  2/1threshold:  4
  Screen Saver:
    prefer blanking:  yesallow exposures:  yes
    timeout:  0cycle:  0
  Colors:
    default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
  Font Path:
    
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins
  DPMS (Energy Star):
    Standby: 0Suspend: 0Off: 0
    DPMS is Enabled
    Monitor is On

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.20-0ubuntu9
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Sat Jan 11 12:06:30 2014
  InstallationDate: Installed on 2014-01-07 (3 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: nvidia-graphics-drivers-331
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1364911] Re: Support globbing in seat config sections

[Robert Ancell]

** Changed in: lightdm
   Status: Triaged => Fix Committed

** Changed in: lightdm
Milestone: None => 1.13.0

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

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

** Changed in: lightdm (Ubuntu)
   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/1364911

Title:
  Support globbing in seat config sections

Status in Light Display Manager:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  Fix Committed

Bug description:
  Add support for simple globbing in seat config sections.

  Example: if a config section [Seat:seatFoo*] is available in
  lightdm.conf, it will match any seat name starting with "seatFoo",
  like "seatFooBar", "seatFooBaz", etc.

  In particular, [Seat:seat*] will match any seat added from logind
  (including seat0), and [Seat:*] will match any seat (including those
  eventually added from other mechanisms than logind), just as
  [SeatDefaults] currently does.

  It was already merged into trunk in revision 2040, but has been
  reverted in revision 2042 due to some unexpected problem, so I'm
  opnening this bug report to keep track of changes.

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

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

[Desktop-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

[Martin Matuska]

This has been fixed upstream:
https://github.com/karelzak/util-linux/issues/119
https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb

** Package changed: gvfs (Ubuntu) => util-linux (Ubuntu)

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in “util-linux” package in Ubuntu:
  Confirmed

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t  to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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

[Desktop-packages] [Bug 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Jay Berkenbilt]

I guess getPageContents should just return an empty vector in that case
and the documentation should specify that an empty vector might be
returned. This is already the case if /Contents is literally an empty
array. Thanks for the triage.

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

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

[Desktop-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

[Launchpad Bug Tracker]

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

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

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in “util-linux” package in Ubuntu:
  Confirmed

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t  to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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

[Desktop-packages] [Bug 1390961] Re: bug at initializing a radeon graphics card on pci-e

[Eric]

Ok, So I fiddled with kernel boot parameters and enable_mtrr_cleanup
seems to do fix the MTRR mess like in:

$ cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=35910738-c8fc-48e5-8b80-5c7766a720fc ro enable_mtrr_cleanup

So I'll close the bug

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

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

Title:
  bug at initializing a radeon graphics card on pci-e

Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  I have a Thinkpad T60 running 14.10 with a built-in intel graphics
  card. I plug the laptop in a docking station which has a radeon cedar
  graphics card on a pci-e port. Card can't be initialized.

  Nov  9 19:35:04 pico-T60 kernel: [  133.635825] [drm] radeon kernel 
modesetting enabled.
  Nov  9 19:35:04 pico-T60 kernel: [  133.656080] radeon :0c:00.0: Refused 
to change power state, currently in D3
  Nov  9 19:35:04 pico-T60 kernel: [  133.656672] [drm] initializing kernel 
modesetting (CEDAR 0x1002:0x68F9 0x1043:0x0471).
  Nov  9 19:35:04 pico-T60 kernel: [  133.656703] [drm] register mmio base: 
0x8800
  Nov  9 19:35:04 pico-T60 kernel: [  133.656707] [drm] register mmio size: 
131072
  Nov  9 19:35:04 pico-T60 kernel: [  133.656769] radeon :0c:00.0: Invalid 
ROM contents
  Nov  9 19:35:04 pico-T60 kernel: [  133.656903] radeon :0c:00.0: Invalid 
ROM contents
  Nov  9 19:35:04 pico-T60 kernel: [  133.656997] [drm:radeon_get_bios] *ERROR* 
Unable to locate a BIOS ROM
  Nov  9 19:35:04 pico-T60 kernel: [  133.657106] radeon :0c:00.0: Fatal 
error during GPU init
  Nov  9 19:35:04 pico-T60 kernel: [  133.657204] [drm] radeon: finishing 
device.
  Nov  9 19:35:04 pico-T60 kernel: [  133.657208] [TTM] Memory type 2 has not 
been initialized
  Nov  9 19:35:04 pico-T60 kernel: [  133.664743] radeon: probe of :0c:00.0 
failed with error -22

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  Uname: Linux 3.18.0-031800rc2-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Nov  9 20:03:03 2014
  DistUpgraded: 2014-10-30 20:59:07,260 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.18, 3.16.0-24-generic, i686: installed
   virtualbox, 4.3.18, 3.18.0-031800rc2-generic, i686: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
 Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a]
  InstallationDate: Installed on 2012-06-18 (874 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MachineType: LENOVO 1952AT7
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-031800rc2-generic 
root=UUID=35910738-c8fc-48e5-8b80-5c7766a720fc ro quiet splash 
enable_mtrr_cleanup pciehp.pciehp_force=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-30 (9 days ago)
  dmi.bios.date: 03/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE7WW (2.27 )
  dmi.board.name: 1952AT7
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 1952at7l3a9167
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE7WW(2.27):bd03/21/2011:svnLENOVO:pn1952AT7:pvrThinkPadT60:rvnLENOVO:rn1952AT7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1952AT7
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Nov  9 19:58:46 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/lo

[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable

[Jbankes1]

Same issue here, It appears that after I scan one time it switches the
source of the scan to another scanner on my network. The LiDe goes
missing from the list. I am also using Simple Scan.

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

Title:
  Canon LIDE 110 can only scan once, then I need to replug the usb cable

Status in Simple Scan:
  New
Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. 
  The problem is after first scan, I can not scan for second time. I need to 
reconnect the USB cable to use the scanner again.

  # TEST 1 : without reconnecting the usb cable
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I don't unplug plug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # FAIL
  scanimage: no SANE devices found

  # TEST 2 : reconnect usb cable between scan attempts
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I unplug and replug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # SUCCESS
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total

  francois@pc:~$ dmesg # extract
  [  829.365158] usb 3-1: USB disconnect, device number 2
  [  834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [  834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [  834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  834.952522] usb 3-1: Product: CanoScan
  [  834.952524] usb 3-1: Manufacturer: Canon
  [ 1623.738811] usb 3-1: USB disconnect, device number 4
  [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW 
list!
  [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1625.546334] usb 3-1: Product: CanoScan
  [ 1625.546336] usb 3-1: Manufacturer: Canon

  francois@pc:~$ uname -a && cat /etc/issue
  Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
  Ubuntu 13.04 \n \l

  The problem was reported here by someone else :
  http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect-
  usb-for-each-scan

  Thanks
  François

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1184699/+subscriptions

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

[Desktop-packages] [Bug 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Tobias Hoffmann]

Per PDF Spec, the /contents key in a Page dictionary is optional.
The attached pdf's page 9 has no /contents key.

But QPdfObjectHandle::getPageContents() throws an exception;
cups-filter (pdftopdf) calls it via QPDFObjectHandle::addPageContents().

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

-- 
Mailing list: https://launchpad.net/~desktop-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: lightdm is leaking FDs -fix

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.2

-- 
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:
  lightdm is leaking FDs -fix

Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.12 series:
  Triaged
Status in Light Display Manager 1.2 series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Triaged
Status in Fedora:
  Unknown

Bug description:
  Description of problem:
  Each time the greeter starts the number of open FDs increase. After each 
login and logout cycle the number of open FDs is increased. Which over time 
leads to impossible logins and the message in /var/log/messages is:

  Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipe to communicate with session process: To...en files
  Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files
  Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files

  
  Tested on:
  Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0

  Steps to Reproduce:

  1. login on a console and find the pid of main lightdm process then:
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  26

  2. switch to X console and login through lightdm and then logout

  3. go back on comsole
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  32

  Here is a patch that fixes the issue. It may have several lines offset
  because we use modified lightdm but it is good for the original
  version too.

  regards,
  Rumen

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 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Tobias Hoffmann]

/Contents  is the correct spelling.

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

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

[Desktop-packages] [Bug 1392048] Re: File not printed "Exception: unknown object type inspecting /Contents key in page dictionary"

[Tobias Hoffmann]

Exception is thrown in libqpdf

** Package changed: cups-filters (Ubuntu) => qpdf (Ubuntu)

** Also affects: cups-filters (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  File not printed  "Exception: unknown object type inspecting /Contents
  key in page dictionary"

Status in “cups-filters” package in Ubuntu:
  New
Status in “qpdf” package in Ubuntu:
  New

Bug description:
  Hello. I am trying to print this file:
  https://www.dropbox.com/s/jpw5szew0f9z51a/1415820191149.pdf?dl=0

  With CUPS 1.7.2 on Lubuntu 14.04. and the HP LaserJet m9050 MFP pcl3,
  hpcups 3.14.6 PPD.

  I haven't been able to print the file

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

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

[Desktop-packages] [Bug 879218] Re: some users prefer the old grid behaviour (dividing each time the keybinding are used)

[Vivek Ramadoss]

So is there a fix for making ctrl + alt + numpad 4 and numpad 6 cycle
between the various widths for multiple keypresses instead of just being
half? Because my compiz grid still does not work. I am on Ubuntu 12.04
LTS.

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

Title:
  some users prefer the old grid behaviour (dividing each time the
  keybinding are used)

Status in Compiz:
  Fix Released
Status in Compiz Grid Plugin:
  Fix Committed
Status in Compiz Main Plugins:
  Fix Committed
Status in Unity:
  Won't Fix
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz-plugins-main” package in Ubuntu:
  Fix Committed

Bug description:
  I've used the Compiz Grid function for a long time and I generally use
  it to set my browser to the right 2/3 or 3/4 of the screen and have
  other apps on the top or bottom half of the remaining part. Now when I
  press ctrl + alt numpad 4 or numpad 6 it only does half and when
  pressing it a second or third time it does nothing. The options for
  different sizes work for all the corners and top and bottom. When I
  press ctrl + alt numpad 9 it does the same thing as pressing ctrl +
  alt numpat 8.  Here's a video that may illustrate the problem better
  than my description.

  http://www.youtube.com/watch?v=i3WC0BnXe5E

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.22.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,move,gnomecompat,mousepoll,imgpng,unitymtgrabhandles,regex,animation,grid,snap,expo,workarounds,ezoom,resize,vpswitch,place,wall,staticswitcher,fade,session,scale,unityshell]
  Date: Thu Oct 20 23:03:00 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

  A video of the latest Grid version (also showing this fix in action):
  
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/745159/+attachment/3660185/+files/GridAllFunctionalityFullyFixed.mp4

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

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

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

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

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

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

** Changed in: lightdm/1.12
Milestone: None => 1.12.2

** Changed in: lightdm
Milestone: None => 1.13.0

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

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

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

** Also affects: lightdm (Ubuntu Vivid)
   Importance: Medium
   Status: Fix Released

** Changed in: lightdm (Ubuntu Vivid)
   Status: Fix Released => 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/1383321

Title:
  Support XDG DesktopNames field in session files

Status in Light Display Manager:
  Fix Committed
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.12 series:
  Fix Committed
Status in “lightdm” package in Ubuntu:
  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 Committed

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 1384297] Re: gpu i915 OOPS on power change intel_display_power_put+0xf9

[David JB]

What looks to be the same issue affects my Ubuntu 14.10 install on my
MacBook Pro 10,2.  The screen locks up, but the mouse is able to be
moved and seen moving, and interacting with windows and desktop elements
is stlll possible (eg if a video is playing with VLC, can press Space to
pause and resume and hear audio), though because they are 'frozen', no
visual changes happen.

After about 5 minutes or so, I'm able to continue using the computer
without issues.  I switch TTY during the 'freeze' and the screen remains
blank for the period, and when the login console appears, I can switch
back to TTY7 and continue using my graphical session, no restart of
anything required.

For what it's worth, output of dmesg:

[47924.464983] WARNING: CPU: 0 PID: 9647 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:5997 
intel_display_power_put+0x14c/0x160 [i915]()
[47924.464986] Modules linked in: hfsplus nls_utf8 udf crc_itu_t uas 
usb_storage btusb snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic 
joydev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
snd_hda_intel applesmc snd_hda_controller snd_hda_codec snd_hwdep 
crct10dif_pclmul input_polldev crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw snd_pcm gf128mul glue_helper ablk_helper cryptd snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq bnep uvcvideo videobuf2_vmalloc rfcomm 
bluetooth wl(POE) 6lowpan_iphc bcm5974 i915 snd_seq_device drm_kms_helper 
snd_timer videobuf2_memops videobuf2_core v4l2_common videodev media drm 
lpc_ich cfg80211 snd i2c_algo_bit mei_me mei soundcore shpchp sbs binfmt_misc 
sbshc apple_gmux mac_hid nls_iso8859_1 parport_pc ppdev video
[47924.465046]  apple_bl lp parport hid_generic hid_apple usbhid hid sdhci_pci 
sdhci ahci libahci
[47924.465060] CPU: 0 PID: 9647 Comm: kworker/0:0 Tainted: PW  OE 
3.16.0-24-generic #32-Ubuntu
[47924.465063] Hardware name: Apple Inc. MacBookPro10,2/Mac-AFD8A9D944EA4843, 
BIOS MBP102.88Z.0106.B05.1408291503 08/29/2014
[47924.465096] Workqueue: events edp_panel_vdd_work [i915]
[47924.465100]  0009 880140cd3d30 8277fcbc 

[47924.465104]  880140cd3d68 8206fd8d 880087ea002c 
000b
[47924.465108]  880087ea8520 880262905000 880087ea 
880140cd3d78
[47924.465113] Call Trace:
[47924.465123]  [] dump_stack+0x45/0x56
[47924.465130]  [] warn_slowpath_common+0x7d/0xa0
[47924.465135]  [] warn_slowpath_null+0x1a/0x20
[47924.465156]  [] intel_display_power_put+0x14c/0x160 [i915]
[47924.465184]  [] edp_panel_vdd_off_sync+0xf4/0x1e0 [i915]
[47924.465209]  [] edp_panel_vdd_work+0x34/0x50 [i915]
[47924.465215]  [] process_one_work+0x182/0x4e0
[47924.465219]  [] worker_thread+0x6b/0x6a0
[47924.465224]  [] ? __schedule+0x39d/0x890
[47924.465228]  [] ? process_one_work+0x4e0/0x4e0
[47924.465234]  [] kthread+0xdb/0x100
[47924.465240]  [] ? kthread_create_on_node+0x1c0/0x1c0
[47924.465247]  [] ret_from_fork+0x7c/0xb0
[47924.465255]  [] ? kthread_create_on_node+0x1c0/0x1c0

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

Title:
  gpu i915 OOPS on power change intel_display_power_put+0xf9

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

Bug description:
  [ 3871.551684] WARNING: CPU: 2 PID: 2161 at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/i915/intel_pm.c:5997 
intel_display_power_put+0x14c/0x160 [i915]()
  [ 3871.551686] Modules linked in: ctr ccm ec_sys dm_crypt intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
crc32_pclmul arc4 ghash_clmulni_intel rfcomm dm_multipath scsi_dh bnep 
aesni_intel iwlmvm hid_multitouch aes_x86_64 mac80211 lrw gf128mul glue_helper 
ablk_helper cryptd snd_hda_codec_hdmi snd_hda_codec_realtek iwlwifi 
snd_hda_codec_generic nfsd rtsx_pci_ms snd_hda_intel auth_rpcgss 
snd_hda_controller nfs_acl btusb memstick joydev snd_hda_codec nfs lockd 
snd_hwdep bluetooth snd_seq_midi snd_seq_midi_event sunrpc snd_rawmidi 
snd_soc_rt5640 6lowpan_iphc fscache snd_soc_rl6231 cfg80211 snd_seq 
snd_soc_core snd_compress binfmt_misc snd_pcm_dmaengine snd_pcm snd_seq_device 
tpm_infineon snd_timer lpc_ich dw_dmac dw_dmac_core i2c_hid 8250_dw 
i2c_designware_platform
  [ 3871.551704]  i2c_designware_core snd shpchp snd_soc_sst_acpi mei_me mei 
spi_pxa2xx_platform mac_hid soundcore serio_raw parport_pc ppdev lp parport 
btrfs xor raid6_pq dm_mirror dm_region_hash dm_log mmc_block usbhid hid 
rtsx_pci_sdmmc i915 i2c_algo_bit rtsx_pci psmouse ahci drm_kms_helper r8169 
libahci mii drm wmi sdhci_acpi video sdhci
  [ 3871.551717] CPU: 2 PID: 2161 Comm: unity-system-co Tainted: GW I   
3.16.0-23-generic #30-Ubuntu
  [ 3871.551718] Hardware name: System76, IncDarter 
UltraThin/Darter UltraThin, BIOS 4.6.5 10/28/2013
  [ 3871.551719]  0009 

[Desktop-packages] [Bug 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf

[Damiön la Bagh]

Here is a video of the bug, LightDM ignores the settings and moves the pointer 
to the right
https://drive.google.com/file/d/0B4c5GbInagPqZEZvUlQxZ01qX0U/view?usp=sharing


Here is a video of a working user session after logging in from LightDM, 
proving that the script works.
https://drive.google.com/file/d/0B4c5GbInagPqNW5BU1BsWGV2cDA/view?usp=sharing

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

Title:
  lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Setup:
  Ubuntu 14.04.1LTS
  IIyama 19" Pro-Lite Touchscreen
  Dell 17" regular monitor

  Due to another bug in the detection of input devices I had to write a
  script to tell Ubuntu which screen to use the touch from the
  touchscreen.

  so I put the following two entries into a basic bash script based on xinput 
list and xrandr -q 
  
  #!/bin/bash
  xinput map-to-output 12 DVI-I-1
  xrandr --output DVI-I-1 --primary
  =

  I added this script to 
/usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf
  and the contents look like this.
  
  [SeatDefaults]
  greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh
  session-setup-script=/usr/local/bin/iiyama-touchscreen.sh
  
  When I start a user session the touchscreen is calibrated and works normally 
with the touch happening on the touchscreen.
  As soon as I logoff into LightDM the touch calibration is off moving the 
pointer a logarithmic distance from the left of the touchscreen. 

  As soon as I log in again, no problems, touch works great, log back
  out into the lightDM greeter and boom touch is all crazy.

  Can lightdm please detect that a touchscreen can only accept touch input and 
output to the touchscreen device??
  Or at least have lightdm actually run the script when given?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  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 Nov 12 22:11:38 2014
  InstallationDate: Installed on 2014-11-03 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  LightdmConfig:
   [SeatDefaults]
   autologin-user=boerske
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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: lightdm is leaking FDs -fix

[Launchpad Bug Tracker]

** Branch linked: lp:lightdm/1.12

** Branch linked: lp:lightdm/1.10

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

Title:
  lightdm is leaking FDs -fix

Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.12 series:
  Triaged
Status in Light Display Manager 1.2 series:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “lightdm” source package in Precise:
  Triaged
Status in “lightdm” source package in Trusty:
  Triaged
Status in “lightdm” source package in Utopic:
  Triaged
Status in “lightdm” source package in Vivid:
  Triaged
Status in Fedora:
  Unknown

Bug description:
  Description of problem:
  Each time the greeter starts the number of open FDs increase. After each 
login and logout cycle the number of open FDs is increased. Which over time 
leads to impossible logins and the message in /var/log/messages is:

  Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipe to communicate with session process: To...en files
  Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files
  Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed 
to create pipes: Too many open files

  
  Tested on:
  Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0

  Steps to Reproduce:

  1. login on a console and find the pid of main lightdm process then:
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  26

  2. switch to X console and login through lightdm and then logout

  3. go back on comsole
  # lsof -p {lightdm_pid} |grep FIFO |wc -l
  32

  Here is a patch that fixes the issue. It may have several lines offset
  because we use modified lightdm but it is good for the original
  version too.

  regards,
  Rumen

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