** Changed in: nautilus (Ubuntu)
Status: Fix Released = In Progress
--
Nautilus memory leak on regular usage for long hours
https://bugs.launchpad.net/bugs/417589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
I'm not sure if it is the right thing to do but I've just moved the
state of this bug back to In Progress.
I've been running Nautilus for over 2 months. It is using 1.4GB of
virtual memory:
USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
martins 2674 0.0 4.5 1515596
Public bug reported:
Binary package hint: gnome-control-center
In Ubuntu 9.10 (Karmic Koala) the Disable touchpad while typing option
causes an otherwise disabled touchpad to be re-enabled after typing
ceases.
The expected behaviour is that a disabled touchpad stays disabled until
it is
Does this also mean the bug is now as unlikely to be fixed in karmic as
it was in jaunty?
This means that novice users will be going for a whole year potentially
unable to print PDFs. That's a disaster. :-(
--
evince sometimes yield error Error printing: Too many failed attempts
This is sounding a little too much like a flame war. This is a bug
report not a place to argue.
Can people please find a better place to have their arguments? ;-)
--
evince sometimes yield error Error printing: Too many failed attempts
https://bugs.launchpad.net/bugs/359975
You received this
Ummm... this is a regression that makes F-Spot close to useless for
novice users... :-(
I think the Ubuntu project needs a process that imports well tested
fixes from individuals' PPAs. That would make this sort of thing easy
to release a fix for...
--
Imports all photos to the root of the
Although comment #25 wasn't addressed to me...
If this works sometimes and not others, I fail to see how it could be an
authentication issue. Authentication isn't the sort of thing that comes
and goes... :-)
Note comment #15 where I observe that *no* network traffic is sent to
the remote cups
Well, that seems to remove any suggestion that this problem is HP-
related or driver-related. The Lexmark X560n looks to be a Postscript
printer:
http://www.linuxprinting.org/show_printer.cgi?recnum=Lexmark-X560n
Not HP and no need for conversion from Postscript to some other wacky
format...
I'm seeing this too on an up-to-date 32-bit Jaunty install. Printing
works sometimes. Other times, even printing the same PDF from evince it
fails and I see errors like this in /var/log/cups/error_log:
E [28/Jul/2009:08:45:20 +1000] cupsdReadClient: 10 IPP Read Error!
When printing I run
Public bug reported:
Binary package hint: f-spot
In 8.10 (Intrepid), f-spot 0.5.0.3-0ubuntu4 can be made to crash as
follows:
1. Double-click a tag to show only photos with that tag.
2. Select another tag that has no photos in common with the first tag and drag
this tag onto the other tag in
David, can you please post a recipe that includes a timeline click for
crashing the Jaunty version?
--
When no photos are displayed, clicking on timeline crashes f-spot
https://bugs.launchpad.net/bugs/373202
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Import now works fine when a media card is inserted. This is on a fresh
install of Hardy.
Right-clicking on a folder in Nautilus and selecting F-spot Photo
Manager still causes an attempt to import from a camera or media card.
This seems wrong. However, it is easy to work around by selecting
Didn't see this bug on: 1 laptop upgrade from Gutsy to Hardy and 1
laptop fresh install of Hardy.
However, since you have to go to some effort to switch on numeric
keyboard mode on laptops, that doesn't tell us much. :-(
--
Numeric keypad no longer works after upgrade
I haven't tried with a new user yet.
Something is deciding to import the photos from the card instead of the
directory I've selected in Nautilus. f-spot-import was my 1st guess
since it contains some logic that tries to figure out where to import
from.
Sorry I haven't had time to debug this
I don't see the problem with importing from a media card fixed by this
update.
I upgraded these packages from proposed-updates:
2008-06-01 11:23:19 status installed gvfs 0.2.4-0ubuntu1
2008-06-01 11:23:20 status installed gvfs-backends 0.2.4-0ubuntu1
2008-06-01 11:23:20 status installed nautilus
Will there be a delay before this hits the hardy-proposed repository?
I don't see it there yet... but then I haven't used -proposed before.
Thanks!
--
Can't open multiple files from File Browser in F-Spot Photo Viewer
https://bugs.launchpad.net/bugs/202717
You received this bug notification
OK, got it - approx was caching Packages.bz2 a little too aggressively.
The version in hardy-proposed fixes this bug.
I'll add some comments to bug #208467 about this release and importing
photos.
--
Can't open multiple files from File Browser in F-Spot Photo Viewer
The new version of f-spot in hardy-updates (0.4.3.1-0ubuntu1) does not
fix this bug - not surprising, since the bug is in nautilus... :-)
Behaviour:
* Inserting a media card from a camera still results in failure in the
form of a usage message from f-spot.
* Saying
f-spot-import dir
I'm a surprised to see this tagged with Low importance. Given that
F-spot gets its own page in the list of Hardy features
http://www.ubuntu.com/products/whatisubuntu/804features/photos/ I would
have thought the prominence of the package, and the availability of a
fix, would make the importance
For anyone stuck on gutsy, I've applied the above patch and built a
version of the package in my PPA:
https://launchpad.net/~martin-meltin/+archive
I've tested the i386 version and it definitely fixes the problem.
--
F-spot crash on changing tag icon
https://bugs.launchpad.net/bugs/140853
To ensure that the patch fixes the bug and so that I (and others) have a
working version I've uploaded a patched version to my PPA at:
https://launchpad.net/~martin-meltin/+archive
You'll want the hardy version (my gutsy package for f-spot fixes a bug
in the gutsy version).
I've tested the
This is fixed upstream:
http://svn.gnome.org/viewvc/f-spot/trunk/src/main.cs?r1=3883r2=3882pathrev=3883
That patch applies with a bit of fuzz. I've attached a rediffed version
that should apply with no fuzz.
** Attachment added: Rediffed, fuzzless patch to src/main.cs to allow multiple
The above patch is now even more dodgy, since
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/202717 is fixed
upstream, so multiple files/uris to --view are supported again. I've
attached a rediffed patch to that bug.
However, the import via nautilus problem is still there.. so this bug
Yep, I agree with the last 2 comments.
So, given that changes in argument handling for f-spot has caused 2 bugs
(this one and
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/202717), it would
make sense to return the argument handling to the old behavour. Since
f-spot is a script, it seems
By the way, the above doesn't seem to fix f-spot --view dir or
f-spot --view file://dir, which seems broken either way. It works
in the gutsy version and the documentation seems to suggest it should
work. :-(
--
Camera Device button Open F-spot Photo Manager doesn't work
Just to double-check before I do this...
In my case I'm not actually plugging in a camera. I'm inserting an SD
card from a camera into a reader. I assume that this should behave
similarly to a camera, but since this bug was initially concerned with
actual cameras I thought I'd check before I
Sorry, that was a bit over the top, especially out of context... :-(
I'll send you an email explaining my frustration - it doesn't belong in
this bug report.
So, you'd like to see the output of:
gconftool-2 --get
/desktop/gnome/accessibility/keyboard/mousekeys_enable
before and after an
There's still something weird going on that is related to this.
If I insert media containing photos I expect the command specified by
the gconf key /desktop/gnome/volume_manager/autophoto_command to be
run.
However, this isn't happening. Instead, nautilus is trying to launch
its idea of what
Aaarrrggghhh! /usr/share/applications/f-spot.desktop isn't being
accessed when the media is inserted. So where does the association
between nautilus and f-spot come from? Explain this to me and you'll
get much better bug reports on this sort of thing... :-)
Things I have checked:
* There
3 things to add:
* In Gutsy, it was possible to select multiple files in Nautilus and open them
in F-Spot. Therefore, the behaviour we're seeing in Hardy is a regression.
* If this isn't going to be considered an F-Spot bug, then it is a bug in
Nautilus
since it allows you to select
However, opening a whole folder doesn't maintain the sort order. The
files are displayed in directory order (same as ls -U) rather than
sorted alphabetically.
Therefore, this isn't as useful as the old behaviour where multiple
files could be selected and they would appear in F-Spot in the order
I'm seeing the same inconsistent behaviour as in comment 34. After the
first reboot after the upgrade, the keypad was in the cursor control
mode. This time it is in normal number mode. My upgrade was from Gutsy
to the released version of Hardy.
This would be a very frustrating bug for a novice
I'm very surprised that the fix for this hasn't made feisty-updates.
I have several USB devices that I could unmount/eject just fine from the
right-clock menu in Edgy but they are immediately remounted after
being ejected in Feisty. Ways of fixing this so I can safely remove
my devices include:
33 matches
Mail list logo
