Public bug reported:
Switching back from the console or (more commonly) resuming from suspend
incurs a 5-second wait if there's a serial wacom device. The following
messages appear in Xorg.0.log:
(WW) Serial Wacom Tablet: Waited too long for answer (failed after 3 tries).
(WW) Serial Wacom
Here's an idea: Why not make the upper right hand corner of each window
an 'activity corner' in gnome 3?
On 04/01/2010 02:12 PM, Mark Shuttleworth wrote:
Our intent is to encourage innovation, discussion, and design with the
right of the window title bar. We have some ideas, and others are
On 03/30/2010 01:03 PM, Mirco Müller wrote:
The branch for fixing this in notify-osd I put up for review here:
https://code.edge.launchpad.net/~macslow/notify-
osd/fix-546650/+merge/22469
This keeps the changes within notify-osd. I don't fully understand why
only this works and the old way
I've attached a patch that adds the battery percentage when it is
useful. I've also built the package which is temporarily available in
my PPA:
https://launchpad.net/~thjaeger/+archive/ppa/+packages
** Attachment added: percentage.debdiff
Is this really true? I just replaced object_width/object_height by
width/height in my metacity-theme-1.xml file and then increased
button_width/button_height. The buttons scale up as expected. They are
are a little blurry, of course, but this wouldn't be an issue if they
were .svg files instead
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
--
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
Seconded. This makes the new theme very awkward to use on a
high-resolution display -- and I'm in my 20s.
On 03/18/2010 11:13 AM, jgv wrote:
Can you confirm this is a design decision and not a design flaw?
So the designers have made a specific decision to ignore the needs of
disabled Ubuntu
@asac:
Sorry it took me so long to reply, here's a little bit about the history
of the patch.
The subpixel patch that ubuntu is currently using was added to cairo
master during the 1.8.0 cycle, but then dropped shortly before the
release [1], essentially because of concerns over the test suite
@asac:
Sorry it took me so long to reply, here's a little bit about the history
of the patch.
The subpixel patch that ubuntu is currently using was added to cairo
master during the 1.8.0 cycle, but then dropped shortly before the
release [1], essentially because of concerns over the test suite
Please ignore the last comment, I meant to add it to bug #512615. Sorry
about the noise.
--
MASTER - FF 3.5 font hinting does not honour gnome-settings
https://bugs.launchpad.net/bugs/379761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
On 03/24/2010 01:13 PM, Pako wrote:
Oh, you made me cry
http://www.ubuntu.com/community/conduct
If you don't have anything nice (or meaningful) to say, don't say it.
This bug is already long enough.
--
[Master] Window Control buttons: position/order/alignment
On 03/22/2010 09:21 AM, Aigars Mahinovs wrote:
While you might the merfect mouse sharpshooter, keeping in mind the
needs of people with less precise mouse movements is also important -
the precision needed to hit these buttons on the left among all the
other control elements there is much
Public bug reported:
Binary package hint: gnome-power-manager
Ever since the gnome-power-manager icon transition from the notification
area to the indicator applet it is unnecessary complicated to find out
what the current battery charge percentage is. We used to be able to
just hover over the
Yeah, there's more obvious ways of shortening the menu text, like
writing 1:50 instead of 1 hour and 50 minutes or dropping Laptop
battery altogether.
On 03/16/2010 06:11 PM, Chris Coulson wrote:
We just removed the percentage from the menu deliberately, because the
menu was far too wide with
Martin, let me repeat my question from comment #126: Why not take care
of this now? What do you expect to happen between now and beta 2?
On 03/12/2010 09:03 AM, Martin Pitt wrote:
** Changed in: firefox (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-1 = ubuntu-10.04-beta-2
--
fonts are
Can you run
udevadm info --path=/sys/class/tty/ttyS0/ --attribute-walk
? I'll also attach my /etc/udev/rules.d/65-xorg-wacom.rules file for
reference.
On 03/03/2010 03:05 AM, michael.huettemann wrote:
After the update, now that the committed patch has arrived, it still
does not work. The
The only thing I can think of is that the new rules need to be added
before the KERNEL!=event[0-9]* or after the LABEL=wacom_end line,
since you only get an event device for USB tablets.
On 03/03/2010 04:46 AM, michael.huettemann wrote:
@Tom Jaeger
Bingo! Your /etc/udev/rules.d/65-xorg
On 03/02/2010 11:04 AM, Timo Aaltonen wrote:
I've got a lenovo X61 tablet, and 'udevadm info --export-db' shows WAC
only for some acpi device. 'cat /sys/class/tty/ttyS1/device/id' shows
WACf004 though, but since udev doesn't seem to know about the device, it
isn't initialized though I have the
Are you sure you're running a patched X server? The status of the bug
is still 'fix committed', so the package currently in lucid does not
contain the patch. What is the output of
cat /sys/class/tty/ttyS0/device/id
on your system?
On 03/01/2010 12:10 PM, michael.huettemann wrote:
On my
Sorry, I've been slow at uploading updated packages lately, partly
because I'm not running karmic anymore, so I don't notice when the
repository gets out of date. Anyway, it should work now until the next
update...
On 02/21/2010 08:13 PM, NoBugs! wrote:
The latest Firefox security update broke
Public bug reported:
Binary package hint: indicator-applet
The items in the indicator applet are much farther apart then anything
else in the gnome panel. In particular, its icons are presented very
differently from the icons in the notification area. This is both
visually unappealing and a
Public bug reported:
Fixing this requires two things:
(1) An xserver patch. This is now upstream:
http://cgit.freedesktop.org/xorg/xserver/commit/?id=84905007702da2c05a4f7446b3fc5ff52be49655
(2) Additional udev rules need to be added to the xf86-input-wacom rules
file.
ACTION==add|change,
Public bug reported:
Binary package hint: easystroke
The release fixes a crasher, all other changes are pretty minor.
** Affects: easystroke (Ubuntu)
Importance: Undecided
Status: New
--
Please upgrade easystroke to 0.5.3
https://bugs.launchpad.net/bugs/521548
You received this
easystroke (0.5.3-0ubuntu1) lucid; urgency=low
* New upstream release (LP: #521548)
- Fixes a crash when a gesture times out during recording
-- Thomas Jaeger thjae...@gmail.com Sat, 13 Feb 2010 19:09:23 -0500
** Attachment added: easystroke_0.5.3.orig.tar.gz
Alexander Sack wrote:
On Thu, Feb 11, 2010 at 07:07:07PM -, Tom Jaeger wrote:
I fail to see how the two issues are related and why one needs to be
fixed before the other. I also think you have your priorities wrong:
This issue has already generated much more discussion than the hinting
Alexander Sack wrote:
I guess I don't really understand what you expect to happen between now
and beta1. The chances of an lcd filtering patch landing in cairo
master in this timeframe is minuscule and even if it did, there'd be
hardly enough time for testing. So we're limited to the patch
Alexander Sack wrote:
On Sun, Feb 07, 2010 at 03:55:29PM -, Yuri Khan wrote:
Alexander Sack wrote on 2010-02-04:
This has highest priority ... but we prefer this getting fixed
upstream rather than running our own patches or even system cairo
again
What are the negative consequences of
*** This bug is a duplicate of bug 217908 ***
https://bugs.launchpad.net/bugs/217908
** This bug has been marked a duplicate of bug 217908
FFe: Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD
implementation in several video drivers
--
Bad image quality
Public bug reported:
Binary package hint: hdparm
A recent version of hdparm is required to get the wiper.sh script
running, which is the only practical way of issuing TRIM commands to
SSDs at this point. While I wouldn't suggest shipping wiper.sh yet,
updating to hdparm-9.27 would make it
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38677453/Dependencies.txt
--
Please upgrade to hdparm-9.27
https://bugs.launchpad.net/bugs/516249
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Andy,
As far as I can tell, this issue has been fixed upstream in the stable tree,
and the fix is already in the ubuntu kernel:
http://bugzilla.kernel.org/show_bug.cgi?id=14781
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
lucid.git;a=commit;h=b9e13497d8cdc40e74a4f14faaa255a0051bb1db
So there
If that's the case, why is the workaround not limited to 945? I think
such a workaround is a bad idea anyway: Not having this linked to an
upstream bug virtually guarantees that even if the issue gets fixed
upstream we won't notice and continue to waste power.
Robert Hooker wrote:
The 965
*** This bug is a duplicate of bug 466532 ***
https://bugs.launchpad.net/bugs/466532
This bug has been fixed in a later version of easystroke, I suggest that
you install 0.4.11 from the easystroke PPA:
https://launchpad.net/~easystroke/+archive/ppa/
** This bug has been marked a duplicate
For the record, here's an updated patch for xulrunner-1.9.2/firefox-3.6.
** Attachment added: extend-pad.patch
http://launchpadlibrarian.net/37586395/extend-pad.patch
--
FFe: Pixellated Images in Firefox/Opera due to incorrect EXTEND_PAD
implementation in several video drivers
Benjamin Drung wrote:
Thanks for your work, I have uploaded it now. I have switched to
debhelper v7 and it builds without problems. The files are installed
correctly.
Is there an reason, why this package is only in Ubuntu and not in
Debian?
It seems it'd be a lot of work to also maintain
Public bug reported:
Binary package hint: easystroke
In order for easystroke to take advantage of XI 2.0, we need to upgrade
to the 0.5 series.
** Affects: easystroke (Ubuntu)
Importance: Undecided
Status: New
--
Please upgrade easystroke to 0.5.2
easystroke (0.5.2-0ubuntu1) lucid; urgency=low
* New upstream release (LP: #502366)
- Fixes crash when the third axis is a relative one (LP: #466532)
-- Thomas Jaeger thjae...@gmail.com Sat, 02 Jan 2010 11:41:36 -0500
** Attachment added: easystroke_0.5.2.orig.tar.gz
/37366738/changes.diff
** Changed in: easystroke (Ubuntu)
Status: New = Incomplete
** Changed in: easystroke (Ubuntu)
Assignee: (unassigned) = Tom Jaeger (thjaeger)
** Attachment added: easystroke_0.5.2.orig.tar.gz
http://launchpadlibrarian.net/37370420/easystroke_0.5.2
Sorry, I didn't realize the version of xinput in karmic was this old.
xinput set-int-prop device-num 'Device Enabled' 8 0 should work then.
Redge wrote:
Hmm, the command xinput set-prop doesn't seem to work. For me, it just
prints usage:
--
easystroke at times doesn't recognize mouse movement
Thanks for the log. I think what the issue is that you have two
Logitech USB Receiver devices, one of which sends bogus motion events
(or no motion events at all). Easystroke will only accept input from
the device which emitted the first press, so if the buggy device wins
the race, easystroke
*** This bug is a duplicate of bug 44082 ***
https://bugs.launchpad.net/bugs/44082
** This bug is no longer a duplicate of bug 111893
Panel items lose their order when panel is not expanded
** This bug has been marked a duplicate of bug 44082
GNOME Panel icons (on right side) move
*** This bug is a duplicate of bug 44082 ***
https://bugs.launchpad.net/bugs/44082
** This bug is no longer a duplicate of bug 111893
Panel items lose their order when panel is not expanded
** This bug has been marked a duplicate of bug 44082
GNOME Panel icons (on right side) move
*** This bug is a duplicate of bug 44082 ***
https://bugs.launchpad.net/bugs/44082
** This bug is no longer a duplicate of bug 111893
Panel items lose their order when panel is not expanded
** This bug has been marked a duplicate of bug 44082
GNOME Panel icons (on right side) move
*** This bug is a duplicate of bug 44082 ***
https://bugs.launchpad.net/bugs/44082
** This bug is no longer a duplicate of bug 111893
Panel items lose their order when panel is not expanded
** This bug has been marked a duplicate of bug 44082
GNOME Panel icons (on right side) move
*** This bug is a duplicate of bug 44082 ***
https://bugs.launchpad.net/bugs/44082
** This bug has been marked a duplicate of bug 44082
GNOME Panel icons (on right side) move apparently randomly on session start
in some situations
--
Panel items lose their order when panel is not
Does restarting easystroke fix this? Can you attach a log of when this
happens (easystroke - easystroke.log)?
--
easystroke at times doesn't recognize mouse movement
https://bugs.launchpad.net/bugs/480807
You received this bug notification because you are a member of Ubuntu
Bugs, which is
laulau wrote:
if the workaround isn't still needed, can someone drop it so that
Firefox has the same features as under Windows (fast and beatifull
scalings) ?
That's exactly what the packages in the firefox-smooth-scaling PPA do.
But upstream is unresponsive on the issue, and the ubuntu
First could someone explain exactly what feature in the graphics driver
people think is wrong.
Many graphics drivers didn't use to accelerate composite operations with
repeat type PAD (and REFLECT) correctly. This was a year ago; i believe
these issues have long been fixed.
Could a small
kenjo wrote:
On Wed, 2009-11-18 at 01:57 +, Tom Jaeger wrote:
First could someone explain exactly what feature in the graphics driver
people think is wrong.
Many graphics drivers didn't use to accelerate composite operations with
repeat type PAD (and REFLECT) correctly. This was a year
This bug is about cleaning up the (totally screwed-up) package that is
currently in ubuntu, not about any functional change. This could make
everybody's life easier that's going to work on the package in the
future, but apparently, killing off the package is a higher priority.
Not exactly the way
** Changed in: easystroke (Ubuntu)
Status: Confirmed = Invalid
** Also affects: gnome2-globalmenu
Importance: Undecided
Status: New
--
Easystroke not start in Ubuntu 9.10
https://bugs.launchpad.net/bugs/474488
You received this bug notification because you are a member of
Why do people want their linux desktop to look like Mac OS? Disgusting.
In any case, this is not a bug in any package shipping with ubuntu.
** Bug watch added: code.google.com/p/gnome2-globalmenu/issues #536
http://code.google.com/p/gnome2-globalmenu/issues/detail?id=536
** Changed in:
Well, did the package from my PPA fix it?
gidantribal wrote:
I have the same crash problem, but with an ordinary 3/buttons mouse.
--
[Karmic]Easystroke: Crash when recording.
https://bugs.launchpad.net/bugs/466532
You received this bug notification because you are a member of Ubuntu
Bugs,
Googling reveals that this is a general problem with gtkmm applications
(such as easystroke and gnome-system-monitor) that somehow depends on
the theme used:
http://ubuntuforums.org/showthread.php?t=1289649
This is probably not a gtkmm bug either, but I've assigned it to gtkmm
so that the gtkmm
** Changed in: ubuntu
Status: New = Confirmed
** Summary changed:
- [Karmic]Easystroke: Crash when record. (kernel)
+ [Karmic]Easystroke: Crash when recording.
** Changed in: ubuntu
Status: Confirmed = Invalid
** Package changed: ubuntu = easystroke (Ubuntu)
** Changed in:
MephSnake wrote:
/home/daniel
apt-get source easystroke
(.)
gpgv: Firmado el jue 20 ago 2009 18:50:04 CEST usando clave DSA ID 491E5389
gpgv: Imposible comprobar la firma: Clave pública no encontrada
dpkg-source: aviso: fallo al verificar la firma en
./easystroke_0.4.9-0ubuntu1.dsc
Can you attach the output of grep -r ^console /etc/init?
Ride wrote:
Same problem here.
As manolo said, I just upgraded to 9.10 (from a 9.04), network upgrade,
and Xorg cpu consumption rises to almost 100%. The machine is an Acer
5810T laptop (with an Intel graph card). With 9.04 went
manolo wrote:
Hi Wolfgang Kufner.
Thanks for your reply. At the moment I can provide the following video
showing my tests made in order to confirm that Xorg still goes crazy, at
least on my system:
http://www.youtube.com/watch?v=skuog28ZnoM
Then, please show me any other way to
Ride wrote:
Hi again,
this is the output of the command grep -r ^console /etc/init
/etc/init/mountall.conf:console output
/etc/init/ufw.conf:console output
/etc/init/mountall-shell.conf:console owner
/etc/init/rcS.conf:console owner
Killing Xorg process doen't work for me. It seems
manolo wrote:
Tom, thanks for your reply.
Actually that video showed the best performing session I've had with karmic
:(
Anyway, the CPU consuming is ** at least 25% ** when no other programm
is running, beside system daemons. Executing Firefox, for example, maked
Xorg consume up to 80%
Sorry, I'll need a real backtrace with debug symbols enabled. This is a
little bit more work since you need to recompile the applications. You
should be able to use the following instructions (untested):
sudo apt-get build-dep easystroke
apt-get source easystroke
cd easystroke-0.4.9
echo
I don't have the time and energy to keep the jaunty packages up to date,
so I deleted them. The karmic packages should work fine on jaunty, though.
NoBugs! wrote:
Firefox 3.5.4 update seems to have broken the pixellated images fix.
Will this package be updated in 9.04?
--
FFe: Pixellated
*** This bug is a duplicate of bug 461344 ***
https://bugs.launchpad.net/bugs/461344
Sorry, I can't tell you anything about this bug until someone unlocks
the master bug.
--
easystroke assert failure: ERROR:poa.c:1028:ORBit_POA_activate_object_T:
assertion failed: ((poa-life_flags
There's no obvious place where a division by zero could occur, so I'll
need a backtrace. As a first step, can you run easystroke in gdb (gdb
easystroke, then enter run) and then issue the bt command when it
crashes?
--
[Karmic]Easystroke: Crash when record. (kernel)
My guess would also be that this is somehow related to gtk's new client-
side window approach. Can someone try if invoking firefox from the
command line as GDK_NATIVE_WINDOWS=1 firefox fixes the issue?
--
flash does not recognise mouse clicks
https://bugs.launchpad.net/bugs/410407
You received
I have neither the time nor enough knowledge about its internals to even
consider taking over the project. I just want things to work smoothly:
Thinkfinger is stable enough that it only takes minimal effort to keep
up with minor kernel or X changes that happen over time. But one thing
is for
This makes no sense. If the package is dropped from debian, we should
be free to do whatever we want with the package.
fprint is not an acceptable replacement for thinkfinger, as it allows
password login only after fingerprint authentication has timed out (i.e.
after 30 seconds!).
Michael Terry
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: easystroke (Ubuntu)
Status: New = Invalid
** Changed in: compiz (Ubuntu)
Status: Invalid = Confirmed
--
Easystroke problem when
Easystroke does send out the clear command, I think the problem is that
compiz never processes it. IIRC, the compiz main loop is coded in such
a way that compiz only processes commands sent by DBus if it is idle, so
it never gets to clearing the screen when it is too busy drawing the
fire.
--
** Bug watch added: sourceforge.net/apps/trac/easystroke/ #6
https://sourceforge.net/apps/trac/easystroke/ticket/6
** Also affects: easystroke via
https://sourceforge.net/apps/trac/easystroke/ticket/6
Importance: Unknown
Status: Unknown
--
Easystroke crashes when trying to add
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cryptsetup (Ubuntu Karmic)
Status: New = Confirmed
** Changed in: usplash (Ubuntu Karmic)
Status: Confirmed = Invalid
** Changed in: upstart (Ubuntu Karmic)
Status: Invalid =
rid of console owner is upstart, right?
Now if someone familiar with the cryptsetup package could explain why it
needs console ownership, we could actually get anywhere.
Scott James Remnant wrote:
On Tue, 2009-10-13 at 15:46 +, Tom Jaeger wrote:
** Also affects: cryptsetup (Ubuntu
Steve Langasek wrote:
On Tue, Oct 13, 2009 at 07:05:18PM -, Tom Jaeger wrote:
Now if someone familiar with the cryptsetup package could explain why it
needs console ownership, we could actually get anywhere.
Because it needs to be able to prompt users for passphrases. How does
knowing
Scott was kind enough to provide some background on this bug in the
#upstart channel:
Keybuk in Linux, we have consoles
Keybuk but really we mean Virtual Terminals (VTs)
Keybuk and we have TTYs too
Keybuk not to mention Pseudo-Terminals
Keybuk (PTYs)
Keybuk it's all a bit of the kind of jumble
Does upstart ensure that only one 'console owner' job can run at the
same time? I assume it would also be a problem if one 'console owner'
job took away the console from another one. In this case, couldn't we
just make gdm/kdm 'console owner' jobs as well?
--
[karmic] Xorg 100% CPU utilization
Scott James Remnant wrote:
That precisely fits the problem definition.
console owner while X is running while forcibly take the ownership of
tty7 away from X. It doesn't like that so much (cf. this bug)
Scott
So this is essentially bug #60487 (!). Any thoughts on a solution? X
really
I can still reproduce the issue after the latest updates.
Steve Langasek wrote:
Seeing how cryptsetup wasn't updated and usplash was, sounds like this
was indeed fixed in usplash, then. :) Marking as fixed; if anyone is
still seeing this with usplash 0.5.41, please reopen (and yell).
**
Sorry, I didn't realize this was an upstream task.
The last thing I noticed before my shiny new SSD died a horrible death
today was that the problem would go away if I commented out the line
console owner in /etc/init/cryptdisks-enable.conf.
Steve Langasek wrote:
(re-closing the cryptsetup
Martin Pitt wrote:
So Scott says that something in the boot process steals vt7 (where X.org
starts up). /etc/init.d/console-setup does not touch vt7, so that's not
it. So we need to find what it is.
Do all of the reporters have cryptsetup installed? If you don't need it
for encrypted hard
** Changed in: xorg-server (Ubuntu)
Status: Triaged = Invalid
--
Easystroke doesn't like Up or Down
https://bugs.launchpad.net/bugs/412169
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Sorry, I think I was wrong in calling this a bug: My assumption that
each event contains a full set of axis values was wrong. (But I'm in
good company here, until very recently, gtk+ made the same faulty
assumption).
--
Easystroke doesn't like Up or Down
https://bugs.launchpad.net/bugs/412169
StefanPotyra wrote:
Ack #2, FFe granted, please go ahead.
(side note: maybe it makes sense to merge 0.4.5-1 from unstable instead
of bringing in the new upstream version independently?)
I hadn't noticed that debian has the new version already, I guess we can
just sync, then.
Debian has
Bryce Harrington wrote:
On Wed, Oct 07, 2009 at 09:56:10PM -, Martin Albisetti wrote:
Bryce's GDM fixes the issue for me as well.
I'm still seeing the issue after disabling ACPI in the X server. The
only thing it does is get rid of the warning in xorg.conf, since the
acpi initialization
Scott James Remnant wrote:
What's this got to do with Upstart?
X is started too early during bootup when the console isn't ready yet.
Where we don't know yet what ready means. There's also this:
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
directory)
So we need a dependency
It has *nothing* to do with tcflush(). As I said above, If I revert the
patch that introduced the tcflush() call, I can still reproduce this
problem. This is just the semantics of select(): If a fd is in an error
state, then a subsequent read() or write() won't block (since they will just
return
You're right, I actually forgot to install the package, so you don't
have 100% CPU anymore after reverting the commit. But this really
doesn't fix the underlying problem, we still have an invalid console fd
floating around, which for example is preventing us from switching
virtual terminals.
Samuel thibault wrote:
Tom Jaeger, did you actually notice switching VT not working? Could
you get an strace of that happening?
Yes, I did. The issue comes and goes; and unfortunately I can't
reproduce it right now. This is the system call that failed, though
(hw/xfree86/common/xf86Events.c
Samuel thibault wrote:
Could people getting the error check /proc/`pidof X`/status? Here I
have
SigIgn: 10301000
The important part is the 3. If the 3 is not there it's normal that
tcflush() return EIO for the console: because X starts its own session
alone, it is an orphaned
** Changed in: xournal (Ubuntu)
Status: Incomplete = Confirmed
--
[FFe] Please upgrade xournal to 0.4.5
https://bugs.launchpad.net/bugs/441755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
kenjo wrote:
deb http://ppa.launchpad.net/firefox-smooth-scaling/ppa/ubuntu jaunty
ii xulrunner-1.9.1
1.9.1.4~hg20091002r26447+nobinonly-0ubuntu2~umd1~jaunty XUL + XPCOM
application runner
ii xulrunner-1.9.1-gnome-support
This one doesn't make the system slow and unresponsive at all -- it's
barely noticable at all, except for the fan ramping up. But I agree,
some of the 'me too' replies are clearly instances of this bug.
--
[karmic] Xorg 100% CPU utilization -- only after first login
** Changed in: xorg-server (Ubuntu)
Status: New = Confirmed
--
[karmic] Xorg 100% CPU utilization -- only after first login
https://bugs.launchpad.net/bugs/439138
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: xournal
The recent release of xournal 0.4.5 contains some much-needed bug fixes
along with some very worthwhile new features (in particular, much better
PDF rendering). Let me know if I need to file a FFE.
** Affects: xournal (Ubuntu)
Importance:
xournal (0.4.5-0ubuntu1) karmic; urgency=low
* New upstream release (LP: #441755)
- bugfixes for GTK+ 2.16/2.17 issues with xinput events
(LP: #410813, LP: #348706, LP: #432388)
- gettext internationalization (contributed by David Planella)
- use poppler instead of pdftoppm to
** Attachment added: xournal_0.4.5-0ubuntu1+1.dsc
http://launchpadlibrarian.net/32953677/xournal_0.4.5-0ubuntu1%2B1.dsc
--
Please upgrade xournal to 0.4.5
https://bugs.launchpad.net/bugs/441755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry, I attached the wrong .dsc file.
** Attachment added: xournal_0.4.5-0ubuntu1.dsc
http://launchpadlibrarian.net/32953794/xournal_0.4.5-0ubuntu1.dsc
--
Please upgrade xournal to 0.4.5
https://bugs.launchpad.net/bugs/441755
You received this bug notification because you are a member of
Thanks, fixed in the attachment.
Denis Auroux wrote:
On 10/03/2009 03:00 PM, Tom Jaeger wrote:
Sorry, I attached the wrong .dsc file.
** Attachment added: xournal_0.4.5-0ubuntu1.dsc
http://launchpadlibrarian.net/32953794/xournal_0.4.5-0ubuntu1.dsc
Small correction needed
Denis has convinced me that leaving the XInput workaround enabled is the
correct thing to do (main reasons: rotation and touchpad/mouse input),
so here's another update.
--
xournal (0.4.5-0ubuntu1) karmic; urgency=low
* New upstream release (LP: #441755)
- bugfixes for GTK+ 2.16/2.17
Here's the relevant part of the upstream changelog:
Version 0.4.5 (Oct 2, 2009):
- bugfixes for GTK+ 2.16/2.17 issues with xinput events
- various minor UI bugfixes
- gettext internationalization (contributed by David Planella)
- Catalan translation (by David Planella), French translation
Build log and install log attached.
** Attachment added: xournal-build.log
http://launchpadlibrarian.net/32964208/xournal-build.log
** Attachment added: xournal-install.log
http://launchpadlibrarian.net/32964209/xournal-install.log
--
Please upgrade xournal to 0.4.5
101 - 200 of 524 matches
Mail list logo
