[Dx-packages] [Bug 1226962]

[Yuval Adam]

This bug exists in a fully-updated Arch system:

$ uname -a
Linux X 3.17.3-1-ARCH #1 SMP PREEMPT Fri Nov 14 23:13:48 CET 2014 x86_64 
GNU/Linux

$ libreoffice --version
LibreOffice 4.3.4.1 430m0(Build:1)

Please fix this annoying bug, it prevents non-English locale users from
getting any meaningful work done.

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04,
  14.04.1, 14.10

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

-- 
Mailing list: https://launchpad.net/~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 1385441] Re: Can't unlock the screen in Ubuntu 14.10

[Matthieu Patou]

@andrea: what do you mean with gnome-screensaver ? I'm using unity as
far as I know I can't change the screensaver.

Also I found out that if I go to a terminal (ALT+F1) and kill -9 compiz then 
when I go back to the X11/Unity I can log correctly.
Seems related to compiz getting out of control (as plain kill didn't work).

@Gerardo: just use the terminal to kill compiz, then go back to the GUI
and you should be able to log.

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

Title:
  Can't unlock the screen in Ubuntu 14.10

Status in Unity:
  Incomplete
Status in “unity” package in Ubuntu:
  Incomplete

Bug description:
  The bug is similar to the one reported in 
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314095 (Unity 
Lockscreen in 14.04 can't unlock when using LDAP account)

  The difference is that I don't have an LDAP account just a local one, the box 
was working well in 14.04 and after upgrade to 14.10 I can't unlock the screen.
  Changing /sbin/unix_chkpwd to setuid does the trick too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1385441/+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 1396603] Re: Application menu title can't be set

[Phil Wolff]

Not a bug. When there is a valid .desktop file accompanying the
application, it works just fine.

** Changed in: unity (Ubuntu)
   Status: New => Invalid

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

Title:
  Application menu title can't be set

Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.10 64-bit
  Unity 7.3.1+14.10.20141016-0ubuntu1

  My application subclasses Gtk::Application, and my constructor calls
  Glib::set_application_name ( "Test App Menu" ). I expected the app
  menu to be titled "Test App Menu", which is what happens when using
  the Gnome desktop. Instead, Unity titles it "Unknown Application
  Name."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1396603/+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 1396700] Re: Needs to be updated to bluez5

[Robert Ancell]

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Triaged

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

Title:
  Needs to be updated to bluez5

Status in “indicator-bluetooth” package in Ubuntu:
  Triaged

Bug description:
  See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
  details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1396700] Re: Needs to be updated to bluez5

[Robert Ancell]

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Needs to be updated to bluez5

Status in “indicator-bluetooth” package in Ubuntu:
  New

Bug description:
  See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
  details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1368814] Re: Volume slider still available when Silent Mode is on

[Olli Ries]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => r1

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Volume slider still available when Silent Mode is on

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Won't Fix
Status in “ubuntu-system-settings” package in Ubuntu:
  Won't Fix

Bug description:
  During usability testing in August, one participant was confused that
  a volume slider was still available after turning on Silent Mode.

  : "Whenever “Silent
  Mode” is on, the volume slider should be insensitive."

  : "As with System Settings,
  whenever Silent Mode is on the volume slider should be insensitive."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368814/+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 1361702] Re: clock-app alarms need to be handled differently from other VTODO events

[Olli Ries]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => r1

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  clock-app alarms need to be handled differently from other VTODO
  events

Status in the base for Ubuntu mobile products:
  Confirmed
Status in The Date and Time Indicator:
  In Progress
Status in Calendar application for Ubuntu devices:
  Invalid
Status in Ubuntu UI Toolkit:
  Fix Released
Status in “indicator-datetime” package in Ubuntu:
  In Progress

Bug description:
  When you disable an alarm in the new clock app (with white
  background), it causes the alarm to show up as a calendar event. The
  expected behaviour is to not show up at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361702/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

I you view the video of this bug (on YouTube), under it is a message board 
where Brendan Hide said this:
 
"I've had this exact same bug running ArchLinux. Seems to have been fixed in 
the latest version however. My pacman log shows I updated Remmina on Thursday 
October 17th from v1.0.0 to v1.1.1."

Video: http://youtu.be/wKGLff7HhS8

Since Ubuntu 14.04 is an LTS, the Remmina package should be upgraded in
the Ubuntu repositories to version 1.1.1 (or later perhaps).

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in “remmina” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1378048] Re: Make music controls work in the sound indicator

[Olli Ries]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => r1

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  Make music controls work in the sound indicator

Status in the base for Ubuntu mobile products:
  Confirmed
Status in “indicator-sound” package in Ubuntu:
  Incomplete
Status in “media-hub” package in Ubuntu:
  Confirmed

Bug description:
  Steps:
  1. Play an album in the music player
  2. Pull down sound indicator
  3. Click forward button

  Observed: the music does not advance
  Expected: the music advances

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1378048/+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 1387231] Re: [regression][clock] alarm still rings once it's been disabled or deleted

[Olli Ries]

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
Milestone: None => r1

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Canonical Devices Products 
(canonical-devices-products-team)

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

Title:
  [regression][clock] alarm still rings once it's been disabled or
  deleted

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Clock application for Ubuntu devices:
  Confirmed
Status in “indicator-datetime” package in Ubuntu:
  In Progress

Bug description:
  (r135)

  Steps to reproduce:

  1. Create a single type alarm to ring in the next 5 minutes.
  2. Wait for the alarm to ring.
  3. After dismissing the alarm, delete it from the clock app.

  Actual behaviour:

  Once the alarm's been deleted, it still rings!

  Expected behaviour:

  Once you delete the alarm, this shouldn't ring anymore.

  

  Mako, Image #5 ubuntu rtm,

  Steps to reproduce:

  1. Create an alarm to ring in the next 5 minutes.
  2. Disable the alarm after it is created.

  Actual Behaviour:

  Alarm still rings!

  Expected Behaviour:

  Once you disable an alarm, it shouldn't ring anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387231/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

Is this bug fixed in later versions? Perhaps the 14.04 package needs
upgrading?

In Ubuntu 14.04, I'm running this version:

remmina:amd64/trusty 1.0.0-4ubuntu3 uptodate

You can see what version you are running by running the following in one
command line:

sudo apt-get install apt-show-versions ; sudo apt-show-versions remmina

This remains an issue for me.

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in “remmina” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace

[Lonnie Lee Best]

** Tags added: upgrade-software-version

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

Title:
  Remmina Launching Remote Sessions Larger than Workspace

Status in Unity:
  New
Status in “remmina” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Please view this video of the bug I'm reporting:
  http://youtu.be/wKGLff7HhS8

  Essentially, when using the Unity desktop in a Multiple Monitor setup
  (using workspaces), Remmina is launching remote sessions into a window
  larger than the workspace to which I'm launching it.

  Another thing to note about my set up, is that I do use Ubuntu's
  scaling feature to make things about 10% larger than the default size
  (to accommodate my otherwise straining eyes). Some times I use large
  text too. These facts may be totally unrelated to the bug, but I
  thought I would at least mention them.

  I'm using a fully update Ubuntu 14.04 Desktop 64bit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1370014/+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 1396699] [NEW] Needs to be updated to bluez5

[Sebastien Bacher]

Public bug reported:

See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
details

** Affects: indicator-bluetooth (Ubuntu)
 Importance: Low
 Status: Invalid

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Invalid

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Needs to be updated to bluez5

Status in “indicator-bluetooth” package in Ubuntu:
  Invalid

Bug description:
  See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
  details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396699/+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 1396700] Re: Needs to be updated to bluez5

[Sebastien Bacher]

Bluez interfaces changed between 4 and 5, the code probably needs
changes. Robert, since you wrote that indicator and know the codebase
best, do you think you could have a look to that?

Bluez5 test packages can be found in https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/bluez5 (should be https://launchpad.net/~ubuntu-
desktop/+archive/ubuntu/transitions so that might change)

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

Title:
  Needs to be updated to bluez5

Status in “indicator-bluetooth” package in Ubuntu:
  New

Bug description:
  See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
  details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1396700] [NEW] Needs to be updated to bluez5

[Sebastien Bacher]

Public bug reported:

See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
details

** Affects: indicator-bluetooth (Ubuntu)
 Importance: High
 Status: New

** Changed in: indicator-bluetooth (Ubuntu)
   Importance: Undecided => High

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

Title:
  Needs to be updated to bluez5

Status in “indicator-bluetooth” package in Ubuntu:
  New

Bug description:
  See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for
  details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1396700/+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 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars

[Launchpad Bug Tracker]

This bug was fixed in the package overlay-scrollbar -
0.2.16+r359+15.04.20141126-0ubuntu1

---
overlay-scrollbar (0.2.16+r359+15.04.20141126-0ubuntu1) vivid; urgency=low

  [ Tim Lunn ]
  * Check for null grab_notify handler before hijacking it. This fixes a
crash in GTK+3.14 where grab_notify is no longer used, Thanks Marius
Gedminas for the fix! (LP: #1386255)
 -- Ubuntu daily releaseWed, 26 Nov 2014 
15:18:56 +

** Changed in: overlay-scrollbar (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  devhelp and many other apps crash with SIGSEGV in g_closure_invoke()
  due to overlay-scrollbars

Status in Overlay Scrollbar:
  New
Status in Ubuntu GNOME:
  New
Status in “overlay-scrollbar” package in Ubuntu:
  Fix Released

Bug description:
  With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications
  segfault when I do stuff like

  - Press the  key
  - Press the Save button in gedit's headerbar
  - Press the hamburger menu button in devhelp's headerbar (the stack trace 
attached to this bug)
  - Press the Add button in gtimelog
  - Try to open any of the regular menus in gtimelog

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 27 17:15:30 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/devhelp
  InstallationDate: Installed on 2012-07-25 (824 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: devhelp
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: devhelp
  StacktraceTop:
   ?? ()
   g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, 
param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, 
instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483
   g_signal_emit_valist (instance=, signal_id=, 
detail=, var_args=var_args@entry=0x7fffd6ed0ab0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309
   g_signal_emit (instance=instance@entry=0x182a510, signal_id=, 
detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365
  Title: devhelp crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare 
shared sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1386255/+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 1396693] Re: host system loses keyboard

[Launchpad Bug Tracker]

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

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

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

Title:
  host system loses keyboard

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I use virtual machine or remote desktop and those operating systems 
crash or froze the host system sometimes "loses" the keyboard. I must kill the 
VM or RD to have keyboard again.
  I experienced this issue with Ubuntu 12.04 and 14.04 and mainly Windows as VM 
or RD.

  Kernel version:
  At least the series of 3.13 (64 bit) on both Ubuntu.

  Unity versions:
  Ubuntu 12.04.5 LTS: 5.20.0-0ubuntu3
  Ubuntu 14.04.1 LTS: 7.2.3-0ubuntu1

  Compiz versions:
  Ubuntu 12.04.5 LTS: 0.9.7.12-0ubuntu4
  Ubuntu 14.04.1 LTS: 0.9.11.2-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1396693/+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 1396693] [NEW] host system loses keyboard

[Svivi]

Public bug reported:

When I use virtual machine or remote desktop and those operating systems crash 
or froze the host system sometimes "loses" the keyboard. I must kill the VM or 
RD to have keyboard again.
I experienced this issue with Ubuntu 12.04 and 14.04 and mainly Windows as VM 
or RD.

Kernel version:
At least the series of 3.13 (64 bit) on both Ubuntu.

Unity versions:
Ubuntu 12.04.5 LTS: 5.20.0-0ubuntu3
Ubuntu 14.04.1 LTS: 7.2.3-0ubuntu1

Compiz versions:
Ubuntu 12.04.5 LTS: 0.9.7.12-0ubuntu4
Ubuntu 14.04.1 LTS: 0.9.11.2-0ubuntu1

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

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

Title:
  host system loses keyboard

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I use virtual machine or remote desktop and those operating systems 
crash or froze the host system sometimes "loses" the keyboard. I must kill the 
VM or RD to have keyboard again.
  I experienced this issue with Ubuntu 12.04 and 14.04 and mainly Windows as VM 
or RD.

  Kernel version:
  At least the series of 3.13 (64 bit) on both Ubuntu.

  Unity versions:
  Ubuntu 12.04.5 LTS: 5.20.0-0ubuntu3
  Ubuntu 14.04.1 LTS: 7.2.3-0ubuntu1

  Compiz versions:
  Ubuntu 12.04.5 LTS: 0.9.7.12-0ubuntu4
  Ubuntu 14.04.1 LTS: 0.9.11.2-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1396693/+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 1386255] Re: devhelp and many other apps crash with SIGSEGV in g_closure_invoke() due to overlay-scrollbars

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/overlay-scrollbar

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

Title:
  devhelp and many other apps crash with SIGSEGV in g_closure_invoke()
  due to overlay-scrollbars

Status in Overlay Scrollbar:
  New
Status in Ubuntu GNOME:
  New
Status in “overlay-scrollbar” package in Ubuntu:
  In Progress

Bug description:
  With the gnome3-team/gnome3-staging PPA enabled all Gtk+ applications
  segfault when I do stuff like

  - Press the  key
  - Press the Save button in gedit's headerbar
  - Press the hamburger menu button in devhelp's headerbar (the stack trace 
attached to this bug)
  - Press the Add button in gtimelog
  - Try to open any of the regular menus in gtimelog

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: devhelp 3.14.0-1~utopic1 [origin: LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 27 17:15:30 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/devhelp
  InstallationDate: Installed on 2012-07-25 (824 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcCmdline: devhelp
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: devhelp
  StacktraceTop:
   ?? ()
   g_closure_invoke (closure=0x11e4ce0, return_value=0x0, n_param_values=2, 
param_values=0x7fffd6ed0920, invocation_hint=0x7fffd6ed08c0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x11e50b0, detail=detail@entry=0, 
instance=instance@entry=0x182a510, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd6ed0920) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3483
   g_signal_emit_valist (instance=, signal_id=, 
detail=, var_args=var_args@entry=0x7fffd6ed0ab0) at 
/build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3309
   g_signal_emit (instance=instance@entry=0x182a510, signal_id=, 
detail=detail@entry=0) at /build/buildd/glib2.0-2.42.0/./gobject/gsignal.c:3365
  Title: devhelp crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (3 days ago)
  UserGroups: adm cdrom dip docker libvirtd lp lpadmin plugdev sambashare 
shared sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/overlay-scrollbar/+bug/1386255/+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 1300649] Re: Schemas should not come with the library package

[Michael Zanetti]

schemas moved to unity-schemas, and unity8 has been updated to depend on
that instead of libunity-core

** Changed in: unity
   Status: Confirmed => Fix Released

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

** Changed in: unity8 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Schemas should not come with the library package

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity8” package in Ubuntu:
  Fix Released

Bug description:
  ⟫ dpkg -L libunity-core-6.0-9 | grep schemas
  /usr/share/glib-2.0/schemas
  /usr/share/glib-2.0/schemas/com.canonical.Unity.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.unityshell.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.unitymtgrabhandles.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.unitydialog.gschema.xml
  /usr/share/glib-2.0/schemas/org.compiz.networkarearegion.gschema.xml

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr  1 09:30:16 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1300649/+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 1395455] Re: indicator-sound-service crashes on vivid

[Dmitry Shachnev]

** Description changed:

  On vivid, indicator-sound-service crashes on startup. I am not using
- Unity, and I cat reproduce the crash reliably in a minimal environment
+ Unity, and I can reproduce the crash reliably in a minimal environment
  (plain X with Metacity WM).
  
  (I recompiled indicator-sound with -g and -O0 to get an useful trace,
  thus not using apport-crash).

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

Title:
  indicator-sound-service crashes on vivid

Status in “indicator-sound” package in Ubuntu:
  Triaged

Bug description:
  On vivid, indicator-sound-service crashes on startup. I am not using
  Unity, and I can reproduce the crash reliably in a minimal environment
  (plain X with Metacity WM).

  (I recompiled indicator-sound with -g and -O0 to get an useful trace,
  thus not using apport-crash).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395455/+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 1335658] Re: No message or signal to notify the user that the battery is full

[Charles Kerr]

** Changed in: indicator-power (Ubuntu)
   Status: New => Confirmed

** Changed in: indicator-power (Ubuntu)
   Importance: Low => Wishlist

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

Title:
  No message or signal to notify the user that the battery is full

Status in The Power Indicator:
  New
Status in “indicator-power” package in Ubuntu:
  Confirmed

Bug description:
  There is no message or visual change to indicate to the user that the
  battery is full and we can disconnect the phone from the power
  adapter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-power/+bug/1335658/+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 1388235] Re: Battery icon turns red at 30%

[Charles Kerr]

** Changed in: indicator-power (Ubuntu)
   Importance: Undecided => High

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

Title:
  Battery icon turns red at 30%

Status in Ubuntu UX bugs:
  Confirmed
Status in “indicator-power” package in Ubuntu:
  In Progress
Status in “ubuntu-themes” package in Ubuntu:
  In Progress

Bug description:
  This seems a bit pessimistic since the phone still has a great deal of
  capacity and time left, perhaps 15 or 20% is a better threshold

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+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 1394887] Re: appmenu-qt5 fails to build against Qt 5.4.0 beta

[Launchpad Bug Tracker]

This bug was fixed in the package appmenu-qt5 -
0.3.0+15.04.20141126-0ubuntu1

---
appmenu-qt5 (0.3.0+15.04.20141126-0ubuntu1) vivid; urgency=low

  [ Łukasz 'sil2100' Zemczak ]
  * Change the way QKdeTheme is constructed to fit the way presented by
the new Qt 5.4.0 version. Make this change conditional so that it's
still buildable with earlier releases. (LP: #1394887)
 -- Ubuntu daily releaseWed, 26 Nov 2014 
10:36:43 +

** Changed in: appmenu-qt5 (Ubuntu)
   Status: New => Fix Released

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

Title:
  appmenu-qt5 fails to build against Qt 5.4.0 beta

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  Fix Released

Bug description:
  appmenu-qt5 fails to build against Qt 5.4.0 beta:

  https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing-
  archive-extra

  "appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 
'QKdeTheme::QKdeTheme(const QString&, int&)'
   : QKdeTheme(kdeHome, kdeVersion)"

  More information about Qt testing versions at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+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 1388235] Re: Battery icon turns red at 30%

[Charles Kerr]

According to Paty in IRC, this is fine with Design and tiheum's going to
add the new needed icons.

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

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-themes (Ubuntu)
 Assignee: (unassigned) => Matthieu James (tiheum)

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

Title:
  Battery icon turns red at 30%

Status in Ubuntu UX bugs:
  Confirmed
Status in “indicator-power” package in Ubuntu:
  In Progress
Status in “ubuntu-themes” package in Ubuntu:
  In Progress

Bug description:
  This seems a bit pessimistic since the phone still has a great deal of
  capacity and time left, perhaps 15 or 20% is a better threshold

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+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 1394887] Re: appmenu-qt5 fails to build against Qt 5.4.0 beta

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/vivid-proposed/appmenu-qt5

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

Title:
  appmenu-qt5 fails to build against Qt 5.4.0 beta

Status in Application menu for Qt5:
  In Progress
Status in “appmenu-qt5” package in Ubuntu:
  New

Bug description:
  appmenu-qt5 fails to build against Qt 5.4.0 beta:

  https://launchpad.net/~canonical-
  qt5-edgers/+archive/ubuntu/qt5-beta2/+sourcepub/4580920/+listing-
  archive-extra

  "appmenuplatformmenubar.cpp:304:36: error: no matching function for call to 
'QKdeTheme::QKdeTheme(const QString&, int&)'
   : QKdeTheme(kdeHome, kdeVersion)"

  More information about Qt testing versions at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1394887/+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 1376982] Re: Reboot and shutdown options doesn't work

[Charles Kerr]

What happens if you initiate the shutdown sequence from the command
line, rather than with indicator-session?

$ dbus-send --print-reply --dest="org.gnome.Shell"
/org/gnome/SessionManager/EndSessionDialog
org.gnome.SessionManager.EndSessionDialog.Open uint32:2 uint32:0
uint32:60 array:objpath:

** Changed in: indicator-session (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Reboot and shutdown options doesn't work

Status in “indicator-session” package in Ubuntu:
  Incomplete

Bug description:
  Choosing Reboot or Shutdown from the session menu shows you the
  confirmation dialog box, but doesn't reboot or shutdown the machine
  after confirming.

  The same is true in the login screen for Shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-session 12.10.5+14.10.20140919-0ubuntu1
  Uname: Linux 3.17.0-031700rc7-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  3 09:50:08 2014
  InstallationDate: Installed on 2012-06-26 (828 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  SourcePackage: indicator-session
  UpgradeStatus: Upgraded to utopic on 2014-09-22 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1376982/+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 1395455] Re: indicator-sound-service crashes on vivid

[Charles Kerr]

Dmitry, thanks for the patch!

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

Title:
  indicator-sound-service crashes on vivid

Status in “indicator-sound” package in Ubuntu:
  Triaged

Bug description:
  On vivid, indicator-sound-service crashes on startup. I am not using
  Unity, and I cat reproduce the crash reliably in a minimal environment
  (plain X with Metacity WM).

  (I recompiled indicator-sound with -g and -O0 to get an useful trace,
  thus not using apport-crash).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1395455/+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 1396603] [NEW] Application menu title can't be set

[Phil Wolff]

Public bug reported:

Ubuntu 14.10 64-bit
Unity 7.3.1+14.10.20141016-0ubuntu1

My application subclasses Gtk::Application, and my constructor calls
Glib::set_application_name ( "Test App Menu" ). I expected the app menu
to be titled "Test App Menu", which is what happens when using the Gnome
desktop. Instead, Unity titles it "Unknown Application Name."

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

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

Title:
  Application menu title can't be set

Status in “unity” package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10 64-bit
  Unity 7.3.1+14.10.20141016-0ubuntu1

  My application subclasses Gtk::Application, and my constructor calls
  Glib::set_application_name ( "Test App Menu" ). I expected the app
  menu to be titled "Test App Menu", which is what happens when using
  the Gnome desktop. Instead, Unity titles it "Unknown Application
  Name."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1396603/+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 1383382] Re: Adding indicator-applet appmenu does not export/move all menu items to panel (Utopic)

[Launchpad Bug Tracker]

** Branch linked: lp:~mitya57/unity-gtk-module/lp1383382

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

Title:
  Adding indicator-applet appmenu does not export/move all menu items to
  panel (Utopic)

Status in “unity-gtk-module” package in Ubuntu:
  In Progress

Bug description:
  Current Scenario

  1. install indicator-applet-appmenu
  2. add it to panel.

  3. In the panel, For some gtk apps (gnome-terminal) It is showing only
  a single menu; File->close. All other menu items remains in the app.
  For some other gtk apps (i.e. Nautilus, eog) it doesn't show any menu
  at all.

  4. Surprisingly for Firefox it does properly move all the menus to
  panel.

  Expected Scenario:

  Adding indicator-applet-appmenu or global menu should move all the
  menu items from local app to panel.

  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4
  unity-gtk-module: 0.0.0+14.10.20140716-0ubuntu1
  gtk3+: 3.12.2-0ubuntu14
  indicator-applet: 12.10.2+14.04.20140403-0ubuntu1
  indicator-appmenu: 13.01.0+14.04.20140404-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1383382/+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 1383382] Re: Adding indicator-applet appmenu does not export/move all menu items to panel (Utopic)

[Dmitry Shachnev]

This needs a fix in unity-gtk-module as well.

** Package changed: indicator-appmenu (Ubuntu) => unity-gtk-module
(Ubuntu)

** Changed in: unity-gtk-module (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: unity-gtk-module (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  Adding indicator-applet appmenu does not export/move all menu items to
  panel (Utopic)

Status in “unity-gtk-module” package in Ubuntu:
  In Progress

Bug description:
  Current Scenario

  1. install indicator-applet-appmenu
  2. add it to panel.

  3. In the panel, For some gtk apps (gnome-terminal) It is showing only
  a single menu; File->close. All other menu items remains in the app.
  For some other gtk apps (i.e. Nautilus, eog) it doesn't show any menu
  at all.

  4. Surprisingly for Firefox it does properly move all the menus to
  panel.

  Expected Scenario:

  Adding indicator-applet-appmenu or global menu should move all the
  menu items from local app to panel.

  Gnome-Panel version on Utopic: 1:3.8.1-2ubuntu4
  unity-gtk-module: 0.0.0+14.10.20140716-0ubuntu1
  gtk3+: 3.12.2-0ubuntu14
  indicator-applet: 12.10.2+14.04.20140403-0ubuntu1
  indicator-appmenu: 13.01.0+14.04.20140404-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1383382/+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 1308265] Re: First password letter not registered in lockscreen if screen off

[Olivier Febwin]

unity  7.3.1+14.10.20141016-0ubuntu1amd64

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

Title:
  First password letter not registered in lockscreen if screen off

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308265/+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 1308265] Re: First password letter not registered in lockscreen if screen off

[Olivier Febwin]

and this bug is still present on ubuntu 14.10

** Tags added: utopic

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

Title:
  First password letter not registered in lockscreen if screen off

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308265/+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 1396553] [NEW] No rating and 0 reviews shown for all applications in the dash

[Bruno Nova]

Public bug reported:

When viewing the preview of any application in the dash (installed or not) by 
right-clicking it, the displayed number of reviews is always 0 (zero) and the 
rating is always empty.
This used to work in previous Ubuntu versions.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Wed Nov 26 11:08:57 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (43 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  No rating and 0 reviews shown for all applications in the dash

Status in “unity” package in Ubuntu:
  New

Bug description:
  When viewing the preview of any application in the dash (installed or not) by 
right-clicking it, the displayed number of reviews is always 0 (zero) and the 
rating is always empty.
  This used to work in previous Ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Nov 26 11:08:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (43 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1396553/+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

Re: [Dx-packages] [Bug 1308265] Re: First password letter not registered in lockscreen if screen off

[Gotiniens]

I'm Also updated, and also experience the bug. Ridiculous that this is not
fixed yet. I experience this bug 10-20 times a day...

On Tue, Nov 25, 2014 at 4:05 PM, rpgmaker <1308...@bugs.launchpad.net>
wrote:

> Actually, I'm  a fully updated 14.04 and I still get this bug. I think
> the reason why it worked for #4 it's because of the shift thing, not
> because the bug isn't present on 14.04.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1308265
>
> Title:
>   First password letter not registered in lockscreen if screen off
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/1308265/+subscriptions
>

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

Title:
  First password letter not registered in lockscreen if screen off

Status in Unity:
  In Progress
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  In Progress

Bug description:
  With the new lockscreen, if my screen is off, I just start typing,
  every time my password is too short. It looks like the first key only
  triggers the screen on and does not go to the input field.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140414.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 15 23:59:08 2014
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308265/+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 1311316] Re: After locking screen there is no input field to type password for unlock

[Dmytro Tkanov]

I still get this issue on Ubuntu 14.04. Managed to get an input field
after killing all instances of unity-panel-service (it might be that
you'll have to run killall several times). After doing that I get
windows messed up among desktops. The good thing there are borders and
titles for all the windows. Usage of "unity --replace" solution works,
but removes borders and title bars for all windows.

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

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311316/+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