** Changed in: easystroke (Ubuntu)
Assignee: Tom Jaeger (thjaeger) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1106922
Title:
editing actions no longer possible
To manage
** Patch added: make-event-argument-nullable.patch
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1106922/+attachment/3561211/+files/make-event-argument-nullable.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This should be fixed in git now; I've uploaded a rc for a new version to
the PPA, which is getting built right now (i386) / should be built in a
few hours (amd64). Please test, the fix needs to get in before beta
freeze on Thursday.
https://launchpad.net/~easystroke/+archive/ppa/+packages
**
** Attachment added: dsc file
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1106922/+attachment/3553326/+files/easystroke_0.5.99.2-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: easystroke_0.5.99.2.orig.tar.gz
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1106922/+attachment/3553329/+files/easystroke_0.5.99.2.orig.tar.gz
** Description changed:
+ This is a pretty serious issue, it basically prevents new actions from
+ being defined
** Attachment added: easystroke_0.5.99.2-0ubuntu1.debian.tar.gz
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1106922/+attachment/3553327/+files/easystroke_0.5.99.2-0ubuntu1.debian.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for testing. I don't see any reason why i386 should be any
different from amd64 in this respect, so I'll try to get the fixed
sponsered now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: easystroke (Ubuntu)
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/1106922
Title:
Impossible to set keys with movments
To manage notifications about
investigate. Importance should be set to 'High'.
** Changed in: easystroke (Ubuntu)
Assignee: (unassigned) = Tom Jaeger (thjaeger)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1106922
Title
** Bug watch added: Xiph.org Trac #1251
http://trac.xiph.org/ticket/1251
** Also affects: vorbis via
http://trac.xiph.org/ticket/1251
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's a backtrace from when the options get reset, but I can't quite
make sense of it. It looks like compiz gets notified that the gsettings
key 'org.compiz.core close-window-key' (which I can't find in dconf-
editor!) got changed. As a response to that it sets
'org.gnome.desktop.wm.keybindings
Isn't this one itself a dup of bug 986208? In any case, here's a stack
trace.
** Attachment added: stack trace
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1063617/+attachment/3431101/+files/compiz.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 986208 ***
https://bugs.launchpad.net/bugs/986208
** This bug has been marked a duplicate of bug 986208
Compiz does not remember user preferences upon system restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't think gsettings-data-convert was the cause of this bug (still
there is no reason to run it on every login). This appears to be
compiz' fault, and should probably be a dup of one of the following two
bugs:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1063617
This appears to be the fault of gsettings-data-convert. Deleting
/etc/xdg/autostart/gsettings-data-convert.desktop fixes this issue for
me.
** Also affects: gconf2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
** Branch linked: lp:~thjaeger/indicator-datetime/bugfixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069177
Title:
Bogus insensitive events after clicking on different date
To manage
** Branch linked: lp:~thjaeger/indicator-datetime/bugfixes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1000182
Title:
indicator-datetime shows all-day events one day too early
To manage
Trivial fix. Is indicator-datetime still being maintained?
** Patch added: fix
https://bugs.launchpad.net/indicator-datetime/+bug/1000182/+attachment/3408245/+files/lp1000182.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This should be fixed in 0.5.6.
** Changed in: easystroke (Ubuntu)
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/995841
Title:
Exceptions don't work
To
Is this still an issue in quantal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798552
Title:
Easystroke don't identify my touchscreen moves
To manage notifications about this bug go to:
Closing since 0.4.x is not supported any longer.
** Changed in: easystroke (Ubuntu)
Status: Confirmed = 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/480807
Title:
easystroke
** Changed in: easystroke (Ubuntu)
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/749403
Title:
Compiz Effect doesn't display in gesture
To manage
Closing, since it pertains to an old version of easystroke (the gesture
handling code has been mostly rewritten since then).
** Changed in: easystroke (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Closing. If this is still an issue on 0.5.6 please reopen.
** Changed in: easystroke (Ubuntu)
Status: Triaged = 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/356504
Title:
Public bug reported:
The events indicator-datetime shows below the calendar depends on the
selected date. When a new date is selected that has fewer associated
events than the current date, some of the old events remain in the list,
but are shown as insensitive rather than deleted. If for
** Patch added: fix
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1069177/+attachment/3406468/+files/1069177.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069177
The call to hide_all_appointments in day_selected_cb should probably be
removed as well to prevent ugly flickering, but I don't know if that has
any unintended side effects.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bulk of this needs to be done in ido, but it doesn't seem
complicated. And support for marking days that are not in the current
month could be added at the same time.
** Also affects: ido
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: ido
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/876167
Title:
calendar applet no longer grays out days for months other than current
To manage
Sorry, no changes are necessary in ido, since this can be implemented in
the theme. Adding the following to '/usr/share/themes/Ambiance/gtk-3.0
/gtk-widgets.css' or '/usr/share/themes/Radiance/gtk-3.0/gtk-
widgets.css' fixes the issue for me.
.menuitem GtkCalendar:inconsistent {
color: shade
Public bug reported:
If another client already has a touch grab on the root window, libgeis
crashes, taking unity down in the process.
To reproduce, compile the attached program, and then add it to the
startup applications. The command should be '/path/to/touchgrab 2 0
reject'. Then log out
The original plan was to release 0.6.0 with touch support (including a
fix for this issue) shortly after 0.5.6. But it turns out that touch
support in the X server isn't as mature as one would hope, and I'm
currently working on identifying what the issues are. So it'll probably
be a while before
Thanks for testing!
** Changed in: xorg-server (Ubuntu)
Status: New = Invalid
** Changed in: easystroke (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You can use the dash or command line to bring the configuration window
and then either add it to the dock or define a gesture to bring up the
configuration window again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking as invalid since launchpad doesn't allow me to do Won't fix.
** Changed in: easystroke (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059807
Title:
Can you check if this is still an issue with 0.5.6?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048865
Title:
The focus randomly changes between windows if easystroke is in use and
the evdev
Who decided not to update gnome-settings-daemon with the rest of gnome?
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The new interface was introduced in
9b12bfdd245867f928651bc5414cba67a3f84169, but it doesn't revert -- not
even close. I think going back to 3.4.1 makes the most sense at this
point, since it doesn't look like bug #1008840 is getting addressed for
quantal.
--
You received this bug notification
Looks like this is the patch that we need:
commit 4e7b7337e41b84b3fc3928f7b7a1909b49c125f8
Author: Ping Cheng pingli...@gmail.com
Date: Tue Jun 12 00:14:12 2012 -0700
Input: wacom - rearrange type enum
So we can simplify a few type related if statements
Signed-off-by:
Sorry, the id of the commit is ea2e60244573a9204c8cee9b4fb181106784c617.
(I rebased all the wacom patches in the range v3.5..v3.6-rc1 on top of
v3.5 and then bisected, which obviously changed the commit ids)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
The taskbar entry of the active application looks funny; a similar thing
happens when hovering over any entry. See the screenshot for details.
** Affects: light-themes (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
** Attachment added: bad.png
https://bugs.launchpad.net/bugs/1055376/+attachment/3337248/+files/bad.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1055376
Title:
gnome-panel not rendered
I stumbled on a solution purely by accident, I have no idea why it works
or if it is the correct solution, but here it goes.
** Patch added: debdiff that fixes the bug
** Attachment added: screenshot after applying the patch
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1055376/+attachment/3337251/+files/good.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks, so it turns out that the X server doesn't emit raw events for
touch events. Kind of makes sense.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001429
Title:
scroll doesn't work with my
Seems like this is the X server's fault, which doesn't generate
EnterNotify events on touch input.
** Changed in: mtdev
Status: New = Invalid
** Changed in: evdev
Status: New = Invalid
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You
** Changed in: easystroke (Ubuntu)
Status: Triaged = 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/966714
Title:
Spanish typo
To manage notifications about this bug go to:
This should be fixed in git now, please reopen if it's still an issue.
** Changed in: easystroke (Ubuntu)
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/908222
My guess would be that utouch interferes with easystroke. I can't test
this, though since the wacom driver does not send multitouch events to
the X server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I fixed this a while ago. Please reopen if it is still an issue
(note that you also need to enable the compiz dbus plugin).
** Changed in: easystroke (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 741869 ***
https://bugs.launchpad.net/bugs/741869
** This bug has been marked a duplicate of bug 741869
Unity/compiz intercepts Super and Alt keypresses from grabbed windows like
VMs.
--
You received this bug notification because you are a member of
Can you attach the output of 'easystroke -v' when attempting the
scroll gesture?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001429
Title:
scroll doesn't work with my touchscreen
To manage
This should have been fixed a long time ago, is this still an issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781856
Title:
does not start when config dir is a symlink
To manage notifications
@mpt: Please at least fix the bug mentioned in comment #7. (Trivial)
patch is attached.
** Patch added: messaging-menu-case.debdiff
https://bugs.launchpad.net/indicator-messages/+bug/957922/+attachment/3206217/+files/messaging-menu-case.debdiff
--
You received this bug notification
Chris,
The message is addressed directly to the recipient (eg, not CC) AND the
message is not low prioirty AND the message wasn't automated AND the
message is not from a mailing list
It appears that this check is case-sensitive, so the envelope won't turn
blue if the email address (as entered by
In case anybody needs to bring DVD+RWs back to life after brasero is
done with them, i figured out after much experimentation that the
sequence of the following two commands will work:
sudo dvd+rw-format -force /dev/cdrw
sudo dvd+rw-format -lead-out /dev/cdrw
--
You received this bug
I don't understand why, but this apparently is how unity reacts to
shortcuts emitted through XTest; xte exhibits the same behavior:
xte 'keydown Super_L' 'key Right' 'keyup Super_L'
So there is probably nothing I can do in easystroke to fix this.
--
You received this bug notification because
I got my X220t yesterday, but I can't reproduce this problem. Can you
attach the output of easystroke -v when you're trying to record
the gesture.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the debugging output. Everything seems to be working as intended in
those examples (although I admittedly did a horrible job of documenting how
things are supposed to work). Instant Gestures trigger the moment the button
is pressed. This is primarily for mice that have lots of
I think what you're experiencing is bug #788980.
On 06/03/2011 03:50 AM, teixeiras wrote:
Hello everyone:
My problem is more hw specific ones. My notepad ( acer 1425 pt ) have
hid-multitouch device, more concretely an hid-cando touchscreen monitor. On
10.10 was working just fine.
It works
** Also affects: xorg-server (Ubuntu)
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/757972
Title:
Easystroke doesn't recognize button release
--
Thanks for your bug report. This looks to be a bug introduced in the
latest xserver update: the new server does not seem to handle XI2 SD
button grabs correctly anymore. I'll forward the issue upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch added: freedesktop.org Bugzilla #36146
http://bugs.freedesktop.org/show_bug.cgi?id=36146
** Also affects: easystroke via
http://bugs.freedesktop.org/show_bug.cgi?id=36146
Importance: Unknown
Status: Unknown
** Project changed: easystroke = xorg-server
--
You
*** This bug is a duplicate of bug 731146 ***
https://bugs.launchpad.net/bugs/731146
On 03/14/2011 05:24 AM, Didier Roche wrote:
Thanks Tom for your bug report and your proposed patch.
The issue with your autohide fade-progress implementation is that for a
y given position, moving the
*** This bug is a duplicate of bug 731146 ***
https://bugs.launchpad.net/bugs/731146
On 03/14/2011 02:30 PM, Didier Roche wrote:
*** This bug is a duplicate of bug 731146 ***
https://bugs.launchpad.net/bugs/731146
@Tom: hum, I don't see how it exists in the current code. I'm
:03 AM, Tom Jaeger 695...@bugs.launchpad.net
wrote:
How is one supposed to raise a window then when 'click to raise' is
disabled if not by clicking on the title bar or by doing Alt+Click?
When click raise is disabled raise happens on a timeout. The way the
options works is confusing though, I
This bug has not been fixed. Alt+Click should raise the window
unconditionally (just like clicking on the title bar does), irrespective
of what 'raise-on-click' is set too. This was also the behavior of
compiz-0.8. Patch is attached, please reopen.
** Patch added:
How is one supposed to raise a window then when 'click to raise' is
disabled if not by clicking on the title bar or by doing Alt+Click?
On 03/11/2011 09:48 PM, Sam SmSpillaz Spilsbury wrote:
On Sat, Mar 12, 2011 at 5:39 AM, Tom Jaeger 695...@bugs.launchpad.net wrote:
This bug has not been fixed
At the very least, I'd need a stack trace, but issues like this are hard
to debug without a reproducible test case.
On 02/17/2011 12:17 AM, The Compiler wrote:
Just happened to me as well, with Ubuntu 11.04 with a custom kernel based on
the Zen kernel (2.6.37-zen).
seems randomly, hasn't
Just the samba package... The rest of the system is fine.
On 11/13/2010 08:45 AM, Jack wrote:
ok! it works!
Back to Ubuntu.
By the way Tom, when you're saying (...)installing them will prevent
future automatic updates, what do you mean precisely? you're talking
about samba package or no
Just the samba package... The rest of the system is fine.
On 11/13/2010 08:45 AM, Jack wrote:
ok! it works!
Back to Ubuntu.
By the way Tom, when you're saying (...)installing them will prevent
future automatic updates, what do you mean precisely? you're talking
about samba package or no
I can confirm that this is a samba problem: Downgrading to samba
version 3.4.7 from lucid fixed the issue for me. I've uploaded a
downgraded samba package to my PPA (but be warned, I bumped the epoch on
those, so installing them will prevent future automatic updates):
I can confirm that this is a samba problem: Downgrading to samba
version 3.4.7 from lucid fixed the issue for me. I've uploaded a
downgraded samba package to my PPA (but be warned, I bumped the epoch on
those, so installing them will prevent future automatic updates):
Public bug reported:
Binary package hint: easystroke
This is just a bugfix release and the difference to 0.5.3 is small:
git diff --stat 0.5.3 0.5.4 -- *.h *.cc
actions.cc | 11 ---
grabber.cc |7 ---
grabber.h |1 -
main.cc| 23 ---
stats.cc
easystroke (0.5.4-0ubuntu1) maverick; urgency=low
* New upstream release (LP: #623955)
-- Thomas Jaeger thjae...@gmail.com Wed, 25 Aug 2010 14:38:25 +0200
** Attachment added: easystroke_0.5.4.orig.tar.gz
Just to be clear, we're letting this usability nightmare go on for
another release, correct?
On 08/18/2010 10:46 PM, Pedro Villavicencio wrote:
Please do not change the status of the reports without adding a comment.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Triaged
Thanks for uploading the package. fprint is just as dead upstream as
thinkfinger, and in addition does not allow the user to chose between
fingerprint and password authentication, so it's not a viable
alternative at this point.
On 07/27/2010 05:53 AM, Fabrice Coutadeur wrote:
Hi,
For your
maverick ships a 1.8 xserver, so this problem is fixed now.
** Tags removed: hardy maverick
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Fix Released
--
log spam when detaching a slave device
https://bugs.launchpad.net/bugs/566375
You received this bug notification because
** Patch added: thinkfinger.debdiff
http://launchpadlibrarian.net/52418704/thinkfinger.debdiff
--
Intrepid regression: carriage-return required after finger scan
https://bugs.launchpad.net/bugs/256429
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: thinkfinger (Ubuntu)
Status: Fix Released = Confirmed
--
Intrepid regression: carriage-return required after finger scan
https://bugs.launchpad.net/bugs/256429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The mozilla foundation does not allow the use of the firefox name and
logo when shipping a modified version of firefox, so this is both
expected and unavoidable.
On 06/30/2010 08:44 PM, NoBugs! wrote:
I noticed when Firefox updated to the normal version, it was called Firefox.
Then when it
Public bug reported:
Looks like Ron's incorrect udev rules have crept in again from debian.
Also, it doesn't seem like we're shipping a wacom config with the
xserver-xorg-core package. There's a package that fixes these things
(they're just backports from 0.10.5) in my PPA:
On 05/09/2010 01:17 PM, John D Lamb wrote:
I’ve been trying to configure an antique Wacom serial tablet I got in
the lower oölitic silurian. This one gets its power from the PS/2 mouse
or keyboard socket and transfers data through the serial port. First:
Now /var/log/Xorg.0.log gives (for
This issue is specific to the new xf86-input-wacom driver, so it was
only ever an issue on lucid, and it still is. I don't know of any fix,
though.
On 05/14/2010 10:24 AM, Bryce Harrington wrote:
[This is an automatic notification.]
Hi Tom,
This bug was reported against an earlier version
** Bug watch added: Debian Bug tracker #582308
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582308
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582308
Importance: Unknown
Status: Unknown
--
[needs packaging] mango lassi
** Tags added: lucid
** Tags removed: hardy needs-retested-on-lucid-by-june
--
log spam when detaching a slave device
https://bugs.launchpad.net/bugs/566375
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Please don't hijack this bug report. This bug is about the removal of
the battery percentage info from g-p-m, not about the way this
information is presented. If you want to argue tooltips vs. indicator
menus, please do so in bug #527458.
On 05/11/2010 03:24 PM, Alexander Fomichev wrote:
** Summary changed:
- current battery charge not easily accessable
+ current battery charge not easily accessible
--
current battery charge not easily accessible
https://bugs.launchpad.net/bugs/539912
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On 05/05/2010 04:52 PM, Bryce Harrington wrote:
[This is an automatic notification.]
Hi Tom,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Sorry if this wasn't clear before, the bug is specific to xserver-1.7,
so it was originally
*** This bug is a duplicate of bug 539912 ***
https://bugs.launchpad.net/bugs/539912
** This bug has been marked a duplicate of bug 539912
[lucid] current battery charge not easily accessable
--
Battery indicator doesn't show percentage
https://bugs.launchpad.net/bugs/573460
You received
On 04/27/2010 04:33 PM, Frederik Elwert wrote:
As others, I’m not against change in the systray thing. And I don’t want
to complain about a change just because it is a change. I just request
answers to these simple questions:
1. How do I know the current charging (percentage) of my laptop
** Changed in: xulrunner
Importance: Unknown = Undecided
** Changed in: xulrunner
Status: Confirmed = New
** Changed in: xulrunner
Remote watch: Mozilla Bugzilla #468496 = None
** Changed in: xulrunner
Status: New = Invalid
** Changed in: firefox (Ubuntu)
Status:
This a hardware independent issue, so I'm not sure why an lspci-vvnn
would be needed, but I'll attach it anyway.
On 04/19/2010 08:08 AM, Bryce Harrington wrote:
Hi Tom,
Please run the command 'apport-collect BUGNUMBER', which will attach several
files we need for debugging.
[This is an
There is still the issue of the actual error message, which certainly
shouldn't appear on the user's screen. Is this bug tracked anywhere?
On 04/18/2010 06:09 PM, Steve Langasek wrote:
The getpwuid_r() message is a generic warning that is displayed for all
users, but is usually hidden by the
For those looking for a one-click solution, I've recently updated the
'wacomrotate' package in my tablet ppa to lucid:
https://launchpad.net/~thjaeger/+archive/tabletpc
--
Rotate Screen in TabletPC stylus and pointer mouse not coincidence
https://bugs.launchpad.net/bugs/217182
You received this
Public bug reported:
Each time a slave device gets detached, the server logs the following
messages:
[mi] miSpriteRealizeCursor called for floating device.
[mi] miSpriteSetCursor called for floating device.
[mi] miSpriteSetCursor called for floating device.
[mi] miSpriteRealizeCursor called for
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
window controls don't scale up
https://bugs.launchpad.net/bugs/532641
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Metacity/gnome-window-decorator supports .svg, so this is entirely
possible. Besides, having blurry buttons is still better than having
tiny buttons that are next to impossible to click.
On 04/07/2010 08:08 AM, Kenneth Wimer wrote:
As long as there is blurriness the bug still exsits. I don't
Here's a proof of concept.
On 04/05/2010 05:29 PM, Kenneth Wimer wrote:
Ideally things would be able to scale up but currently this is not
possible
** Changed in: light-themes (Ubuntu)
Importance: Medium = Wishlist
** Attachment added: scaling.png
Could you elaborate on what the issue is here exactly? I did some
preliminary testing (see above), and the buttons scaled up fine (modulo
blurriness).
On 04/05/2010 05:29 PM, Kenneth Wimer wrote:
Ideally things would be able to scale up but currently this is not
possible
** Changed in:
1 - 100 of 524 matches
Mail list logo
