Sorry for coming in a little late on this, but it's really horrible
having the input clear on escape. I push escape a lot (a habit I picked
up from using Vim a lot) and I don't ever want it to clear the input
field. There are a great many other Linux users with this habit too I'm
sure.
It is also
Yes, does the same thing for me with 8.10
Did you try it? Does it do the same for you?
--
xine --auto-play=q segfaults
https://bugs.launchpad.net/bugs/217401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I posted this bug to the mozilla site. Here's the link:
https://bugzilla.mozilla.org/show_bug.cgi?id=465880
--
Firefox problems with desktop-effects
https://bugs.launchpad.net/bugs/99740
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Saïvann Carignan,
Can you think of any reason why javascript should be able to request
that the a window be places such that the top of it's content was even
with the top of the screen? (And that request should be taken seriously
by firefox?)
Metacity ignores this request because it is unreasonab
Firefox should not tell the window manager to put the window at (0,0) at
the request of javascript, because with the width and height set ust
right this triggers the "legacy fullscreen support" feature of some
window managers like compiz and wmii (something javascript should not be
able to do.)
Su
I agree that firefox should be fixed.
Perhaps it should be fixed before the values get into localstore.rdf.
I think it's absurd to let javascript set the screenY to 0 ever. Very
few window managers will actually let you put the window there (because
the title bar is hanging off the screen.)
My s
Wahoo! We figured it out.
Now what do we do about it?
Makes sense to me to disable "legacy fullscreen support" by default in
compiz to match metacity. If gnome's default setup doesn't support
"legacy fullscreen support" (and I presume if metacity doesn't now, it
probably hasn't for a long time) t
I fired up gnome, and I'm happy to say that desktop-effects are now
working on my computer (as of intrepid upgrade I assume).
I have steps to reproduce this issue with compiz. This produces the
fullscreen bug described in the original post for this bug report when
done with desktop-effects on. Whe
OK, I looked through the diff between my working and buggy
~/.mozilla/firefox/ folders.
I first discovered that deleting my
~/.mozilla/firefox/xxx.default/localstore.rdf fixed firefox (and deleted
my toolbar customizations).
Then I searched through that file and found the bit that was causing
pro
I can easily enable/disable this bug by swapping between my bad .mozilla
directory and my good one.
Therefore either 1) it's a firefox preference. or 2) it's a firefox bug.
Now since I (the user) didn't change my preferences or install a plugin
or anything (I think it was triggered by going to a
I saved my ~/.mozilla directory from when this bug was driving me nuts.
When I replace it, the bug is reproducible every time by opening a
window.
I grabbed the xprop output by typing this, hitting enter, and starting
firefox: sleep 10; xprop > foo.log
I did this with the .mozilla directory that
Taipan,
I don't think it's possible to run compiz with wmii. To double-check
here's an excerpt from my ps axf:
5900 tty1 Ss 0:00 /bin/login --
6153 tty1 S 0:00 \_ -zsh
6367 tty1 S+ 0:00 \_ /bin/bash /usr/bin/startx
6384 tty1 S+ 0:00 \_ xin
I get this bug without gnome
I'm using the wmii window manager.
Firefox worked fine for months, and since intrepid upgrade.
But now every time I open a firefox window it's fullscreen... really
fullscreen, as described in this bug, I see now title bars, noothing
except what is normally the conten
Thanks for testing everybody!
I had a conversation last year with the FreeBSD maintainer of gforth,
and he couldn't get gforth to build on the build farm with or without
libffcall1, though it always built on his home machine (and mine). It
could well be that this is a 64-bit issue, but I would lik
And here's the one that doesn't need ffcall.
** Attachment added: "nofftest.fs"
http://launchpadlibrarian.net/18095735/nofftest.fs
--
gforth missing libffcall1 dependancy
https://bugs.launchpad.net/bugs/269127
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I'm attaching two scripts.
Just simple "do math and print result" type things.
One uses ffcall to access libm's sin() and sinf(). The other uses
builtin math primitives.
** Attachment added: "a simple test that requires ffcall"
http://launchpadlibrarian.net/18095722/fftest.fs
--
gforth miss
I'm pretty sure the additional functionality provided by ffcall in
gforth is only activated when specifically requested by the programmer
(as it is in some example scripts that come with gforth). So I don't
think inclusion of ffcall could possibly break any existing code written
for gforth.
If you
Done!
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500640
--
gforth missing libffcall1 dependancy
https://bugs.launchpad.net/bugs/269127
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.
Without ffcall you cannot use libraries, so eg it's almost impossible to
write graphical programs or do networking.
--
gforth missing libffcall1 dependancy
https://bugs.launchpad.net/bugs/269127
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
Binary package hint: gforth
gforth 0.6.2-7.2 is built without ffcall support. This makes it nearly
impossible to use libraries.
Solution: install libffcall1-dev before compiling gforth
** Affects: gforth (Ubuntu)
Importance: Undecided
Status: New
--
gforth
Public bug reported:
Binary package hint: apt
The manpage for apt-cache says that --names-only should "Only search on
the package names, not the long descriptions."
And yet it frequently lists packages that do not have the search terms
in the name or short description.
Example: (bash script)
** Attachment added: "apt_cache_false_positives.txt"
http://launchpadlibrarian.net/16457465/apt_cache_false_positives.txt
--
apt-cache search --names-only gives many false positives
https://bugs.launchpad.net/bugs/253761
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
Binary package hint: evince
I've got evince version 2.22.2-ubuntu1
It's lacking the standard "quit" option in the file menu, and ^q doesn't
quit.
ProblemType: Bug
Architecture: i386
Date: Fri Jun 6 14:06:12 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/evince
Pa
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/15089144/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/15089145/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/15089146/ProcStatus.txt
--
contro
** Attachment added: "config"
http://launchpadlibrarian.net/13431693/config
--
xine --auto-play=q segfaults
https://bugs.launchpad.net/bugs/217401
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Public bug reported:
Binary package hint: xine-ui
When run with --auto-play=q xine often crashes (sometimes with a
segfault). Example:
lappy ~> mv .xine dotxine
lappy ~> /usr/bin/xine -g --no-splash --auto-play=q
downloads/keepers/byron_katie_why.flv
This is xine (X11 gui) - a free video player
Public bug reported:
libsdl-1.2debian-all (version 1.2.11-7debian1) claims (in the
description I can see in synaptic) to come with ggi support, but doesn't
appear to. I did apt-get source and found that it explecitly passes
--disable-ggi for the debian-all variant (libsdl1.2-1.2.11/debian/rules
li
>I'm having difficulties reproducing that. Which architecture do you
>use? Also, are you encountering this error on feisty, or on gutsy?
Oh, I'm sorry, I'm on PPC. I think I've got feisty, but I don't
know how to check. I'm pretty sure I installed Ubuntu 7.04-desktop.
Best regards, - Jason
--
Public bug reported:
Binary package hint: starfighter
$ sudo apt-get install starfighter
[...]
Setting up starfighter-data (1.1-6ubuntu1) ...
Setting up starfighter (1.1-6ubuntu1) ...
$ starfighter
starfighter: error while loading shared libraries: libstdc++.so.5: cannot open
shared object file
"new partition size" is a total ambiguity. I didn't see the ambiguity
until reading this bug report. I just took it to mean "size of the new
partition" and was pissed when it resized the old partition to that
size, not the new one.
Please label it:
"Resize old partition to:" or "New size for old
30 matches
Mail list logo