Fix for onboard had been released with version 0.96.
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788514
Title:
python packages
Fixed in the 0.96 branch.
** Changed in: onboard
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/897678
Title:
onBoard shifts after changing Language Layout
Hi thanks for the report, that was helpful. The stretching the window
part was the key to get the move button off-screen. I'll look into it.
** Changed in: onboard (Ubuntu)
Status: New => Confirmed
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
We're preparing a bug fix release 0.96.2 for Oneiric and Precise
including this fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891931
Title:
Onboard should provide an accessible description for
I believe your first problem in fixed too now. There are timed thresholds
before resizing and moving the keyboard window and the floating icon.
This will probably be available for testing in a PPA before the next release.
We'll let you know when it is ready.
** Changed in: onboard
Status
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/893644
Title:
Onboard got r
Hi, thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have pushed a fix for your second issue, the icon palette being resized by
the grid plugin.
Until that arrives you could perhaps try to disable the grid plugin in
CompizConfig Settings manager (ccsm).
I'll
Thanks Luke, I've added a fix to trunk.
** Changed in: onboard
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891931
Title:
Onboard should provide an access
** Changed in: onboard
Status: New => Confirmed
** Changed in: onboard
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/891931
Title:
Onboard should provide a
** Also affects: onboard
Importance: Undecided
Status: New
** Changed in: onboard
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885608
Title:
if you ma
** Changed in: onboard
Status: New => Confirmed
** Changed in: onboard
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/626064
Title:
onboard: add haptic feedbac
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801208
Title:
should use gsettings rather than gconf
To manage notifications about
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/68716
Title:
Caps Lock not sticky enough
To manage notifications about this bug go
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/857813
Title:
onboard doesn't show on lock screen in 11.10 beta 2
To manage notific
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/643204
Title:
Transparency all the time
To manage notifications about this bug go t
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801203
Title:
Should use gobject introspection (GTK3)
To manage notifications about
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/564040
Title:
RFE: Add a big hide button
To manage notifications about this bug go
** Changed in: onboard
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/584119
Title:
PATCH: close button + tray icon
To manage notifications about this bu
Looks good to me, I think it's ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880085
Title:
SRU oneiric: New release available: version 0.96.1
To manage notifications about this bug go to:
ht
Works as intended on my fresh install. The toggle in preferences does
turn it on and off in the unlock screen. Also Onboard shows up there
right after its first launch.
Once it's in there, it doesn't go away on its own though. It's still in
the lock screen when I turn off the osk in universal acce
Runs ok now, preferences on the live cd does indeed show up. Although it
can't be launched from everywhere:
- desktop shortcut: yes
- command line: yes
- layout button: no
- status menu: no
However, as a result of the discussion with Francesco, this is probably
the best we can do as long the live
Appears fixed, I haven't seen this issue since the commit and there was
nothing wrong with the corners today during testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877604
Title:
Black window
Looks good. I've logged into unity-2d a halve dozen times with a reset
schema, and the autostarted onboard always came up fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877601
Title:
Theme is s
Confirming too. I've tested my freshly updated Oneiric installs and the layout
switches are still occurring for Onboard and kvkbd.
Other distributions appear to be affected too, I've seen this happening with
Onboard on Mandriva 2011 (under KDE) recently.
--
You received this bug notification be
Thanks Sergey, I've added that plus a toggle in preferences. Sticky
state is enabled by default for now.
** Changed in: onboard
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
> I leave the bug open because the situation might be improved.
Francesco, did you have anything specific in mind back then? I could be wrong,
but IMO an additional preferences button would just slow the scanning down,
while not really helping either, since preferences aren't scanable.
--
You r
Fixed in trunk (I believe). It should be harder to push the move button off the
display edges, even partially. If this somehow still happens, the button is
brought back into view on resize, hide and restart.
Tested in unity, unity-2d, gnome-shell and gnome classic.
** Changed in: onboard (Ubunt
Another solution may be to have a gsettings vendor override file for
gnome-screen-saver. That way Onboard wouldn't need to run once to have
lock screen working. I don't believe this should be installed by Onboard
though, pretty sure not by the upstream version and probably neither
with an Ubuntu p
The keys are in gsettings, at org.gnome.desktop.screensaver. To have Onboard
show up when unlocking the screen they need to be set to
embedded-keyboard-command = 'onboard --xid'
embedded-keyboard-enabled = True
The lightdm greeter (unity-greeter) has "onboard --xid" hard-coded into
the greeter c
Ah, VirtualBox, that could explain it, at least for the guests. If
Alt+click is intercepted by the host's window manager, VirtualBox guests
don't get to see those events. You would have to make sure that both WMs
use different mouse_modifiers.
For example, keep the guests at the default and on th
I wonder what's grabbing the Alt key there. I've tried, but wasn't able
to break Alt-drag. Some more ideas:
Alt+ opens the window menu, which has an unmaximize option
Alt+Shift+ moves the window to snapped positions
Alt+ moves the window (for completeness, not new)
If none work and you haven't do
@Rocko, it ought to work in unity-2d too. As I understand it, metacity
had that alt-left-click-drag thing long before compiz. I wonder if it
had been disabled at some point in the release cycle. Try this:
gconftool-2 -s /apps/metacity/general/mouse_button_modifier -t string
""
Does that enable it
> but the checkbox isn't selected by default to show on the lock screen
I've added this recently, should come with the bug fix release.
Onboard then silently sets those g-s-s keys on startup, but does so only if no
other osk has taken them before.
@Francesco, just in case, this needs xembed-onb
@Rocko, Alt-F4 does not work because Onboard needs to be unfocusable, i.e. it
calls set_accept_focus(False) for the main window.
However, Alt+Drag (with Alt held on a hardware keyboard) is definitely able to
unmaximize Onboard in unity and unity2D.
--
You received this bug notification because
Quang, there may be a workaround. If you are able to use a regular
keyboard, you could try to hold the Alt key there, click anywhere on
Onboard and drag it away from the top. This should snap it out of the
maximisation.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Upstream bug report at
https://bugzilla.gnome.org/show_bug.cgi?id=662241
** Bug watch added: GNOME Bug Tracker #662241
https://bugzilla.gnome.org/show_bug.cgi?id=662241
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Onboard main has a workaround, though now there is a new glib warning in
the console output (lp:878505).
** Changed in: onboard (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Causing this are unexpected gsettings change events, coming in after
onboard's initialization is done. Some events of keys onboard touches
are expected on first start, but here each and every one onboard
subscribes too is fired.
This happens rather frequently when first-time auto-starting onboard
Here is a minimal python sample. The output is:
/usr/lib/python2.7/dist-packages/gi/types.py:43: Warning: g_value_get_boxed:
assertion `G_VALUE_HOLDS_BOXED (value)' failed
return info.invoke(*args, **kwargs)
[] 1
** Attachment added: "gio-test2"
https://bugs.launchpad.net/ubuntu/+source/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/878505
Title:
Gsettings "change-event" not fully introspectable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
Public bug reported:
The current parameters of the call-back for Gio.Settings."change-event" appear
to be
(settings, keys, n_keys), where keys is always empty.
I believe they are meant to be
(settings, keys), with "keys" actually containing the list of changes keys.
There is also this assert,
Alan's lp:877385 should be fixed, but some more issues came up when I tested on
live CD and a fresh install:
There are lp:877592, lp:877604 with committed fixes, but lp:877601 needs more
investigation, could be a gsettings problem.
--
You received this bug notification because you are a member
Public bug reported:
When onboard is auto-started in the unity session, compositing is unavailable
at first, but comes back on seconds later.
Transparency isn't initialised correctly and black corners remain around the
window.
** Affects: onboard (Ubuntu)
Importance: Undecided
Sta
Public bug reported:
Sometimes on first start onboard's theme is partially reset, leaving it in a
visually unpleasant state. This corrects itself on the following start, but can
be repeated occasionally by resetting onboards gsettings schema with
gsettings reset-recursive apps.onboard.
** Affec
Public bug reported:
Onboard-settings silently fails to start on the live cd. The live CD has
RUNNING_UNDER_GDM defined in the user session, which was supposed to
block settings in GDM only.
Affects onboard 0.96.0-0ubuntu1
** Affects: onboard (Ubuntu)
Importance: Undecided
Status:
Removed the check in trunk.
** Changed in: onboard (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877592
Title:
onboard-settings fails to start on Oneiri
Oh, thanks Alan. Fixed in trunk.
** Changed in: onboard (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/877385
Title:
scanning layout has return mapped to
The switch to gsettings is done, no need to assign to this anymore
Abhishek.
** Changed in: onboard
Assignee: Abhishek kumar singh (abhishekkumarsingh-cse) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Seems so, unfortunately. The new features we planned where somewhat
time-consuming to add. The bulk is done by now, but there are a couple of bugs
left to fix.
Also there is https://bugs.launchpad.net/bugs/739812. I was hoping to get a fix
in for that too.
--
You received this bug notification
*** This bug is a duplicate of bug 858988 ***
https://bugs.launchpad.net/bugs/858988
** This bug has been marked a duplicate of bug 858988
onboard auto-starts by default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
I'm not sure what happens with onboard in GDM. As far as I know gnome-shell
will have a built-in on-screen keyboard and thus onboard might be replaced in
GDM too. Jeremy could probably tell you more about this.
If you still want to try, playing with or creating
/usr/share/gdm/autostart/LoginWind
I should have remembered. The keys to enable embedding in gnome-
screensaver have moved from gconf to gsettings. The gtk3 changes in
upstream take care of that, but the current release still sets them in
gconf.
Chadmerkert, as a workaround try running these in a terminal:
gsettings set org.gnome.
@Neil, comment #24, could you elaborate what you discussed with Sam and
Jason?
Francesco and me have been discussing this bug too and to us the window-
type DOCK approach (or alternatively marking onboard "override-
redirect") seems feasible. The main obstacle appears to be missing
window decorati
XEmbed mode is supposed to work in the current release. The gtk3 changes
aren't required yet, not for this bug at least. I'm looking into it.
** Changed in: onboard
Assignee: (unassigned) => marmuta (marmuta)
** Changed in: onboard
Importance: Undecided => Medium
--
Y
I have retested this with in gir1.2-gtk-3.0, 3.1.90-0ubuntu1 and found
it to be fixed.
** Changed in: gtk+3.0 (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: gtk+3.0 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: onboard
Status: New => Invalid
--
Yo
That would explain it. With focus-follows-mouse Onboard sends keystrokes
at best to itself.
I wonder if a simple XSetInputFocus() on the password entry would help.
"It causes keyboard input to go to the selected window regardless of the
position of the pointer. When the root window is selected, k
FWIW, here is a gdb backtrace with a break point set on
XkbSendLegacyMapNotify, probably the source of the MappingNotify event.
Apparently the keyboard device changes from physical to on-screen
keyboard and the two devices don't share the same keyboard map (?).
** Attachment added: "gdb.txt"
h
xev log of pressing the space bar once in Onboard and another time on an
USB keyboard. Note unexpected MappingNotify events before the two
KeyPress events.
** Attachment added: "xev.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/837456/+attachment/2333772/+files/xev.log
--
You rece
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/837456
Title:
[Oneiric] XTestFakeKeyEvent changes kayboard mapping to 'us'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
Public bug reported:
Typing with the onscreen keyboard Onboard on a system with German
default layout immediately switches the keyboard layout to 'English
(US)'. Touching any key on a physical keyboard switches back to the
German default. This can be repeated indefinitely.
Onboard uses XTestFakeK
Thank you for you bug report. I too suspect that this is a graphics
driver problem. In particular double buffering may be handled
incorrectly for some reason. If you are feeling adventurous you could
try disabling that in Onboard and live with flickering keys. Let me know
if you do and I'll tell yo
The switch to gtk3 and gobject introspection is done in trunk, thanks to
extensive patches by Gerd Kohlberger.
Two notes:
- https://bugs.launchpad.net/onboard/+bug/807473 (gtk_plug_get_id not
introspectable) currently prevents Onboard from being xembedded into
gnome-screen-saver.
- Cairo doesn
Switched to gsettings in trunk. No more dependency on gconf.
** Changed in: onboard
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/801208
Title:
should use gsetti
Upstream bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=654238
** Bug watch added: GNOME Bug Tracker #654238
https://bugzilla.gnome.org/show_bug.cgi?id=654238
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
** Also affects: onboard
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807473
Title:
gtk_plug_get_id not introspectable
To manage notifications about thi
Public bug reported:
Current gir1.2-gtk-3.0, 3.1.8-0ubuntu1 does not expose the get_id()
method of GtkPlug.
python -c 'from gi.repository import Gtk; Gtk.Plug().get_embedded();
Gtk.Plug().get_id()'
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'Plug' object has no att
This is not fixed in Oneirics version 6.0.2-0ubuntu1. The linked
bugzilla report seems to have stalled too.
As this bug report states, it is impossible to exchange data with programs
using E-notation (i.e. all programs I care for).
Also In it's current form entering numbers in scientific notation
Revision 248 breaks the package build for Onboard in Oneiric and
according to Francesco Fumanti also in Natty.
setup.py: error: no such option: --build-base
The reason is apparently, that importing certain files triggers Onboards own
command line processing, which obviously doesn't know or care
Onboard main has support for themes now. There is an Ambiance theme included
based on Alan Bells design. The system wide default theme can be specified in a
new configuration file onboard-defaults.conf (see sample file in the project
root).
Have a look and let me know if you want to see any chan
I was always using screen0 and
dbus-send --print-reply --dest=org.freedesktop.compiz
/org/freedesktop/compiz/obs/screen0/brightness_values
org.freedesktop.compiz.set array:int32:80
doesn't work. If no introspection, Is there any up-to-date documentation or
working examples?
--
You received t
Still happens in Natty. I can live with it though. My workaround is
having a launcher in another panel that does "sh -c "gconftool-2 -s -t
bool /apps/panel/toplevels/top_panel_screen0/auto_hide false;
gconftool-2 -s -t bool /apps/panel/toplevels/top_panel_screen0/auto_hide
true".
--
You received
Thanks for the bug report. I've pushed a fix to onboard main. The
message has been demoted to level "info", which hides it for the default
invocation.
** Changed in: onboard
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Changed in: onboard
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/768583
Title:
UIFe: Onboard (on-screen keyboard) does not use Ubuntu interface font
or
Same here, I used to set screen brightness with something like
dbus-send --print-reply --dest=org.freedesktop.compiz
/org/freedesktop/compiz-1/obs/screen0/brightness_values
org.freedesktop.compiz.set array:int32:80
that has no effect now.
Also the examples at http://wiki.compiz.org/Plugins/Dbus
Had the same symptoms and downgrading to libusb-0.1.4 fixed it here too
(HP 3330 MFP).
In Synaptic select package libusb-0.1.4, then the menu item
Package->Force Version, choose "2:0.1.12-14 (lucid)" and apply the
changes. After that reconnecting the printer was enough to make both
scanning and pr
I've pushed a workaround to onboard and virtkey trunks. Instead of
crashing on a missing X keyboard, onboard now waits until one becomes
available (if ever) and should generally react more dynamically to
keyboard and keyboard layout changes. Bug 548891 for vmware users seems
resolved, but the worka
I've tried it and it does work in principle. I did
gconftool-2 -s /desktop/gnome/peripherals/keyboard/general/disable_indicator -t
bool true
then logged out and back in and the layout indicator was gone.
However there is no schema for the key, it has to be created manually
and cannot be discov
The direct cause of the segfault appears to be a missing error exit in
python-virtkey.c. I don't have launchpad access to virtkey, so I'll
attach a tiny patch. However this doesn't fix the root cause, it only
shifts the error from a SIGSEGV to a python backtrace:
Traceback (most recent call last):
** Also affects: virtkey
Importance: Undecided
Status: New
--
onboard crashed with SIGSEGV in XkbGetNames()
https://bugs.launchpad.net/bugs/526791
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/42751653/Dependencies.txt
--
Make step size of mouse wheel volume control configurable
https://bugs.launchpad.net/bugs/553073
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
Binary package hint: indicator-sound
Since there are differing opinions on how fast or slow the mouse wheel
should adjust the volume, see Bug #551725, I suggest to make the step
size user configurable.
There already exists a gconf key for the keybord step size in
"/apps/gnom
Thanks for the explanation. I didn't have rhythmbox-ubuntuone-music-
store installed but I also didn't realize the rest of ubuntuone was
optional. As you suggested, libubuntuone-1.0-1 and python-ubuntuone can
be removed. ACK for invalid.
--
libubuntuone forces installation of ubuntuone-client-
"which displays automatically when you configure multiple keyboard layouts"
> Why is it bad?
I have multiple keyboard layouts setup all the time but I'm only occasionally
switching between them for example. There is no reason for me to have the
layout switcher cluttering up precious panel space.
Perhaps, but I haven't knowingly touched the Qt theme myself. Also I've
been using upstream Anki since and tooltips were fine there. When I
switched back and forth between repo- and upstream Anki the former's
tooltips where unreadable and the latter's were fine.
However for whatever reason that ch
** Attachment added: "anki_tooltips.jpg"
http://launchpadlibrarian.net/41966128/anki_tooltips.jpg
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41964665/Dependencies.txt
--
Anki's tooltips are unreadable with Lucid's light-themes
https://bugs.launchpad.net/bugs/547
Public bug reported:
Binary package hint: anki
Hi, Anki's tool-tips become unreadable with Ambiance and Radiance of
Lucid's light-themes package. Have a look at the screenshot.
I believe this is because Anki hard-codes the background color and this
doesn't go well with the white on black tool-ti
*** This bug is a duplicate of bug 544622 ***
https://bugs.launchpad.net/bugs/544622
Stuart, I don't see how this bug report is a duplicate of bug #544622, can you
explain?
This bug is about being able to choose not to have ubuntuone-client-gnome
installed, vs. download delays when using ubu
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41931861/Dependencies.txt
--
libubuntuone forces installation of ubuntuone-client-gnome
https://bugs.launchpad.net/bugs/546709
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
libubuntuone 0.2.101-0ubuntu2 adds a new depends on ubuntuone-client-
gnome which forces the installation of the client. ubuntu-desktop has
ubuntuone-client-gnome as recommends only, thus it used to be possible
to not install the client if one elected to do so. However with th
Ok, thanks, I'll do so then.
--
onboard has overactive dependencies
https://bugs.launchpad.net/bugs/524148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com
Hi Emmet, sorry for the delay.
> I suspect that for
> advanced hackers (not I) it would be possible to use the development
> headers to generate compiled python bindings and set the right
> dependencies at build time.
Turns out there are actually code generators for ctypes.
http://starship.python.
Yep, following the instructions it comes up enabled and working. Thanks, I
didn't know about indicator-sound-service.
At first it looked like "killall indicator-sound-service" alone would work too,
but on second try I ended up with everything added twice to the indicator menu,
i.e. two sets of v
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39609492/Dependencies.txt
--
Volume slider disabled
https://bugs.launchpad.net/bugs/526439
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: indicator-sound
Hi, the volume slider is disabled (grayed) on my system, probably
because pulseaudio fails to start on login (still investigating).
However even after starting pa manually the slider never becomes
enabled, in fact I have never seen it enab
An automated test-case for the CDLL-calls sounds like a good idea, if I
new how to do this, I would add it to trunk too.
I should have mentioned that in this case I am part of the upstream, the
ctypes piece in question was actually my (troublesome) contribution. You
found quite correctly that my i
Emmet, instead of patching X11.py on build, wouldn't it be preferable to
permanently modify the source to reference sonames instead of linker names?
I.e. changing libX11.so -> libX11.so.6 and libXi.so -> libXi.so.6 in X11.py.
That way running onboard from the project directory wouldn't require ha
Similar things happen here with gnome-terminal 2.29.1-0ubuntu3 when
switching themes. Only the the terminals background color seems affected
though. Switching from Human to DarkRoom gives a DarkRoom-brown
background color #4C4039, switching back to Human makes it an unreadable
(white text on) light
This seems fixed in lucid, didn't find any artifacts there.
--
[RV730] xorg-edgers: Mist of artifacts in highlight color over menus and buttons
https://bugs.launchpad.net/bugs/425303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
[RV730] xorg-edgers: Mist of artifacts in highlight color over menus and buttons
https://bugs.launchpad.net/bugs/425303
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
No change, still ugly in lucid.
--
weird looking gksu window for "password dialogs as normal windows"
https://bugs.launchpad.net/bugs/290714
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
401 - 500 of 657 matches
Mail list logo
