[Dx-packages] [Bug 1436120] Re: Faulty transparency in Gtk+ "About" dialog due to overlay scrollbar

2015-05-16 Thread Daniel Hahler 
I've noticed this also, but it appears to be more prominent for me (with
Gtk3 apps).

E.g., with gtk3-widget-factory there will be no background.

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1436120/+attachment/4398528/+files/gtk3-widget-factory_066.png

** Changed in: overlay-scrollbar (Ubuntu)
   Status: New => Triaged

** Changed in: overlay-scrollbar (Ubuntu)
   Importance: Undecided => Medium

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

Title:
   Faulty transparency in Gtk+ "About" dialog due to overlay scrollbar

Status in overlay-scrollbar package in Ubuntu:
  Triaged

Bug description:
  Open the Help->About dialog of a Gtk+ app, e.g. gnome-terminal, gedit,
  evince...

  Some text appears over the default gray background.  Click on the
  Credits or License button.  New text appears on white.  Now click on
  this button again to close the info that just appeared.

  Expected behivior:  The initial look of the About dialog should be
  restored.

  Actual behavior:  The foreground text is there, but the background
  becomes black (Utopic) or transparent (Vivid beta).

  If the dialog is closed and opened again, it'll be faulty right away
  for the rest of the app's lifetime.  You have to restart the
  application to make it show correctly again.

  Tested both with Gnome-shell and Unity; and both with Adwaita and
  Ambiance.  In case of gnome-terminal, both with and without the
  unofficial transparency patch.

  LIBOVERLAY_SCROLLBAR=0 makes the bug go away.

  In https://bugzilla.gnome.org/show_bug.cgi?id=746707 mainsteam Gtk+
  developer stated that he (presumably on Fedora) can't see the bug
  either, and his (apparently correct) guess was that it's caused by the
  overlay scrollbar.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: overlay-scrollbar-gtk3 0.2.16+r359+15.04.20150319-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 25 01:34:25 2015
  InstallationDate: Installed on 2012-05-30 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: overlay-scrollbar
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1436120/+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 1412709] [NEW] Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme'

2015-01-20 Thread Daniel Hahler 
Public bug reported:

I am seeing the following warning with notify-osd when changing the
volume:

   loading icon 'notification-notification-audio-volume-medium' caused
error: 'Icon 'notification-notification-audio-volume-medium' not present
in theme'

This happens also when running it manually (as in src/send-test-
notification.sh):

notify-send "Volume" -i notification-audio-volume-medium -h
int:value:75 -h string:x-canonical-private-synchronous:

When leaving out the "notification-" prefix there's no error:

notify-send "Volume" -i audio-volume-medium -h int:value:75 -h
string:x-canonical-private-synchronous:

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: notify-osd 0.9.35+14.10.20140819-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jan 20 10:41:03 2015
DesktopSession: 'ubuntu'
GtkTheme: 'Numix'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2012-05-28 (966 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: LENOVO 42992PG
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu8
 libgl1-mesa-glx  10.1.3-0ubuntu0.2
 libdrm2  2.4.56-1~ubuntu1
 xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
 xserver-xorg-video-ati   1:7.3.0-1ubuntu3.1
SourcePackage: notify-osd
UpgradeStatus: Upgraded to trusty on 2015-01-17 (2 days ago)
dmi.bios.date: 07/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET69WW (1.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42992PG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42992PG
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO

** Affects: notify-osd (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 notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1412709

Title:
  Error: loading icon 'notification-notification-audio-volume-medium'
  caused error: 'Icon 'notification-notification-audio-volume-medium'
  not present in theme'

Status in notify-osd package in Ubuntu:
  New

Bug description:
  I am seeing the following warning with notify-osd when changing the
  volume:

 loading icon 'notification-notification-audio-volume-medium' caused
  error: 'Icon 'notification-notification-audio-volume-medium' not
  present in theme'

  This happens also when running it manually (as in src/send-test-
  notification.sh):

  notify-send "Volume" -i notification-audio-volume-medium -h
  int:value:75 -h string:x-canonical-private-synchronous:

  When leaving out the "notification-" prefix there's no error:

  notify-send "Volume" -i audio-volume-medium -h int:value:75 -h
  string:x-canonical-private-synchronous:

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: notify-osd 0.9.35+14.10.20140819-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 20 10:41:03 2015
  DesktopSession: 'ubuntu'
  GtkTheme: 'Numix'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2012-05-28 (966 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: LENOVO 42992PG
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic 
root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu8
   libgl1-mesa-glx  10.1.3-0ubuntu0.2
   libdrm2  2.4.56-1~ubuntu1
   xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
   xserver-xorg-video-ati   1:7.3.0-1ubuntu3.1
  SourcePackage: notify-osd
  UpgradeStatus: Upgraded to trusty on 2015-01-17 (2 days ago)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42992PG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.na

[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2014-05-07 Thread Daniel Hahler 
After upgrading to 14.04 I am more affected by this bug than before: 
network-manager does not wake up properly after hibernation.
With 13.10 this might only happen when I was using overriding the METHOD to 
METHOD=suspend_hybrid for METHOD=suspend.


The workaround: `sudo nmcli nm sleep false`.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in “systemd-shim” package in Ubuntu:
  Confirmed
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2014-01-27 Thread Daniel Hahler 
@pitti
Just an update from my side:
Not using hybrid suspend (via overriding "METHOD=suspend_hybrid") fixed it for 
me.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in “systemd-shim” package in Ubuntu:
  Incomplete
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Incomplete

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2013-12-21 Thread Daniel Hahler 
Since using non-hybrid suspend (via METHOD override, pasted above) it
has not happened for me again (with two night cycles in between, where
this bug would usually get triggered).

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in “systemd-shim” package in Ubuntu:
  Incomplete
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Incomplete

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2013-12-19 Thread Daniel Hahler 
With the normal suspend methd, PrepareForSleep=false showed up now (and
the network came up again), (together with PrepareForSleep=true):

signal sender=:1.3 -> dest=(null destination) serial=1094 
path=/org/freedesktop/login1; 
interface=org.freedesktop.login1.Manager; member=PrepareForSleep
   boolean false

However, it usually requires a suspend cycle over night to trigger this bug 
anyway - so I will report back tomorrow.
(I was rather surprised that it was triggered in my last attempt)

Where is the PrepareForSleep=false signal emitted and what is it supposed to do?
Is it something NetworkManager requires to wake up again?

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in “systemd-shim” package in Ubuntu:
  Incomplete
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Incomplete

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2013-12-19 Thread Daniel Hahler 
@pitti
Ok, I have setup the dbus monitor (any filter suggestions?), tee'ing to a 
logfile.

I have then suspended and resumed (after a minute maybe), and there's no
PrepareForSleep=false in the log, only:

signal sender=:1.3 -> dest=(null destination) serial=1076 
path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; 
member=PrepareForSleep
   boolean true

The network also did not came up after resuming.

Is it safe/wise to post the dbus-monitor log unfiltered puclicitly, or
can I send it directly to you?

I will now disable hybrid suspend and report back.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in “systemd-shim” package in Ubuntu:
  Incomplete
Status in “systemd-shim” source package in Saucy:
  Confirmed
Status in “systemd-shim” source package in Trusty:
  Incomplete

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 367947] Re: Notifications appear in non-visible area of multi-head desktop

2013-12-17 Thread Daniel Hahler 
Thanks, Samuel!

For reference, the default is 'dont-follow-focus'.

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

Title:
  Notifications appear in non-visible area of multi-head desktop

Status in Notify OSD:
  New
Status in “notify-osd” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: notify-osd

  I use xrandr to configure a multi-head display -- a main LCD screen and a 
TV-out. 
  In order to keep within my video card's 2048x2048 virtual display size for 3D 
acceleration, I stack my screens vertically in the virtual display, with the 
smaller screen on top. 

  Also, I have a single gnome panel at the bottom of my LCD screen.

  Without the top gnome panel (if I understand correctly), notify-osd
  defaults to placing the notifications at the top right of the display.
  However, for me, this is either a non-visible area, or a TV screen
  that is across the room from me (and most likely not even turned on).

  Re-arranging the screens side-by-side 'fixes' things, but at the cost
  of 3d acceleration (the virtual display is now greater than my card's
  2048x2048 limit).

  If there is no top panel, any arrangement of screens with differing
  resolutions that leaves a 'dead area' at the top right will trigger
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/notify-osd/+bug/367947/+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 1256780] [NEW] Need to restart unity to activate changes to Custom Shortcuts (Settings => Keyboard)

2013-12-01 Thread Daniel Hahler 
Public bug reported:

After changing the Custom Shortcuts (e.g. adding a new entry), I need to
restart unity to make it effective ("unity --replace &!").

This also affects changes to existing config entries: if I change them,
the previous and new combination both are not recognized (until I
restart unity).

TEST CASE:
1. Open Keyboard / Custom Shortcuts
2. Add a new entry or change an existing one
3. Press the new shortcut

ACTUAL RESULT:
Any changed hotkeys (added or edited) are ignored, until you restart unity.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
Date: Mon Dec  2 06:56:10 2013
InstallationDate: Installed on 2012-05-28 (552 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: Upgraded to saucy on 2013-10-08 (54 days ago)

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


** Tags: amd64 apport-bug saucy

** Description changed:

  After changing the Custom Shortcuts (e.g. adding a new entry), I need to
  restart unity to make it effective ("unity --replace &!").
  
  This also affects changes to existing config entries: if I change them,
  the previous and new combination both are not recognized (until I
  restart unity).
+ 
+ TEST CASE:
+ 1. Open Keyboard / Custom Shortcuts
+ 2. Add a new entry or change an existing one
+ 3. Press the new shortcut
+ 
+ ACTUAL RESULT:
+ Any changed hotkeys (added or edited) are ignored, until you restart unity.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  Date: Mon Dec  2 06:56:10 2013
  InstallationDate: Installed on 2012-05-28 (552 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (54 days ago)

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

Title:
  Need to restart unity to activate changes to Custom Shortcuts
  (Settings => Keyboard)

Status in “unity” package in Ubuntu:
  New

Bug description:
  After changing the Custom Shortcuts (e.g. adding a new entry), I need
  to restart unity to make it effective ("unity --replace &!").

  This also affects changes to existing config entries: if I change
  them, the previous and new combination both are not recognized (until
  I restart unity).

  TEST CASE:
  1. Open Keyboard / Custom Shortcuts
  2. Add a new entry or change an existing one
  3. Press the new shortcut

  ACTUAL RESULT:
  Any changed hotkeys (added or edited) are ignored, until you restart unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  Date: Mon Dec  2 06:56:10 2013
  InstallationDate: Installed on 2012-05-28 (552 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (54 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1256780/+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 865389] Re: Appmenu-gtk should not blacklist eclipse

2013-11-15 Thread Daniel Hahler 
FWIW, @splaktar: you have to unset (or assign 0 to) UBUNTU_MENUPROXY.
This should work (from a shell): UBUNTU_MENUPROXY=0 eclipse
See also https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019.

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

Title:
  Appmenu-gtk should not blacklist eclipse

Status in Application menu module for GTK+:
  Confirmed
Status in “appmenu-gtk” package in Ubuntu:
  Confirmed

Bug description:
  The current version of eclipse and swt library in oneiric work perfectly with 
appmenu.
  Thus eclipse should be removed from appmenu's blacklist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-gtk/+bug/865389/+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 971147] Re: xdotool and wmctrl don't move and resize windows after they are (semi)maximized

2013-11-01 Thread Daniel Hahler 
I have just tried to reproduce this on Ubuntu 13.10, but could not do so.
I noticed however, that the window gets moved sometimes from the right to the 
left screen, but sometimes only to the upper left of the right screen.

Besides, for moving a window to the next/previous output, you can use
Unity's "Put" plugin. I have mapped Ctrl-Alt-n to move a window from one
output to the next.

** Changed in: unity (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: unity (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  xdotool and wmctrl don't move and resize windows after they are
  (semi)maximized

Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  The command

  /usr/bin/xdotool windowmove `/usr/bin/xdotool getwindowfocus` 0 0

  is supposed to move currenly selected window to the top left corner.
  It works fine on clean start, but after I maximize (or half-maximize)
  and then restore some window, it becomes "broken", and this command
  silently do nothing with it. The same holds for appropriate wmctrl
  command like

  wmctrl -i -r `/usr/bin/xdotool getwindowfocus` -e 10,0,0,-1,-1

  This affects Unity desktop, but does NOT affect Gnome shell desktop,
  so I believe it's a bug somewhere in Unity.

  The same issue is discussed in the following thread:

  http://ubuntuforums.org/showthread.php?t=1414155&page=2

  It seems to affect both 11.10 and 12.04 (but I checked only 12.04).

  user@xennie:~$ lsb_release -rd
  Description:  Ubuntu precise (development branch)
  Release:  12.04

  user@xennie:~$ apt-cache policy unity
  unity:
Installed: 5.8.0-0ubuntu2
Candidate: 5.8.0-0ubuntu2
Version table:
   *** 5.8.0-0ubuntu2 0
  500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  user@xennie:~$ apt-cache policy xdotool
  xdotool:
Installed: 1:2.20110530.1-3ubuntu1
Candidate: 1:2.20110530.1-3ubuntu1
Version table:
   *** 1:2.20110530.1-3ubuntu1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ precise/universe amd64 
Packages
  100 /var/lib/dpkg/status

  user@xennie:~$ apt-cache policy compiz
  compiz:
Installed: 1:0.9.7.2-0ubuntu4
Candidate: 1:0.9.7.2-0ubuntu4
Version table:
   *** 1:0.9.7.2-0ubuntu4 0
  500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  user@xennie:~$ apt-cache policy xorg
  xorg:
Installed: 1:7.6+12ubuntu1
Candidate: 1:7.6+12ubuntu1
Version table:
   *** 1:7.6+12ubuntu1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Apr  2 02:50:17 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/971147/+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 1238929] Re: Unity dash searches forever, no search results

2013-10-22 Thread Daniel Hahler 
** Changed in: unity (Ubuntu)
   Importance: Undecided => Medium

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

** Description changed:

  Since upgrading from 13.04 to 13.10 (beta) I can no longer launch
  applications by searching them in the dash (topmost entry in the
  launcher bar). Whatever I enter as a search term, the spinning circle
  rotates, rotates, without ever showing any results. No message about
  "nothing found", either. Launching applications from the command line or
  from the launcher bar works just fine.
  
  To make sure we talk about the same I made a screenshot, please find it
  attached.
  
  I tried to remove everything in $HOME/.cache, no change.
  
  Then I ran unity in a terminal:
  
  $ unity
  compiz (core) - Info: Loading plugin: core
  compiz (core) - Info: Starting plugin: core
  [same for ccp]
  compizconfig - Info: Backend : gsettings
  compizconfig - Info: Integration : true
  compizconfig - Info: Profile : unity
  compiz (core) - Info: Loading plugin: opengl
  compiz (core) - Info: Starting plugin: opengl
  [same for composite, compiztoolbox, decor, imgpng, unitymtgrabhandles, 
vpswitch, move, copytex, mousepoll, place,
-   gnomecompat, grid, snap, resize, regex, session, wall, animation, fade, 
expo, scale, workarounds, ezoom, unityshell]
+   gnomecompat, grid, snap, resize, regex, session, wall, animation, fade, 
expo, scale, workarounds, ezoom, unityshell]
  compizconfig - Info: Backend : gsettings
  compizconfig - Info: Integration : true
  compizconfig - Info: Profile : unity
  WARN  2013-10-11 20:45:03 unity.glib.dbus.server GLibDBusServer.cpp:586 Can't 
register object 'com.canonical.Autopilot.Introspection' yet as we don't have a 
connection, waiting for it...
  WARN  2013-10-11 20:45:03 unity.glib.dbus.server GLibDBusServer.cpp:586 Can't 
register object 'com.canonical.Unity.Debug.Logging' yet as we don't have a 
connection, waiting for it...
  ERROR 2013-10-11 20:45:03 unity.glib-gio :0 
g_file_monitor_set_rate_limit: assertion 'G_IS_FILE_MONITOR (monitor)' failed
  ERROR 2013-10-11 20:45:03 unity.launcher.icon.trash TrashLauncherIcon.cpp:64 
Could not create file monitor for trash uri: Vorgang wird nicht unterstützt
  WARN  2013-10-11 20:45:03 unity.glib.dbus.server GLibDBusServer.cpp:586 Can't 
register object 'com.canonical.Unity.Launcher' yet as we don't have a 
connection, waiting for it...
  WARN  2013-10-11 20:45:03 unity.glib.dbus.server GLibDBusServer.cpp:586 Can't 
register object 'com.canonical.Unity.Dash' yet as we don't have a connection, 
waiting for it...
  WARN  2013-10-11 20:45:03 nux.inputmethod.ibus InputMethodIBus.cpp:63 
Impossible to connect to connect to ibus
  WARN  2013-10-11 20:45:03 unity.glib.dbus.server GLibDBusServer.cpp:586 Can't 
register object 'org.gnome.SessionManager.EndSessionDialog' yet as we don't 
have a connection, waiting for it...
  compiz (decor) - Warn: No default decoration found, placement will not be 
correct
  [repeated 10 times]
  WARN  2013-10-11 20:45:04 unity.glib.dbus.proxy GLibDBusProxy.cpp:418 Calling 
method "CanShutdown" on object path: "/org/gnome/SessionManager" failed: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  ERROR 2013-10-11 20:45:04 unity.session.gnome GnomeSessionManager.cpp:297 
Gnome Session call failed: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files
  WARN  2013-10-11 20:45:05 nux.inputmethod.ibus InputMethodIBus.cpp:63 
Impossible to connect to connect to ibus
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: home.scope 
: Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
applications.scope : Es wurde keine gültige Schlüsselwertedatei in den 
Suchordnern gefunden
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: files.scope 
: Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: video.scope 
: Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: music.scope 
: Es wurde keine gültige Schlüsselwertedatei in den Suchordnern gefunden
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
photos.scope : Es wurde keine gültige Schlüsselwertedatei in den Suchordnern 
gefunden
  WARN  2013-10-11 20:45:05 unity.dash.gsettingsscop

[Dx-packages] [Bug 1237072] Re: Dash Home displays no results (spins forever): "Valid key file could not be found in search dirs"

2013-10-16 Thread Daniel Hahler 
** Changed in: unity (Ubuntu)
   Status: New => Triaged

** Changed in: unity (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- Dash Home displays no results (spins forever): "Valid key file could not be 
found in search dirs"
+ Dash Home displays no results (spins forever): "Valid key file could not be 
found in search dirs": no scopes installed

** Description changed:

  I've upgraded to Ubuntu 13.10 (development) from 13.04.
  
  When tapping the Super key, the Dash appears, but is empty.
  When typing anything, the loading indicator spins forever.
  
  unity displays the following on STDERR:
  
  WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
  WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: home.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
applications.scope : Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: files.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: video.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: music.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
photos.scope : Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
social.scope : Valid key file could not be found in search dirs
  
+ I had to manually install some scopes, which apparently were not
+ installed by default during the upgrade: unity-scopes-master-default
+ unity-scopes-runner unity-scope-home unity-scope-devhelp unity-scope-
+ gdrive unity-scope-github unity-scope-launchpad unity-scope-manpages
+ unity-scope-sshsearch
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  Date: Tue Oct  8 22:40:13 2013
  InstallationDate: Installed on 2012-05-28 (498 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)

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

Title:
  Dash Home displays no results (spins forever): "Valid key file could
  not be found in search dirs": no scopes installed

Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  I've upgraded to Ubuntu 13.10 (development) from 13.04.

  When tapping the Super key, the Dash appears, but is empty.
  When typing anything, the loading indicator spins forever.

  unity displays the following on STDERR:

  WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
  WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: home.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
applications.scope : Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: files.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.

[Dx-packages] [Bug 1203888] Re: appindicator doesn't work in Saucy

2013-10-09 Thread Daniel Hahler 
JFI: for Glipper, GlipIt is a good alternative.

** Changed in: libappindicator (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: glipper (Ubuntu)
   Status: Confirmed => Triaged

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

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

** Summary changed:

- appindicator doesn't work in Saucy
+ appindicator ignores menu entries after having sent the menu to the indicator

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

Title:
  appindicator ignores menu entries after having sent the menu to the
  indicator

Status in Glipper:
  New
Status in “blueman” package in Ubuntu:
  Confirmed
Status in “glipper” package in Ubuntu:
  Triaged
Status in “libappindicator” package in Ubuntu:
  Triaged

Bug description:
  On Saucy, the glipper appindicator shows but none of its menu items
  show up when left or right-clicking on it.

  $ glipper
  SHARED_DATA_DIR: /usr/share/glipper
  Binding shortcut c to popup glipper
  Changed process name to: glipper
  /usr/lib/python2.7/dist-packages/glipper/AppIndicator.py:43: Warning: 
/build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:2475: signal 'child-added' is 
invalid for instance '0x20c90f0' of type 'GtkMenu'
self._app_indicator.set_menu(self.menu)

  (glipper:20249): LIBDBUSMENU-GLIB-WARNING **: About to Show called on
  an item wihtout submenus.  We're ignoring it.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: glipper 2.4-3
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Jul 22 18:17:16 2013
  InstallationDate: Installed on 2013-06-14 (38 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130613)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: glipper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glipper/+bug/1203888/+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 762032] Re: alt+tab broken with click-to-focus off

2013-10-08 Thread Daniel Hahler 
** Changed in: compiz (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  alt+tab broken with click-to-focus off

Status in Unity:
  Invalid
Status in “compiz” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: unity

  If compiz is configured with “Click to Focus” off, then alt+Tab is broken:
  * Open a full-screen/maximized application, such as a browser
  * Open a normally-windowed application such as a terminal or pidgin’s buddy 
list
  * Move the focus to the browser (alt+tab)
  * Keeping the mouse cursor where the windowed application will *not* be, 
press alt+tab.

  Focus will remain with the full-screen app, while it should move to the 
window switched to by alt+tab.
  If in the final step you put the mouse cursor where the windowed application 
will be after alt+tab, focus changes to the windowed application as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/762032/+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 1237072] [NEW] Dash Home displays no results (spins forever): "Valid key file could not be found in search dirs"

2013-10-08 Thread Daniel Hahler 
Public bug reported:

I've upgraded to Ubuntu 13.10 (development) from 13.04.

When tapping the Super key, the Dash appears, but is empty.
When typing anything, the loading indicator spins forever.

unity displays the following on STDERR:

WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: home.scope 
: Valid key file could not be found in search dirs
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
applications.scope : Valid key file could not be found in search dirs
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: files.scope 
: Valid key file could not be found in search dirs
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: video.scope 
: Valid key file could not be found in search dirs
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: music.scope 
: Valid key file could not be found in search dirs
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
photos.scope : Valid key file could not be found in search dirs
WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
social.scope : Valid key file could not be found in search dirs

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.1+13.10.20131004-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
Date: Tue Oct  8 22:40:13 2013
InstallationDate: Installed on 2012-05-28 (498 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)

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


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

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

Title:
  Dash Home displays no results (spins forever): "Valid key file could
  not be found in search dirs"

Status in “unity” package in Ubuntu:
  New

Bug description:
  I've upgraded to Ubuntu 13.10 (development) from 13.04.

  When tapping the Super key, the Dash appears, but is empty.
  When typing anything, the loading indicator spins forever.

  unity displays the following on STDERR:

  WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
  WARN  2013-10-08 22:47:26 unity.glib-gio :0 g_settings_set_value: 
value for key 'visual-bell-type' in schema 'org.gnome.desktop.wm.preferences' 
is outside of valid range
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: home.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
applications.scope : Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: files.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: video.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: music.scope 
: Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetching protocol metadata for scope: 
photos.scope : Valid key file could not be found in search dirs
  WARN  2013-10-08 22:47:53 unity.dash.gsettingsscopereader 
GSettingsScopes.cpp:108 Error fetch

[Dx-packages] [Bug 1237057] [NEW] Huge icons with Apllication Switcher (Alt-Tab) ("Icon", but not "Only show icon")

2013-10-08 Thread Daniel Hahler 
Public bug reported:

With the option "Icon" set in the Application Switcher General options
(but not "Only show icon"), the overlay icons are far too huge.

Without the "Icon" option, or "Only show icon" it looks OK.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: unity 7.1.1+13.10.20131004-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-11-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue Oct  8 22:00:17 2013
DistUpgraded: 2013-10-08 21:37:21,390 DEBUG enabling apt cron job
DistroCodename: saucy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21db]
InstallationDate: Installed on 2012-05-28 (497 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
MachineType: LENOVO 42992PG
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-11-generic 
root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to saucy on 2013-10-08 (0 days ago)
dmi.bios.date: 04/11/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET68WW (1.38 )
dmi.board.asset.tag: Not Available
dmi.board.name: 42992PG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 42992PG
dmi.product.version: ThinkPad X220 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.10+13.10.20131004-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.46-1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.903-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
xserver.bootTime: Tue Oct  8 21:42:15 2013
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728 
 vendor LGD
xserver.version: 2:1.14.3-3ubuntu1

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


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

** Attachment added: "Workspace 1_007.png"
   
https://bugs.launchpad.net/bugs/1237057/+attachment/3867665/+files/Workspace%201_007.png

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

Title:
  Huge icons with Apllication Switcher (Alt-Tab) ("Icon", but not "Only
  show icon")

Status in “unity” package in Ubuntu:
  New

Bug description:
  With the option "Icon" set in the Application Switcher General options
  (but not "Only show icon"), the overlay icons are far too huge.

  Without the "Icon" option, or "Only show icon" it looks OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20131004-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct  8 22:00:17 2013
  DistUpgraded: 2013-10-08 21:37:21,390 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21db]
  InstallationDate: Installed on 2012-05-28 (497 days ago)
  InstallationMedia: Ubu