[Dx-packages] [Bug 815996] Re: Desktop occasionally freezes/locks up when switching workspaces

2015-04-07 Thread Leon Liao
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority/trusty
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/815996

Title:
  Desktop occasionally freezes/locks up when switching workspaces

Status in Compiz:
  Confirmed
Status in Compiz Main Plugins:
  Confirmed
Status in Compiz Desktop Wall Plugin:
  Confirmed
Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in compiz package in Ubuntu:
  Confirmed
Status in compiz-plugins-main package in Ubuntu:
  Confirmed

Bug description:
  I'm assuming the issue is related to Compiz, but I'm not 100% sure.
  When I'm switching workspaces, it occasionally locks up (becoming more
  frequent). Most of the time, I'm going from the current one down
  (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able
  to correct things by backing out to a terminal then returning
  (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual
  screen setup acts as one large screen (windows are stretched to the
  full width of both screens) and many of the windows collect on the
  first workspace.

  
  Ubuntu 11.04 (Classic)
  All packages up-to-date.

  If there are any logs/etc that would be helpful, let me know.
  --- 
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale]
  DistroCodename: natty
  DistroRelease: Ubuntu 11.04
  DistroVariant: ubuntu
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  InstallationMedia_: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  NonfreeKernelModules: nvidia
  Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Tags:  natty natty ubuntu
  Uname: Linux 2.6.38-10-generic x86_64
  UnreportableReason: Please work this issue through technical support channels 
first.
  UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago)
  UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev 
sambashare

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

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


[Dx-packages] [Bug 1441372] [NEW] System freezes when switching accounts from the system menu

2015-04-07 Thread Rob
Public bug reported:

I've never reported a bug before, so I apologize if I'm doing something
wrong.

I have this problem when switching users. If I use the system menu and
then just click the other name, I freeze on a black screen every time. I
have to ctrl-f1, login, sudo reboot, and as far as I can see that's the
only way out.

Alternately I can go to the system menu, and then click "Lock/Switch
Account" and it's 50/50 whether it will freeze or take me back to the
screen where I can select the other user.

I have a bog-standard Ubuntu 14.04LTS installation, unity, no major
customizations. This has been driving me batty but I don't have the
ability/experience to be able to troubleshoot it properly but I feel
like it's a big enough issue that it should be reported in full. I can't
be the only person with this problem.

Description:Ubuntu 14.04.2 LTS
Release:14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-session 12.10.5+14.04.20140925-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
Uname: Linux 3.13.0-48-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr  7 19:13:55 2015
InstallationDate: Installed on 2014-06-13 (298 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: indicator-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: indicator-session (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1441372

Title:
  System freezes when switching accounts from the system menu

Status in indicator-session package in Ubuntu:
  New

Bug description:
  I've never reported a bug before, so I apologize if I'm doing
  something wrong.

  I have this problem when switching users. If I use the system menu and
  then just click the other name, I freeze on a black screen every time.
  I have to ctrl-f1, login, sudo reboot, and as far as I can see that's
  the only way out.

  Alternately I can go to the system menu, and then click "Lock/Switch
  Account" and it's 50/50 whether it will freeze or take me back to the
  screen where I can select the other user.

  I have a bog-standard Ubuntu 14.04LTS installation, unity, no major
  customizations. This has been driving me batty but I don't have the
  ability/experience to be able to troubleshoot it properly but I feel
  like it's a big enough issue that it should be reported in full. I
  can't be the only person with this problem.

  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-session 12.10.5+14.04.20140925-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16
  Uname: Linux 3.13.0-48-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 19:13:55 2015
  InstallationDate: Installed on 2014-06-13 (298 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: indicator-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1436021] Re: max volume warning for headphones not working on all devices

2015-04-07 Thread Ted Gould
Seems PA is getting the correct active port:

$ pactl list sinks
Sink #0
State: SUSPENDED
Name: sink.primary
Description: Droid sink primary
Driver: module-droid-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 4
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: sink.primary.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Droid sink primary"
device.class = "sound"
device.form_factor = "internal"
droid.hw_module = "primary"
device.icon_name = "audio-card"
Ports:
output-earpiece: Output to earpiece (priority: 200)
output-speaker: Output to speaker (priority: 300)
output-wired_headset: Output to wired headset (priority: 400, 
not available)
output-wired_headphone: Output to wired headphone (priority: 
400, not available)
output-bluetooth_sco: Output to bluetooth sco (priority: 100)
output-sco_headset: Output to sco headset (priority: 100)
output-sco_carkit: Output to sco carkit (priority: 100)
output-aux_digital: Output to aux digital (priority: 100)
output-analog_dock_headset: Output to analog dock headset 
(priority: 100)
output-digital_dock_headset: Output to digital dock headset 
(priority: 100)
output-fm_tx: Output to fm tx (priority: 200)
output-speaker+wired_headphone: Output to speaker+wired 
headphone (priority: 100)
output-parking: Parking port (priority: 50)
Active Port: output-speaker
Formats:
pcm

Sink #1
State: SUSPENDED
Name: sink.fake.sco
Description: Null Output
Driver: module-null-sink.c
Sample Specification: s16le 1ch 8000Hz
Channel Map: mono
Owner Module: 5
Mute: no
Volume: mono: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: sink.fake.sco.monitor
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Null Output"
device.class = "abstract"
device.icon_name = "audio-card"
Formats:
pcm

Then plugging in a headphone goes to:

$ pactl list sinks
Sink #0
State: SUSPENDED
Name: sink.primary
Description: Droid sink primary
Driver: module-droid-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 4
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: sink.primary.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Droid sink primary"
device.class = "sound"
device.form_factor = "internal"
droid.hw_module = "primary"
device.icon_name = "audio-card"
Ports:
output-earpiece: Output to earpiece (priority: 200)
output-speaker: Output to speaker (priority: 300)
output-wired_headset: Output to wired headset (priority: 400, 
not available)
output-wired_headphone: Output to wired headphone (priority: 
400, available)
output-bluetooth_sco: Output to bluetooth sco (priority: 100)
output-sco_headset: Output to sco headset (priority: 100)
output-sco_carkit: Output to sco carkit (priority: 100)
output-aux_digital: Output to aux digital (priority: 100)
output-analog_dock_headset: Output to analog dock headset 
(priority: 100)
output-digital_dock_headset: Output to digital dock headset 
(priority: 100)
output-fm_tx: Output to fm tx (priority: 200)
output-speaker+wired_headphone: Output to speaker+wired 
headphone (priority: 100)
output-parking: Parking port (priority: 50)
Active Port: output-wired_headphone
Formats:
pcm

Sink #1
State: SUSPENDED
Name: sink.fake.sco
Description: Null Output
Driver: module-null-sink.c
Sample Specification: s16le 1ch 8000Hz
Channel Map: mono
Owner Module: 5
Mute: no
Volume: mono: 65536 / 100% / 0.00 dB

[Dx-packages] [Bug 1436538] Re: brigtness slider should not allow total darkness

2015-04-07 Thread Ted Gould
Marking the indicator-power task as invalid as I believe the fix we're
doing is to change the device specific configuration for the bq device
and nothing general in indicator-power.

** Changed in: indicator-power (Ubuntu)
   Status: In Progress => Invalid

** Changed in: indicator-power (Ubuntu)
 Assignee: Ricardo Salveti (rsalveti) => (unassigned)

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-power in Ubuntu.
https://bugs.launchpad.net/bugs/1436538

Title:
  brigtness slider should not allow total darkness

Status in the base for Ubuntu mobile products:
  In Progress
Status in indicator-power package in Ubuntu:
  Invalid

Bug description:
  bq aquaris 4.5, Utopic Unicorn 20150312-002053:
  slider allows to minimize the brightess to the point of not seeing at all.
  Even if you manage to reboot (you don't see the confirmation dialogue) you 
still have completly dark display which effectively "bricks" the phone (no 
battery removal) unless you are patient enought to blindly try and hit long 
time enough to increase the brigtness again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436538/+subscriptions

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


[Dx-packages] [Bug 777140] Re: launcher doesn't hide on its own after gesture reveal

2015-04-07 Thread Stephen M. Webb
Still definitely happens in Ubuntu 15.04

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

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

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

Title:
  launcher doesn't hide on its own after gesture reveal

Status in Ayatana Design:
  Invalid
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  When i show the launcher with a 4 finger drag, it stays open until I
  manually dismiss it. It should go away on its own at some point.

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

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


[Dx-packages] [Bug 1440825] Re: dnd_is_screensaver_inhibited no longer works

2015-04-07 Thread Ubuntu Foundations Team Bug Bot
The attachment "notify-osd_dnd.patch" seems to be a patch.  If it isn't,
please remove the "patch" flag from the attachment, remove the "patch"
tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the
team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1440825

Title:
  dnd_is_screensaver_inhibited no longer works

Status in notify-osd package in Ubuntu:
  New

Bug description:
  Notifications are still shown even if the system inhibits
  screensaver(expecting dnd_is_screensaver_inhibited state).

  The code seems to expect "GetInhibitors" method is in
  "org.gnome.ScreenSaver", but the method is no longer there. The
  equivalent is "IsInhibited" method in org.gnome.SessionManager.

  
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
  ## unit32:8 = (Inhibit the session being marked as idle)
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
  method return sender=:1.24 -> dest=:1.284 reply_serial=2
 boolean true

  [src/dnd.c]
  100 static DBusGProxy*
  101 get_screensaver_proxy (void)
  102 {
  103 if (gsmgr == NULL)
  104 {
  105 DBusGConnection *connection = dbus_get_connection ();
  106 gsmgr = dbus_g_proxy_new_for_name (connection,
  107
"org.gnome.ScreenSaver",
  108
"/org/gnome/ScreenSaver",
  109
"org.gnome.ScreenSaver");
  110 }
  111 
  112 return gsmgr;
  113 }   
  114 
  115 gboolean
  116 dnd_is_screensaver_inhibited ()
  117 {
  118 GError  *error = NULL;
  119 gboolean inhibited = FALSE;
  120 char **list;
  121 
  122 if (! get_screensaver_proxy ())
  123 return FALSE;
  124 
  125 if (dbus_g_proxy_call_with_timeout (
  126 gsmgr, "GetInhibitors", 2000, &error,
  127 G_TYPE_INVALID,
  128 G_TYPE_STRV, &list,
  129 G_TYPE_INVALID))

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 01:49:02 2015
  DesktopSession: 'ubuntu'
  EcryptfsInUse: Yes
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2015-02-28 (37 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
  MachineType: FUJITSU FMVS54KR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu4
   libgl1-mesa-glx  10.5.2-0ubuntu1
   libdrm2  2.4.59-0ubuntu1
   xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
   xserver-xorg-video-ati   1:7.5.0-1ubuntu2
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.06
  dmi.board.name: FJNB24F
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
  dmi.product.name: FMVS54KR
  dmi.sys.vendor: FUJITSU
  glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+subscriptions

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


[Dx-packages] [Bug 1441126] Re: Por uma actualização parte parcial em que foi apagado o Ubuntu-desktop, e não mais ser possivel concertar o problema

2015-04-07 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1441126

Title:
  Por uma actualização parte parcial em que foi apagado o Ubuntu-
  desktop, e não mais ser possivel concertar o problema

Status in libunity package in Ubuntu:
  New

Bug description:
  Recebi esta actualização:
  Nem todas as actualizações podem ser instaladas
  Executar um upgrade parcial, para instalar o maior número de actualizações 
possíveis.

  Isto pode ser originado por:

  Um upgrade anterior não terminado
  Problemas com algum software instalado
  Pacotes de software não fornecidos pelo Ubuntu
  Mudanças normais de uma versão de pré lançamento do Ubuntu

  De seguida
  Can't install 'ubuntu-desktop'
  It was impossible to install a required package. Please report this is a bug 
using 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.

  Já dei várias ordens, não necessàriamente na ordem que as vou colocar

  sudo apt-get clean
  sudo apt-get install -f
  sudo dpkg --configure -a
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade
  sudo apt-get autoremove
  sudo rm /var/lib/apt/lists/* ; sudo rm /var/lib/apt/lists/partial/* ; sudo 
apt-get -f install ; sudo apt-get clean ; sudo apt-get update ; sudo apt-get 
dist-upgrade : sudo apt-get clean ; sudo apt-get autoclean ; sudo apt-get 
autoremove
  sudo apt-get install --reinstall ubntu-desktop

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  Uname: Linux 3.18.10-031810-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Tue Apr  7 10:40:56 2015
  DuplicateSignature: package:libunity9:7.1.4+14.04.20140210-0ubuntu1:a tentar 
sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de 
outras instâncias do pacote libunity9:i386
  ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
  InstallationDate: Installed on 2014-08-31 (218 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: libunity
  Title: package libunity9 7.1.4+14.04.20140210-0ubuntu1 failed to 
install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Dx-packages] [Bug 1441126] [NEW] Por uma actualização parte parcial em que foi apagado o Ubuntu-desktop, e não mais ser possivel concertar o problema

2015-04-07 Thread João Fernando Machado Mão de Ferro
Public bug reported:

Recebi esta actualização:
Nem todas as actualizações podem ser instaladas
Executar um upgrade parcial, para instalar o maior número de actualizações 
possíveis.

Isto pode ser originado por:

Um upgrade anterior não terminado
Problemas com algum software instalado
Pacotes de software não fornecidos pelo Ubuntu
Mudanças normais de uma versão de pré lançamento do Ubuntu

De seguida
Can't install 'ubuntu-desktop'
It was impossible to install a required package. Please report this is a bug 
using 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.

Já dei várias ordens, não necessàriamente na ordem que as vou colocar

sudo apt-get clean
sudo apt-get install -f
sudo dpkg --configure -a
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
sudo apt-get autoremove
sudo rm /var/lib/apt/lists/* ; sudo rm /var/lib/apt/lists/partial/* ; sudo 
apt-get -f install ; sudo apt-get clean ; sudo apt-get update ; sudo apt-get 
dist-upgrade : sudo apt-get clean ; sudo apt-get autoclean ; sudo apt-get 
autoremove
sudo apt-get install --reinstall ubntu-desktop

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
Uname: Linux 3.18.10-031810-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
Date: Tue Apr  7 10:40:56 2015
DuplicateSignature: package:libunity9:7.1.4+14.04.20140210-0ubuntu1:a tentar 
sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de 
outras instâncias do pacote libunity9:i386
ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' partilhado, 
que é diferente de outras instâncias do pacote libunity9:i386
InstallationDate: Installed on 2014-08-31 (218 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: libunity
Title: package libunity9 7.1.4+14.04.20140210-0ubuntu1 failed to 
install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1441126

Title:
  Por uma actualização parte parcial em que foi apagado o Ubuntu-
  desktop, e não mais ser possivel concertar o problema

Status in libunity package in Ubuntu:
  New

Bug description:
  Recebi esta actualização:
  Nem todas as actualizações podem ser instaladas
  Executar um upgrade parcial, para instalar o maior número de actualizações 
possíveis.

  Isto pode ser originado por:

  Um upgrade anterior não terminado
  Problemas com algum software instalado
  Pacotes de software não fornecidos pelo Ubuntu
  Mudanças normais de uma versão de pré lançamento do Ubuntu

  De seguida
  Can't install 'ubuntu-desktop'
  It was impossible to install a required package. Please report this is a bug 
using 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal.

  Já dei várias ordens, não necessàriamente na ordem que as vou colocar

  sudo apt-get clean
  sudo apt-get install -f
  sudo dpkg --configure -a
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get dist-upgrade
  sudo apt-get autoremove
  sudo rm /var/lib/apt/lists/* ; sudo rm /var/lib/apt/lists/partial/* ; sudo 
apt-get -f install ; sudo apt-get clean ; sudo apt-get update ; sudo apt-get 
dist-upgrade : sudo apt-get clean ; sudo apt-get autoclean ; sudo apt-get 
autoremove
  sudo apt-get install --reinstall ubntu-desktop

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
  Uname: Linux 3.18.10-031810-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  Date: Tue Apr  7 10:40:56 2015
  DuplicateSignature: package:libunity9:7.1.4+14.04.20140210-0ubuntu1:a tentar 
sobreescrever '/usr/bin/unity-scope-loader' partilhado, que é diferente de 
outras instâncias do pacote libunity9:i386
  ErrorMessage: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
  InstallationDate: Installed on 2014-08-31 (218 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: libunity
  Title: package libunity9 7.1.4+14.04.20140210-0ubuntu1 failed to 
install/upgrade: a tentar sobreescrever '/usr/bin/unity-scope-loader' 
partilhado, que é diferente de outras instâncias do pacote libunity9:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Dx-packages] [Bug 1440825] Re: dnd_is_screensaver_inhibited no longer works

2015-04-07 Thread Nobuto Murata
The attached patch would "fix" the issue. However the
dnd_is_screensaver_inhibited is broken at least for a few years now,
users of caffeine[1] or indicator-session-idle-inhibit[2] might feel the
"fix" is a regression, i.e. notification suddenly stops working by
notify-osd update.

[1] https://launchpad.net/caffeine
[2] https://github.com/oyvindstegard/indicator-session-idle-inhibit

** Patch added: "notify-osd_dnd.patch"
   
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+attachment/4368321/+files/notify-osd_dnd.patch

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1440825

Title:
  dnd_is_screensaver_inhibited no longer works

Status in notify-osd package in Ubuntu:
  New

Bug description:
  Notifications are still shown even if the system inhibits
  screensaver(expecting dnd_is_screensaver_inhibited state).

  The code seems to expect "GetInhibitors" method is in
  "org.gnome.ScreenSaver", but the method is no longer there. The
  equivalent is "IsInhibited" method in org.gnome.SessionManager.

  
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
  ## unit32:8 = (Inhibit the session being marked as idle)
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
  method return sender=:1.24 -> dest=:1.284 reply_serial=2
 boolean true

  [src/dnd.c]
  100 static DBusGProxy*
  101 get_screensaver_proxy (void)
  102 {
  103 if (gsmgr == NULL)
  104 {
  105 DBusGConnection *connection = dbus_get_connection ();
  106 gsmgr = dbus_g_proxy_new_for_name (connection,
  107
"org.gnome.ScreenSaver",
  108
"/org/gnome/ScreenSaver",
  109
"org.gnome.ScreenSaver");
  110 }
  111 
  112 return gsmgr;
  113 }   
  114 
  115 gboolean
  116 dnd_is_screensaver_inhibited ()
  117 {
  118 GError  *error = NULL;
  119 gboolean inhibited = FALSE;
  120 char **list;
  121 
  122 if (! get_screensaver_proxy ())
  123 return FALSE;
  124 
  125 if (dbus_g_proxy_call_with_timeout (
  126 gsmgr, "GetInhibitors", 2000, &error,
  127 G_TYPE_INVALID,
  128 G_TYPE_STRV, &list,
  129 G_TYPE_INVALID))

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 01:49:02 2015
  DesktopSession: 'ubuntu'
  EcryptfsInUse: Yes
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2015-02-28 (37 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
  MachineType: FUJITSU FMVS54KR
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu4
   libgl1-mesa-glx  10.5.2-0ubuntu1
   libdrm2  2.4.59-0ubuntu1
   xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
   xserver-xorg-video-ati   1:7.5.0-1ubuntu2
  SourcePackage: notify-osd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.06
  dmi.board.name: FJNB24F
  dmi.board.vendor: FUJITSU
  dmi.board.version: D2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
  dmi.product.name: FMVS54KR
  dmi.sys.vendor: FUJITSU
  glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+subscriptions

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


[Dx-packages] [Bug 1364568] Re: Feature: Option to have the alarm get louder as time goes on.

2015-04-07 Thread Alexander Dobetsberger
Good idea, would save me some near heart attacks in the morning since
it's going off way too loud at the moment.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-datetime in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1364568

Title:
  Feature: Option to have the alarm get louder as time goes on.

Status in Clock application for Ubuntu devices:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  I know a lot of alarms start off quiet, and gradually get louder as
  time goes on. Might be a nice feature. The only con of this is feature
  creep.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1364568/+subscriptions

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


[Dx-packages] [Bug 1420630] Re: indicator-sound menu icon disappeared after volume down to zero

2015-04-07 Thread TienFu Chen
@Ara:
I have verified it again under stock 14.04.2 with fully system upgraded on HP 
Pez 6, I can reproduce it.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-sound in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1420630

Title:
  indicator-sound menu icon disappeared after volume down to zero

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  Incomplete
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-sound source package in Trusty:
  New

Bug description:
  On the HP commercial notebooks, there're function keys to control volume.
  The menu volume icon will be disappeared if we volume down
  (with key combination: Fn+F6, you can also emulate the keys with "xdotool key 
XF86AudioLowerVolume") to zero then logout and back in.
  But if we just zero down volume(with the single volume on/off button), then 
logout and back in, the volume icon is still there.

  This issue is fixed with installing indicator-
  sound_12.10.2+14.10.20141010-0ubuntu1(Utopic)

  Package: indicator-sound_12.10.2+14.04.20140401-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-38.65stella1-generic 3.13.11.8
  Uname: Linux 3.13.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Wed Feb 11 14:18:50 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-datong140729-trusty-amd64-20150114-3
  InstallationDate: Installed on 2015-01-29 (13 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150114-08:50
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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