[Dx-packages] [Bug 778054] Re: Packages shouldn't depend on the transitional package python-gobject

2015-03-12 Thread Brian Murray
** Changed in: zeitgeist (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: zeitgeist (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: zeitgeist (Ubuntu Trusty)
   Importance: Undecided => Low

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

** Changed in: zeitgeist (Ubuntu Trusty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  Packages shouldn't depend on the transitional package python-gobject

Status in aptdaemon package in Ubuntu:
  Fix Released
Status in desktopcouch package in Ubuntu:
  Invalid
Status in eglibc package in Ubuntu:
  Invalid
Status in gnome-utils package in Ubuntu:
  Invalid
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in wine1.4 package in Ubuntu:
  Fix Released
Status in zeitgeist package in Ubuntu:
  In Progress
Status in aptdaemon source package in Trusty:
  Fix Released
Status in desktopcouch source package in Trusty:
  Invalid
Status in eglibc source package in Trusty:
  Invalid
Status in gnome-utils source package in Trusty:
  Invalid
Status in libreoffice source package in Trusty:
  Fix Released
Status in openoffice.org source package in Trusty:
  Invalid
Status in system-config-printer source package in Trusty:
  Fix Released
Status in wine1.4 source package in Trusty:
  Invalid
Status in zeitgeist source package in Trusty:
  In Progress

Bug description:
  [Impact]

  python-zeitgeist depends on python-gobject, which means python-gobject
  cannot be removed from the system. python-gobject is a transitional
  package, and packages should be updated to no longer depend on it.

  [Test Case]

  * Install python-zeitgeist, and verify that python-gobject is not
  installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing python-zeitgeist.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

  ---

  [Impact]

  system-config-printer-gnome depends on python-gobject, which means
  python-gobject cannot be removed from the system. python-gobject is a
  transitional package, and packages should be updated to no longer
  depend on it.

  [Test Case]

  * Install system-config-printer-gnome, and verify that python-gobject
  is not installed with it.

  * If it is already installed, you should be able to run 'apt-get purge
  python-gobject' without removing system-config-printer-gnome.

  [Regression Potential]

  Negligible. There are no code changes. The fix only removes a
  dependency on a transitional package that doesn't provide any files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/778054/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-03-12 Thread JW
> Devices that report a wrong time remaining need to be blacklisted,
just like any other misbehaving hardware device.

Even if this means most devices will need to be blacklisted? Wouldn't it
require an extreme amount of effort to start blacklisting every mouse
that doesn't work with this feature?

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1413411] Re: underscore in mounted drive name mishandled in menu

2015-03-12 Thread Stephen M. Webb
** Also affects: unity/7.2
   Importance: Undecided
   Status: New

** Changed in: unity/7.2
   Status: New => In Progress

** Changed in: unity/7.2
   Importance: Undecided => Medium

** Changed in: unity/7.2
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Changed in: unity/7.2
Milestone: None => 7.2.5

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

Title:
  underscore in mounted drive name mishandled in menu

Status in One Hundred Papercuts:
  In Progress
Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  If you have a mounted drive with an underscore in it's name (e.g.
  host_S), then, when you right-click on the drive icon in the sidebar,
  the menu interprets the underscore as a keyboard-shortcut indicator,
  so shows the name as hostS (with S underlined). Hovering over the
  drive results in the correct "host_S" name; the bug is only in the
  right-click menu. Note that right-clicking on the "Files" icon will
  show a menu that includes the correct mounted disk names. It is only
  right-clicking on the drive-icons themselves that shows the incorrect
  name.

  Ubuntu 14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  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
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Thu Jan 22 11:51:46 2015
  InstallationDate: Installed on 2015-01-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service

2015-03-12 Thread Martin Pitt
** Changed in: systemd-shim (Ubuntu)
   Importance: High => Medium

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

Title:
  [7.287663] systemd-logind[1057]: Failed to start unit
  user@126.service: Unknown unit: user@126.service

Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd-shim package in Ubuntu:
  Triaged
Status in systemd source package in Utopic:
  Triaged
Status in systemd-shim source package in Utopic:
  Won't Fix
Status in systemd-shim package in Debian:
  New

Bug description:
  ATTENTION: This bug is fully understood, there is *no need* to add
  even more comments about "me too" here.

  [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: 
Unknown unit: user@126.service
  [7.287677] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@126.service
  [7.293871] systemd-logind[1057]: New session c1 of user lightdm.
  [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/126/X11-display.
  [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team
  [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
  [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready
  [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec
  [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3)
  [9.920181] wlan0: authenticated
  [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3)
  [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 
status=0 aid=2)
  [9.927753] wlan0: associated
  [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [   12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope
  [   12.677122] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc1_2escope
  [   12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
  [   12.683912] systemd-logind[1057]: Failed to start user service: Unknown 
unit: user@1000.service
  [   12.685157] systemd-logind[1057]: New session c2 of user caravena.
  [   12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  [  234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope
  [  234.494478] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
  [  235.514349] systemd-logind[1057]: New session c3 of user lightdm.
  [  244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope
  [  244.245923] systemd-logind[1057]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc3_2escope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: systemd 208-7ubuntu4 [modified: 
usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic x86_64
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 20 18:26:06 2014
  InstallationDate: Installed on 2014-04-27 (115 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1359439/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged

2015-03-12 Thread Ryan Lortie
Just to play devil's advocate a bit here:

The logic taken in this bug (that we should show the device that will
run out of power first) seems perfectly sound, but it makes a very large
assumption, which I suspect will often be untrue: that reporting of time
remaining on mice will always be completely accurate.

I think there are two problems with the assumption.

The first is that there have been reports (one just now on IRC from
jcastro) about faulty hardware/driver combos that report things like "1
minute remaining" all the time.  Users with this hardware would probably
like that fixed, but for lack of a fix, would probably prefer to be able
to go on with their lives with the minimum amount of disruption.

Second issue is that I wonder if "estimated time left" reporting on a
device which has a battery that lasts up to a year is _ever_ accurate to
the hours or minutes that we would need it to be in order to
meaningfully compare it against laptop battery life.

Those two point combined cause me to believe that the only case in which
this feature would be engaged would be in the "wrong" case.  Maybe it
makes sense to just remove it entirely after all?

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

Title:
  Mouse with no time remaining estimate showing in preference to battery
  being charged

Status in indicator-power package in Ubuntu:
  In Progress

Bug description:
  When my laptop battery is in a charging state, but is not fully
  charged, I expect it to be displayed in preference to my mouse, which
  has no time remaining estimate.

  The spec here:

  https://wiki.ubuntu.com/Power

  says:

  "If anything is discharging, the menu title should represent the
  component (not battery, but component) that is estimated to lose power
  first. For example, if your notebook battery is estimated to discharge
  in 1 hour 47 minutes, and your wireless mouse battery is estimated to
  discharge in 27 minutes, the menu title should represent the mouse. "

  but there doesn't seem to be any guideline to what happens when a
  battery is being charged.

  I suggest the time remaining to charge a battery should be displayed
  in preference to the power level in a wireless mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May  2 11:50:36 2014
  InstallationDate: Installed on 2013-11-26 (156 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1428015] Re: Xubuntu 15.04: indicator-sound-service crashed with signal 5 in main()

2015-03-12 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Xubuntu 15.04: indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  Xubuntu 15.04 fresh install

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150227.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar  4 08:27:28 2015
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  InstallationDate: Installed on 2015-03-02 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150224)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1428015/+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 10905] Re: Keyboard shortcuts, window management - Can't use any global keyboard shortcuts or hotkeys when applet/menu is open

2015-03-12 Thread Mathew Hodson
** Bug watch removed: Ubuntu.com Bugzilla [Obsoleted by Launchpad] #4360
   http://bugzilla.ubuntu.com/show_bug.cgi?id=4360

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

Title:
  Keyboard shortcuts, window management - Can't use any global keyboard
  shortcuts or hotkeys when applet/menu is open

Status in Ayatana Design:
  Fix Committed
Status in GTK+ GUI Toolkit:
  Won't Fix
Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Reproduce scenario :
   - left click on an applet
   - try the ^-Alt arrow to switch desktop

  When an applet contextual menu is opened, you can't switch desktop with 
keyboard shortcuts.
  Normally,we should have a consistent behaviour in regards with the 
workspace-selector applet, ie :
   - first ^-Alt-arrow (for the workspace-selector : click), the menu is 
unfolded
   - second ^-Alt-arrow , we go to the next desktop

  ===

  see bug 29894 for not being able to take screenshots when menu is
  open, another symptom of this bug.

  
  --

  Note from Design:

  This is a critical bug, a user should be able to use a global keyboard
  shortcut at any moment, including when a menu is open.  In the
  unlikely case that there is a conflict between the global keyboard
  shortcuts ( see
  https://launchpadlibrarian.net/85352653/Super_key_shutcuts_overlay.png
  ) and the menu keyboard shortcuts, the menu keyboard shortcuts should
  take precedence.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/10905/+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 29894] Re: can't take screenshot when menu on panel is opened

2015-03-12 Thread Mathew Hodson
** Project changed: gnome-utils => gnome-panel

** Package changed: gnome-utils (Ubuntu) => gnome-panel (Ubuntu)

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

Title:
  can't take screenshot when menu on panel is opened

Status in Desktop panel for GNOME:
  In Progress
Status in Unity:
  Triaged
Status in gnome-panel package in Ubuntu:
  Triaged
Status in gnome-screenshot package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged

Bug description:
  I can always press the "Print screen" key to take a screenshot of my
  desktop. When i click on say, the System menu in the gnome-panel, it
  just doesn't work anymore.

  Note: this is in fact only a symptom of bug 10905 that states that no
  hotkeys/shortcuts whatsoever can be triggered when a menu is open.
  there seems to be a dispute if that is a bug or an intended design
  decision. thus bug 10905 and its duplicates always get closed. people
  seem to agree that not being able to take screenshots is not intended
  bahavior and considered a bug. thus this report is allowed to stay
  open :)

  a known workaround for taking screenshots of menus is to directly launch the 
screengrabber with a delay like so:
  gnome-screenshot --delay=5

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/29894/+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 1431223] Re: notify-osd crashed with signal 5 in _XReply()

2015-03-12 Thread Apport retracing service
*** This bug is a duplicate of bug 1275524 ***
https://bugs.launchpad.net/bugs/1275524

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1275524
   notify-osd crashed with signal 5 in _XReply()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  notify-osd crashed with signal 5 in _XReply()

Status in notify-osd package in Ubuntu:
  New

Bug description:
  Notify OSD crashed on me this morning.  I was changing networks from
  wifi to Ethernet at the time.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 12 09:08:31 2015
  DesktopSession: 'ubuntu'
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd
  GtkTheme: 'Ambiance'
  IconTheme: 'ubuntu-mono-dark'
  InstallationDate: Installed on 2014-06-05 (279 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  MachineType: LENOVO 2320CTO
  ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=8f6baa39-b057-41c2-bfe9-6c77484299ab ro quiet splash pcie_aspm=force 
crashkernel=384M-:128M
  RelatedPackageVersions:
   xserver-xorg 1:7.7+7ubuntu2
   libgl1-mesa-glx  10.5.0-0ubuntu1
   libdrm2  2.4.59-0ubuntu1
   xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2
   xserver-xorg-video-ati   1:7.4.0-2ubuntu2
  Signal: 5
  SourcePackage: notify-osd
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: notify-osd crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare sbuild 
sudo
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET31WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2320CTO
  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:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2320CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1431223/+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 1295445] Re: Cursor size is not updated on HiDPI at intermediate UI scale levels

2015-03-12 Thread David White
I've come across this or a similar bug in 14.10 which runs unity 7.3.1.
I'm on a DELL XPS 15 with a 240 dpi screen. This looks best with a
scaling factor of 2 or 2.5. The mouse in most applications (firefox,
terminal) is the proper size but on the desktop and in nautilus windows
it is very tiny.

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

Title:
  Cursor size is not updated on HiDPI at intermediate UI scale levels

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When UI scale factor is at intermediate values from 1.0-2.0 and from
  2.0-3.0 the cursor size is not updated to match current settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295445/+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 1413773] Re: [Regressions] Dash dnd icons rendered behind dash.

2015-03-12 Thread Stephen M. Webb
** Also affects: unity/7.2
   Importance: Undecided
   Status: New

** Changed in: unity/7.2
   Status: New => In Progress

** Changed in: unity/7.2
   Importance: Undecided => High

** Changed in: unity/7.2
 Assignee: (unassigned) => Stephen M. Webb (bregma)

** Changed in: unity/7.2
Milestone: None => 7.2.5

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

Title:
  [Regressions] Dash dnd icons rendered behind dash.

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

Bug description:
  In Ubuntu 15.04 dragged icons are rendered behind dash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1413773/+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 1320880] Re: Calendar notifications are treated the same as an alarm notification

2015-03-12 Thread Kunal Parmar
** Changed in: ubuntu-calendar-app
   Status: In Progress => Fix Released

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

Title:
  Calendar notifications are treated the same as an alarm notification

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Calendar application for Ubuntu devices:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  If an alarm fires, the alarm sound seemingly will persist forever.
  This seems like perhaps the right choice for an alarm clock, but seems
  inappropriate for a calendar reminder. I would expect a calendar
  reminder to sound for only a short period.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1320880/+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 1295445] Re: Cursor size is not updated on HiDPI at intermediate UI scale levels

2015-03-12 Thread Treviño
As a workaround, restarting unity should work (i.e. open a terminal or
alt+f2 and launch "unity" or "compiz --replace").

It looks that these settings aren't picked at the right time...

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

Title:
  Cursor size is not updated on HiDPI at intermediate UI scale levels

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When UI scale factor is at intermediate values from 1.0-2.0 and from
  2.0-3.0 the cursor size is not updated to match current settings.

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

2015-03-12 Thread Pat McGowan
** Changed in: media-hub (Ubuntu)
 Assignee: (unassigned) => Canonical Phone Foundations 
(canonical-phonedations-team)

** No longer affects: media-hub (Ubuntu RTM)

** Changed in: canonical-devices-system-image
Milestone: ww11-2015 => ww13-2015

-- 
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:
  Invalid
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 1387691] Re: Media Player should not be visible in the app scope and launcher

2015-03-12 Thread Pat McGowan
** Changed in: canonical-devices-system-image
Milestone: ww11-2015 => ww13-2015

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

Title:
  Media Player should not be visible in the app scope and launcher

Status in the base for Ubuntu mobile products:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in mediaplayer-app package in Ubuntu:
  In Progress
Status in unity8 package in Ubuntu:
  Invalid
Status in url-dispatcher package in Ubuntu:
  In Progress
Status in mediaplayer-app package in Ubuntu RTM:
  In Progress
Status in url-dispatcher package in Ubuntu RTM:
  In Progress

Bug description:
  The mediaplayer is an 'auxiliary app' in the current design approach.
  That means that its purpouse it playback media launched by other apps
  (e.g Messaging) or scopes (e.g. Videos). It should not be launched
  from the App scopes.

  However, the 'Update' section System Settings should still display it
  when an update to mediaplayer is available.

  Current behaviour
  - Mediaplayer app displayed in App Scope, Launcher and Settings

  Desired behaviour
  - Mediaplayer app not displayed in App Scope or Launcher
  - Mediaplayer displayed in Settings > Update

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+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 1423855] Re: Unity can't show the global menu item for some gnome apps

2015-03-12 Thread Stephen M. Webb
** Changed in: unity
Milestone: 7.3.2 => None

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

Title:
  Unity can't show the global menu item for some gnome apps

Status in Unity:
  Won't Fix
Status in indicator-appmenu package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  Unity can't show the global menu item for some gnome apps.

  For example, the 'terminal' menu for gnome-terminal, or the
  'calculator' menu for gnome-calculator cannot be opened.  Other menus
  can be displayed (file, edit,...)

  This is a recent regression I think.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Feb 20 21:14:01 2015
  InstallationDate: Installed on 2015-01-31 (20 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1423855/+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 833727] Re: Panel opacity setting is ignored (always opaque) on startup

2015-03-12 Thread Stephen M. Webb
Also verified Panel opacity works correctly with the Ambiance, Radiance,
and High Contrast themes in the 5 series of Unity.

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

Title:
  Panel opacity setting is ignored (always opaque) on startup

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Expired

Bug description:
  Tried to set panel transparency with unity plugin in CCSM and I can't
  obtain tranparency for the panel while using Radiance Theme. That's OK
  with Ambiance Theme .

   Last Update/upgrade done at 13.00 pm

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.8.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,vpswitch,gnomecompat,mousepoll,regex,imgpng,animation,grid,wall,workarounds,place,resize,move,snap,session,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Aug 25 14:12:54 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  GraphicsCard: ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490] 
(prog-if 00 [VGA controller])
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110808)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic 
root=UUID=b2f3b035-88c2-450b-919e-0b65be858730 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 04/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0220
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QPL-VM EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0220:bd04/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-VMEPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu16
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/833727/+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 1295445] Re: Cursor size is not updated on HiDPI at intermediate UI scale levels

2015-03-12 Thread David White
Thank you, that worked!  However, on reboot it's all back to how it was.
At least I know there's a workaround and don't have to carry on
searching through settings trying to get it to work.

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

Title:
  Cursor size is not updated on HiDPI at intermediate UI scale levels

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  When UI scale factor is at intermediate values from 1.0-2.0 and from
  2.0-3.0 the cursor size is not updated to match current settings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1295445/+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 1425078] Re: Cannot callback/send messages from Notifications

2015-03-12 Thread Pat McGowan
** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Cannot callback/send messages from Notifications

Status in the base for Ubuntu mobile products:
  Fix Released
Status in indicator-messages package in Ubuntu:
  Fix Released
Status in unity-notifications package in Ubuntu:
  New

Bug description:
  1. Create an incoming call to your Ubuntu phone from another device
  2. Don't pickup the call so that missed call notification appears in the 
'Notifications' menu
  3. Open Notifications and tap on the missed call entry for it to expand
  4. press the 'Call back' button

  What happens: Nothing

  What should happen:
  Dialer app should open with the relevant number already in the input box.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-messages 13.10.1+15.04.20150219-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: armhf
  Date: Tue Feb 24 18:36:59 2015
  InstallationDate: Installed on 2015-02-24 (0 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150224-020204)
  SourcePackage: indicator-messages
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425078/+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 833727] Re: Panel opacity setting is ignored (always opaque) on startup

2015-03-12 Thread Stephen M. Webb
Verified that Panel transparency is 100% controllable on the Adwaita,
Ambience, Radiance, and High Contrast themes in Unity 7 or later.
Marking as fixed for those series.

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

** Changed in: unity
Milestone: 7.3.2 => None

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

Title:
  Panel opacity setting is ignored (always opaque) on startup

Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Expired

Bug description:
  Tried to set panel transparency with unity plugin in CCSM and I can't
  obtain tranparency for the panel while using Radiance Theme. That's OK
  with Ambiance Theme .

   Last Update/upgrade done at 13.00 pm

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.8.2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,vpswitch,gnomecompat,mousepoll,regex,imgpng,animation,grid,wall,workarounds,place,resize,move,snap,session,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  Date: Thu Aug 25 14:12:54 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  GraphicsCard: ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490] 
(prog-if 00 [VGA controller])
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110808)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic 
root=UUID=b2f3b035-88c2-450b-919e-0b65be858730 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   
  dmi.bios.date: 04/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0220
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QPL-VM EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0220:bd04/10/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-VMEPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu16
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/833727/+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 1431384] [NEW] Need a mechanism for specifying an ical event's icon

2015-03-12 Thread Charles Kerr
Public bug reported:

This issue was raised in discussion with mzanetti, who would like
reminders (created with reminder-app) to be shown in the drop-down menu
with that app's icon.

datetime currently is implemented with "everything is either a clock-app
alarm or a calendar-app event", which is not an approach that will scale
to 3rd party apps. I suggest we add something like an x-unity-alarm-icon
tag to the ical components to let clients specify their own icon as a
string that gets passed to unity8.

See related bug https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1426519 for letting the clients, rather than datetime,
specify the behavior when the menuitems are clicked.

** Affects: indicator-datetime (Ubuntu)
 Importance: Medium
 Assignee: Charles Kerr (charlesk)
 Status: Confirmed

** Summary changed:

- Need a mechanism for specifying an icon for an appointment
+ Need a mechanism for specifying an ical event's icon

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Need a mechanism for specifying an ical event's icon

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This issue was raised in discussion with mzanetti, who would like
  reminders (created with reminder-app) to be shown in the drop-down
  menu with that app's icon.

  datetime currently is implemented with "everything is either a clock-
  app alarm or a calendar-app event", which is not an approach that will
  scale to 3rd party apps. I suggest we add something like an x-unity-
  alarm-icon tag to the ical components to let clients specify their own
  icon as a string that gets passed to unity8.

  See related bug https://bugs.launchpad.net/ubuntu/+source/indicator-
  datetime/+bug/1426519 for letting the clients, rather than datetime,
  specify the behavior when the menuitems are clicked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1431384/+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 1426519] Re: Need a mechanism for specifying what happens when an ical menuitem is clickced

2015-03-12 Thread Charles Kerr
** Summary changed:

- i-dt should support ical's "url" property for launching related apps
+ Need a mechanism for specifying what happens when an ical menuitem is clickced

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

Title:
  Need a mechanism for specifying what happens when an ical menuitem is
  clickced

Status in Clock application for Ubuntu devices:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in reminders-app package in Ubuntu:
  New
Status in ubuntu-calendar-app package in Ubuntu:
  New

Bug description:
  indicator-datetime needs a way to dispatch an arbitrary URL when a
  user clicks on an ical event menuitem.

  In practice, datetime currently has clock-app hardwired for
  dispatching alarms (dispatch_url('appid://com.ubuntu.clock/clock
  /current-user-version')) and calendar-app for everything else
  (dispatch_url('appid://com.ubuntu.calendar/calendar/current-user-
  version')).

  There are two use cases that can be supported by datetime handling the
  URL property :

  (1) Clicking on an alarm menuitem opens up clock-app to that specific
  alarm, rather than to clock-app's main page. Clock-app could specify
  the information it needs in the URL, then open the right page when
  passed that information later. indicator-datetime would act as a
  simple pass-through.

  (2) non-calendar, non-alarm items such as from the reminders app as
  requested by mzanetti. The pattern would be the same as clock-app:
  Reminders would add whatever URL it wants, then datetime would act as
  a simple pass-through. This is preferable to adding more special cases
  to indicator-datetime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1426519/+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 1431384] Re: Need a mechanism for specifying an ical event's icon

2015-03-12 Thread Michael Zanetti
** Changed in: indicator-datetime (Ubuntu)
   Status: Triaged => Confirmed

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

Title:
  Need a mechanism for specifying an ical event's icon

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  This issue was raised in discussion with mzanetti, who would like
  reminders (created with reminder-app) to be shown in the drop-down
  menu with that app's icon.

  datetime currently is implemented with "everything is either a clock-
  app alarm or a calendar-app event", which is not an approach that will
  scale to 3rd party apps. I suggest we add something like an x-unity-
  alarm-icon tag to the ical components to let clients specify their own
  icon as a string that gets passed to unity8.

  See related bug https://bugs.launchpad.net/ubuntu/+source/indicator-
  datetime/+bug/1426519 for letting the clients, rather than datetime,
  specify the behavior when the menuitems are clicked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1431384/+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 1426519] Re: Need a mechanism for specifying what happens when an ical menuitem is clickced

2015-03-12 Thread Charles Kerr
nik90, what I mean is that the necessary information you're referring to
would be encoded in the URL that is provided by clock-app (or by the
alarm controls in ubuntu-ui-toollkit, depending on where that logic
lives).

So I'd like to replace the current implentation
('url_dispatch("appid://com.ubuntu.calendar/calendar/current-user-
version")') with something like 'url_dispatch(event.url)' where the url
would be provided by clock/calendar/reminder and would read something
like, say, 'appid://com.ubuntu.calendar/calendar/current-user-
version?alarm=someAlarmId'

This would require clock-app (or the alarm controls) to add this code,
but the advantage of this approach is it scales to future third-party
apps as well as adding reminder to the current pool of clock & calendar.

** Description changed:

  indicator-datetime needs a way to dispatch an arbitrary URL when a user
  clicks on an ical event menuitem.
  
  In practice, datetime currently has clock-app hardwired for dispatching
  alarms (dispatch_url('appid://com.ubuntu.clock/clock/current-user-
  version')) and calendar-app for everything else
  (dispatch_url('appid://com.ubuntu.calendar/calendar/current-user-
  version')).
  
  There are two use cases that can be supported by datetime handling the
  URL property :
  
  (1) Clicking on an alarm menuitem opens up clock-app to that specific
  alarm, rather than to clock-app's main page. Clock-app could specify the
  information it needs in the URL, then open the right page when passed
  that information later. indicator-datetime would act as a simple pass-
  through.
  
  (2) non-calendar, non-alarm items such as from the reminders app as
  requested by mzanetti. The pattern would be the same as clock-app:
  Reminders would add whatever URL it wants, then datetime would act as a
  simple pass-through. This is preferable to adding more special cases to
  indicator-datetime.
+ 
+ See also related bug  which discusses abstracting out the
+ icon shown in ical events' menuitems

** Summary changed:

- Need a mechanism for specifying what happens when an ical menuitem is clickced
+ Need a mechanism for specifying what happens when an ical menuitem is clicked

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Need a mechanism for specifying what happens when an ical menuitem is
  clicked

Status in Clock application for Ubuntu devices:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  New
Status in ubuntu-calendar-app package in Ubuntu:
  New

Bug description:
  indicator-datetime needs a way to dispatch an arbitrary URL when a
  user clicks on an ical event menuitem.

  In practice, datetime currently has clock-app hardwired for
  dispatching alarms (dispatch_url('appid://com.ubuntu.clock/clock
  /current-user-version')) and calendar-app for everything else
  (dispatch_url('appid://com.ubuntu.calendar/calendar/current-user-
  version')).

  There are two use cases that can be supported by datetime handling the
  URL property :

  (1) Clicking on an alarm menuitem opens up clock-app to that specific
  alarm, rather than to clock-app's main page. Clock-app could specify
  the information it needs in the URL, then open the right page when
  passed that information later. indicator-datetime would act as a
  simple pass-through.

  (2) non-calendar, non-alarm items such as from the reminders app as
  requested by mzanetti. The pattern would be the same as clock-app:
  Reminders would add whatever URL it wants, then datetime would act as
  a simple pass-through. This is preferable to adding more special cases
  to indicator-datetime.

  See also related bug  which discusses abstracting out the
  icon shown in ical events' menuitems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1426519/+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 1429388] Re: Can't select sunday 29.03.2015

2015-03-12 Thread Charles Kerr
This might be an IDO bug rather than a datetime bug; I'll need to triage
more to know for certain.

seb128 is able to repeat this for 2015.03.29 in vivid with french locale

larsu's also seeing it for 2015.03.29 in en_US

I'm not able to trigger it on that date, but Laney and I are both seeing
it on 2015.03.08 -- if you click on that date, it immediately jumps back
to 2015.03.07.

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Medium

** Changed in: indicator-datetime (Ubuntu)
 Assignee: (unassigned) => Charles Kerr (charlesk)

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

Title:
  Can't select sunday 29.03.2015

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Can't select sunday 29.03.2015 in calendar. Date is changing to
  28.03.2015 immediately. See the video.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  7 15:12:01 2015
  InstallationDate: Installed on 2014-11-04 (122 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1429388/+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 1313446] Re: window disappears on toggle shade

2015-03-12 Thread Paarvai Naai
I am extremely surprised and disappointed at how this bug continues to
persist for so long with no hope in sight for a fix.  Window shading has
been a fundamental function present in X11 window managers for 20+
years.  This feature has critically broken in Unity somewhere between
12.04 and 14.04 yet there has been no movement on fixing this bug.

Unfortunately in my office environment our computers are standardized on
Unity which makes this even more painful on a daily basis (I run KDE at
home).

Is there any way this issue can be prioritized before more and more
releases of Ubuntu are made with this issue?

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

Title:
  window disappears on toggle shade

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I used Unity Tweak Tool to enable Toggle Shade using middle click.
  When I click to top of the window, it rolls up and disappears. A
  "ghost" outline of the window appears and the only way to get the
  window back is by using Alt-tab. Sometimes, when reselecting the
  window using Alt-tab, Ubuntu freezes (crashes) and an internal error
  is generated. It seems to be related to Compiz but I'm not sure. An
  error report was generated and sent.

  Description:  Ubuntu 14.04 LTS (64-bit)
  Release:  14.04
  unity-tweak-tool 0.0.6ubuntu1

  I expected the window would "roll up" and I'd be left with the
  window's top bar like with previous versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1313446/+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 1429388] Re: Can't select sunday 29.03.2015

2015-03-12 Thread Charles Kerr
Oh of course, the 8th and the 29th are a giveaway aren't they... those
are the dates for US and European DST changes

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

Title:
  Can't select sunday 29.03.2015

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Can't select sunday 29.03.2015 in calendar. Date is changing to
  28.03.2015 immediately. See the video.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-datetime 13.10.0+14.10.20141009-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  7 15:12:01 2015
  InstallationDate: Installed on 2014-11-04 (122 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1429388/+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 1313446] Re: window disappears on toggle shade

2015-03-12 Thread Bob-El
I'm with you Paarvai. This is a terrible lack of support. I frequently find
bug complaints are passed over

Nooo laddie, not an iThing. It's a Samsung Galaxy.
On Mar 12, 2015 10:55 AM, "Paarvai Naai"  wrote:

> I am extremely surprised and disappointed at how this bug continues to
> persist for so long with no hope in sight for a fix.  Window shading has
> been a fundamental function present in X11 window managers for 20+
> years.  This feature has critically broken in Unity somewhere between
> 12.04 and 14.04 yet there has been no movement on fixing this bug.
>
> Unfortunately in my office environment our computers are standardized on
> Unity which makes this even more painful on a daily basis (I run KDE at
> home).
>
> Is there any way this issue can be prioritized before more and more
> releases of Ubuntu are made with this issue?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1313446
>
> Title:
>   window disappears on toggle shade
>
> Status in Unity:
>   Confirmed
> Status in unity package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I used Unity Tweak Tool to enable Toggle Shade using middle click.
>   When I click to top of the window, it rolls up and disappears. A
>   "ghost" outline of the window appears and the only way to get the
>   window back is by using Alt-tab. Sometimes, when reselecting the
>   window using Alt-tab, Ubuntu freezes (crashes) and an internal error
>   is generated. It seems to be related to Compiz but I'm not sure. An
>   error report was generated and sent.
>
>   Description:  Ubuntu 14.04 LTS (64-bit)
>   Release:  14.04
>   unity-tweak-tool 0.0.6ubuntu1
>
>   I expected the window would "roll up" and I'd be left with the
>   window's top bar like with previous versions of Ubuntu.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/unity/+bug/1313446/+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/1313446

Title:
  window disappears on toggle shade

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  I used Unity Tweak Tool to enable Toggle Shade using middle click.
  When I click to top of the window, it rolls up and disappears. A
  "ghost" outline of the window appears and the only way to get the
  window back is by using Alt-tab. Sometimes, when reselecting the
  window using Alt-tab, Ubuntu freezes (crashes) and an internal error
  is generated. It seems to be related to Compiz but I'm not sure. An
  error report was generated and sent.

  Description:  Ubuntu 14.04 LTS (64-bit)
  Release:  14.04
  unity-tweak-tool 0.0.6ubuntu1

  I expected the window would "roll up" and I'd be left with the
  window's top bar like with previous versions of Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1313446/+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 1424312] Re: compiz crashed with SIGSEGV in unity::XdndStartStopNotifierImp::DndTimeoutSetup()

2015-03-12 Thread 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/1424312

Title:
  compiz crashed with SIGSEGV in
  unity::XdndStartStopNotifierImp::DndTimeoutSetup()

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  problems with unity

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Feb 21 22:08:10 2015
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-02-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  ProcCmdline: compiz
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   unity::XdndStartStopNotifierImp::DndTimeoutSetup() () from 
/usr/lib/compiz/libunityshell.so
   sigc::internal::signal_emit1::emit(sigc::internal::signal_impl*, unsigned long const&) () from 
/usr/lib/compiz/libunityshell.so
   unity::PluginAdapter::Notify(CompWindow*, CompWindowNotify) () from 
/usr/lib/compiz/libunityshell.so
   unity::UnityWindow::windowNotify(CompWindowNotify) () from 
/usr/lib/compiz/libunityshell.so
   CompWindow::windowNotify(CompWindowNotify) () from 
/usr/lib/x86_64-linux-gnu/libcompiz_core.so.ABI-20140123
  Title: compiz crashed with SIGSEGV in 
unity::XdndStartStopNotifierImp::DndTimeoutSetup()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1424312/+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 1431512] Re: compiz crashed with signal 5 in _XReply()

2015-03-12 Thread Apport retracing service
*** This bug is a duplicate of bug 1358238 ***
https://bugs.launchpad.net/bugs/1358238

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1358238

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  compiz crashed with signal 5 in _XReply()

Status in unity package in Ubuntu:
  New

Bug description:
  Dont know more

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150227-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Mar 12 18:51:59 2015
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2015-03-06 (6 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20150305)
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
   XSync () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
  Title: compiz crashed with signal 5 in _XReply()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1431512/+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 1431513] [NEW] Properly handle dismissal of first run shortcut overlay

2015-03-12 Thread Christopher Townsend
Public bug reported:

A stop gap workaround has been put in place for bug #1313597, but the
proper fix is to use the input::Monitor when it merges.  See
https://code.launchpad.net/~3v1n0/unity/lockscreen-grabbing

** Affects: unity
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

** Affects: unity (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

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

** Changed in: unity
   Status: New => Confirmed

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

** Changed in: unity
   Importance: Undecided => Medium

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

** Changed in: unity
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
Milestone: None => 7.3.2

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

Title:
  Properly handle dismissal of first run shortcut overlay

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  A stop gap workaround has been put in place for bug #1313597, but the
  proper fix is to use the input::Monitor when it merges.  See
  https://code.launchpad.net/~3v1n0/unity/lockscreen-grabbing

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1431513/+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 1358238] Re: compiz crashed with signal 5 in _XReply()

2015-03-12 Thread Christopher Townsend
** Information type changed from Private to Public

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

Title:
  compiz crashed with signal 5 in _XReply()

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  in start ubuntu before update

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140811-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Uname: Linux 3.16.0-9-generic i686
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Aug 17 13:58:51 2014
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-12-20 (240 days ago)
  InstallationMedia: Stoq 1.7.0 "Stoq" - Release i386 (20130403)
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=pt_BR:
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: unity
  StacktraceTop:
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
   _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
   XSync () from /usr/lib/i386-linux-gnu/libX11.so.6
   ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2
  Title: compiz crashed with signal 5 in _XReply()
  UpgradeStatus: Upgraded to utopic on 2014-08-14 (3 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo

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