[Desktop-packages] [Bug 1056488] Re: [UIFe] Messaging menu title icons are indistinct

2012-10-03 Thread Michael Casadevall
Reverted upload accepted.

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

Title:
  [UIFe] Messaging menu title icons are indistinct

Status in “humanity-icon-theme” package in Ubuntu:
  Fix Released
Status in “ubuntu-mono” package in Ubuntu:
  Fix Released
Status in “humanity-icon-theme” source package in Quantal:
  Fix Released
Status in “ubuntu-mono” source package in Quantal:
  Fix Released

Bug description:
  ubuntu-mono 0.0.45, Ubuntu Q

  1. gthumb /usr/share/icons/Humanity/status/*/user-* /usr/share/icons
  /ubuntu-mono-*/status/*/indicator-messages-*

  What you see:

  A. Humanity's standalone IM status icons are a bit hard to see against
  a white background -- such as Empathy's status menu -- because the
  tops of the icons are white with no outline.

  B. The corresponding emblems are similarly hard to see against the
  light grey, black, or blue envelopes in Ubuntu Mono's messaging menu
  icons. http://cloudfront.omgubuntu.co.uk/wp-content/uploads/2012/08
  /new-icons.jpg The Offline and mixed-status icons are particularly
  bad.

  C. The Invisible icons and emblems have a pure black or white
  interior, which just looks weird. http://cloudfront.omgubuntu.co.uk
  /wp-content/uploads/2012/09/Screen-Shot-2012-09-19-at-10.34.18.png

  D. The Available and Away icons look bigger than the others.

  What you should see:

  A. All the icons, while beautiful, are robust enough to be thoroughly
  distinct against a white, light grey, or dark grey background.

  B. The icons remain simple enough that in emblem form they are
  thoroughly distinct against a bright blue, light grey, or dark grey
  background. If necessary, the envelope could have an emblem-shaped
  chunk bitten out of its bottom right corner, to make the emblem
  distinct.

  C. The Invisible icons and emblems have a transparent interior.

  D. All the chat status icons look the same size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1056488/+subscriptions

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


[Desktop-packages] [Bug 1056381] Re: [FFe: spice] error on x startup

2012-10-03 Thread Michael Casadevall
I've granted a FFE on this. I've reviewed the code changes in all the
packages, and is fairly low and the current amount of breakage is quite
high. In review of the code,  given the vast majority of code merely
adds new enums and structs I believe risk of regression is acceptable.

Packages released from the queue.

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

Title:
  [FFe: spice] error on x startup

Status in “spice” package in Ubuntu:
  Fix Released
Status in “spice-protocol” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-video-qxl” package in Ubuntu:
  Fix Released

Bug description:
  FFe:

  New upstream versions needed for spice to work with quantal. Serge
  tested and reported (on irc) that the new versions work and fixed the
  original bug.

  --

  When installing a new quantal VM from the desktop iso, (or when
  selecting 'Try ubuntu' from that iso), when x starts up it crashes and
  the X low resolution failsafe dialog comes up.

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

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


[Desktop-packages] [Bug 1056488] Re: [UIFe] Messaging menu title icons are indistinct

2012-10-02 Thread Michael Casadevall
Approved through the queue.

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

Title:
  [UIFe] Messaging menu title icons are indistinct

Status in “ubuntu-mono” package in Ubuntu:
  Fix Released
Status in “ubuntu-mono” source package in Quantal:
  Fix Released

Bug description:
  ubuntu-mono 0.0.45, Ubuntu Q

  1. gthumb /usr/share/icons/Humanity/status/*/user-* /usr/share/icons
  /ubuntu-mono-*/status/*/indicator-messages-*

  What you see:

  A. Humanity's standalone IM status icons are a bit hard to see against
  a white background -- such as Empathy's status menu -- because the
  tops of the icons are white with no outline.

  B. The corresponding emblems are similarly hard to see against the
  light grey, black, or blue envelopes in Ubuntu Mono's messaging menu
  icons. http://cloudfront.omgubuntu.co.uk/wp-content/uploads/2012/08
  /new-icons.jpg The Offline and mixed-status icons are particularly
  bad.

  C. The Invisible icons and emblems have a pure black or white
  interior, which just looks weird. http://cloudfront.omgubuntu.co.uk
  /wp-content/uploads/2012/09/Screen-Shot-2012-09-19-at-10.34.18.png

  D. The Available and Away icons look bigger than the others.

  What you should see:

  A. All the icons, while beautiful, are robust enough to be thoroughly
  distinct against a white, light grey, or dark grey background.

  B. The icons remain simple enough that in emblem form they are
  thoroughly distinct against a bright blue, light grey, or dark grey
  background. If necessary, the envelope could have an emblem-shaped
  chunk bitten out of its bottom right corner, to make the emblem
  distinct.

  C. The Invisible icons and emblems have a transparent interior.

  D. All the chat status icons look the same size.

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

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


[Desktop-packages] [Bug 1036856] Re: Unable to transfer files over bluetooth from an Android device using Nautilus

2012-09-24 Thread Michael Casadevall
Not sure this is valid. Most Android devices don'tsupport OBEX out of
the box. When I installed an OBEX server on the phone such as Bluetooth
File Transfer from the app store, this seems to work.

Marking incomplete.

** Changed in: bluez (Ubuntu)
   Status: Confirmed = Incomplete

** Changed in: gvfs (Ubuntu)
   Status: New = Incomplete

** Changed in: nautilus (Ubuntu)
   Status: New = Incomplete

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

Title:
  Unable to transfer files over bluetooth from an Android device using
  Nautilus

Status in “bluez” package in Ubuntu:
  Incomplete
Status in “gvfs” package in Ubuntu:
  Incomplete
Status in “nautilus” package in Ubuntu:
  Incomplete

Bug description:
  
  Transferring files from many Android devices fail using Nautilus.  Command 
line obexftp utilities work.

  I'm not sure if this is an issue with gvfs, nautilus, or bluez.

  Steps:
  1. log into desktop
  2. pair phone with laptop
  3. click bluetooth applet and select browse files on device
  4. copy file from harddrive in nautilus and paste it in phone in nautilus

  Expected results: file is transfered

  Actual results: files is not transfered

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

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


[Desktop-packages] [Bug 408903] Re: Does not handle microphone mute button (KEY_MICMUTE)

2012-09-24 Thread Michael Casadevall
** Also affects: udev (Ubuntu R-series)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-input-evdev (Ubuntu R-series)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu R-series)
   Importance: Undecided
   Status: New

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

Title:
  Does not handle microphone mute button (KEY_MICMUTE)

Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “udev” package in Ubuntu:
  Fix Released
Status in “xserver-xorg-input-evdev” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in r-series:
  New
Status in “udev” source package in r-series:
  New
Status in “xserver-xorg-input-evdev” source package in r-series:
  New

Bug description:
  Ubuntu 9.04

  Pressing the new microphone mute button does not do anything.  It
  should toggle the mute on the current capture device and toggle an led
  that is part of the button.

  acpi_listen output:

  ibm/hotkey HKEY 0080 101b

  
  xev output:

  MappingNotify event, serial 34, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248  

  MappingNotify event, serial 34, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 247

  KeyPress event, serial 34, synthetic NO, window 0x341,
  root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 34, synthetic NO, window 0x341,
  root 0x118, subw 0x0, time 10334714, (317,-162), root:(322,207),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

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

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


[Desktop-packages] [Bug 900636] Re: libreoffice ftbfs on armhf

2012-01-10 Thread Michael Casadevall
** Changed in: libreoffice (Ubuntu Precise)
 Assignee: Björn Michaelsen (bjoern-michaelsen) = Michael Casadevall 
(mcasadevall)

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

Title:
  libreoffice ftbfs on armhf

Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “libreoffice” source package in Precise:
  Confirmed

Bug description:
  in precise,

  /bin/bash: line 1: 11191 Segmentation fault  
LD_LIBRARY_PATH=/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/bin/uno
 -ro uno_services.rdb -ro uno_types.rdb -s com.sun.star.test.bridge.BridgeTest 
-- com.sun.star.test.bridge.CppTestObject
  dmake:  Error code 139, while making 'runtest'
  Retrying 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/testtools/source/bridgetest

  Making:all_bridgetest.dpslo
  cd ../../unxlngr.pro/lib  :  
LD_LIBRARY_PATH=/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/bin/uno
 \
  -ro uno_services.rdb -ro uno_types.rdb \
  -s com.sun.star.test.bridge.BridgeTest -- \
  com.sun.star.test.bridge.CppTestObject
  /bin/bash: line 1: 11210 Segmentation fault  
LD_LIBRARY_PATH=/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/bin/uno
 -ro uno_services.rdb -ro uno_types.rdb -s com.sun.star.test.bridge.BridgeTest 
-- com.sun.star.test.bridge.CppTestObject
  dmake:  Error code 139, while making 'runtest'

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

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


[Desktop-packages] [Bug 900636] Re: libreoffice ftbfs on armhf

2012-01-05 Thread Michael Casadevall
This is going to be a non-trivial porting project due to libreoffice
needing to know a massive *ton* about how the C++ calling conventions on
a given platform work.

Here's a general idea of what it took to build libreoffice (partially)
on Windows x64 which explains the broken module:
http://libreofficeaustralia.org/pa/community/blog/planet/20110328
/porting-libreoffice-x64-windows

I'm reading through the ARM calling convention guide and using libffi's
source as a handy reference guide, and will take a stab at doing the
port, but its absolutely suck and pain.

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

Title:
  libreoffice ftbfs on armhf

Status in “libreoffice” package in Ubuntu:
  Confirmed
Status in “libreoffice” source package in Precise:
  Confirmed

Bug description:
  in precise,

  /bin/bash: line 1: 11191 Segmentation fault  
LD_LIBRARY_PATH=/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/bin/uno
 -ro uno_services.rdb -ro uno_types.rdb -s com.sun.star.test.bridge.BridgeTest 
-- com.sun.star.test.bridge.CppTestObject
  dmake:  Error code 139, while making 'runtest'
  Retrying 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/testtools/source/bridgetest

  Making:all_bridgetest.dpslo
  cd ../../unxlngr.pro/lib  :  
LD_LIBRARY_PATH=/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/bin/uno
 \
  -ro uno_services.rdb -ro uno_types.rdb \
  -s com.sun.star.test.bridge.BridgeTest -- \
  com.sun.star.test.bridge.CppTestObject
  /bin/bash: line 1: 11210 Segmentation fault  
LD_LIBRARY_PATH=/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
 
/build/buildd/libreoffice-3.4.4/libreoffice-build/build/libreoffice-3.4.3.2/solver/340/unxlngr.pro/bin/uno
 -ro uno_services.rdb -ro uno_types.rdb -s com.sun.star.test.bridge.BridgeTest 
-- com.sun.star.test.bridge.CppTestObject
  dmake:  Error code 139, while making 'runtest'

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

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