date:20140710

https://bugzilla.kernel.org/show_bug.cgi?id=73851

** Bug watch added: Linux Kernel Bug Tracker #73851
   http://bugzilla.kernel.org/show_bug.cgi?id=73851

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

Title:
  [USB-Audio - USB Audio, playback] Playback problem Playback only at
  maximum level, if the volume is turned down just a little no sound is
  played.

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

Bug description:
  The headphones worked with 10.04 at any volume level.
  Now the headphones work only at maximum volume level (tested with 11.10, 
12.04 13.04) if the volume is turned down just a little no sound is played.

  lsb_release -rd:
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ulrich 8418 F pulseaudio
   /dev/snd/controlC0:  ulrich 8418 F pulseaudio
   /dev/snd/pcmC0D0c:   ulrich 8418 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfd80 irq 50'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:11060448,15585130,0010 
HDA:80862804,15585130,0010'
 Controls  : 38
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Audio'/'USB Audio at usb-:00:1a.0-1.1.1, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0006'
 Controls  : 12
 Simple ctrls  : 7
  Date: Sat Jul 13 15:08:49 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio failed
  Symptom_Card: Storm HP-USB500 5.1 Headset - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: B5130M
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/27/2010:svnCLEVOCO.:pnB5130M:pvrNotApplicable:rvnCLEVOCO.:rnB5130M:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: B5130M
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

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

-- 
Mailing list: https://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 1316035] Re: matrox g200eR2 is unclaimed in 14.04

2014-07-10 Thread Zoltán Maróti

Hi,

Problem could be that you have other packages installed in the xorg-driver
package which were pulled automatically when you installed X. That means
you have probably other modules and dependencies unresolved. What I did was
first of all removing all unecessary xorg driver packages, xorg modules
which has nothing to do with this configuration anyway. Then I copied only
the corresponding package content from 12.04 (that is in my hack tar.gz).

My package list is therfore pretty lean:
dpkg -l | grep xorg
ii  xorg
1:7.7+1ubuntu8amd64X.Org X Window System
ii  xorg-docs-core
1:1.7-1   all  Core documentation for
the X.org X Window System
ii  xserver-xorg
1:7.7+1ubuntu8amd64X.Org X server
ii  xserver-xorg-core
2:1.15.1-0ubuntu2 amd64Xorg X server - core
server
ii  xserver-xorg-input-evdev
1:2.8.2-1ubuntu2  amd64X.Org X server -- evdev
input driver
ii  xserver-xorg-input-mouse
1:1.9.0-1build1   amd64X.Org X server -- mouse
input driver
ii  xserver-xorg-input-vmmouse
1:13.0.0-1build1  amd64X.Org X server --
VMMouse input driver to use with VMWare
ii  xserver-xorg-video-mga
1:1.6.3-1build1   amd64X.Org X server -- MGA
display driver
rc  xserver-xorg-video-vmware
1:13.0.2-2ubuntu1 amd64X.Org X server -- VMware
display driver

hope that helps

Regards,
Zoltan


2014-06-28 11:41 GMT+02:00 iwbnwif iwbn...@gmail.com:

 I am having exactly the same issue as this on two brand new Dell
 PowerEdge R360 which I am setting up for the first time. This server is
 also certified for use with 14.04 LTS
 http://www.ubuntu.com/certification/hardware/201207-11432/

 I tried to apply Zoltan's hack but ended up with a system that won't
 boot. I guess this is something to do with the fact that Grub is using
 the framebuffer otherwise I can't see how the changes would stop even a
 text screen appearing.

 In the end I installed 12.04 which works almost flawlessly (resizing
 windows is still painfully slow). However given these are new servers I
 would like to start them off with the latest LTS.

 Zoltan if you read this please could you give any hint why we are
 getting different results with the hack?

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

 Title:
   matrox g200eR2 is unclaimed in 14.04

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

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

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

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

   Thus xserver is not hardver accelerated.

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

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

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+subscriptions


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

Title:
  matrox g200eR2 is unclaimed in 14.04

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

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

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

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

  Thus xserver is not hardver accelerated.

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

  kernel

[Desktop-packages] [Bug 1021651] Re: preview screen to save the changes is too small

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

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

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

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

Title:
  preview screen to save the changes is too small

Status in “eog” package in Ubuntu:
  Confirmed

Bug description:
  I opened some photos in eog picture viewer and as their rotation was
  not correct I rotated them by using rotate left / rotate right
  options. After closing the viewer, it gave me the option that whether
  I want to save the changes or not . In this screen the preview of the
  images was too small ( See the attached screen-shot ) . I think there
  should be a maximize buttom on this window to preview the things
  correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: eog 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jul  6 14:16:45 2012
  ExecutablePath: /usr/bin/eog
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1340067] [NEW] Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9

2014-07-10 Thread Monsta

Public bug reported:

On 2013-09-30, the alternate scroll mode has been implemented in vte3
upstream [1]. In the same commit,
vte_terminal_set_alternate_screen_scroll function has been added which
does nothing and is there only for the compatibility with the previously
patched Ubuntu's vte3 (the patch has been dropped in vte3
0.34.9-1ubuntu1).

Since this function now does nothing, Ubuntu's
20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too.
It doesn't matter whether you turn the alt.scroll on or off in gnome-
terminal's preferences window - the mouse scroll in console apps like
man is ALWAYS turned on. Seems like it's always turned on in vte3 =
0.34.9 (again, see [1] for more info).

So I prorose to drop this 20_add_alt_screen_toggle_ui.patch since it's
useless now.


[1] 
https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275

** Affects: gnome-terminal (Ubuntu)
 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.
https://bugs.launchpad.net/bugs/1340067

Title:
  Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 =
  0.34.9

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

Bug description:
  On 2013-09-30, the alternate scroll mode has been implemented in vte3
  upstream [1]. In the same commit,
  vte_terminal_set_alternate_screen_scroll function has been added which
  does nothing and is there only for the compatibility with the
  previously patched Ubuntu's vte3 (the patch has been dropped in vte3
  0.34.9-1ubuntu1).

  Since this function now does nothing, Ubuntu's
  20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too.
  It doesn't matter whether you turn the alt.scroll on or off in gnome-
  terminal's preferences window - the mouse scroll in console apps like
  man is ALWAYS turned on. Seems like it's always turned on in vte3 =
  0.34.9 (again, see [1] for more info).

  So I prorose to drop this 20_add_alt_screen_toggle_ui.patch since it's
  useless now.

  
  [1] 
https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275

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

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

[Desktop-packages] [Bug 1340067] Re: Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 = 0.34.9

2014-07-10 Thread Monsta

** Description changed:

  On 2013-09-30, the alternate scroll mode has been implemented in vte3
  upstream [1]. In the same commit,
  vte_terminal_set_alternate_screen_scroll function has been added which
  does nothing and is there only for the compatibility with the previously
  patched Ubuntu's vte3 (the patch has been dropped in vte3
  0.34.9-1ubuntu1).
  
  Since this function now does nothing, Ubuntu's
  20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too.
  It doesn't matter whether you turn the alt.scroll on or off in gnome-
  terminal's preferences window - the mouse scroll in console apps like
  man is ALWAYS turned on. Seems like it's always turned on in vte3 =
  0.34.9 (again, see [1] for more info).
  
- So I prorose to drop this 20_add_alt_screen_toggle_ui.patch since it's
+ So I propose to drop this 20_add_alt_screen_toggle_ui.patch since it's
  useless now.
  
- 
- [1] 
https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275
+ [1]
+ 
https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275

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

Title:
  Drop 20_add_alt_screen_toggle_ui.patch - it does nothing with vte3 =
  0.34.9

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

Bug description:
  On 2013-09-30, the alternate scroll mode has been implemented in vte3
  upstream [1]. In the same commit,
  vte_terminal_set_alternate_screen_scroll function has been added which
  does nothing and is there only for the compatibility with the
  previously patched Ubuntu's vte3 (the patch has been dropped in vte3
  0.34.9-1ubuntu1).

  Since this function now does nothing, Ubuntu's
  20_add_alt_screen_toggle_ui.patch for gnome-terminal does nothing too.
  It doesn't matter whether you turn the alt.scroll on or off in gnome-
  terminal's preferences window - the mouse scroll in console apps like
  man is ALWAYS turned on. Seems like it's always turned on in vte3 =
  0.34.9 (again, see [1] for more info).

  So I propose to drop this 20_add_alt_screen_toggle_ui.patch since it's
  useless now.

  [1]
  
https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275

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

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

[Desktop-packages] [Bug 1270118] Update Released

2014-07-10 Thread Colin Watson

The verification of the Stable Release Update for lightdm has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  lightdm ask ldap administrator password when changing an expired
  password

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.4 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Fix Released
Status in “lightdm” source package in Saucy:
  Triaged
Status in “lightdm” package in Debian:
  Fix Released

Bug description:
  [Impact]
  LightDM does not correctly use PAM to change users passwords when they 
expire. This causes some PAM modules (e.g. pam_ldap) to not correctly perform 
password changing.

  [Test Case]
  1. Setup LDAP logins
  2. Expire users password
  3. Attempt to log into greeter
  Expected result:
  - User is prompted to change password. Password limitations are correctly 
enforced.
  Observed result:
  - User is prompted to change password. Password limitations are not correctly 
enforced.

  [Regression Potential]
  Any PAM module that relied on the previous incorrect behaviour might behave 
differently. It is not expected that any module would intentionally do this.

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

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

[Desktop-packages] [Bug 1270118] Re: lightdm ask ldap administrator password when changing an expired password

This bug was fixed in the package lightdm - 1.2.3-0ubuntu2.5

---
lightdm (1.2.3-0ubuntu2.5) precise; urgency=medium

  * debian/patches/08_chauthtok.patch:
- Correctly invoke PAM to change authentication token (LP: #1270118)
 -- Robert Ancell robert.anc...@canonical.com   Tue, 01 Apr 2014 16:03:51 
+1300

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

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

Title:
  lightdm ask ldap administrator password when changing an expired
  password

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.4 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Fix Released
Status in “lightdm” source package in Saucy:
  Triaged
Status in “lightdm” package in Debian:
  Fix Released

Bug description:
  [Impact]
  LightDM does not correctly use PAM to change users passwords when they 
expire. This causes some PAM modules (e.g. pam_ldap) to not correctly perform 
password changing.

  [Test Case]
  1. Setup LDAP logins
  2. Expire users password
  3. Attempt to log into greeter
  Expected result:
  - User is prompted to change password. Password limitations are correctly 
enforced.
  Observed result:
  - User is prompted to change password. Password limitations are not correctly 
enforced.

  [Regression Potential]
  Any PAM module that relied on the previous incorrect behaviour might behave 
differently. It is not expected that any module would intentionally do this.

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

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

[Desktop-packages] [Bug 1339908] Re: PCI/internal sound card not detected

0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe1Block: 
0/32 (20131115/tbfadt-572)
[0.00] ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has zero 
address or length: 0x102C/0x0 (20131115/tbfadt-603)

[
[0.137171] ACPI FADT declares the system doesn't support PCIe ASPM, so 
disable it
[0.137251] ACPI: bus type PCI registered

does sound work previous version Ubuntu  live cd ?

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

Title:
  PCI/internal sound card not detected

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

Bug description:
  After the update to 14.04 LTS both my wireless and sounds cards are no longer 
working. I'm on a Lenovo t60 IBM ThinkPad.
   I ran 
aplay -l
  aplay: device_list:268: no soundcards found...

  
  Then ran 
  sudo lspci -v
  00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller (rev 02)
Subsystem: Lenovo ThinkPad T60/R60 series
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at ee24 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link


  Now what??

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jul  9 16:04:32 2014
  InstallationDate: Installed on 2013-08-13 (330 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (74 days ago)
  dmi.bios.date: 07/13/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETD6WW (2.16 )
  dmi.board.name: 1953DAU
  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:bvr79ETD6WW(2.16):bd07/13/2007:svnLENOVO:pn1953DAU:pvrThinkPadT60:rvnLENOVO:rn1953DAU:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 1953DAU
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1270118] Re: lightdm ask ldap administrator password when changing an expired password

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

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

Title:
  lightdm ask ldap administrator password when changing an expired
  password

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.2 series:
  Fix Released
Status in Light Display Manager 1.4 series:
  Fix Released
Status in Light Display Manager 1.8 series:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” source package in Precise:
  Fix Released
Status in “lightdm” source package in Saucy:
  Triaged
Status in “lightdm” package in Debian:
  Fix Released

Bug description:
  [Impact]
  LightDM does not correctly use PAM to change users passwords when they 
expire. This causes some PAM modules (e.g. pam_ldap) to not correctly perform 
password changing.

  [Test Case]
  1. Setup LDAP logins
  2. Expire users password
  3. Attempt to log into greeter
  Expected result:
  - User is prompted to change password. Password limitations are correctly 
enforced.
  Observed result:
  - User is prompted to change password. Password limitations are not correctly 
enforced.

  [Regression Potential]
  Any PAM module that relied on the previous incorrect behaviour might behave 
differently. It is not expected that any module would intentionally do this.

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

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

[Desktop-packages] [Bug 1340076] [NEW] HDMI audio is severely distorted.

2014-07-10 Thread Luke

Public bug reported:

I have recently installed Ubuntu onto a newly built computer with an
ASRock H87 Performance Motherboard. I am using a TV monitor for a
screen, connected with HDMI. The visuals work fine but the audio is
severely distorted and echoes.

When testing the sound in the hardware settings, it sounds like
FRONTFRONTFRONTFRONT with static or overdrive getting more and more
prominent as the sound goes on. I have changed the Alsamixer levels but
found no change. The built-in sound card also shows up when i look for
it as per the Sound Troubleshooting page.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
NonfreeKernelModules: snd_hda_codec_generic snd_hda_controller fglrx
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  luke   2371 F pulseaudio
 /dev/snd/controlC1:  luke   2371 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 10 17:52:52 2014
InstallationDate: Installed on 2014-07-09 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
Symptom_Card: HD-Audio Generic - HD-Audio Generic
Symptom_Jack: Digital Out, HDMI
Symptom_Type: Digital clip or distortion, or overdriven sound
Title: [To Be Filled By O.E.M., ATI R6xx HDMI, Digital Out, HDMI] Sound is 
distorted
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: H87 Performance
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd05/06/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug trusty

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

Title:
  HDMI audio is severely distorted.

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

Bug description:
  I have recently installed Ubuntu onto a newly built computer with an
  ASRock H87 Performance Motherboard. I am using a TV monitor for a
  screen, connected with HDMI. The visuals work fine but the audio is
  severely distorted and echoes.

  When testing the sound in the hardware settings, it sounds like
  FRONTFRONTFRONTFRONT with static or overdrive getting more and more
  prominent as the sound goes on. I have changed the Alsamixer levels
  but found no change. The built-in sound card also shows up when i look
  for it as per the Sound Troubleshooting page.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: snd_hda_codec_generic snd_hda_controller fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  luke   2371 F pulseaudio
   /dev/snd/controlC1:  luke   2371 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 10 17:52:52 2014
  InstallationDate: Installed on 2014-07-09 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [To Be Filled By O.E.M., ATI R6xx HDMI, Digital Out, HDMI] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Performance
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd05/06/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.

[Desktop-packages] [Bug 494067]

2014-07-10 Thread Andreas-nordal-4

Please remember the notorious Well, this is embarrassing after KDE logout:
http://support.mozilla.org/en-US/questions/982769
http://bugs.launchpad.net/ubuntu/+bug/492001

If you, like me, tend to have Firefox open when exiting KDE (like
turning off computer), then voila, this becomes your computer's greeting
message... (That's KDE restoring last open programs for you.)

It's like this even on openSUSE. And it happens _always_.

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

Title:
  Provide better Firefox KDE integration

Status in The Mozilla Firefox Browser:
  Confirmed
Status in XUL + XPCOM application runner:
  Confirmed
Status in “firefox” package in Ubuntu:
  Fix Released
Status in “xulrunner-1.9.1” package in Ubuntu:
  Invalid
Status in Baltix GNU/Linux:
  New
Status in openSUSE:
  Fix Released

Bug description:
  Binary package hint: firefox-3.5

  The KDE integration of Firefox is still suboptimal in Ubuntu.

  openSUSE developed a set of patches that improves the situation:
  http://en.opensuse.org/KDE/FirefoxIntegration
  http://gitorious.org/firefox-kde-opensuse/

  These should be integrated into the firefox-3.5 / xulrunner-1.9.1 packages and
  a new package for the helper application kmozillahelper is necessary.

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

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

[Desktop-packages] [Bug 1339922] Re: Sync lbdb 0.39 (main) from Debian unstable (main)

2014-07-10 Thread Daniel Holbach

This bug was fixed in the package lbdb - 0.39
Sponsored for Jackson Doak (noskcaj)

---
lbdb (0.39) unstable; urgency=low

  * Use dh_autotools-dev (Closes: #727289).
  * Update packaged autotools files.
  * Rebuild aclocal/autoconf.
  * Change debian/source-format to 3.0 (native).
  * Remove mutt-ja from Suggests, since this no longer exists.
  * Upgrade build depenency to debhelper (= 9).
  * Change debian/compat to 9.
  * Complete rewrite of debian/rules.
  * Now uses hardening via debhelper.
  * Add $CPPFLAGS to $CFLAGS to really use hardening.
  * Upgrade to Standards-Version 3.9.5 (no changes).
  * m_vcf: Optimize missing names handling (Thanks to Jamey Sharp)
(Closes: #624590).
  * Made debian/copyright machine readable.
  * m_abook: fix formatting (Thanks to Alfredo Finelli) (Closes: #681526).
  * mutt-ldap-query: Add parameters for TLS and SASL_MECH (Thanks to
Alexandra N. Kossovsky) (Closes: #512074).
  * Mention user mutt-ldap-query configuration files in lbdbq(1) man page
(Closes: #534710).
  * Update ABQuery build mechanism (Thanks to Brendan Cully).

 -- Roland Rosenfeld rol...@debian.org  Sat, 10 May 2014 17:33:51
+0200

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

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

Title:
  Sync lbdb 0.39 (main) from Debian unstable (main)

Status in “lbdb” package in Ubuntu:
  Fix Released

Bug description:
  Please sync lbdb 0.39 (main) from Debian unstable (main)

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

  Changelog entries since current utopic version 0.38ubuntu1:

  lbdb (0.39) unstable; urgency=low

* Use dh_autotools-dev (Closes: #727289).
* Update packaged autotools files.
* Rebuild aclocal/autoconf.
* Change debian/source-format to 3.0 (native).
* Remove mutt-ja from Suggests, since this no longer exists.
* Upgrade build depenency to debhelper (= 9).
* Change debian/compat to 9.
* Complete rewrite of debian/rules.
* Now uses hardening via debhelper.
* Add $CPPFLAGS to $CFLAGS to really use hardening.
* Upgrade to Standards-Version 3.9.5 (no changes).
* m_vcf: Optimize missing names handling (Thanks to Jamey Sharp)
  (Closes: #624590).
* Made debian/copyright machine readable.
* m_abook: fix formatting (Thanks to Alfredo Finelli) (Closes: #681526).
* mutt-ldap-query: Add parameters for TLS and SASL_MECH (Thanks to
  Alexandra N. Kossovsky) (Closes: #512074).
* Mention user mutt-ldap-query configuration files in lbdbq(1) man page
  (Closes: #534710).
* Update ABQuery build mechanism (Thanks to Brendan Cully).

   -- Roland Rosenfeld rol...@debian.org  Sat, 10 May 2014 17:33:51
  +0200

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

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

[Desktop-packages] [Bug 1339921] Re: Sync gsl 1.16+dfsg-2 (main) from Debian unstable (main)

2014-07-10 Thread Daniel Holbach

This bug was fixed in the package gsl - 1.16+dfsg-2
Sponsored for Jackson Doak (noskcaj)

---
gsl (1.16+dfsg-2) unstable; urgency=low

  * debian/rules: Applies patch by Fernando Seiti Furusato to switch to
autoreconf use via debhelper in order to build on eg the ppc64el
architecture.   (Closes: #753360)
  * debian/control: Idem, in Build-Depends s/autotools-dev/dh-autoreconf/

  * debian/rules: Add dpkg-buildflags call for CFLAGS and LDFLAGS
  
  * debian/control: Set Standards-Version: to current version 
  
 -- Dirk Eddelbuettel e...@debian.org  Sat, 05 Jul 2014 11:23:16 -0500

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

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

Title:
  Sync gsl 1.16+dfsg-2 (main) from Debian unstable (main)

Status in “gsl” package in Ubuntu:
  Fix Released

Bug description:
  Please sync gsl 1.16+dfsg-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Patch aclocal.m4 for powerpc64le and regenerate configure to match.
  Seems to be fixed in debian

  Changelog entries since current utopic version 1.16+dfsg-1ubuntu1:

  gsl (1.16+dfsg-2) unstable; urgency=low

* debian/rules: Applies patch by Fernando Seiti Furusato to switch to
  autoreconf use via debhelper in order to build on eg the ppc64el
  architecture. (Closes: #753360)
* debian/control: Idem, in Build-Depends s/autotools-dev/dh-autoreconf/

* debian/rules: Add dpkg-buildflags call for CFLAGS and LDFLAGS

* debian/control: Set Standards-Version: to current version 

   -- Dirk Eddelbuettel e...@debian.org  Sat, 05 Jul 2014 11:23:16 -0500

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

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

[Desktop-packages] [Bug 1339244] Re: Comparison of exit_status in run_custom_command is wrong

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

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

Title:
  Comparison of exit_status in run_custom_command is wrong

Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Trusty:
  New

Bug description:
  In file /plugins/common/gsd-input-helper.c in function
  run_custom_command the variable exit_status doesn't contain the exit
  status of the process, so the statement return (exit_status == 1);
  is wrong.

  The documentation 
(https://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#g-spawn-sync)
 says:
  exit_statusreturn location for child exit status, as returned by 
waitpid(), or NULL.

  And in the documentation of waitpid
  (http://linux.die.net/man/2/waitpid) exit_status is described.

  You have to do something like this:
  if (WIFEXITED(exit_status) == FALSE) {
  return FALSE;
  }
  return (WEXITSTATUS(exit_status) == 1);

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

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

[Desktop-packages] [Bug 1243806] Re: The names column has its width dictated by other columns

2014-07-10 Thread Ric Flomag

This page:
https://bugzilla.redhat.com/show_bug.cgi?id=1037577

Strongly suggests its a GTK3 bug.


** Bug watch added: Red Hat Bugzilla #1037577
   https://bugzilla.redhat.com/show_bug.cgi?id=1037577

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

Title:
  The names column has its width dictated by other columns

Status in Nautilus:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “nautilus” source package in Trusty:
  Triaged

Bug description:
  Folder names in Location area keeps the width even though when I go back to 
upper folder.
  First of all this new downgraded nautilus folder section holds its width and 
I cannot even change the width at all.
  Then when I go deep down lower folders or open folder with long name, it 
would squeeze down the Name part and I cannot even see names anymore. Then 
when I go up to upper folder or root, I cannot see the names anymore becaue 
location column takes up all the space. Once I click one of the unseen folder, 
I may see the names again. 
  This is one of too many problems of 13.10.

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

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

[Desktop-packages] [Bug 1312135] Re: Under KDE firefox uses nautilus instead of dolphin to handle directories

2014-07-10 Thread Jorge Suárez de Lis

I have tried the workaround from #5, but nautilus is still being opened!
:(

Launching nautilus from the command line opens dolphin instead, but
Firefox always launches nautilus. Weird, huh?

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

Title:
  Under KDE firefox uses nautilus instead of dolphin to handle
  directories

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  1. Run firefox under kde
  2. Download a file with it
  3. Click the download icon
  4. Right click on the download object
  5. Ask to open the containing folder

  I would expect the KDE file browser dolphin to open.

  What instead happens the GNOME file browser nautilus is opened
  without the needed icons. (see screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
   /dev/snd/controlC0:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
  BuildID: 20140410211200
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Thu Apr 24 13:43:20 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-04-23 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  IpRoute:
   default via 192.168.254.254 dev eth0  proto static 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.254.0/24 dev eth0  proto kernel  scope link  src 192.168.254.42  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.01
  dmi.board.asset.tag: CZC3523T17
  dmi.board.name: 18EB
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3523T17
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 490 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1308322] Re: columns are not resizeable

2014-07-10 Thread Ric Flomag

This page:
https://bugzilla.redhat.com/show_bug.cgi?id=1037577

Strongly suggests its a GTK3 bug.

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

Title:
  columns are not resizeable

Status in “baobab” package in Ubuntu:
  Confirmed

Bug description:
  On trusty with version 3.8.2-1ubuntu1, I cannot resize the columns
  Folder, Usage, Size and Contents.  If there are long folder
  names, you will not be able to see any of the other information
  without scrolling vertically.  FWIW, the pointer DOES change into
  resize arrows but even if you click and drag to resize the columns,
  nothing will happen.

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

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

[Desktop-packages] [Bug 1193370] Re: Should run tests during build

2014-07-10 Thread Timo Jyrinki

Reopening qtscript, Debian disabled the tests for it (temporarily) and
we got it via autosync.

** Changed in: qtscript-opensource-src (Ubuntu)
   Status: Fix Committed = Triaged

** Also affects: qtimageformats-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtlocation-opensource-src (Ubuntu)
   Status: Fix Committed = Fix Released

** Changed in: qtxmlpatterns-opensource-src (Ubuntu)
   Status: Fix Committed = Fix Released

** Also affects: qtgraphicaleffects-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtgraphicaleffects-opensource-src (Ubuntu)
   Status: New = Fix Released

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

Title:
  Should run tests during build

Status in “qt3d-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtbase-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtconnectivity-opensource-src” package in Ubuntu:
  New
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtfeedback-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtgraphicaleffects-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtimageformats-opensource-src” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtpim-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtscript-opensource-src” package in Ubuntu:
  Triaged
Status in “qtsensors-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsvg-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsystems-opensource-src” package in Ubuntu:
  Fix Released
Status in “qttools-opensource-src” package in Ubuntu:
  New
Status in “qtwebkit-opensource-src” package in Ubuntu:
  New
Status in “qtxmlpatterns-opensource-src” package in Ubuntu:
  Fix Released

Bug description:
  Qt modules should run their tests during build. qtwebkit seems to have
  some under Tools/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1193370/+subscriptions

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

[Desktop-packages] [Bug 1193370] Re: Should run tests during build

2014-07-10 Thread Timo Jyrinki

** Also affects: qtconnectivity-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtsystems-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: qtsystems-opensource-src (Ubuntu)
   Status: New = Fix Released

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

Title:
  Should run tests during build

Status in “qt3d-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtbase-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtconnectivity-opensource-src” package in Ubuntu:
  New
Status in “qtdeclarative-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtfeedback-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtgraphicaleffects-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtimageformats-opensource-src” package in Ubuntu:
  New
Status in “qtlocation-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtmultimedia-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtpim-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtscript-opensource-src” package in Ubuntu:
  Triaged
Status in “qtsensors-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsvg-opensource-src” package in Ubuntu:
  Fix Released
Status in “qtsystems-opensource-src” package in Ubuntu:
  Fix Released
Status in “qttools-opensource-src” package in Ubuntu:
  New
Status in “qtwebkit-opensource-src” package in Ubuntu:
  New
Status in “qtxmlpatterns-opensource-src” package in Ubuntu:
  Fix Released

Bug description:
  Qt modules should run their tests during build. qtwebkit seems to have
  some under Tools/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt3d-opensource-src/+bug/1193370/+subscriptions

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

[Desktop-packages] [Bug 1339041] Re: package blt-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc-base/blt', which is also in package blt 2.4z-7ubuntu2

2014-07-10 Thread Matthias Klose

fixed in 2.5.3-4

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

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

Title:
  package blt-dev (not installed) failed to install/upgrade: trying to
  overwrite '/usr/share/doc-base/blt', which is also in package blt 2
  .4z-7ubuntu2

Status in “blt” package in Ubuntu:
  Fix Released

Bug description:
  dist-upgrade on utopic caused this error

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: blt-dev (not installed)
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  Date: Tue Jul  8 09:04:53 2014
  DuplicateSignature: package:blt-dev:(not installed):trying to overwrite 
'/usr/share/doc-base/blt', which is also in package blt 2.4z-7ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/doc-base/blt', which is also in 
package blt 2.4z-7ubuntu2
  InstallationDate: Installed on 2013-12-06 (213 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: blt
  Title: package blt-dev (not installed) failed to install/upgrade: trying to 
overwrite '/usr/share/doc-base/blt', which is also in package blt 2.4z-7ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1339244] Re: Comparison of exit_status in run_custom_command is wrong

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  Comparison of exit_status in run_custom_command is wrong

Status in “gnome-settings-daemon” package in Ubuntu:
  In Progress
Status in “gnome-settings-daemon” source package in Trusty:
  New

Bug description:
  In file /plugins/common/gsd-input-helper.c in function
  run_custom_command the variable exit_status doesn't contain the exit
  status of the process, so the statement return (exit_status == 1);
  is wrong.

  The documentation 
(https://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#g-spawn-sync)
 says:
  exit_statusreturn location for child exit status, as returned by 
waitpid(), or NULL.

  And in the documentation of waitpid
  (http://linux.die.net/man/2/waitpid) exit_status is described.

  You have to do something like this:
  if (WIFEXITED(exit_status) == FALSE) {
  return FALSE;
  }
  return (WEXITSTATUS(exit_status) == 1);

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

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

[Desktop-packages] [Bug 1340115] [NEW] Black squares appear for 1-2 sec. on almost the whole screen and then disappear.

2014-07-10 Thread Salih114

Public bug reported:

This problem exists since updating from ubuntu 12.04 to 14.04. It may
have to do with the drivers for my intel HD4000 gpu. I'm not able to
reproduce the error, which occures randomly.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-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 Jul 10 11:59:03 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 20130623, 3.13.0-30-generic, i686: installed
 tp-smapi, 0.41, 3.13.0-30-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:5008]
InstallationDate: Installed on 2014-07-07 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: LENOVO 3358BBG
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=d10ccc8f-9556-4813-86b0-f1a879385e4c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: H4ET92WW (2.52 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3358BBG
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrH4ET92WW(2.52):bd04/18/2013:svnLENOVO:pn3358BBG:pvrThinkPadEdgeE130:rvnLENOVO:rn3358BBG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3358BBG
dmi.product.version: ThinkPad Edge E130
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140423-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 Jul 10 11:46:18 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1161 
 vendor IVO
xserver.version: 2:1.15.1-0ubuntu2

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

Title:
  Black squares appear for 1-2 sec. on almost the whole screen and then
  disappear.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This problem exists since updating from ubuntu 12.04 to 14.04. It may
  have to do with the drivers for my intel HD4000 gpu. I'm not able to
  reproduce the error, which occures randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-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 Jul 10 11:59:03 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 20130623, 3.13.0-30-generic, i686: installed
   tp-smapi, 0.41, 3.13.0-30-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:5008]
  InstallationDate: Installed on 2014-07-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: LENOVO 3358BBG
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1339244] Re: Comparison of exit_status in run_custom_command is wrong

This bug was fixed in the package gnome-settings-daemon -
3.8.6.1-0ubuntu15

---
gnome-settings-daemon (3.8.6.1-0ubuntu15) utopic; urgency=low

  * debian/patches/git_lp1339244.patch:
- fix exit status check in gsd-input-helper.c (LP: #1339244)
 -- Michael Vogt michael.v...@ubuntu.com   Thu, 10 Jul 2014 11:05:00 +0200

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: In Progress = Fix Released

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

Title:
  Comparison of exit_status in run_custom_command is wrong

Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” source package in Trusty:
  New

Bug description:
  In file /plugins/common/gsd-input-helper.c in function
  run_custom_command the variable exit_status doesn't contain the exit
  status of the process, so the statement return (exit_status == 1);
  is wrong.

  The documentation 
(https://developer.gnome.org/glib/stable/glib-Spawning-Processes.html#g-spawn-sync)
 says:
  exit_statusreturn location for child exit status, as returned by 
waitpid(), or NULL.

  And in the documentation of waitpid
  (http://linux.die.net/man/2/waitpid) exit_status is described.

  You have to do something like this:
  if (WIFEXITED(exit_status) == FALSE) {
  return FALSE;
  }
  return (WEXITSTATUS(exit_status) == 1);

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

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

[Desktop-packages] [Bug 1318584] Re: qt crashed when switching video out mode to external or internal only mode

2014-07-10 Thread Maarten Lankhorst

On utopic when I disable the active screen I get the following
backtrace:

pure virtual method called
terminate called without an active exception

Program received signal SIGABRT, Aborted.
0x74e4c117 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56  ../nptl/sysdeps/unix/sysv/linux/raise.c: Bestand of map bestaat niet.
(gdb) bt
#0  0x74e4c117 in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x74e4d808 in __GI_abort () at abort.c:89
#2  0x75453285 in __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#3  0x754510f6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x75451141 in std::terminate() () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x75451c8f in __cxa_pure_virtual () from 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x75ef6efa in QPlatformScreen::physicalSize (this=optimized out) 
at kernel/qplatformscreen.cpp:139
#7  0x75f30772 in QScreen::physicalSize (this=this@entry=0x6620c0) at 
kernel/qscreen.cpp:243
#8  0x75f30819 in QScreen::physicalDotsPerInch 
(this=this@entry=0x6620c0) at kernel/qscreen.cpp:166
#9  0x778343d2 in QQuickScreenAttached::screenChanged (this=0x2e16f20, 
screen=0x6621b0) at items/qquickscreen.cpp:315
#10 0x759f391e in QMetaObject::activate 
(sender=sender@entry=0x7fffe7b0, signalOffset=optimized out, 
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffd9a0) 
at kernel/qobject.cpp:3680
#11 0x759f3dd7 in QMetaObject::activate 
(sender=sender@entry=0x7fffe7b0, m=m@entry=0x765125c0 
QWindow::staticMetaObject, local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffd9a0) at kernel/qobject.cpp:3546
#12 0x75f0b78f in QWindow::screenChanged 
(this=this@entry=0x7fffe7b0, _t1=_t1@entry=0x6621b0) at 
.moc/moc_qwindow.cpp:623
#13 0x75f0e160 in QWindowPrivate::setScreen (this=0x8aa3a0, 
newScreen=0x6621b0, recreate=optimized out) at kernel/qwindow.cpp:372
#14 0x75f0e2e2 in QWindow::screenDestroyed (this=0x7fffe7b0, 
object=optimized out) at kernel/qwindow.cpp:1637
#15 0x759f391e in QMetaObject::activate (sender=sender@entry=0x6620c0, 
signalOffset=optimized out, local_signal_index=local_signal_index@entry=0, 
argv=argv@entry=0x7fffdb60) at kernel/qobject.cpp:3680
#16 0x759f3dd7 in QMetaObject::activate (sender=sender@entry=0x6620c0, 
m=m@entry=0x75e1bf20 QObject::staticMetaObject, 
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fffdb60) 
at kernel/qobject.cpp:3546
#17 0x759f3e6f in QObject::destroyed (this=this@entry=0x6620c0, 
_t1=_t1@entry=0x6620c0) at .moc/moc_qobject.cpp:202
#18 0x759fb308 in QObject::~QObject (this=0x6620c0, 
__in_chrg=optimized out) at kernel/qobject.cpp:901
#19 0x7624faf7 in ~QScreen (this=0x6620c0, __in_chrg=optimized out) 
at .moc/../kernel/qscreen.h:64
#20 QScreen::~QScreen (this=0x6620c0, __in_chrg=optimized out) at 
.moc/../kernel/qscreen.h:64
#21 0x75ef70aa in QPlatformScreen::~QPlatformScreen (this=0x65b8e0, 
__in_chrg=optimized out) at kernel/qplatformscreen.cpp:65
#22 0x7fffedf51a99 in QXcbScreen::~QXcbScreen (this=0x65b8e0, 
__in_chrg=optimized out) at qxcbscreen.cpp:209
#23 0x7fffedf4511b in QXcbConnection::updateScreens 
(this=this@entry=0x6492b0) at qxcbconnection.cpp:258
#24 0x7fffedf45815 in QXcbConnection::handleXcbEvent 
(this=this@entry=0x6492b0, event=event@entry=0x7fffe4003490) at 
qxcbconnection.cpp:928
#25 0x7fffedf46a0b in QXcbConnection::processXcbEvents (this=0x6492b0) at 
qxcbconnection.cpp:1232
#26 0x759f45b6 in QObject::event (this=0x6492b0, e=optimized out) at 
kernel/qobject.cpp:1241
#27 0x768e66dc in QApplicationPrivate::notify_helper 
(this=this@entry=0x63cce0, receiver=receiver@entry=0x6492b0, 
e=e@entry=0x7fffe4004260) at kernel/qapplication.cpp:3504
#28 0x768eb456 in QApplication::notify (this=0x7fffe750, 
receiver=0x6492b0, e=0x7fffe4004260) at kernel/qapplication.cpp:3287
#29 0x759c49d5 in QCoreApplication::notifyInternal 
(this=0x7fffe750, receiver=0x6492b0, event=event@entry=0x7fffe4004260) at 
kernel/qcoreapplication.cpp:935
#30 0x759c6827 in sendEvent (event=0x7fffe4004260, receiver=optimized 
out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:237
#31 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, 
event_type=event_type@entry=0, data=0x63ce40) at 
kernel/qcoreapplication.cpp:1539
#32 0x759c6e58 in QCoreApplication::sendPostedEvents 
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at 
kernel/qcoreapplication.cpp:1397
#33 0x75a1c243 in postEventSourceDispatch (s=0x6ca730) at 
kernel/qeventdispatcher_glib.cpp:279
#34 0x73beade4 in g_main_context_dispatch () from

[Desktop-packages] [Bug 1312135] Re: Under KDE firefox uses nautilus instead of dolphin to handle directories

2014-07-10 Thread Uqbar

Jorge, I have another workaround that really works.
apt get purge nautilus
It worked for me with a KDE native environment.

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

Title:
  Under KDE firefox uses nautilus instead of dolphin to handle
  directories

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  1. Run firefox under kde
  2. Download a file with it
  3. Click the download icon
  4. Right click on the download object
  5. Ask to open the containing folder

  I would expect the KDE file browser dolphin to open.

  What instead happens the GNOME file browser nautilus is opened
  without the needed icons. (see screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
   /dev/snd/controlC0:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
  BuildID: 20140410211200
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Thu Apr 24 13:43:20 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-04-23 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  IpRoute:
   default via 192.168.254.254 dev eth0  proto static 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.254.0/24 dev eth0  proto kernel  scope link  src 192.168.254.42  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.01
  dmi.board.asset.tag: CZC3523T17
  dmi.board.name: 18EB
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3523T17
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 490 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1338872] Re: Button Shading is misaligned in base

2014-07-10 Thread Christopher M. Penalver

** Tags added: ppa

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided = Low

** Changed in: libreoffice (Ubuntu)
   Status: Incomplete = New

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

Title:
  Button Shading is misaligned in base

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  the buttons in the left pane are shaded incorrectly

  The large buttons in the Database pane on the left side of the
  screen are not shaded correctly.

  To reproduce:
  Open Firebird_test_intern.odb from 
https://bugs.freedesktop.org/attachment.cgi?id=87557

  I've attached a screenshot to show the error.

  his issue doesn’t occur in Windows 7. Please let me know if there is a fix to 
the issue.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-06-27 (12 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  Package: libreoffice 1:4.2.5~rc2-0ubuntu2 [origin: 
LP-PPA-libreoffice-libreoffice-4-2]
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Tags: third-party-packages trusty
  Uname: Linux 3.13.0-30-generic i686
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1290785] Re: Users with UID 60000 are invisible in login and Settings-User unless /etc/login.defs updated

2014-07-10 Thread Robert Euhus

Robert, if I found the correct sources, then I Ithink something went
very wrong with your patch for trusty:

I found sources for version 0.6.35-0ubuntu7.1 here:
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1 , namely:
http://launchpadlibrarian.net/179519600/accountsservice_0.6.35-0ubuntu7.1.dsc
http://launchpadlibrarian.net/179519599/accountsservice_0.6.35-0ubuntu7.1.debian.tar.xz
http://launchpadlibrarian.net/179519598/accountsservice_0.6.35.orig.tar.gz

and the diff:
http://launchpadlibrarian.net/179519604/accountsservice_0.6.35-0ubuntu7_0.6.35-0ubuntu7.1.diff.gz

As one can already guess from the diff, this is not only the patch
mentioned above, but quite a lot of aclocal/m4 files were simply removed
from the sources.

This leads to build errors as you can see from the attached log excerpt
from a pbuilder run.

The old version accountsservice_0.6.35-0ubuntu7 compiles without any
problems, but the new one just doesn't. compile at all.

Please correct this.

** Attachment added: accountsservice_0.6.35-0ubuntu7.1 compile error log from
pbuilder run

https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+attachment/4149529/+files/accountsservice-0.6.35-0ubuntu7.1_pbuilder-error.log

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

Title:
Users with UID 6 are invisible in login and Settings-User
unless /etc/login.defs updated

Status in “accountsservice” package in Ubuntu:
Fix Released
Status in “accountsservice” source package in Trusty:
Triaged

Bug description:
[Impact]
Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or
system settings without editing UID_MAX in /etc/login.defs. This was not
required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID
UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX.

[Test Case]
1. Create a user with a UID UID_MAX:
$ adduser --uid 60001 big-uid
2. Restart system
Expected result:
big-uid is shown in the greeter. Once logged in big-uid is shown in
system settings.
Observed result:
big-uid is not shown in the greeter (14.04 LTS, 14.10)
big-uid is not shown in system settings (13.10, 14.04LTS, 14.10)

[Regression Potential]
This could cause users that were previously hidden to be shown. This seems
unlikely to be a problem as all system created user accounts are less than
UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for
this case.

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

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

[Desktop-packages] [Bug 1314924] Re: Adressbox Entries unreadable: Grey/Black Mask overlaying text

2014-07-10 Thread Rüdiger Kupper

Please note that setting gfx.xrender.enabled to false cannot be a
permanent solution. It makes graphic rendering extremely sluggy over
network connections, where X client and server are not on the same
machine (and that's what X was designed for).

We deploy firefox in a client/server setup (Linux Terminal Server
Project, LTSP), for 800 users. Their firefox display is extremely slow
with xrender disabled. Scrolling down a page is a pain. Currently I need
to tell mu users: You can have gray boxes in the address field, or you
can have slow scolling. What would you like?

Setting gfx.xrender.enabled to false does *not fix* the issue, it just
hides it by the cost of losing other features.

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

Title:
  Adressbox Entries unreadable: Grey/Black Mask overlaying text

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Labtop: Asus M2400, 512MB RAM, Pentium M Banias using forcepae.
  OS: Xubuntu 14.04, all updates up to May 1, 2014.
  Application: Firefox 29, version 29.0+build1-0ubuntu0.14.04.2

  Updated Firefox to Firefox 29 by automatic software update. Restarted
  firefox, now all the HTTP address entries in the address box are
  unreadable; it looks like they are masked by a black or grey/black
  mask. This independent of address and website.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 29.0+build1-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tschmid1708 F pulseaudio
lightdm5509 F pulseaudio
  BuildID: 20140428194004
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Thu May  1 10:24:14 2014
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-19 (11 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.254.10 dev eth1  proto static 
   192.168.254.0/24 dev eth1  proto kernel  scope link  src 192.168.254.100  
metric 9
  NoProfiles: True
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 03/08/2004
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0208
  dmi.board.name: M2N
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0208:bd03/08/2004:svnASUSTeKComputerInc.:pnM2N:pvr1.0:rvnASUSTeKComputerInc.:rnM2N:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M2N
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Desktop-packages] [Bug 1339917] Re: [E-265M, SigmaTel STAC9200, Speaker, Internal] No sound at all

Default sink name: alsa_output.pci-_00_1b.0.iec958-stereo
Default source name: alsa_input.pci-_00_1b.0.analog-stere


https://wiki.ubuntu.com/PulseAudio/Log

https://wiki.ubuntu.com/Audio/AlsaInfo

** Changed in: pulseaudio (Ubuntu)
   Status: New = Incomplete

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

Title:
  [E-265M, SigmaTel STAC9200, Speaker, Internal] No sound at all

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  ubuntuone-instaler 3.0.2-0ubuntu1.1 is the version

  I had thought it was 12.04.2 if that makes sense ??

  I used to have sound, I went into the sound menu to turn up the sound
  and boom, no more sound.  I have windows on this computer as well and
  there is sound there but not for anything on ubuntu - nothing.

  I was shocked when the test tone played from your database for the first test 
and puzzled why it didn't play for the second.  I selected speaker internal but 
it is the same for anything headphones or what have you.  I have looked for 
instruction and gotten here.  I just did a system update and that didn't help 
the problem.
  here is this from the terminal:
  sudo lspci
  00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory 
Controller Hub (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (primary) (rev 03)
  00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) (rev 03)
  00:19.0 Ethernet controller: Intel Corporation 82566MC Gigabit Network 
Connection (rev 03)
  00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #3 (rev 03)
  00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 03)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
  00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface 
Controller (rev 03)
  00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE 
Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA 
Controller [AHCI mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 
03)
  02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  03:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
  03:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 
1394 Host Controller
  03:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card 
Reader (SD/MMC/MS/MS PRO/xD)
  03:09.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant 
SD Host Controller
  03:09.4 Communication controller: Texas Instruments PCIxx12 GemCore based 
SmartCard controller
  john@john-E-265M:~$ sudo lspci -v
  00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory 
Controller Hub (rev 03)
Subsystem: Gateway, Inc. Device 0370
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0a ?
Kernel driver in use: agpgart-intel

  00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (primary) (rev 03) (prog-if 00 [VGA controller])
Subsystem: Gateway, Inc. Device 0370
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f000 (64-bit, non-prefetchable) [size=1M]
Memory at d000 (64-bit, prefetchable) [size=256M]
I/O ports at 1800 [size=8]
Expansion ROM at unassigned [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 3
Kernel driver in use: i915
Kernel modules: intelfb, i915

  00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) (rev 03)
Subsystem: Gateway, Inc. Device 0370
Flags: bus master, fast devsel, latency 0
Memory at f010 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 3

  00:19.0 Ethernet controller:

[Desktop-packages] [Bug 1339917] Re: [E-265M, SigmaTel STAC9200, Speaker, Internal] No sound at all

active profile: output:iec958-stereo+input:analog-stereo
sinks:
alsa_output.pci-_00_1b.0.iec958-stereo/#0: Built-in Audio 
Digital Stereo (IEC958)
sources:
alsa_output.pci-_00_1b.0.iec958-stereo.monitor/#0: Monitor 
of Built-in Audio Digital Stereo (IEC958)
alsa_input.pci-_00_1b.0.analog-stereo/#1: Built-in Audio 
Analog Stereo
ports:
analog-output-headphones: Headphones (priority 9000, available: 
no)
properties:

analog-input-microphone-internal: Internal Microphone (priority 
8900, available: unknown)
properties:

analog-input-microphone: Microphone (priority 8700, available: 
no)
properties:

analog-input-linein: Line In (priority 8100, available: unknown)
properties:

iec958-stereo-output: Digital Output (S/PDIF) (priority 0, 
available: unknown)
properties:


seem internal speaker path was removed when there is no volume control for 
headphone and speaker

https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio


 mixer control 'Master',0
  Capabilities: pvolume pswitch penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 31
  Mono:
  Front Left: Playback 31 [100%] [0.00dB] [on]
  Front Right: Playback 31 [100%] [0.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume penum
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [

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

Title:
  [E-265M, SigmaTel STAC9200, Speaker, Internal] No sound at all

Status in “pulseaudio” package in Ubuntu:
  Incomplete

Bug description:
  ubuntuone-instaler 3.0.2-0ubuntu1.1 is the version

  I had thought it was 12.04.2 if that makes sense ??

  I used to have sound, I went into the sound menu to turn up the sound
  and boom, no more sound.  I have windows on this computer as well and
  there is sound there but not for anything on ubuntu - nothing.

  I was shocked when the test tone played from your database for the first test 
and puzzled why it didn't play for the second.  I selected speaker internal but 
it is the same for anything headphones or what have you.  I have looked for 
instruction and gotten here.  I just did a system update and that didn't help 
the problem.
  here is this from the terminal:
  sudo lspci
  00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory 
Controller Hub (rev 03)
  00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (primary) (rev 03)
  00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated 
Graphics Controller (secondary) (rev 03)
  00:19.0 Ethernet controller: Intel Corporation 82566MC Gigabit Network 
Connection (rev 03)
  00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #3 (rev 03)
  00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI 
Controller #1 (rev 03)
  00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
  00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface 
Controller (rev 03)
  00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE 
Controller (rev 03)
  00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA 
Controller [AHCI mode] (rev 03)
  00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 
03)
  02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
Network Connection (rev 02)
  03:09.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
  03:09.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 
1394 Host Controller
  03:09.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card 
Reader (SD/MMC/MS/MS PRO/xD)
  03:09.3 SD Host

[Desktop-packages] [Bug 1318584] Re: qt crashed when switching video out mode to external or internal only mode

2014-07-10 Thread Timo Jyrinki

For completeness sake, here's mine on Latitude D630 (Intel 965GM
graphics), also inside qglxintegration.cpp but slightly different.

Program received signal SIGSEGV, Segmentation fault.
0x7fffee0aa81c in QGLXContext::swapBuffers (this=0x81d790, 
surface=0x638450) at qglxintegration.cpp:392
(gdb) bt
#0  0x7fffee0aa81c in QGLXContext::swapBuffers (this=0x81d790, 
surface=0x638450) at qglxintegration.cpp:392
#1  0x7641cd92 in QOpenGLContext::swapBuffers (this=0x6c6b60, 
surface=optimized out) at kernel/qopenglcontext.cpp:906
#2  0x77990a8c in QSGGuiThreadRenderLoop::renderWindow (
this=this@entry=0xb44110, window=0x7943c0)
at scenegraph/qsgrenderloop.cpp:381
#3  0x77990f1e in QSGGuiThreadRenderLoop::exposureChanged (
this=0xb44110, window=0x7943c0) at scenegraph/qsgrenderloop.cpp:414
#4  0x763e4769 in QWindow::event (this=this@entry=0x7943c0, 
ev=ev@entry=0x7fffd8a0) at kernel/qwindow.cpp:1956
#5  0x779bad73 in QQuickWindow::event (this=0x7943c0, e=0x7fffd8a0)
at items/qquickwindow.cpp:1339
#6  0x76b3a6dc in QApplicationPrivate::notify_helper (
this=this@entry=0x616560, receiver=receiver@entry=0x7943c0, 
e=e@entry=0x7fffd8a0) at kernel/qapplication.cpp:3504
#7  0x76b3f456 in QApplication::notify (this=0x7fffddc0, 
receiver=0x7943c0, e=0x7fffd8a0) at kernel/qapplication.cpp:3287
#8  0x75e999d5 in QCoreApplication::notifyInternal (this=
0x7fffddc0, receiver=receiver@entry=0x7943c0, 
event=event@entry=0x7fffd8a0) at kernel/qcoreapplication.cpp:935
#9  0x763ddee6 in sendSpontaneousEvent (event=0x7fffd8a0, 
receiver=0x7943c0)
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:240
#10 QGuiApplicationPrivate::processExposeEvent (e=0x62f080)
at kernel/qguiapplication.cpp:2528
#11 0x763dea45 in QGuiApplicationPrivate::processWindowSystemEvent (
e=e@entry=0x62f080) at kernel/qguiapplication.cpp:1566
#12 0x763c54d8 in QWindowSystemInterface::sendWindowSystemEvents (
flags=...) at kernel/qwindowsysteminterface.cpp:579
#13 0x7fffee0ad000 in userEventSourceDispatch (source=optimized out)
at eventdispatchers/qeventdispatcher_glib.cpp:78
#14 0x74512de4 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x74513028 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x745130cc in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x75ef06bc in QEventDispatcherGlib::processEvents (this=0x6ece20, 
flags=...) at kernel/qeventdispatcher_glib.cpp:426
#18 0x75e978eb in QEventLoop::exec (this=this@entry=0x7fffdb60, 
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#19 0x75e9ef46 in QCoreApplication::exec ()
at kernel/qcoreapplication.cpp:1188
#20 0x763d60cc in QGuiApplication::exec ()
at kernel/qguiapplication.cpp:1436
#21 0x76b38e05 in QApplication::exec () at kernel/qapplication.cpp:2749
#22 0x00404301 in main (argc=2, argv=optimized out) at main.cpp:548

I also added one more patch to the qt5-beta1 PPA's qtbase:
https://qt.gitorious.org/qt/qtbase/commit/075c36e39beedb33ec4b239d57075f54acb21acf

Since Maarten experienced a trace that also concerned qtdeclarative (Qt
Quick), it's worth mentioning there's an updated 5.3 branch snapshot
build of qtdeclarative (made compatible with 5.3.0) soon finished
building at: https://launchpad.net/~canonical-
qt5-edgers/+archive/ubuntu/qt5-proper

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

Title:
  qt crashed when switching video out mode to external or internal only
  mode

Status in Checkbox - Graphical Test Runner:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  New
Status in Qt:
  New
Status in “libxcb” package in Ubuntu:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  checkbox-gui crashed with following console outputs:

  pure virtual method called
  terminate called without an active exception
  Aborted (core dumped)

  Steps to reproduce:

  1. open checkbox-gui

  2. connected external display

  3. switch video output mode, usually by using the common video output
  switch hotkey.

  Expected result:

  checkbox-gui still running when switching back to extended desktop
  video out mode.

  Actual result:

  checkbox-gui crashed

  ---
  https://bugreports.qt-project.org/browse/QTBUG-39663

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+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 1290785] Re: Users with UID 60000 are invisible in login and Settings-User unless /etc/login.defs updated

2014-07-10 Thread Robert Euhus

After some more search I found that the original gzipped tar archive that is 
referenced in your new version accountsservice_0.6.35-0ubuntu7.1.dsc differs a 
lot from the xz-compressed original tar used by the old trusty version:
https://launchpad.net/ubuntu/+archive/primary/+files/accountsservice_0.6.35.orig.tar.xz

This is exactly the difference seen in the diff mentioned above.

In the attached accountsservice_0.6.35-0ubuntu7.1.dsc I have just replaced all 
references to the dubios accountsservice_0.6.35.orig.tar.gz by the 
corresponding lines for accountsservice_0.6.35.orig.tar.xz as found in 
https://launchpadlibrarian.net/162749972/accountsservice_0.6.35-0ubuntu7.dsc
(and removed the pgp signature).

With this change the packag compiles cleanly and works as expected.

@Robert: please use the working original tar.xz from the old package and
repost the patch. Thanks.

** Attachment added: accountsservice_0.6.35-0ubuntu7.1.dsc with corrected 
accountsservice_0.6.35.orig.tar.xz
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+attachment/4149542/+files/accountsservice_0.6.35-0ubuntu7.1.dsc

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

Title:
  Users with UID  6 are invisible in login and Settings-User
  unless /etc/login.defs updated

Status in “accountsservice” package in Ubuntu:
  Fix Released
Status in “accountsservice” source package in Trusty:
  Triaged

Bug description:
  [Impact]
  Users of Ubuntu 14.04 LTS with UID  6 will not show in the greeter or 
system settings without editing UID_MAX in /etc/login.defs. This was not 
required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID  
UID_MIN. In 13.10 this was changed to UID  UID_MIN or UID  UID_MAX.

  [Test Case]
  1. Create a user with a UID  UID_MAX:
  $ adduser --uid 60001 big-uid
  2. Restart system
  Expected result:
  big-uid is shown in the greeter. Once logged in big-uid is shown in 
system settings.
  Observed result:
  big-uid is not shown in the greeter (14.04 LTS, 14.10)
  big-uid is not shown in system settings (13.10, 14.04LTS, 14.10)

  [Regression Potential]
  This could cause users that were previously hidden to be shown. This seems 
unlikely to be a problem as all system created user accounts are less than 
UID_MIN and there doesn't seem be a convention to use accounts  UID_MAX for 
this case.

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

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

[Desktop-packages] [Bug 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8

2014-07-10 Thread PS Jenkins bot

Fix committed into lp:mir/devel at revision None, scheduled for release
in mir, milestone Unknown

** Changed in: mir
   Status: In Progress = Fix Committed

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

Title:
  g++-4.9 binary incompatibilties with libraries built with g++-4.8

Status in Mir:
  Fix Committed
Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “firefox” package in Ubuntu:
  New
Status in “gcc-4.9” package in Ubuntu:
  Confirmed
Status in “gcc-defaults” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu:
  Invalid
Status in “mir” package in Ubuntu:
  New
Status in “process-cpp” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New
Status in “unity-scope-click” package in Ubuntu:
  New
Status in “unity-scopes-api” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  New
Status in Debian GNU/Linux:
  New

Bug description:
  The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic,
  when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built
  with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the
  default), fails the package build in its test suite.

   2/14 Test  #2: acceptance_tests ..***Failed   30.54 sec
  DBus daemon: 
unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b
  task-0: Started with PID: 13031
  task-0: [==] Running 2 tests from 1 test case.
  task-0: [--] Global test environment set-up.
  task-0: [--] 2 tests from LocationServiceStandalone
  task-0: [ RUN  ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus

  ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of
  30 seconds.

  (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: 
assertion 'all_tasks(service, all_tasks_finished_helper)' failed
  task-0: Shutting down
  DBus daemon: Shutdown

  This test suite does *not* fail if either dbus-cpp is rebuilt with
  g++-4.9, or if location-service is built with g++-4.8.

  This implies a binary compatibility problem for C++ libraries in g++
  4.9, which is critical to resolve.

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

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

[Desktop-packages] [Bug 1318584] Re: qt crashed when switching video out mode to external or internal only mode

2014-07-10 Thread Maarten Lankhorst

It seems display driver is not important, I always hit this bug it
seems, on nvidia, nouveau, radeon and intel.

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

Title:
  qt crashed when switching video out mode to external or internal only
  mode

Status in Checkbox - Graphical Test Runner:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  New
Status in Qt:
  New
Status in “libxcb” package in Ubuntu:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  checkbox-gui crashed with following console outputs:

  pure virtual method called
  terminate called without an active exception
  Aborted (core dumped)

  Steps to reproduce:

  1. open checkbox-gui

  2. connected external display

  3. switch video output mode, usually by using the common video output
  switch hotkey.

  Expected result:

  checkbox-gui still running when switching back to extended desktop
  video out mode.

  Actual result:

  checkbox-gui crashed

  ---
  https://bugreports.qt-project.org/browse/QTBUG-39663

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+subscriptions

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

[Desktop-packages] [Bug 1299975] Re: wireless script checks wrong sys file

** Also affects: pm-utils (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

Title:
  wireless script checks wrong sys file

Status in “pm-utils” package in Ubuntu:
  Confirmed
Status in “pm-utils” source package in Trusty:
  New

Bug description:
  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does
  not exist.  That happens to be the case for me (intel wireless), which
  the actual location is '/sys/class/net/$1/device/enabled' (enable -
  enabled).

  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless
  issues for others.  My wireless power-saving is correctly turned off
  upon resume now, though (it would get stuck in power-saving mode
  sometimes).

  
  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy pm-utils
  pm-utils:
Installed: 1.4.1-13
Candidate: 1.4.1-13
Version table:
   *** 1.4.1-13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+subscriptions

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

[Desktop-packages] [Bug 1299975] Re: wireless script checks wrong sys file

2014-07-10 Thread Martin Pitt

Thanks! Applied to Debian VCS in http://anonscm.debian.org/gitweb/?p
=collab-maint/pm-utils.git;a=commitdiff;h=d33ba310

** Changed in: pm-utils (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  wireless script checks wrong sys file

Status in “pm-utils” package in Ubuntu:
  Fix Committed
Status in “pm-utils” source package in Trusty:
  New

Bug description:
  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does
  not exist.  That happens to be the case for me (intel wireless), which
  the actual location is '/sys/class/net/$1/device/enabled' (enable -
  enabled).

  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless
  issues for others.  My wireless power-saving is correctly turned off
  upon resume now, though (it would get stuck in power-saving mode
  sometimes).

  
  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy pm-utils
  pm-utils:
Installed: 1.4.1-13
Candidate: 1.4.1-13
Version table:
   *** 1.4.1-13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+subscriptions

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

[Desktop-packages] [Bug 1318584] Re: qt crashed when switching video out mode to external or internal only mode

2014-07-10 Thread Maarten Lankhorst

I think it only depends on whether opengl acceleration is enabled
whether you get the former or latter behavior.

** No longer affects: libxcb (Ubuntu)

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

Title:
  qt crashed when switching video out mode to external or internal only
  mode

Status in Checkbox - Graphical Test Runner:
  Confirmed
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project trusty series:
  New
Status in Qt:
  New
Status in “qtbase-opensource-src” package in Ubuntu:
  Confirmed

Bug description:
  checkbox-gui crashed with following console outputs:

  pure virtual method called
  terminate called without an active exception
  Aborted (core dumped)

  Steps to reproduce:

  1. open checkbox-gui

  2. connected external display

  3. switch video output mode, usually by using the common video output
  switch hotkey.

  Expected result:

  checkbox-gui still running when switching back to extended desktop
  video out mode.

  Actual result:

  checkbox-gui crashed

  ---
  https://bugreports.qt-project.org/browse/QTBUG-39663

To manage notifications about this bug go to:
https://bugs.launchpad.net/checkbox-gui/+bug/1318584/+subscriptions

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

[Desktop-packages] [Bug 1310260] Re: Pulseaudio fails to detect card (probably due to hybrid graphics)

2014-07-10 Thread Paul Konecny

UPDATE:

After reinstalling on a larger SSD the fix mentioned above does not work
anymore. On the other hand installing fglrx deactivates the card
properly but using fglrx gives me unbearable tearing if using the radeon
so this is not an ideal solution.

Btw. will this bug be escalated upstream as it affects not only ubuntu
but vanilla packages as well? Or should I post it to the pulseaudio
bugzilla myself?

Best regards

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

Title:
  Pulseaudio fails to detect card (probably due to hybrid graphics)

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I wanted to install Trusty on my Elitebook 850 G1 with hybrid graphics (Intel 
/ AMD) but pulseaudio goes nuts on me as soon as I try to play any music / 
sound, try to change volume, etc.
  I've tried it with Ubuntu, Kubuntu and now with Xubuntu with the same result 
everytime.

  My guess is that pulseaudio has problems with the AMD GPU and it's sound 
processor being switched off automatically as enabled by Kernel 3.13 (formerly 
achieved by adding the radeon.runpm=1 kernel parameter)
  (http://lists.freedesktop.org/archives/dri-devel/2013-September/045650.html)

  root@HP-EliteBook-850-G1:~# cat /sys/kernel/debug/vgaswitcheroo/switch
  0:IGD:+:Pwr::00:02.0
  1:DIS: :DynOff::03:00.0
  2:DIS-Audio: :Off::03:00.1

  As you can see, the AMD GPU has been turned off automatically. Pulseaudio, 
the (X)Ubuntu volume applet and KMix on the other hand list it as still 
available.
  Based on that I asume pulseaudio tries to access a switched-off device and 
fails.

  I've followed the steps listed
  here: https://wiki.ubuntu.com/DebuggingSoundProblems
  and
  here: https://wiki.ubuntu.com/PulseAudio/Log

  I'll attach the logs right away. (pulseverbose1.log and my dmesg
  output)

  Pusleverbose is full of messages like this one:
  (   0.013|   0.000) I: [pulseaudio] alsa-util.c: Error opening PCM device 
hw:0: No such file or directory

  This output of dmesg also caught my attention:
  [  354.927935] HDMI ATI/AMD: no speaker allocation for ELD
  [  357.695010] hda-intel :03:00.1: Disabling via VGA-switcheroo

  One thing I noticed using Kubuntu is that after pulseaudio becomes 
unresponsive the taskmanager lists 4 pulseaudio processes two of which are 
active on harddrive (Aktiv auf Festplatte). Those two processes cannot be 
killed even as root.
  Currently being on Xubuntu the same thing is true, although it lists only one 
process in the taskmanager that cannot be killed.

  I hope you can help me.

  Best regards,
  Paul

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  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
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', 
'/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Sun Apr 20 13:47:09 2014
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Title: [HP EliteBook 850 G1, IDT 92HD91BXX, Speaker, Internal] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.08
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.54
  dmi.chassis.asset.tag: CNU345BY96
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.08:bd02/19/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3008CC10003:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 850 G1
  dmi.product.version: A3008CC10003
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1299975] Re: wireless script checks wrong sys file

** Description changed:

+ TEST CASE: 
+ - on a machine with a wireless interface, run:  
+   PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex  
/usr/lib/pm-utils/power.d/wireless true
+   and verify that it fails with /sys/class/net/wlan0/device/enable: No such 
file or directory
+ - install the update and run the command again and verify that the script 
continue beyond the point it stopped earlier, i.e. that it stops at a later 
point when running e.g. iwconfig 
+ - now powersaving for wireless via pm-utils should work as intended from the 
script
+ 
+ REGRESSION POTENTIAL:
+ - the functionality in the script was completely broken before, by fixing 
this bug any bug in the power management that were previously hidden may now be 
uncovered. 
+ 
  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does not
  exist.  That happens to be the case for me (intel wireless), which the
  actual location is '/sys/class/net/$1/device/enabled' (enable -
  enabled).
  
  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless issues
  for others.  My wireless power-saving is correctly turned off upon
  resume now, though (it would get stuck in power-saving mode sometimes).
  
- 
  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  
  $ apt-cache policy pm-utils
  pm-utils:
-   Installed: 1.4.1-13
-   Candidate: 1.4.1-13
-   Version table:
-  *** 1.4.1-13 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.4.1-13
+   Candidate: 1.4.1-13
+   Version table:
+  *** 1.4.1-13 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+ 100 /var/lib/dpkg/status

** Changed in: pm-utils (Ubuntu Trusty)
   Status: New = Fix Committed

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

Title:
  wireless script checks wrong sys file

Status in “pm-utils” package in Ubuntu:
  Fix Committed
Status in “pm-utils” source package in Trusty:
  Fix Committed

Bug description:
  TEST CASE: 
  - on a machine with a wireless interface, run:  
PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex  
/usr/lib/pm-utils/power.d/wireless true
and verify that it fails with /sys/class/net/wlan0/device/enable: No such 
file or directory
  - install the update and run the command again and verify that the script 
continue beyond the point it stopped earlier, i.e. that it stops at a later 
point when running e.g. iwconfig 
  - now powersaving for wireless via pm-utils should work as intended from the 
script

  REGRESSION POTENTIAL:
  - the functionality in the script was completely broken before, by fixing 
this bug any bug in the power management that were previously hidden may now be 
uncovered. 

  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does
  not exist.  That happens to be the case for me (intel wireless), which
  the actual location is '/sys/class/net/$1/device/enabled' (enable -
  enabled).

  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless
  issues for others.  My wireless power-saving is correctly turned off
  upon resume now, though (it would get stuck in power-saving mode
  sometimes).

  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy pm-utils
  pm-utils:
    Installed: 1.4.1-13
    Candidate: 1.4.1-13
    Version table:
   *** 1.4.1-13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+subscriptions

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

[Desktop-packages] [Bug 1312135] Re: Under KDE firefox uses nautilus instead of dolphin to handle directories

2014-07-10 Thread Jorge Suárez de Lis

I can't remove it. long story short, I'm in a large network with
multiple computers running Ubuntu, all with the same setup. I can't just
uninstall Nautilus from one of them.

Fortunately, I tried again the workaround and it worked. I probably made
something wrong the first time, sorry. The changes are being rolled out
to all the computers over the network. I hope I won't break anything
with it.

Thanks!

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

Title:
  Under KDE firefox uses nautilus instead of dolphin to handle
  directories

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  1. Run firefox under kde
  2. Download a file with it
  3. Click the download icon
  4. Right click on the download object
  5. Ask to open the containing folder

  I would expect the KDE file browser dolphin to open.

  What instead happens the GNOME file browser nautilus is opened
  without the needed icons. (see screenshot).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: firefox 28.0+build2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
   /dev/snd/controlC0:  enzo   2178 F pulseaudio
enzo   2301 F pulseaudio
  BuildID: 20140410211200
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Thu Apr 24 13:43:20 2014
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2014-04-23 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  IpRoute:
   default via 192.168.254.254 dev eth0  proto static 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1 
   192.168.254.0/24 dev eth0  proto kernel  scope link  src 192.168.254.42  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=28.0/20140410211200
  RfKill:
   
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.01
  dmi.board.asset.tag: CZC3523T17
  dmi.board.name: 18EB
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC3523T17
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.01:bd09/22/2013:svnHewlett-Packard:pnHPProDesk490G1MT:pvr:rvnHewlett-Packard:rn18EB:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP ProDesk 490 G1 MT
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 943104] Re: recipient address: comma inserted when pressing AltGr

2014-07-10 Thread kybernetes

Confirm this bug in Ubuntu 14.04 Evolution 3.10.4, Keyboard German (Austria).
For reproduction it is sufficient to press 'Alt Gr' after at least one 
character in the To field. No further keystrike required. Comma and blank 
appear immediate at keystrike.

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

Title:
  recipient address: comma inserted when pressing AltGr

Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Expired

Bug description:
  I want to send a message using evolution. When I type the recipient address 
pippo.pa...@pluto.com I notice a comma followed by a blank character before the 
@ character, and these two spare characters are inserted every time I press  
AltGr in my keyboard (italian localisation), I experience this behaviour  just 
in A:(TO:)  CC: and CCN: (BCC): fields.
  See the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evolution 3.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  CasperVersion: 1.304
  Date: Wed Feb 29 07:23:44 2012
  LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Beta i386 (20120228.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/943104/+subscriptions

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

[Desktop-packages] [Bug 1340192] [NEW] [K53TA, Realtek ALC269VB, Speaker, Internal ]Totum halts after toiling whit volume slider. windows grey out

2014-07-10 Thread Jan de Jonge

Public bug reported:

Lisend to totum 3.10.1 while usb-creator-kde 0.2.56.1 was running.
Totum sound drop a shot while at shutting down usb-creator-kde. (1.5 sec)
Using the volume slider of Totum did Totum seem to halt. No sound, video halted
First the window greyed out and later closed.
Then a Totum window annoused that it found someting wrong.
Must be mentioned in dmesg for those who can read this.

And just before this all happend i was using Nautilus to move som files around.
This has cased earier this mounth some nautilus stops

Hope this helps
Jan

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jan   17007 F pulseaudio
 /dev/snd/controlC0:  jan   17007 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 10 15:01:05 2014
InstallationDate: Installed on 2014-03-22 (109 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140322)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=nl_NL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 successful
Symptom_Card: Intern geluid - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jan   17007 F pulseaudio
 /dev/snd/controlC0:  jan   17007 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [K53TA, Realtek ALC269VB, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/20/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53TA
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr206:bd07/20/2011:svnASUSTeKComputerInc.:pnK53TA:pvr1.0:rvnASUSTeKComputerInc.:rnK53TA:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K53TA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-bug trusty

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

Title:
  [K53TA, Realtek ALC269VB, Speaker, Internal ]Totum halts after toiling
  whit volume slider. windows grey out

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

Bug description:
  Lisend to totum 3.10.1 while usb-creator-kde 0.2.56.1 was running.
  Totum sound drop a shot while at shutting down usb-creator-kde. (1.5 sec)
  Using the volume slider of Totum did Totum seem to halt. No sound, video 
halted
  First the window greyed out and later closed.
  Then a Totum window annoused that it found someting wrong.
  Must be mentioned in dmesg for those who can read this.

  And just before this all happend i was using Nautilus to move som files 
around.
  This has cased earier this mounth some nautilus stops

  Hope this helps
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jan   17007 F pulseaudio
   /dev/snd/controlC0:  jan   17007 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 10 15:01:05 2014
  InstallationDate: Installed on 2014-03-22 (109 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140322)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 
successful
  Symptom_Card: Intern geluid - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jan   17007 F pulseaudio
   /dev/snd/controlC0:  jan   17007 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [K53TA, Realtek ALC269VB, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 206

[Desktop-packages] [Bug 1315285] Re: [AMD Richland + Mars] Unable to switch graphics

2014-07-10 Thread Chih-Hsyuan Ho

@Yung, if the Switchable Graphics is enabled in BIOS, the PX mode that
AMD referred to should already be there. And according to AMD team,
switchable graphics in AMD Richland should just work.

Can you help provide more info by going through the following commands:

aticonfig --lsa

Is the xorg.conf existent? If not, can you run the following command to
create one?

sudo amdconfig --initial --force --adapter=all

Afterwards, please reboot the system and retest this issue. Thank you.

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

Title:
  [AMD Richland + Mars] Unable to switch graphics

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

Bug description:
  
  Unable to switch in between APU and Discrete GPU.

  
  Step to reproduce:

  Oepn AMD Crystal Control Center,

  $ sudo amdcccle

  
  Expected:
  Switchable graphics settings menu will shown

  
  Actual result:
  Found no switchable graphics settings


  Currently found effected:

  APU:
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Richland [Radeon HD 8450G] [1002:9995]
  with GPU:
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] [1002:6600]


  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 1562 F pulseaudio
   /dev/snd/controlC0:  ubuntu 1562 F pulseaudio
  CRDA:
   country TW:
    (2402 - 2472 @ 40), (3, 27)
    (5270 - 5330 @ 40), (3, 17), DFS
    (5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Fri May  2 15:59:50 2014
  HibernationDevice: RESUME=UUID=be96939f-ffde-4407-a99e-17beebf60ad5
  InstallationDate: Installed on 2014-04-30 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ProBook 445 G1 Notebook PC
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=58dd6874-a445-4c06-ab93-5be7a08a2c62 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CPE Ver. F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1950
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.0B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1NotebookPC:pvrA201BC1203:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 445 G1 Notebook PC
  dmi.product.version: A201BC1203
  dmi.sys.vendor: Hewlett-Packard

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

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

[Desktop-packages] [Bug 1340204] [NEW] nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel module failed to build:

2014-07-10 Thread Guido

Public bug reported:

I don't know what happened in sofware, I had to remove the nvidia card because 
of a final failure; I'm thinking to buy another graphic card, sigh..., while 
using the Mother-board integrated one.
Main data:
Description:Ubuntu 12.04.4 LTS
Release:12.04

nvidia-331-updates:
  Installato: 331.38-0ubuntu0.0.1
  Candidato:  331.38-0ubuntu0.0.1
  Tabella versione:
 *** 331.38-0ubuntu0.0.1 0
500 http://it.archive.ubuntu.com/ubuntu/ precise-updates/restricted 
amd64 Packages
100 /var/lib/dpkg/status

I didn't expect anything (removed card)
The error condition jumped out.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: nvidia-331-updates 331.38-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 3.13.0-31.55~precise2-generic 3.13.11.4
Uname: Linux 3.13.0-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DKMSKernelVersion: 3.5.0-54-generic
Date: Thu Jul 10 16:05:18 2014
InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
MarkForUpload: True
PackageVersion: 331.38-0ubuntu0.0.1
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package precise

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

Title:
  nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel
  module failed to build:

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

Bug description:
  I don't know what happened in sofware, I had to remove the nvidia card 
because of a final failure; I'm thinking to buy another graphic card, 
sigh..., while using the Mother-board integrated one.
  Main data:
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  nvidia-331-updates:
Installato: 331.38-0ubuntu0.0.1
Candidato:  331.38-0ubuntu0.0.1
Tabella versione:
   *** 331.38-0ubuntu0.0.1 0
  500 http://it.archive.ubuntu.com/ubuntu/ precise-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status

  I didn't expect anything (removed card)
  The error condition jumped out.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331-updates 331.38-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.13.0-31.55~precise2-generic 3.13.11.4
  Uname: Linux 3.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DKMSKernelVersion: 3.5.0-54-generic
  Date: Thu Jul 10 16:05:18 2014
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MarkForUpload: True
  PackageVersion: 331.38-0ubuntu0.0.1
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1340204] Re: nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel module failed to build:

2014-07-10 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel
  module failed to build:

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

Bug description:
  I don't know what happened in sofware, I had to remove the nvidia card 
because of a final failure; I'm thinking to buy another graphic card, 
sigh..., while using the Mother-board integrated one.
  Main data:
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  nvidia-331-updates:
Installato: 331.38-0ubuntu0.0.1
Candidato:  331.38-0ubuntu0.0.1
Tabella versione:
   *** 331.38-0ubuntu0.0.1 0
  500 http://it.archive.ubuntu.com/ubuntu/ precise-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status

  I didn't expect anything (removed card)
  The error condition jumped out.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: nvidia-331-updates 331.38-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.13.0-31.55~precise2-generic 3.13.11.4
  Uname: Linux 3.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DKMSKernelVersion: 3.5.0-54-generic
  Date: Thu Jul 10 16:05:18 2014
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MarkForUpload: True
  PackageVersion: 331.38-0ubuntu0.0.1
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.38-0ubuntu0.0.1: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1287753] Re: Please update to 331. 49 and/or provide Nvidia 334.21

2014-07-10 Thread Samuel PHAN

I also join in requesting an update of the nvidia driver 331 or better.
I'm experiencing redrawing/repainting/display corruption of OpenGL
applications when minimized.

http://forums.linuxmint.com/viewtopic.php?f=206t=169316

https://bugs.launchpad.net/linuxmint/+bug/1338744

On NVIDIA forums, this thread seems to indicate that the last NVIDIA
driver 331.89 fixes the problem.

https://devtalk.nvidia.com/default/topic/75/linux/340-17-337-xx-
gtx-750-ti-random-glitches-when-minimizing-opengl-accelerated-
applications/

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

Title:
  Please update to 331. 49 and/or provide Nvidia 334.21

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

Bug description:
  Provide Nvidia 334.21 drivers for ubuntu 14.04 in the xorg-edgers PPA.
  This driver provides alot of performance improvements and new GPUs support.

  Changlog:
  http://www.nvidia.com/download/driverResults.aspx/73666/en-us

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

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

[Desktop-packages] [Bug 1340217] [NEW] [mako] wlan0 state 'unavailable' after flashing

Public bug reported:

After flashing latest image from today, I noticed that on the first boot
the wlan0 device has it state reported as 'unavailable' and thus no WiFi
connection is possible.

urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1


$ nmcli d
DEVICE TYPE  STATE
/ril_0 gsm   connected
wlan0  802-11-wireless   unavailable


$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no


$ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
method return sender=:1.4 - dest=:1.122 reply_serial=2
   variant   int32 0

$ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
method return sender=:1.4 - dest=:1.123 reply_serial=2
   variant   int32 0

$ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
method return sender=:1.4 - dest=:1.124 reply_serial=2
   variant   int32 0


$ sudo system-image-cli -i
current build number: 123
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/utopic-proposed
last update: 2014-07-10 13:20:45
version version: 123
version ubuntu: 20140710
version device: 20140709

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  After flashing latest image from today, I noticed that on the first boot
  the wlan0 device has it state reported as 'unavailable' and thus no WiFi
  connection is possible.
  
  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1
  
- 
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
-variant   int32 0
+    variant   int32 0
  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
-variant   int32 0
- 
+    variant   int32 0
  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
-variant   int32 0
+    variant   int32 0
+ 
+ $ sudo system-image-cli -i
+ current build number: 123
+ device name: mako
+ channel: ubuntu-touch/devel-proposed
+ alias: ubuntu-touch/utopic-proposed
+ last update: 2014-07-10 13:20:45
+ version version: 123
+ version ubuntu: 20140710
+ version device: 20140709

** Description changed:

  After flashing latest image from today, I noticed that on the first boot
  the wlan0 device has it state reported as 'unavailable' and thus no WiFi
  connection is possible.
  
  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1
+ 
+ 
+ $ nmcli d
+ DEVICE TYPE  STATE
+ /ril_0 gsm   connected
+ wlan0  802-11-wireless   unavailable
+ 
+ 
+ $ rfkill list
+ 0: phy0: Wireless LAN
+ Soft blocked: no
+ Hard blocked: no
+ 1: hci0: Bluetooth
+ Soft blocked: no
+ Hard blocked: no
+ 
  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0
  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0
  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0
  
+ 
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

** Attachment added: nmcli_nm.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+attachment/4149619/+files/nmcli_nm.txt

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

** Attachment added: saved-states.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+attachment/4149621/+files/saved-states.txt

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

** Attachment added: rfkill_list.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+attachment/4149620/+files/rfkill_list.txt

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

** Attachment added: urfkill_enumerate.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+attachment/4149623/+files/urfkill_enumerate.txt

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

** Attachment added: nmcli_d.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+attachment/4149618/+files/nmcli_d.txt

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

** Attachment added: syslog.txt
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+attachment/4149622/+files/syslog.txt

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1339189] [NEW] dual monitor mouse speed

You have been subscribed to a public bug:

When you plug in a second monitor the horizontal mouse speed doubles.

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


** Tags: bot-comment
-- 
dual monitor mouse speed
https://bugs.launchpad.net/bugs/1339189
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xinput in Ubuntu.

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

2014-07-10 Thread Tony Espy

I also reproduced it flashing this morning's image with --wipe.  Here's
the output of urfkill's enumerate script and nmcli:

root@ubuntu-phablet:~# /usr/share/urfkill/scripts/enumerate 
/org/freedesktop/URfkill/devices/100
Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100
Printing props for Ofono device: /org/freedesktop/URfkill/devices/100
soft: 0
platform: 0
name: Fake Manufacturer Fake Modem Model
type: 5
urftype: org.freedesktop.URfkill.Device.Ofono
index: 100
/org/freedesktop/URfkill/devices/0
Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0
Printing props for Kernel device: /org/freedesktop/URfkill/devices/0
soft: 0
platform: 1
name: phy0
type: 1
urftype: org.freedesktop.URfkill.Device.Kernel
index: 0
hard: 0
/org/freedesktop/URfkill/devices/1
Printing props for unspecialized device: /org/freedesktop/URfkill/devices/1
Printing props for Kernel device: /org/freedesktop/URfkill/devices/1
soft: 0
platform: 0
name: hci0
type: 2
urftype: org.freedesktop.URfkill.Device.Kernel
index: 1
hard: 0
root@ubuntu-phablet:~# nmcli d
DEVICE TYPE  STATE
/ril_0 gsm   connected
wlan0  802-11-wireless   unavailable  


** Changed in: network-manager (Ubuntu)
   Status: New = Confirmed

** Changed in: network-manager (Ubuntu)
   Importance: Undecided = Critical

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1339183] [NEW] Touchpad overly sensitive and jittery

You have been subscribed to a public bug:

This has been the case in the last few versions of Ubuntu but I had
hoped that it would be fixed in 14.04 LTS.

I have a XPS 15 L521x which has a synaptics touchpad. The touchpad
control is overly sensitive and feels jittery especially when trying to
select text and click on links.

It is very fustrating and makes the operating system unusable at times.

dmesg output for touchpad
[2.898477] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd00123/0x840300/0x126c00, board id: 2080, fw id: 1114765
[2.974217] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5

I've also attached the synclient -l output

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


** Tags: bot-comment
-- 
Touchpad overly sensitive and jittery
https://bugs.launchpad.net/bugs/1339183
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xinput in Ubuntu.

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

[Desktop-packages] [Bug 1340244] [NEW] flickering screen

2014-07-10 Thread Jessie James A. Aton

Public bug reported:

my default screen size resolution is 1366x78 (16:9) , after updating my
intel grahics card there was another screen size resolution showing up
which is 1360x768 (16:9) available in display option.. when i used my
default resolution the screen showing some black screen flickering, even
in some browser like opera developer, in firefox evrything seems fine..
when i used another resolution which is 1360x768 (16:9) evything is ok
but opera developer not ok..

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jul 10 22:54:57 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-29-generic, x86_64: installed
 bbswitch, 0.7, 3.13.0-30-generic, x86_64: installed
 nvidia-331, 331.89, 3.13.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0647]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev ff) (prog-if ff)
InstallationDate: Installed on 2014-06-06 (34 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Acer Aspire V3-571G
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=7e7f70c1-9f23-424d-9cca-d0c03ec8c2ce ro plymouth:debug splash quiet 
drm.debug=0xe acpi_backlight=vendor
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2012
dmi.bios.vendor: Acer
dmi.bios.version: V2.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA50_HC_CR
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.04
dmi.modalias: 
dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnAspireV3-571G:pvrV2.04:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04:
dmi.product.name: Aspire V3-571G
dmi.product.version: V2.04
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54+git20140628.e8c3c135-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 
10.3.0~git20140710.acaed8f4-0ubuntu0sarvatt~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
10.3.0~git20140710.acaed8f4-0ubuntu0sarvatt~trusty
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.4.99+git20140703.c4ae0e2c-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.912+git20140710.8587b2ff-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt
xserver.bootTime: Thu Jul 10 21:35:53 2014
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 intel: Failed to load module dri3 (module does not exist, 0)
 intel: Failed to load module present (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8940 
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: amd64 apport-bug compiz-0.9 possible-manual-nvidia-install 
third-party-packages trusty ubuntu

** Attachment added: Kazam_screenshot_3.png
   
https://bugs.launchpad.net/bugs/1340244/+attachment/4149631/+files/Kazam_screenshot_3.png

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

Title:
  flickering screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  my default screen size resolution is 1366x78 (16:9) , after updating
  my intel grahics card there was another screen size resolution showing
  up which is 1360x768 (16:9) available in display option.. when i used
  my default resolution the screen showing some black screen flickering,
  even in some browser like opera developer, in firefox

[Desktop-packages] [Bug 1339189] Re: dual monitor mouse speed

2014-07-10 Thread donaldinho

** Package changed: ubuntu = xinput (Ubuntu)

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

Title:
  dual monitor mouse speed

Status in “xinput” package in Ubuntu:
  New

Bug description:
  When you plug in a second monitor the horizontal mouse speed doubles.

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

2014-07-10 Thread Parameswaran Sivatharman

This (or a similar issue to bug 1321627) was impacting the wifi network
setup on mako devices for smoke test with image 123. When I tried the
workaround suggested in
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627/comments/17,
the wifi became active and useable

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1339183] Re: Touchpad overly sensitive and jittery

2014-07-10 Thread donaldinho

** Package changed: ubuntu = xinput (Ubuntu)

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

Title:
  Touchpad overly sensitive and jittery

Status in “xinput” package in Ubuntu:
  New

Bug description:
  This has been the case in the last few versions of Ubuntu but I had
  hoped that it would be fixed in 14.04 LTS.

  I have a XPS 15 L521x which has a synaptics touchpad. The touchpad
  control is overly sensitive and feels jittery especially when trying
  to select text and click on links.

  It is very fustrating and makes the operating system unusable at
  times.

  dmesg output for touchpad
  [2.898477] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd00123/0x840300/0x126c00, board id: 2080, fw id: 1114765
  [2.974217] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5

  I've also attached the synclient -l output

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

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

[Desktop-packages] [Bug 317452] Re: Proposal: interactive progress bar

2014-07-10 Thread Bug Watch Updater

** Changed in: gtk
   Status: New = Won't Fix

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

Title:
  Proposal: interactive progress bar

Status in GTK+ GUI Toolkit:
  Won't Fix
Status in “gtk+2.0” package in Ubuntu:
  Triaged

Bug description:
  While installing Ubuntu once more on a friends machine, I thought of the 
interactive progress bar element for wizard-type applications. Basically, it 
should provide very fast intuitive way for the person:
  * to get an idea on how far he/she is in the step-wise process of some sort
  * fast switch to particular relevant step (like go back few steps to change a 
name)
  * ...

  I may sketch it as follows:
  []  [++S1++][++S2][S3][S4][S5]   []

  In the middle there is a progress bar like element, which is composed
  of click-able areas with short description plus a possible mouse-over
  or similar pop-ups with a more elaborate description, so that a person
  may really go back a few steps in one click to change some relevant
  information or do/redo actions on a particular step a while back. On a
  sides - some advance to previous/next step controls.

  In the example above the person is on a current step S2, further steps
  like S3 S4 S5 might be inactive, while activation of active elements
  follows some logic.

  Next, next step:
  []  [++S1++][++S2++][++S3++][++S4]  [S5]   []

  Sometimes, you realize, that you might have given not entirely correct
  response a while back. Here, going with a mouse over the progress bar
  and reading concise descriptions (if short step names is not enough)
  person may be able to go back exactly to required step without
  multiple use of go-back control element.

  In my opinion such a control or set of controls (I do not know how
  complex will it be to implement something like this) might be very
  handy, since user may very fast recognize how far he is in the process
  using just graphical feedback to get an estimate instead of realizing
  what actually step 3 out of 7 means, and additionally go back few
  steps at once.

  Hope, that I made the description and intention clear.

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

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

[Desktop-packages] [Bug 1340244] Re: flickering screen

2014-07-10 Thread Jessie James A. Aton

** Description changed:

  my default screen size resolution is 1366x78 (16:9) , after updating my
  intel grahics card there was another screen size resolution showing up
  which is 1360x768 (16:9) available in display option.. when i used my
  default resolution the screen showing some black screen flickering, even
  in some browser like opera developer, in firefox evrything seems fine..
  when i used another resolution which is 1360x768 (16:9) evything is ok
- but opera developer not ok..
+ but opera developer not ok.. another is that the black line showing up
+ when using screenshot with mouse active
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jul 10 22:54:57 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  bbswitch, 0.7, 3.13.0-29-generic, x86_64: installed
-  bbswitch, 0.7, 3.13.0-30-generic, x86_64: installed
-  nvidia-331, 331.89, 3.13.0-30-generic, x86_64: installed
+  bbswitch, 0.7, 3.13.0-29-generic, x86_64: installed
+  bbswitch, 0.7, 3.13.0-30-generic, x86_64: installed
+  nvidia-331, 331.89, 3.13.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Acer Incorporated [ALI] Device [1025:0647]
-  NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev ff) (prog-if ff)
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Acer Incorporated [ALI] Device [1025:0647]
+  NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-06-06 (34 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Acer Aspire V3-571G
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=7e7f70c1-9f23-424d-9cca-d0c03ec8c2ce ro plymouth:debug splash quiet 
drm.debug=0xe acpi_backlight=vendor
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.04
  dmi.modalias: 
dmi:bvnAcer:bvrV2.04:bd09/14/2012:svnAcer:pnAspireV3-571G:pvrV2.04:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.04:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.04
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54+git20140628.e8c3c135-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.3.0~git20140710.acaed8f4-0ubuntu0sarvatt~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.3.0~git20140710.acaed8f4-0ubuntu0sarvatt~trusty
  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.4.99+git20140703.c4ae0e2c-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.912+git20140710.8587b2ff-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt
  xserver.bootTime: Thu Jul 10 21:35:53 2014
  xserver.configfile: default
  xserver.errors:
-  open /dev/dri/card0: No such file or directory
-  intel: Failed to load module dri3 (module does not exist, 0)
-  intel: Failed to load module present (module does not exist, 0)
+  open /dev/dri/card0: No such file or directory
+  intel: Failed to load module dri3 (module does not exist, 0)
+  intel: Failed to load module present (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id8940 
-  vendor AUO
+  product id8940
+  vendor

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

2014-07-10 Thread Tony Espy

** Tags added: rtm14

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

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

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

[Desktop-packages] [Bug 1340252] [NEW] Error occured during update, package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.s

2014-07-10 Thread Parvez Bukhari

Public bug reported:

Error occured during installation of an software update and in the end a
message that ' Installation of package failed'.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libxml2 2.9.1+dfsg1-3ubuntu4
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
Date: Thu Jul 10 10:50:47 2014
DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4:cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2014-06-19 (20 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
SourcePackage: libxml2
Title: package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libxml2 (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 libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1340252

Title:
  Error occured during update, package libxml2 2.9.1+dfsg1-3ubuntu4
  failed to install/upgrade: cannot copy extracted data for
  './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to '/usr/lib/x86_64
  -linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file or
  stream

Status in “libxml2” package in Ubuntu:
  New

Bug description:
  Error occured during installation of an software update and in the end
  a message that ' Installation of package failed'.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libxml2 2.9.1+dfsg1-3ubuntu4
  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
  Date: Thu Jul 10 10:50:47 2014
  DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2014-06-19 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: libxml2
  Title: package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1340252] Re: Error occured during update, package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.

2014-07-10 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  Error occured during update, package libxml2 2.9.1+dfsg1-3ubuntu4
  failed to install/upgrade: cannot copy extracted data for
  './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to '/usr/lib/x86_64
  -linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file or
  stream

Status in “libxml2” package in Ubuntu:
  New

Bug description:
  Error occured during installation of an software update and in the end
  a message that ' Installation of package failed'.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libxml2 2.9.1+dfsg1-3ubuntu4
  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
  Date: Thu Jul 10 10:50:47 2014
  DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2014-06-19 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: libxml2
  Title: package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1339961] Re: chromium-browser crashed with SIGABRT

2014-07-10 Thread Cristian Aravena Romero

** Information type changed from Private to Public

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

Title:
  chromium-browser crashed with SIGABRT

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

Bug description:
  Open dropbox and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  Uname: Linux 3.16.0-031600rc4-lowlatency x86_64
  ApportVersion: 2.14.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Jul  9 21:49:02 2014
  Desktop-Session:
   DESKTOP_SESSION = gnome
   XDG_CONFIG_DIRS = /etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = /usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2014-04-27 (73 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  ProcCmdline: chromium-browser\ 
--ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so\ 
--ppapi-flash-version=13.0.0.206\ --enable-pinch
  Signal: 6
  SourcePackage: chromium-browser
  StacktraceTop:
   
  Title: chromium-browser crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-27T17:58:46.529285

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

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

[Desktop-packages] [Bug 1287753] Re: Please update to 331. 49 and/or provide Nvidia 334.21

2014-07-10 Thread Jaime Marques

nv 340.24 is the lastest long lived driver so im expencting it to land
on the archives soon...

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

Title:
  Please update to 331. 49 and/or provide Nvidia 334.21

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

Bug description:
  Provide Nvidia 334.21 drivers for ubuntu 14.04 in the xorg-edgers PPA.
  This driver provides alot of performance improvements and new GPUs support.

  Changlog:
  http://www.nvidia.com/download/driverResults.aspx/73666/en-us

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

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

[Desktop-packages] [Bug 1340272] [NEW] Synergy stuck bottom right

2014-07-10 Thread Érico Boskovisch

Public bug reported:

I have been using synergy for some time, between a Windows 8.1 machine
to control a Ubuntu 12.04 LTS, from today I can use it properly, the
mouse icon is stuck in bottom right screen, keyboard works fine, but not
the mouse.

Windows Machine is the server and is placed in the right side, Ubuntu
12.04 is the client, and is placed in the left side. I´ve tried
uninstalling, rebooting, using different versions of synergy (1.4.10,
1.4.18 and 1.5) all of them present the same bug.

synergy logs show me this information when I move the cursor to the
Ubuntu Machine:


DEBUG1: try to leave ericom-T420 on right
DEBUG1: no neighbor right
DEBUG2: clamp to right of ericom-T420
DEBUG2: clamp to bottom of ericom-T420
DEBUG2: onMouseMoveSecondary +176,+101
DEBUG2: find neighbor on right of ericom-T420
DEBUG2: no neighbor on right of ericom-T420
DEBUG1: try to leave ericom-T420 on right

(ericom-T420 is the Ubuntu Machine)

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

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

Title:
  Synergy stuck bottom right

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

Bug description:
  I have been using synergy for some time, between a Windows 8.1 machine
  to control a Ubuntu 12.04 LTS, from today I can use it properly, the
  mouse icon is stuck in bottom right screen, keyboard works fine, but
  not the mouse.

  Windows Machine is the server and is placed in the right side, Ubuntu
  12.04 is the client, and is placed in the left side. I´ve tried
  uninstalling, rebooting, using different versions of synergy (1.4.10,
  1.4.18 and 1.5) all of them present the same bug.

  synergy logs show me this information when I move the cursor to the
  Ubuntu Machine:

  
  DEBUG1: try to leave ericom-T420 on right
  DEBUG1: no neighbor right
  DEBUG2: clamp to right of ericom-T420
  DEBUG2: clamp to bottom of ericom-T420
  DEBUG2: onMouseMoveSecondary +176,+101
  DEBUG2: find neighbor on right of ericom-T420
  DEBUG2: no neighbor on right of ericom-T420
  DEBUG1: try to leave ericom-T420 on right

  (ericom-T420 is the Ubuntu Machine)

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

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

[Desktop-packages] [Bug 1340249] Re: No volume control over speakerphone

2014-07-10 Thread Bill Filler

this is not a dialer bug, but backend

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

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

** Tags added: rtm14

** No longer affects: dialer-app

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

Title:
  No volume control over speakerphone

Status in “android” package in Ubuntu:
  New
Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  When putting the phone in speakerphone mode, there's no way to adjust
  the volume of the call.

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

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

[Desktop-packages] [Bug 1305798] Re: [Dell Mini Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, dropouts or crackling sound

2014-07-10 Thread Soko

** Summary changed:

- [Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, dropouts or 
crackling sound
+ [Dell Mini Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, 
dropouts or crackling sound

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

Title:
  [Dell Mini Inspiron 1010, Realtek ALC269, Speaker, Internal]
  Underruns, dropouts or crackling sound

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

Bug description:
  Crackling audio ever since installed on both Ubuntu 12.04 and Linux
  Lite 1.0.8 alongside WinXP SP3.  Windows stills works fine.  Codec
  ALC269, I can find no relevant model configuration that fits my
  computer properly.  Though, I do know it's possible to have perfect
  sound as it happened once.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-18-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  heat   1892 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xd83a irq 22'
 Mixer name : 'Silicon Image SiI1392 HDMI'
 Components : 'HDA:10ec0269,102802c6,0014 
HDA:10951392,,0010'
 Controls  : 36
 Simple ctrls  : 14
  CheckboxSubmission: ebbf4fe7cec14300c941675a1c212902
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Thu Apr 10 12:31:51 2014
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 
(20140204)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or crackling sound
  Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: **
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: **
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd10/27/2009:svnDellInc.:pnInspiron1010:pvrA11:rvnDellInc.:rn**:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Inspiron 1010
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-04-10T12:31:15.990751

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing

2014-07-10 Thread Mathieu Trudel-Lapierre

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

** Changed in: network-manager (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  [mako] wlan0 state 'unavailable' after flashing

Status in “network-manager” package in Ubuntu:
  In Progress

Bug description:
  After flashing latest image from today, I noticed that on the first
  boot the wlan0 device has it state reported as 'unavailable' and thus
  no WiFi connection is possible.

  urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1

  
  $ nmcli d
  DEVICE TYPE  STATE
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable

  
  $ rfkill list
  0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  1: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.122 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.123 reply_serial=2
     variant   int32 0

  $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill 
/org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get 
string:org.freedesktop.URfkill.Killswitch string:state
  method return sender=:1.4 - dest=:1.124 reply_serial=2
     variant   int32 0

  
  $ sudo system-image-cli -i
  current build number: 123
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/utopic-proposed
  last update: 2014-07-10 13:20:45
  version version: 123
  version ubuntu: 20140710
  version device: 20140709

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

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

This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1

---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Bump version to 0.9.11.1.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Jul 2014 
11:51:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
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 Released

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://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.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

This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1

---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Bump version to 0.9.11.1.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Jul 2014 
11:51:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/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 Released
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 Released
Status in “unity” source package in Trusty:
  Confirmed

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://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.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

This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1

---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Bump version to 0.9.11.1.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Jul 2014 
11:51:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
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 Released

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://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.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 347390] Re: Compiz can't resize a window vertically AND horizontally with keyboard.

This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1

---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Bump version to 0.9.11.1.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Jul 2014 
11:51:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
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 Released

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://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.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 1063617] Re: 1:0.9.8+bzr3319-0ubuntu1 regression: keeps setting gsettings keys to wrong values

This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1

---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Bump version to 0.9.11.1.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Jul 2014 
11:51:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
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 Released

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://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.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

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

This bug was fixed in the package compiz -
1:0.9.11.1+14.04.20140701-0ubuntu1

---
compiz (1:0.9.11.1+14.04.20140701-0ubuntu1) trusty; urgency=medium

  [ Chris Townsend ]
  * Bump version to 0.9.11.1.

  [ Ubuntu daily release ]
  * New rebuild forced
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Tue, 01 Jul 2014 
11:51:26 +

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
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 Released

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://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.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 1288747] Re: [334] Parts of the UI randomly flicker when moving the mouse

2014-07-10 Thread Richard Illes

nv 340.24 got pushed to the xserve ppa yesterday and I updated to 340.24 and 
after a full day of use the issues I had appear to be gone.
The issues were: screen shaking or wiggling text on web pages in addition 
to the flicking of random UI elements.

stock compiz was untouched.  Ubuntu 14.04 using a Geforce GTX750 (which
forced me to use 331.x or higher).

-- 
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] [Bug 1340252] Re: Error occured during update, package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.

2014-07-10 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: libxml2 (Ubuntu)
   Importance: Undecided = Low

** Changed in: libxml2 (Ubuntu)
   Status: New = Invalid

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

Title:
  Error occured during update, package libxml2 2.9.1+dfsg1-3ubuntu4
  failed to install/upgrade: cannot copy extracted data for
  './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to '/usr/lib/x86_64
  -linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file or
  stream

Status in “libxml2” package in Ubuntu:
  Invalid

Bug description:
  Error occured during installation of an software update and in the end
  a message that ' Installation of package failed'.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libxml2 2.9.1+dfsg1-3ubuntu4
  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
  Date: Thu Jul 10 10:50:47 2014
  DuplicateSignature: package:libxml2:2.9.1+dfsg1-3ubuntu4:cannot copy 
extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2014-06-19 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: libxml2
  Title: package libxml2 2.9.1+dfsg1-3ubuntu4 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1' to 
'/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.1.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1296506] Re: [Dell Inspiron N5425] Unable to adjust brightness after suspend

2014-07-10 Thread Michele Roviello

I confirm, the beta fixes the issue.

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

Title:
  [Dell Inspiron N5425] Unable to adjust brightness after suspend

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

Bug description:
  CID: 201206-11418 Dell Inspiron N5425

  With the proprietary driver:
  ii  fglrx-updates  2:13.125-0ubuntu0.0.1  Video driver for the AMD 
graphics accelerators
  The brightness cannot be adjusted after suspend.

  Steps:
  1. Install 12.04.4 + fglrx-updates, boot to desktop
  2. Suspend and wake the system up.
  3. Try to adjust the brightness with the hotkey and the applet

  Expected result:
  * The screen backlight could be adjusted.

  Actual result:
  * Brightness cannot be adjusted by any means, the brightness level indicator 
would change with the hotkey press

  Debugging Information:
  ubuntu@201206-11418:~/Desktop$ lspci -nn | grep 300
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Trinity [Radeon HD 7640G] [1002:9903]
  01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841]

  ubuntu@201206-11418:/sys/class/backlight$ l
  acpi_video0@  acpi_video1@

  Tried to write brightness level value into the Brightness file in
  the above directories, not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: fglrx-updates 2:13.125-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Fri Mar 21 06:09:27 2014
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fglrx-installer-updates
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1299975] Re: wireless script checks wrong sys file

** Branch linked: lp:debian/pm-utils

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

Title:
  wireless script checks wrong sys file

Status in “pm-utils” package in Ubuntu:
  Fix Committed
Status in “pm-utils” source package in Trusty:
  Fix Committed

Bug description:
  TEST CASE: 
  - on a machine with a wireless interface, run:  
PM_FUNCTIONS=/usr/lib/pm-utils/functions sh -ex  
/usr/lib/pm-utils/power.d/wireless true
and verify that it fails with /sys/class/net/wlan0/device/enable: No such 
file or directory
  - install the update and run the command again and verify that the script 
continue beyond the point it stopped earlier, i.e. that it stops at a later 
point when running e.g. iwconfig 
  - now powersaving for wireless via pm-utils should work as intended from the 
script

  REGRESSION POTENTIAL:
  - the functionality in the script was completely broken before, by fixing 
this bug any bug in the power management that were previously hidden may now be 
uncovered. 

  On Trusty (beta), while trying to diagnose an issue with the wireless
  not connecting upon resume from standby, I discovered an invalid check
  in '/usr/lib/pm-utils/power.d/wireless'.  The script checks
  '/sys/class/net/$1/device/enable' to see if the wireless device is
  enabled, failing to perform any configuration if this sys file does
  not exist.  That happens to be the case for me (intel wireless), which
  the actual location is '/sys/class/net/$1/device/enabled' (enable -
  enabled).

  Changing the script to use the correct location has not fixed my
  wireless resume issue, but perhaps it is contributing to wireless
  issues for others.  My wireless power-saving is correctly turned off
  upon resume now, though (it would get stuck in power-saving mode
  sometimes).

  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy pm-utils
  pm-utils:
    Installed: 1.4.1-13
    Candidate: 1.4.1-13
    Version table:
   *** 1.4.1-13 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1299975/+subscriptions

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

[Desktop-packages] [Bug 1220426] Re: [nvidia-prime]Freeze while using touchpad

2014-07-10 Thread Ken McWilliams

Issue not resolved however I did test for a very considerable period of
time before the issue surfaced. The issue seems to be greatly reduced
but not removed.

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

Title:
  [nvidia-prime]Freeze while using touchpad

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

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: 
touchpad found each time I did a VT switch and regained control.

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

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

[Desktop-packages] [Bug 1184160] Re: multitouch - not all 3 finger actions working

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

** This bug has been marked a duplicate of bug 1172172
   Some multitouch gestures not working on 13.04

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

Title:
  multitouch - not all 3 finger actions working

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  New

Bug description:
  As reported on https://wiki.ubuntu.com/Multitouch, the following 3
  gestures are not working (and they are the ones I find most useful):

  3 finger pinch to maximize/restore windows
  3 finger press and drag to move window
  3 finger touch to show grab handles 

  The other 3 finger gestures appear to be working (although I don't
  really want to use them).

  I have followed instructions as on 
https://wiki.ubuntu.com/DebuggingTouchpadDetection
  and am attaching the appropriate files.

  Laptop model: Asus N56VJ
  Running kernel: 3.9.0-rc6-custom+ (from Aaron Lu git branch)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu6
  Uname: Linux 3.9.0-rc6-custom+ x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sat May 25 16:40:43 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  InstallationDate: Installed on 2013-05-15 (10 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. N56VJ
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-rc6-custom+ 
root=UUID=e16af3ef-7f12-4a5d-9a73-a494b86af80e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VJ.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VJ.203:bd08/29/2012:svnASUSTeKCOMPUTERINC.:pnN56VJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VJ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.43-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sat May 25 15:50:12 2013
  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.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1184160/+subscriptions

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

[Desktop-packages] [Bug 1319574] Re: 3 finger drag does not work on 14.04

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

** This bug has been marked a duplicate of bug 1172172
   Some multitouch gestures not working on 13.04

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

Title:
  3 finger drag does not work on 14.04

Status in “unity” package in Ubuntu:
  New

Bug description:
  I'm using a Mid 2010 MacBook Pro, and the three-finger drag on the
  trackpad does not work.

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

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

[Desktop-packages] [Bug 921592] Re: multi-touch dash and window drag broken

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

** This bug is no longer a duplicate of bug 940612
   three-finger move does not move (Precise)
** This bug has been marked a duplicate of bug 1172172
   Some multitouch gestures not working on 13.04

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

Title:
  multi-touch dash and window drag broken

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

Bug description:
  I upgraded a few days ago and now I realise that 4-finger tap does not
  bring up the dash, 3-fingers do not drag windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
  Uname: Linux 3.2.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,resize,mousepoll,imgpng,move,regex,grid,unitymtgrabhandles,snap,place,wall,vpswitch,commands,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  Date: Wed Jan 25 09:25:44 2012
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-01-19 (6 days ago)

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

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

[Desktop-packages] [Bug 889144] Re: Three-finger window drag no longer works

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

** This bug has been marked a duplicate of bug 1172172
   Some multitouch gestures not working on 13.04

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

Title:
  Three-finger window drag no longer works

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

Bug description:
  I have a summer-2009 MacBook Pro that I've been upgrading to beta
  Ubuntu versions (as per policy) since it was new.  In Natty's Unity I
  could drag windows around and resize them with a 3-finger gesture,
  without clicking.

  In Oneiric, this no longer seems to work.  That's a shame; my trackpad
  and wrists are suffering as a result.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.24.0-0ubuntu2b1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  CheckboxSubmission: e56271c144a9c8f9f675c77e2e4edb56
  CheckboxSystem: 7e42599bda39ea7ff8b528272b6ef52b
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,mousepoll,place,vpswitch,regex,animation,move,resize,gnomecompat,snap,grid,imgpng,unitymtgrabhandles,wall,session,workarounds,fade,resizeinfo,expo,scale,ezoom,unityshell]
  Date: Fri Nov 11 21:55:56 2011
  ProcEnviron:
   LC_TIME=en_DK.UTF-8
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to oneiric on 2011-09-02 (70 days ago)

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

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

[Desktop-packages] [Bug 1310514] Re: On startup the volume settings are not correctly restored

2014-07-10 Thread Brian Teague

I would note that I'm also using a digital (SPDIF/optical) output.  The
next time I restart I'll check the analog outputs too.

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

Title:
  On startup the volume settings are not correctly restored

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  Whenever I start my pc the sound indicator show the volume I had, when
  I shutdown the PC. But the actual volume is at maximum.

  When I increase the volume by pressing volume up button, the sound
  volume jump to the new volume setting. But in the end the volume is
  decreased.

  The bug is reproducible on every restart.
  My TV is connected over a HDMI cable to my pc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: tbs6982fe tbs6680fe tbs6923fe wl tbs6985se tbs6928se 
tbs6982se tbs6991fe tbs6618fe tbs6922fe tbs6928fe tbs6991se
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mat2730 F pulseaudio
   /dev/snd/controlC0:  mat2730 F pulseaudio
   /dev/snd/pcmC0D8p:   mat2730 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 21 10:37:20 2014
  InstallationDate: Installed on 2014-03-30 (21 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140329)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: Z87E-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd06/25/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87E-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Desktop-packages] [Bug 940612] Re: three-finger move does not move (Precise)

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

** This bug has been marked a duplicate of bug 1172172
   Some multitouch gestures not working on 13.04

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

Title:
  three-finger move does not move (Precise)

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

Bug description:
  On my MacBook Pro 5,3 on today's Precise, using a three finger drag
  does not move any windows (though it does turn the pointer into a
  fist).  Please let me know what additional details I may provide.

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

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

[Desktop-packages] [Bug 1340217] Re: [mako] wlan0 state 'unavailable' after flashing