[Desktop-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

2014-05-28 Thread Simplet
Ubuntu 14.04 fresh install here and same problem.
Daniel's solution works like a charm.

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

Title:
  Media keyboard shortcuts not working

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

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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


[Desktop-packages] [Bug 476211]

2014-05-28 Thread Jose Gómez
I can confirm that the bug is still present in LibreOffice 4.2.4, for
both Windows and Linux.

When the Changes toolbar is enabled, the buttons contained have no
icons, so the 6 buttons require half the width of the screen.

I'd say having a toolbar without icons is more of a bug than an
enhancement.

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

Title:
  [Upstream] Record, accept and reject changes as toolbar

Status in LibreOffice Productivity Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  Feature suggestion: make a toolbar default available in OpenOffice for
  recording, accepting and rejecting changes. And make it easily
  accessible by for example a 'record changes' button on the the
  'standard' toolbar.

  The 'changes' functions are frequently used in office work /
  collaboration. For an efficient workflow they should be easily
  accessible. Now the are (default) only accessible form the (edit) menu
  in OpenOffice 3.1.

  ProblemType: Bug
  Architecture: i386
  Date: Fri Nov  6 08:27:49 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: wl nvidia
  Package: openoffice.org-core 1:3.1.1-5ubuntu1 [modified: 
var/lib/openoffice/basis3.1/program/services.rdb]
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: openoffice.org
  Uname: Linux 2.6.31-14-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2138): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2138): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2286): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2276): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2247): Gdk-WARNING **: 
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a 
pixmap or window
  --- 
  Architecture: i386
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  NonfreeKernelModules: wl
  Package: openoffice.org-core 1:3.2.0-7ubuntu4.1
  PackageArchitecture: i386
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Tags: lucid
  Uname: Linux 2.6.32-23-generic i686
  UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev 
sambashare tape video

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

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


[Desktop-packages] [Bug 1263302] Re: 404 on any page for "More"

2014-05-28 Thread CSRedRat
When this fixed?

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

Title:
  404 on any page for "More"

Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  If you translated any page in Chrome with Google Translate - click on
  top "More" and have 404.

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

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


[Desktop-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor

2014-05-28 Thread Robert Ancell
And bug 1211141 was tracking this feature in 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/1324183

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  New
Status in Unity System Compositor:
  New
Status in The Unity 8 shell:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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


[Desktop-packages] [Bug 1324183] Re: [enhancement] FD passing for unity-system-compositor

2014-05-28 Thread Robert Ancell
lp:~robert-ancell/lightdm/private-mir-connection contains previous work
trying to fix this.

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

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  New
Status in Unity System Compositor:
  New
Status in The Unity 8 shell:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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


[Desktop-packages] [Bug 1324364] [NEW] Sound stopped, banshee crashed.

2014-05-28 Thread vitaly.mzungu
Public bug reported:

Banshee was happily playing in the background, and then no more sound.
Banshee no longer running.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-27.50-lowlatency 3.13.11
Uname: Linux 3.13.0-27-lowlatency i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vitaly 2061 F pulseaudio
 /dev/snd/controlC0:  vitaly 2061 F pulseaudio
Date: Thu May 29 15:16:32 2014
InstallationDate: Installed on 2012-09-22 (614 days ago)
InstallationMedia: Ubuntu-Studio 12.04.1 "Precise Pangolin" - Release i386 
(20120818)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  vitaly 2061 F pulseaudio
 /dev/snd/controlC0:  vitaly 2061 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [MS-7756, Realtek ALC892, Green Headphone Out, Front] No sound at all
UpgradeStatus: Upgraded to trusty on 2014-05-02 (27 days ago)
dmi.bios.date: 04/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77MA-G43 (MS-7756)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd04/20/2012:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7756
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: apport-bug i386 trusty

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

Title:
  Sound stopped, banshee crashed.

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

Bug description:
  Banshee was happily playing in the background, and then no more sound.
  Banshee no longer running.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-27.50-lowlatency 3.13.11
  Uname: Linux 3.13.0-27-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vitaly 2061 F pulseaudio
   /dev/snd/controlC0:  vitaly 2061 F pulseaudio
  Date: Thu May 29 15:16:32 2014
  InstallationDate: Installed on 2012-09-22 (614 days ago)
  InstallationMedia: Ubuntu-Studio 12.04.1 "Precise Pangolin" - Release i386 
(20120818)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vitaly 2061 F pulseaudio
   /dev/snd/controlC0:  vitaly 2061 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [MS-7756, Realtek ALC892, Green Headphone Out, Front] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-05-02 (27 days ago)
  dmi.bios.date: 04/20/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H77MA-G43 (MS-7756)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd04/20/2012:svnMSI:pnMS-7756:pvr1.0:rvnMSI:rnH77MA-G43(MS-7756):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7756
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Desktop-packages] [Bug 1324361] [NEW] Screen blank after resuming from suspend

2014-05-28 Thread Josh
Public bug reported:

I can successfully suspend my Ubuntu session. After hitting the power
button on my desktop to wake up, the computer and monitor turn back on
ok, but the screen comes up blank. The mouse is present and can move,
but there is nothing to interact with. I also cannot switch to other
terminal modes with Ctrl-Alt-F2, etc. The only way to recover is to hard
boot. I tried booting with both S1 and S3 power management modes set in
the bios; S1 does not suspend at all (gives errors) and S3 suspends but
does not wake up properly as described.

I am running Ubuntu 14.04 with Gnome Shell 3.12.1, but the issue
persists with standard Unity Ubuntu as well. I have dual monitors with
an NVIDIA GeForce 8400 GS rev 3 PCI express adapter using nouveau
drivers. I am running full disk encryption; home folder is not
encrypted.

Any advise is much appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed May 28 21:56:12 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation GT218 [GeForce 8400 GS Rev. 3] [10de:10c3] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: eVga.com. Corp. Device [3842:1301]
InstallationDate: Installed on 2014-05-04 (24 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
MachineType: Dell Inc. OptiPlex 360
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-27-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0T656F
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd11/28/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.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 May 28 21:55:06 2014
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: nouveau

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


** Tags: apport-bug freeze i386 suspend 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/1324361

Title:
  Screen blank after resuming from suspend

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I can successfully suspend my Ubuntu session. After hitting the power
  button on my desktop to wake up, the computer and monitor turn back on
  ok, but the screen comes up blank. The mouse is present and can move,
  but there is nothing to interact with. I also cannot switch to other
  terminal modes with Ctrl-Alt-F2, etc. The only way to recover is to
  hard boot. I tried booting with both S1 and S3 power management modes
  set in the bios; S1 does not suspend at all (gives errors) and S3
  suspends but does not wake up properly as described.

  I am running Ubuntu 14.04 with Gnome Shell 3.12.1, but the issue
  persists with standard Unity Ubuntu as well. I have dual monitors with
  an NVIDIA GeForce 8400 GS rev 3 PCI express adapter using nouveau
  drivers. I am running full disk encryption; home folder is not
  encrypted.

  Any advise is much appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386

[Desktop-packages] [Bug 1288309] Re: fake bug: the image is corrupted in an external monitor

2014-05-28 Thread WeiShen
Not a real bug, close it.

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

Title:
  fake bug: the image is corrupted in an external monitor

Status in “xorg” package in Ubuntu:
  Invalid

Bug description:
  Hardware:

  HP Compaq 8510p

  Steps:
  1 boot ubuntu system
  2 plug an external monitor
  3 press Fn + F5 and observe the external monitor
  4 the image is corrupted

  expected results:
  the external monitor should display the image correctly

  How reproducible:
  every time

  other information:
  os: ubuntu desktop 12.04.4
  kernel version:  3.2.0-58-generic x86_64

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

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


[Desktop-packages] [Bug 1254028] Re: [precise] network manager set incorrect /64 prefix from dhcpv6 client

2014-05-28 Thread Bug Watch Updater
** Changed in: network-manager (Debian)
   Status: Confirmed => Fix Released

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

Title:
  [precise] network manager set incorrect /64 prefix from dhcpv6 client

Status in NetworkManager:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released
Status in “network-manager” source package in Precise:
  Fix Released
Status in “network-manager” source package in Quantal:
  Fix Released
Status in “network-manager” source package in Raring:
  Fix Released
Status in “network-manager” source package in Saucy:
  Fix Released
Status in “network-manager” source package in Trusty:
  Fix Released
Status in “network-manager” package in Debian:
  Fix Released

Bug description:
  [Impact]

   * dhcpv6 sets an incorrect netmask on ipv6 networks, leading to
  probable communication failures in certain networks

  [Test Case]

   * You need an ipv6 network using dhcpv6 statefull configuration with
  prefix which is not equal to /64

  [Regression Potential]

   * None, this patch has been accepted upstream and is available since
  quantal

  network-manager in ubuntu precise use incorrect /64 prefix from dhcpv6
  client which cause that internet connection not working on some ipv6
  networks. this problem was fixed in upstream network-manager version
  0.9.6 which is already available in ubuntu quantal and newer - but not
  in ubuntu precise. because this is critical problem (non working
  network/internet) new version of network manager (e.g 0.9.6) or at
  least patch which fixing this problem should be included in ubuntu
  precise which is LTS.

  upstream commit which fixing this problem:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eb460b70dad82d366d35fa5703c0e79a1389e4d1

  more info about it:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661885
  http://bugzilla.gnome.org/show_bug.cgi?id=656610

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

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


[Desktop-packages] [Bug 1245136] Re: Super+Space and Shift+Super+Space hotkeys for keyboard layout switching do not work in Saucy and Unity session

2014-05-28 Thread 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/1245136

Title:
  Super+Space and Shift+Super+Space hotkeys for keyboard layout
  switching do not work in Saucy and Unity session

Status in “unity” package in Ubuntu:
  Expired

Bug description:
  On clean Ubuntu 13.10 install with enabled proposed updates Super+Space and 
Shift+Super+Space are default options for keyboard layout change.
  But they do not work in Unity session.
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Oct 27 12:39:30 2013
  InstallationDate: Installed on 2013-10-20 (6 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1297604] Re: Chromium does not redraw the background when resizing the browser window

2014-05-28 Thread Launchpad Bug Tracker
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Chromium does not redraw the background when resizing the browser
  window

Status in “chromium-browser” package in Ubuntu:
  Expired

Bug description:
  The Chromium browser does not redraw (refresh) the background (i.e.,
  desktop) when resizing. This can be seen when making the browser
  window smaller by dragging its corners. Seen on Chromium Version
  33.0.1750.152 Ubuntu 12.04 (256984).

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

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


[Desktop-packages] [Bug 1262068] Re: nvidia-prime should support gdm also

2014-05-28 Thread Launchpad Bug Tracker
This bug was fixed in the package gdm - 3.10.0.1-0ubuntu6

---
gdm (3.10.0.1-0ubuntu6) utopic; urgency=medium

  * debian/patches/ubuntu_nvidia_prime.patch:
- Add hook to run prime-offload (as root) and prime-switch if
  nvidia-prime is installed (LP: #1262068)
 -- Tim LunnSat, 22 Mar 2014 10:26:40 +1100

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

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

Title:
  nvidia-prime should support gdm also

Status in Ubuntu GNOME:
  Triaged
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends
  on lightdm. This means that

  1. Anyone installing nvidia binary drivers will pull in nvidia-prime and 
subsequently lightdm. As a consequence of this they are also going to get the 
potentially confusing dconf pop-up asking them to choose a DM.
  2. nvidia-prime probably won't work when using gdm

  I haven't looked to closely at how deeply integrated this is with
  lightdm, however we particularly don't want #1 happening, and it would
  be nice if #2 worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 18 16:56:19 2013
  InstallationDate: Installed on 2012-09-23 (451 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1324351] [NEW] Automatically split large files when copying to vfat

2014-05-28 Thread Hopungo Semi-bit
Public bug reported:

Please classify this as feature request.

When file sized >4Gb (e.g. DVD9 ISO image) is copied on VFAT
filesystems, it can't fit on it due to limitations of the fs. I suggest
check before copying such files and give dialog with options to split or
to refuse copying.

Now, the file starts copying, but interrupts in the middle. I had to
remove already copied useless part of the file on destination media and
split/copy file using Double Commander.

VFAT filesystems are still used on most removable media, including phone
cards.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu9.1 [modified: usr/bin/nautilus 
usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server 
usr/lib/nautilus/nautilus-convert-metadata]
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Thu May 29 09:55:05 2014
GsettingsChanges:
 
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Automatically split large files when copying to vfat

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  Please classify this as feature request.

  When file sized >4Gb (e.g. DVD9 ISO image) is copied on VFAT
  filesystems, it can't fit on it due to limitations of the fs. I
  suggest check before copying such files and give dialog with options
  to split or to refuse copying.

  Now, the file starts copying, but interrupts in the middle. I had to
  remove already copied useless part of the file on destination media
  and split/copy file using Double Commander.

  VFAT filesystems are still used on most removable media, including
  phone cards.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu9.1 [modified: usr/bin/nautilus 
usr/bin/nautilus-autorun-software usr/bin/nautilus-connect-server 
usr/lib/nautilus/nautilus-convert-metadata]
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu May 29 09:55:05 2014
  GsettingsChanges:
   
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1262068] Re: nvidia-prime should support gdm also

2014-05-28 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/utopic-proposed/gdm

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

Title:
  nvidia-prime should support gdm also

Status in Ubuntu GNOME:
  Triaged
Status in “gdm” package in Ubuntu:
  Confirmed
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “nvidia-prime” source package in Precise:
  Fix Released

Bug description:
  On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends
  on lightdm. This means that

  1. Anyone installing nvidia binary drivers will pull in nvidia-prime and 
subsequently lightdm. As a consequence of this they are also going to get the 
potentially confusing dconf pop-up asking them to choose a DM.
  2. nvidia-prime probably won't work when using gdm

  I haven't looked to closely at how deeply integrated this is with
  lightdm, however we particularly don't want #1 happening, and it would
  be nice if #2 worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 18 16:56:19 2013
  InstallationDate: Installed on 2012-09-23 (451 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread Peter Curtis
A kernel problem has been identified at
https://bugzilla.kernel.org/show_bug.cgi?id=74861 by kernel commit
bisection  and the simple fix works for me on a Chillblast Defiant mini
laptop which has Haswell/Optimus Architecture, Core i7 Processor and
nVidia GTX 765M graphics running Mint 17 (equivalent to 14.04).

The quick fix is to pass i915.disable_power_well=0 on the kernel command
line which works around the problem, letting audio play at the correct
speed again. After confirmation one can modify /etc/default/grub.

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  Fix Released
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1324334] [NEW] Ctrl+alt+[numpad 5] does not correctly maximize window

2014-05-28 Thread Ian Nicholson
Public bug reported:

When I use ctrl+alt+[numpad 5] to maximize the currently active window,
the window does not move the window title bar into the global title bar.
I've attached a screenshot to demonstrate.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed May 28 21:08:19 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-22 (96 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: "Picture of window titlebar"
   
https://bugs.launchpad.net/bugs/1324334/+attachment/4121806/+files/Screenshot%20from%202014-05-28%2021%3A22%3A38.png

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

Title:
  Ctrl+alt+[numpad 5] does not correctly maximize window

Status in “unity” package in Ubuntu:
  New

Bug description:
  When I use ctrl+alt+[numpad 5] to maximize the currently active
  window, the window does not move the window title bar into the global
  title bar.  I've attached a screenshot to demonstrate.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed May 28 21:08:19 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-22 (96 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1296275] Re: PTP Cameras not working on 14.04, works flawlessly on 12.04

2014-05-28 Thread T_W
Same problem with Samsung Galaxy S4 when mounted in Camera (PTP) mode.

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

Title:
  PTP Cameras not working on 14.04, works flawlessly on 12.04

Status in GVFS:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Triaged

Bug description:
  I have a Canon Powershot A3200 camera. It works perfectly on 12.04,
  pops right up when I plug it in. However on 14.04 nothing happens.

  lsusb outputs shows that the camera is detected, with the right model.

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

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


[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C

2014-05-28 Thread Kieran Clancy
Simon,

It looks like your UEFI variable has a different name:

KBDBacklitLvl-8be4df61-93ca-11d2-aa0d-00e098032b8c

Please do xxd on this and see if it looks similar to my
SecKeyboardBacklightLevel variable.

Thanks for your DSDT. It looks like your machine doesn't have a KBLL
variable... the closest thing I could find was a KBCL variable, but I
have no idea if it does the same thing.

I have uploaded a program to probe the memory at this region, designed
for your DSDT, at:

https://github.com/kieranclancy/probe-dsdt-regions/tree/900x3g

(Note to others, do NOT run this program, it is just for Simon's DSDT
and could break your system. If you want a version of this program for
your machine's DSDT, please ask me.)

If you have time, can you please:

1. Compile this program from the 900x3g branch
2. Reboot to get a relatively clean variable state
3. Save the output of 'sudo ./probe'
4. Dump the KBDBacklitLvl UEFI variable with xxd and save this too.
5. Modify the KBDBacklitLvl variable slightly (e.g. from 00 00 00 07 to 00 00 
00 06)
6. Reboot to reload variables
7. Save the output of 'sudo ./probe' to a new file

This will tell me whether your KBCL variable is the important one, or if
the variable has another name.

At some point I would like to handle these KBLL/KBCL variables in the
kernel, and this information from your machine can help me to write a
safe kernel module to do this.

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

Title:
  Keyboard backlight does not work in Samsung Series 9 NP900X4C

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 13.04, the keyboard backlight does not work in Samsung
  Series 9 NP900X4C.

  Adding the FN key mappings as described in
  https://help.ubuntu.com/community/SamsungSeries9 does show information
  in the notification area when pressing the keyboard backlight's + and
  - buttons, but:

  1) The notification always identifies the backlight as "full max"
  2) It has no effect on the backlight - it's always off

  When I first installed Ubuntu on this machine (12.10), even though the
  fn keys never worked I did have intermitent backlight functionality -
  the light sensor would sometimes work and I'd see light in the
  keyboard.

  I dual boot in Windows 8 and backlighting works there, so this is not
  a hardware issue.

  More discussion can be found here:
  http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-
  fn-buttons-work-in-samsung-series-9

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

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


[Desktop-packages] [Bug 1324320] [NEW] Unexpected behavior when launcher and panel opacity are set to 0

2014-05-28 Thread Davide Depau
Public bug reported:

When I set the panel and the launcher opacity to zero, the launcher, even if 
transparent, makes the wallpaper a little lighter behind it, and the panel 
makes it darker and keeps the blur.
Steps to reproduce:
1. Install and open ccsm
2. Go to Ubuntu Unity Plugin
3. Set launcher or panel opacity to 0.0

I'd expect the panel not to blur the wallpaper, to hide all the shadows
and to be completely transparent, showing only the icons and the text,
and the launcher to also be completely transparent and hide all the
shadows without making the wallpaper look lighter.

See picture for more details.

** Affects: unity
 Importance: Undecided
 Status: New

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

** Attachment added: "Screenshot from 2014-05-28 20:51:23.png"
   
https://bugs.launchpad.net/bugs/1324320/+attachment/4121781/+files/Screenshot%20from%202014-05-28%2020%3A51%3A23.png

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

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

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

Title:
  Unexpected behavior when launcher and panel opacity are set to 0

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

Bug description:
  When I set the panel and the launcher opacity to zero, the launcher, even if 
transparent, makes the wallpaper a little lighter behind it, and the panel 
makes it darker and keeps the blur.
  Steps to reproduce:
  1. Install and open ccsm
  2. Go to Ubuntu Unity Plugin
  3. Set launcher or panel opacity to 0.0

  I'd expect the panel not to blur the wallpaper, to hide all the
  shadows and to be completely transparent, showing only the icons and
  the text, and the launcher to also be completely transparent and hide
  all the shadows without making the wallpaper look lighter.

  See picture for more details.

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

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


[Desktop-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep

2014-05-28 Thread Christopher M. Penalver
sanette, could you please test the latest upstream kernel available (3.15-rc7) 
following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow 
additional upstream developers to examine the issue. Once you've tested the 
upstream kernel, please comment on which kernel version specifically you 
tested. If this bug is fixed in the mainline kernel, please add the following 
tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For 
example:
kernel-fixed-upstream-3.15-rc6

This can be done by clicking on the yellow circle with a black pencil icon next 
to the word Tags located at the bottom of the bug description. As well, please 
remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your
understanding.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Low => Medium

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

Title:
  [Dell XPS 13 (L321X)] External monitor does not wake up after sleep

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The problem started after I upgraded from kubuntu 13.10 to 14.04.
  the monitor is connected to my laptop via a VGA mini display port.
  At boot, it works correctly, but if the screen goes blank after some 
inactivity, then it stays black forever.

  WORKAROUND: If I unplug the VGA adapter, and plug it back, it works
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Fri May 23 16:02:09 2014
  DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sputnik-20120802-0
  DistroCodename: trusty
  DistroVariant: kubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed
   fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed
   vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:052e]
  InstallationDate: Installed on 2012-11-13 (555 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun 
fichier ou dossier de ce type
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun 
fichier ou dossier de ce type
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Dell Inc. Dell System XPS L321X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 085X6F
  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.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  ver

[Desktop-packages] [Bug 1324320] [NEW] Unexpected behavior when launcher and panel opacity are set to 0

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

When I set the panel and the launcher opacity to zero, the launcher, even if 
transparent, makes the wallpaper a little lighter behind it, and the panel 
makes it darker and keeps the blur.
Steps to reproduce:
1. Install and open ccsm
2. Go to Ubuntu Unity Plugin
3. Set launcher or panel opacity to 0.0

I'd expect the panel not to blur the wallpaper, to hide all the shadows
and to be completely transparent, showing only the icons and the text,
and the launcher to also be completely transparent and hide all the
shadows without making the wallpaper look lighter.

See picture for more details.

** Affects: unity
 Importance: Undecided
 Status: New

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

-- 
Unexpected behavior when launcher and panel opacity are set to 0
https://bugs.launchpad.net/bugs/1324320
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to unity in Ubuntu.

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


[Desktop-packages] [Bug 1322644] Re: [Dell XPS 13 (L321X)] External monitor does not wake up after sleep

2014-05-28 Thread Christopher M. Penalver
** Tags removed: bios-outdated-a08
** Tags added: latest-bios-a08

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

Title:
  [Dell XPS 13 (L321X)] External monitor does not wake up after sleep

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  The problem started after I upgraded from kubuntu 13.10 to 14.04.
  the monitor is connected to my laptop via a VGA mini display port.
  At boot, it works correctly, but if the screen goes blank after some 
inactivity, then it stays black forever.

  WORKAROUND: If I unplug the VGA adapter, and plug it back, it works
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Fri May 23 16:02:09 2014
  DistUpgraded: 2014-05-09 13:04:30,209 DEBUG enabling apt cron job
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sputnik-20120802-0
  DistroCodename: trusty
  DistroVariant: kubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 14.03.01, 3.11.0-20-generic, x86_64: installed
   fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.6, 3.11.0-20-generic, x86_64: installed
   vboxhost, 4.3.6, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:052e]
  InstallationDate: Installed on 2012-11-13 (555 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf 
in 'binary/casper/initrd.img' LIVE/INSTALL Binary 20120802-21:13
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun 
fichier ou dossier de ce type
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Aucun 
fichier ou dossier de ce type
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Dell Inc. Dell System XPS L321X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f18a56b7-1429-4ce3-b6e3-65edacff16a3 ro quiet splash 
crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-05-09 (14 days ago)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 085X6F
  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.:bvrA06:bd07/02/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.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: Fri May 23 06:57:33 2014
  xserver.configfile: None
  xserver.errors: Failed to load module "displaylink" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4920
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

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

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

[Desktop-packages] [Bug 1072442] Re: Adressbook entries not visible after selection "To:" email field

2014-05-28 Thread Mathew Hodson
The fix is in quantal-proposed.

** Changed in: evolution
   Importance: Medium => Unknown

** Changed in: evolution
   Status: Expired => Unknown

** Changed in: evolution
 Remote watch: GNOME Bug Tracker #660870 => GNOME Bug Tracker #688479

** Package changed: evolution (Ubuntu) => evolution-data-server (Ubuntu)

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Adressbook entries not visible after selection "To:" email field

Status in The Evolution Mail & Calendaring Tool:
  Unknown
Status in “evolution-data-server” package in Ubuntu:
  Fix Committed
Status in “evolution” package in Arch Linux:
  New

Bug description:
  Hi there,

  I've been using evolution with address book quite long. When inserting
  adresses manually into the recipient field, entries are correctly
  recommended by evolution after typing the first letters. But it's not
  possible to select one or several adresses after clicking on the "To:"
  field when composing a new mail. The main contact list, every category
  chosen is simply empty, none of my addressbook entries is shown. So
  I'm unable to add or remove contacts to or from the "To:", "CC:" or
  "BCC:" lists.

  I wonder wether this behaviour is due to evolution or evolution-data-
  server and would appreciate any help.

  Kind regards,

  Stefan

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: evolution 3.6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sun Oct 28 20:44:01 2012
  InstallationDate: Installed on 2012-08-16 (72 days ago)
  InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120815)
  MarkForUpload: True
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1324274] Re: package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to install/upgrade: ErrorMessage: cannot copy extracted data for './usr/share/libreoffice/share/config/

2014-05-28 Thread Ubuntu Foundations Team Bug Bot
** Attachment removed: "VarLogDistupgradeTermlog.gz"
   
https://bugs.launchpad.net/bugs/1324274/+attachment/4121681/+files/VarLogDistupgradeTermlog.gz

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

Title:
  package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to
  install/upgrade: ErrorMessage: cannot copy extracted data for
  './usr/share/libreoffice/share/config/images_tango.zip' to
  '/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new':
  unexpected end of file or stream

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Also, I get a message stating that ubuntu has experienced an internal
  system error. I don't know how nor why this happens, but that's all I
  can make of it.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  Date: Tue May 27 02:56:26 2014
  DuplicateSignature: 
package:libreoffice-style-tango:1:4.2.3~rc3-0ubuntu2:ErrorMessage: cannot copy 
extracted data for './usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: ErrorMessage: cannot copy extracted data for 
'./usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
  InstallationDate: Installed on 2012-05-19 (738 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  SourcePackage: libreoffice
  Title: package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to 
install/upgrade: ErrorMessage: cannot copy extracted data for 
'./usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-05-27 (1 days ago)

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

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


[Desktop-packages] [Bug 1058356] Re: fails to install when kernel does not provide block_suspend capability

2014-05-28 Thread Mathew Hodson
The upstart package in quantal-proposed was released so removing the
verification-needed tag.

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

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

Title:
  fails to install when kernel does not provide block_suspend capability

Status in “cups” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  New
Status in “upstart” source package in Quantal:
  Fix Released

Bug description:
  [IMPACT]
   * Some users upgrading from 12.04 LTS to 12.10 have encountered upgrade 
errors because
     apparmor_parser fails to load new policy on an old kernel. Specifically, 
the
     block_suspend capability is new in the 12.10 kernel and does not exist in 
the
     12.04 LTS kernel. On upgrade, the cups upstart job calls
     /lib/init/apparmor-profile-load from upstart, which in turn calls 
apparmor_parser.
     apparmor_parser can exit with error on upgrades causing the upstart job to 
fail.

  [TESTCASE]
   * Regular upgrades using do-release-upgrade or update-manager don't seem to 
be affected,
     so it is best to:
     - obtain the apparmor profile from the 12.10 cups package[1], copy it to
   /etc/apparmor.d/usr.sbin.cupsd and then perform 'sudo stop cups ; sudo 
start cups'.
   If the bug is not fixed, you will see 'start: Job failed to start'. If 
it is
   fixed, you will see 'cups start/running, process '.

  [1]http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/quantal/cups/quantal/view/head:/debian/local/apparmor-
  profile

  [Regression Potential]
   * The regression potential is extremely low. The only change is adding '|| 
exit 0' to a
     shell script.

  [Other Info]
   * This has been discussed with the security team, the release team and 
foundations and
     we all agree this is the best fix at this time.
   * On upgrades, upstart is unpacked very early (much earlier than cups), so 
the new
     /lib/init/apparmor-profile-load should be in place before the upstart job 
is used
   * apparmor_parser failure will not remove the old profile when it faces this 
error
 condition, so the program will not go unconfined

  Previous report:
  On our Jenkins builds we're getting a failure to install the cups package.  
This seems to be because the apparmor profile looks for suspend capability but 
the virtualized builders do not have it.  Here seems to be the relevant log:

  AppArmor parser error for /etc/apparmor.d/usr.sbin.cupsd in 
/etc/apparmor.d/usr.sbin.cupsd at line 24: Invalid capability block_suspend.
  start: Job failed to start
  invoke-rc.d: initscript cups, action "start" failed.
  dpkg: error processing cups (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   cups
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Full log: https://jenkins.qa.ubuntu.com/job/indicator-session-
  ci/label=quantal/16/console

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

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


[Desktop-packages] [Bug 1315265] Re: Broadcom Device BCM43142 Wireless Driver for Ubuntu 14.04 LTS 64Bit Desktop not working out of box

2014-05-28 Thread epek
My lenovo E330 shows the same error behaviour as described by Stephen A. Goss.
Since updating from 13.10 to 14.04 I sporadically receive:
"(1) Creating object for path 
'/org/freedesktop/NetworkManager/ActiveConnection/7' failed in libnm-glib" on 
connecting to a radius /EAP-TTLS-authenticated network.
Side effect: the (previously saved) password vanishes from the settings 
dialog

My wireless lan adapter is a:
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)

The error does not occur on another laptop with 14.04 and an ath9-based
pccard.

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

Title:
  Broadcom Device BCM43142 Wireless Driver for Ubuntu 14.04 LTS 64Bit
  Desktop not working out of box

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

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

  $ apt-cache policy network-manager
  network-manager:
Installed: 0.9.8.8-0ubuntu7
Candidate: 0.9.8.8-0ubuntu7
Version table:
   *** 0.9.8.8-0ubuntu7 0
  500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  After installing Ubuntu 14.04 Desktop version 64 bit on my Dell Vostro 2520 
Laptop, I expected the wirless card to automatically be detected and to be able 
to connect to any wireless network for seamless internet access. 

  However, the driver for wifi did not get automatically installed. I
  looked around for some information in the web and found a blog
  suggestion to run the following command for wifi to work:

  $sudo apt-get install linux-headers-generic build-essential dkms

  After running this command, I found the driver to show up in the right
  corner, but when I select a wifi network, I saw another error:

  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/2' failed in libnm-
  glib.

  I tried asking in the freenode ubuntu irc chatroom but did not get any
  solutions.

  After trying out several suggestions from the chat room, nothing
  worked.

  Workaround:
  Finally, through nm-applet I clicked on "Edit Connections" and selected the 
wifi network I was trying to add. Then in the security settings, I typed the 
password for accessing the wifi and configured it. 

  When I unplugged my LAN and restarted wifi, it worked. Now I am able
  to access the wifi.

  The forum member in Ubuntu chatroom suggested I file a bug:

  To summarize the issue is, there is no inbuilt driver for Broadcom
  BCM43142 Network Controller.

  Please help fix this in the next update.  Let me know if you need any
  further information.

  Thanks
  Sharath

  $ lsusb
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 0c45:6473 Microdia 
  Bus 001 Device 003: ID 0a5c:21d7 Broadcom Corp. BCM43142 Bluetooth 4.0
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ lspci 
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.3 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 4 (rev c4)
  00:1c.5 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 6 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation HM75 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
  07:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)

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

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

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

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

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

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

Title:
  matrox g200eR2 is unclaimed in 14.04

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

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

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

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

  Thus xserver is not hardver accelerated.

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

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

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

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


[Desktop-packages] [Bug 763005] Re: fglrx driver + compiz's "Sync to Vblank" makes display stutter/slow

2014-05-28 Thread Mathew Hodson
Removing verification-needed tag for compiz in oneiric-proposed, because
it is no longer targeted.

** Tags removed: verification-needed

** Tags added: precise

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

Title:
  fglrx driver + compiz's "Sync to Vblank" makes display stutter/slow

Status in Compiz Core:
  Fix Released
Status in Ubutter: Making Ubuntu buttery smooth:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “fglrx-installer” package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  The user's display only redraws at 20-30Hz (1/3-1/2 of the correct monitor 
refresh rate). Making a highly unpleasant graphics experience.

  [Development Fix]
  Simplified the way the compiz opengl plugin does vsync, using fewer functions 
and simpler code. This works around the slow functions in the fglrx driver 
which are the root cause.

  [Stable Fix]
  As above.

  [Test Case]
  Make sure "Sync To VBlank" is enabled in the OpenGL section of CompizConfig 
Settings Manager. In Ubuntu 11.04 it is enabled by default.

  Drag some windows around. Also open and close windows. The animations
  will not be smooth as they appear to stutter. The framerate is only
  around 20-30Hz.

  Now turn "Sync To VBlank" off and repeat the above steps again. If you
  notice the animations are much smoother than with "Sync To VBlank" on
  then you are suffering from this bug.

  [Regression Potential]
  Low.
  Worst case: Video tearing occurs. However this is unlikely given the fix has 
been in everyday use by many users of ppa:vanvugt/compiz for many months 
already.

  [Original Report]
  This bug is primarily for users of the fglrx driver, but the proposed fix 
does improve performance with other drivers. Most NVIDIA users should look at 
bug 92599 instead.

  Package: fglrx
  Version: 2:8.840-0ubuntu2

  01:00.0 VGA compatible controller: ATI Technologies Inc Juniper
  [Radeon HD 5700 Series]

  I have ATI's 5770 with fglrx. Having "Sync to Vblank" on makes Unity
  and many Compiz features (Enhanced Zoom, Scale etc.) really slow.
  Turning "Sync to Vblank" off has a huge effect on desktop,
  responsiveness is much, much better. Turning "tearing" off/on from
  amdccle doesn't seem to have any effect on responsiveness.

  In Maverick "Sync to Vblank" was off by default, in Natty it's on.
  This will probably have a huge impact on many fglrx users.

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

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


[Desktop-packages] [Bug 1320763] Re: Have support for Gtk-Headerbar in Trusty (14.04)

2014-05-28 Thread Treviño
** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  Have support for Gtk-Headerbar in Trusty (14.04)

Status in Themes for Ubuntu:
  New
Status in Unity:
  New
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty, Unity window decorator & compiz doesn't have proper support
  for gtk-headerbar. As a result applications using gtk-headerbar look
  ugly & awkward.

  1. There is no re-size grip, they are inaccessible for mouse-resizing.

  2. It appears shadow-less & border-less.

  3.  In gnome-tweak-tool, when toggling among tabs, the middle section
  gets transparent! (Screenshot attached).

  It seems applications are drawn without any decoration properly
  applied on them.It also occurs with themes which do have headerbar
  support. Other desktop-shells based on compiz are affected as
  well...for example, compiz session for Gnome-Flashback.

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

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


[Desktop-packages] [Bug 407344] Re: pdf printing on karmic fails: pdftopdf crashed on signal 11

2014-05-28 Thread Mathew Hodson
The package in karmic-proposed was released so removing verification-
needed tag.

** Tags removed: verification-needed

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

Title:
  pdf printing on karmic fails: pdftopdf crashed on signal 11

Status in “cups” package in Ubuntu:
  Fix Released
Status in “lcms” package in Ubuntu:
  New
Status in “cups” source package in Karmic:
  Fix Released
Status in “lcms” source package in Karmic:
  Invalid

Bug description:
  Binary package hint: cups

  In Karmic (9.10), printing a large pdf file (or, one of its pages
  containing a large image) using Acroread (8.1.2) fails (document not
  being printed).

  When printing fails , the job is reported as "pending" and fails upon
  retry a few minutes later.

  Extra info:
  Karmic with cups_1.3.11-1_i386 
  In cups/error_log: 
  PID 324 (/usr/lib/cups/filter/pdftopdf) crashed on signal 11!
  [job 424] Empty print file!

  Printing a page containing only text does work, printing the large
  page using Evince works as well.

  Downgraded cups to 1.3.9-17, dependency libpoppler4_0.10.5-1ubuntu2.2
  and the same file is printed correctly using Acroread and Evince

  Thanks, Robert

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

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


[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver

2014-05-28 Thread Mathew Hodson
The gdm oackages in raring and precise-proposed have been released so
removing the verification-needed tag.

** Tags removed: verification-needed

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

Title:
  X trying to start before plymouth has finished using the drm driver

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project precise series:
  Fix Released
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “kde-workspace” package in Ubuntu:
  New
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “plymouth” package in Ubuntu:
  Fix Released
Status in “xorg-server-lts-quantal” package in Ubuntu:
  Invalid
Status in “gdm” source package in Precise:
  Fix Released
Status in “kde-workspace” source package in Precise:
  New
Status in “lightdm” source package in Precise:
  Fix Released
Status in “plymouth” source package in Precise:
  Fix Released
Status in “xorg-server-lts-quantal” source package in Precise:
  Triaged
Status in “gdm” source package in Raring:
  Fix Released
Status in “kde-workspace” source package in Raring:
  New
Status in “lightdm” source package in Raring:
  Fix Released
Status in “plymouth” source package in Raring:
  Fix Released
Status in “xorg-server-lts-quantal” source package in Raring:
  Invalid
Status in “gdm” source package in Saucy:
  Fix Released
Status in “kde-workspace” source package in Saucy:
  New
Status in “lightdm” source package in Saucy:
  Fix Released
Status in “plymouth” source package in Saucy:
  Fix Released
Status in “xorg-server-lts-quantal” source package in Saucy:
  Invalid

Bug description:
  X server fails to start the first time after boot, it works fine when
  I start it again.

  Looks like a race condition with intel drm initialization, i guess X
  tries to start faster than drm driver is initialized so it fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Apr 16 10:35:28 2012
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:7750]
   Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] 
[1002:6738] (prog-if 00 [VGA controller])
 Subsystem: Giga-byte Technology Device [1458:21fa]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
  MachineType: MSI MS-7750
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic 
root=/dev/mapper/ssd-ubuntu--precise ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V4.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z68A-G43 (G3) (MS-7750)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7750
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.7.6-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.32-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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

[Desktop-packages] [Bug 1324302] [NEW] Xorg - Touch Pad/Screen loses events

2014-05-28 Thread Evan Langlois
Public bug reported:

HP Pavilion Touch-screen Laptop...

Technically, Xorg isn't completely freezing.  It will just suddenly
start losing mouse events.  I normally use the Synaptics touchpad and it
seems these have a history of problems.   Once I start losing events, I
usually can't click on anything, or I'll move the mouse and get the
response a few events later.   This has a touch-screen too, and it will
have the same problem.  It's unclear if the events are being lost or
delayed or what.   However, the system becomes unusable and I end up
switching to a text console and killing Xorg (and losing everything I
was doing).   Xorg restarts and then it will  work fine for hours.

It would seem that moving windows around in the Workspace Switcher while
its showing the reduced-size views will trigger this bug the fastest.
I usually see some Firmware errors when I switch consoles ...

[10343.203992] [Firmware Bug]: cpu 0, try to use APIC500 (LVT offset 0) for 
vector 0xf9, but the register is already in use for vector 0x400 on another cpu
[10343.203994] [Firmware Bug]: cpu 0, failed to setup threshold interrupt for 
bank 4, block 1 (MSRC408=0xc100)

Dmesg also says ...
[0.233872] [Firmware Info]: CPU: Re-enabling disabled Topology Extensions 
Support
[0.268901] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[1.050054] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-3f] only partially covers this bridge

However, its possible that none of this is related.   I checked the
Changelog for the latest kernel, and the synaptics driver has a few bug
fixes (as does my wireless driver).  However, I don't know what patches
ubuntu puts onto the stock kernel, so I'll wait for further instructions
before trying the 3.14 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May 28 18:01:58 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:216b]
InstallationDate: Installed on 2014-05-25 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=a4738195-0b98-431e-a06a-afb674123cb2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 216B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 30.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/21/2013:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr0974110002405E0620180:rvnHewlett-Packard:rn216B:rvr30.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion TS 15 Notebook PC
dmi.product.version: 0974110002405E0620180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.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 May 28 13:20:31 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 false-gpu-hang freeze 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

[Desktop-packages] [Bug 1324298] [NEW] Incorrect (perhaps outdated) number of windows displayed next to launcher icons

2014-05-28 Thread Teo
Public bug reported:

The number of white arrows on the left of Launcher icons, which is supposed to 
indicate the number of open windows of a given application, often is incorrect; 
I think it is because it doesn't always get updated when the number of windows 
changes (e.g. a window of the same application is open or closed).
Switching to another application and then back to the affected one fixes the 
issue.

For example, i have observed only one arrow next to the Terminal icon on 
Launcher, when I did have two terminal windows open.
AND viceversa, on another occasion, there were two arrows next to Google 
Chrome's Launcher icon when I there was only one open Google Chrome window (I 
had closed the second window several minutes earlier).

I'm almost sure this is a regression in Ubuntu 14.04, because I had
never observed it before the upgrade, and now, after upgrading, I have
already observed it twice in just a couple of days. Unless that's just
an unlikely coincidence.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Thu May 29 01:01:20 2014
InstallationDate: Installed on 2013-10-11 (229 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-24 (4 days ago)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Incorrect (perhaps outdated) number of windows displayed next to
  launcher icons

Status in “unity” package in Ubuntu:
  New

Bug description:
  The number of white arrows on the left of Launcher icons, which is supposed 
to indicate the number of open windows of a given application, often is 
incorrect; I think it is because it doesn't always get updated when the number 
of windows changes (e.g. a window of the same application is open or closed).
  Switching to another application and then back to the affected one fixes the 
issue.

  For example, i have observed only one arrow next to the Terminal icon on 
Launcher, when I did have two terminal windows open.
  AND viceversa, on another occasion, there were two arrows next to Google 
Chrome's Launcher icon when I there was only one open Google Chrome window (I 
had closed the second window several minutes earlier).

  I'm almost sure this is a regression in Ubuntu 14.04, because I had
  never observed it before the upgrade, and now, after upgrading, I have
  already observed it twice in just a couple of days. Unless that's just
  an unlikely coincidence.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu May 29 01:01:20 2014
  InstallationDate: Installed on 2013-10-11 (229 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (4 days ago)

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

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


[Desktop-packages] [Bug 1133794] Re: Printer not detected by system-config-printer 1.3.11 in Lubuntu 13.04

2014-05-28 Thread Mathew Hodson
It seems http://launchpad.net/ubuntu/+source/cups/1.6.2-1ubuntu7 was
deleted from raring-proposed, so removing verification-needed tag.

** Tags removed: verification-needed

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

Title:
  Printer not detected by system-config-printer 1.3.11 in  Lubuntu 13.04

Status in “cups” package in Ubuntu:
  Fix Released
Status in “lubuntu-meta” package in Ubuntu:
  In Progress
Status in “system-config-printer” package in Ubuntu:
  Invalid
Status in “cups” source package in Raring:
  Fix Committed
Status in “lubuntu-meta” source package in Raring:
  Invalid
Status in “system-config-printer” source package in Raring:
  Invalid

Bug description:
  1) Raring daily Lubuntu 13.04 i386
  2) system-config-printer 1.3.11
  3) I expected the printer to be detected without a cups error. The printer 
was not detected.
  4)
  1) When selecting Printer from the System Tools menu the Printers-localhost 
dialog box appears with the following message.
  'Printing service not available. Start the service on this computer or 
connect to another server.'
  2) After clicking the connect button once the 'Connect to CUPS server' box 
appears.
  3) After clicking the connect button on this message box  the Cups server 
error box appears with the following dialog.
  There was an error during the CUPS operation: 'failed to connect to server'.

  [IMPACT]

  As the standard installation of Lubuntu does not include avahi-daemon
  CUPS does not get started as the Upstart script for CUPS requires
  avahi-daemon to be started first. Therefore there is no printing
  functionality for Lubuntu users even with the printing stack being
  installed by default.

  [TESTCASE]

  Do a standard installation of Lubuntu and run

  lpstat -r

  in a terminal. The CUPS daemon is not running.

  The proposed package adds a dependency to the cups-daemon binary
  package pulling in avahi-daemon and so CUPS will start during boot.
  Check with

  lpstat -r

  in a terminal window.

  [Regression Potential]

  Low. An additional package gets installed, but this package is already
  well-known and work well in other Ubuntu flavors.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: system-config-printer-gnome 1.3.11+20120807-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  CasperVersion: 1.330
  CurrentDmesg:

  Date: Wed Feb 27 01:04:06 2013
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InterpreterPath: /usr/bin/python2.7
  LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130226)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Transport endpoint is not connected
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  PackageArchitecture: all
  Papersize: a4
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: initrd=/ubninit file=/cdrom/preseed/username.seed 
boot=casper quiet splash -- persistent BOOT_IMAGE=/ubnkern
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2005
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1024.001
  dmi.board.name: P4C800-E
  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.:bvr1024.001:bd08/04/2005:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASUSTeKComputerInc.:rnP4C800-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Desktop-packages] [Bug 1307877] Re: Laptop Monitor Brightness reduced to minimum and disabled after disconnection from external monitor.

2014-05-28 Thread Sérgio Serra
I have the same problem with ubuntu 14.04. Any workaround?

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

Title:
  Laptop Monitor Brightness reduced to minimum and disabled after
  disconnection from external monitor.

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have the following problem under Ubuntu 14.04. As soon as I
  disconnect my external monitor from my Laptop (Lenovo X1 Carbon), the
  brigthness is reduced to minimum (backlight switches off) and I can
  not increase it again. When I use the brightness control keys the
  brightness bar shows that it is set to maximum even though it clearly
  is not. Using the control keys still changes the brightness bar but
  does nothing to the brightness itself.

  Upon a restart of the laptop the brightness returns to its maximum and
  is controllable again.

  I encountered this problem under the Unity version shipped with Ubuntu
  14.04, but it might happen with other desktop managers as well.

  This problem did not exist when my Laptop was running under Ubuntu
  13.10.

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

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


[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

2014-05-28 Thread silver_slice
Artur, I have the same bug with this ppa - in JetBrains phpStorm hotkeys
now work only in non-latin keyboard layout. I installed ppa on clean
Ubuntu 14.04.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in Aptana Studio Installer:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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


[Desktop-packages] [Bug 112955] Re: vino (vnc) keyboard mapping problem

2014-05-28 Thread Mathew Hodson
The verification-needed tag is added by the SRU team when the upload is
approved in the -proposed pocket.

** Tags removed: verification-needed

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

** No longer affects: tightvnc (Ubuntu Feisty)

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

Title:
  vino (vnc) keyboard mapping problem

Status in TightVNC: VNC-Based Free Remote Control Solution:
  Unknown
Status in GNOME Remote Desktop:
  Fix Released
Status in “tightvnc” package in Ubuntu:
  New
Status in “vino” package in Ubuntu:
  Fix Released
Status in “vnc4” package in Ubuntu:
  Confirmed
Status in “vino” source package in Feisty:
  Won't Fix
Status in “vnc4” source package in Feisty:
  Invalid

Bug description:
  Binary package hint: vino

  I'm pretty sure this started after an upgrade from Edgy to Feisty.

  VNC / Vino no longer works correctly.  The main alphanumeric keys map
  from the client to the server OK (so if I press A on the client
  keyboard A appears on the VNC screen in whatever application I'm
  working in), but others do not.  For example:

  | (pipe) is interpreted by vino as ` (backquote)
  < and > are interpreted as z and x

  Other people seem to have a similar problem - see
  http://ubuntuforums.org/showthread.php?t=382441

  I can't find any obvious configuration files to tweak.  Both client
  and server machines have UK keyboards (and Ubuntu is configured with
  UK keyboard layout).  The client machine is Win98 running realvnc
  3.3.6 but I've just tried 4.1.2 and that doesn't fix it.

  Thanks in advance for your help.

  James.

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

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


[Desktop-packages] [Bug 1323843] Re: Sync gnome-icon-theme-symbolic 3.12.0-1 (main) from Debian unstable (main)

2014-05-28 Thread Jackson Doak
I'm willing to try and merge the main icon theme, but it says "don't
merge" in the MoM. Is there a reason for that

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

Title:
  Sync gnome-icon-theme-symbolic 3.12.0-1 (main) from Debian unstable
  (main)

Status in “gnome-icon-theme-symbolic” package in Ubuntu:
  Fix Released

Bug description:
  Please sync gnome-icon-theme-symbolic 3.12.0-1 (main) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/patches/git_directory_symbolic.patch: symlink directory
  symbolic icon, thanks Lars Uebernickel (lp: #1289872)
  Fixed upstream

  Changelog entries since current utopic version 3.10.1-1ubuntu1:

  gnome-icon-theme-symbolic (3.12.0-1) unstable; urgency=medium

[ Jackson Doak ]
* New upstream release
* debian/control: Bump standards-version to 3.9.5 (no changes)

   -- Andreas Henriksson   Tue, 25 Mar 2014 10:20:52
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme-symbolic/+bug/1323843/+subscriptions

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


[Desktop-packages] [Bug 1305327] Re: Always in visible workspace does not work

2014-05-28 Thread berend
A recent update fixed this indeed, apologies for not closing this.

** Changed in: compiz
   Status: Incomplete => Fix Released

** Changed in: compiz (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Always in visible workspace does not work

Status in Compiz:
  Fix Released
Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  I can enable this option, but doesn't do anything, stays in single
  workspace.

  If you go to compiz, general options, and look at desktop size, it
  doesn't show data for vertical virtual size and number of desktops.
  Can set them with the unity tweak tool, but does not show up in
  compiz. Setting these options in compiz won't make them stick.

  So possibly related: i.e. workspaces don't work, therefore this option
  doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  337.12  Fri Apr  4 14:51:15 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 10 08:50:44 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-19-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-22-generic, x86_64: installed
   bbswitch, 0.7, 3.13.0-23-generic, x86_64: installed
   nvidia-337, 337.12, 3.13.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:2119]
  InstallationDate: Installed on 2014-04-01 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: LENOVO 2757CTO
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-23-generic 
root=UUID=52ddc899-ca26-4fe9-b2ba-e7562258b42c ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7ZET71WW (1.54 )
  dmi.board.name: 2757CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7ZET71WW(1.54):bd11/27/2008:svnLENOVO:pn2757CTO:pvrThinkPadW700:rvnLENOVO:rn2757CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2757CTO
  dmi.product.version: ThinkPad W700
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140408-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.2.0~git20140331.ec4b8d16-0ubuntu0ricotz
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.2.0~git20140331.ec4b8d16-0ubuntu0ricotz
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.3.99+git20140317.bdc41204-0ubuntu0sarvatt
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.911+git20140331.5c0623b5-0ubuntu0ricotz
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt
  xserver.bootTime: Thu Apr 10 08:49:38 2014
  xserver.configfile: default
  xserver.errors:
   open /dev/fb0: No such file or directory
   Tablet ISD-V4 stylus: Invalid type 'cursor' for this device.
   Tablet ISD-V4 stylus: Invalid type 'touch' for this device.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 112955] Re: vino (vnc) keyboard mapping problem

2014-05-28 Thread Mathew Hodson
** Package changed: tightvnc (Baltix) => tightvnc

** Changed in: tightvnc
   Importance: Undecided => Unknown

** Changed in: tightvnc
   Status: Confirmed => Unknown

** Changed in: tightvnc
 Remote watch: None => SourceForge.net Tracker #2232405

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

Title:
  vino (vnc) keyboard mapping problem

Status in TightVNC: VNC-Based Free Remote Control Solution:
  Unknown
Status in GNOME Remote Desktop:
  Fix Released
Status in “vino” package in Ubuntu:
  Fix Released
Status in “vnc4” package in Ubuntu:
  Confirmed
Status in “vino” source package in Feisty:
  Won't Fix
Status in “vnc4” source package in Feisty:
  Invalid

Bug description:
  Binary package hint: vino

  I'm pretty sure this started after an upgrade from Edgy to Feisty.

  VNC / Vino no longer works correctly.  The main alphanumeric keys map
  from the client to the server OK (so if I press A on the client
  keyboard A appears on the VNC screen in whatever application I'm
  working in), but others do not.  For example:

  | (pipe) is interpreted by vino as ` (backquote)
  < and > are interpreted as z and x

  Other people seem to have a similar problem - see
  http://ubuntuforums.org/showthread.php?t=382441

  I can't find any obvious configuration files to tweak.  Both client
  and server machines have UK keyboards (and Ubuntu is configured with
  UK keyboard layout).  The client machine is Win98 running realvnc
  3.3.6 but I've just tried 4.1.2 and that doesn't fix it.

  Thanks in advance for your help.

  James.

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

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


[Desktop-packages] [Bug 1324274] [NEW] package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to install/upgrade: ErrorMessage: cannot copy extracted data for './usr/share/libreoffice/share/confi

2014-05-28 Thread Benito Abreu
Public bug reported:

Also, I get a message stating that ubuntu has experienced an internal
system error. I don't know how nor why this happens, but that's all I
can make of it.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
Date: Tue May 27 02:56:26 2014
DuplicateSignature: 
package:libreoffice-style-tango:1:4.2.3~rc3-0ubuntu2:ErrorMessage: cannot copy 
extracted data for './usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
ErrorMessage: ErrorMessage: cannot copy extracted data for 
'./usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
InstallationDate: Installed on 2012-05-19 (738 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
PackageArchitecture: all
SourcePackage: libreoffice
Title: package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to 
install/upgrade: ErrorMessage: cannot copy extracted data for 
'./usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
UpgradeStatus: Upgraded to trusty on 2014-05-27 (1 days ago)

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


** Tags: apport-package i386 need-duplicate-check third-party-packages trusty

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

Title:
  package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to
  install/upgrade: ErrorMessage: cannot copy extracted data for
  './usr/share/libreoffice/share/config/images_tango.zip' to
  '/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new':
  unexpected end of file or stream

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  Also, I get a message stating that ubuntu has experienced an internal
  system error. I don't know how nor why this happens, but that's all I
  can make of it.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  Date: Tue May 27 02:56:26 2014
  DuplicateSignature: 
package:libreoffice-style-tango:1:4.2.3~rc3-0ubuntu2:ErrorMessage: cannot copy 
extracted data for './usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
  ErrorMessage: ErrorMessage: cannot copy extracted data for 
'./usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
  InstallationDate: Installed on 2012-05-19 (738 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  SourcePackage: libreoffice
  Title: package libreoffice-style-tango 1:4.2.3~rc3-0ubuntu2 failed to 
install/upgrade: ErrorMessage: cannot copy extracted data for 
'./usr/share/libreoffice/share/config/images_tango.zip' to 
'/usr/share/libreoffice/share/config/images_tango.zip.dpkg-new': unexpected end 
of file or stream
  UpgradeStatus: Upgraded to trusty on 2014-05-27 (1 days ago)

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

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


[Desktop-packages] [Bug 1323843] Re: Sync gnome-icon-theme-symbolic 3.12.0-1 (main) from Debian unstable (main)

2014-05-28 Thread Martin Pitt
Meh, this introduced uninstallability as gnome-icon-theme is still at
3.10. So that needs to be merged to get 3.12.x.

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

Title:
  Sync gnome-icon-theme-symbolic 3.12.0-1 (main) from Debian unstable
  (main)

Status in “gnome-icon-theme-symbolic” package in Ubuntu:
  Fix Released

Bug description:
  Please sync gnome-icon-theme-symbolic 3.12.0-1 (main) from Debian
  unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/patches/git_directory_symbolic.patch: symlink directory
  symbolic icon, thanks Lars Uebernickel (lp: #1289872)
  Fixed upstream

  Changelog entries since current utopic version 3.10.1-1ubuntu1:

  gnome-icon-theme-symbolic (3.12.0-1) unstable; urgency=medium

[ Jackson Doak ]
* New upstream release
* debian/control: Bump standards-version to 3.9.5 (no changes)

   -- Andreas Henriksson   Tue, 25 Mar 2014 10:20:52
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme-symbolic/+bug/1323843/+subscriptions

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


[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C

2014-05-28 Thread Simon N.
** Attachment added: "ls -la /sys/firmware/efi/efivars/ > list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+attachment/4121664/+files/list.txt

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

Title:
  Keyboard backlight does not work in Samsung Series 9 NP900X4C

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 13.04, the keyboard backlight does not work in Samsung
  Series 9 NP900X4C.

  Adding the FN key mappings as described in
  https://help.ubuntu.com/community/SamsungSeries9 does show information
  in the notification area when pressing the keyboard backlight's + and
  - buttons, but:

  1) The notification always identifies the backlight as "full max"
  2) It has no effect on the backlight - it's always off

  When I first installed Ubuntu on this machine (12.10), even though the
  fn keys never worked I did have intermitent backlight functionality -
  the light sensor would sometimes work and I'd see light in the
  keyboard.

  I dual boot in Windows 8 and backlighting works there, so this is not
  a hardware issue.

  More discussion can be found here:
  http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-
  fn-buttons-work-in-samsung-series-9

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

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


[Desktop-packages] [Bug 1203592] Re: Keyboard backlight does not work in Samsung Series 9 NP900X4C

2014-05-28 Thread Simon N.
** Attachment added: "sudo cat /sys/firmware/acpi/tables/DSDT > DSDT.aml"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1203592/+attachment/4121663/+files/DSDT.aml

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

Title:
  Keyboard backlight does not work in Samsung Series 9 NP900X4C

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 13.04, the keyboard backlight does not work in Samsung
  Series 9 NP900X4C.

  Adding the FN key mappings as described in
  https://help.ubuntu.com/community/SamsungSeries9 does show information
  in the notification area when pressing the keyboard backlight's + and
  - buttons, but:

  1) The notification always identifies the backlight as "full max"
  2) It has no effect on the backlight - it's always off

  When I first installed Ubuntu on this machine (12.10), even though the
  fn keys never worked I did have intermitent backlight functionality -
  the light sensor would sometimes work and I'd see light in the
  keyboard.

  I dual boot in Windows 8 and backlighting works there, so this is not
  a hardware issue.

  More discussion can be found here:
  http://askubuntu.com/questions/233312/how-to-make-keyboard-backlight-
  fn-buttons-work-in-samsung-series-9

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

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


[Desktop-packages] [Bug 1281250] Re: VNC accessible from non-linux machines only with encryption disabled

2014-05-28 Thread Wes Garner
FYI Solution for Android users - use bVNC Free
It accepts this encryption type

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

Title:
  VNC accessible from non-linux machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

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

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


[Desktop-packages] [Bug 1324249] [NEW] Hidden startup applications are not started on login

2014-05-28 Thread Tais Plougmann Hansen
Public bug reported:

Startup applications in ~/.config/autostart with Hidden=true are not
autostarted on login. If Hidden is changed to false, the applications
start as expected on login.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed May 28 22:26:29 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-14 (1351 days ago)
InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.2)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-05-21 (7 days ago)

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


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

** Summary changed:

- Hidden startup applications is not started on login
+ Hidden startup applications are not started on login

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

Title:
  Hidden startup applications are not started on login

Status in “unity” package in Ubuntu:
  New

Bug description:
  Startup applications in ~/.config/autostart with Hidden=true are not
  autostarted on login. If Hidden is changed to false, the applications
  start as expected on login.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed May 28 22:26:29 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-09-14 (1351 days ago)
  InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-21 (7 days ago)

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

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


[Desktop-packages] [Bug 1203899] Re: NPAPI Flash plugin freezes chrome, firefox

2014-05-28 Thread Mathew Hodson
The verification-needed tag is added by the SRU team when the upload is
approved in the -proposed pocket.

** Tags removed: verification-needed

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

Title:
  NPAPI Flash plugin freezes chrome, firefox

Status in “flashplugin-nonfree” package in Ubuntu:
  Confirmed

Bug description:
  If i disable  PPAPI Flash Plugin in chrome, then try to run a flash
  object (YouTube video, flash game, etc...) chrome will hang causing me
  to force restart. this seems to only happen with the NPAPI plugin
  (11.2 r202 of libflashplayer.so)

  firefox SEEMS  to start working AFTER I installed chrome, as it
  provided it's own version of flash.  (PPAPI plugin) (I cannot create
  the firefox crashes after i installed chrome. maybe it delegates flash
  to other programs?)

  OS:
  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  FireFox: firefox23.0~b4+buil amd64 
  Chrome: 28.0.1500.71 (Official Build 209842)

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

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


[Desktop-packages] [Bug 987331] Re: gedit lacks icons

2014-05-28 Thread Lanoxx
Confirmed in Ubuntu 14.04, is there any known workaround?

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

Title:
  gedit lacks icons

Status in “gnome-icon-theme” package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Xubuntu 12.04 Beta, and now, gedit lacks some icons:

  - Do "Ctrl+f". A popup dialog appears to make a search. "Previous" and
  "Next" arrows are missing.

  - Enable the "External Tools" plugin and go to "Tools > Manage
  External Tools...". "Add" and "Delete" arrows are missing.

  See attached screenshots.

  My theme is the default Gnome theme.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 23 10:15:14 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to precise on 2012-04-09 (13 days ago)

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

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


[Desktop-packages] [Bug 987331] Re: gedit lacks icons

2014-05-28 Thread Lanoxx
Sorry, my mistake. Actually it works on 14.04, but its broken on 13.10.

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

Title:
  gedit lacks icons

Status in “gnome-icon-theme” package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Xubuntu 12.04 Beta, and now, gedit lacks some icons:

  - Do "Ctrl+f". A popup dialog appears to make a search. "Previous" and
  "Next" arrows are missing.

  - Enable the "External Tools" plugin and go to "Tools > Manage
  External Tools...". "Add" and "Delete" arrows are missing.

  See attached screenshots.

  My theme is the default Gnome theme.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Mon Apr 23 10:15:14 2012
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to precise on 2012-04-09 (13 days ago)

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

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


[Desktop-packages] [Bug 1318616] Re: lts-trusty enablement in precise

2014-05-28 Thread Mathew Hodson
These three packages are in the proposed pocket.

** Changed in: x11proto-xext (Ubuntu)
   Status: New => Fix Committed

** Changed in: x11proto-gl (Ubuntu)
   Status: New => Fix Committed

** Changed in: llvm-toolchain-3.4 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  lts-trusty enablement in precise

Status in “libdrm” package in Ubuntu:
  Invalid
Status in “llvm-toolchain-3.4” package in Ubuntu:
  Fix Committed
Status in “x11proto-gl” package in Ubuntu:
  Fix Committed
Status in “x11proto-xext” package in Ubuntu:
  Fix Committed
Status in “xorg-lts-transitional” package in Ubuntu:
  Invalid
Status in “libdrm” source package in Precise:
  Fix Committed
Status in “libdrm” source package in Saucy:
  Fix Committed
Status in “xorg-lts-transitional” source package in Trusty:
  New

Bug description:
  Some packages need to be updated for precise.

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

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


[Desktop-packages] [Bug 576160] Re: [SigmaTel STAC9228] Recording problem

2014-05-28 Thread Mathew Hodson
The linux package in lucid-proposed was released, so removing tag.

** Tags removed: verification-needed

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

Title:
  [SigmaTel STAC9228] Recording problem

Status in “alsa-driver” package in Ubuntu:
  Fix Committed
Status in “linux” package in Ubuntu:
  Invalid
Status in “alsa-driver” source package in Lucid:
  Confirmed
Status in “linux” source package in Lucid:
  Fix Released

Bug description:
  none of my mics are working.  Cant use audacity or skype.  Made sure
  all inputs were on.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion:
   Advanced Linux Sound Architecture Driver Version 1.0.22.1.
   Compiled on Apr 29 2010 for kernel 2.6.32-22-generic (SMP).
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  me 2184 F pulseaudio
   /dev/snd/pcmC0D0c:   me 2184 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf7ffc000 irq 32'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:83847616,102801f7,00100201'
 Controls  : 32
 Simple ctrls  : 22
  Date: Wed May  5 20:56:53 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 
(20100419.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [SigmaTel STAC9228] Recording problem
  dmi.bios.date: 12/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0Y012C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/16/2008:svnDellInc.:pnMXG071:pvr:rvnDellInc.:rn0Y012C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MXG071
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 586347] Re: 0x104d9069 needs LPIB quirk

2014-05-28 Thread Mathew Hodson
** Tags added: lucid

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

Title:
  0x104d9069 needs LPIB quirk

Status in “alsa-driver” package in Ubuntu:
  Fix Committed
Status in “linux” package in Ubuntu:
  Invalid
Status in “alsa-driver” source package in Lucid:
  New
Status in “linux” source package in Lucid:
  Fix Released

Bug description:
  Listening to music (in this case via rhythmbox) results in stuttering
  sound. This happens once in a while (every 1min or so) on low load and
  increases when there is a lot of disk activity.

  Using the driver version 2.6.32-22.201005210601 from audio-dev-ppa.
  Problem does not appear with the official lucid drivers in linux-
  backports-modules-alsa-lucid-generic (2.6.32.22.23). I'm using the dev
  version for nvidia hdmi-support.

  my alsa-info.sh output: http://www.alsa-
  project.org/db/?f=b8502df177229c979aa475c0aaad0a02c2825b23

  dmesg get's filled with these (not in accordance with stuttering):

  [ 1761.476830] ALSA hda_intel.c:1666: azx_pcm_prepare: bufsize=0x1, 
format=0x4011
  [ 1761.476844] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x2, 
stream=0x5, channel=0, format=0x4011
  [ 1761.493735] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x3, 
stream=0x5, channel=0, format=0x4011
  [ 1761.513715] ALSA hda_intel.c:1666: azx_pcm_prepare: bufsize=0x1, 
format=0x4011
  [ 1761.513726] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x2, 
stream=0x5, channel=0, format=0x4011
  [ 1761.533673] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x3, 
stream=0x5, channel=0, format=0x4011

  Happy to debug further!

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

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


[Desktop-packages] [Bug 586347] Re: 0x104d9069 needs LPIB quirk

2014-05-28 Thread Mathew Hodson
The linux package in lucid-proposed was released, so removing tag.

** Tags removed: verification-needed

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

Title:
  0x104d9069 needs LPIB quirk

Status in “alsa-driver” package in Ubuntu:
  Fix Committed
Status in “linux” package in Ubuntu:
  Invalid
Status in “alsa-driver” source package in Lucid:
  New
Status in “linux” source package in Lucid:
  Fix Released

Bug description:
  Listening to music (in this case via rhythmbox) results in stuttering
  sound. This happens once in a while (every 1min or so) on low load and
  increases when there is a lot of disk activity.

  Using the driver version 2.6.32-22.201005210601 from audio-dev-ppa.
  Problem does not appear with the official lucid drivers in linux-
  backports-modules-alsa-lucid-generic (2.6.32.22.23). I'm using the dev
  version for nvidia hdmi-support.

  my alsa-info.sh output: http://www.alsa-
  project.org/db/?f=b8502df177229c979aa475c0aaad0a02c2825b23

  dmesg get's filled with these (not in accordance with stuttering):

  [ 1761.476830] ALSA hda_intel.c:1666: azx_pcm_prepare: bufsize=0x1, 
format=0x4011
  [ 1761.476844] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x2, 
stream=0x5, channel=0, format=0x4011
  [ 1761.493735] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x3, 
stream=0x5, channel=0, format=0x4011
  [ 1761.513715] ALSA hda_intel.c:1666: azx_pcm_prepare: bufsize=0x1, 
format=0x4011
  [ 1761.513726] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x2, 
stream=0x5, channel=0, format=0x4011
  [ 1761.533673] ALSA hda_codec.c:1158: hda_codec_setup_stream: NID=0x3, 
stream=0x5, channel=0, format=0x4011

  Happy to debug further!

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

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


[Desktop-packages] [Bug 1281250] Re: VNC accessible from non-linux machines only with encryption disabled

2014-05-28 Thread Kurt M. Sanger
Today we tried the command gsettings set org.gnome.Vino disable-xdamage
true, which also did not work.  Then we wiped the hard drive and loaded
Ubuntu 12.04 LTS.  We could not remote into 12.04 LTS from 12.04 LTS
using either Remmina Remote Desktop nor Gtk VNC Viewer until we first
logged into the remote machine using 2D mode.  Then the remote session
updated the screen and enabled us to see our controlling of the remote
PC.

Interestingly we then logged off and logged back into the remote PC in
3D mode and the remote connection still worked.  Finally we rebooted the
remote PC, logged in under 3D mode, and the remote connection still
works.  I have no idea what is different but logging in one time under
2D mode set something up correctly.  Wish I had tried that on 14.04,
however I'm not going back soon.  Hopefully this will help you guys
figure this out.

Currently the command gsettings get org.gnome.Vino disable-xdamage
returns false on the remote PC.

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

Title:
  VNC accessible from non-linux machines only with encryption disabled

Status in GNOME Remote Desktop:
  Confirmed
Status in “vino” package in Ubuntu:
  Triaged
Status in “vino” source package in Trusty:
  Triaged
Status in “vino” package in Fedora:
  Unknown

Bug description:
  Since a recent update, it is impossible to connect to my Ubuntu box
  using VNC from a Windows machine unless I disable encryption on the
  vino server.

  I tested up-to-date tightVNC client and TigerVNC client on the Windows
  machine, with the same result. As soon I try to connect, I receive the
  following error:

  [ 5872/ 6448] 2014-01-20 12:11:18:247   List of security type is read
  [ 5872/ 6448] 2014-01-20 12:11:18:247 : Security Types received (1): Unknown 
type (18)
  [ 5872/ 6448] 2014-01-20 12:11:18:247   Selecting auth-handler
  [ 5872/ 6448] 2014-01-20 12:11:18:247 + RemoteViewerCore. Exception: No 
security types supported. Server sent security types, but we do not support any 
of their.

  So it seems that the update changed the security type of vino to a new
  one. I searched for a way to go back to the old one (until the clients
  catches up) with no avail.

  A solution is disabling the encryption completely, by

  gsettings set org.gnome.Vino require-encryption false

  ...but this is subotpimal. Is there a way to switch the encryption
  back to the old one?

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

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


[Desktop-packages] [Bug 1248260] Re: ibus-daemon hogging resources

2014-05-28 Thread madmaze
I have been having a similar problem for a while now, very randomly. I
am not sure if its the same as described by others.

I cannot reproduce it at will(It seems to happen when moving between
windows, especially gnome-terminal, eclipse and guake), but every now
and again the IBUS-daemon pegs one CPU core at 100% and all typing
becomes very delayed.

Today I finally managed to get an strace log of it happening, at least
the tail end of it. I did not catch the beginning of the event only the
end before it went back to normal, but you can see that it's trying to
continuously access an unavailable resource.

Please see attached log.

** Attachment added: "Issue log"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1248260/+attachment/4121633/+files/ibus.log

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

Title:
  ibus-daemon hogging resources

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  At times, typing becomes very sluggish and I can see ibus-daemon
  becomes the process consuming most CPU and most memory in the system.

  Everything else is responsive, i.e. mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 17:08:06 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-07-07 (1217 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  SourcePackage: ibus
  UpgradeStatus: Upgraded to saucy on 2013-10-25 (11 days ago)

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

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


[Desktop-packages] [Bug 1248260] Re: ibus-daemon hogging resources

2014-05-28 Thread madmaze
for comparison, I also attached what the strace log looks like during
normal operation

** Attachment added: "ibus_normal.log"
   
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1248260/+attachment/4121634/+files/ibus_normal.log

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

Title:
  ibus-daemon hogging resources

Status in “ibus” package in Ubuntu:
  Confirmed

Bug description:
  At times, typing becomes very sluggish and I can see ibus-daemon
  becomes the process consuming most CPU and most memory in the system.

  Everything else is responsive, i.e. mouse

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Tue Nov  5 17:08:06 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-07-07 (1217 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  MarkForUpload: True
  SourcePackage: ibus
  UpgradeStatus: Upgraded to saucy on 2013-10-25 (11 days ago)

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

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


[Desktop-packages] [Bug 493766] Re: Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

2014-05-28 Thread Jesse Glick
Confirmed workaround from comment #12 in emacs24 24.3+1-2ubuntu1 (Ubuntu
14.04), normally using @im=ibus and the right Ctrl key as the compose
key.

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

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

Title:
  Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Ubuntu:
  New
Status in “emacs23” package in Fedora:
  Unknown

Bug description:
  Binary package hint: emacs23

  Ubuntu 9.10
  emacs23:
Installed: 23.1+1-4ubuntu3.1

  Using X with a configuration for SCIM input methods, environment
  variable XMODIFIERS then contains @im=SCIM

  Start emacs

  Hit Multi_key (aka Compose key, often bound to one of the Windows keys
  depending on keyboard layout and layout options) ' (single quote) e

  You should be getting é (e acute accent)

  Instead, emacs complains that  is undefined.

  Problem disappears if launching Emacs with XMODIFIERS="'

  ProblemType: Bug
  Architecture: i386
  Date: Mon Dec  7 21:56:37 2009
  DistroRelease: Ubuntu 9.10
  Package: emacs (not installed)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: emacs22
  Uname: Linux 2.6.31-16-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2548): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2537): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2536): Gdk-WARNING **: 
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a 
pixmap or window

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

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


[Desktop-packages] [Bug 1111884] Re: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT

2014-05-28 Thread Jochen Fahrner
I have to correct myself. Kernel 3.7.10 does not solve the issues with
nouveau. The only difference is: it does not always freeze after resume,
but sometimes it also does. With later kernel version it always freezes.

In many years as a Ubuntu user my experience is, that the free graphic
drivers (nouveau, radeon) never worked satisfying, and this has not
changed until now. The proprietary drivers always worked better, and I
hope they gain control of the problems with nvidia driver.

At the moment I think it's best to downgrade to 12.04 and wait for a
half year or a year.

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

Title:
  10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT

Status in The Linux Kernel:
  Invalid
Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Triaged

Bug description:
  Happens when resuming from standby. Can be reproduced. Every time.

  nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 
0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT
  nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 
0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT
  nouveau E[  PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at 
address 00449b
  nouveau E[  PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: 
, e1c: , e20: 0011, e24: 0c03
  nouveau E[  PGRAPH][:05:00.0]  TRAP
  nouveau E[  PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d 
mthd 0x060c data 0x04b0
  nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 
0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT
  nouveau E[  PGRAPH][:05:00.0] magic set 0:
  nouveau E[  PGRAPH][:05:00.0] 0x00408904: 0x20087701
  nouveau E[  PGRAPH][:05:00.0] 0x00408908: 0x00449b00
  nouveau E[  PGRAPH][:05:00.0] 0x0040890c: 0x8432
  nouveau E[  PGRAPH][:05:00.0] 0x00408910: 0x9b00
  nouveau E[  PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 
0x0003
  nouveau E[  PGRAPH][:05:00.0]  TRAP

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-core 2:1.13.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
  Uname: Linux 3.8.0-2-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.8-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CrashCounter: 1
  Date: Thu Jan 31 22:17:49 2013
  DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job
  DistroCodename: raring
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:2330]
  MachineType: System manufacturer System Product Name
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch -background none
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic 
root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
   ?? () from /usr/lib/xorg/modules/libexa.so
  Title: Xorg crashed with SIGABRT
  UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago)
  UserGroups:

  dmi.bios.date: 12/24/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0806
  dmi.board.name: P5WD2-Premium
  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.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.41-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  ve

[Desktop-packages] [Bug 1112061] Re: unity forgets focus-follows-mouse setting across update and reboot

2014-05-28 Thread Raik Gruenberg
I can confirm this bug on a fresh 14.04 installation. Every other day,
the focus-follows mouse and autoraise setting is reset to default. I
have been using this feature on linux since 13 years. It's really
disruptive that settings are just lost.

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

Title:
  unity forgets focus-follows-mouse setting across update and reboot

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I had gone roughly two weeks without rebooting my 12.10 installation.
  After applying updates that included a new kernel today, I rebooted to
  finish the updates.

  Unity forgot my focus-follows-mouse setting across the updates and
  reboot.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Jan 31 18:57:02 2013
  InstallationDate: Installed on 2012-10-18 (105 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-20 (12 days ago)

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

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


[Desktop-packages] [Bug 1112061] Re: unity forgets focus-follows-mouse setting across update and reboot

2014-05-28 Thread Raik Gruenberg
PS: I actually seem to have lost the setting mid-session without even
logging out.

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

Title:
  unity forgets focus-follows-mouse setting across update and reboot

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I had gone roughly two weeks without rebooting my 12.10 installation.
  After applying updates that included a new kernel today, I rebooted to
  finish the updates.

  Unity forgot my focus-follows-mouse setting across the updates and
  reboot.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.12.0-0ubuntu0.2
  ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Thu Jan 31 18:57:02 2013
  InstallationDate: Installed on 2012-10-18 (105 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2013-01-20 (12 days ago)

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

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


[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread Jason Gerard DeRose
Marked as fixed release for System76 as the 14.04.5 release of the
system76-driver includes a grub line fix for this:

http://bazaar.launchpad.net/~system76-dev/system76-driver/trunk/view/head:/debian/changelog

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  Fix Released
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1288004] Re: hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

2014-05-28 Thread Jason Gerard DeRose
Marked as fixed release for System76 as the 14.04.5 release of the
system76-driver includes a grub line fix for this:

http://bazaar.launchpad.net/~system76-dev/system76-driver/trunk/view/head:/debian/changelog

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

Title:
  hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell
  HDMI, Digital Out, HDMI] Playback problem

Status in System76:
  Fix Released
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  Not sure which  package
  Sound comes through hdmi sounding like a chipmunks tune.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Mar  4 18:21:58 2014
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1231947] Re: gnome-settings-daemon input "hotplug-command" not working in 13.10

2014-05-28 Thread Quinn Strahl
Also affected by this issue, on 14.04. Very irksome. =S

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

Title:
  gnome-settings-daemon input "hotplug-command" not working in 13.10

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  I have always used this method in ubuntu to enable 3-finger tap on my
  synaptics touchpad (and by the way, 3-finger tap works out of the box
  in every non-ubuntu distro  /rant):

  
  create a file called touchpad_settings.sh.
  chmod +x touchpad_settings.sh
  gsettings set org.gnome.settings-daemon.peripherals.input-devices 
hotplug-command "/home/brandon/touchpad_settings.sh"

  This way 3 finger tap is working and gnome always respects the setting
  and doesn't reset it on suspend/resume. This worked perfectly in
  12.04, 12.10, and 13.04. In 13.10 it just does not work. I double
  checked, made sure I had the right path to the file, and that the file
  was executable. If I manually execute touchpad_settings.sh it works,
  but when I boot my computer it just does not seem to run the hotplug
  command, and if I manually run the script and then suspend/resume,
  gnome disables the 3 finger tap upon resume, again not respecting the
  hotplug-command.

  This is a big issue, this is the only way to get 3 finger tap working
  on a touchpad in ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 27 07:37:54 2013
  InstallationDate: Installed on 2013-09-27 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.xdg.autostart.gnome.fallback.mount.helper.desktop: 
[modified]
  modified.conffile..etc.xdg.autostart.gnome.settings.daemon.desktop: [modified]
  mtime.conffile..etc.xdg.autostart.gnome.fallback.mount.helper.desktop: 
2013-09-27T07:35:28.871725
  mtime.conffile..etc.xdg.autostart.gnome.settings.daemon.desktop: 
2013-09-27T07:35:28.875723

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

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


[Desktop-packages] [Bug 1324214] Re: NetworkManager sets MTU to 9000 even on 100mbps connections

2014-05-28 Thread Rob A
FYI: to test, you need to have a network that supports jumbo frames,
then snip the 2 wires on your patch cable (so 1gbps can't be
negotiated), or set the VM to only negotiate 100mbps in the VM
definition, but leave NetworkManager's automatic MTU detection enabled.

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

Title:
  NetworkManager sets MTU to 9000 even on 100mbps connections

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

Bug description:
  I have a network which supports jumbo frames end-to-end internally.
  This weekend, after rebooting my laptop, it came up only negotiating
  100mbps, but networkManager still set the MTU to 9000, which doesn't
  work (can't do jumbo frames on anything except 1gbps, by spec).  NM
  should recognie the auto-negotiated rate as part of the "automatic
  MTU" determiniation.

  Kubuntu 14.04.  When I pulled the cable, and rerouted it, the laptop
  re-negotiated 1gbps again, and jumbo frames went fine.  This output
  was gathered during the time when the laptop was stuck at 100mbps.

  rob@kubuntu4:~$ lsb_release -rd
  Description:Ubuntu 14.04 LTS
  Release:14.04
  rob@kubuntu4:~$ sudo apt-cache policy network-manager
  [sudo] password for rob: 
  network-manager:
Installed: 0.9.8.8-0ubuntu7
Candidate: 0.9.8.8-0ubuntu7
Version table:
   *** 0.9.8.8-0ubuntu7 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  Network setup is:
  kubuntu laptop -> dlink switch -> ESXi 5.1 server -> VMs
   
  MTU=9000 causes problems.
   
  VM -> VM works on same server.
   
  Switch hardware: 
http://www.dlink.com/us/en/business-solutions/switching/unmanaged-switches/rackmount/dgs-1024d-24-port-copper-gigabit-switch
  ESX set up following: 
http://www.edge-cloud.net/2013/11/jumbo-frames-vmware-esxi/
   
  TCP packets over 1500 bytes just keep getting retransmitted, accordint to 
tcpdump captures.
   
  Laptop:
  rob@kubuntu4:/var/log$ sudo ethtool eth0
  [sudo] password for rob:
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: 100Mb/s
  Duplex: Full
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: off (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
 drv probe link
  Link detected: yes
  rob@kubuntu4:/var/log$ ifconfig eth0
  eth0  Link encap:Ethernet  HWaddr 00:21:cc:cf:e0:78 
inet addr:192.168.0.106  Bcast:192.168.0.255  Mask:255.255.255.0
inet6 addr: fe80::221:ccff:fecf:e078/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
RX packets:17744 errors:0 dropped:0 overruns:0 frame:0
TX packets:15941 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:11750951 (11.7 MB)  TX bytes:5220060 (5.2 MB)
Interrupt:20 Memory:d250-d252
   
   
  VM SSH Server:
   
  rob@srv1:/var/log$ sudo ethtool eth0
[8/1084]
  [sudo] password for rob:
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   1000baseT/Full
  1baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: No
  Advertised link modes:  Not reported
  Advertised pause frame use: No
  Advertised auto-negotiation: No
  Speed: 1Mb/s
  Duplex: Full
  Port: Twisted Pair
  PHYAD: 0
  Transceiver: internal
  Auto-negotiation: off
  MDI-X: Unknown
  Supports Wake-on: uag
  Wake-on: d
  Link detected: yes
  rob@srv1:/var/log$ ifconfig eth0
  eth0  Link encap:Ethernet  HWaddr 00:50:56:B6:7F:3D 
inet addr:192.168.0.21  Bcast:192.168.0.255  Mask:255.255.255.0
inet6 addr: fe80::250:56ff:feb6:7f3d/64 Scope:Link
 

[Desktop-packages] [Bug 1288004] Re: hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

2014-05-28 Thread Jason Gerard DeRose
** Changed in: system76
   Status: New => Fix Released

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

Title:
  hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell
  HDMI, Digital Out, HDMI] Playback problem

Status in System76:
  Fix Released
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  Not sure which  package
  Sound comes through hdmi sounding like a chipmunks tune.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Mar  4 18:21:58 2014
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread Jason Gerard DeRose
** Changed in: system76
   Status: In Progress => Fix Released

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  Fix Released
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1324214] [NEW] NetworkManager sets MTU to 9000 even on 100mbps connections

2014-05-28 Thread Rob A
Public bug reported:

I have a network which supports jumbo frames end-to-end internally.
This weekend, after rebooting my laptop, it came up only negotiating
100mbps, but networkManager still set the MTU to 9000, which doesn't
work (can't do jumbo frames on anything except 1gbps, by spec).  NM
should recognie the auto-negotiated rate as part of the "automatic MTU"
determiniation.

Kubuntu 14.04.  When I pulled the cable, and rerouted it, the laptop re-
negotiated 1gbps again, and jumbo frames went fine.  This output was
gathered during the time when the laptop was stuck at 100mbps.

rob@kubuntu4:~$ lsb_release -rd
Description:Ubuntu 14.04 LTS
Release:14.04
rob@kubuntu4:~$ sudo apt-cache policy network-manager
[sudo] password for rob: 
network-manager:
  Installed: 0.9.8.8-0ubuntu7
  Candidate: 0.9.8.8-0ubuntu7
  Version table:
 *** 0.9.8.8-0ubuntu7 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status


Network setup is:
kubuntu laptop -> dlink switch -> ESXi 5.1 server -> VMs
 
MTU=9000 causes problems.
 
VM -> VM works on same server.
 
Switch hardware: 
http://www.dlink.com/us/en/business-solutions/switching/unmanaged-switches/rackmount/dgs-1024d-24-port-copper-gigabit-switch
ESX set up following: 
http://www.edge-cloud.net/2013/11/jumbo-frames-vmware-esxi/
 
TCP packets over 1500 bytes just keep getting retransmitted, accordint to 
tcpdump captures.
 
Laptop:
rob@kubuntu4:/var/log$ sudo ethtool eth0
[sudo] password for rob:
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 2
Transceiver: internal
Auto-negotiation: on
MDI-X: off (auto)
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes
rob@kubuntu4:/var/log$ ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:21:cc:cf:e0:78 
  inet addr:192.168.0.106  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::221:ccff:fecf:e078/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:9000  Metric:1
  RX packets:17744 errors:0 dropped:0 overruns:0 frame:0
  TX packets:15941 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:11750951 (11.7 MB)  TX bytes:5220060 (5.2 MB)
  Interrupt:20 Memory:d250-d252
 
 
VM SSH Server:
 
rob@srv1:/var/log$ sudo ethtool eth0
[8/1084]
[sudo] password for rob:
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   1000baseT/Full
1baseT/Full
Supported pause frame use: No
Supports auto-negotiation: No
Advertised link modes:  Not reported
Advertised pause frame use: No
Advertised auto-negotiation: No
Speed: 1Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
MDI-X: Unknown
Supports Wake-on: uag
Wake-on: d
Link detected: yes
rob@srv1:/var/log$ ifconfig eth0
eth0  Link encap:Ethernet  HWaddr 00:50:56:B6:7F:3D 
  inet addr:192.168.0.21  Bcast:192.168.0.255  Mask:255.255.255.0
  inet6 addr: fe80::250:56ff:feb6:7f3d/64 Scope:Link
  UP BROADCAST RUNNING ALLMULTI MULTICAST  MTU:9000  Metric:1
  RX packets:22817347 errors:0 dropped:80 overruns:0 frame:0
  TX packets:11956945 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:11504454844 (10.7 GiB)  TX bytes:32510875048 (30.2 GiB)
 
 
 
ESX Server:
This system has been migrated to ESXi 5.1.0.
~ # esxcfg-vswitch -l
Switch Name  Num Ports   Used Ports  Configured Ports  MTU Uplinks  
 
vSwitch0 128 24  128   9000
vmnic0,vmnic1
 
  PortGroup NameVLAN ID  Used Ports  Uplinks   
  Management Network01   vmnic0,vmnic1
  VM Networ

[Desktop-packages] [Bug 1294163] Re: Please update precise nvidia drivers to support 3.13 trusty backport kernel

2014-05-28 Thread Ryan Tandy
Hi Alberto,

You wrote: "As for 304, I haven't fixed it to 3.13 yet." That appears to
still be the case in precise.

I applied the patch from http://bazaar.launchpad.net/~ubuntu-
branches/ubuntu/trusty/nvidia-graphics-drivers-304/trusty/revision/21 to
nvidia-304 from precise, and it works for me. Would you accept a merge
proposal with that change?

(I guess we also need 304.117 in order to support the lts-trusty X
server...)

Can you please add nvidia-304{,-updates} tasks for Precise to this bug
for tracking? (If you prefer I can open a separate bug.)

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

Title:
  Please update precise nvidia drivers to support 3.13 trusty backport
  kernel

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Invalid
Status in “nvidia-graphics-drivers-331” source package in Precise:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” source package in Precise:
  Fix Released

Bug description:
  [Impact]

  * The 3.13 trusty backport kernel for 12.04 will be released fairly
  soon.  Some people have started testing the daily builds out the the
  Kernel Team PPA.  However the NVIDIA binary drivers in precise need
  patches to support the 3.13 kernel.

  [Test Case]

   * The latest Nvidia binary driver series in 12.04 should work with
  the upcomping 3.13 backport kernel; it currently does not.

  [Regression Potential]

   * Low.  The patches enable compatibility with newer kernels but do
  not affect installations on older kernels.

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

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


[Desktop-packages] [Bug 1324204] [NEW] some bug error

2014-05-28 Thread Prabhudev
Public bug reported:

i think its regarding graphics issue

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  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.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed May 28 23:17:29 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-27-generic, x86_64: installed
 nvidia-331-updates, 331.38, 3.13.0-27-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3978]
   Subsystem: Lenovo GeForce GT 720M [17aa:3800]
InstallationDate: Installed on 2014-05-14 (13 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 20298
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic 
root=UUID=ef054f6c-0a60-469d-8954-d1952d06407b ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 89CN25WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo IdeaPad S510p
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S510p
dmi.modalias: 
dmi:bvnLENOVO:bvr89CN25WW:bd08/07/2013:svnLENOVO:pn20298:pvrLenovoIdeaPadS510p:rvnLENOVO:rnLenovoIdeaPadS510p:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoIdeaPadS510p:
dmi.product.name: 20298
dmi.product.version: Lenovo IdeaPad S510p
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54+git20140523.8fc62ca8-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.3.0~git20140523.172ef0c5-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.3.0~git20140523.172ef0c5-0ubuntu0ricotz~trusty
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.99+git20140523.851b2cf8-0ubuntu0ricotz~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.911+git20140523.417997f3-0ubuntu0ricotz~trusty
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt
xserver.bootTime: Wed May 28 23:11:58 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  some bug error

Status in “xorg” package in Ubuntu:
  New

Bug description:
  i think its regarding graphics issue

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  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.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 28 23:17:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-27-ge

[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

2014-05-28 Thread Yotam Benshalom
I think that we have here a derious regression no matter what we choose
to do, because non-latin hotkeys were usable in previous versions of
Gnome. But I also think that users of apps like Eclipse and JetBrains
are programmers who rarely have to use non-latin languages, while users
of LibreOffice use these languages all the time and are more dependant
on them.

This is why I think that until a solution is found, these patches should
be used across the board. If they are problematic, maybe it makes more
sense to enable them for the PPA's only, and not in the stable version.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in Aptana Studio Installer:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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


[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread mika
after saving,

 sudo update-grub

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  In Progress
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread mika
nb : for other noob like me, that'll save you the "how to" search :

sudo gedit /etc/default/grub

replace

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

with

GRUB_CMDLINE_LINUX_DEFAULT="i915.disable_power_well=0 quiet splash"

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  In Progress
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread mika
Intel® Core™ i7-4712MQ CPU @ 2.30GHz × 8  & GeForce GTX 860M/PCIe/SSE2

fix worked for me

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  In Progress
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1290611] Re: [Clevo W65_67SZ, Intel Haswell HDMI, Digital Out, HDMI] crackling sound and audio up a note

2014-05-28 Thread mika
*** This bug is a duplicate of bug 1256655 ***
https://bugs.launchpad.net/bugs/1256655

bug was duplicate indeed sorry, good fix available now

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

Title:
  [Clevo W65_67SZ, Intel Haswell HDMI, Digital Out, HDMI] crackling
  sound and audio up a note

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

Bug description:
  installed pavucontrol to get the sound from HDMI but the result is
  crackle sound and audio is up a note.

  This problem exists on 13.10 and 14.04 not on 13.04. I noticed the

  
  alsa info from 13.4 shows the soundcard: 
  00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06)
  00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio 
Controller (rev 05)

  while from 14.04
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 10 23:55:20 2014
  InstallationDate: Installed on 2014-03-04 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140302)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [W65_67SZ, Intel Haswell HDMI, Digital Out, HDMI] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RTO
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RTO:bd12/05/2013:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


[Desktop-packages] [Bug 1319191] Re: middle-click in window's top bar does not send-to-back

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Confirmed

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

Title:
  middle-click in window's top bar does not send-to-back

Status in “chromium-browser” package in Ubuntu:
  Confirmed

Bug description:
  In Unity, middle-clicking the title bars of other windows sends those
  windows to the bottom of the stack, making it very easy to expose the
  windows underneath. Chromium-browser, however, does not respect this
  convention.

  To reproduce this issue, start another program or two, such as urxvt
  or firefox, and chromium-browser. Drag all the windows to e.g. the
  right side of the screen to have them occupy the right half of the
  screen. Middle click the chromium-browser title bar and notice how
  nothing happens. Raise one of the other windows using the Unity dock,
  middle-click the title bar, and notice how the window is sent to the
  bottom of the stack.

  If the stack does not contain chromium-browser, it is possible to
  cycle through all windows this way. If the stack does contain
  chromium-browser, the cycle is broken with chromium-browser.

  I expect chromium-browser to behave identical to the other programs I
  run and move to the bottom of the stack.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 13 14:19:04 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2012-10-18 (572 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to trusty on 2014-04-12 (31 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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


[Desktop-packages] [Bug 1315384] Re: python-indicate doesn't work in 14.04

2014-05-28 Thread Jochen Fahrner
Charles, if libindicate ist dead, please remove this package and all
dependent packages. It makes no sense to keep non working packages! It
confuses everybody.

Canonical should make it clear that libindicate does not longer exist.

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

Title:
  python-indicate doesn't work in 14.04

Status in The Messaging Menu:
  Won't Fix
Status in “libindicate” package in Ubuntu:
  Won't Fix

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1308152] Re: Cant boot from kernel 3.13.0.24 after upgrade to ubuntu 14.04 LTS but able to boot with Kernel 3.11.0.20

2014-05-28 Thread Shravan
Hi Massimo Forti (slackwarelife) ,
Thanks for Posting my issue is solved after applying the solution

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

Title:
  Cant boot from kernel 3.13.0.24 after upgrade to ubuntu 14.04 LTS but
  able to boot with Kernel 3.11.0.20

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  Today i have upgraded my PC from Ubuntu 13.10 to Ubuntu 14.04 LTS beta but 
after the Upgrade i am unable to boot with Linux 3.13.0-24-generic
  and i am getting this error "Serious errors were found while checking the 
disk drive for Press I to ignore S to skip mount M to Manual intervention"
  But i am able to Boot with the Old Linux Kernel 3.11.0-20-generic.

  I tried to do the following after checking the fourm
  fsck /dev/sda1
  fsck -Aa
  but it returned that file system is clean

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10
  ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6
  Uname: Linux 3.11.0-20-generic i686
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Apr 15 22:06:55 2014
  InstallationDate: Installed on 2013-11-23 (143 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-04-15 (0 days ago)

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

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


[Desktop-packages] [Bug 1314694] Re: nm-connection-editor segfaults when importing vpn configuration

2014-05-28 Thread b3nmore
*** This bug is a duplicate of bug 1294899 ***
https://bugs.launchpad.net/bugs/1294899

** This bug has been marked a duplicate of bug 1294899
   Import saved VPN connection has been Recently Broken

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

Title:
  nm-connection-editor segfaults when importing vpn configuration

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

Bug description:
  Trying to import a vpnc configuration, but the connection editor segfaults 
when the configuration file gets loaded:
  nm-connection-e[18008]: segfault at 1bd02b0 ip 01bd02b0 sp 
7fff768f9e58 error 15

  Adding the vpnc profile manually works fine, but in previous versions
  the import did work too.

  network-manager 0.9.8.8-0ubuntu7 on a fully updated xubuntu 14.04.

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

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


[Desktop-packages] [Bug 1315384] Re: python-indicate doesn't work in 14.04

2014-05-28 Thread Charles Kerr
** Project changed: libindicate => indicator-messages

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

Title:
  python-indicate doesn't work in 14.04

Status in The Messaging Menu:
  Won't Fix
Status in “libindicate” package in Ubuntu:
  Won't Fix

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1314694] Re: nm-connection-editor segfaults when importing vpn configuration

2014-05-28 Thread Matthew Moppett
It seems that this problem has already been addressed on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/network-manager-
openvpn/+bug/1294899

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

Title:
  nm-connection-editor segfaults when importing vpn configuration

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

Bug description:
  Trying to import a vpnc configuration, but the connection editor segfaults 
when the configuration file gets loaded:
  nm-connection-e[18008]: segfault at 1bd02b0 ip 01bd02b0 sp 
7fff768f9e58 error 15

  Adding the vpnc profile manually works fine, but in previous versions
  the import did work too.

  network-manager 0.9.8.8-0ubuntu7 on a fully updated xubuntu 14.04.

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

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


[Desktop-packages] [Bug 1314694] Re: nm-connection-editor segfaults when importing vpn configuration

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  nm-connection-editor segfaults when importing vpn configuration

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

Bug description:
  Trying to import a vpnc configuration, but the connection editor segfaults 
when the configuration file gets loaded:
  nm-connection-e[18008]: segfault at 1bd02b0 ip 01bd02b0 sp 
7fff768f9e58 error 15

  Adding the vpnc profile manually works fine, but in previous versions
  the import did work too.

  network-manager 0.9.8.8-0ubuntu7 on a fully updated xubuntu 14.04.

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

-- 
Mailing list: https://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 1298913] Re: package flashplugin-installer 11.2.202.346ubuntu0.13.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2014-05-28 Thread Stefano Rizzinelli
Hello, sorry for not answering before,
but I had already solved by reinstalling
*.*

Thank you all the same


2014-03-28 15:27 GMT+01:00 Jörg Frings-Fürst :

> Hello,
>
> we need some more information. From a terminal window please run:
>
> sudo apt-get clean
> sudo apt-get update
> sudo apt-get -f install
>
> attach the output here
> and then change the status of the bug to 'Confirmed'.
>
> Jörg
>
>
> ** Changed in: flashplugin-nonfree (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1298913
>
> Title:
>   package flashplugin-installer 11.2.202.346ubuntu0.13.10.1 failed to
>   install/upgrade: subprocess installed post-installation script
>   returned error exit status 1
>
> Status in “flashplugin-nonfree” package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I'm not able to provide more details
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 13.10
>   Package: flashplugin-installer 11.2.202.346ubuntu0.13.10.1
>   ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
>   Uname: Linux 3.11.0-14-generic i686
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.12.5-0ubuntu2.2
>   Architecture: i386
>   Date: Fri Mar 28 11:32:17 2014
>   DuplicateSignature:
> package:flashplugin-installer:11.2.202.346ubuntu0.13.10.1:subprocess
> installed post-installation script returned error exit status 1
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
>   InstallationDate: Installed on 2013-12-17 (100 days ago)
>   InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386
> (20131016.1)
>   MarkForUpload: True
>   SourcePackage: flashplugin-nonfree
>   Title: package flashplugin-installer 11.2.202.346ubuntu0.13.10.1 failed
> to install/upgrade: subprocess installed post-installation script returned
> error exit status 1
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1298913/+subscriptions
>


-- 
Stefano Rizzinelli

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

Title:
  package flashplugin-installer 11.2.202.346ubuntu0.13.10.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in “flashplugin-nonfree” package in Ubuntu:
  Expired

Bug description:
  I'm not able to provide more details

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: flashplugin-installer 11.2.202.346ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  Date: Fri Mar 28 11:32:17 2014
  DuplicateSignature: 
package:flashplugin-installer:11.2.202.346ubuntu0.13.10.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2013-12-17 (100 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release i386 
(20131016.1)
  MarkForUpload: True
  SourcePackage: flashplugin-nonfree
  Title: package flashplugin-installer 11.2.202.346ubuntu0.13.10.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 141388] Re: Sort order of Processes %CPU column reversed (compared to Nice, ID, Memory, etc.)

2014-05-28 Thread Christoph Michelbach
I had the problem of all columns in the past, too. But I don't remember
which version it was. Since then everything was ok but now I have the
problem that the CPU usage column is reversed, too. I use Ubuntu 14.04
64 Bit and think this problem didn't exist in the last few versions of
Ubuntu.

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

Title:
  Sort order of Processes %CPU column reversed (compared to Nice, ID,
  Memory, etc.)

Status in The GNOME System Monitor:
  Invalid
Status in “gnome-system-monitor” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-system-monitor

  When selecting a Processes column for sorting and the down-arrow icon
  is displayed Process Name, Status, Nice, ID, and Memory sort low-to-
  high top-to-bottom (towards the bottom of the screen).

  However the %CPU column when displaying the down-arrow icon sorts
  high-to-low top-to-bottom.

  When the up-arrow icon is displayed the situation is reversed; %CPU is
  low-to-high top-to-bottom and the others high-to-low top-to-bottom.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/141388/+subscriptions

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


[Desktop-packages] [Bug 141388] Re: Sort order of Processes %CPU column reversed (compared to Nice, ID, Memory, etc.)

2014-05-28 Thread Christoph Michelbach
Why is the status of this bug report "invalid"?

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

Title:
  Sort order of Processes %CPU column reversed (compared to Nice, ID,
  Memory, etc.)

Status in The GNOME System Monitor:
  Invalid
Status in “gnome-system-monitor” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-system-monitor

  When selecting a Processes column for sorting and the down-arrow icon
  is displayed Process Name, Status, Nice, ID, and Memory sort low-to-
  high top-to-bottom (towards the bottom of the screen).

  However the %CPU column when displaying the down-arrow icon sorts
  high-to-low top-to-bottom.

  When the up-arrow icon is displayed the situation is reversed; %CPU is
  low-to-high top-to-bottom and the others high-to-low top-to-bottom.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/141388/+subscriptions

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


[Desktop-packages] [Bug 1315384] Re: python-indicate not showing up in message indicator

2014-05-28 Thread Charles Kerr
Ah, for some reason I thought that python-indicate was coming from
outside of that repo.

So instead I'm marking as wontfix since libindicate is dead. :)

Possibly Lars' example in comment:14 should be added to a README or
examples file in indicator-messages...

** Changed in: libindicate (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: libindicate
   Status: Confirmed => Won't Fix

** Summary changed:

- python-indicate not showing up in message indicator
+ python-indicate doesn't work in 14.04

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

Title:
  python-indicate doesn't work in 14.04

Status in Libindicate:
  Won't Fix
Status in “libindicate” package in Ubuntu:
  Won't Fix

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1324183] [NEW] [enhancement] FD passing for unity-system-compositor

2014-05-28 Thread Chris Halse Rogers
Public bug reported:

Here's the global bug for FD passing from unity-system-compositor to
unity8 rather than having a socket file.

The general flow would be:
*) LightDM gets a client socket from USC
*) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
*) unity8 pulls the fd from logind on startup

This then needs an apparmour profile so that dbus denies access to the
system-compositor fd from everything that's not unity.

** Affects: lightdm
 Importance: Undecided
 Status: New

** Affects: systemd
 Importance: Undecided
 Status: New

** Affects: unity-system-compositor
 Importance: Undecided
 Status: New

** Affects: unity8
 Importance: Undecided
 Status: New

** Affects: lightdm (Ubuntu)
 Importance: Wishlist
 Assignee: Chris Halse Rogers (raof)
 Status: Triaged

** Affects: systemd (Ubuntu)
 Importance: Wishlist
 Assignee: Chris Halse Rogers (raof)
 Status: Triaged

** Affects: unity-system-compositor (Ubuntu)
 Importance: Wishlist
 Assignee: Chris Halse Rogers (raof)
 Status: Triaged

** Affects: unity8 (Ubuntu)
 Importance: Wishlist
 Assignee: Chris Halse Rogers (raof)
 Status: Triaged

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

** Also affects: unity-system-compositor
   Importance: Undecided
   Status: New

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

** Also affects: unity-system-compositor (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: unity-system-compositor (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

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

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

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

** Changed in: unity-system-compositor (Ubuntu)
   Status: New => Triaged

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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: unity8 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: unity-system-compositor (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [enhancement] FD passing for unity-system-compositor

Status in Light Display Manager:
  New
Status in systemd:
  New
Status in Unity System Compositor:
  New
Status in The Unity 8 shell:
  New
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “systemd” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Triaged
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Here's the global bug for FD passing from unity-system-compositor to
  unity8 rather than having a socket file.

  The general flow would be:
  *) LightDM gets a client socket from USC
  *) LightDM sends that fd to logind as a part of the session description 
(instead of X server number)
  *) unity8 pulls the fd from logind on startup

  This then needs an apparmour profile so that dbus denies access to the
  system-compositor fd from everything that's not unity.

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

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


[Desktop-packages] [Bug 1315384] Re: python-indicate not showing up in message indicator

2014-05-28 Thread Charles Kerr
Reassigning to python-indicate since this isn't a bug in libindicate.

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

Title:
  python-indicate doesn't work in 14.04

Status in Libindicate:
  Won't Fix
Status in “libindicate” package in Ubuntu:
  Won't Fix

Bug description:
  Install python-indicate and libindicate-doc. Run:

  python /usr/share/doc/libindicate/examples/im-client.py

  An entry should appear in message indicator, but does not. That worked
  in 12.04 but is broken in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: python-indicate 12.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 15:22:27 2014
  InstallationDate: Installed on 2014-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: libindicate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse scrolling speed

2014-05-28 Thread Devin Linnington
Weird, comment 63 actually fixed this for me.

I'm using Fedora 20 with gnome 3 and stumbled on this bug. My scroll has
been going crazy since I restarted, and the only thing that fixed it was
unplugging and replugging the little USB wireless key. I have a
microsoft wireless mobile mouse 4000.

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

Title:
  [enhancement] Ubuntu needs a way to set mouse scrolling speed

Status in GNOME Control Center:
  New
Status in GTK+ GUI Toolkit:
  New
Status in One Hundred Papercuts:
  Confirmed
Status in Mir:
  Triaged
Status in Unity:
  Invalid
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “gtk+3.0” package in Ubuntu:
  Confirmed

Bug description:
  This has been driving me nuts for a while now. The scroll wheel on my
  desktop mouse (it's an MS wireless optical mouse model 1008) scrolls
  rather fast. Instead of moving a few lines, it scrolls half a page or
  more with a very gentle scroll. The bluetooth mouse I use with my
  laptop does not do this so it's probably somewhat hardware specific.
  However, I'm wondering if there is a way to modify the speed or
  sensitivity. I found an answer here from about a year ago
  (https://answers.launchpad.net/ubuntu/+question/1339) that suggests
  there isn't a way but I'm wondering if anything has changed since
  then. I've also skimmed through synaptic but didn't see anything
  promising (like gsynaptic for touchpads).

  Thanks.

  See https://answers.launchpad.net/ubuntu/+question/9200 for more
  information.

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

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


[Desktop-packages] [Bug 1283491] Re: rendering and size issues on high-dpi screen

2014-05-28 Thread Andreas E.
Thanks, the version 1.0.1 in the ppa renders properly. However, it is
still not perfectly usable on the high-dpi screen because it expands to
much to the top (I believe the snapping feature gets sometimes the
window coordinates wrong). I will try to narrow it down to write a
separate bug report.

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

Title:
  rendering and size issues on high-dpi screen

Status in Onboard on-screen keyboard:
  Fix Released
Status in “onboard” package in Ubuntu:
  Triaged

Bug description:
  When the global scaling factor is set to 2, onboard is not usable for
  touch input. In docked mode (bottom half of screen), it draws keys too
  large and most of the onboard UI is not drawn at all. In windowed mode
  (with titlebar and resizeable), the size is correct but it does not
  refresh the rendering.

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

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: onboard 1.0.0-0ubuntu2
  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
  CurrentDesktop: Unity
  Date: Sat Feb 22 17:44:03 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (19 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201)
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1322300] Re: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar)

2014-05-28 Thread Robert Ancell
** Changed in: lightdm
Milestone: None => 1.11.3

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

Title:
  [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
  similar)

Status in Light Display Manager:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  /tmp/mir_socket is created by unity-system-compositor. It is easy to
  prevent mir from starting by creating this file before hand. Eg:

  # stop lightdm ; touch /tmp/mir_socket ; start lightdm

  lightdm fails to start. It would be better if /run/mir_socket (or some
  other root-owned directory) were used.

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

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


[Desktop-packages] [Bug 1275416] Re: touchscreen do not work after suspend/resume

2014-05-28 Thread ADRIANO MARCELINO SALGADO
Same with ACER aspire M5. Touchscreen stops after first suspend/resume
and Ctrl+Alt+F6 / Ctrl+Alt+F7 solves the issue.

Quite odd!!

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

Title:
  touchscreen do not work after suspend/resume

Status in “xinput” package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Thinkpad X200T with multi-touch screen) installed the
  'Trusty' ubuntu 14.04 (64bits), touchscreen works well after cold
  boot! But after suspend/resume, touchsreen do not response. Execute
  'xsetwacom --list' in terminal, there is nothing, both 'wacom touch'
  and 'wacom stylus' are gone. I must logout and relogin or reboot, the
  touchscreen can be normal again.

  By the way, the same problem happens in the 'Saucy' ubuntu 13.10
  (64bits). But in 'Raring' ubuntu 13.04 (64bits), this problem does no
  exist, touchscreen WORKS WELL after suspend/resume.

  This Thinkpad X200T updated the newest BIOS, and keep ubuntu OS up to
  date.

  Please fix this bug, because 14.04 is a very important version for
  touchscreen devices, and i think 'suspend/resume' function is
  important too. Thanks!

  ---
  Feb 4, 2014 update

  Oh I'm sorry, I find a new change for this bug that I never noticed
  before.

  I keep Trusty ubuntu up to date(Feb 4, 2014). When the OS's first boot
  from cold boot, touchscreen works well. Then if suspend/resume for the
  first time, touchscreen will not response. At this moment, logout and
  relogin, touchscreen works well again even after suspend/resume.

  Simply put, touchscreen do not response only after the first
  suspend/resume since a cold boot. Once the OS logout and relogin,
  touchscreen will work well after any suspend/resume. The key point is
  that the OS must logout and relogin for at least one time.

  Always keep 'Trusty' ubuntu OS updated.

  that's a strange bug

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

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


[Desktop-packages] [Bug 1288004] Re: hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem

2014-05-28 Thread Peter Curtis
Neil Shepperd was too modest to say he produced a quick workaround in
https://bugzilla.kernel.org/show_bug.cgi?id=74861.  This simple simple
fix works for me on a Chillblast Defiant mini laptop which has
Haswell/Optimus Architecture, Core i7 Processor and nVidia GTX 765M
graphics running Mint 17 (equivalent to 14.04).

The quick fix is to pass i915.disable_power_well=0 on the kernel command
line which works around the problem, letting audio play at the correct
speed again. After confirmation one can modify /etc/default/grub to make
it permanent. Hopefully the commit will soon be reversed.

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

Title:
  hdmi audio is sped up/high pitched[Gazelle Professional, Intel Haswell
  HDMI, Digital Out, HDMI] Playback problem

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

Bug description:
  Ubuntu 13.10
  Not sure which  package
  Sound comes through hdmi sounding like a chipmunks tune.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Mar  4 18:21:58 2014
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RS76:bd01/15/2014:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1322300] Re: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar)

2014-05-28 Thread Robert Ancell
** Changed in: lightdm
   Importance: Undecided => Medium

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

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

Title:
  [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
  similar)

Status in Light Display Manager:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  /tmp/mir_socket is created by unity-system-compositor. It is easy to
  prevent mir from starting by creating this file before hand. Eg:

  # stop lightdm ; touch /tmp/mir_socket ; start lightdm

  lightdm fails to start. It would be better if /run/mir_socket (or some
  other root-owned directory) were used.

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

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


[Desktop-packages] [Bug 1322300] Re: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar)

2014-05-28 Thread Chris Halse Rogers
** Changed in: lightdm (Ubuntu)
   Importance: Undecided => High

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

** No longer affects: mir

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

Title:
  [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
  similar)

Status in Light Display Manager:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  /tmp/mir_socket is created by unity-system-compositor. It is easy to
  prevent mir from starting by creating this file before hand. Eg:

  # stop lightdm ; touch /tmp/mir_socket ; start lightdm

  lightdm fails to start. It would be better if /run/mir_socket (or some
  other root-owned directory) were used.

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

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


[Desktop-packages] [Bug 1324173] [NEW] Screen flickers black and backtraces in dmesg

2014-05-28 Thread Jussi Pakkanen
Public bug reported:

Using newest utopic my screen flickers to black and back every now and
then during regular use. After a few seconds it comes back. Whenever
this happens I get an error trace in dmesg. All of them are slightly
different, here is an example one:

[55848.787245] CPU: 3 PID: 15271 Comm: kworker/3:2 Tainted: GW  OE 
3.15.0-2-generic #6-Ubuntu
[55848.787248] Hardware name: Apple Inc. MacBookPro11,1/Mac-189A3D4F975D5FFC, 
BIOS MBP111.88Z.0138.B07.1402121134 02/12/2014
[55848.787252] Workqueue: pm pm_runtime_work
[55848.787255]  0009 8803a94c1c20 81729283 
8803a94c1c68
[55848.787260]  8803a94c1c58 81066a5d 880453fe 
880453948378
[55848.787266]  880453948380  880458a71098 
8803a94c1cb8
[55848.787271] Call Trace:
[55848.787275]  [] dump_stack+0x45/0x56
[55848.787281]  [] warn_slowpath_common+0x7d/0xa0
[55848.787286]  [] warn_slowpath_fmt+0x4c/0x50
[55848.787322]  [] hsw_enable_pc8+0x64e/0x6f0 [i915]
[55848.787330]  [] ? pci_legacy_suspend_late+0xf0/0xf0
[55848.787350]  [] i915_runtime_suspend+0x80/0xd0 [i915]
[55848.787361]  [] pci_pm_runtime_suspend+0x61/0x140
[55848.787368]  [] ? pci_legacy_suspend_late+0xf0/0xf0
[55848.787373]  [] __rpm_callback+0x36/0xc0
[55848.787379]  [] ? try_to_grab_pending+0xa9/0x160
[55848.787384]  [] rpm_callback+0x24/0x80
[55848.787389]  [] rpm_suspend+0x111/0x640
[55848.787394]  [] pm_runtime_work+0xb2/0xe0
[55848.787401]  [] process_one_work+0x182/0x450
[55848.787408]  [] worker_thread+0x121/0x410
[55848.787414]  [] ? rescuer_thread+0x430/0x430
[55848.787420]  [] kthread+0xc9/0xe0
[55848.787426]  [] ? kthread_create_on_node+0x190/0x190
[55848.787431]  [] ret_from_fork+0x7c/0xb0
[55848.787436]  [] ? kthread_create_on_node+0x190/0x190
[55848.787439] ---[ end trace 9a13d45f13da41fc ]---

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
ProcVersionSignature: Ubuntu 3.15.0-2.6-generic 3.15.0-rc6
Uname: Linux 3.15.0-2-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.2-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May 28 18:38:19 2014
DistUpgraded: 2014-05-27 12:43:31,956 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed
 virtualbox, 4.3.10, 3.15.0-2-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:0a2e] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:011a]
InstallationDate: Installed on 2014-05-22 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417)
MachineType: Apple Inc. MacBookPro11,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-2-generic 
root=UUID=aec3f04d-865c-4f0f-9872-d8953e94278d ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to utopic on 2014-05-27 (1 days ago)
dmi.bios.date: 02/12/2014
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B07.1402121134
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue May 27 15:51:39 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40992 
 vendor APP
xserver.version: 2:1.15.1-0ubuntu5

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification be

[Desktop-packages] [Bug 1256655] Re: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback problem, built in speakers work but no audio over HDMI

2014-05-28 Thread Peter Curtis
The kernel problem has been identified at
https://bugzilla.kernel.org/show_bug.cgi?id=74861 by kernel commit
bisection  and the simple fix works for me on a Chillblast Defiant mini
laptop which has Haswell/Optimus Architecture, Core i7 Processor and
nVidia GTX 765M graphics running Mint 17 (equivalent to 14.04).

The quick fix is to pass i915.disable_power_well=0 on the kernel command
line which works around the problem, letting audio play at the correct
speed again. After confirmation one can modify /etc/default/grub. The
commit needs reversing.

** Bug watch added: Linux Kernel Bug Tracker #74861
   http://bugzilla.kernel.org/show_bug.cgi?id=74861

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

Title:
  [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback
  problem, built in speakers work but no audio over HDMI

Status in System76:
  In Progress
Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  The laptop came with Ubuntu 13.04 installed and when I installed the Intel 
drivers from 01.org there was audio over the HDMI port.
  With Ubuntu 13.10 it has since been impossible to get the sound over the HDMI 
port. When I downgrade to 13.04 with the 01.org drivers it works again.
  In windows 7 the audio over HDMI works perfectly as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  remco  1361 F pulseaudio
   /dev/snd/controlC1:  remco  1361 F pulseaudio
  Date: Sun Dec  1 16:58:25 2013
  InstallationDate: Installed on 2013-12-01 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Only some of outputs are working
  Title: [Gazelle Professional, Intel Haswell HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/13/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1322300] Re: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar)

2014-05-28 Thread Chris Halse Rogers
Actually, those tasks are really for a separate bug. It's trivial to fix
this issue, so I'll do so. And then open a separate bug.

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

Title:
  [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
  similar)

Status in Light Display Manager:
  New
Status in Mir:
  Opinion
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  /tmp/mir_socket is created by unity-system-compositor. It is easy to
  prevent mir from starting by creating this file before hand. Eg:

  # stop lightdm ; touch /tmp/mir_socket ; start lightdm

  lightdm fails to start. It would be better if /run/mir_socket (or some
  other root-owned directory) were used.

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

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


[Desktop-packages] [Bug 1322300] Re: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar)

2014-05-28 Thread Launchpad Bug Tracker
** Branch linked: lp:~raof/lightdm/run-is-the-new-tmp

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

Title:
  [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
  similar)

Status in Light Display Manager:
  New
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  /tmp/mir_socket is created by unity-system-compositor. It is easy to
  prevent mir from starting by creating this file before hand. Eg:

  # stop lightdm ; touch /tmp/mir_socket ; start lightdm

  lightdm fails to start. It would be better if /run/mir_socket (or some
  other root-owned directory) were used.

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

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


[Desktop-packages] [Bug 1322300] Re: [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or similar)

2014-05-28 Thread Chris Halse Rogers
…cue lots of discussion…

Unless we change the way we start Unity8 (which I've yet to convince
people we should), we - tragically - can't pass an fd to unity on
startup.

What we *can* do is hand off an FD to logind, and have unity8 pull it
from there. Keeping that fd away from non-Unity processes is then left
as an exercise for AppArmour confinement profiles written by the
security team.

Adding appropriate tasks.

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

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

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

** No longer affects: systemd (Ubuntu)

** No longer affects: unity8 (Ubuntu)

** No longer affects: unity-system-compositor (Ubuntu)

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

** Changed in: lightdm (Ubuntu)
 Assignee: (unassigned) => Chris Halse Rogers (raof)

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

Title:
  [enhancement] Please move /tmp/mir_socket to /run/mir_socket (or
  similar)

Status in Mir:
  Opinion
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  /tmp/mir_socket is created by unity-system-compositor. It is easy to
  prevent mir from starting by creating this file before hand. Eg:

  # stop lightdm ; touch /tmp/mir_socket ; start lightdm

  lightdm fails to start. It would be better if /run/mir_socket (or some
  other root-owned directory) were used.

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

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


[Desktop-packages] [Bug 1313658] Re: Xorg crashes when enabling second monitor

2014-05-28 Thread Stefan Bethge
Another error case is as follows: successfully use the second monitor after 
cold starting, disable it in display properties. Suspend and later resume the 
system without the monitor attached. Attach the monitor and enable it in 
display properties, Xorg will crash.
After logging in again, trying to activate the monitor will not result in a 
crash but will give the following error message (in my locale, german):
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2:
 Konfiguration für CRTC »583« konnte nicht angewendet werden

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

Title:
  Xorg crashes when enabling second monitor

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

Bug description:
  After attaching my second monitor, I can open display properties and select 
and enable it. After pressing apply, Xorg crashes and puts me back to the login 
screen. The monitor then can be used. A suspend and resume cycle crashes X 
again regardless of the monitor still being attached or not. Re-attaching 
sometimes also immediately crashes X. Setting the computer to sleep with the 
monitor attached sometimes keeps the computer flashing the suspend led until I 
hard reset it. The logfile after one such crash is attached. It gives the error 
"(EE) NVIDIA(0): Failed to allocate primary buffer: out of memory." which I 
found some related bug reports to but none in ubuntu that crashes X. There is a 
similar bug report for the exact same machine (Thinkpad R61) without solution 
for Mageia here: https://bugs.mageia.org/show_bug.cgi?id=9229#c13.
  Just to confirm, the same computer monitor combination can be used fine in 
windows, so it should be capable of the combined resolution.
  (The same behaviour might also be seen using the nouveau driver, but I have 
to try that again).

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

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


  1   2   >