date:20140619

This bug was fixed in the package gtk+3.0 - 3.12.2-0ubuntu4

---
gtk+3.0 (3.12.2-0ubuntu4) utopic; urgency=medium

  * debian/patches/git-gtkpopover-set-background-and-popover-css.patch
- backport from master (lp: #1329792, gnome: #731834)
 -- Lars Uebernickel lars.uebernic...@ubuntu.com   Wed, 18 Jun 2014 17:32:26 
+0200

** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  gtkpopover widgets not rendered

Status in “gtk+3.0” package in Ubuntu:
  Fix Released

Bug description:
  After Utopic update to use gtk+ 3.12, GtkVolumeButton do not let to
  use volume pops up control. I can change volume only if mouse cursor
  is over volume icon and I use mouse scroll wheel.

  You can reproduce this in totem and rhythmbox by clicking in volume
  icon and try to move up or down volume control slider that show's up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1329792/+subscriptions

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

[Desktop-packages] [Bug 1308771] Re: Update Swedish spellcheck and hyphenation dictionaries

2014-06-19 Thread Gunnar Hjalmarsson

Hi Björn!

Are you in doubt about this, or can it be uploaded to trusty-proposed?

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

Title:
  Update Swedish spellcheck and hyphenation dictionaries

Status in “libreoffice-dictionaries” package in Ubuntu:
  Fix Released
Status in “openoffice.org-hyphenation” package in Ubuntu:
  Fix Released
Status in “libreoffice-dictionaries” source package in Trusty:
  Triaged
Status in “openoffice.org-hyphenation” source package in Trusty:
  Triaged

Bug description:
  trusty SRU request
  ==

  [Impact]
  While the libreoffice-dictionaries source package contains reasonably updated 
spell check dictionaries and hyphenation patterns for Swedish, it does 
currently not build hunspell-sv-se and hyphen-sv. In Utopic this has now been 
fixed, and the outdated hyphenation patterns for Swedish in 
openoffice.org-hyphenation have been dropped.

  It's desirable that it's fixed in Trusty as well, so Swedish 14.04
  users don't need to go hunting on the web for up-to-date writing aids.
  After all, LibreOffice is one of the core tools on the desktop.

  [Test Case]
  I haven't figured out specific examples of words or patterns that are 
currently missing and will be included with this SRU.

  [Regression Potential]
  Once it has been verified that the up-to-date dictionaries are installed 
correctly, and that spell checking and hyphenation works as expected in 
LibreOffice, the risk for regression ought to be limited to the risk that 
certain words or patterns, which are currently included, proves to have been 
dropped.

  [Other Info]
  I have attached an SRU patch for libreoffice-dictionaries. As regards 
openoffice.org-hyphenation, some encoding problem in one of the removed files 
prevented me from creating a patch that applies seamlessly. Instead I simply 
suggest that openoffice.org-hyphenation 0.8 is uploaded to trusty-proposed as 
version 0.7.1.

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

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

[Desktop-packages] [Bug 1327774] Re: asus x200la brightness hotkeys not working (rest of them do)

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

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New = Confirmed

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

Title:
  asus x200la brightness hotkeys not working (rest of them do)

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

Bug description:
  If I click on brightness hotkeys nothing (apparently) happens. I
  suppose keys are missbinded or something like that. How can I fix it?

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

Using Ubuntu 14.04, intel hd 3000, nvidia gt540m, same problem as above
unable to switch from intel to nvidia, updated system still same bug,

sudo prime-select query
unknown

sudo prime-select nvidia
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

sudo cat /proc/acpi/bbswitch
:01:00.0 ON

dmesg | grep -E 'bbswitch|nvidia'
[9.854343] bbswitch: module verification failed: signature and/or  required 
key missing - tainting kernel
[9.854498] bbswitch: version 0.7
[9.854504] bbswitch: Found integrated VGA device :00:02.0: 
\_SB_.PCI0.GFX0
[9.854510] bbswitch: Found discrete VGA device :01:00.0: 
\_SB_.PCI0.PEG0.PEGP
[9.854565] bbswitch: detected an Optimus _DSM function
[9.854574] bbswitch: Succesfully loaded. Discrete card :01:00.0 is on
[   22.177483] init: Failed to spawn nvidia-persistenced main process: unable 
to execute: No such file or directory

** Attachment added: dmidecode.log
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310023/+attachment/4134695/+files/dmidecode.log

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  In Progress

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1066529] Re: All jobs stopped, epson_inkjet_printer_filter failed

2014-06-19 Thread ferro

Epson driver just does not work. I tried Ubuntu 14.04 with all available
drivers, i always got filter error. If you try to call the filter from
bash it says: no such file or directory. I compiled the filter myself,
then a cammand line call gave me  insufficient options which looked
promising, but the filter did not work. Unfortunately there is zero
documentation for the filter, so i could not get it to spit out a log,
althoug the source code has some debugging code.  Openprinting.org gives
information that is just a lie. This printer driver does not work. As
last resort i chose turboprint, a 30 EUR software which is not GPL but
at least worked perfectly from the beginning. Even printing PDF files on
a DVD surface on an Epson XP-750 works perfectly. I am running
turboprint on a dedicated print server on Ubuntu 14.04 without X, this
works perfectly, not the driver provided by epson.

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

Title:
  All jobs stopped, epson_inkjet_printer_filter failed

Status in “cups” package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 12.04.1 64bit
  Cups 1.5.3-0ubuntu4
  EPSON WF-7520 - epson-inkjet-printer 1.0.0-1lsb3.2 - the last driver from 
Epson.
  Connected via USB.

  The printer just stopped to print - every job added in stopped state and 
this error:
  
/opt/epson-inkjet-printer-201115w/cups/lib/filter/epson_inkjet_printer_filter 
failed

  The printer screen says Printing endless.

  Will happy to provide additional info to resolve this issue.

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

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

[Desktop-packages] [Bug 1331959] [NEW] Loads static contents if I switch to another network connections

2014-06-19 Thread VINAY Kr. SHARMA

Public bug reported:

I've determined many times when I changes network connections.

Nightly loads static contents again like fonts and images again even
that contents has long expiry on every network switch.

I frequently switchs to Data Card 3G network and my office Wi-Fi
network, then I saw that problems with Nightly.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox-trunk 33.0~a1~hg20140617r188919-0ubuntu1~umd1
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  vinay  2376 F pulseaudio
BuildID: 20140617055833
Channel: nightly
CurrentDesktop: Unity
Date: Thu Jun 19 13:19:41 2014
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2014-04-03 (76 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
IpRoute:
 default via 10.228.10.6 dev ppp0  proto static 
 10.228.10.6 dev ppp0  proto kernel  scope link  src 180.215.166.109
Locales: extensions.sqlite corrupt or missing
PrefSources:
 prefs.js
 
[Profile]/extensions/{bee6eb20-01e0-ebd1-da83-080329fb9a3a}/defaults/preferences/prefs.js
Profiles: Profile0 (Default) - LastVersion=33.0a1/20140617055833 (In use)
RelatedPackageVersions:
 google-talkplugin 5.4.2.0-1
 rhythmbox-mozilla 3.0.2-0ubuntu2
 totem-mozilla 3.10.1-1ubuntu4
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 06RYX8
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/19/2013:svnDellInc.:pnInspiron3521:pvrA10:rvnDellInc.:rn06RYX8:rvrA02:cvnDellInc.:ct8:cvrA10:
dmi.product.name: Inspiron 3521
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug nightly-channel trusty

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

Title:
  Loads static contents if I switch to another network connections

Status in “firefox” package in Ubuntu:
  New

Bug description:
  I've determined many times when I changes network connections.

  Nightly loads static contents again like fonts and images again even
  that contents has long expiry on every network switch.

  I frequently switchs to Data Card 3G network and my office Wi-Fi
  network, then I saw that problems with Nightly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox-trunk 33.0~a1~hg20140617r188919-0ubuntu1~umd1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vinay  2376 F pulseaudio
  BuildID: 20140617055833
  Channel: nightly
  CurrentDesktop: Unity
  Date: Thu Jun 19 13:19:41 2014
  EcryptfsInUse: Yes
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2014-04-03 (76 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  IpRoute:
   default via 10.228.10.6 dev ppp0  proto static 
   10.228.10.6 dev ppp0  proto kernel  scope link  src 180.215.166.109
  Locales: extensions.sqlite corrupt or missing
  PrefSources:
   prefs.js
   
[Profile]/extensions/{bee6eb20-01e0-ebd1-da83-080329fb9a3a}/defaults/preferences/prefs.js
  Profiles: Profile0 (Default) - LastVersion=33.0a1/20140617055833 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.4.2.0-1
   rhythmbox-mozilla 3.0.2-0ubuntu2
   totem-mozilla 3.10.1-1ubuntu4
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06RYX8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias:

[Desktop-packages] [Bug 749934] Re: incorrect keymap name in indicator-applet

2014-06-19 Thread Elbarbudo

My 2 cents comment :
I have Fr and En(USA) environment (Keyboard)

On 1st login from fresh start : OK
When I close the session and log in again, The applet show Fr, but the keyboard 
is US.

Just clicking on the applet and switching to En then to Fr get things
OK.

My 2 cents hint : This seems to be a time-race problem : when the applet
starts up, Kbd is FR, but some init put it back discretly in En.

OR : The applet uses the latest settings but they are Not applied to the
Kbd map

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

Title:
  incorrect keymap name in indicator-applet

Status in “libgnomekbd” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-control-center

  My desktop currently is configured with the following keyboard maps
  (according to gconf names):

  [fi classic,se rus]

  In the keyboard map applet that appears in application-indicator, the
  first one is correctly identified as Fin.

  However, the second one is incorrectly identified as Swe, even though
  this is a Russian keyboard map variant (with the usual Cyrillic
  letters). The se prefix in the gconf key refers to the fact that
  punctuation marks are designed to match the locations on a Swedish
  keyboard map, to ease a phonetic transition between a normal Swedish
  map using Latin letters with Scandinavian vowels and a Russian
  phonetic map using Cyrillic letters. This is mainly usefull for
  Russian speakers living in Finland or Sweden, who constantly need to
  switch between two alphabets. It therefore should be identified as Rus
  in the 3-letter identifier that appears besides the applet's icon in
  the notification area or in indicator-application.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-control-center 1:2.32.1-0ubuntu12
  ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  Date: Mon Apr  4 07:35:06 2011
  ProcEnviron:
   LANGUAGE=fi_FI:fi_FI.UTF-8:fi
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to natty on 2009-09-14 (566 days ago)

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

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

[Desktop-packages] [Bug 1331960] [NEW] after suspend/resume cycle screen remains black with working cursor

2014-06-19 Thread Andy Whitcroft

Public bug reported:

After some (not all by any means) suspend/resume cycles, the screen
remains black with a movable cursor.  Note this is with an external
monitor attached, the cursor can be moved to either normally.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.1+14.04.20140513-0ubuntu2
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
Uname: Linux 3.15.0-5-generic x86_64
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]
Date: Thu Jun 19 09:07:16 2014
DistUpgraded: 2014-01-17 11:38:47,872 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:029f]
   Subsystem: Dell Device [1028:029f]
MachineType: Dell Inc. Studio 1537
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-5-generic 
root=UUID=0c1a857a-009e-48e4-bba0-19bd862bfe63 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-01-17 (152 days ago)
dmi.bios.date: 09/22/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
dmi.product.name: Studio 1537
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Tue Jun 10 12:24:55 2014
xserver.configfile: default
xserver.errors: intel(0): Failed to submit rendering commands, disabling 
acceleration.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8771 
 vendor AOC
xserver.version: 2:1.15.1-0ubuntu2
--- 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  apw3083 F pulseaudio
 /dev/snd/pcmC0D0p:   apw3083 F...m pulseaudio
 /dev/snd/controlC0:  apw3083 F pulseaudio
 /dev/snd/controlC1:  apw3083 F pulseaudio
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]
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=19a8d63a-3fd5-4b14-aa6a-13c3dc353651
MachineType: Dell Inc. Studio 1537
Package: unity 7.2.1+14.04.20140513-0ubuntu2
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-5-generic 
root=UUID=0c1a857a-009e-48e4-bba0-19bd862bfe63 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
RelatedPackageVersions:
 linux-restricted-modules-3.15.0-5-generic N/A
 linux-backports-modules-3.15.0-5-generic  N/A
 linux-firmware1.127.2
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: trusty third-party-packages trusty
Uname: Linux 3.15.0-5-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-01-17 (152 days ago)
UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild 
sudo
_MarkForUpload: True
dmi.bios.date: 09/22/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A03
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd09/22/2008:svnDellInc.:pnStudio1537:pvrA03:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrA03:
dmi.product.name: Studio 1537
dmi.product.version: A03
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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


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

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

** Tags added: apport-collected

[Desktop-packages] [Bug 1219245] Please test proposed package

Hello j, or anyone else affected,

Accepted libreoffice-l10n into trusty-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/libreoffice-
l10n/1:4.2.4-0ubuntu2 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  soffice.bin crashed with SIGSEGV in
  ImplDevFontListData::~ImplDevFontListData()

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Committed
Status in “libreoffice” source package in Trusty:
  Fix Committed
Status in “libreoffice” package in Fedora:
  Unknown

Bug description:
  [Impact]

   * crash, high counts of stack traces on errors.ubuntu.com

  [Test Case]

   * no good reproduction scenario known

  [Regression Potential]

   * limited:
     - patch is on master upstream
     - patch has been released to the LibreOffice PPA for a while without
   any negative feedback
     - changes limited to vcl

  [Other Info]

   * backport of fix by RedHat

  original report:

  ubuntustudio 13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-core 1:4.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.1-lowlatency 3.11.0-rc5
  Uname: Linux 3.11.0-2-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sat Aug 31 17:27:00 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-08-28 (3 days ago)
  InstallationMedia: Ubuntu-Studio 13.10 Saucy Salamander - Alpha amd64 
(20130824)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7f1e300bfd30:mov0x58(%rdi),%rdx
   PC (0x7f1e300bfd30) ok
   source 0x58(%rdi) (0x0056) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ImplDevFontList::Clear() () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   SalGenericDisplay::DispatchInternalEvent() () from 
/usr/lib/libreoffice/program/libmergedlo.so
  Title: soffice.bin crashed with SIGSEGV in ImplDevFontList::Clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare scanner sudo video

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

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

[Desktop-packages] [Bug 1296715] Please test proposed package

Hello LostinSpacetime, or anyone else affected,

Accepted libreoffice-l10n into trusty-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/libreoffice-
l10n/1:4.2.4-0ubuntu2 in a few hours, and then in the -proposed
repository.

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

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

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

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

Title:
  Menu items are greyed  out in Libreoffice menu.

Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * Unity-only bug

  [Test Case]

   * Start LibreOffice Writer
   * click menu Insert-Object-Formula
   * press Escape to leave formula mode
   * Open Insert menu
   * expected behaviour: e.g. Insert Bookmark is enabled
   * actual behavious: Insert Bookmark is disabled

  [Regression Potential]

   * limited:
 - patch has been released to the LibreOffice PPA for a while without
   any negative feedback
 - changes limited to vcl (mostly gtk backend) and framework (trivial)

  [Other Info]

   * original report:

  After adding a formula, OLE-Object or diagram to the document and then
  exiting the editing mode, one cannot choose several items from the
  menubar, neither using a mouse or the HUD. The affected items are
  greyed out and mostly in the Add and Format dropdown menu. After
  first navigating to that item with the mouse pointer, the second time
  the items become available.

  After deinstalling the indicator-appmenu package, the Libreoffice menu works 
without problems.
  ---
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-05-03 (324 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  NonfreeKernelModules: nvidia
  Package: indicator-appmenu 13.01.0+14.04.20140320-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-03-16 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1296715] Re: Menu items are greyed out in Libreoffice menu.

Hello LostinSpacetime, or anyone else affected,

Accepted libreoffice into trusty-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/libreoffice/1:4.2.4-0ubuntu2 in a
few hours, and then in the -proposed repository.

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

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

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

** Tags added: verification-needed

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

Title:
  Menu items are greyed  out in Libreoffice menu.

Status in “indicator-appmenu” package in Ubuntu:
  Invalid
Status in “libreoffice” package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * Unity-only bug

  [Test Case]

   * Start LibreOffice Writer
   * click menu Insert-Object-Formula
   * press Escape to leave formula mode
   * Open Insert menu
   * expected behaviour: e.g. Insert Bookmark is enabled
   * actual behavious: Insert Bookmark is disabled

  [Regression Potential]

   * limited:
 - patch has been released to the LibreOffice PPA for a while without
   any negative feedback
 - changes limited to vcl (mostly gtk backend) and framework (trivial)

  [Other Info]

   * original report:

  After adding a formula, OLE-Object or diagram to the document and then
  exiting the editing mode, one cannot choose several items from the
  menubar, neither using a mouse or the HUD. The affected items are
  greyed out and mostly in the Add and Format dropdown menu. After
  first navigating to that item with the mouse pointer, the second time
  the items become available.

  After deinstalling the indicator-appmenu package, the Libreoffice menu works 
without problems.
  ---
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-05-03 (324 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  NonfreeKernelModules: nvidia
  Package: indicator-appmenu 13.01.0+14.04.20140320-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-03-16 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1219245] Re: soffice.bin crashed with SIGSEGV in ImplDevFontListData::~ImplDevFontListData()

Hello j, or anyone else affected,

Accepted libreoffice into trusty-proposed. The package will build now
and be available at
http://launchpad.net/ubuntu/+source/libreoffice/1:4.2.4-0ubuntu2 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  soffice.bin crashed with SIGSEGV in
  ImplDevFontListData::~ImplDevFontListData()

Status in LibreOffice Productivity Suite:
  Fix Released
Status in “libreoffice” package in Ubuntu:
  Fix Committed
Status in “libreoffice” source package in Trusty:
  Fix Committed
Status in “libreoffice” package in Fedora:
  Unknown

Bug description:
  [Impact]

   * crash, high counts of stack traces on errors.ubuntu.com

  [Test Case]

   * no good reproduction scenario known

  [Regression Potential]

   * limited:
     - patch is on master upstream
     - patch has been released to the LibreOffice PPA for a while without
   any negative feedback
     - changes limited to vcl

  [Other Info]

   * backport of fix by RedHat

  original report:

  ubuntustudio 13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libreoffice-core 1:4.1.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.1-lowlatency 3.11.0-rc5
  Uname: Linux 3.11.0-2-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sat Aug 31 17:27:00 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-08-28 (3 days ago)
  InstallationMedia: Ubuntu-Studio 13.10 Saucy Salamander - Alpha amd64 
(20130824)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0x7f1e300bfd30:mov0x58(%rdi),%rdx
   PC (0x7f1e300bfd30) ok
   source 0x58(%rdi) (0x0056) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ImplDevFontList::Clear() () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   ?? () from /usr/lib/libreoffice/program/libmergedlo.so
   SalGenericDisplay::DispatchInternalEvent() () from 
/usr/lib/libreoffice/program/libmergedlo.so
  Title: soffice.bin crashed with SIGSEGV in ImplDevFontList::Clear()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare scanner sudo video

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

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

[Desktop-packages] [Bug 1325273] Re: Samsung Note II does not mount as drives after upgrade to 14.04

2014-06-19 Thread KalaDude

Some further notes:  the card that I plugged into to the card reader was
the one from my canon camera.  When I tried to plud other cards no of
them were read, only canon formatted card was readable.  Finally I
turned off my Samsung Note II and removed the card from it and plugged
it into the card reader.  The card showed up in the file manger but an
error message box appeared with the following error message:

Error mounting /dev/sdd1 at /media/edward/3062-6439: Command-line `mount
-t exfat -o
uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,namecase=0,errors
=remount-ro,umask=0077 /dev/sdd1 /media/edward/3062-6439' exited
with non-zero exit status 32: mount: unknown filesystem type 'exfat'

Hope that helps !  Aloha !

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

Title:
  Samsung Note II does not mount as drives after upgrade to 14.04

Status in “gvfs” package in Ubuntu:
  New

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

  When plugging my Samsung Note II into the USB port, I expect two
  Nautilus windows to pop up on the screen.

  This worked fine before my upgrade.

  There is no logging to /var/log/syslog when I plug in the device.

  lsusb does not list the device.

  $ lsusb
  Bus 001 Device 003: ID 046d:082c Logitech, Inc. 
  Bus 001 Device 002: ID 03f0:c211 Hewlett-Packard 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 003: ID 1130:1620 Tenx Technology, Inc. 
  Bus 003 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  I have also an HTC Vivid that would not mount after the upgrade.  Recently 
however, it has started mounting properly.
  The Samsung Note however, does not mount at all.

  Thanks,

  
  John

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

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

[Desktop-packages] [Bug 1307163] Re: not work gnome-screensaver-command -d

2014-06-19 Thread Andy Buchanan

I too am affected by this problem as I used blueproximity under 12.04 to
lock and unlock my desktop, and it is now unable to unlock it again with
gnome-screensaver-command -d.

What is the solution to this? I need to be able to programmatically
unlock the desktop.

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

Title:
  not work gnome-screensaver-command -d

Status in “blueproximity” package in Ubuntu:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade not work gnome-screensaver-command --deactivate
  jwm + gnome-screensaver impossible to see video because not working 
gnome-screensaver-command -d

  not works:
  gnome-screensaver-command -a
  gnome-screensaver-command -d
  gnome-screensaver-command -l

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 13 18:47:32 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-04-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1302770] Re: keymap unstable

2014-06-19 Thread Jimbo Jambo

thank's marmuta, I'm looking for an answer and I understand that
It is a X problem because if I go in another tty (where isn't X) the keymap is 
the right ones.
well when I returned back with the X ambient the keymap was charged well.


So definitely 'setxkbmap it' make work my keyboard but is it possible that in 
log on this is completely ignored??

And what is meaning the right corner of unity panel with the flag of
current keylayout? (maybe only the linux keymap and not X keymap)

I will try in xinit or some, to put 'setxkbmap'

Thank's marmuta

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

Title:
  keymap unstable

Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  on a tablet pc, once the keyboard has been deactivate, if I try to
  reactivate the keymapping don't load my language, but the American.
  The same after using Onboard keyboard on screen, the real ones changed
  the map.

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

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

Additional:  I added the udev rule back in as it did not get installed
with the download.  Still no good.  Any ideas/help would be greatly
appreciated.  As mentioned way back in my initial post, the camera is
Kodak EasyShare C182.

-- 
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 libgphoto:
  New
Status in Rapid Photo Downloader:
  Invalid
Status in “gvfs” package in Ubuntu:
  Triaged
Status in “libgphoto2” package in Ubuntu:
  Fix Released
Status in “gvfs” source package in Trusty:
  Won't Fix
Status in “libgphoto2” source package in Trusty:
  Fix Committed
Status in “gvfs” source package in Utopic:
  Triaged
Status in “libgphoto2” source package in Utopic:
  Fix Released

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.

  SRU INFORMATION:
  
  IMPACT: All PtP cameras which don't have an explicit vendor/model match in 
/lib/udev/hwdb.d/20-libgphoto2-6.hwdb stop working in gvfs/shotwell/etc. This 
is a regression since Saucy.

  FIX: Bring back the udev rule to tag generic PtP devices that we had had for 
many releases. This will tag the udev_device with the ID_GPHOTO2 property which 
is where gvfs and friends are looking (not on the usb_interface child).
  Patch: 
http://launchpadlibrarian.net/177343655/libgphoto2_2.5.4-1ubuntu1_2.5.4-1ubuntu2.diff.gz

  REGRESSION POTENTIAL: Very low. Adding tags to the wrong device might
  confuse gvfs/shotwell and friends, but this rule had been in
  production for many years. Broken udev rules are harmless except for
  error spew in syslog, and this doesn't interfere with the hwdb
  database as it only matches on usb_devices, not on usb_interfaces.

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 1325273] Re: Samsung Note II does not mount as drives after upgrade to 14.04

2014-06-19 Thread KalaDude

Hmmm, I'm a linux newbie trying to come up to speed.  Hope I'm not
overdoing it with details.  I opened a terminal window and ran the blkid
command.  I have 3 hardrives in my machine, no optical disk, blkid is
clearly showing 4 devices.  Here is the readout from the blkid:

/dev/sda1: LABEL=Blk Cav UUID=1048E52C48E51170 TYPE=ntfs 
/dev/sdb1: UUID=2D030D790055A20C TYPE=ntfs 
/dev/sdc1: UUID=8f4996c0-c2f5-449f-a35c-47f301f66803 TYPE=ext4 
/dev/sdc5: UUID=bb5a4de5-52c7-4781-9520-853743d23b58 TYPE=swap

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

Title:
  Samsung Note II does not mount as drives after upgrade to 14.04

Status in “gvfs” package in Ubuntu:
  New

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

  When plugging my Samsung Note II into the USB port, I expect two
  Nautilus windows to pop up on the screen.

  This worked fine before my upgrade.

  There is no logging to /var/log/syslog when I plug in the device.

  lsusb does not list the device.

  $ lsusb
  Bus 001 Device 003: ID 046d:082c Logitech, Inc. 
  Bus 001 Device 002: ID 03f0:c211 Hewlett-Packard 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 003: ID 1130:1620 Tenx Technology, Inc. 
  Bus 003 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  I have also an HTC Vivid that would not mount after the upgrade.  Recently 
however, it has started mounting properly.
  The Samsung Note however, does not mount at all.

  Thanks,

  
  John

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

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

[Desktop-packages] [Bug 1307163] Vacation reply

2014-06-19 Thread mikael hammarlind

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

Title:
  not work gnome-screensaver-command -d

Status in “blueproximity” package in Ubuntu:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade not work gnome-screensaver-command --deactivate
  jwm + gnome-screensaver impossible to see video because not working 
gnome-screensaver-command -d

  not works:
  gnome-screensaver-command -a
  gnome-screensaver-command -d
  gnome-screensaver-command -l

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-screensaver 3.6.1-0ubuntu13
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 13 18:47:32 2014
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 0
  InstallationDate: Installed on 2014-04-11 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

@Adix: the update hasn't been approved yet, so it's kind of expected
that no fix is available yet.

1) How did you install the nvidia driver?
2) Is bumblebee installed? (it shouldn't be)
3) please attach your /var/log/gpu-manager.log

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

Title:
14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “ubuntu-drivers-common” package in Ubuntu:
Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
In Progress

Bug description:
SRU Request

On some systems bbswitch requires the skip_optimus_dsm=1 option in
order to load properly. So far we have dealt with this problem with
system specific quirks based on DMI information. This some times gives
us false positives or doesn't cover all systems (it's hard to quirk
all systems). We should simply try with and without that option and
use whatever works best for the system. This should cover all cases
with no need for additional quirks.

[Impact]
* Loading bbswitch with the wrong option causes the module to fail from
loading which, in turn, prevents hybrid graphics from working properly.

[Test Case]
* Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is
enabled (attach your /var/log/gpu-manager.log)
- Expected: the NVIDIA GPU is enabled.
- Bad behavior: the system switches back to the intel driver and the
NVIDIA GPU is not used.

[Regression Potential]
* Low. Systems that currently work will keep working as usual, the ones that
currently fail should finally work.

[Other Info]
* N/A

I did a fresh install of 14.04 the day it was released. I use a XPS 15z
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia
Geforce GT 525M). Booting doesn't work out of the box, but by setting
GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0
quiet splash
in /etc/default/grub it works. acpi=off when installing, removed that from
the grub file when installed.

I expected that the Prime feature introduced in kernel 3.12 (kernel
3.13.x here) would let me switch between the Intel and Nvidia cards as
i like, instead of using Bumblebee, which doesn't work properly with
everything. I've installed and tried both the nvidia-331 and
nvidia-304 drivers. Exactly the same result from both.

Attempting to switch to the Nvidia card in nvidia-settings (tried on almost
all of the drivers available, including 331.38) resulted in an error message,
in a new window, with no text.
prime-switch in terminal gives this output: Segmentation fault (core dumped)
Sudoing the process gives no output at all. No graphical performance boost
either, still the Intel card...

sudo prime-select nvidia gives this output:
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

I've also tried Bumblebee (not PPA) a few times, but it's also unable
to switch.

I'm able to use the Intel card temporary, but I would really like to
be able to use the full power of my computer...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nvidia-prime 0.6.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 19 20:52:42 2014
InstallationDate: Installed on 2014-04-17 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

Installed driver using : sudo apt-cache search nvidia-3* sudo apt-get
install nvidia-331 nvidia-prime

Bumblebee and primus are not installed

Attached /var/log/gpu-manager.log

** Attachment added: gpu-manager.log

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310023/+attachment/4134800/+files/gpu-manager.log

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

Title:
14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “ubuntu-drivers-common” package in Ubuntu:
Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
In Progress

Bug description:
SRU Request

[Impact]
* Loading bbswitch with the wrong option causes the module to fail from
loading which, in turn, prevents hybrid graphics from working properly.

[Regression Potential]
* Low. Systems that currently work will keep working as usual, the ones that
currently fail should finally work.

[Other Info]
* N/A

sudo prime-select nvidia gives this output:
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

I've also tried Bumblebee (not PPA) a few times, but it's also unable
to switch.

I'm able to use the Intel card temporary, but I would really like to
be able to use the full power of my computer...

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

[Desktop-packages] [Bug 1331997] [NEW] ???? i dont no

2014-06-19 Thread Daniel Gußmann

Public bug reported:

sorry my english is very old

i install first time ubuntu on an older laptop: hp pavilion dv7 1008eg
with 2gb ram (all hardware is original)

this is my first trip in to the world of linux and i am very happy.

creat an usb stick, install, update an all is running :-)

but an silverlight plugin or add for looking watchever or maxdome? i
dont find some answer.

so i hope i can help you for the next step with send of this datas

good luck an all linux-people, make more

thank to all

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Jun 19 11:06:19 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:30fc]
InstallationDate: Installed on 2014-06-18 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=b7a3cdd0-9d73-4d05-9e9f-6a9f8011e53a ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.49
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 30FD
dmi.board.vendor: Compal
dmi.board.version: 01.99
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.49:bd08/17/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr1:rvnCompal:rn30FD:rvr01.99:cvnCompal:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Jun 19 10:25:36 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output  HDMI-0LVDS 
  VGA-0
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 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/1331997

Title:
   i dont no

Status in “xorg” package in Ubuntu:
  New

Bug description:
  sorry my english is very old

  i install first time ubuntu on an older laptop: hp pavilion dv7 1008eg
  with 2gb ram (all hardware is original)

  this is my first trip in to the world of linux and i am very happy.

  creat an usb stick, install, update an all is running :-)

  but an silverlight plugin or add for looking watchever or maxdome? i
  dont find some answer.

  so i hope i can help you for the next step with send of this datas

  good luck an all linux-people, make more

  thank to all

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun 19 11:06:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470]

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

Please type the following commands:

sudo update-alternatives --config x86_64-linux-gnu_gl_conf
sudo ldconfig -n
sudo update-initramfs -u

then reboot and see if it works

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

Title:
14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “ubuntu-drivers-common” package in Ubuntu:
Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
In Progress

Bug description:
SRU Request

[Impact]
* Loading bbswitch with the wrong option causes the module to fail from
loading which, in turn, prevents hybrid graphics from working properly.

[Regression Potential]
* Low. Systems that currently work will keep working as usual, the ones that
currently fail should finally work.

[Other Info]
* N/A

sudo prime-select nvidia gives this output:
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

I've also tried Bumblebee (not PPA) a few times, but it's also unable
to switch.

I'm able to use the Intel card temporary, but I would really like to
be able to use the full power of my computer...

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

[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

2014-06-19 Thread zig59

@David Henningsson

Hi David,
Have installed the new bluemantest from the ppa and for me it works. Thank you.

It works in the same way that editing the Pulseaudio.py file worked as 
specified by Hartmut. I.e. there are quirks (specified in post #81) to navigate 
to actually get the sound routed to the headphones, it's not simply a case of 
connecting the headphones and everything else is seamless.
In particular, 
i) even after pairing/trusting the headphones in blueman I couldn't select the 
A2DP profile (pulseaudio[1926]: [pulseaudio] module-bluetooth-device.c: Profile 
not connected, refused to switch profile to a2dp; pulseaudio[1926]: 
[pulseaudio] module-bluetooth-device.c: Default profile not connected, 
selecting off profile) until I ran Setup for the headset in blueman
ii) had to manually select the headset in Sound Settings
iii) selecting the headset (Output tab) in Sound Settings caused A2DP to switch 
Off
iv) switching A2DP back on in blueman showed A2DP assigned in Sound Settings 
(Output tab) UNTIL I went into the Input tab to select the headphones there and 
then A2DP dropped out in the Output tab. Selecting A2DP after the headset was 
selected in both Output and Input tabs allowed things to work as required.


@Kiori

Indeed. In my case the irony is that without blueman (which I originally
didn't have installed) I couldn't get the headset to work at all. So
despite blueman having problems of its own it has actually helped to
resolve my problem to the extent where I can actually use the headset
albeit by going around the houses.

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman - Bluetooth Manager:
  Confirmed
Status in “blueman” package in Ubuntu:
  Confirmed
Status in “gnome-bluetooth” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1168582] Re: Google talk Requires Authorization after suspend/resume

2014-06-19 Thread Sayantan Das

Yes same bug. with Ubuntu 14.04
Tested with
1. 13.03.0-29-generic 
2. 3.15.0-031500-generic #201406081435

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

Title:
  Google talk Requires Authorization after suspend/resume

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of raring with all updates. After suspend/resuming my
  laptop, the google talk account refuses to reconnect, and emparthy
  says it requires authorization, if I click the button next to requires
  authorzation it just brings me to UOA and nothing happens. toggling
  the gtalk account on and off doesn't help, it just requires
  authorization again. only way to get it back is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri Apr 12 20:14:00 2013
  InstallationDate: Installed on 2013-04-12 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130411)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1331997] Re: ???? i dont no

2014-06-19 Thread Jackson Doak

Please describe what you were doing before the error occurred rather
than unhelpful things like  i dont no

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

Title:
   i dont no

Status in “xorg” package in Ubuntu:
  New

Bug description:
  sorry my english is very old

  i install first time ubuntu on an older laptop: hp pavilion dv7 1008eg
  with 2gb ram (all hardware is original)

  this is my first trip in to the world of linux and i am very happy.

  creat an usb stick, install, update an all is running :-)

  but an silverlight plugin or add for looking watchever or maxdome? i
  dont find some answer.

  so i hope i can help you for the next step with send of this datas

  good luck an all linux-people, make more

  thank to all

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun 19 11:06:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30fc]
  InstallationDate: Installed on 2014-06-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=b7a3cdd0-9d73-4d05-9e9f-6a9f8011e53a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30FD
  dmi.board.vendor: Compal
  dmi.board.version: 01.99
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.49:bd08/17/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr1:rvnCompal:rn30FD:rvr01.99:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jun 19 10:25:36 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

I tried the following commands, doesn't work after reboot still get:

sudo prime-select query
unknown

sudo cat /proc/acpi/bbswitch
cat: /proc/acpi/bbswitch: No such file or directory

I Have to manually load bbswitch as it has stopped starting at boot
using:

sudo modprobe bbswitch to get sudo cat /proc/acpi/bbswitch :01:00.0
ON

sudo update-alternatives --config x86_64-linux-gnu_gl_conf
There are 3 choices for the alternative x86_64-linux-gnu_gl_conf (providing
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf).

SelectionPath Priority Status

0/usr/lib/nvidia-331/ld.so.conf 8604 auto mode
1/usr/lib/nvidia-331-prime/ld.so.conf8603 manual mode
2/usr/lib/nvidia-331/ld.so.conf 8604 manual mode
* 3/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf 500 manual mode

Press enter to keep the current choice[*], or type selection number: (Tried
with all the above selections)
update-alternatives: using /usr/lib/nvidia-331-prime/ld.so.conf to provide
/etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in manual
mode

sudo ldconfig -n
sudo update-initramfs -u
sudo reboot

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

Title:
14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “ubuntu-drivers-common” package in Ubuntu:
Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
In Progress

Bug description:
SRU Request

[Impact]
* Loading bbswitch with the wrong option causes the module to fail from
loading which, in turn, prevents hybrid graphics from working properly.

[Regression Potential]
* Low. Systems that currently work will keep working as usual, the ones that
currently fail should finally work.

[Other Info]
* N/A

sudo prime-select nvidia gives this output:
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

I've also tried Bumblebee (not PPA) a few times, but it's also unable
to switch.

I'm able to use the Intel card temporary, but I would really like to
be able to use the full power of my computer...

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

--
Mailing list:

[Desktop-packages] [Bug 1331347] Re: [Dell Inspiron 3542] 'ubuntu-driver list' does not suggest to use nvidia-graphics-drivers-331

2014-06-19 Thread Anthony Wong

** Changed in: nvidia-graphics-drivers-331 (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

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

Title:
  [Dell Inspiron 3542] 'ubuntu-driver list' does not suggest to use
  nvidia-graphics-drivers-331

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

Bug description:
  tested by Dell Inspiron 3542 (CID 201402-14684) on 14.04 and 14.10
  daily build

  Steps to reproduce the bugs:
  1. install the system
  2. click 'Software center'--Preference--Additional drivers,
  or, use the command 'ubuntu-driver list'

  Expected result:
  the system should suggest nvidia-graphics-drivers-331 driver package because
  there is a nvidia graphic card
  NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 620M/625M/630M/720M] 
[10de:1140]

  Actual result:
  It didn't suggest any graphic driver to be used.


  -- lspci -nnvv -d 10de:1140 --

  08:00.0 3D controller [0302]: NVIDIA Corporation GF117M [GeForce 
610M/710M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1)
Subsystem: Dell Device [1028:0652]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 63
Region 0: Memory at f600 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at e000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at f000 (64-bit, prefetchable) [size=32M]
Region 5: I/O ports at d000 [size=128]
[virtual] Expansion ROM at f700 [disabled] [size=512K]
Capabilities: access denied
Kernel driver in use: nvidia

  
  -- more information --

  * apt-cache show nvidia-331 | grep 0625
  doesn't give you the expected modalias of the graphic card under sysfs

  * manual installation of nvidia-331 could enable the graphic card and
  works fine.

  $ dpkg -l | grep nvidia
  ii  nvidia-331331.79-0ubuntu1 

 amd64NVIDIA binary driver - version 331.79
  ii  nvidia-libopencl1-331 331.79-0ubuntu1 

 amd64NVIDIA OpenCL Driver and ICD Loader library
  ii  nvidia-opencl-icd-331 331.79-0ubuntu1 

 amd64NVIDIA OpenCL ICD
  ii  nvidia-prime  0.6.5   

 amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings   331.20-0ubuntu8 

 amd64Tool for configuring the NVIDIA graphics 
driver

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

Please repeat what I suggested and attach your /var/log/gpu-manager.log
again

** Also affects: nvidia-prime (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “nvidia-prime” package in Ubuntu:
  New
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  In Progress

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1330942] Re: Gimp does not open pdf

2014-06-19 Thread Filip Sohajek

Tested on this version on 3 different versions of Ubuntu (13.10, 14.04,
14.10), without this problem.

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

Title:
  Gimp does not open pdf

Status in “gimp” package in Ubuntu:
  New

Bug description:
  Trying to open a pdf file gives the message (after selecting 'all
  files'):

  '/home/paulo/test.pdf' failed: Unknown file type

  It is possible though to export an image as pdf.

  This problem started in Ubuntu 13.10 (can't remember any
  specific change or update in other packages other than the regular updates 
from
  Ubuntu repositories) and persisted after a clean install of Ubuntu 14.04 and
  Gimp. 

  Below the console output while opening a pdf file (from the command
  line):

  paulo@paulo-HP-Z600-Workstation:~$ gimp --verbose test.pdf
  INIT: gimp_load_config
  Parsing '/home/paulo/.gimp-2.8/unitrc'
  Parsing '/usr/local/gimp/etc/gimp/2.0/gimprc'
  Parsing '/home/paulo/.gimp-2.8/gimprc'
  gimp_composite: verbose=no
  Processor instruction sets: +mmx +sse +sse2 -3dnow -altivec -vis
  Adding theme 'Default' (/usr/local/gimp/share/gimp/2.0/themes/Default)
  Adding theme 'Small' (/usr/local/gimp/share/gimp/2.0/themes/Small)
  Writing '/home/paulo/.gimp-2.8/themerc'
  Trying splash '/home/paulo/.gimp-2.8/gimp-splash.png' ... failed
  Trying splash '/usr/local/gimp/share/gimp/2.0/images/gimp-splash.png' ... OK
  INIT: gimp_initialize
  INIT: gimp_real_initialize
  INIT: gui_initialize_after_callback
  INIT: gimp_restore
  Parsing '/home/paulo/.gimp-2.8/parasiterc'
  Loading 'brush factory' data
  Loading 'dynamics factory' data
  Loading 'pattern factory' data
  Loading 'palette factory' data
  Loading 'gradient factory' data
  Loading fonts
  Loading 'tool preset factory' data
  Parsing '/home/paulo/.gimp-2.8/templaterc'
  Parsing '/home/paulo/.gimp-2.8/modulerc'
  INIT: gui_restore_callback
  clipboard: writable pixbuf format: image/png
  clipboard: writable pixbuf format: image/x-icon
  clipboard: writable pixbuf format: image/x-ico
  clipboard: writable pixbuf format: image/x-win-bitmap
  clipboard: writable pixbuf format: image/tiff
  clipboard: writable pixbuf format: image/bmp
  clipboard: writable pixbuf format: image/x-bmp
  clipboard: writable pixbuf format: image/x-MS-bmp
  clipboard: writable pixbuf format: image/jpeg
  Parsing '/home/paulo/.gimp-2.8/sessionrc'
  Parsing '/home/paulo/.gimp-2.8/dockrc'
  Parsing '/home/paulo/.gimp-2.8/toolrc'
  Parsing '/home/paulo/.gimp-2.8/contextrc'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-rect-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-ellipse-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-free-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-fuzzy-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-by-color-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-iscissors-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-foreground-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-vector-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-color-picker-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-zoom-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-measure-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-move-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-align-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-crop-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-rotate-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-scale-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-shear-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-perspective-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-flip-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-cage-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-text-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-bucket-fill-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-blend-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-pencil-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-paintbrush-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-eraser-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-airbrush-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-ink-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-clone-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-heal-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-perspective-clone-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-convolve-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-smudge-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-dodge-burn-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-desaturate-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-color-balance-tool'
  Parsing

[Desktop-packages] [Bug 1328003] Re: Update to 24.6.0

2014-06-19 Thread Chris Coulson

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-1536

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-1537

** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-1534

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

Title:
  Update to 24.6.0

Status in “thunderbird” package in Ubuntu:
  Fix Released

Bug description:
  ...

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

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

Repeated all steps, attaching new log

** Attachment added: gpu-manager.log

https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310023/+attachment/4134884/+files/gpu-manager.log

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

Title:
14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “nvidia-prime” package in Ubuntu:
New
Status in “ubuntu-drivers-common” package in Ubuntu:
Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
In Progress

Bug description:
SRU Request

[Impact]
* Loading bbswitch with the wrong option causes the module to fail from
loading which, in turn, prevents hybrid graphics from working properly.

[Regression Potential]
* Low. Systems that currently work will keep working as usual, the ones that
currently fail should finally work.

[Other Info]
* N/A

sudo prime-select nvidia gives this output:
Error: alternatives are not set up properly
Error: nvidia mode can't be enabled

I've also tried Bumblebee (not PPA) a few times, but it's also unable
to switch.

I'm able to use the Intel card temporary, but I would really like to
be able to use the full power of my computer...

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

[Desktop-packages] [Bug 1332044] [NEW] iBus installed w/ Chinese Pinyin but [Invalid UTF-8] results on selection of characters

2014-06-19 Thread Cedric Bhihe

Public bug reported:

Platform: Linux xxx 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

IBus: version 1.5.0 is correctly installed and running as part of TT 14.04 
(LTS). (iBus Daemon runs in current session)
Fonts: ipafont-gothic and ipafont-mincho are installed, as evidenced by a 
proper 'fc-list'
Japanese Anthy text entry: works well (direct trial), except in terminal window.
Chinese SunPinyin text entry: works well, except in terminal window, but not an 
acceptable option for this user
Chinese Pinyin: fails   -- ***

The whole gui seems to work perfectly well, setting of preferences,
Eｎｇｌｉｓｈ full width text entry and toggling between English and Chinese
Pinyin entry with the shift key.

Chinese Text entry (apparently) is well configured with my choice of Chinese 
Pinyin. Pinyin entry actually works and iBus actually reacts well to nihao, 
by proposing 你好 in return (this was pasted from a translation website, not 
generated by this iBus !) . 
However selecting that choice with the space bar, results invariably in 
[Invalid UTF-8].  
 (even after multpiple reboots  restarts of iBus)

Steps to reproduce the error: 
  Unknown. 
  This is the result of a normal dual boot install.
More info:
  If more info is required (hardware, etc), ask.

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

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

Title:
  iBus installed w/ Chinese Pinyin but [Invalid UTF-8] results on
  selection of characters

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

Bug description:
  Platform: Linux xxx 3.13.0-27-generic #50-Ubuntu SMP Thu May 15
  18:06:16 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  IBus: version 1.5.0 is correctly installed and running as part of TT 14.04 
(LTS). (iBus Daemon runs in current session)
  Fonts: ipafont-gothic and ipafont-mincho are installed, as evidenced by a 
proper 'fc-list'
  Japanese Anthy text entry: works well (direct trial), except in terminal 
window.
  Chinese SunPinyin text entry: works well, except in terminal window, but not 
an acceptable option for this user
  Chinese Pinyin: fails   -- ***

  The whole gui seems to work perfectly well, setting of preferences,
  Eｎｇｌｉｓｈ full width text entry and toggling between English and Chinese
  Pinyin entry with the shift key.

  Chinese Text entry (apparently) is well configured with my choice of Chinese 
Pinyin. Pinyin entry actually works and iBus actually reacts well to nihao, 
by proposing 你好 in return (this was pasted from a translation website, not 
generated by this iBus !) . 
  However selecting that choice with the space bar, results invariably in 
[Invalid UTF-8].  
   (even after multpiple reboots  restarts of iBus)

  Steps to reproduce the error: 
Unknown. 
This is the result of a normal dual boot install.
  More info:
If more info is required (hardware, etc), ask.

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

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

[Desktop-packages] [Bug 1271513]

2014-06-19 Thread Alberto Salvia Novella

I keep telling my family in the cuisine you can distinguish bad
management because two things:

1. Lots of unfinished work in sight.
2. Lots of speaking being exchanged.

The reason is always the same: there isn't really anybody taking care of
the process, but just some people blindly working in smoke.

So stop working and start solving. Perhaps it will take you moths, but
not years.

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

Title:
  www.cert.fnmt.es certificates are not included in Mozilla products

Status in The Mozilla Firefox Browser:
  In Progress
Status in Mozilla Thunderbird Mail and News:
  Won't Fix
Status in “firefox” package in Ubuntu:
  Won't Fix
Status in “thunderbird” package in Ubuntu:
  Won't Fix

Bug description:
  Please add www.cert.fnmt.es (National Coin and Ding Factory of
  Spain) as a valid certification authority in the default Firefox
  installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: firefox 26.0+build2-0ubuntu0.13.10.2
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  es20490446e   2130 F pulseaudio
   /dev/snd/controlC1:  es20490446e   2130 F pulseaudio
   /dev/snd/controlC0:  es20490446e   2130 F pulseaudio
  BuildID: 20131206145143
  Channel: Unavailable
  Date: Wed Jan 22 12:49:53 2014
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2013-05-21 (245 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  IpRoute:
   default via 192.168.2.1 dev eth0  proto static
   192.168.2.0/24 dev eth0  proto kernel  scope link  src 192.168.2.117  metric 
1
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  Locales: extensions.sqlite corrupt or missing
  MarkForUpload: True
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=26.0/20131206145143 (In use)
  RelatedPackageVersions:
   google-talkplugin 4.9.1.0-1
   icedtea-7-plugin  1.4-3ubuntu2
   totem-mozilla 3.8.2-0ubuntu1
   rhythmbox-mozilla 2.99.1-0ubuntu1
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to saucy on 2013-10-18 (96 days ago)
  WifiSyslog:

  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

-- 
Mailing list: https://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 1330942] Re: Gimp does not open pdf

2014-06-19 Thread pvanb

On 19-06-14 13:06, Filip Sohajek wrote:
 Tested on this version on 3 different versions of Ubuntu (13.10, 14.04,
 14.10), without this problem.

I solved the problem. As expected, also from your comments, it was a 
problem on my computer. There were a number of GIMP files in my 
/usr/local folder. I really cannot remember ever having compiled GIMP 
myself, so I have not clue how that ended up there, but also not why 
they were not removed with the new Ubuntu install. But in any case, 
removing them solved the problem. Many thanks for your help and sorry 
for the troubles.

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

Title:
  Gimp does not open pdf

Status in “gimp” package in Ubuntu:
  New

Bug description:
  Trying to open a pdf file gives the message (after selecting 'all
  files'):

  '/home/paulo/test.pdf' failed: Unknown file type

  It is possible though to export an image as pdf.

  This problem started in Ubuntu 13.10 (can't remember any
  specific change or update in other packages other than the regular updates 
from
  Ubuntu repositories) and persisted after a clean install of Ubuntu 14.04 and
  Gimp. 

  Below the console output while opening a pdf file (from the command
  line):

  paulo@paulo-HP-Z600-Workstation:~$ gimp --verbose test.pdf
  INIT: gimp_load_config
  Parsing '/home/paulo/.gimp-2.8/unitrc'
  Parsing '/usr/local/gimp/etc/gimp/2.0/gimprc'
  Parsing '/home/paulo/.gimp-2.8/gimprc'
  gimp_composite: verbose=no
  Processor instruction sets: +mmx +sse +sse2 -3dnow -altivec -vis
  Adding theme 'Default' (/usr/local/gimp/share/gimp/2.0/themes/Default)
  Adding theme 'Small' (/usr/local/gimp/share/gimp/2.0/themes/Small)
  Writing '/home/paulo/.gimp-2.8/themerc'
  Trying splash '/home/paulo/.gimp-2.8/gimp-splash.png' ... failed
  Trying splash '/usr/local/gimp/share/gimp/2.0/images/gimp-splash.png' ... OK
  INIT: gimp_initialize
  INIT: gimp_real_initialize
  INIT: gui_initialize_after_callback
  INIT: gimp_restore
  Parsing '/home/paulo/.gimp-2.8/parasiterc'
  Loading 'brush factory' data
  Loading 'dynamics factory' data
  Loading 'pattern factory' data
  Loading 'palette factory' data
  Loading 'gradient factory' data
  Loading fonts
  Loading 'tool preset factory' data
  Parsing '/home/paulo/.gimp-2.8/templaterc'
  Parsing '/home/paulo/.gimp-2.8/modulerc'
  INIT: gui_restore_callback
  clipboard: writable pixbuf format: image/png
  clipboard: writable pixbuf format: image/x-icon
  clipboard: writable pixbuf format: image/x-ico
  clipboard: writable pixbuf format: image/x-win-bitmap
  clipboard: writable pixbuf format: image/tiff
  clipboard: writable pixbuf format: image/bmp
  clipboard: writable pixbuf format: image/x-bmp
  clipboard: writable pixbuf format: image/x-MS-bmp
  clipboard: writable pixbuf format: image/jpeg
  Parsing '/home/paulo/.gimp-2.8/sessionrc'
  Parsing '/home/paulo/.gimp-2.8/dockrc'
  Parsing '/home/paulo/.gimp-2.8/toolrc'
  Parsing '/home/paulo/.gimp-2.8/contextrc'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-rect-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-ellipse-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-free-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-fuzzy-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-by-color-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-iscissors-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-foreground-select-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-vector-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-color-picker-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-zoom-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-measure-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-move-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-align-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-crop-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-rotate-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-scale-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-shear-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-perspective-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-flip-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-cage-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-text-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-bucket-fill-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-blend-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-pencil-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-paintbrush-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-eraser-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-airbrush-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-ink-tool'
  Parsing '/home/paulo/.gimp-2.8/tool-options/gimp-clone-tool'
  Parsing

[Desktop-packages] [Bug 1328003] Re: Update to 24.6.0

2014-06-19 Thread Chris Coulson

** Description changed:

- ...
+ http://www.ubuntu.com/usn/usn-2250-1/

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

Title:
  Update to 24.6.0

Status in “thunderbird” package in Ubuntu:
  Fix Released

Bug description:
  http://www.ubuntu.com/usn/usn-2250-1/

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

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

[Desktop-packages] [Bug 1329792] Re: gtkpopover widgets not rendered

This bug was fixed in the package ubuntu-themes -
14.04+14.10.20140619-0ubuntu1

---
ubuntu-themes (14.04+14.10.20140619-0ubuntu1) utopic; urgency=low

  [ Robert Ancell ]
  * Make ubuntu-mobile inherit from the Humanity / gnome themes. In the
Unity 8 desktop session some applications refer to icons in these
themes and this causes Unity 8 not to show an icon for them.

  [ Lars Uebernickel ]
  * Add preliminary support for popovers Add borders and shadow for the
.popover class. Also set the background color for the .background
class instead of on GtkWindow directly, because GtkPopover sets
.background as well. (LP: #1329792)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Thu, 19 Jun 2014 
09:07:31 +

** Changed in: ubuntu-themes (Ubuntu)
   Status: New = Fix Released

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

Title:
  gtkpopover widgets not rendered

Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “ubuntu-themes” package in Ubuntu:
  Fix Released

Bug description:
  After Utopic update to use gtk+ 3.12, GtkVolumeButton do not let to
  use volume pops up control. I can change volume only if mouse cursor
  is over volume icon and I use mouse scroll wheel.

  You can reproduce this in totem and rhythmbox by clicking in volume
  icon and try to move up or down volume control slider that show's up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1329792/+subscriptions

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

[Desktop-packages] [Bug 1331895] Re: nVidia GF119M [GeForce 705M][10de:105b] Xorg terminates when running hybrid suspend

2014-06-19 Thread Daniel Manrique

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

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

Title:
  nVidia GF119M [GeForce 705M][10de:105b] Xorg terminates when running
  hybrid suspend

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

Bug description:
  CID: 201301-12638 HP 110 Desktop

  Steps:
  1. Install 14.04 + update + proprietary nVidia driver
  2. hybrid suspend with sudo pm-suspend-hybrid
  3. Wake it up

  Expected results:
  * Every program that I opened before this hybrid suspend should be still there

  Actual result:
  * Xorg terminated and restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-29-generic 3.13.0-29.53
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3349 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 18 22:38:33 2014
  HibernationDevice: RESUME=UUID=276cb423-5fa1-4d04-a04f-a4263d200c53
  InstallationDate: Installed on 2014-06-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard TEST
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed 
root=UUID=3c74549d-d5eb-4d17-978c-a44c061c2cb6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-29-generic N/A
   linux-backports-modules-3.13.0-29-generic  N/A
   linux-firmware 1.127.2
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: 3.04
  dmi.board.name: 2AFB
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.02
  dmi.chassis.asset.tag: TBW1010026
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr3.04:bd12/14/2012:svnHewlett-Packard:pnTEST:pvr1.00:rvnPEGATRONCORPORATION:rn2AFB:rvr1.02:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: TEST
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates

2014-06-19 Thread Andrey

Thank you, David!
I installed blueman from your ppa (#75), reboot, and all works fine.
(Mint 17 (2014-03) Mate 32bit)

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

Title:
  [Bluetooth + 14.04] Bluetooth headsets are not working after last
  couple of updates

Status in Blueman - Bluetooth Manager:
  Confirmed
Status in “blueman” package in Ubuntu:
  Confirmed
Status in “gnome-bluetooth” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I found a bug in Ubuntu 14.04 !

  I tried to pair a bluetooth stereo headset (A2DP compatible). The
  pairing process goes well, but after that I can't select it on the
  audio preferences.

  When I select it, it only shows the last selected item options and don't do 
anything. (he should switch to the headset output).
  I must mention that it worked very well on Ubuntu 12.04.

  This bug can be in the bluetooth stack or in unity-control-center or
  maybe pulseaudio. I actually have no idea.

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

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

[Desktop-packages] [Bug 1328003] Re: Update to 24.6.0

@alexander-buchner: The update has been pushed to the 14.04
repositories. If you are interested, you can subscribe to the trusty-
changes mailing list to get notifications by e-mail.

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

Title:
  Update to 24.6.0

Status in “thunderbird” package in Ubuntu:
  Fix Released

Bug description:
  http://www.ubuntu.com/usn/usn-2250-1/

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

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

[Desktop-packages] [Bug 874268] Re: system-config-printer not reachable in menus of GNOME shell

2014-06-19 Thread Paál , Balázs

Ubuntu 14.04 gnome affected

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

Title:
  system-config-printer not reachable in menus of GNOME shell

Status in “system-config-printer” package in Ubuntu:
  Confirmed
Status in Baltix GNU/Linux:
  New

Bug description:
  /usr/share/applications/system-config-printer.desktop has the hidden
  option enabled, which prevents users from locating the tool from
  within GNOME 3, now that the System menu is gone as of GNOME 3.2. It
  needs to be enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: system-config-printer-gnome 1.3.6+20110831-0ubuntu9 [modified: 
usr/share/applications/system-config-printer.desktop]
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CupsErrorLog:
   W [14/Oct/2011:01:57:44 +0300] failed to AddProfile: 
org.freedesktop.ColorManager.Failed:profile object path 
'/org/freedesktop/ColorManager/profiles/PDF_Gray__' has already been added
   W [14/Oct/2011:01:57:44 +0300] failed to AddProfile: 
org.freedesktop.ColorManager.Failed:profile object path 
'/org/freedesktop/ColorManager/profiles/PDF_RGB__' has already been added
  Date: Fri Oct 14 17:14:54 2011
  Lpstat: device for PDF: cups-pdf:/
  MachineType: Dell Inc. Latitude D430
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: PDF: Generic CUPS-PDF Printer
  ProcEnviron:
   LANGUAGE=fi:en
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic 
root=UUID=cd9a1998-9fb2-4208-aba6-bc2ba8f5e36a ro panic=15 quiet splash 
vt.handoff=7
  SourcePackage: system-config-printer
  UdevDb: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 07
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd06/20/2007:svnDellInc.:pnLatitudeD430:pvr:rvnDellInc.:rn07:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D430
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/874268/+subscriptions

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

[Desktop-packages] [Bug 1095534] Re: Remmina remote desktop client goes fullscreen on the wrong display

2014-06-19 Thread Noah Putman

It's been this way for years in xubuntu. I have a triple-head setup at
work and at home with AMD graphics cards and I can never get it to go
fullscreen on the center monitor. It works fine on the left and the
right, but when I hit fullscreen when it's in the middle, it jumps to
the right.

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

Title:
  Remmina remote desktop client goes fullscreen on the wrong display

Status in “remmina” package in Ubuntu:
  Confirmed

Bug description:
  When the fullscreen button on the toolbar is used with multiple
  displays enabled, Remmina maximizes on a random display rather than on
  the display where it is placed.

  To replicate on a computer with multiple displays:

  1. Launch Remmina.
  2. Connect to a computer using RDP protocol.
  3. Click the full screen button.

  The application flips over to the other display and goes full screen.

  4. Restore the application.
  5. Drag it back to the display where you want it.
  6. Click the full screen button again.

  The application flips over to the other display and goes full screen.

  The expectation is that the application should stay on the display
  where I put it or it should offer an option to allow me to specify the
  screen I want it on.

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

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

[Desktop-packages] [Bug 1160434] Re: firefox needs porting for aarch64

2014-06-19 Thread Riku Voipio

Supposedly Released in Firefox 30 - thanks to tireless work from Marcin!

** Changed in: linaro-aarch64
   Status: Fix Committed = Fix Released

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

Title:
  firefox needs porting for aarch64

Status in Linaro AArch64 cross-distro work:
  Fix Released
Status in “firefox” package in Ubuntu:
  New
Status in “xulrunner” package in Fedora:
  Unknown

Bug description:
   configure: error: libffi has not been ported to aarch64-unknown-linux-gnu.
   configure: error: 
/home/abuild/rpmbuild/BUILD/mozilla/js/src/ctypes/libffi/configure failed for 
ctypes/libffi
   configure: error: /home/abuild/rpmbuild/BUILD/mozilla/js/src/configure 
failed for js/src
   *** Fix above errors and then restart with   make -f client.mk 
build

  it seems to have an embedded and patched copy of libffi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1160434/+subscriptions

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

[Desktop-packages] [Bug 501601] Re: Bash in gnome-terminal shows control characters as unsupported-unicode squares

2014-06-19 Thread Douglas Bagnall

The annoying thing for me is not that these characters are represented,
but that they ignore the character grid. If I run,

for x in `seq 1 31`;do echo -e $x-\\x$(printf %x $x)=;done

it should print the character code, followed by a minus, followed by a
representation of the character code, followed by an equals sign --
except when the character code tells the cursor to jump around or delete
stuff.

On the linux console, and in plain old xterm, the non-moving characters
print are invisible and take up no space.

In xfce4-terminal, they print as little squares but stay within their
assigned box.

In gnome terminal, as in the attached picture, they encroach over the
following character, so that you can't read it.

This is annoying, because it means you can't look at files that e.g. use
the field separator codes (28-31) as field separators.

** Attachment added: Image showing many control characters misbehaving

https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/501601/+attachment/4134902/+files/gnome-terminal.png

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

Title:
Bash in gnome-terminal shows control characters as unsupported-unicode
squares

Status in “gnome-terminal” package in Ubuntu:
Incomplete

Bug description:
Binary package hint: gnome-terminal

When I upgraded to Karmic (clean install) I noticed bash echoes
control characters using the hat notation (ex. ctrl+c shows as ^C).
stty reported echoctl being set, so I tried to unset it. This helped,
and pressing ctrl+c at a prompt cancels the prompt, shows a new one
and nothing is echoed.

Though, when pressing ctrl+c while a program is running (ex. cat or
ping), a unicode square is echoed like for unicode characters not
supported by the selected font. I tried selecting many different
encodings and fonts, though nothing seemed to help.

Futher, if inside this same shell I open a screen session, this
behaviour is gone and everything works as intended, which is to have
ctrl+c or ctrl+z have the desired effect with nothing echoed.

Finally, opening a bash session in xterm or tty[1-6] and disabling
echoctl/ctrlecho using stty command, this cannot be reproduced. So it
seems that only an plain bash session in gnome-terminal does this.

To see a screenshot, view the attached PNG.
Basically what happens there is
1. 2 ctrl+c presses at the prompt.
2. Then 1 ctrl+c during cat
3. Then 1 ctrl+z during cat
4. Bring cat back to the foreground and press ctrl+c again
THEN disable echoctl
5. Repeat the process - where you can now see instead of hat notation, the
prompt presses are fine, but the in-program presses echo unicode squares.

Very frustrating.

ProblemType: Bug
Architecture: i386
Date: Wed Dec 30 12:40:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-terminal
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
NonfreeKernelModules: fglrx
Package: gnome-terminal 2.28.1-0ubuntu1
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: gnome-terminal
Uname: Linux 2.6.31-16-generic i686

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

straight from the log: Kernel Module is not loaded

Please make sure the relevant kernel headers are installed and that the
nvidia dkms module is built.

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “nvidia-prime” package in Ubuntu:
  New
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  In Progress

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1288747] Re: [334] Parts of the UI randomly flicker when moving the mouse

2014-06-19 Thread Christopher Townsend

For those experiencing freezes, I have made some new packages that might
help this out.  They are currently built for Trusty and Utopic and I'm
working on updating the Precise package.  Please report back to let me
know if this helps out or not.

Thanks!

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

Title:
  [334] Parts of the UI randomly flicker when moving the mouse

Status in Compiz:
  Triaged
Status in “compiz” package in Ubuntu:
  Triaged

Bug description:
  Nvidia 334.21 makes the UI jearky, googled and found this on Nvidia
  forums:

  This looks like a problem caused by the system compositor not
  properly waiting for X rendering to finish before performing OpenGL
  rendering in response. The GL_EXT_x11_sync_object extension was
  designed to solve this problem, but it looks like cogl (the back-end
  library used by GNOME's compositor) doesn't use it yet. 

  more details:
  
https://devtalk.nvidia.com/default/topic/690704/linux/-334-16-parts-of-the-ui-randomly-flicker-when-moving-the-mouse/post/4128101/#4128101
  --- 
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É uma directoria: 
u'/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-16ubuntu6)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-16-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   nvidia-331-updates, 331.38, 3.13.0-16-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:34fe]
  InstallationDate: Installed on 2014-03-03 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=d2c3632d-4280-4961-91c8-0b7d3fe95be1 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Tags:  trusty trusty possible-manual-nvidia-install ubuntu single-occurrence 
reproducible compiz-0.9
  Uname: Linux 3.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0620
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-ASUS-SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0620:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-ASUS-SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11+14.04.20140305-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~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  7 10:50:58 2014
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6

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

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

[Desktop-packages] [Bug 1327624] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher produces unexpected results

2014-06-19 Thread Doug McMahon

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

** This bug has been marked a duplicate of bug 1328615
   [regression] Activation state is not passed anymore to compiz plugins

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

Title:
  Launcher, Window management - Dragging and holding a selection over an
  entry in the Launcher produces unexpected results

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

Bug description:
  according to Bug 607796 (fix released) this should initiate a spread.
  Test case:
  Open 3 nautilus windows
  Grab a folder from one, drag  hover over Files launcher icon

  What happens:
  either nothing or goes to some weird sort of semi-spread 
  If nothing then repeat a few times
  In the case of later while hovering you'll notice a slight change in at least 
1 nautilus window, the shadow will increase
  Return dragged file to orig folder  windows are in some strange state, see 
screen for the look

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: compiz 1:0.9.11+14.10.20140606-0ubuntu1
  ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
  Uname: Linux 3.15.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Jun  7 17:47:24 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2014-05-28 (10 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  MachineType: LENOVO 20217
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-5-generic.efi.signed 
root=UUID=a6d824a1-9cb2-4aad-9241-7b563a3dbdd0 ro quiet splash
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.10.20140606-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: Sat Jun  7 17:41:22 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 729 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu5

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

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

[Desktop-packages] [Bug 1302770] Re: keymap unstable

2014-06-19 Thread marmuta

You could probably set it in xorg.conf.d, but I wish there was a better
solution. This problem keeps coming up, infrequently, but persistently
over the years.

OK, let's see. The indicator in unity panel writes to gsettings.
gsettings monitor org.gnome.desktop.input-sources current 

Unity-settings-daemon listens for this key's changes and in response sets the 
root window property _XKB_RULES_NAMES. As I understand it, that's basically 
what setxkbmap does too.
xprop -root | grep XKB

However, unity-settings-daemon seems to always add the us layout as a second 
group, something setxkbmap it,us would do.
setxkbmap -query | grep layout
layout: it,us

I don't know why that happens. There's probably a good reason for it,
but I could imagine this is what exposes you to the old bug #837456.

** Also affects: unity-settings-daemon
   Importance: Undecided
   Status: New

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

Title:
  keymap unstable

Status in Unity Settings Daemon:
  New
Status in “onboard” package in Ubuntu:
  Confirmed

Bug description:
  on a tablet pc, once the keyboard has been deactivate, if I try to
  reactivate the keymapping don't load my language, but the American.
  The same after using Onboard keyboard on screen, the real ones changed
  the map.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1302770/+subscriptions

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

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

** Changed in: nvidia-prime (Ubuntu)
   Status: New = In Progress

** Changed in: nvidia-prime (Ubuntu)
   Importance: Undecided = Medium

** Changed in: nvidia-prime (Ubuntu)
 Assignee: (unassigned) = Alberto Milone (albertomilone)

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

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “nvidia-prime” package in Ubuntu:
  In Progress
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  In Progress

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2014-06-19 Thread Chris

Sadly I've disable the unity switcher and fall back to application
switcher also experiencing the same error. It is not only Unity switcher
causing the issue. :(

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

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

Status in “compiz” package in Ubuntu:
  Confirmed

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

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

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

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

[Desktop-packages] [Bug 1326780] Re: totem crashed with SIGSEGV in GI_pthread_mutex_lock()

2014-06-19 Thread Sebastien Bacher

** Information type changed from Private to Public

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

Title:
  totem crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in “totem” package in Ubuntu:
  Invalid

Bug description:
  Test case:
  Install grilo-plugins
  Open Videos  View  Search
  Leave on default of 'Youtube'
  Type in a search term, press enter on keyboard

  Test case 2:
  Same as above but in 'View' choose Browse
  Try to browse some Youtube categories

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: totem 3.10.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
  Uname: Linux 3.15.0-5-generic x86_64
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun  5 08:51:21 2014
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2014-05-28 (7 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  ProcCmdline: totem
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc126393414 __GI___pthread_mutex_lock+4:  mov
0x10(%rdi),%esi
   PC (0x7fc126393414) ok
   source 0x10(%rdi) (0x0010) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   __GI___pthread_mutex_lock (mutex=0x170e2) at ../nptl/pthread_mutex_lock.c:66
   ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.28
   ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.28
   ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.28
   ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26
  Title: totem crashed with SIGSEGV in __GI___pthread_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

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

2014-06-19 Thread heikki

This bug really seems to be random. My version of this bug really did disappear 
a month ago with description I gave earlier. I promise to you if this bug ever 
comes back to me I will do my best to nail it for good! It was really annoying. 
1306550 Never forget!

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

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

Status in “compiz” package in Ubuntu:
  Confirmed

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

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

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

To manage

[Desktop-packages] [Bug 1231916] Re: AMD A6-5400k APU with Radeon HD 8600 - Failed to start X after Installation

2014-06-19 Thread Anthony Wong

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) = Timo Aaltonen (tjaalton)

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

Title:
  AMD A6-5400k APU with Radeon HD 8600 - Failed to start X after
  Installation

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

Bug description:
  On this hardware system, user can only see graphic installer using
  UEFI mode, in the other hand legacy mode can only see black screen
  during when booting installer.

  After installation successfully by using UEFI mode, it can't boot into
  X desktop.

  It's blocking user to use jockey-gtk to install fglrx driver.

  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.4
  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
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  DkmsStatus: fglrx-updates, 12.104, 3.8.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7540D] [1002:9991] 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:2af6]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8750M] 
[1002:6600] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:2af6]
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  JockeyStatus:
   xorg:fglrx_experimental_13 - ATI/AMD proprietary FGLRX graphics driver 
(**experimental** beta) (Proprietary, Disabled, Not in use)
   xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release 
updates) (Proprietary, Enabled, Not in use)
  MachineType: Hewlett-Packard DVT-ys002
  MarkForUpload: True
  NonfreeKernelModules: fglrx
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic.efi.signed 
root=UUID=600f7c05-868f-479d-80a1-a96c33ce8ca5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6
  Tags:  precise running-unity ubuntu referred-by-support compiz-0.9
  Uname: Linux 3.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 3.13H
  dmi.board.asset.tag: 4CS247000Z
  dmi.board.name: 2AF6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 011
  dmi.chassis.asset.tag: 4CS247000Z
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr3.13H:bd01/07/2013:svnHewlett-Packard:pnDVT-ys002:pvr:rvnHewlett-Packard:rn2AF6:rvr011:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: DVT-ys002
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.12-0ubuntu2
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Desktop-packages] [Bug 1330118] Re: Software-center isn't able to deal with root priviledge (which are mandatory to install a software, may I recall…)

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

** This bug has been marked a duplicate of bug 1315541
   Software-center does not ask for root password when needed.

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

Title:
  Software-center isn't able to deal with root priviledge (which are
  mandatory to install a software, may I recall…)

Status in “software-center” package in Ubuntu:
  New

Bug description:
  I have already reported this, but as it's still not working, I guess no one 
reads the bugs there… great.
  Here is the usual problem: I download a package from the Internet, typically 
Google-talk's plugin.
  It's a package, I double click on it and software-center launches itself.  I 
ask to install/upgrade the software… and I'm facing an *error* saying that I 
have no priviledge to install this application.  This error is a stupid error 
from dpkg saying “I'm not run as root!”.
  Is that so complex to ask for the root password before installing something 
and running dpkg?!?
  Martin, as usual very impressed by how “easy” it is to use Ubuntu rather than 
any serious Debian system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 14 21:52:41 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-31 (864 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: software-center
  UpgradeStatus: Upgraded to trusty on 2014-05-01 (43 days ago)

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

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

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

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

** Also affects: compiz (Ubuntu Trusty)
   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/1304531

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1331812] Re: Stickykeys disabled on reboot

** Changed in: unity-control-center (Ubuntu)
   Importance: Undecided = High

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

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

Title:
  Stickykeys disabled on reboot

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

Bug description:
  I turn on Universal Access  Typing  Sticky Keys

  Works fine until I reboot, then it stops working (but is still
  selected in Universal Access  Typing).

  Turning it off then back on in Universal Access  Typing fixes it.

  New bug in 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 19 09:04:29 2014
  InstallationDate: Installed on 2012-06-18 (730 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-04-20 (59 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56.1

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

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

[Desktop-packages] [Bug 1087090] Re: [raring][regression] Window management - Maximized windows aren't fullscreen in the workspace switcher

** Also affects: compiz (Ubuntu Trusty)
   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/1087090

Title:
  [raring][regression] Window management - Maximized windows aren't
  fullscreen in the workspace switcher

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Having a maximized window in Expo mode has kind of a jarring effect
  with a blank space where the Launcher and Panel should be.  This leads
  to poor visual experience for users.

  [Test case]

  1. Make sure workspaces are enabled.
  2. Open a window and make sure it's maximized.
  3. Initiate Expo by hitting Super+S.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Hello,

  Since today's updates of compiz, the workspace switcher don't work the
  same way as before. When you have a maximized windows and you click on
  the launcher's workspace icon, the workspace switcher appears but the
  maximized windows aren't fullscreened. You can see the voids that
  represent the launcher and the panel.

  I attached a screenshot for a better understanding of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1087090/+subscriptions

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

[Desktop-packages] [Bug 347390] Re: Compiz can't resize a window vertically AND horizontally with keyboard.

** Also affects: compiz (Ubuntu Trusty)
   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/347390

Title:
  Compiz can't resize a window vertically AND horizontally with
  keyboard.

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  New

Bug description:
  [Impact]

  Some users like to use the keyboard for many functions including
  resizing windows.  Due to this bug, resizing windows with the keyboard
  is not very easy.

  [Test case]

  1. Open a window such as gedit.  Make sure it is not maximized.
  2. Initiate keyboard resizing by hitting Alt+Space, then r.
  3. Use cursor keys to resize the window.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  when trying to resize a window using the keyboard (ALT+SPACE, then
  choose resize from the menu and then use the keyboard arrows) its not
  possible to resize both horizontally and vertically - like its
  possible using the mouse by grabbing a window corner.

  Normally one would expect that its possible to press the right arrow
  key repeatedly to enlarge the window horizontally, and then press the
  down arrow key repeatedly to enlarge the window vertically, before
  pressing ENTER to submit the changes

  What actually happens is that once the second button is pressed (down in this 
case), the previous dimension (horizontal) reverts to is old size and the new 
dimension is being adjusted. Try to press right arrow and the vertical 
dimension reverts back to its old value. In order to successfully resize a 
window both vertically and horizontally one needs to:
  1. start a resize action
  2. resize in one direction
  3. submit the changes
  4. start another resize action
  5. resize in the other direction
  6. submit the changes

  Making it twice as complicated to do. This may or may not be related
  to desktop effects being enabled, I haven't disabled them to check yet
  but I do not remember this being a problem with standard Metacity.

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

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

[Desktop-packages] [Bug 626064] Re: onboard: add haptic feedback

** Changed in: onboard (Ubuntu)
   Importance: Low = Wishlist

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

Title:
  onboard: add haptic feedback

Status in Onboard on-screen keyboard:
  Confirmed
Status in Ubuntu on modern Smartphones:
  New
Status in “onboard” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: onboard

  I am using onboard as input method on a phone with capacitive touchscreen. 
Since these touchscreens are not very precise it is good to get a firm feedback 
from the device to know a button was pressed. In windows mobile (stock 
operating system on this device), a very short vibration pulse will be 
triggered each time a button on the included on screen keyboard is pressed.
  In Linux vibration is triggered by writing the vibration duration in ms to a 
sysfs node on the device. 
  E.g. this could be inserted where the button will change color on press.
  As there are other mechanism like LED or whatever else is available on other 
devices to think of it would be nice to make this dynamic. E.g. add an input 
field where the user can put a command to execute on button press.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: onboard 0.93.2-0ubuntu1
  Uname: Linux 2.6.32.9-38168-g65aefba-dirty armv7l
  Architecture: armel
  Date: Mon Jan 11 13:45:41 2010
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: onboard

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

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

[Desktop-packages] [Bug 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

** Also affects: compiz (Ubuntu Trusty)
   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/1063617

Title:
  1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
  wrong values

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users set custom shortcuts in Compiz for various functionality.
  When this issue hits, many, if not all, of these custom shortcuts get
  reset to the defaults which can cause much frustration in the user.
  It is a very bad user experience.

  [Test case]

  1. Open CCSM
  2. Set a custom shortcut or change a behavior.  For example, go to General 
Options-Focus  Raise Behavior and uncheck Click To Focus.
  3. Restart the Unity session multiple times.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  NOTE: This bug is for Ubuntu 12.10 and later only. If you experience
  something similar in 12.04 then please see bug 964270.

  ORIGINAL DESCRIPTION:
  Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my 
gsettings (keybindings and WM prefs). This was already covered in bug 1042041, 
but the change there mostly caused the bug to happen consistently now.

  At every session startup I have a script to fix my settings like this:

  --- 8 
  gsettings reset org.gnome.desktop.wm.preferences auto-raise
  gsettings set org.gnome.desktop.wm.keybindings lower ['Altb']
  gsettings set org.gnome.desktop.wm.keybindings maximize ['SuperUp']
  gsettings set org.gnome.desktop.wm.keybindings unmaximize ['SuperDown']
  gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
  --- 8 

  But after restarting compiz, it changes the settings to:

  --- 8 
  $ gsettings get org.gnome.desktop.wm.preferences auto-raise
  true
  $ gsettings get org.gnome.desktop.wm.keybindings lower
  ['disabled']
  $ gsettings get org.gnome.desktop.wm.keybindings maximize
  ['ControlPrimarySuperUp']
  $ gsettings get org.gnome.desktop.wm.keybindings unmaximize
  ['ControlPrimarySuperDown']
  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'click'
  --- 8 

  I tried to move away /usr/bin/session-migration, that does not change
  anything, so it's not that script.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu1
  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 Oct  8 10:23:04 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:215a]
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627)
  MachineType: LENOVO 3323REG
  PackageArchitecture: all
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=8f327c01-56d7-401c-8bd1-5442854e3c85 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET46WW (1.16 )
  dmi.board.name: 3323REG
  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:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3323REG:pvrThinkPadX201:rvnLENOVO:rn3323REG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3323REG
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A

[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card

This bug was fixed in the package nvidia-prime - 0.6.6

---
nvidia-prime (0.6.6) utopic; urgency=medium

  * prime-select:
- Simplify the logic for enablement. The simplified logic
  should also be more robust and try harder instead of
  complaining and aborting early (LP: #1310023).
  This is now possible thanks to the fact that we allow
  installing only one binary driver at the time. This is
  not the case in Ubuntu = 12.04.
 -- Alberto Milone alberto.mil...@canonical.com   Thu, 19 Jun 2014 15:48:06 
+0200

** Changed in: nvidia-prime (Ubuntu)
   Status: In Progress = 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/1310023

Title:
  14.04: Nvidia Prime is unable to switch to the Nvidia card

Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” source package in Trusty:
  In Progress

Bug description:
  SRU Request

  On some systems bbswitch requires the skip_optimus_dsm=1 option in
  order to load properly. So far we have dealt with this problem with
  system specific quirks based on DMI information. This some times gives
  us false positives or doesn't cover all systems (it's hard to quirk
  all systems). We should simply try with and without that option and
  use whatever works best for the system. This should cover all cases
  with no need for additional quirks.

  
  [Impact]
   * Loading bbswitch with the wrong option causes the module to fail from 
loading which, in turn, prevents hybrid graphics from working properly.

  [Test Case]
   * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is 
enabled (attach your /var/log/gpu-manager.log)
  - Expected: the NVIDIA GPU is enabled.
  - Bad behavior: the system switches back to the intel driver and the 
NVIDIA GPU is not used.

  [Regression Potential]
   * Low. Systems that currently work will keep working as usual, the ones that 
currently fail should finally work.

  [Other Info]
   * N/A

  --

  I did a fresh install of 14.04 the day it was released. I use a XPS 15z 
laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia 
Geforce GT 525M). Booting doesn't work out of the box, but by setting
  GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 
quiet splash
  in /etc/default/grub it works. acpi=off when installing, removed that from 
the grub file when installed.

  I expected that the Prime feature introduced in kernel 3.12 (kernel
  3.13.x here) would let me switch between the Intel and Nvidia cards as
  i like, instead of using Bumblebee, which doesn't work properly with
  everything. I've installed and tried both the nvidia-331 and
  nvidia-304 drivers. Exactly the same result from both.

  Attempting to switch to the Nvidia card in nvidia-settings (tried on almost 
all of the drivers available, including 331.38) resulted in an error message, 
in a new window, with no text.
  prime-switch in terminal gives this output: Segmentation fault (core dumped)
  Sudoing the process gives no output at all. No graphical performance boost 
either, still the Intel card...

  sudo prime-select nvidia gives this output:
  Error: alternatives are not set up properly
  Error: nvidia mode can't be enabled

  I've also tried Bumblebee (not PPA) a few times, but it's also unable
  to switch.

  I'm able to use the Intel card temporary, but I would really like to
  be able to use the full power of my computer...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime 0.6.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 19 20:52:42 2014
  InstallationDate: Installed on 2014-04-17 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1311303] Re: Compiz mouse functions mapped to horizontal scrolling buttons do not work

** Also affects: compiz (Ubuntu Trusty)
   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/1311303

Title:
  Compiz mouse functions mapped to horizontal scrolling buttons do not
  work

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Users who have the horizontal scroll button mapped to other functions
  using CCSM no longer have working mapped functions.  This breaks the
  user's workflow.

  [Test case]

  * Need a mouse with horizontal scrolling, ie, click the mouse wheel left and 
right.
  * Open CCSM.
  * Map a function to the horizontal scroll buttons, ie, buttons 6  7.  For 
example:
    * Enable workspaces.
    * CCSM-Viewport Switcher-Desktop-based Viewport Switching
    * Set Move Next to button 6 and Move Prev to button 7.

  [Regression potential]

  When a user has a function mapped to the horizontal scroll buttons,
  horizontal scrolling in windows that support horizontal scrolling will
  no longer work.  The user must recognize that when they map the
  function, they loose the original functionality.  This is the same
  case in previous versions of Ubuntu before this regression occurred,
  so no real regression potential.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  Running Ubuntu 14.04 and compiz 0.9.11.

  Upon upgrading to 14.04 I can no longer use mouse buttons to switch
  between desktops in the Desktop Wall when a maximised window is
  focussed. It works as expected when using keyboard functions, or when
  the desktop is focussed.

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

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

[Desktop-packages] [Bug 1325156] Re: Window controls looks inconsistent in Ubuntu 14.04

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

** Changed in: gnome-themes-standard (Ubuntu)
   Status: New = Confirmed

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

Title:
  Window controls and decorations looks inconsistent in Ubuntu 14.04

Status in “gnome-themes-standard” package in Ubuntu:
  Confirmed

Bug description:
  Adwaita is a nice theme, however the window controls look out of place
  in Ubuntu 14.04 which makes it look ugly.

  I have attached a screenshot.

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

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

[Desktop-packages] [Bug 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

Hello Martin, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
  wrong values

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users set custom shortcuts in Compiz for various functionality.
  When this issue hits, many, if not all, of these custom shortcuts get
  reset to the defaults which can cause much frustration in the user.
  It is a very bad user experience.

  [Test case]

  1. Open CCSM
  2. Set a custom shortcut or change a behavior.  For example, go to General 
Options-Focus  Raise Behavior and uncheck Click To Focus.
  3. Restart the Unity session multiple times.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  NOTE: This bug is for Ubuntu 12.10 and later only. If you experience
  something similar in 12.04 then please see bug 964270.

  ORIGINAL DESCRIPTION:
  Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my 
gsettings (keybindings and WM prefs). This was already covered in bug 1042041, 
but the change there mostly caused the bug to happen consistently now.

  At every session startup I have a script to fix my settings like this:

  --- 8 
  gsettings reset org.gnome.desktop.wm.preferences auto-raise
  gsettings set org.gnome.desktop.wm.keybindings lower ['Altb']
  gsettings set org.gnome.desktop.wm.keybindings maximize ['SuperUp']
  gsettings set org.gnome.desktop.wm.keybindings unmaximize ['SuperDown']
  gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
  --- 8 

  But after restarting compiz, it changes the settings to:

  --- 8 
  $ gsettings get org.gnome.desktop.wm.preferences auto-raise
  true
  $ gsettings get org.gnome.desktop.wm.keybindings lower
  ['disabled']
  $ gsettings get org.gnome.desktop.wm.keybindings maximize
  ['ControlPrimarySuperUp']
  $ gsettings get org.gnome.desktop.wm.keybindings unmaximize
  ['ControlPrimarySuperDown']
  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'click'
  --- 8 

  I tried to move away /usr/bin/session-migration, that does not change
  anything, so it's not that script.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu1
  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 Oct  8 10:23:04 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:215a]
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627)
  MachineType: LENOVO 3323REG
  PackageArchitecture: all
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

Hello Alfred, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: compiz (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

** Tags added: verification-needed

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some windows that open from within another window such as a Firefox
  popup window will be placed with the decorations under the Panel.
  Also, some windows will just open with the decoration under the Panel
  such as virt-manager.  This can cause confusion for the user on how to
  move the window and how to close it.  This can be very disruptive to a
  user's workflow.

  [Test case]

  1. Install virt-manager.
  2. Make sure no other windows are open.
  3. Start virt-manager.

  virt-manager should start in the top left.  With this fix, the
  decoration should be visible.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  TEMPORARY WORKAROUND:
  Use the Cntrl+SuperKey+Right or Left Arrow Key
  This will resize your currently focused window to occupy the Right (Left) 
half of the screen. The Title Bar should now be visible, so you need to drag it 
and resize it at your prefered position. This will save the new position in 
place of the previously hidden state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

Hello Christopher, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1087090] Re: [raring][regression] Window management - Maximized windows aren't fullscreen in the workspace switcher

Hello John, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  [raring][regression] Window management - Maximized windows aren't
  fullscreen in the workspace switcher

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Having a maximized window in Expo mode has kind of a jarring effect
  with a blank space where the Launcher and Panel should be.  This leads
  to poor visual experience for users.

  [Test case]

  1. Make sure workspaces are enabled.
  2. Open a window and make sure it's maximized.
  3. Initiate Expo by hitting Super+S.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Hello,

  Since today's updates of compiz, the workspace switcher don't work the
  same way as before. When you have a maximized windows and you click on
  the launcher's workspace icon, the workspace switcher appears but the
  maximized windows aren't fullscreened. You can see the voids that
  represent the launcher and the panel.

  I attached a screenshot for a better understanding of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1087090/+subscriptions

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

[Desktop-packages] [Bug 1325156] Re: Window controls and decorations looks inconsistent in Ubuntu 14.04

2014-06-19 Thread Fabio

The Adwaita theme has completely wrong decorations and control buttons.
This bug happens using Unity but not using Gnome Shell.. May it be a
problem with Compiz?

** Summary changed:

- Window controls looks inconsistent in Ubuntu 14.04
+ Window controls and decorations looks inconsistent in Ubuntu 14.04

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

Title:
  Window controls and decorations looks inconsistent in Ubuntu 14.04

Status in “gnome-themes-standard” package in Ubuntu:
  Confirmed

Bug description:
  Adwaita is a nice theme, however the window controls look out of place
  in Ubuntu 14.04 which makes it look ugly.

  I have attached a screenshot.

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

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

[Desktop-packages] [Bug 1311303] Re: Compiz mouse functions mapped to horizontal scrolling buttons do not work

Hello dominus_sapiens, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Compiz mouse functions mapped to horizontal scrolling buttons do not
  work

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Users who have the horizontal scroll button mapped to other functions
  using CCSM no longer have working mapped functions.  This breaks the
  user's workflow.

  [Test case]

  * Need a mouse with horizontal scrolling, ie, click the mouse wheel left and 
right.
  * Open CCSM.
  * Map a function to the horizontal scroll buttons, ie, buttons 6  7.  For 
example:
    * Enable workspaces.
    * CCSM-Viewport Switcher-Desktop-based Viewport Switching
    * Set Move Next to button 6 and Move Prev to button 7.

  [Regression potential]

  When a user has a function mapped to the horizontal scroll buttons,
  horizontal scrolling in windows that support horizontal scrolling will
  no longer work.  The user must recognize that when they map the
  function, they loose the original functionality.  This is the same
  case in previous versions of Ubuntu before this regression occurred,
  so no real regression potential.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  Running Ubuntu 14.04 and compiz 0.9.11.

  Upon upgrading to 14.04 I can no longer use mouse buttons to switch
  between desktops in the Desktop Wall when a maximised window is
  focussed. It works as expected when using keyboard functions, or when
  the desktop is focussed.

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

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

[Desktop-packages] [Bug 1332118] [NEW] Update to 0.9.6

2014-06-19 Thread Iain Lane

Public bug reported:

JFYI. I've merged this in my ppa:laney/arm for testing, will upload
soonish.

** Affects: folks (Ubuntu)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress


** Tags: upgrade-software-version

** Changed in: folks (Ubuntu)
   Status: New = In Progress

** Changed in: folks (Ubuntu)
 Assignee: (unassigned) = Iain Lane (laney)

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

Title:
  Update to 0.9.6

Status in “folks” package in Ubuntu:
  In Progress

Bug description:
  JFYI. I've merged this in my ppa:laney/arm for testing, will upload
  soonish.

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

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

[Desktop-packages] [Bug 347390] Re: Compiz can't resize a window vertically AND horizontally with keyboard.

Hello Oded, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Compiz can't resize a window vertically AND horizontally with
  keyboard.

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some users like to use the keyboard for many functions including
  resizing windows.  Due to this bug, resizing windows with the keyboard
  is not very easy.

  [Test case]

  1. Open a window such as gedit.  Make sure it is not maximized.
  2. Initiate keyboard resizing by hitting Alt+Space, then r.
  3. Use cursor keys to resize the window.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  when trying to resize a window using the keyboard (ALT+SPACE, then
  choose resize from the menu and then use the keyboard arrows) its not
  possible to resize both horizontally and vertically - like its
  possible using the mouse by grabbing a window corner.

  Normally one would expect that its possible to press the right arrow
  key repeatedly to enlarge the window horizontally, and then press the
  down arrow key repeatedly to enlarge the window vertically, before
  pressing ENTER to submit the changes

  What actually happens is that once the second button is pressed (down in this 
case), the previous dimension (horizontal) reverts to is old size and the new 
dimension is being adjusted. Try to press right arrow and the vertical 
dimension reverts back to its old value. In order to successfully resize a 
window both vertically and horizontally one needs to:
  1. start a resize action
  2. resize in one direction
  3. submit the changes
  4. start another resize action
  5. resize in the other direction
  6. submit the changes

  Making it twice as complicated to do. This may or may not be related
  to desktop effects being enabled, I haven't disabled them to check yet
  but I do not remember this being a problem with standard Metacity.

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1311303] Re: Compiz mouse functions mapped to horizontal scrolling buttons do not work

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  Compiz mouse functions mapped to horizontal scrolling buttons do not
  work

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Users who have the horizontal scroll button mapped to other functions
  using CCSM no longer have working mapped functions.  This breaks the
  user's workflow.

  [Test case]

  * Need a mouse with horizontal scrolling, ie, click the mouse wheel left and 
right.
  * Open CCSM.
  * Map a function to the horizontal scroll buttons, ie, buttons 6  7.  For 
example:
    * Enable workspaces.
    * CCSM-Viewport Switcher-Desktop-based Viewport Switching
    * Set Move Next to button 6 and Move Prev to button 7.

  [Regression potential]

  When a user has a function mapped to the horizontal scroll buttons,
  horizontal scrolling in windows that support horizontal scrolling will
  no longer work.  The user must recognize that when they map the
  function, they loose the original functionality.  This is the same
  case in previous versions of Ubuntu before this regression occurred,
  so no real regression potential.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  Running Ubuntu 14.04 and compiz 0.9.11.

  Upon upgrading to 14.04 I can no longer use mouse buttons to switch
  between desktops in the Desktop Wall when a maximised window is
  focussed. It works as expected when using keyboard functions, or when
  the desktop is focussed.

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

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

[Desktop-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab

Hello Iain, or anyone else affected,

Accepted compiz into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140617-0ubuntu1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: verification-needed

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

Title:
  Lock screen is unusable when some windows have a keyboard/mouse grab

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed
Status in “unity” source package in Trusty:
  New

Bug description:
  [Impact]

  Some windows will grab the keyboard/mouse and when the lockscreen
  kicks in, this window will still have the grab and thusly, ou can
  enter your password in the lockscreen.

  [Test case]

  1. Open a window that will hold the grab, such as the ssh password dialog.
  2. Wait for the lock screen to activate.
  3. Enter your password to unlock the screen.

  [Regression potential]

  This particular fix doesn't fix all cases, but does fix it for some.
  That said, no new regressions are expected.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  My screen just timed out and locked when a password prompt which had a
  grab was displaying.

  I couldn't type my password or interact with the indicators.

  gnome-screensaver just refuses to lock in this situation, perhaps
  unity could do the same unless it's possible to remove and readd the
  grabs yourself, but I don't think XLib lets you do that (you can only
  remove your own grabs AFAIK).

  TEMPORARY WORKAROUND TO LOGIN AGAIN:
  Click on the guest session
  Once the guest session is started log out
  This takes you back to the lightdm session screen you can then login to your 
user session and it be in the same state

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown]
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CrashDB: unity
  CurrentDesktop: Unity
  Date: Thu Apr 10 09:39:45 2014
  InstallationDate: Installed on 2012-10-07 (549 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago)

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

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

[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  [Regression] Window titlebars placed behind panel

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some windows that open from within another window such as a Firefox
  popup window will be placed with the decorations under the Panel.
  Also, some windows will just open with the decoration under the Panel
  such as virt-manager.  This can cause confusion for the user on how to
  move the window and how to close it.  This can be very disruptive to a
  user's workflow.

  [Test case]

  1. Install virt-manager.
  2. Make sure no other windows are open.
  3. Start virt-manager.

  virt-manager should start in the top left.  With this fix, the
  decoration should be visible.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Windows with a height of (Display Height - Panel Height) get placed at y=0 
(behind the top panel)
  which means window titlebars are not reachable without alt-moving the window.
  I assume this happens with windows that want to resize themselves if their 
height exceeds the display resolution.
  Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop 
application I'm working on.

  TEMPORARY WORKAROUND:
  Use the Cntrl+SuperKey+Right or Left Arrow Key
  This will resize your currently focused window to occupy the Right (Left) 
half of the screen. The Title Bar should now be visible, so you need to drag it 
and resize it at your prefered position. This will save the new position in 
place of the previously hidden state.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140403-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr  6 21:45:41 2014
  InstallationDate: Installed on 2014-04-04 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1087090] Re: [raring][regression] Window management - Maximized windows aren't fullscreen in the workspace switcher

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  [raring][regression] Window management - Maximized windows aren't
  fullscreen in the workspace switcher

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Having a maximized window in Expo mode has kind of a jarring effect
  with a blank space where the Launcher and Panel should be.  This leads
  to poor visual experience for users.

  [Test case]

  1. Make sure workspaces are enabled.
  2. Open a window and make sure it's maximized.
  3. Initiate Expo by hitting Super+S.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original description:

  Hello,

  Since today's updates of compiz, the workspace switcher don't work the
  same way as before. When you have a maximized windows and you click on
  the launcher's workspace icon, the workspace switcher appears but the
  maximized windows aren't fullscreened. You can see the voids that
  represent the launcher and the panel.

  I attached a screenshot for a better understanding of the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1087090/+subscriptions

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

[Desktop-packages] [Bug 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to
  wrong values

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users set custom shortcuts in Compiz for various functionality.
  When this issue hits, many, if not all, of these custom shortcuts get
  reset to the defaults which can cause much frustration in the user.
  It is a very bad user experience.

  [Test case]

  1. Open CCSM
  2. Set a custom shortcut or change a behavior.  For example, go to General 
Options-Focus  Raise Behavior and uncheck Click To Focus.
  3. Restart the Unity session multiple times.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  NOTE: This bug is for Ubuntu 12.10 and later only. If you experience
  something similar in 12.04 then please see bug 964270.

  ORIGINAL DESCRIPTION:
  Since version 1:0.9.8+bzr3319-0ubuntu1, compiz/unity keeps messing up my 
gsettings (keybindings and WM prefs). This was already covered in bug 1042041, 
but the change there mostly caused the bug to happen consistently now.

  At every session startup I have a script to fix my settings like this:

  --- 8 
  gsettings reset org.gnome.desktop.wm.preferences auto-raise
  gsettings set org.gnome.desktop.wm.keybindings lower ['Altb']
  gsettings set org.gnome.desktop.wm.keybindings maximize ['SuperUp']
  gsettings set org.gnome.desktop.wm.keybindings unmaximize ['SuperDown']
  gsettings set org.gnome.desktop.wm.preferences focus-mode sloppy
  --- 8 

  But after restarting compiz, it changes the settings to:

  --- 8 
  $ gsettings get org.gnome.desktop.wm.preferences auto-raise
  true
  $ gsettings get org.gnome.desktop.wm.keybindings lower
  ['disabled']
  $ gsettings get org.gnome.desktop.wm.keybindings maximize
  ['ControlPrimarySuperUp']
  $ gsettings get org.gnome.desktop.wm.keybindings unmaximize
  ['ControlPrimarySuperDown']
  $ gsettings get org.gnome.desktop.wm.preferences focus-mode
  'click'
  --- 8 

  I tried to move away /usr/bin/session-migration, that does not change
  anything, so it's not that script.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: compiz 1:0.9.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.6.1-0ubuntu1
  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 Oct  8 10:23:04 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:215a]
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120627)
  MachineType: LENOVO 3323REG
  PackageArchitecture: all
  PlymouthDebug: Error: [Errno 13] Keine Berechtigung: 
'/var/log/plymouth-debug.log'
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=8f327c01-56d7-401c-8bd1-5442854e3c85 ro quiet splash vt.handoff=7
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET46WW (1.16 )
  dmi.board.name: 3323REG
  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:bvr6QET46WW(1.16):bd06/07/2010:svnLENOVO:pn3323REG:pvrThinkPadX201:rvnLENOVO:rn3323REG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3323REG
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.8.4-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx

[Desktop-packages] [Bug 347390] Re: Compiz can't resize a window vertically AND horizontally with keyboard.

** Branch linked: lp:ubuntu/trusty-proposed/compiz

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

Title:
  Compiz can't resize a window vertically AND horizontally with
  keyboard.

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Some users like to use the keyboard for many functions including
  resizing windows.  Due to this bug, resizing windows with the keyboard
  is not very easy.

  [Test case]

  1. Open a window such as gedit.  Make sure it is not maximized.
  2. Initiate keyboard resizing by hitting Alt+Space, then r.
  3. Use cursor keys to resize the window.

  [Regression potential]

  None identified.

  * Debdiff is found at
  https://bugs.launchpad.net/compiz/+bug/1303462/+attachment/4134214/+files
  /compiz-trusty-sru.debdiff *

  Original Description:

  when trying to resize a window using the keyboard (ALT+SPACE, then
  choose resize from the menu and then use the keyboard arrows) its not
  possible to resize both horizontally and vertically - like its
  possible using the mouse by grabbing a window corner.

  Normally one would expect that its possible to press the right arrow
  key repeatedly to enlarge the window horizontally, and then press the
  down arrow key repeatedly to enlarge the window vertically, before
  pressing ENTER to submit the changes

  What actually happens is that once the second button is pressed (down in this 
case), the previous dimension (horizontal) reverts to is old size and the new 
dimension is being adjusted. Try to press right arrow and the vertical 
dimension reverts back to its old value. In order to successfully resize a 
window both vertically and horizontally one needs to:
  1. start a resize action
  2. resize in one direction
  3. submit the changes
  4. start another resize action
  5. resize in the other direction
  6. submit the changes

  Making it twice as complicated to do. This may or may not be related
  to desktop effects being enabled, I haven't disabled them to check yet
  but I do not remember this being a problem with standard Metacity.

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

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

[Desktop-packages] [Bug 1330198] Re: Regression: rev 3862 causes no scrolling on an unfocused gtk3 window with usb mouse

2014-06-19 Thread Christopher Townsend

** Changed in: compiz (Ubuntu)
   Status: New = In Progress

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

** Changed in: compiz
   Status: New = In Progress

** Changed in: compiz
   Importance: Undecided = Medium

** Changed in: compiz
 Assignee: (unassigned) = Christopher Townsend (townsend)

** Changed in: compiz
Milestone: None = 0.9.12.0

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

Title:
  Regression: rev 3862 causes no scrolling on an unfocused gtk3 window
  with usb mouse

Status in Compiz:
  In Progress
Status in “compiz” package in Ubuntu:
  In Progress

Bug description:
  Was fixed/working in compiz (1:0.9.11+14.04.20140423-0ubuntu1, broken
  in compiz (1:0.9.11+14.10.20140606-0ubuntu1 (revision 3862

  Test case: (here
  Have a laptop with usb mouse
  Open 2 scroll-able nautilus or gedit windows
  Mouse over  try to scroll in the unfocused window

  What happens: nothing

  Do not have a desktop machine to see if it affects usb mouse there

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: compiz 1:0.9.11+14.10.20140606-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
  Uname: Linux 3.15.0-5-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.3-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jun 15 10:18:29 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
   NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Lenovo Device [17aa:3801]
  InstallationDate: Installed on 2014-05-28 (17 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  MachineType: LENOVO 20217
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-5-generic.efi.signed 
root=UUID=a6d824a1-9cb2-4aad-9241-7b563a3dbdd0 ro quiet splash
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 74CN44WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIQY0Y1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y510P
  dmi.modalias: 
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
  dmi.product.name: 20217
  dmi.product.version: Lenovo IdeaPad Y510P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2
  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: Sun Jun 15 10:17:47 2014
  xserver.configfile: default
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0)
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 729
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu5

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

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

[Desktop-packages] [Bug 881526] Re: System freezes, kernel crashes, [fglrx] ASIC hang happened

2014-06-19 Thread Anthony Wong

** Changed in: fglrx-installer (Ubuntu)
 Assignee: James M. Leddy (jm-leddy) = (unassigned)

** Changed in: hwe-next
 Assignee: James M. Leddy (jm-leddy) = (unassigned)

** Changed in: hwe-next
   Status: Fix Committed = Won't Fix

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

Title:
  System freezes, kernel crashes, [fglrx] ASIC hang happened

Status in amd:
  Fix Released
Status in AMD fglrx video driver:
  Won't Fix
Status in HWE Next Project:
  Won't Fix
Status in OEM Priority Project:
  Invalid
Status in “fglrx-installer” package in Ubuntu:
  Confirmed
Status in “fglrx-installer-updates” package in Ubuntu:
  Confirmed

Bug description:
  The system freezes intermittently and the kernel crashes a few seconds
  later. This has only happened since upgrading to 11.10. Found the
  following error in /var/log/kern.log which coincides:

  Oct 25 14:53:46 lt9630 kernel: [  737.900416] INFO: rcu_sched_state detected 
stall on CPU 2 (t=15000 jiffies)
  Oct 25 14:55:46 lt9630 kernel: [  857.813946] [fglrx] ASIC hang happened
  Oct 25 14:55:46 lt9630 kernel: [  857.813950] Pid: 1149, comm: Xorg Tainted: 
P C  3.0.0-12-generic #20-Ubuntu
  Oct 25 14:55:46 lt9630 kernel: [  857.813951] Call Trace:
  Oct 25 14:55:46 lt9630 kernel: [  857.813985]  [a00a0d7e] 
KCL_DEBUG_OsDump+0xe/0x10 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814003]  [a00ae20c] 
firegl_hardwareHangRecovery+0x1c/0x50 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814036]  [a013ad59] ? 
_ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814068]  [a013ad0c] ? 
_ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814099]  [a0135fb4] ? 
_ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$
  Oct 25 14:55:46 lt9630 kernel: [  857.814127]  [a0115acb] ? 
_ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814158]  [a0135e7b] ? 
_ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814187]  [a012e8f1] ? 
_ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814215]  [a0119d8a] ? 
_ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814243]  [a01233f5] ? 
_Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814246]  [810871ee] ? 
down+0x2e/0x50
  Oct 25 14:55:46 lt9630 kernel: [  857.814266]  [a00cc932] ? 
firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814285]  [a00cb260] ? 
firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814288]  [81282e5a] ? 
security_capable+0x2a/0x30
  Oct 25 14:55:46 lt9630 kernel: [  857.814306]  [a00cb1f0] ? 
firegl_cmmqs_createdriver+0x170/0x170 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814322]  [a00a9e18] ? 
firegl_ioctl+0x1e8/0x250 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814333]  [a009a9be] ? 
ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814335]  [8117939a] ? 
do_vfs_ioctl+0x8a/0x340
  Oct 25 14:55:46 lt9630 kernel: [  857.814338]  [811679ed] ? 
vfs_read+0x10d/0x180
  Oct 25 14:55:46 lt9630 kernel: [  857.814339]  [811796e1] ? 
sys_ioctl+0x91/0xa0
  Oct 25 14:55:46 lt9630 kernel: [  857.814342]  [815f22c2] ? 
system_call_fastpath+0x16/0x1b
  Oct 25 14:55:46 lt9630 kernel: [  857.814345] pubdev:0xa02fd600, num 
of device:1 , name:fglrx, major 8, minor 88.
  Oct 25 14:55:46 lt9630 kernel: [  857.814346] device 0 : 0x88019b85 .

  Oct 25 14:55:46 lt9630 kernel: [  857.814345] pubdev:0xa02fd600, num 
of device:1 , name:fglrx, major 8, minor 88.
  Oct 25 14:55:46 lt9630 kernel: [  857.814346] device 0 : 0x88019b85 .
  Oct 25 14:55:46 lt9630 kernel: [  857.814348] Asic ID:0x6779, revision:0x3c, 
MMIOReg:0xc90012b8.
  Oct 25 14:55:46 lt9630 kernel: [  857.814349] FB phys addr: 0xc000, MC 
:0xf, Total FB size :0x4000.
  Oct 25 14:55:46 lt9630 kernel: [  857.814351] gart table MC:0xf0f8fd000, 
Physical:0xcf8fd000, size:0x402000.
  Oct 25 14:55:46 lt9630 kernel: [  857.814353] mc_node :FB, total 1 zones
  Oct 25 14:55:46 lt9630 kernel: [  857.814354] MC start:0xf, 
Physical:0xc000, size:0xfd0.
  Oct 25 14:55:46 lt9630 kernel: [  857.814356] Mapped heap -- Offset:0x0, 
size:0xf8fd000, reference count:33, mapping count:0,
  Oct 25 14:55:46 lt9630 kernel: [  857.814357] Mapped heap -- Offset:0x0, 
size:0x100, reference count:1, mapping count:0,
  Oct 25 14:55:46 lt9630 kernel: [  857.814359] Mapped heap -- 
Offset:0xf8fd000,

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

2014-06-19 Thread Mantas Kriaučiūnas

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
Matching subscriptions: dp-unity
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 Default settings for the Baltix GNU/Linux OS and desktop:
  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 1332136] [NEW] package emacsen-common 2.0.7 failed to install/upgrade: ErrorMessage: 子程序已安裝的 post-installation script 傳回了錯誤退出狀態 1

2014-06-19 Thread BlueT - Matthew Lien - 練喆明

Public bug reported:

failed during do-release-upgrade from 12.04 to 14.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: emacsen-common 2.0.7
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Thu Jun 19 17:45:59 2014
Dependencies:
 
ErrorMessage: ErrorMessage: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
PackageArchitecture: all
SourcePackage: emacsen-common
Title: package emacsen-common 2.0.7 failed to install/upgrade: ErrorMessage: 
子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
UpgradeStatus: Upgraded to trusty on 2014-06-19 (0 days ago)

** Affects: emacsen-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package emacsen-common 2.0.7 failed to install/upgrade: ErrorMessage:
  子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1

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

Bug description:
  failed during do-release-upgrade from 12.04 to 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: emacsen-common 2.0.7
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Thu Jun 19 17:45:59 2014
  Dependencies:
   
  ErrorMessage: ErrorMessage: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
  PackageArchitecture: all
  SourcePackage: emacsen-common
  Title: package emacsen-common 2.0.7 failed to install/upgrade: ErrorMessage: 
子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
  UpgradeStatus: Upgraded to trusty on 2014-06-19 (0 days ago)

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

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

[Desktop-packages] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate

2014-06-19 Thread Dmitry Shachnev

I am not very comfortable with removing
miInitializeBackingStore(pScreen); call. If it causes no regression
in earlier versions, that does not mean anything, as you can't cover
all test cases.

Why was that line added?

** Changed in: xserver-xorg-video-openchrome-lts-saucy (Ubuntu)
   Status: Confirmed = Incomplete

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

Title:
  VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy  12.04.4
  candidate

Status in “xserver-xorg-video-openchrome” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-openchrome-lts-saucy” package in Ubuntu:
  Incomplete
Status in “xserver-xorg-video-openchrome” source package in Saucy:
  Fix Released
Status in “xserver-xorg-video-openchrome” source package in Trusty:
  Fix Released

Bug description:
  * Impact:
  - the driver doesn't work with the X.org version in 12.04 with the Saucy 
hardware enablement stack.

  * Test case:
  - try using 12.04 with the Saucy hardware enablement stack on a machine 
needing the openchrome driver.

  * regression potential:
  - check that xorg sessions work as they should. The patches have received 
testing in Debian/Trusty/Saucy and upstream, so presumably should be fairly 
safe. The number of people using openchrome is relatively small compared to the 
main X drivers, so the scope of risk is rather small here.

  --
  Saucy Hardware Enablement Stack:

  https://wiki.ubuntu.com/Kernel/LTSEnablementStack

  ---

  Please bear with me and read all of this. Since I can't get a working
  display in Saucy with that graphics chip I need to use this method to
  file the initial bug report, but I can provide info using a chroot or
  replacing the quiet splash boot parameter with text which takes me
  to a tty interface.

  I hope using the tty interface provided by using the text boot
  parameter I can use apport-collect to collect the info needed from
  an installed Lubuntu 13.10 but I won't do so until asked by a dev in
  case some switch needs to be set to collect the appropriate info.

  I also want to say that I'm fully aware that graphics chip is not
  supported by Ubuntu/compiz itself, or even GNOME's mutter window
  manager, but I think it should still work with the openbox, metacity,
  and Xfwm window managers .. at least I hope so :^)

  So onto what actually happens. When I try to boot either Lubuntu or
  Xubuntu Saucy Alpha 2, either the live image or an installed version,
  I just get a frozen progress bar. So it's just 5 frozen dots on the
  screen. If I try booting through the recovery mode or otherwise trying
  to startx or 'sudo service lightdm start' I just get a blank
  screen. I can see the backlight is working but that's all.

  This is the specific hardware:

  VIA C7 CPU @ 1500MHz
  VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
  VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
  Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
  1GB DDR2 RAM

  I did take a pic of the live image boot process while dealing with an
  unrelated d-i bug during Lubuntu Alpha 2 testing process:

  https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG

  Now I'm wondering what else to say ... the same Saucy
  images and installs work with two other totally different sets of
  hardware.

  I'm ready to roll up my sleeves to help gather any needed info. Thanks
  in advance.

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

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

[Desktop-packages] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its logout applet are running

2014-06-19 Thread Matthieu Baerts

** Changed in: cairo-dock (Ubuntu Trusty)
   Status: Confirmed = Invalid

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

Title:
  Shutdown/restart dialogue is not working if Cairo-Dock and its logout
  applet are running

Status in Cairo-Dock : Core:
  Invalid
Status in “cairo-dock” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed
Status in “cairo-dock” source package in Trusty:
  Invalid
Status in “unity” source package in Trusty:
  Confirmed
Status in “cairo-dock” source package in Utopic:
  Invalid
Status in “unity” source package in Utopic:
  Confirmed

Bug description:
  Using latest stable release (3.3.1). Just upgraded to Saucy Salamander
  in Ubuntu. When cairo dock is set to automatically run at boot up the
  options to shutdown/restart do not work from the top menu panel next
  to the clock. When run manually after boot the shutdown/restart works
  fine. The shutdown/restart options do work fine from cairo
  dock/terminal but just mess up the shutdown/restart from the top menu
  panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions

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

[Desktop-packages] [Bug 1319338] Re: Default boost v1.54 has broken asio while available 1.55 is fixed

2014-06-19 Thread Brian Murray

Utopic, which will become 14.10, has boost version 1.55 so I am marking
this as Fix Released, but will open a 14.04 (Trusty) task for it.

** Changed in: boost-defaults (Ubuntu)
   Importance: Undecided = High

** Changed in: boost-defaults (Ubuntu)
   Status: Confirmed = Fix Released

** Also affects: boost-defaults (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: boost-defaults (Ubuntu Trusty)
   Status: New = Triaged

** Changed in: boost-defaults (Ubuntu Trusty)
   Importance: Undecided = High

** Changed in: boost-defaults (Ubuntu Trusty)
Milestone: None = ubuntu-14.04.1

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

Title:
  Default boost v1.54 has broken asio while available 1.55 is fixed

Status in Boost C++ Libraries:
  Fix Released
Status in “boost-defaults” package in Ubuntu:
  Fix Released
Status in “boost-defaults” source package in Trusty:
  Triaged

Bug description:
  Release: 14.04 LTS
  Version: 1.54.0.1ubuntu1
  Expected: Depend on working version of boost
  Happened: Depends on boost 1.54

  Here is a bug that was fixed in boost 7 months ago: 
https://svn.boost.org/trac/boost/ticket/8795
  Due to that, working with boost/asio seems impossible.

  The bug is still present in boost1.54 but fixed in boost1.55.
  Therefore I consider it a bug to use version 1.54 as default, as other
  libraries' dev-packages depend on boost-default and hence cannot be
  installed together with libboost1.55-dev without being rebuild.

  Of course, other possibilities would be to ask upstream if version 1.54 could 
be patched or add this patch to boost1.54.
  But there might be more benefits in boost1.55 and as both versions are not 
perfect I see no reason to stick with the older one.

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

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

[Desktop-packages] [Bug 1048430] Re: dnsmasq not available on the bus

2014-06-19 Thread Mathieu Trudel-Lapierre

The thing is, this error in and of itself is not a problem, it's just
traces of what NetworkManager is doing, to start dnsmasq on boot. The
fact that this message is showing is not a bug.

However, if you don't get nameservers properly set (ie. Firefox or
Chrome can't resolve web addresses), then I'd like you to please file
your own bug so we can get to the bottom of it. Use 'ubuntu-bug network-
manager' to do so, so all the necessary information will be there to
debug the problems.

This isn't an issue with dnsmasq itself or dnsmasq-base (the latter
being more likely the package installed on your system). Please don't
purge and reinstall these packages unless requested by a developer: it's
not likely to change much.

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

Title:
  dnsmasq not available on the bus

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

Bug description:
  Dnsmasq seems to be having some issues. This occurs whenever I try to
  connect to my wireless network; sometimes it only happens once, but
  sometimes the error loops for a while.

  Sep  9 17:43:51 bkerensa NetworkManager[935]: info DNS: starting dnsmasq...
  Sep  9 17:43:51 bkerensa NetworkManager[935]: error [1347237831.899067] 
[nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update 
servers.
  Sep  9 17:43:51 bkerensa NetworkManager[935]: error [1347237831.899142] 
[nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get 
owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
  Sep  9 17:43:51 bkerensa NetworkManager[935]: warn DNS: plugin dnsmasq 
update failed
  Sep  9 17:43:51 bkerensa NetworkManager[935]: info ((null)): writing 
resolv.conf to /sbin/resolvconf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: dnsmasq (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 17:47:22 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago)

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

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

[Desktop-packages] [Bug 1048430] Re: dnsmasq not available on the bus

2014-06-19 Thread Mathieu Trudel-Lapierre

Setting this back to incomplete so we don't miss comments, but please
file new bugs for any issues you find -- piling comments on older bugs,
for different machines and circumstances make debugging very hard.

Thanks!

** Changed in: network-manager (Ubuntu)
   Status: Expired = Incomplete

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

Title:
  dnsmasq not available on the bus

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

Bug description:
  Dnsmasq seems to be having some issues. This occurs whenever I try to
  connect to my wireless network; sometimes it only happens once, but
  sometimes the error loops for a while.

  Sep  9 17:43:51 bkerensa NetworkManager[935]: info DNS: starting dnsmasq...
  Sep  9 17:43:51 bkerensa NetworkManager[935]: error [1347237831.899067] 
[nm-dns-dnsmasq.c:390] update(): dnsmasq not available on the bus, can't update 
servers.
  Sep  9 17:43:51 bkerensa NetworkManager[935]: error [1347237831.899142] 
[nm-dns-dnsmasq.c:392] update(): dnsmasq owner not found on bus: Could not get 
owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
  Sep  9 17:43:51 bkerensa NetworkManager[935]: warn DNS: plugin dnsmasq 
update failed
  Sep  9 17:43:51 bkerensa NetworkManager[935]: info ((null)): writing 
resolv.conf to /sbin/resolvconf

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: dnsmasq (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 17:47:22 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to quantal on 2012-08-08 (32 days ago)

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

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

[Desktop-packages] [Bug 1332183] [NEW] Installing gnome-session-flashback in Ubuntu GNOME Trusty provides a Flashback (Compiz) session when compiz is not installed

2014-06-19 Thread Erick Brunzell

Public bug reported:

Just as the title says, installing 'gnome-session-flashback' in Ubuntu
GNOME provides a GNOME Flashback (Compiz) session even though 'compiz'
is not installed:

lance@lance-desktop:~$ ls /usr/share/xsessions
gnome-classic.desktop  gnome-fallback-compiz.desktop
gnome.desktop  gnome-fallback.desktop
lance@lance-desktop:~$ apt-cache policy compiz
compiz:
  Installed: (none)
  Candidate: 1:0.9.11+14.04.20140423-0ubuntu1
  Version table:
 1:0.9.11+14.04.20140423-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
 1:0.9.11+14.04.20140409-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

This is much more than a minor inconvenience since Ubuntu GNOME has no
keyboard shortcut set for killing X out-of-box so, if the user selected
auto-login during installation, with no window manager running it can be
quite difficult to get back to the login screen to select a different
session.

The easiest way I found so far is to open a TTY via Ctrl+Alt+F1 and then
run sudo nano /etc/gdm/custom.conf, change AutomaticLoginEnable=true
to AutomaticLoginEnable=False, then run sudo dpkg-reconfigure gdm,
followed by sudo reboot. Then on reboot a working session can be
selected.

I would hope that there is some way to NOT display a session if it's
window manager is not installed.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnome-session-flashback 1:3.8.0-1ubuntu12
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CurrentDesktop: Unity
Date: Thu Jun 19 11:27:41 2014
GsettingsChanges:
 
InstallationDate: Installed on 2014-05-30 (20 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release i386 
(20140416.2)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Installing gnome-session-flashback in Ubuntu GNOME Trusty provides a
  Flashback (Compiz) session when compiz is not installed

Status in “gnome-panel” package in Ubuntu:
  New

Bug description:
  Just as the title says, installing 'gnome-session-flashback' in Ubuntu
  GNOME provides a GNOME Flashback (Compiz) session even though 'compiz'
  is not installed:

  lance@lance-desktop:~$ ls /usr/share/xsessions
  gnome-classic.desktop  gnome-fallback-compiz.desktop
  gnome.desktop  gnome-fallback.desktop
  lance@lance-desktop:~$ apt-cache policy compiz
  compiz:
Installed: (none)
Candidate: 1:0.9.11+14.04.20140423-0ubuntu1
Version table:
   1:0.9.11+14.04.20140423-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

  This is much more than a minor inconvenience since Ubuntu GNOME has no
  keyboard shortcut set for killing X out-of-box so, if the user
  selected auto-login during installation, with no window manager
  running it can be quite difficult to get back to the login screen to
  select a different session.

  The easiest way I found so far is to open a TTY via Ctrl+Alt+F1 and
  then run sudo nano /etc/gdm/custom.conf, change
  AutomaticLoginEnable=true to AutomaticLoginEnable=False, then run
  sudo dpkg-reconfigure gdm, followed by sudo reboot. Then on reboot
  a working session can be selected.

  I would hope that there is some way to NOT display a session if it's
  window manager is not installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session-flashback 1:3.8.0-1ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Jun 19 11:27:41 2014
  GsettingsChanges:
   
  InstallationDate: Installed on 2014-05-30 (20 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release i386 
(20140416.2)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1332212] [NEW] Evolution - Send Later

2014-06-19 Thread Jared

Public bug reported:

Earlier Evolution was configured such that all mails went into the
outbox and these were sent later when I wanted them to be sent.

I am now using Ub 11.10 with all the updates and I cannot find a way to
configure Evolution to keep all emails in my outbox until I am ready to
send the. Now Evolution sends each mail as soon I it is completed.

Is there a way to configure Evolution to send the mail to my outbox and
then send it to the receipient when I want to?

any suggestions
Thank you
Srikumar


Evolution 3.10, shipped with Ubuntu 14.04 - has no such feature.

Please include 'Send Later'

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

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

Title:
  Evolution - Send Later

Status in “evolution” package in Ubuntu:
  New

Bug description:
  Earlier Evolution was configured such that all mails went into the
  outbox and these were sent later when I wanted them to be sent.

  I am now using Ub 11.10 with all the updates and I cannot find a way
  to configure Evolution to keep all emails in my outbox until I am
  ready to send the. Now Evolution sends each mail as soon I it is
  completed.

  Is there a way to configure Evolution to send the mail to my outbox
  and then send it to the receipient when I want to?

  any suggestions
  Thank you
  Srikumar

  
  Evolution 3.10, shipped with Ubuntu 14.04 - has no such feature.

  Please include 'Send Later'

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

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

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

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

** Changed in: ubuntu-drivers-common (Ubuntu)
   Status: New = Confirmed

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

Title:
  xorg.conf overwritten by booting system

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

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error -- AIGLX error: failed to open
  /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot
  open shared object file: No such file or directory] but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

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

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Apr 21 08:43:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1985]
     Subsystem: Hewlett-Packard Company Device [103c:1985]
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open

[Desktop-packages] [Bug 1332210] [NEW] Apple Magic Mouse battery life read as 0%

2014-06-19 Thread Luke Faraone

Public bug reported:

Despite being fully-functional, my Apple Magic Mouse is shown to be in
the discharging state at 0%. It is also marked rechargable, which is
false -- you need to replace the batteries when they run out.

Output of `upower --dump` attached.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: upower 0.9.23-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jun 19 10:30:37 2014
InstallationDate: Installed on 2014-04-01 (79 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
SourcePackage: upower
UpgradeStatus: Upgraded to trusty on 2014-04-24 (55 days ago)

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


** Tags: amd64 apport-bug trusty

** Attachment added: upower-2014-06-19.txt
   
https://bugs.launchpad.net/bugs/1332210/+attachment/4135007/+files/upower-2014-06-19.txt

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

Title:
  Apple Magic Mouse battery life read as 0%

Status in “upower” package in Ubuntu:
  New

Bug description:
  Despite being fully-functional, my Apple Magic Mouse is shown to be in
  the discharging state at 0%. It is also marked rechargable, which
  is false -- you need to replace the batteries when they run out.

  Output of `upower --dump` attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 19 10:30:37 2014
  InstallationDate: Installed on 2014-04-01 (79 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: upower
  UpgradeStatus: Upgraded to trusty on 2014-04-24 (55 days ago)

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

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

[Desktop-packages] [Bug 1302770] Re: keymap unstable

** Package changed: onboard (Ubuntu) = unity-settings-daemon (Ubuntu)

** Changed in: unity-settings-daemon (Ubuntu)
   Importance: Undecided = High

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

Title:
  keymap unstable

Status in Unity Settings Daemon:
  New
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  on a tablet pc, once the keyboard has been deactivate, if I try to
  reactivate the keymapping don't load my language, but the American.
  The same after using Onboard keyboard on screen, the real ones changed
  the map.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1302770/+subscriptions

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

[Desktop-packages] [Bug 1332226] [NEW] sensible-browser opens a new chromium even if one is already running