[Desktop-packages] [Bug 1378660] [NEW] Notification appears when applications need to be (re-)authorized

2014-10-08 Thread Alberto Mardegan 
Public bug reported:

Whenever the OAuth flow needs to be started on behalf of an application, we 
emit a notification which, if clicked, will initiate the OAuth flos in a 
separate window.
However, if the client application has its own visible window, the 
authentication window could (and should, according to design) be happening as a 
prompt session on top of the application.

In order to do so, we need signond to pass the PID of the client
application, and online-accounts-ui to create a prompt session for it.

** Affects: ubuntu-system-settings-online-accounts
 Importance: High
 Assignee: Alberto Mardegan (mardy)
 Status: Confirmed

** Affects: signon (Ubuntu)
 Importance: Undecided
 Assignee: Alberto Mardegan (mardy)
 Status: In Progress

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Assignee: Alberto Mardegan (mardy)
 Status: Confirmed

** Branch linked: lp:~online-accounts/signon/packaging

** Also affects: ubuntu-system-settings-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-system-settings-online-accounts
   Importance: Undecided
   Status: New

** Changed in: ubuntu-system-settings-online-accounts
   Status: New => Confirmed

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

** Changed in: ubuntu-system-settings-online-accounts
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: signon (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: ubuntu-system-settings-online-accounts
   Importance: Undecided => High

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

** Changed in: signon (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-system-settings-online-accounts (Ubuntu)
   Status: New => Confirmed

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

Title:
  Notification appears when applications need to be (re-)authorized

Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in “signon” package in Ubuntu:
  In Progress
Status in “ubuntu-system-settings-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Whenever the OAuth flow needs to be started on behalf of an application, we 
emit a notification which, if clicked, will initiate the OAuth flos in a 
separate window.
  However, if the client application has its own visible window, the 
authentication window could (and should, according to design) be happening as a 
prompt session on top of the application.

  In order to do so, we need signond to pass the PID of the client
  application, and online-accounts-ui to create a prompt session for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1378660/+subscriptions

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

[Desktop-packages] [Bug 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected

2014-10-08 Thread Ricardo Salveti 
Fixes available at https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/landing-019/

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-touch-session (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Music playback does not re-route audio when Bluetooth speaker
  connected/disconnected

Status in “pulseaudio” package in Ubuntu:
  In Progress
Status in “ubuntu-touch-session” package in Ubuntu:
  In Progress

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth speaker is connected/disconnected to the krillin, the music 
playback route does not automatically update to accomodate this. The music app 
must be re-started for the new configuration to work.

  STEPS:
  1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss)
  2) Start music playback
  3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings

  EXPECTED RESULT:
  The music should play back through the Bluetooth speaker until it is 
disconnected. When the speaker is disconnected it should revert to using the 
krillin loud speaker.

  ACTUAL RESULT:
  The music plays back through the Bluetooth speaker until it is disconnected. 
When the speaker is disconnected, there is no music heard from the krillin. The 
music app is still playing the track as the progress bar is still updating, but 
there is no sound.

  When the music app is re-started, music will play through the krillin
  loud speaker.

  NOTES:
  The same problem is observed for the opposite situation where a Bluetooth 
speaker is connected to the device when it is already playing music through the 
krillin loud speaker. The Bluetooth speaker will only be used once the music 
app is restarted.

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

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

[Desktop-packages] [Bug 1341155] Re: Xorg crashed with SIGABRT in pci_device_next() with mesa utils

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

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

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

Title:
  Xorg crashed with SIGABRT in pci_device_next() with mesa utils

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

Bug description:
  came up when i installed mesa utils with nvidia optimus graphic card
  and i was testing it happend when i change from nvidia to intel after
  i tested glxgears

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.15.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Sat Jul 12 18:22:19 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1af2]
  InstallationDate: Installed on 2014-07-10 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: ASUSTeK Computer Inc. UL30VT
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic 
root=UUID=b797dc1a-0cba-433f-89ce-7fb6e4f6d4c9 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   pci_device_find_by_slot () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   pci_device_vgaarb_init () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   ?? ()
   xf86BusConfig ()
  Title: Xorg crashed with SIGABRT in pci_device_next()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 211
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UL30VT
  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.:bvr211:bd07/14/2010:svnASUSTeKComputerInc.:pnUL30VT:pvr1.0:rvnASUSTeKComputerInc.:rnUL30VT:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UL30VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.54-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Jul 12 18:22:34 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4140 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu8

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

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

[Desktop-packages] [Bug 1378665] Re: Xorg crashed with SIGABRT in pci_device_next()

2014-10-08 Thread Apport retracing service 
*** This bug is a duplicate of bug 1341155 ***
https://bugs.launchpad.net/bugs/1341155

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1341155, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1378665/+attachment/4228139/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1341155
   Xorg crashed with SIGABRT in pci_device_next() with mesa utils

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Xorg crashed with SIGABRT in pci_device_next()

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

Bug description:
  There is a message indicating that the system cannot find the back
  light controler.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Wed Oct  8 08:03:53 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:216c]
 Subsystem: Hewlett-Packard Company Device [103c:216c]
  InstallationDate: Installed on 2014-09-28 (9 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic.efi.signed 
root=UUID=0b66c77e-1489-4205-ac58-a12830847857 ro recovery nomodeset
  Renderer: Software
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   pci_device_find_by_slot () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   pci_device_vgaarb_init () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   ?? ()
   xf86BusConfig ()
  Title: Xorg crashed with SIGABRT in pci_device_next()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd06/03/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216C:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  version.xserver-xorg-core: xserver-xo

[Desktop-packages] [Bug 1377847] Re: unity screen saver no longer blanks nor locks automatically

2014-10-08 Thread Seth Arnold 
Thanks Tim, I'll go undup my bug again.

** Tags removed: trusty

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

Title:
  unity screen saver no longer blanks nor locks automatically

Status in “gnome-desktop3” package in Ubuntu:
  Confirmed
Status in “gnome-desktop3” source package in Utopic:
  Confirmed

Bug description:
  After updating over the weekend the screen saver is no longer blanking
  or locking.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Oct  6 09:44:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-06-20 (472 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2013-11-10 (329 days ago)

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

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

[Desktop-packages] [Bug 1311515] Re: Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

2014-10-08 Thread Bin Li 
L.D

 What's script do you run? Do you need more information? Thanks!

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

Title:
  Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Confirmed

Bug description:
  [Test details]
  Image: 14.04 LTS
  Platforms:
  ThinkPad-Edge-E531:~$ dmesg | grep -i syn
  [4.135984] hda_codec: Enable sync_write for stable communication
  [4.846020] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd001a3/0x940300/0x127c00, board id: 2722, fw id: 1310036
  [4.846024] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [4.906051] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input6

  [Steps]
  1. install image kittyhawk-trusty-amd64-iso-20140314-1.iso via bootable USB 
or DVD
  2. launch google maps in web browser
  3. pinch touchpad with two fingers and see if map zooms in & out accordingly

  [Expected result]
  map should zoom-in when user pinches two fingers apart, zoom-out when user 
pinches two fingers together.

  [Actual result]
  sometimes zoom in & out behavior is reversed.

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

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

[Desktop-packages] [Bug 1375445] Re: No phonetic Russian layout for azerty keyboards

2014-10-08 Thread Raphaël Jakse 
I reported this in the Freedesktop's Bugzilla, (hopefully) following the
rules for suggesting a new layout. I think this bug is not relevant
anymore. Closing it.

Thanks William Lee for having taken the time to look at my report.

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

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

Title:
  No phonetic Russian layout for azerty keyboards

Status in “xkeyboard-config” package in Ubuntu:
  Invalid

Bug description:
  Users of azerty keyboards lack of Russian phonetic layout. Their only option 
is to use phonetic qwerty. This is not really acceptable, so I propose to add 
support with the attached patches for azerty Russian phonetic wit the following 
variants:
   - ru(phonetic_azerty): basic phonetic azerty
   - ru(phonetic_winkeys_azerty): basic phonetic azerty, with WinKeys
   - ru(phonetic_fr): French specific phonetic azerty. This 
completes the 3rd level  following the French layout (Alt Gr + a key) 
   - ru(phonetic_winkeys_fr): same, with WinKeys

  base.xml.patchpatches   /usr/share/X11/xkb/rules/base.xml
  base.lst.patchpatches   /usr/share/X11/xkb/rules/base.lst
  evdev.xml.patch   patches   /usr/share/X11/xkb/rules/evdev.xml
  ru.patch  patches   /usr/share/X11/xkb/symbols/ru

  Please tell me if anything is wrong or could be improved. Please also
  note that I know almost nothing of the Russian language and its
  Cyrillic alphabet so there could be errors.

  We also could want to add this layout for users coming from Windows
  and used to it : http://tnit.fr/aa.htm

  Cheers,
  Raphaël.

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

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

[Desktop-packages] [Bug 1375445] Re: No phonetic Russian layout for azerty keyboards

2014-10-08 Thread Raphaël Jakse 
https://bugs.freedesktop.org/show_bug.cgi?id=84789

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  No phonetic Russian layout for azerty keyboards

Status in “xkeyboard-config” package in Ubuntu:
  Invalid

Bug description:
  Users of azerty keyboards lack of Russian phonetic layout. Their only option 
is to use phonetic qwerty. This is not really acceptable, so I propose to add 
support with the attached patches for azerty Russian phonetic wit the following 
variants:
   - ru(phonetic_azerty): basic phonetic azerty
   - ru(phonetic_winkeys_azerty): basic phonetic azerty, with WinKeys
   - ru(phonetic_fr): French specific phonetic azerty. This 
completes the 3rd level  following the French layout (Alt Gr + a key) 
   - ru(phonetic_winkeys_fr): same, with WinKeys

  base.xml.patchpatches   /usr/share/X11/xkb/rules/base.xml
  base.lst.patchpatches   /usr/share/X11/xkb/rules/base.lst
  evdev.xml.patch   patches   /usr/share/X11/xkb/rules/evdev.xml
  ru.patch  patches   /usr/share/X11/xkb/symbols/ru

  Please tell me if anything is wrong or could be improved. Please also
  note that I know almost nothing of the Russian language and its
  Cyrillic alphabet so there could be errors.

  We also could want to add this layout for users coming from Windows
  and used to it : http://tnit.fr/aa.htm

  Cheers,
  Raphaël.

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

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

[Desktop-packages] [Bug 1360303] Re: [SB-XFi - Creative X-Fi, playback] No automute when headphones are plugged in

2014-10-08 Thread Anthony Tiongson 
I'm using a X-fi titanium fatal1ty with the front panel audio drive and
Ubuntu 14.04. No autodetect/mute speakers for whenever I plug in my
headphones into the front panel.

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

Title:
  [SB-XFi - Creative X-Fi, playback] No automute  when headphones are
  plugged in

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

Bug description:
  Dell XPS 720.  fresh install 14.04 all updates.   10.04 was previous
  OS and did not have this problem.  plugging in headphones has no
  effect on the sound coming from the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 22 10:41:50 2014
  InstallationDate: Installed on 2014-08-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Juniper HDMI Audio [Radeon HD 5700 Series] - HDA ATI HDMI
  Symptom_Type: No auto-mute between outputs
  Title: [SB-XFi - Creative X-Fi, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0YU822
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/01/2008:svnDellInc.:pnDellXPS720:pvr:rvnDellInc.:rn0YU822:rvrA00:cvnDellInc.:ct7:cvr:
  dmi.product.name: Dell XPS720
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1373404] Re: No warning of high volume level

2014-10-08 Thread Albert Astals Cid 
As spaniard and thus still someone in the EU here is the behaviour of
the phones i have around me with headset attached:

Shows a notification at 70/80% that doesn't let you increase the volume unless 
you say "ok, sure"
 * Blackberry Z10
 * Nexus 4 with Android 4.4
 * Unknown manufacturer with Android 4.2

Shows a notification at 70/80% that says "your volume is high, don't listen to 
it during a long time"
 * Some old Samsung with Android 2.x

Shows nothing:
 * Some old Samsung with Android 2.x
 * HUAWEI U8815N with Android 4.0.x
 * HTC One S with Android 4.0.x

Some of those that show nothing may have been rooted with non european
version of firmware or are "too old"

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

Title:
  No warning of high volume level

Status in Ubuntu UX bugs:
  Fix Committed
Status in “pulseaudio” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  For the purpose of this Decision, a ‘personal music player’ means a
  portable device, that is not covered by Directive 1999/5/EC or
  Directive 2006/95/EC, with headphones or earphones, used to listen to
  recorded, generated or broadcasted sound.

  1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the
  safety requirement for personal music players shall be the following:
  Personal music players shall be designed and manufactured in a manner
  that ensures that, under reasonably foreseeable conditions of use,
  they are inherently safe and do not cause hearing damage.

  2. The requirement set out in paragraph 1 shall include in particular
  the following:

  (1) Exposure to sound levels shall be time limited to avoid hearing
  damage. At 80 dB(A) exposure time shall be limited to 40 hours/week,
  whereas at 89 dB(A) exposure time shall be limited to 5 hours/week.
  For other exposure levels a linear intra- and extrapolation applies.
  Account shall be taken of the dynamic range of sound and the
  reasonably foreseeable use of the products.

  (2) Personal music players shall provide adequate warnings on the risks 
involved in using the device and to the ways of avoiding them and information 
to users in cases where exposure poses a risk of hearing damage.
  

  Related documents:
  http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/
  http://europa.eu/rapid/press-release_IP-08-1492_en.htm
  http://ec.europa.eu/news/environment/090928_en.htm
  http://europa.eu/rapid/press-release_IP-09-1364_en.htm

  Design:

  : "Whenever you are using
  headphones, Ubuntu should frequently measure the volume of sound
  output. Whenever it is over 47 dB(A), your quota should be reduced
  accordingly..."

  [Originally reported in private bug 1370591.]

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

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

[Desktop-packages] [Bug 1378416] Re: turned off wifi to test 3g I see H in the indicator but I recieve nothing from the system

2014-10-08 Thread Dave Morley 
** 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/1378416

Title:
  turned off wifi to test 3g I see H in the indicator but I recieve
  nothing from the system

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

Bug description:
  STEPS:
  1. Install RTM88 on krillin
  2. Use the system a litlle on wifi
  3. Pull down the indicator network
  4. Disable Wifi

  EXPECTED:
  I expect the system to seemless flip over to using 3g

  ACTUAL:
  I got no page (see screen shot) I tried pinging google and got ping: unknown 
host google.com

  ip route gave no feedback
  phablet@ubuntu-phablet:~$ nmcli dev
  DEVICE TYPE  STATE
  /ril_1 gsm   disconnected 
  /ril_0 gsm   connected
  wlan0  802-11-wireless   unavailable 

  Devices is correct.

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

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

[Desktop-packages] [Bug 1373404] Re: No warning of high volume level

2014-10-08 Thread Albert Astals Cid 
Shows nothing:
 * iPhone 5S bought in the USA (so may have not the EU law applied)

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

Title:
  No warning of high volume level

Status in Ubuntu UX bugs:
  Fix Committed
Status in “pulseaudio” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  For the purpose of this Decision, a ‘personal music player’ means a
  portable device, that is not covered by Directive 1999/5/EC or
  Directive 2006/95/EC, with headphones or earphones, used to listen to
  recorded, generated or broadcasted sound.

  1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the
  safety requirement for personal music players shall be the following:
  Personal music players shall be designed and manufactured in a manner
  that ensures that, under reasonably foreseeable conditions of use,
  they are inherently safe and do not cause hearing damage.

  2. The requirement set out in paragraph 1 shall include in particular
  the following:

  (1) Exposure to sound levels shall be time limited to avoid hearing
  damage. At 80 dB(A) exposure time shall be limited to 40 hours/week,
  whereas at 89 dB(A) exposure time shall be limited to 5 hours/week.
  For other exposure levels a linear intra- and extrapolation applies.
  Account shall be taken of the dynamic range of sound and the
  reasonably foreseeable use of the products.

  (2) Personal music players shall provide adequate warnings on the risks 
involved in using the device and to the ways of avoiding them and information 
to users in cases where exposure poses a risk of hearing damage.
  

  Related documents:
  http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/
  http://europa.eu/rapid/press-release_IP-08-1492_en.htm
  http://ec.europa.eu/news/environment/090928_en.htm
  http://europa.eu/rapid/press-release_IP-09-1364_en.htm

  Design:

  : "Whenever you are using
  headphones, Ubuntu should frequently measure the volume of sound
  output. Whenever it is over 47 dB(A), your quota should be reduced
  accordingly..."

  [Originally reported in private bug 1370591.]

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

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

[Desktop-packages] [Bug 1373404] Re: No warning of high volume level

2014-10-08 Thread Albert Astals Cid 
Shows a notification at 70/80% that doesn't let you increase the volume unless 
you say "ok, sure"
 * MWG509 Wings GII with Android 4.2

And that's all the phones i could find in the house :D

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

Title:
  No warning of high volume level

Status in Ubuntu UX bugs:
  Fix Committed
Status in “pulseaudio” package in Ubuntu:
  New
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  For the purpose of this Decision, a ‘personal music player’ means a
  portable device, that is not covered by Directive 1999/5/EC or
  Directive 2006/95/EC, with headphones or earphones, used to listen to
  recorded, generated or broadcasted sound.

  1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the
  safety requirement for personal music players shall be the following:
  Personal music players shall be designed and manufactured in a manner
  that ensures that, under reasonably foreseeable conditions of use,
  they are inherently safe and do not cause hearing damage.

  2. The requirement set out in paragraph 1 shall include in particular
  the following:

  (1) Exposure to sound levels shall be time limited to avoid hearing
  damage. At 80 dB(A) exposure time shall be limited to 40 hours/week,
  whereas at 89 dB(A) exposure time shall be limited to 5 hours/week.
  For other exposure levels a linear intra- and extrapolation applies.
  Account shall be taken of the dynamic range of sound and the
  reasonably foreseeable use of the products.

  (2) Personal music players shall provide adequate warnings on the risks 
involved in using the device and to the ways of avoiding them and information 
to users in cases where exposure poses a risk of hearing damage.
  

  Related documents:
  http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/
  http://europa.eu/rapid/press-release_IP-08-1492_en.htm
  http://ec.europa.eu/news/environment/090928_en.htm
  http://europa.eu/rapid/press-release_IP-09-1364_en.htm

  Design:

  : "Whenever you are using
  headphones, Ubuntu should frequently measure the volume of sound
  output. Whenever it is over 47 dB(A), your quota should be reduced
  accordingly..."

  [Originally reported in private bug 1370591.]

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

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

[Desktop-packages] [Bug 1168742] Re: Disks are not unmounted when physical eject button is used

2014-10-08 Thread rogue-spectre 
Update to Phil Wright solution, for a more general context

1 - Create a udev rules file '/etc/udev/rules.d/61-sr-change.rules' and
add the line :

KERNEL=="sr*", ACTION=="change", RUN+="/usr/local/bin/sr_change.sh %n"

2 - And create the script '/usr/local/bin/sr_change.sh' :

#!/bin/sh
 
if [ $# -eq 1 ]
then
source=/dev/sr$1
else
source=/dev/sr0
fi

dvd+rw-mediainfo $source > /dev/null
n=$?

 if [ "$n" -eq '251' ]  then 
umount $source
 fi
exit 0

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

Title:
  Disks are not unmounted when physical eject button is used

Status in “udisks2” package in Ubuntu:
  Confirmed

Bug description:
  In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the
  hardware button on the drive. After ejecting disks via the hardware
  button, an entry for the disk still shows up in the file manager, and
  shows when I run df. If I do a soft eject (ie from the right click
  menu from the icon on the launcher), however, everything works
  properly.

  Just as a note, as per
  https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I
  attempted to report this using ubuntu-bug storage, however there is
  not an option dealing with unmounting devices, and clicking other
  tells you that you should run ubuntu-bug again with a specific package
  name. In an attempt to get this to a semi-relevant audience, I ended
  up just saying that a disk wasn't auto-mounted, clicking through the
  next few popups, and ended up here. If this isn't the right place to
  report this bug, I apologize.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-17-generic 3.8.0-17.27
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1590 F pulseaudio
   /dev/snd/controlC0:  chris  1590 F pulseaudio
  Date: Sat Apr 13 12:54:33 2013
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2013-03-26 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325)
  MachineType: ASUSTeK COMPUTER INC. G55VW
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.105
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   12:54:42.343: The udisks-daemon is running (name-owner :1.39).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G55VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G55VW
  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.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G55VW
  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/udisks2/+bug/1168742/+subscriptions

-- 
Mailing list: https://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 1355041] Re: [SRU] fglrx dependencies had conflicts in 12.04.5(kernel 3.13)

2014-10-08 Thread Alberto Milone 
On 02-10-14 19:27:22, Brian Murray wrote:
> The fglrx-installer-updates upload in the precise proposed queue makes
> an incorrect modification to the debian/changelog.
>

I had rebased my work against the wrong git branch. I've just fixed it
and reuploaded.

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

Title:
  [SRU] fglrx dependencies had conflicts in 12.04.5(kernel 3.13)

Status in HWE Next Project:
  Invalid
Status in HWE Next precise series:
  Confirmed
Status in “fglrx-installer” package in Ubuntu:
  Invalid
Status in “fglrx-installer-updates” package in Ubuntu:
  Invalid
Status in “fglrx-installer” source package in Precise:
  Fix Committed
Status in “fglrx-installer-updates” source package in Precise:
  In Progress

Bug description:
  [Impact]
  fglrx cannot be installed on 12.04.5 as it has a new X and dependency cannot 
be satisfied.

  [Test case]
  To test the installation of fglrx on a 12.04.5 machine if it succeeds or not, 
if it does check if the driver performs correctly.

  [Regression potential]

  --

  Trying to install fglrx from console but got following message:

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

  The following packages have unmet dependencies:
   fglrx : Depends: xorg-video-abi-11 or
    xorg-video-abi-12 but it is not installable or
    xorg-video-abi-13 or
    xorg-video-abi-14
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.6
  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 Aug 11 03:32:26 2014
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus: fwts-efi-runtime-dkms, 14.07.00, 3.13.0-32-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:184c]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=c1336d4c-028e-4d9c-975a-152b6183a869 ro quiet splash initcall_debug 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 184C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr089D1100501020100:rvnHewlett-Packard:rn184C:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g7 Notebook PC
  dmi.product.version: 089D1100501020100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1~precise1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

[Desktop-packages] [Bug 1378702] [NEW] cathegories in unity-lens-applications wrong

2014-10-08 Thread Marti Van Lin 
Public bug reported:

The categories in unity-lens-applications are wrong.

1. They are shown twice (in English and the local language);
2. the categories show the wrong set of applications.

This "bug" was introduced in Unity 7 on Trusty Thar and still exists in
Utopic Unicorn (Development Branch)

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Utopic Unicorn (development branch)
Release:14.10
Codename:   utopic

Please see screenshot for further explanation.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity-lens-applications 7.1.0+13.10.20131011-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-21.28-lowlatency 3.16.4
Uname: Linux 3.16.0-21-lowlatency x86_64
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct  8 10:51:03 2014
InstallationDate: Installed on 2014-10-03 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=nl_NL
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
SourcePackage: unity-lens-applications
UpgradeStatus: Upgraded to utopic on 2014-10-08 (0 days ago)

** Affects: unity-lens-applications (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

** Attachment added: "Schermafdruk van 2014-10-08 10:12:37.png"
   
https://bugs.launchpad.net/bugs/1378702/+attachment/4228260/+files/Schermafdruk%20van%202014-10-08%2010%3A12%3A37.png

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

Title:
  cathegories in unity-lens-applications wrong

Status in “unity-lens-applications” package in Ubuntu:
  New

Bug description:
  The categories in unity-lens-applications are wrong.

  1. They are shown twice (in English and the local language);
  2. the categories show the wrong set of applications.

  This "bug" was introduced in Unity 7 on Trusty Thar and still exists
  in Utopic Unicorn (Development Branch)

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10
  Codename: utopic

  Please see screenshot for further explanation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-lens-applications 7.1.0+13.10.20131011-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-21.28-lowlatency 3.16.4
  Uname: Linux 3.16.0-21-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct  8 10:51:03 2014
  InstallationDate: Installed on 2014-10-03 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-lens-applications
  UpgradeStatus: Upgraded to utopic on 2014-10-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1378353] Re: monitor brightness switched to lowest level after logout

2014-10-08 Thread b3nmore 
On a closer look, pressing the brightness up or down key makes a
difference: With the up key brightness is set to its highest level, with
the down key its set to the highest level - 1.

Btw. the newest driver 2:2.99.916+git20141006.ec2b9ac8-0ubuntu0sarvatt
shows the same behavior.

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

Title:
  monitor brightness switched to lowest level after logout

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

Bug description:
  After logout, switching to another login screen or shutting down the
  monitor brightness is set to its lowest level, making it rather hard
  to read in bright environments. Pressing a brightness key once (up or
  down does not matter) sets the monitor brightness to its highest
  level. Therefore it seems, that a vt switch leaves the brightness
  level at a undefined state and after triggering a manual change, it
  switches to some default setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Oct  7 14:54:55 2014
  InstallationDate: Installed on 2014-10-07 (0 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141006)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-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-10-08 Thread Mark Crook 
Also still present with nvidia driver version 343.22
GeForce GT 750M/PCIe/SSE2
Intel® Core™ i7-4702MQ CPU @ 2.20GHz × 8 
Ubuntu 14.04 LTS Linux 3.13.0-36-generic

-- 
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:
  Triaged
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-343” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

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 1378720] [NEW] package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2

2014-10-08 Thread hongwen luo 
Public bug reported:

..

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: signon-ui-service 0.17+14.10.20140814-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
Date: Mon Sep 29 15:58:24 2014
Dependencies:
 
DuplicateSignature: package:signon-ui-service:0.17+14.10.20140814-0ubuntu1:子进程 
dpkg-deb --control 返回了错误号 2
ErrorMessage: 子进程 dpkg-deb --control 返回了错误号 2
InstallationDate: Installed on 2014-09-13 (25 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140910)
PackageArchitecture: all
SourcePackage: signon-ui
Title: package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to 
install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: signon-ui (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check utopic

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

Title:
  package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to
  install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2

Status in “signon-ui” package in Ubuntu:
  New

Bug description:
  ..

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: signon-ui-service 0.17+14.10.20140814-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  Date: Mon Sep 29 15:58:24 2014
  Dependencies:
   
  DuplicateSignature: 
package:signon-ui-service:0.17+14.10.20140814-0ubuntu1:子进程 dpkg-deb --control 
返回了错误号 2
  ErrorMessage: 子进程 dpkg-deb --control 返回了错误号 2
  InstallationDate: Installed on 2014-09-13 (25 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140910)
  PackageArchitecture: all
  SourcePackage: signon-ui
  Title: package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to 
install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1378720/+subscriptions

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

[Desktop-packages] [Bug 1353951] Re: gnome online accounts require autentication on startup

2014-10-08 Thread yazid 
I've noticed that the bug appears only when Evolution is running. That's
why some days I don't see the bug (because in that days I open
Evolution, read the mails and then I close the program, while the other
days I keep Evolution running all day). I don't use other mail clients.
Maybe the other people affected by this bug use other mail clients so
they don't have the bug anymore after the fix was released. Maybe some
Evolution code need to be fixed too.

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

Title:
  gnome online accounts require autentication on startup

Status in Evolution Data Server:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “gnome-online-accounts” package in Ubuntu:
  Invalid
Status in “evolution-data-server” source package in Trusty:
  Fix Released
Status in “gnome-online-accounts” source package in Trusty:
  Invalid

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case]
  1) open gnome-online-accounts
  2) click + and add a google account
  3) enter user name and password
  4) confirm permissions for gnome
  5) Black window pops up and asks for google password, but does not accept the 
correct password.
  Google Contacts are not available in Gnome or Thunderbird

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  

  Gnome online accounts requires autentication on startup, but even typing the 
correct password in the box, the program says the password is wrong. By the way 
evolution and other programs work well with online accounts. I'm using 
Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour.
  Just to be clear: online-accounts works well, just at startup it opens an 
"administration" window where it requires to insert the password for my google 
accounts; if I type the correct password it says that the password is wrong, 
the only way to close the window is to click on "discard" and then all works 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+subscriptions

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

[Desktop-packages] [Bug 1378720] Re: package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2

2014-10-08 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 signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1378720

Title:
  package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to
  install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2

Status in “signon-ui” package in Ubuntu:
  New

Bug description:
  ..

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: signon-ui-service 0.17+14.10.20140814-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  Date: Mon Sep 29 15:58:24 2014
  Dependencies:
   
  DuplicateSignature: 
package:signon-ui-service:0.17+14.10.20140814-0ubuntu1:子进程 dpkg-deb --control 
返回了错误号 2
  ErrorMessage: 子进程 dpkg-deb --control 返回了错误号 2
  InstallationDate: Installed on 2014-09-13 (25 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140910)
  PackageArchitecture: all
  SourcePackage: signon-ui
  Title: package signon-ui-service 0.17+14.10.20140814-0ubuntu1 failed to 
install/upgrade: 子进程 dpkg-deb --control 返回了错误号 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1378720/+subscriptions

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

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

2014-10-08 Thread Sebastien Bacher 
thanks Dariusz, I've uploaded the segfault fix to utopic

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

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

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

Bug description:
  [Impact]

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

  [Test Case]

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

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

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

   * Minor conflict resolution needed (line numbers changed)

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

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

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

[Desktop-packages] [Bug 60103] Re: Can't install freeglut3-dev

2014-10-08 Thread Ehsan Izadi 
I have a same problem.

Does anyone managed to find a solution?

I am running Ubuntu 14.04 (64 bit)
I cannot install freeglut3-dev

the log is:
---
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 freeglut3-dev : Depends: libgl1-mesa-dev but it is not going to be installed or
  libgl-dev
 Depends: libglu1-mesa-dev but it is not going to be installed 
or
  libglu-dev
E: Unable to correct problems, you have held broken packages.
--

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

Title:
  Can't install freeglut3-dev

Status in “freeglut” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: freeglut3-dev

  In the last revision of Ubuntu 6.10, I can't install freeglut3-dev due
  to dependency problems:

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

  Since you only requested a single operation it is extremely likely that
  the package is simply not installable and a bug report against
  that package should be filed.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
freeglut3-dev: Depends: xlibmesa-glu-dev but it is not installable or
libglu-dev
  E: Broken packages

  
  (sorry for this duplicate ID)
  Thanks for all.

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

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

[Desktop-packages] [Bug 1354148] [NEW] python3.4 crashed with SIGSEGV in gtk_tree_row_ref_deleted()

2014-10-08 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

this must be transmageddon when I transcoded a video

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: python3.4-minimal 3.4.0-2ubuntu1
Uname: Linux 3.14.0-031400rc4-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Thu Aug  7 21:55:20 2014
ExecutablePath: /usr/bin/python3.4
InstallationDate: Installed on 2014-01-22 (196 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
ProcCmdline: python3 transmageddon.py
SegvAnalysis:
 Segfault happened at: 0x7f7db11f8e31:  cmp%esi,(%r10,%rax,1)
 PC (0x7f7db11f8e31) ok
 source "%esi" ok
 destination "(%r10,%rax,1)" (0x) not located in a known VMA region 
(needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: python3.4
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: python3.4 crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to trusty on 2014-07-01 (37 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

** Affects: glib2.0 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash trusty
-- 
python3.4 crashed with SIGSEGV in gtk_tree_row_ref_deleted()
https://bugs.launchpad.net/bugs/1354148
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to glib2.0 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 1352552] [NEW] python3.4 crashed with SIGSEGV in gtk_tree_model_filter_row_deleted()

2014-10-08 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

transmageddon crashed after having transcoded a video

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: python3.4-minimal 3.4.0-2ubuntu1
Uname: Linux 3.14.0-031400rc4-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug  4 22:12:30 2014
ExecutablePath: /usr/bin/python3.4
InstallationDate: Installed on 2014-01-22 (194 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
ProcCmdline: python3 transmageddon.py
SegvAnalysis:
 Segfault happened at: 0x7f1c804b84b4:  mov0x28(%rbp),%eax
 PC (0x7f1c804b84b4) ok
 source "0x28(%rbp)" (0x0028) not located in a known VMA region (needed 
readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: python3.4
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: python3.4 crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to trusty on 2014-07-01 (34 days ago)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

** Affects: glib2.0 (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash trusty
-- 
python3.4 crashed with SIGSEGV in gtk_tree_model_filter_row_deleted()
https://bugs.launchpad.net/bugs/1352552
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to glib2.0 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 1354148] Re: python3.4 crashed with SIGSEGV in gtk_tree_row_ref_deleted()

2014-10-08 Thread Matthias Klose 
crashes in the bindings

** Information type changed from Private to Public

** Package changed: python3.4 (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  python3.4 crashed with SIGSEGV in gtk_tree_row_ref_deleted()

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  this must be transmageddon when I transcoded a video

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python3.4-minimal 3.4.0-2ubuntu1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Thu Aug  7 21:55:20 2014
  ExecutablePath: /usr/bin/python3.4
  InstallationDate: Installed on 2014-01-22 (196 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  ProcCmdline: python3 transmageddon.py
  SegvAnalysis:
   Segfault happened at: 0x7f7db11f8e31:cmp%esi,(%r10,%rax,1)
   PC (0x7f7db11f8e31) ok
   source "%esi" ok
   destination "(%r10,%rax,1)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: python3.4
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python3.4 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2014-07-01 (37 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1354148/+subscriptions

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

[Desktop-packages] [Bug 1352552] Re: python3.4 crashed with SIGSEGV in gtk_tree_model_filter_row_deleted()

2014-10-08 Thread Matthias Klose 
crashes in the bindings

** Information type changed from Private to Public

** Package changed: python3.4 (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  python3.4 crashed with SIGSEGV in gtk_tree_model_filter_row_deleted()

Status in “glib2.0” package in Ubuntu:
  New

Bug description:
  transmageddon crashed after having transcoded a video

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: python3.4-minimal 3.4.0-2ubuntu1
  Uname: Linux 3.14.0-031400rc4-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Aug  4 22:12:30 2014
  ExecutablePath: /usr/bin/python3.4
  InstallationDate: Installed on 2014-01-22 (194 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  ProcCmdline: python3 transmageddon.py
  SegvAnalysis:
   Segfault happened at: 0x7f1c804b84b4:mov0x28(%rbp),%eax
   PC (0x7f1c804b84b4) ok
   source "0x28(%rbp)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: python3.4
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: python3.4 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to trusty on 2014-07-01 (34 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1352552/+subscriptions

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

[Desktop-packages] [Bug 1378739] [NEW] Request for sponsorship: update package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
Public bug reported:

Hi,

Onboard does not always automatically start up when logging in , even
though it is set to do so in the system preferences.

We think that it is because the D-Bus name org.gnome.Shell now also
exist in Unity Utopic. Thus, we have patched the onboard-
autostart.desktop file, in a way that we think would cover the needs of
Unity, GNOME and GNOME fallback/fallback-sessions.

As a side effect, Onboard now also starts in other sessions like KDE,
XFCE,... but this might be tolerable as they don't have a switch to
enable it.

We are proposing this fix, because it only needs changes in two lines of
the onboard version currently shipping with Ubuntu Utopic. However,
Onboard trunk has in the meantime also a more soffisticated solution
involving additional checks of XDG_CURRENT_DESKTOP. This latter solution
however required more substantial changes to the code base of Onboard.

Thus, I am attaching here an updated package of Onboard with the first
solution involving only changes to the onboard-autostart.desktop file.
If you prefer the latter, please let us know and we will look whether we
can do something.

Cheers

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

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

Title:
  Request for sponsorship: update package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: update package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Attachment added: "onboard_1.0.0.orig.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+attachment/4228347/+files/onboard_1.0.0.orig.tar.gz

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

Title:
  Request for sponsorship: update package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: update package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Attachment added: "onboard_1.0.0-0ubuntu5_source.build"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+attachment/4228350/+files/onboard_1.0.0-0ubuntu5_source.build

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

Title:
  Request for sponsorship: update package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: update package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Attachment added: "onboard_1.0.0-0ubuntu5.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+attachment/4228349/+files/onboard_1.0.0-0ubuntu5.dsc

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

Title:
  Request for sponsorship: update package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: update package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Attachment added: "onboard_1.0.0-0ubuntu5.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+attachment/4228348/+files/onboard_1.0.0-0ubuntu5.debian.tar.xz

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

Title:
  Request for sponsorship: update package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: update package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Attachment added: "onboard_1.0.0-0ubuntu5_source.changes"
   
https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+attachment/4228351/+files/onboard_1.0.0-0ubuntu5_source.changes

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

Title:
  Request for sponsorship: update package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1371859] Re: can't update loaders.cache: permission denied

2014-10-08 Thread Manfred Hampl 
Putting sudo in front of a command for redirecting output to a file
where you do not have write permission, does not help.

You might try
gdk-pixbuf-query-loaders | sudo tee 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

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

Title:
  can't update loaders.cache: permission denied

Status in “gdk-pixbuf” package in Ubuntu:
  New

Bug description:
  upgrading that fresh Utopic 64 bits installation, i'm seeing that
  error into the dialog box:

  
  Processing triggers for hicolor-icon-theme (0.13-1) ...

  (gtk-update-icon-cache-3.0:3098): GdkPixbuf-WARNING **: Cannot open
  pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
  pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

  This likely means that your installation is broken.
  Try running the command
gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  to make things work again for the time being.

  The terminal output is:

  oem@u64:~$  gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: 
Permission denied

  oem@u64:~$ sudo  gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
  bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: 
Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgdk-pixbuf2.0-0 2.30.8-1
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Sep 20 08:00:57 2014
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1371859/+subscriptions

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

[Desktop-packages] [Bug 1378748] [NEW] All scanning programs hang in pp_probe_devices()

2014-10-08 Thread Dmitry Shachnev 
Public bug reported:

Hi,

I have HP PhotoSmart C4283 and a (mostly) fresh Ubuntu 14.10 amd64
installation.

Any scanning program, like simple-scan or xsane, hangs when trying to do
anything with this printer (the process becomes defunct/zombie).

The backtrace is:

#0  ioctl () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fffecd80b40 in pp_probe_devices (lst=0xb , lst@entry=0x7fff5790 "", lst_size=-2147192681, 
lst_size@entry=16144, 
cnt=0x7fff4d9c, cnt@entry=0x7fff5468) at io/hpmud/pp.c:1228
#2  0x7fffecd78661 in hpmud_probe_devices (bus=bus@entry=HPMUD_BUS_ALL, 
buf=buf@entry=0x7fff56a0 "direct 
hp:/usb/Photosmart_C4200_series?serial=MY798KP16D04VP \"HP Photosmart C4200 
series\" \"HP Photosmart C4200 series USB MY798KP16D04VP HPLIP\" 
\"MFG:HP;MDL:Photosmart C4200 series;CLS:PRINTER;DES:Phot"..., 
buf_size=buf_size@entry=16384, cnt=cnt@entry=0x7fff5468, 
bytes_read=bytes_read@entry=0x7fff546c)
at io/hpmud/hpmud.c:600
#3  0x7fffed3796c5 in DevDiscovery (localOnly=localOnly@entry=0) at 
scan/sane/hpaio.c:278
#4  0x7fffed379cd9 in sane_hpaio_get_devices (deviceList=0x7fff9758, 
localOnly=0) at scan/sane/hpaio.c:359
#5  0x77bd6427 in sane_dll_get_devices (device_list=0x69fb80, 
local_only=0) at dll.c:1058

According to strace, the last two syscalls are:

open("/dev/parport0", O_RDONLY|O_NOCTTY) = 11
ioctl(11, PPGETMODES, 0x7fffbe27f54c)

... and the last one (ioctl) hangs (i.e. strace didn't print even the
closing bracket).

This happens even when the device is NOT plugged via USB.

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

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

Title:
  All scanning programs hang in pp_probe_devices()

Status in “hplip” package in Ubuntu:
  New

Bug description:
  Hi,

  I have HP PhotoSmart C4283 and a (mostly) fresh Ubuntu 14.10 amd64
  installation.

  Any scanning program, like simple-scan or xsane, hangs when trying to
  do anything with this printer (the process becomes defunct/zombie).

  The backtrace is:

  #0  ioctl () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fffecd80b40 in pp_probe_devices (lst=0xb , lst@entry=0x7fff5790 "", lst_size=-2147192681, 
lst_size@entry=16144, 
  cnt=0x7fff4d9c, cnt@entry=0x7fff5468) at io/hpmud/pp.c:1228
  #2  0x7fffecd78661 in hpmud_probe_devices (bus=bus@entry=HPMUD_BUS_ALL, 
  buf=buf@entry=0x7fff56a0 "direct 
hp:/usb/Photosmart_C4200_series?serial=MY798KP16D04VP \"HP Photosmart C4200 
series\" \"HP Photosmart C4200 series USB MY798KP16D04VP HPLIP\" 
\"MFG:HP;MDL:Photosmart C4200 series;CLS:PRINTER;DES:Phot"..., 
buf_size=buf_size@entry=16384, cnt=cnt@entry=0x7fff5468, 
bytes_read=bytes_read@entry=0x7fff546c)
  at io/hpmud/hpmud.c:600
  #3  0x7fffed3796c5 in DevDiscovery (localOnly=localOnly@entry=0) at 
scan/sane/hpaio.c:278
  #4  0x7fffed379cd9 in sane_hpaio_get_devices (deviceList=0x7fff9758, 
localOnly=0) at scan/sane/hpaio.c:359
  #5  0x77bd6427 in sane_dll_get_devices (device_list=0x69fb80, 
local_only=0) at dll.c:1058

  According to strace, the last two syscalls are:

  open("/dev/parport0", O_RDONLY|O_NOCTTY) = 11
  ioctl(11, PPGETMODES, 0x7fffbe27f54c)

  ... and the last one (ioctl) hangs (i.e. strace didn't print even the
  closing bracket).

  This happens even when the device is NOT plugged via USB.

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: updated package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Summary changed:

- Request for sponsorship: update package with patch for LP: #1376764 
+ Request for sponsorship: updated package with patch for LP: #1376764

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

Title:
  Request for sponsorship: updated package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however required more substantial changes to the code base of
  Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 1378752] [NEW] Crackling in PulseAudio when using src-linear or src-sinc-fastest resamplers with 22050Hz audio

2014-10-08 Thread Stephan Sokolow 
Public bug reported:

On my system, I had problems with both excess CPU usage and tried to
resolve them by using a simpler resampling algorithm. However, that
resulted in crackling audio from DOSBox and Windows 3.1 games running
under Wine 1.2.x.

(Both are configured to output audio at 22050Hz, with which ALSA dmix
has no problem, and, in the case of the Windows 3.1 games, that's not
something that can be reconfigured as far as I know.)

Nothing I changed seemed to help and I was forced to return to speex-
float-1.

(As such, the pulseaudio config files in the debug dump don't represent
PA in a broken configuration... just one that consumes more CPU than I'd
like it to.)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Oct  8 06:28:19 2014
InstallationDate: Installed on 2014-08-01 (68 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/07/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-880GMA-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GMA-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.pulse.daemon.conf: [modified]
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763
mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127

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


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

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

Title:
  Crackling in PulseAudio when using src-linear or src-sinc-fastest
  resamplers with 22050Hz audio

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  On my system, I had problems with both excess CPU usage and tried to
  resolve them by using a simpler resampling algorithm. However, that
  resulted in crackling audio from DOSBox and Windows 3.1 games running
  under Wine 1.2.x.

  (Both are configured to output audio at 22050Hz, with which ALSA dmix
  has no problem, and, in the case of the Windows 3.1 games, that's not
  something that can be reconfigured as far as I know.)

  Nothing I changed seemed to help and I was forced to return to speex-
  float-1.

  (As such, the pulseaudio config files in the debug dump don't
  represent PA in a broken configuration... just one that consumes more
  CPU than I'd like it to.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Oct  8 06:28:19 2014
  InstallationDate: Installed on 2014-08-01 (68 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-880GMA-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GMA-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763
  mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127

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

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

[Desktop-packages] [Bug 1168858] Re: Nautilus window opens behind current window

2014-10-08 Thread Cas 
** Changed in: deluge (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Nautilus window opens behind current window

Status in Unity:
  Won't Fix
Status in “deluge” package in Ubuntu:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Invalid

Bug description:
  Since I have upgraded to Ubuntu 13.04 (FINAL BETA), whenever I right
  click on my torrent file and chose OPEN FOLDER option, the folder
  opens in background and not on top of the window like I used to have
  it in Ubuntu 12.10.

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

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

[Desktop-packages] [Bug 1378752] Re: Crackling in PulseAudio when using src-linear or src-sinc-fastest resamplers with 22050Hz audio

2014-10-08 Thread Stephan Sokolow 
** Description changed:

- On my system, I had problems with both excess CPU usage and tried to
- resolve them by using a simpler resampling algorithm. However, that
- resulted in crackling audio from DOSBox and Windows 3.1 games running
- under Wine 1.2.x.
+ On my system, I had problems with excess CPU usage and tried to resolve
+ them by using a simpler resampling algorithm. However, that resulted in
+ crackling audio from DOSBox and Windows 3.1 games running under Wine
+ 1.2.x.
  
  (Both are configured to output audio at 22050Hz, with which ALSA dmix
  has no problem, and, in the case of the Windows 3.1 games, that's not
  something that can be reconfigured as far as I know.)
  
  Nothing I changed seemed to help and I was forced to return to speex-
  float-1.
  
  (As such, the pulseaudio config files in the debug dump don't represent
  PA in a broken configuration... just one that consumes more CPU than I'd
  like it to.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Oct  8 06:28:19 2014
  InstallationDate: Installed on 2014-08-01 (68 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-880GMA-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GMA-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763
  mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127

** Description changed:

  On my system, I had problems with excess CPU usage and tried to resolve
  them by using a simpler resampling algorithm. However, that resulted in
  crackling audio from DOSBox and Windows 3.1 games running under Wine
  1.2.x.
  
  (Both are configured to output audio at 22050Hz, with which ALSA dmix
  has no problem, and, in the case of the Windows 3.1 games, that's not
- something that can be reconfigured as far as I know.)
+ something that can be changed as far as I know.)
  
  Nothing I changed seemed to help and I was forced to return to speex-
  float-1.
  
  (As such, the pulseaudio config files in the debug dump don't represent
  PA in a broken configuration... just one that consumes more CPU than I'd
  like it to.)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Oct  8 06:28:19 2014
  InstallationDate: Installed on 2014-08-01 (68 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/07/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-880GMA-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd03/07/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GMA-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2014-10-08T06:21:40.701763
  mtime.conffile..etc.pulse.default.pa: 2014-10-08T02:32:14.607127

** Description changed:

  On my system, I had problems with excess CPU usage and tried to resolve
  them by using a simpler resampling algorithm. However, that resulted in
  crackling audio from DOSBox and Windows 3.1 games running under Wine
  1.2.x.
  
  (Both are configured to output audio at 22050Hz, with which ALSA dmix
  has no problem, and, in the case of the Windows 3.1 games, that's not
  something that can be changed as far as I know.)
  
- Nothing I changed seemed to help

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

2014-10-08 Thread Dariusz Gadomski 
I have made an attempt to backport this feature to utopic and to trusty (via 
linux-lts-utopic package).
The problem is I don't have a hardware setup (I have a dp1.2-enabled laptop but 
lack any dp monitors and hubs).
If anyone would like to test this, the packages are available in 
ppa:dgadomski/linux-mst.

I will appreciate any feedback.

** Changed in: xserver-xorg-video-intel (Ubuntu)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

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

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1378768] [NEW] windows appear on wrong display after unsuspend

2014-10-08 Thread Jean-Paul Calderone 
Public bug reported:

Configuration:

x230 laptop with an external monitor attached via hdmi (using minidisplay -> 
hdmi adapter).
Tbe builtin display resolution is 1366x768.
The external display resolution is 1920x1080.
Both displays are on.
Displays are not mirrored.
The external monitor is configured as positioned above the internal display, 
aligned along their left edges.

Action:

Run gnome-terminal maximized and positioned on the external display.
Run chrome maximized and positioned on the internal display.
Close the laptop lid to cause the system to suspend.
Wait for the system to suspend and for the external display to go to sleep.
Open the laptop lid.

Observed outcome:

Both gnome-terminal and chrome are now positioned on the external
display and maximized.

Expected outcome:

Both windows are positioned in the same place they were positioned
before the suspend/resume cycle.

System information:

Description:Ubuntu 14.04.1 LTS
Release:14.04

full installed package list attached

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

** Attachment added: "`dpkg -l` output"
   
https://bugs.launchpad.net/bugs/1378768/+attachment/4228382/+files/packages.txt

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

Title:
  windows appear on wrong display after unsuspend

Status in “unity” package in Ubuntu:
  New

Bug description:
  Configuration:

  x230 laptop with an external monitor attached via hdmi (using minidisplay -> 
hdmi adapter).
  Tbe builtin display resolution is 1366x768.
  The external display resolution is 1920x1080.
  Both displays are on.
  Displays are not mirrored.
  The external monitor is configured as positioned above the internal display, 
aligned along their left edges.

  Action:

  Run gnome-terminal maximized and positioned on the external display.
  Run chrome maximized and positioned on the internal display.
  Close the laptop lid to cause the system to suspend.
  Wait for the system to suspend and for the external display to go to sleep.
  Open the laptop lid.

  Observed outcome:

  Both gnome-terminal and chrome are now positioned on the external
  display and maximized.

  Expected outcome:

  Both windows are positioned in the same place they were positioned
  before the suspend/resume cycle.

  System information:

  Description:Ubuntu 14.04.1 LTS
  Release:14.04

  full installed package list attached

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

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

[Desktop-packages] [Bug 1376530] Re: GTK apps crashing with "Attempt to unlock mutex that was not locked"

2014-10-08 Thread Monsta 
I see GTK+3 in Utopic received the patch, but you need to patch GTK+2 as
well:

https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24&id=fbf38d16bcc26630f0f721d266509f5bc292f606

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

Title:
  GTK apps crashing with "Attempt to unlock mutex that was not locked"

Status in “gtk+2.0” package in Ubuntu:
  Fix Committed
Status in “gtk+2.0” package in Debian:
  New

Bug description:
  Attempting to run some GTK apps (e.g. pyrenamer) on 14.10 results in
  an immediate crash, with the message "Attempt to unlock mutex that was
  not locked".

  https://bugzilla.gnome.org/show_bug.cgi?id=735428 seems to be the
  relevant upstream bug, and there is a patch here:
  https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec

  To some extent, this seems to be the result of individual projects
  using GTK incorrectly, and some fixes have been made to those
  individual projects.

  *However*, I am also seeing this bug occur in a closed source third
  party application, Stata 13. As Emmanuele Bassi mentions in the Gnome
  bug thread, there are probably a lot of applications out in the wild
  affected by the same issue, that in some cases cannot be fixed, so it
  would be good if a fix could be included in the versions of GTK that
  Ubuntu ships.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libgtk-3-0 3.12.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct  2 10:05:20 2014
  InstallationDate: Installed on 2014-04-24 (160 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to utopic on 2014-10-01 (0 days ago)

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

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

[Desktop-packages] [Bug 1378739] Re: Request for sponsorship: updated package with patch for LP: #1376764

2014-10-08 Thread Francesco Fumanti 
** Description changed:

  Hi,
  
  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.
  
  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs of
  Unity, GNOME and GNOME fallback/fallback-sessions.
  
  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.
  
  We are proposing this fix, because it only needs changes in two lines of
  the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter solution
- however required more substantial changes to the code base of Onboard.
+ however requires changes to the code base of Onboard.
  
  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether we
  can do something.
  
  Cheers

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

Title:
  Request for sponsorship: updated package with patch for LP: #1376764

Status in “onboard” package in Ubuntu:
  New

Bug description:
  Hi,

  Onboard does not always automatically start up when logging in , even
  though it is set to do so in the system preferences.

  We think that it is because the D-Bus name org.gnome.Shell now also
  exist in Unity Utopic. Thus, we have patched the onboard-
  autostart.desktop file, in a way that we think would cover the needs
  of Unity, GNOME and GNOME fallback/fallback-sessions.

  As a side effect, Onboard now also starts in other sessions like KDE,
  XFCE,... but this might be tolerable as they don't have a switch to
  enable it.

  We are proposing this fix, because it only needs changes in two lines
  of the onboard version currently shipping with Ubuntu Utopic. However,
  Onboard trunk has in the meantime also a more soffisticated solution
  involving additional checks of XDG_CURRENT_DESKTOP. This latter
  solution however requires changes to the code base of Onboard.

  Thus, I am attaching here an updated package of Onboard with the first
  solution involving only changes to the onboard-autostart.desktop file.
  If you prefer the latter, please let us know and we will look whether
  we can do something.

  Cheers

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

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

[Desktop-packages] [Bug 881046]

2014-10-08 Thread Alexander E. Patrakov 
Today I talked about this bug with Keith Packard. As a result of our
testing, I have to state that, with the patch, the pointer is not
constrained properly on the right side if one applies keystone
correction. That's with xorg-server 1.16.1, will now retest with the
latest git.

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

Title:
  Panning in a virtual monitor is not possible after upgrade to Ubuntu
  11.10

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Triaged
Status in “xorg-server” source package in Precise:
  Triaged

Bug description:
  When I go  for a virtual monitor by issuing command "xrandr --output
  LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at
  resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to
  Ubuntu 11.10), the WM bars on top and left side of the screen (in
  Unity) look like extending to the new area, but I cannot move the
  pointer to the new extra area and so I cannot pan. As far as I
  understood by reading around, this *could* be a bug in package "xorg-
  server" rather than in "xrandr" and *could* be related to the
  boundaries set for cursor position.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Mon Oct 24 20:40:14 2011
  DistUpgraded: Log time: 2011-10-22 12:17:44.515205
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus:
   dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! 
Diff between built and installed module!)
   dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff 
between built and installed module!)
   dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0182]
 Subsystem: Dell Device [1028:0182]
  MachineType: Dell Inc. Latitude D610
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 3.3V 32-bit PC Card
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   LANGUAGE=it_IT:it:en_GB:en
  ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet 
splash rootdelay=15
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago)
  dmi.bios.date: 03/02/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0D4571
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D610
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 883319]

2014-10-08 Thread Alexander E. Patrakov 
Today I talked about this bug with Keith Packard. As a result of our
testing, I have to state that, with the patch, the pointer is not
constrained properly on the right side if one applies keystone
correction. That's with xorg-server 1.16.1, will now retest with the
latest git.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

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

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

[Desktop-packages] [Bug 1240145] Re: problems configuring facebook for sharing

2014-10-08 Thread Ugo Riboni 
** Changed in: gallery-app (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  problems configuring facebook for sharing

Status in “friends” package in Ubuntu:
  Invalid
Status in “gallery-app” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-extras” package in Ubuntu:
  Fix Released
Status in “ubuntu-ui-extras” source package in Saucy:
  New

Bug description:
  using latest image 97
  - open photo in gallery
  - press sharing button and then "configure facebook for sharing"
  - correctly brought to online accounts settings panel
  - configure facebook
  - after pressing "Log On" from facebook page you are automatically brought 
back to gallery (not sure this is desired, should bring you back to online 
accounts screen)
  - when in gallery, clicking the share button still shows "configure facebook 
for sharing" even though it has been configured
  - gallery does not recongnize facebook has been configured until you close 
and relaunch gallery

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

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

[Desktop-packages] [Bug 1378794] [NEW] package shotwell-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in package shotwe

2014-10-08 Thread Nocchy 
Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: shotwell-common (not installed)
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic i686
ApportVersion: 2.14.7-0ubuntu5
Architecture: i386
Date: Wed Oct  8 14:05:15 2014
DuplicateSignature: package:shotwell-common:(not installed):trying to overwrite 
'/usr/share/appdata/shotwell.appdata.xml', which is also in package shotwell 
0.20.0+2611~ubuntu14.04.1
ErrorMessage: trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', 
which is also in package shotwell 0.20.0+2611~ubuntu14.04.1
InstallationDate: Installed on 2014-06-13 (116 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
SourcePackage: shotwell
Title: package shotwell-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in 
package shotwell 0.20.0+2611~ubuntu14.04.1
UpgradeStatus: Upgraded to utopic on 2014-09-22 (15 days ago)

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


** Tags: apport-package i386 package-conflict utopic

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

Title:
  package shotwell-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which
  is also in package shotwell 0.20.0+2611~ubuntu14.04.1

Status in “shotwell” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: shotwell-common (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic i686
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  Date: Wed Oct  8 14:05:15 2014
  DuplicateSignature: package:shotwell-common:(not installed):trying to 
overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in package 
shotwell 0.20.0+2611~ubuntu14.04.1
  ErrorMessage: trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', 
which is also in package shotwell 0.20.0+2611~ubuntu14.04.1
  InstallationDate: Installed on 2014-06-13 (116 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: shotwell
  Title: package shotwell-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in 
package shotwell 0.20.0+2611~ubuntu14.04.1
  UpgradeStatus: Upgraded to utopic on 2014-09-22 (15 days ago)

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

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

[Desktop-packages] [Bug 576674] Re: package install-info 4.13a.dfsg.1-5ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

2014-10-08 Thread Zdravko Dzhambov 
My system has not updated since the bug was found.

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

Title:
  package install-info 4.13a.dfsg.1-5ubuntu1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 127

Status in “texinfo” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: texinfo

  failure 127 was mentioned

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: install-info 4.13a.dfsg.1-5ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  AptOrdering:
   install-info: Configure
   libkpathsea5: Install
   info: Configure
   ubuntu-standard: Configure
   libkpathsea5: Configure
  Architecture: i386
  Date: Fri May  7 06:17:05 2010
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  SourcePackage: texinfo
  Title: package install-info 4.13a.dfsg.1-5ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 127

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

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

[Desktop-packages] [Bug 1349859] Re: [MIR] libixion (b-d of liborcus)

2014-10-08 Thread Matthias Klose 
liborcus is dep-wait

** Also affects: libixion (Ubuntu Utopic)
   Importance: Undecided
   Status: Incomplete

** Tags added: ftbfs

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

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

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

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

Title:
  [MIR] libixion (b-d of liborcus)

Status in “libixion” package in Ubuntu:
  Incomplete
Status in “liborcus” package in Ubuntu:
  Confirmed
Status in “libixion” source package in Utopic:
  Incomplete
Status in “liborcus” source package in Utopic:
  Confirmed

Bug description:
  1. Availability: libixion is available in utopic universe and build on all 
platforms
  https://launchpad.net/ubuntu/+source/libixion/0.7.0-2ubuntu1

  2. Rationale: Hard dependency of LibreOffice 4.3, which is already in
  main -- only alternative would be to use the internal copy of the same
  lib (which is what we currently do on utopic).

  3. Security:
  No reported issues on http://secunia.com/search/?search=libixion or 
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libixion
  Any binaries running as root or suid/sgid? No.
  Any daemons? No.
  Network activity: No.
  Does it directly (not through a library) process binary (video, audio, etc) 
or structured (PDF, etc) data ? No, while libixion is processing formulas in 
documents, its in no way a file filter itself.

  4. QA:
  In what situations does the package not work out of the box without 
configuration? None
  Does the package ask any debconf questions higher than priority 'medium'? No
  Debian bugs: None, 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=libixion
  Upstream bug tracker: https://bugs.freedesktop.org
  Is there a test suite in the upstream source or packaging ? Yes.
  Is it enabled to run in the build ? Yes

  5. UI:
  doesnt apply

  6. Deps:
  buildtime: debhelper (>= 8.0.0), autotools-dev, zlib1g-dev, python, 
dh-autoreconf, pkg-config, libboost-system-dev, dpkg-dev (>= 1.16.1), 
libboost-thread-dev, libboost-program-options-dev, libmdds-dev (>= 0.9)
  All are resolvable in utopic-main.
  runtime: libzip-dev, libmdds-dev (>= 0.9)
  All are resolvable in utopic-main.

  7. Standards:
  FHS, Debian Policy compliance? Yes
  Packaging system (debhelper/cdbs/dbs)? debhelper
  Patch system? quilt
  Any packaging oddities? Needed temp. bump of somewhat older autoconf to build 
on ppc64el -- should be solved on upstream master (and thus for subsequest 
releases)

  8. Maintenance
  Small lib with default autotools buildsystem => low maintenance
  Well cared for at Debians OpenOffice/LibreOffice Team.

  9. Background:
  Spin-out from LibreOffice -- we have the code in main already anyway.

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

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

[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another

2014-10-08 Thread Alfredo Tschamler 
Same problem here. Ubuntu 14.04. GNOME Shell 3.10.4. All the issue started when 
I switch from unity to gnome-shell. I hadn't this problem with unity. The 
workaround "gnome-settings-daemon --replace" or  update-monitor-position ->
(http://bernaerts.dyndns.org/linux/74-ubuntu/309-ubuntu-dual-display-monitor-position-lost)

work for me, but these workaround cause that the lock screen shield get blank 
(blue screen with the hour), and that is very annoying!
:(

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

Title:
  Second screen position isn't saved from one session to another

Status in elementary OS:
  Confirmed
Status in Gnome Settings Daemon:
  New
Status in GNOME Shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-shell” package in Ubuntu:
  Triaged

Bug description:
  (Noticed on Ubuntu 14.04 beta 1 GNOME)
  At work I have a second screen, which I prefer to virtually put on the left 
side of my laptop screen.
  Using gnome-control-center I can change the position of the second without 
problem.
  But when I disconnect the second screen (to work on another place) and then 
connect it again
  OR if I just power off the laptop and turn it on again,
  the second screen position is set back to the default right position.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu53
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 14 08:50:00 2014
  InstallationDate: Installed on 2014-03-01 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2

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

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

[Desktop-packages] [Bug 1168742] Re: Disks are not unmounted when physical eject button is used

2014-10-08 Thread Rüdiger Kupper 
** Tags added: trusty

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

Title:
  Disks are not unmounted when physical eject button is used

Status in “udisks2” package in Ubuntu:
  Confirmed

Bug description:
  In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the
  hardware button on the drive. After ejecting disks via the hardware
  button, an entry for the disk still shows up in the file manager, and
  shows when I run df. If I do a soft eject (ie from the right click
  menu from the icon on the launcher), however, everything works
  properly.

  Just as a note, as per
  https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I
  attempted to report this using ubuntu-bug storage, however there is
  not an option dealing with unmounting devices, and clicking other
  tells you that you should run ubuntu-bug again with a specific package
  name. In an attempt to get this to a semi-relevant audience, I ended
  up just saying that a disk wasn't auto-mounted, clicking through the
  next few popups, and ended up here. If this isn't the right place to
  report this bug, I apologize.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-17-generic 3.8.0-17.27
  ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
  Uname: Linux 3.8.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  chris  1590 F pulseaudio
   /dev/snd/controlC0:  chris  1590 F pulseaudio
  Date: Sat Apr 13 12:54:33 2013
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333
  HotplugNewDevices:

  HotplugNewMounts:

  InstallationDate: Installed on 2013-03-26 (18 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325)
  MachineType: ASUSTeK COMPUTER INC. G55VW
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic 
root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-17-generic N/A
   linux-backports-modules-3.8.0-17-generic  N/A
   linux-firmware1.105
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   12:54:42.343: The udisks-daemon is running (name-owner :1.39).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G55VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G55VW
  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.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G55VW
  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/udisks2/+bug/1168742/+subscriptions

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

[Desktop-packages] [Bug 1374945] Re: Known applications list box is very small

2014-10-08 Thread Lanoxx 
Thank you to Dmitry and Chris for backporting this fix.

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

Title:
  Known applications list box is very small

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Trusty:
  Fix Committed

Bug description:
  (Parts copied from Lanoxx's message on gnome-flashback-list)

  = Impact =
  The "Show list of known applications" box collapses to a very small list 
where only one or two entries are visible.

  = Development Fix =
  This patch were applied in 3.8.1 (available in Utopic):

  https://git.gnome.org/browse/gnome-
  panel/commit/?id=6d7833a6d41c4566eeb4f0f7ef2cbb94d42bfac7

  With this patch it should resize together with the dialog window and
  in the default view there are at least 5 items visible. Besides that
  Alberts and me took very good care not to change the design or
  behaviour, I am quite sure it is suitable for an SRU.

  = Stable Fix =
  The patch is cherry-picked in a proposed update for Trusty.

  = Test Case =
  * Press Alt+F2 to open the Run Command dialog.
  * Select "Show list of known applications".
  * There should be at least 5 applications visible.

  = Regression Potential =
  Minimal regression potential, just UI change.

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

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

[Desktop-packages] [Bug 1374943] Re: Fixes for clock applet for Trusty

2014-10-08 Thread Lanoxx 
Thank you to Dmitry and Chris for backporting this fix.

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

Title:
  Fixes for clock applet for Trusty

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Trusty:
  Fix Committed

Bug description:
  = Impact =
  Adding or removing locations in the preferences dialog doesn't work. This 
affects only the standalone clock applet (which is not used in the default 
configuration).

  = Development Fix =
  This patch was applied in 3.8.1 (available in Utopic):

  Fix clock applet preferences
  
https://git.gnome.org/browse/gnome-panel/commit/?id=6fe206c57f372f7466b6a669a816c51b407044f7

  = Stable Fix =
  The patch above is cherry-picked in a proposed update for Trusty.

  = Test Case =
  * Open Clock applet preferences.
  * Try to add new location to the clock applet.
  * It should not crash, and the new locations list should update.
  * Try to remove a location.
  * It should not crash, and the new locations list should update.

  = Regression Potential =
  Minimal regression potential. Does not affect other applets.

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

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

[Desktop-packages] [Bug 1374945] Re: Known applications list box is very small

2014-10-08 Thread Lanoxx 
I confirm this fixes the problem.

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

Title:
  Known applications list box is very small

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Trusty:
  Fix Committed

Bug description:
  (Parts copied from Lanoxx's message on gnome-flashback-list)

  = Impact =
  The "Show list of known applications" box collapses to a very small list 
where only one or two entries are visible.

  = Development Fix =
  This patch were applied in 3.8.1 (available in Utopic):

  https://git.gnome.org/browse/gnome-
  panel/commit/?id=6d7833a6d41c4566eeb4f0f7ef2cbb94d42bfac7

  With this patch it should resize together with the dialog window and
  in the default view there are at least 5 items visible. Besides that
  Alberts and me took very good care not to change the design or
  behaviour, I am quite sure it is suitable for an SRU.

  = Stable Fix =
  The patch is cherry-picked in a proposed update for Trusty.

  = Test Case =
  * Press Alt+F2 to open the Run Command dialog.
  * Select "Show list of known applications".
  * There should be at least 5 applications visible.

  = Regression Potential =
  Minimal regression potential, just UI change.

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

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

[Desktop-packages] [Bug 1374943] Re: Fixes for clock applet for Trusty

2014-10-08 Thread Lanoxx 
I confirm this fixes the problem.

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

Title:
  Fixes for clock applet for Trusty

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Trusty:
  Fix Committed

Bug description:
  = Impact =
  Adding or removing locations in the preferences dialog doesn't work. This 
affects only the standalone clock applet (which is not used in the default 
configuration).

  = Development Fix =
  This patch was applied in 3.8.1 (available in Utopic):

  Fix clock applet preferences
  
https://git.gnome.org/browse/gnome-panel/commit/?id=6fe206c57f372f7466b6a669a816c51b407044f7

  = Stable Fix =
  The patch above is cherry-picked in a proposed update for Trusty.

  = Test Case =
  * Open Clock applet preferences.
  * Try to add new location to the clock applet.
  * It should not crash, and the new locations list should update.
  * Try to remove a location.
  * It should not crash, and the new locations list should update.

  = Regression Potential =
  Minimal regression potential. Does not affect other applets.

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

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

[Desktop-packages] [Bug 60103] Re: Can't install freeglut3-dev

2014-10-08 Thread Ehsan Izadi 
** Changed in: freeglut (Ubuntu)
   Status: Invalid => Incomplete

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

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

Title:
  Can't install freeglut3-dev

Status in “freeglut” package in Ubuntu:
  New

Bug description:
  Binary package hint: freeglut3-dev

  In the last revision of Ubuntu 6.10, I can't install freeglut3-dev due
  to dependency problems:

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

  Since you only requested a single operation it is extremely likely that
  the package is simply not installable and a bug report against
  that package should be filed.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
freeglut3-dev: Depends: xlibmesa-glu-dev but it is not installable or
libglu-dev
  E: Broken packages

  
  (sorry for this duplicate ID)
  Thanks for all.

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

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

[Desktop-packages] [Bug 1378814] [NEW] greeter does not properly update infographic after unlock

2014-10-08 Thread Bill Filler 
Public bug reported:

This bug has been here since forever, but really needs to get cleaned up
for rtm.

Steps to reproduce:
- send 2 text messages
- lock your phone
- unlock your phone
- confirm infographic says "2 text messages sent today"
- lock your phone for the night and go to sleep
- unlock your phone the next day

Expected results:
- infographic should be cleared, or show relevant information for today

Actual results:
- infographic still says "2 text messages sent today"

When the phone is unlocked the greeter should update the infographic
text

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


** Tags: rtm14

** Tags added: rtm14

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

Title:
  greeter does not properly update infographic after unlock

Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says "2 text messages sent today"
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says "2 text messages sent today"

  When the phone is unlocked the greeter should update the infographic
  text

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

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

[Desktop-packages] [Bug 1374943] Re: Fixes for clock applet for Trusty

2014-10-08 Thread Dmitry Shachnev 
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Fixes for clock applet for Trusty

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Trusty:
  Fix Committed

Bug description:
  = Impact =
  Adding or removing locations in the preferences dialog doesn't work. This 
affects only the standalone clock applet (which is not used in the default 
configuration).

  = Development Fix =
  This patch was applied in 3.8.1 (available in Utopic):

  Fix clock applet preferences
  
https://git.gnome.org/browse/gnome-panel/commit/?id=6fe206c57f372f7466b6a669a816c51b407044f7

  = Stable Fix =
  The patch above is cherry-picked in a proposed update for Trusty.

  = Test Case =
  * Open Clock applet preferences.
  * Try to add new location to the clock applet.
  * It should not crash, and the new locations list should update.
  * Try to remove a location.
  * It should not crash, and the new locations list should update.

  = Regression Potential =
  Minimal regression potential. Does not affect other applets.

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

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

[Desktop-packages] [Bug 1192801] Re: [Latitude D630, SigmaTel STAC9205, Black Headphone Out, Left] No sound at all

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

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

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

Title:
  [Latitude D630, SigmaTel STAC9205, Black Headphone Out, Left] No sound
  at all

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  One day for some strange reason, all audio output ceased. I've done a
  lot of diagnostics and common fixes that should have worked myself --
  but I have yet to find a conclusion as everything seems to be in
  check. My soundcard is detected and isn't displayed as a "Dummy Card"
  as seen in many sound related errors. My mixer settings are fine. I've
  tried updating sound related repos and still have yet to come to a
  conclusion.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  echelon1593 F pulseaudio
echelon4682 F pulseaudio
  Date: Wed Jun 19 22:45:42 2013
  InstallationDate: Installed on 2013-06-11 (8 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  echelon1593 F pulseaudio
echelon4682 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Latitude D630, SigmaTel STAC9205, Black Headphone Out, Left] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/24/2008:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D630
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1374945] Re: Known applications list box is very small

2014-10-08 Thread Dmitry Shachnev 
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Known applications list box is very small

Status in “gnome-panel” package in Ubuntu:
  Fix Released
Status in “gnome-panel” source package in Trusty:
  Fix Committed

Bug description:
  (Parts copied from Lanoxx's message on gnome-flashback-list)

  = Impact =
  The "Show list of known applications" box collapses to a very small list 
where only one or two entries are visible.

  = Development Fix =
  This patch were applied in 3.8.1 (available in Utopic):

  https://git.gnome.org/browse/gnome-
  panel/commit/?id=6d7833a6d41c4566eeb4f0f7ef2cbb94d42bfac7

  With this patch it should resize together with the dialog window and
  in the default view there are at least 5 items visible. Besides that
  Alberts and me took very good care not to change the design or
  behaviour, I am quite sure it is suitable for an SRU.

  = Stable Fix =
  The patch is cherry-picked in a proposed update for Trusty.

  = Test Case =
  * Press Alt+F2 to open the Run Command dialog.
  * Select "Show list of known applications".
  * There should be at least 5 applications visible.

  = Regression Potential =
  Minimal regression potential, just UI change.

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

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

[Desktop-packages] [Bug 1378814] Re: greeter does not properly update infographic after unlock

2014-10-08 Thread Bill Filler 
consider marking this critical so it gets fixed for rtm as it's a very
visible thing the user will see from day 1

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

Title:
  greeter does not properly update infographic after unlock

Status in “unity-greeter” package in Ubuntu:
  New

Bug description:
  This bug has been here since forever, but really needs to get cleaned
  up for rtm.

  Steps to reproduce:
  - send 2 text messages
  - lock your phone
  - unlock your phone
  - confirm infographic says "2 text messages sent today"
  - lock your phone for the night and go to sleep
  - unlock your phone the next day

  Expected results:
  - infographic should be cleared, or show relevant information for today

  Actual results:
  - infographic still says "2 text messages sent today"

  When the phone is unlocked the greeter should update the infographic
  text

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

2014-10-08 Thread Michael Schaller 
Thank you, Dariusz. I've asked affected users to test your packages. If
I don't hear back from them I'll test them myself in a few days.

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

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

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1311515] Re: Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

2014-10-08 Thread L.D 
Sorry for my bad english.
I create file "synaptics.sh" script, with your code.
run the script "synaptics.sh" from my user (not root)

dmesg | grep -i syn
[0.200496] pnp 00:08: Plug and Play ACPI device, IDs SYN2601 PNP0f13 
(active)
[2.340322] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, id: 
0x1e0b1, caps: 0xf00133/0x24/0xa2400, board id: 1874, fw id: 1066450
[2.382695] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5

What am I doing wrong?

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

Title:
  Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Confirmed

Bug description:
  [Test details]
  Image: 14.04 LTS
  Platforms:
  ThinkPad-Edge-E531:~$ dmesg | grep -i syn
  [4.135984] hda_codec: Enable sync_write for stable communication
  [4.846020] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd001a3/0x940300/0x127c00, board id: 2722, fw id: 1310036
  [4.846024] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [4.906051] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input6

  [Steps]
  1. install image kittyhawk-trusty-amd64-iso-20140314-1.iso via bootable USB 
or DVD
  2. launch google maps in web browser
  3. pinch touchpad with two fingers and see if map zooms in & out accordingly

  [Expected result]
  map should zoom-in when user pinches two fingers apart, zoom-out when user 
pinches two fingers together.

  [Actual result]
  sometimes zoom in & out behavior is reversed.

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

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

[Desktop-packages] [Bug 1378688] [NEW] after installing nvidia drivers / CUDA the screen turns black after reboot

2014-10-08 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

- Ubuntu 14.04
- GeForce GTX 670
- Large Yamasaki monitor (DVI cable)

I'm trying to install the nvidia drivers (required by CUDA), but after
the successful installation the screen turns permanently black after the
first reboot.

I repeated the procedure several times, using different version of the drivers 
and different sources (i.e., nvidia download center, ubuntu's standard repos, 
and the xorgs-edgers ppa).
The pattern was constant in all these attempt.

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


** Tags: bot-comment
-- 
after installing nvidia drivers / CUDA the screen turns black after reboot
https://bugs.launchpad.net/bugs/1378688
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to nvidia-graphics-drivers-331 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 1378688] Re: after installing nvidia drivers / CUDA the screen turns black after reboot

2014-10-08 Thread nicola.corradi 
** Package changed: ubuntu => nvidia-graphics-drivers-331 (Ubuntu)

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

Title:
  after installing nvidia drivers / CUDA the screen turns black after
  reboot

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

Bug description:
  - Ubuntu 14.04
  - GeForce GTX 670
  - Large Yamasaki monitor (DVI cable)

  I'm trying to install the nvidia drivers (required by CUDA), but after
  the successful installation the screen turns permanently black after
  the first reboot.

  I repeated the procedure several times, using different version of the 
drivers and different sources (i.e., nvidia download center, ubuntu's standard 
repos, and the xorgs-edgers ppa).
  The pattern was constant in all these attempt.

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

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

[Desktop-packages] [Bug 883319]

2014-10-08 Thread Alexander E. Patrakov 
Retested with the latest git. The patch indeed breaks constraining the
mouse on the right side when keystone correction is active. However, the
whole "keystone correction" feature is already so horribly broken that
I'd just propose to drop it.

The breakage is that, if you click something, the click will not go into
a point that you intended to click. I.e. you can't even undo the damage
using the xkeystone GUI.

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

Title:
  xrandr --scale restricts area in which mouse moves

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Fix Released
Status in “xorg-server” source package in Precise:
  Fix Released
Status in “xorg-server” source package in Quantal:
  Fix Released
Status in “xorg-server” source package in Raring:
  Fix Released

Bug description:
  SRU Request:

  [IMPACT]
  A bug in the version of xorg-server in precise prevents users from scaling 
screen resolution. When attempting to do so, as was possible in Natty and 
earlier, and which is possible in Quantal+, the mouse pointer remains locked 
inside the old resolution. This prevents users of small screens such as 
netbooks from scaling to a greater screen resolution.

  [Test Case]
  - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the 
display by using the following command:

  xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25

  See if the mouse moves correctly to all screen extremities, and is not
  confined by a transparent border at 1024x600

  [Regression Potential]
  This is fixed with a patch backported from the xorg-server version in 
Quantal. In theory it should just affect screen which are scaled and panned, 
which is uncommon. If so, the patch can be backed out.


  
  Original Bug Description:
  in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so

  xrandr --output LVDS1 --scale 1.2x1.2

  this worked fine: the desktop scaled to larger size correctly .
   After upgrading to 11.10, in kde the desktop still resizes
  correctly, but the movement of the mouse is restricted to an area equal to
  the screen size *before* issuing the scaling command. .. Ie let's say
  the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the
  screen size changes to 1640x922 but the mouse moves in an area the size of
  1366x768 in the top left of the screen and then 'hits a wall' preventing
  it to move. I also tried ubuntu 11.10 with gnome: here the screen also
  resizes, but I have the same issue with the mouse, and the extended area
  of the desktop is black...

  Some time ago there was a similar issue, which was resolved later. Now it 
seems
  to be back...

  jos@samsungsucks:~$ lsb_release -rd
  Description:Ubuntu 11.10
  Release:11.10

  jos@samsungsucks:~$ xrandr --version
  xrandr program version   1.3.5
  Server reports RandR version 1.3

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

2014-10-08 Thread Vincent Gerris 
It would be great if anyone can explain the complete set of steps of how to 
install the packages needed to test this in 14.04.
I have found no repo with debs to test and the ones I found are not compatible 
with current xorg and such.
I thought I was fairly experienced with this, but I have not been able to 
figure it out.
I compiled and installed a 3.14 kernel which should have some patches, and 
tried the intel installer with it to no avail.
Again, I am happy to test, but I could really help some instructions and help 
from the people here that seem to be able to install it.
Happy to provide feedback

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

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

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 881046]

2014-10-08 Thread Alexander E. Patrakov 
Retested with the latest git. The patch indeed breaks constraining the
mouse on the right side when keystone correction is active. However, the
whole "keystone correction" feature is already so horribly broken that
I'd just propose to drop it.

The breakage is that, if you click something, the click will not go into
a point that you intended to click. I.e. you can't even undo the damage
using the xkeystone GUI.

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

Title:
  Panning in a virtual monitor is not possible after upgrade to Ubuntu
  11.10

Status in X.Org X server:
  Incomplete
Status in “xorg-server” package in Ubuntu:
  Triaged
Status in “xorg-server” source package in Precise:
  Triaged

Bug description:
  When I go  for a virtual monitor by issuing command "xrandr --output
  LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at
  resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to
  Ubuntu 11.10), the WM bars on top and left side of the screen (in
  Unity) look like extending to the new area, but I cannot move the
  pointer to the new extra area and so I cannot pan. As far as I
  understood by reading around, this *could* be a bug in package "xorg-
  server" rather than in "xrandr" and *could* be related to the
  boundaries set for cursor position.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu7
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Mon Oct 24 20:40:14 2011
  DistUpgraded: Log time: 2011-10-22 12:17:44.515205
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus:
   dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! 
Diff between built and installed module!)
   dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff 
between built and installed module!)
   dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller 
[8086:2592] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0182]
 Subsystem: Dell Device [1028:0182]
  MachineType: Dell Inc. Latitude D610
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 3.3V 32-bit PC Card
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   LANGUAGE=it_IT:it:en_GB:en
  ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet 
splash rootdelay=15
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago)
  dmi.bios.date: 03/02/2005
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0D4571
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D610
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 1378627] Re: chromium-browser crashed with SIGSEGV

2014-10-08 Thread C de-Avillez 
happened (twice,so far) on restart.

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

Title:
  chromium-browser crashed with SIGSEGV

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

Bug description:
  No idea what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Wed Oct  8 07:12:48 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2013-12-22 (289 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=3043.0.199670400\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,11,15\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x8086\ --gpu-device-id=0x0126\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7fc0e6b1963f:mov0x1f8(%rax),%r15
   PC (0x7fc0e6b1963f) ok
   source "0x1f8(%rax)" (0x01f8) not located in a known VMA region (needed 
readable region)!
   destination "%r15" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
   ?? () from /usr/lib/chromium-browser/libs/libgpu.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
  Title: chromium-browser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-14T18:16:36.315577

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

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

[Desktop-packages] [Bug 1241972] Re: Drag and drop from Dash to Desktop doesn't work

2014-10-08 Thread  ͡° ͜ʖ ͡° 
** Changed in: chromium-browser
 Assignee: Moris (nerimoris) => (unassigned)

** Changed in: hundredpapercuts
 Assignee: Moris (nerimoris) => (unassigned)

** Changed in: unity
 Assignee: Moris (nerimoris) => (unassigned)

** Changed in: unity/7.1
 Assignee: Moris (nerimoris) => (unassigned)

** Changed in: unity/7.2
 Assignee: Moris (nerimoris) => (unassigned)

** Changed in: unity (Ubuntu)
 Assignee: Moris (nerimoris) => (unassigned)

** Changed in: nautilus (Ubuntu)
 Assignee: Moris (nerimoris) => (unassigned)

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

Title:
  Drag and drop from Dash to Desktop doesn't work

Status in Chromium Browser:
  New
Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in Unity 7.1 series:
  Won't Fix
Status in Unity 7.2 series:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  When you try to drag and drop an app from Dash (both from app lens and
  home lens) to Desktop, system display an error and the shortcut isn't
  created.

  The error is:
  Error while copying - There was an error getting information about "/".
  More details: The specified location is not supported

  Then there are four buttons: "Cancel" - "Skip all" - "Skip" - "Retry".

  Way to reproduce:
  - Open the dash
  - Drag an app icon and drop on desktop

  What happend:
  - An error is raised

  What expected:
  - A shortcut is created

  With file, music and photo is all ok.

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

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

[Desktop-packages] [Bug 1373404] Re: No warning of high volume level

2014-10-08 Thread kevin gunn 
after some discussion with LT wrt timeline & requirement for this bug:
1) we'll rely on device hardware/drivers for the hard limits for
2) we provide a warning at 75% of slider

with this, makes pulse opinion.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Opinion

** Changed in: ubuntu-ux
   Status: Fix Committed => New

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

Title:
  No warning of high volume level

Status in Ubuntu UX bugs:
  New
Status in “pulseaudio” package in Ubuntu:
  Opinion
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  For the purpose of this Decision, a ‘personal music player’ means a
  portable device, that is not covered by Directive 1999/5/EC or
  Directive 2006/95/EC, with headphones or earphones, used to listen to
  recorded, generated or broadcasted sound.

  1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the
  safety requirement for personal music players shall be the following:
  Personal music players shall be designed and manufactured in a manner
  that ensures that, under reasonably foreseeable conditions of use,
  they are inherently safe and do not cause hearing damage.

  2. The requirement set out in paragraph 1 shall include in particular
  the following:

  (1) Exposure to sound levels shall be time limited to avoid hearing
  damage. At 80 dB(A) exposure time shall be limited to 40 hours/week,
  whereas at 89 dB(A) exposure time shall be limited to 5 hours/week.
  For other exposure levels a linear intra- and extrapolation applies.
  Account shall be taken of the dynamic range of sound and the
  reasonably foreseeable use of the products.

  (2) Personal music players shall provide adequate warnings on the risks 
involved in using the device and to the ways of avoiding them and information 
to users in cases where exposure poses a risk of hearing damage.
  

  Related documents:
  http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/
  http://europa.eu/rapid/press-release_IP-08-1492_en.htm
  http://ec.europa.eu/news/environment/090928_en.htm
  http://europa.eu/rapid/press-release_IP-09-1364_en.htm

  Design:

  : "Whenever you are using
  headphones, Ubuntu should frequently measure the volume of sound
  output. Whenever it is over 47 dB(A), your quota should be reduced
  accordingly..."

  [Originally reported in private bug 1370591.]

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

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

[Desktop-packages] [Bug 1104230] Re: DisplayPort 1.2 MST support is missing in the Intel driver

2014-10-08 Thread Dariusz Gadomski 
Vincent, what you could do is to take a look at this instruction:
https://01.org/linuxgraphics/node/358

Based on this you could:

sudo add-apt-repository ppa:dgadomski/linux-mst
sudo add-apt-repository ppa:xorg-edgers/ppa

sudo apt-get update
sudo apt-get install linux-image-3.16.0-19-generic # this will install the 
patched kernel for trusty
sudo apt-get install xserver-xorg-video-intel# this should get you 
the xorg-edgers intel driver with all the dependencies needed

Now you can reboot and verify with xrandr (like in the linked
instruction) whether your displays are available or not.

Please make sure you have ppa-purge available (sudo apt-get install ppa-purge) 
so you will be able to revert it later if anything goes wrong with:
sudo ppa-purge ppa:dgadomski/linux-mst ppa:xorg-edgers/ppa

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

Title:
  DisplayPort 1.2 MST support is missing in the Intel driver

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

Bug description:
  I have two recent DisplayPort monitors, both supporting the 1.2
  version of the standard and one containing an MST hub (DELL 2913WM).

  I have an Intel Haswell based NUC connected over mini-displayport to
  the display containing the hub, then the second display is plugged in
  that one over DisplayPort.

  DisplayPort 1.2 is enabled on the display containing the hub and the
  second display lights up fine but just works as a clone of the first
  display, without ever showing up in xrandr, dmesg or any other useful
  logs I could find.

  My understanding of MST is that the second display should show up as
  DP2 on my laptop so I can configure it as I would any other display.

  UPDATE: Updated the bug report after it was pointed out that the
  original test hardware, a Lenovo x230 isn't DP 1.2 capable. The same
  test on hardware also fails, due to missing support for MST in the
  driver.

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

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

[Desktop-packages] [Bug 1319687] Re: SuiteSparse fails to link in shared library due to missing -fPIC in libsuitesparseconfig.a

2014-10-08 Thread Arne Morten Kvarving 
doh, missed your response. thanks a lot!

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

Title:
  SuiteSparse fails to link in shared library due to missing -fPIC in
  libsuitesparseconfig.a

Status in “suitesparse” package in Ubuntu:
  Confirmed

Bug description:
  The config library is only available as a .a which is not compiled
  with -fPIC. Thus, linking into shared libraries fails on AMD64.

  Attaching a minimal program to trigger the bug.

  gcc -shared -fPIC -o test.so suitetest.cpp -lumfpack
  -lsuitesparseconfig

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

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

[Desktop-packages] [Bug 1309605] Re: OSD (skip, pause) take full window (and fullscreen) height

2014-10-08 Thread D3Hunter 
Patch code below to totem3.10.1, will fix this annoying problem.

**It may cause other display problems as i haven't run a full test**

--- totem-3.10.1/src/totem-object.c 2013-09-29 20:18:43.0 +0800
+++ totem-3.10.1-myversion/src/totem-object.c   2014-10-08 
21:59:52.266918845 +0800
@@ -3356,6 +3356,7 @@
icon_name = totem_get_rtl_icon_name 
("media-playback-start");
else
icon_name = "media-playback-pause-symbolic";
+   icon_name = NULL;
totem_fullscreen_show_popups_or_osd (totem->fs, icon_name, 
FALSE);
totem_action_play_pause (totem);
return TRUE;
@@ -3692,6 +3693,7 @@
retval = FALSE;
}
 
+   icon_name = NULL;
if (icon_name != NULL)
totem_fullscreen_show_popups_or_osd (totem->fs,
 icon_name,

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

Title:
  OSD (skip, pause) take full window (and fullscreen) height

Status in Totem Movie Player:
  Expired
Status in “totem” package in Ubuntu:
  Confirmed

Bug description:
  The  OSD icons for forward/backward skip and pause have the wrong
  heigt. They take the full (sometimes even more) height on the player
  window and also full height in fullscreen mode.

  This appeared after the upgrade to trusty (totem 3.10.1)

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

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

[Desktop-packages] [Bug 1378861] [NEW] Renaming the binary

2014-10-08 Thread Sascha Manns 
Public bug reported:

Please doesn't rename the binary from xml -> xmlstarlet. The Upstream
project produces a /usr/bin/xml.

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

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

Title:
  Renaming the binary

Status in “xmlstarlet” package in Ubuntu:
  New

Bug description:
  Please doesn't rename the binary from xml -> xmlstarlet. The Upstream
  project produces a /usr/bin/xml.

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

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

[Desktop-packages] [Bug 1298552] Re: bluetooth enabled after resume

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

** Changed in: pm-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  bluetooth enabled after resume

Status in “pm-utils” package in Ubuntu:
  Confirmed

Bug description:
  bug observed on ubuntu 14.04 trusty.

  after waking up after suspend the bluetooth function is activated,
  even if it was deactivated before suspending.

  03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230
  [Rainbow Peak] (rev 34)

  i would be glad for any help with this.

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

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

[Desktop-packages] [Bug 1354823] Re: FFe: Please merge or sync usb-modeswitch from Debian unstable/testing - current package is obsolete and latest usb-modeswitch-data will not work

2014-10-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:ubuntu/utopic-proposed/usb-modeswitch

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

Title:
  FFe: Please merge or sync usb-modeswitch from Debian unstable/testing
  - current package is obsolete and latest usb-modeswitch-data will not
  work

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  We believe that usb-modeswitch needs to be synched from Debian again:

  New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-
  data (20140529) released 4 months ago and were packaged in Debian
  unstable since June!

  Lots of other Huawei related issues, like bug #1308895, bug #1192297
  and lots of other bugs are fixed in updated usb-modeswitch
  (2.2.0+repack0-2) and usb-modeswitch-data (20140529-1) packages in
  Debian unstable.

  Please merge usb-modeswitch 2.2.0+repack0-2 package from Debian
  unstable to Ubuntu Utopic.

  Mathieu Trudel-Lapierre already did the merging job (see branch
  bellow) - please merge usb-modeswitch 2.2.0+repack0-2 package from
  Debian unstable to Ubuntu 14.10 (Utopic).

  Here is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
  lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
  
https://code.launchpad.net/~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0

  Here is debian/changelog:

  usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
     * Add patch to set TMPDIR to /run, add Build-Depends version constraint to
   pull a libjim supporting the setting of TMPDIR (Closes: #751271)

  usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
    * New 2.2.0 upstream release
  - Introduction of parameter "HuaweiNewMode", wrapping the standard bulk
    message for all newer Huawei devices;
  - Support for generic fallback config files, combined with OS switch (per
    vendor ID);
    * Repack the upstream tarball:
  - Drop the code copy of jimtcl.
    * Bump usb-modeswitch-data depends to 20140529
    * Update VCS-* fields to canonical form
   -- Didier Raboud  Mon, 09 Jun 2014 11:21:08 +0200

  And here is usb-modeswitch-data debian/changelog:
  
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140722)
  SourcePackage: usb-modeswitch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1354823/+subscriptions

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

[Desktop-packages] [Bug 1373404] Re: No warning of high volume level

2014-10-08 Thread Matthew Paul Thomas 
Albert, thanks for that survey of how various systems meet Requirement
2.2. I'm fairly confident in my design for that, though, so I'm much
more interested in how they meet Requirement 2.1. :-)

I understand that 2.1 is much more difficult to implement (regardless of
whether it's done in the driver or in pulseaudio), so it may make sense
to split this into two bug reports.

** Changed in: ubuntu-ux
   Status: New => Fix Committed

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

Title:
  No warning of high volume level

Status in Ubuntu UX bugs:
  Fix Committed
Status in “pulseaudio” package in Ubuntu:
  Opinion
Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  The EU has a legal requirement for personal music players to prevent hearing 
damage.
  http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490&rid=1
  

  For the purpose of this Decision, a ‘personal music player’ means a
  portable device, that is not covered by Directive 1999/5/EC or
  Directive 2006/95/EC, with headphones or earphones, used to listen to
  recorded, generated or broadcasted sound.

  1. For the purpose of Article 4(1)(a) of Directive 2001/95/EC, the
  safety requirement for personal music players shall be the following:
  Personal music players shall be designed and manufactured in a manner
  that ensures that, under reasonably foreseeable conditions of use,
  they are inherently safe and do not cause hearing damage.

  2. The requirement set out in paragraph 1 shall include in particular
  the following:

  (1) Exposure to sound levels shall be time limited to avoid hearing
  damage. At 80 dB(A) exposure time shall be limited to 40 hours/week,
  whereas at 89 dB(A) exposure time shall be limited to 5 hours/week.
  For other exposure levels a linear intra- and extrapolation applies.
  Account shall be taken of the dynamic range of sound and the
  reasonably foreseeable use of the products.

  (2) Personal music players shall provide adequate warnings on the risks 
involved in using the device and to the ways of avoiding them and information 
to users in cases where exposure poses a risk of hearing damage.
  

  Related documents:
  http://ec.europa.eu/health/opinions/en/hearing-loss-personal-music-player-mp3/
  http://europa.eu/rapid/press-release_IP-08-1492_en.htm
  http://ec.europa.eu/news/environment/090928_en.htm
  http://europa.eu/rapid/press-release_IP-09-1364_en.htm

  Design:

  : "Whenever you are using
  headphones, Ubuntu should frequently measure the volume of sound
  output. Whenever it is over 47 dB(A), your quota should be reduced
  accordingly..."

  [Originally reported in private bug 1370591.]

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

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

[Desktop-packages] [Bug 1378861] Re: Renaming the binary

2014-10-08 Thread Sascha Manns 
Just read the affected bugs. I think a ln -s /usr/bin/xmlstarlet
/usr/bin/xml can be a solution.

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

Title:
  Renaming the binary

Status in “xmlstarlet” package in Ubuntu:
  New

Bug description:
  Please doesn't rename the binary from xml -> xmlstarlet. The Upstream
  project produces a /usr/bin/xml.

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

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

[Desktop-packages] [Bug 1378884] [NEW] Please update WPA supplicant to 2.2

2014-10-08 Thread Michael Schaller 
Public bug reported:

WPA supplicant version 2.2 has been released 4 months ago.

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


** Tags: utopic

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

Title:
  Please update WPA supplicant to 2.2

Status in “wpa” package in Ubuntu:
  New

Bug description:
  WPA supplicant version 2.2 has been released 4 months ago.

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

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

[Desktop-packages] [Bug 1378886] [NEW] package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui appartient aussi

2014-10-08 Thread Zied ALAYA 
Public bug reported:

No thing special.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: shotwell-common 0.20.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
Date: Wed Oct  8 16:05:07 2014
DuplicateSignature: package:shotwell-common:0.20.1-0ubuntu1:tentative de 
remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui appartient 
aussi au paquet shotwell 0.20.0-1~trusty1
ErrorMessage: tentative de remplacement de « 
/usr/share/appdata/shotwell.appdata.xml », qui appartient aussi au paquet 
shotwell 0.20.0-1~trusty1
InstallationDate: Installed on 2013-03-09 (578 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308)
PackageArchitecture: all
SourcePackage: shotwell
Title: package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui 
appartient aussi au paquet shotwell 0.20.0-1~trusty1
UpgradeStatus: Upgraded to utopic on 2014-10-02 (6 days ago)

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


** Tags: amd64 apport-package third-party-packages utopic

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

Title:
  package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade:
  tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml
  », qui appartient aussi au paquet shotwell 0.20.0-1~trusty1

Status in “shotwell” package in Ubuntu:
  New

Bug description:
  No thing special.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: shotwell-common 0.20.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  Date: Wed Oct  8 16:05:07 2014
  DuplicateSignature: package:shotwell-common:0.20.1-0ubuntu1:tentative de 
remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui appartient 
aussi au paquet shotwell 0.20.0-1~trusty1
  ErrorMessage: tentative de remplacement de « 
/usr/share/appdata/shotwell.appdata.xml », qui appartient aussi au paquet 
shotwell 0.20.0-1~trusty1
  InstallationDate: Installed on 2013-03-09 (578 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308)
  PackageArchitecture: all
  SourcePackage: shotwell
  Title: package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui 
appartient aussi au paquet shotwell 0.20.0-1~trusty1
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (6 days ago)

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

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

[Desktop-packages] [Bug 1351977] Re: New upstream release 0.9.10.0

2014-10-08 Thread Michael Schaller 
FYI: I've opened http:://pad.lv/1378884 to also update WPA supplicant to
2.2.

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

Title:
  New upstream release 0.9.10.0

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Debian:
  Fix Released

Bug description:
  Please update package in Utopic to 0.9.10.0.

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

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

[Desktop-packages] [Bug 1354823] Re: FFe: Please merge or sync usb-modeswitch from Debian unstable/testing - current package is obsolete and latest usb-modeswitch-data will not work

2014-10-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package usb-modeswitch -
2.2.0+repack0-2ubuntu1

---
usb-modeswitch (2.2.0+repack0-2ubuntu1) utopic; urgency=medium

  * Merge from unstable; remaining changes: (LP: #1354823)
- patch to rewrite dispatcher to C.
- debian/patches/redirect_dispatcher_output.patch: redirect all dispatcher
  output when called from udev to /dev/null.
- Replace libjim depends with libpipeline-dev, libudev-dev.
 -- Mathieu Trudel-LapierreFri, 03 Oct 2014 10:46:39 
-0400

** Changed in: usb-modeswitch (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  FFe: Please merge or sync usb-modeswitch from Debian unstable/testing
  - current package is obsolete and latest usb-modeswitch-data will not
  work

Status in “usb-modeswitch” package in Ubuntu:
  Fix Released

Bug description:
  We believe that usb-modeswitch needs to be synched from Debian again:

  New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-
  data (20140529) released 4 months ago and were packaged in Debian
  unstable since June!

  Lots of other Huawei related issues, like bug #1308895, bug #1192297
  and lots of other bugs are fixed in updated usb-modeswitch
  (2.2.0+repack0-2) and usb-modeswitch-data (20140529-1) packages in
  Debian unstable.

  Please merge usb-modeswitch 2.2.0+repack0-2 package from Debian
  unstable to Ubuntu Utopic.

  Mathieu Trudel-Lapierre already did the merging job (see branch
  bellow) - please merge usb-modeswitch 2.2.0+repack0-2 package from
  Debian unstable to Ubuntu 14.10 (Utopic).

  Here is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
  lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
  
https://code.launchpad.net/~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0

  Here is debian/changelog:

  usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
     * Add patch to set TMPDIR to /run, add Build-Depends version constraint to
   pull a libjim supporting the setting of TMPDIR (Closes: #751271)

  usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
    * New 2.2.0 upstream release
  - Introduction of parameter "HuaweiNewMode", wrapping the standard bulk
    message for all newer Huawei devices;
  - Support for generic fallback config files, combined with OS switch (per
    vendor ID);
    * Repack the upstream tarball:
  - Drop the code copy of jimtcl.
    * Bump usb-modeswitch-data depends to 20140529
    * Update VCS-* fields to canonical form
   -- Didier Raboud  Mon, 09 Jun 2014 11:21:08 +0200

  And here is usb-modeswitch-data debian/changelog:
  
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140722)
  SourcePackage: usb-modeswitch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1354823/+subscriptions

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

[Desktop-packages] [Bug 1378665] Re: Xorg crashed with SIGABRT in pci_device_next()

2014-10-08 Thread Robert Avant 
*** This bug is a duplicate of bug 1341155 ***
https://bugs.launchpad.net/bugs/1341155

I found that I had not updated.  After Updating I do not appear to have
a problem.

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

Title:
  Xorg crashed with SIGABRT in pci_device_next()

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

Bug description:
  There is a message indicating that the system cannot find the back
  light controler.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xserver-xorg-core 2:1.16.0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CrashCounter: 1
  Date: Wed Oct  8 08:03:53 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7620G] [1002:9907] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:216c]
 Subsystem: Hewlett-Packard Company Device [103c:216c]
  InstallationDate: Installed on 2014-09-28 (9 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion TS 15 Notebook PC
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic.efi.signed 
root=UUID=0b66c77e-1489-4205-ac58-a12830847857 ro recovery nomodeset
  Renderer: Software
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   pci_device_next () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   pci_device_find_by_slot () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   pci_device_vgaarb_init () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0
   ?? ()
   xf86BusConfig ()
  Title: Xorg crashed with SIGABRT in pci_device_next()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 216C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 30.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd06/03/2014:svnHewlett-Packard:pnHPPavilionTS15NotebookPC:pvr088110305E0620100:rvnHewlett-Packard:rn216C:rvr30.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion TS 15 Notebook PC
  dmi.product.version: 088110305E0620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Wed Oct  8 08:08:21 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1

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

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

[Desktop-packages] [Bug 1353185] Re: Chromium 36 upgrade will not execute

2014-10-08 Thread wb8nbs 
Same issue here. Athlon 2800 processor

jbh@junkbox:/usr/bin$ sudo ./chromium-browser --version
Chromium 37.0.2062.120 Ubuntu 12.04

jbh@junkbox:/proc$ cat cpuinfo 
processor   : 0
vendor_id   : AuthenticAMD
cpu family  : 6
model   : 10
model name  : AMD Athlon(tm) XP 2800+
stepping: 0
cpu MHz : 2087.500
cache size  : 512 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 1
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat 
pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up
bogomips: 4176.24
clflush size: 32
cache_alignment : 32
address sizes   : 34 bits physical, 32 bits virtual
power management: ts

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

Title:
  Chromium 36 upgrade will not execute

Status in “chromium-browser” package in Ubuntu:
  Fix Released

Bug description:
  Chromium will no longer start after version 36 upgrade. Previous
  version worked ok. Execution from command line reports "Illegal
  instruction (core dumped)". Nothing displayed on screen.

  lshw reports:

  description: Tower Computer
  version: System Version
  width: 32 bits
  capabilities: smbios-2.3 dmi-2.3
  configuration: boot=normal chassis=tower
*-core
 description: Motherboard
 product: A7V8X
 vendor: ASUSTeK Computer INC.
   *-firmware
description: BIOS
vendor: Award Software, Inc.
physical id: 0
version: ASUS A7V8X ACPI BIOS Revision 1010
   *-cpu
description: CPU
product: AMD Athlon(TM) XP 2400+
vendor: Hynix Semiconductor (Hyundai Electronics)
   *-memory
description: System Memory
slot: System board or motherboard
size: 1GiB

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 36.0.1985.125-0ubuntu1.12.04.0~pkg897
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Tue Aug  5 19:35:30 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu-2d
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/
  DmesgChromium: [   28.356536] type=1400 audit(1407283433.748:15): 
apparmor="STATUS" operation="profile_load" 
name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" 
pid=853 comm="apparmor_parser"
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to precise on 2012-09-15 (689 days ago)
  chromium-default: CHROMIUM_FLAGS=""
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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

[Desktop-packages] [Bug 1378886] Re: package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade: tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui appartient aussi a

2014-10-08 Thread Iain Lane 
I think you've used a PPA or a non-official package. Our official
packages don't have this problem, so we can't help you I'm afraid.

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

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

Title:
  package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade:
  tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml
  », qui appartient aussi au paquet shotwell 0.20.0-1~trusty1

Status in “shotwell” package in Ubuntu:
  Invalid

Bug description:
  No thing special.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: shotwell-common 0.20.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  Date: Wed Oct  8 16:05:07 2014
  DuplicateSignature: package:shotwell-common:0.20.1-0ubuntu1:tentative de 
remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui appartient 
aussi au paquet shotwell 0.20.0-1~trusty1
  ErrorMessage: tentative de remplacement de « 
/usr/share/appdata/shotwell.appdata.xml », qui appartient aussi au paquet 
shotwell 0.20.0-1~trusty1
  InstallationDate: Installed on 2013-03-09 (578 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308)
  PackageArchitecture: all
  SourcePackage: shotwell
  Title: package shotwell-common 0.20.1-0ubuntu1 failed to install/upgrade: 
tentative de remplacement de « /usr/share/appdata/shotwell.appdata.xml », qui 
appartient aussi au paquet shotwell 0.20.0-1~trusty1
  UpgradeStatus: Upgraded to utopic on 2014-10-02 (6 days ago)

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

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

[Desktop-packages] [Bug 1378794] Re: package shotwell-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in package shotwell

2014-10-08 Thread Iain Lane 
Looks like you're using a PPA package - sorry, but Ubuntu doesn't have
this bug. Please report it to the PPA owner.

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

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

Title:
  package shotwell-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which
  is also in package shotwell 0.20.0+2611~ubuntu14.04.1

Status in “shotwell” package in Ubuntu:
  Invalid

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: shotwell-common (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic i686
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: i386
  Date: Wed Oct  8 14:05:15 2014
  DuplicateSignature: package:shotwell-common:(not installed):trying to 
overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in package 
shotwell 0.20.0+2611~ubuntu14.04.1
  ErrorMessage: trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', 
which is also in package shotwell 0.20.0+2611~ubuntu14.04.1
  InstallationDate: Installed on 2014-06-13 (116 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: shotwell
  Title: package shotwell-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/appdata/shotwell.appdata.xml', which is also in 
package shotwell 0.20.0+2611~ubuntu14.04.1
  UpgradeStatus: Upgraded to utopic on 2014-09-22 (15 days ago)

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

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

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

2014-10-08 Thread Brian Smith 
Public bug reported:

Failed to build on update to 3.16.0.21

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
Uname: Linux 3.16.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-21-generic
Date: Wed Oct  8 11:31:48 2014
InstallationDate: Installed on 2014-07-11 (88 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140709)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package utopic

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

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

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

Bug description:
  Failed to build on update to 3.16.0.21

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-21-generic
  Date: Wed Oct  8 11:31:48 2014
  InstallationDate: Installed on 2014-07-11 (88 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140709)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected

2014-10-08 Thread Launchpad Bug Tracker 
This bug was fixed in the package ubuntu-touch-session -
0.108+14.10.20141008-0ubuntu1

---
ubuntu-touch-session (0.108+14.10.20141008-0ubuntu1) utopic; urgency=low

  [ Ricardo Salveti de Araujo ]
  * touch.pa: fixing loading order and adding default devices (LP:
#1363083)
 -- Ubuntu daily releaseWed, 08 Oct 2014 
05:12:22 +

** Changed in: ubuntu-touch-session (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Music playback does not re-route audio when Bluetooth speaker
  connected/disconnected

Status in “pulseaudio” package in Ubuntu:
  In Progress
Status in “ubuntu-touch-session” package in Ubuntu:
  Fix Released

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth speaker is connected/disconnected to the krillin, the music 
playback route does not automatically update to accomodate this. The music app 
must be re-started for the new configuration to work.

  STEPS:
  1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss)
  2) Start music playback
  3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings

  EXPECTED RESULT:
  The music should play back through the Bluetooth speaker until it is 
disconnected. When the speaker is disconnected it should revert to using the 
krillin loud speaker.

  ACTUAL RESULT:
  The music plays back through the Bluetooth speaker until it is disconnected. 
When the speaker is disconnected, there is no music heard from the krillin. The 
music app is still playing the track as the progress bar is still updating, but 
there is no sound.

  When the music app is re-started, music will play through the krillin
  loud speaker.

  NOTES:
  The same problem is observed for the opposite situation where a Bluetooth 
speaker is connected to the device when it is already playing music through the 
krillin loud speaker. The Bluetooth speaker will only be used once the music 
app is restarted.

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

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

[Desktop-packages] [Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()

2014-10-08 Thread Iain Lane 
This is in Utopic now

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

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

** Changed in: pitivi (Ubuntu Trusty)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

Title:
  pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()

Status in PiTiVi , Non-linear video editor:
  Fix Released
Status in “pitivi” package in Ubuntu:
  Fix Released
Status in “pitivi” source package in Trusty:
  New

Bug description:
  [Impact]

  Some users are unable to start Pitivi on 14.04 LTS, because of a
  crasher.

  [Test Case]

  Start pitivi on affected computer.

  [Regression Potential]

  The suggested patch that fixes the problem changes the load order in
  python, which seem fragile then. However at least testing on one
  computer that did not have the crash originally, the fix doesn't break
  anything either.

  ---

  I just upgraded to Kubuntu 14.04 (Trusty) yesterday, and pitivi
  stopped working. It segfaults immediately, with the following stdout
  error:

  lmilano@grisell:crash$ pitivi
  Missing soft dependency:
  - pycanberra not found on the system
  -> enables sound notifications when rendering is complete
  Segmentation fault (core dumped)

  Apport is not popping up, even if I launch pitivi from the main menu
  in KDE. But it did, just once, and it dumped a report in /var/crash -
  I will try to upload that file manually.

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

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

[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

2014-10-08 Thread Iain Lane 
** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

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

Bug description:
  On up to date Raring alpha, on System Settings > Mouse & Touchpad the
  Mouse settings are completely missing.  The General and Touchpad
  sections are there but none for mouse.  See attached screenshot.

  xinput --list shows
  ~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MOSART Semi. 2.4G Keyboard Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ MOSART Semi. 2.4G Keyboard Mouseid=10   [slave  
keyboard (3)]
  ↳ Dell Dell USB Keyboard  id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  and from lsusb:
  Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser 
Mouse SMWLL11]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Sat Feb 23 09:40:41 2013
  InstallationDate: Installed on 2012-08-01 (205 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1378919] [NEW] After going to lock screen can't login as not prompted for password - maybe not a unity bug

2014-10-08 Thread Páll Haraldsson 
Public bug reported:

Expected:

Under my name on login screen I should see the field to put in my
password. [I took a picture, but probably not to helpful?]

[Just a guess, could it be malloc not returning memory if memory tight?]

uptime
 16:12:36 up 9 days

I update all that matters when I reset. At least unity:
2014-09-29 08:19:43 status installed unity:amd64 7.2.3+14.04.20140826-0ubuntu1
/var/log/dpkg.log.1:2014-09-26 13:50:09 status installed libglib2.0-0:amd64 
2.40.2-0ubuntu1
/var/log/dpkg.log.1:2014-09-26 13:50:10 status installed libglib2.0-bin:amd64 
2.40.2-0ubuntu1
/var/log/dpkg.log.1:2014-09-29 08:19:42 status installed libglib2.0-0:amd64 
2.40.2-0ubuntu1


There are exections that I do not think matters:

See: https://bugs.launchpad.net/unity/+bug/1378879
for bug that I manually submitted. [Then I couldn't run "ubuntu-bug unity" 
after pressing Win-start button. I still haven't reset machine and still can't 
but noticed I could from a shell.]

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Oct  8 16:00:40 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed
 bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed
 nvidia-331, 331.38, 3.13.0-36-generic, x86_64: installed
 nvidia-331, 331.38, 3.13.0-37-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: NVIDIA Corporation Device [10de:0835]
InstallationDate: Installed on 2014-08-26 (43 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Precision T1650
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=b342558f-2de5-4795-857d-67d51db3a726 ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0X9M3X
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/31/2013:svnDellInc.:pnPrecisionT1650:pvr01:rvnDellInc.:rn0X9M3X:rvrA04:cvnDellInc.:ct6:cvr:
dmi.product.name: Precision T1650
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Sep 29 08:35:11 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu

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

Title:
   After going to lock screen can't login as not prompted for password -
  maybe not a unity bug

Status in “unity” package in Ubuntu:
  New

Bug description:
  Expected:

  Under my name on login screen I should see the field to put in my
  password. [I took a picture, but probably not to helpful?]

  [Just a guess, could it be malloc not returning memory if memory
  tight?]

  uptime
   16:12:36 up 9 days

  I update all that matters when I reset. At least unity:
  2014-09-29 08:19:43 status installed unity:amd64 7.2.3+14.04.20140826-0ubuntu1
  /var/log/dpkg.log.1:2014-09-26 13:50:09 status installed libg

[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

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

** Changed in: unity-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Mouse settings missing from Mouse & Touchpad dialog

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

Bug description:
  On up to date Raring alpha, on System Settings > Mouse & Touchpad the
  Mouse settings are completely missing.  The General and Touchpad
  sections are there but none for mouse.  See attached screenshot.

  xinput --list shows
  ~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MOSART Semi. 2.4G Keyboard Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ MOSART Semi. 2.4G Keyboard Mouseid=10   [slave  
keyboard (3)]
  ↳ Dell Dell USB Keyboard  id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  and from lsusb:
  Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser 
Mouse SMWLL11]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Sat Feb 23 09:40:41 2013
  InstallationDate: Installed on 2012-08-01 (205 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1303086] Re: Pointer Speed Missing in Unity Settings for Mouse & Trackpad

2014-10-08 Thread Iain Lane 
*** This bug is a duplicate of bug 1132063 ***
https://bugs.launchpad.net/bugs/1132063

This is the same as bug #1132063, let's take it there, thanks for
reporting

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

** This bug has been marked a duplicate of bug 1132063
   Mouse settings missing from Mouse & Touchpad dialog

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

Title:
  Pointer Speed Missing in Unity Settings for Mouse & Trackpad

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

Bug description:
  On updated Ubuntu 14.04 final, the System Settings > Mouse & Touchpad
  dialog is missing several mouse settings, like the "pointer Speed"
  setting. See attached screenshot.

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

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

[Desktop-packages] [Bug 1208988] Re: AppArmor no longer mediates access to path-based AF_UNIX socket files

2014-10-08 Thread Jamie Strandboge 
Marking the apparmor task as 'fixed' since this is available in the
upstream beta tarballs.

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

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

Title:
  AppArmor no longer mediates access to path-based AF_UNIX socket files

Status in AppArmor Linux application security framework:
  Fix Released
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “firefox” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux-grouper” package in Ubuntu:
  Fix Released
Status in “linux-maguro” package in Ubuntu:
  Fix Released
Status in “linux-mako” package in Ubuntu:
  Fix Released
Status in “linux-manta” package in Ubuntu:
  Fix Released
Status in “apparmor” source package in Saucy:
  Fix Released
Status in “apparmor-easyprof-ubuntu” source package in Saucy:
  Fix Released
Status in “firefox” source package in Saucy:
  Fix Released

Bug description:
  [Impact]

   * AppArmor removed unix domain socket mediation as part of the 2.4
  (karmic) rewrite to the security_path hooks so that it could be
  upstreamed into the main kernel. The result being apparmor no longer
  mediates access to AF_UNIX socket files. Or more specifically it does
  not mediation connections between sockets, creation of a socket within
  the filesystem is mediated

   * Confined applications can currently read from and write to any AF_UNIX
     socket files

   * Existing AppArmor profiles that contain file rules granting write access to
     AF_UNIX socket files are effectively being ignored

   * The move from the vfs hooks patches (old, out-of-tree) AppArmor and the 
security_path hooks
     apparmor incorporated into mainline in 2.6.36 were the cause of this 
regression.

     apparmor 2.4 (version in karmic) also removed other features are part of 
the rewrite to
     security_path hooks/upstreaming effort.

   * For Ubuntu, Karmic 9.10  and all newer, releases are affected.
     8.04 LTS used the vfs patches and was not affected.

  * Mediation of unix domain filesystem based sockets is needed for
  13.10 click apps confinement

  [Test Case]

   * Confining dbus-send and sending a message to the system bus is an easy
     manual testing method. Load a profile for dbus-send:

  $ cat << EOF | sudo apparmor_parser -r
  #include 

  /usr/bin/dbus-send {
    #include 
    /usr/bin/dbus-send r,
  #  /var/run/dbus/system_bus_socket rw,
  }
  EOF

   * Note that the system_bus_socket rule is commented out. Now, run dbus-send
     under strace and see if the connect() fails. Here's the unexpected output,
     taken from an Ubuntu Saucy system:

  $ strace -e connect -- \
   dbus-send --system --dest=org.freedesktop.DBus \
   /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  connect(3, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 
33) = 0
  +++ exited with 0 +++

   * Here's the expected output, taken from an 8.04 LTS system:

  $ strace -e connect -- \
   dbus-send --system --dest=org.freedesktop.DBus \
   /org/freedesktop/DBus org.freedesktop.DBus.ListNames
  connect(3, {sa_family=AF_FILE, path="/var/run/dbus/system_bus_socket"}, 33) = 
-1 EACCES (Permission denied)
  Failed to open connection to system message bus: Failed to connect to socket 
/var/run/dbus/system_bus_socket: Permission denied

   * Or, you can apply the AppArmor regression test suite patch attached to this
     bug and run the automated tests:

  $ cd tests/regression/apparmor
  $ make unix_fd_{server,client} unix_socket_file{,_client} >/dev/null
  $ sudo bash unix_fd_server.sh
  $ sudo bash unix_socket_file.sh

  [Regression Potential]

   * Profiles developed with affected kernels aren't likely to have the 
necessary
     rules because the proper LSM hook was not implemented in those kernels, so
     the policy writer didn't need to grant access to AF_UNIX socket files

   * The profiles shipped with AppArmor can, and will, be updated to grant 
access
     to AF_UNIX socket files, but local policy modifications cannot be addressed
     by upstream/distros. Once updated kernels begin enforcing mediation of
     AF_UNIX socket files, rules in local profiles may no longer be sufficient,
     resulting in new AppArmor denials for AF_UNIX socket files.

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

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

[Desktop-packages] [Bug 1363083] Re: Music playback does not re-route audio when Bluetooth speaker connected/disconnected

2014-10-08 Thread Launchpad Bug Tracker 
** Branch linked: lp:ubuntu/utopic-proposed/pulseaudio

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

Title:
  Music playback does not re-route audio when Bluetooth speaker
  connected/disconnected

Status in “pulseaudio” package in Ubuntu:
  In Progress
Status in “ubuntu-touch-session” package in Ubuntu:
  Fix Released

Bug description:
  krillin ubuntu-rtm/14.09-proposed build 4.
  bluez 4.101-0ubuntu19 armhf

  SUMMARY:
  When a Bluetooth speaker is connected/disconnected to the krillin, the music 
playback route does not automatically update to accomodate this. The music app 
must be re-started for the new configuration to work.

  STEPS:
  1) Pair and connect the Bluetooth speaker (BQ Altavoz Bluetooth Strauss)
  2) Start music playback
  3) Disconnect the Bluetooth speaker on krillin from the Bluetooth settings

  EXPECTED RESULT:
  The music should play back through the Bluetooth speaker until it is 
disconnected. When the speaker is disconnected it should revert to using the 
krillin loud speaker.

  ACTUAL RESULT:
  The music plays back through the Bluetooth speaker until it is disconnected. 
When the speaker is disconnected, there is no music heard from the krillin. The 
music app is still playing the track as the progress bar is still updating, but 
there is no sound.

  When the music app is re-started, music will play through the krillin
  loud speaker.

  NOTES:
  The same problem is observed for the opposite situation where a Bluetooth 
speaker is connected to the device when it is already playing music through the 
krillin loud speaker. The Bluetooth speaker will only be used once the music 
app is restarted.

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

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

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

2014-10-08 Thread henry adler 
Public bug reported:

Running Update Manager

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
DKMSKernelVersion: 3.16.0-21-generic
Date: Wed Oct  8 11:27:22 2014
InstallationDate: Installed on 2012-04-02 (919 days ago)
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package utopic

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

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

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

Bug description:
  Running Update Manager

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-21-generic
  Date: Wed Oct  8 11:27:22 2014
  InstallationDate: Installed on 2012-04-02 (919 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 
(20120328)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1211380] Re: pulseaudio socket needs confined app restrictions

2014-10-08 Thread Jamie Strandboge 
Closing trusty task

** Changed in: pulseaudio (Ubuntu Trusty)
   Status: Confirmed => Won't Fix

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

Title:
  pulseaudio socket needs confined app restrictions

Status in PulseAudio sound server:
  New
Status in “apparmor” package in Ubuntu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “pulseaudio” package in Ubuntu:
  Confirmed
Status in “apparmor” source package in Saucy:
  Fix Released
Status in “apparmor-easyprof-ubuntu” source package in Saucy:
  Fix Released
Status in “pulseaudio” source package in Saucy:
  Won't Fix
Status in “apparmor” source package in Trusty:
  Fix Released
Status in “apparmor-easyprof-ubuntu” source package in Trusty:
  Fix Released
Status in “pulseaudio” source package in Trusty:
  Won't Fix

Bug description:
  Confined applications need access to the pulseaudio socket. Currently
  several sockets are available to apps, and some allow performing
  dangerous operations, such as loading a module from an arbitrary path.

  It also allows them to enumerate installed applications by listing
  clients.

  The Pulseaudio daemon should verify if an application is confined, and
  if so, restrict access to certain commands.

  If module loading cannot be disabled for confined applications,
  perhaps it could be modified to only load modules from trusted system
  locations.

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

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

[Desktop-packages] [Bug 1378881] [NEW] nouveau video driver crashing X. Total freeze of computer 14.04.1

2014-10-08 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

14.04.1 crashes.  I suspect the nouveau video driver.  Can not use bug
report from within problem computer as it freezes very quickly after
login.  Video display freezes first with visual corruption followed by
keyboard.  Mouse works for about 10 to 20  seconds more then stops
working.  Final stage the keyboard lights start flashing.  Hard reset
required.

14.04.1 with all updates applied as of October 8th, 2014.
Using nouveau video driver
Nvidia 8800GT card

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
nouveau video driver crashing X.  Total freeze of computer  14.04.1
https://bugs.launchpad.net/bugs/1378881
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xserver-xorg-video-nouveau 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 1378881] Re: nouveau video driver crashing X. Total freeze of computer 14.04.1

2014-10-08 Thread Nathaniel Homier 
** Package changed: ubuntu => xserver-xorg-video-nouveau (Ubuntu)

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

Title:
  nouveau video driver crashing X.  Total freeze of computer  14.04.1

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  New

Bug description:
  14.04.1 crashes.  I suspect the nouveau video driver.  Can not use bug
  report from within problem computer as it freezes very quickly after
  login.  Video display freezes first with visual corruption followed by
  keyboard.  Mouse works for about 10 to 20  seconds more then stops
  working.  Final stage the keyboard lights start flashing.  Hard reset
  required.

  14.04.1 with all updates applied as of October 8th, 2014.
  Using nouveau video driver
  Nvidia 8800GT card

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

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

  1   2   3   >