Just wanted to keep this rolling towards a fix. I am experiencing the
same issue with NM in Lucid. I am able to create an ad-hoc, users are
able to connect, but there is no functionality. I am using a T40 with
ipw2100
--
ad-hoc networks don't work with Intel wireless
Sadly have to report that I have issues with Lucid and my Radeon 7500.
Randomly the system goes black, shows some quick text (the only part I have
caught says something like checking battery state) and I am prompted to log
back in.
Also, when booting up, the splash screen is in funky (maybe
I'm still getting this with Chromium (Version 25.0.1364.160 Ubuntu 12.04
(25.0.1364.160-0ubuntu0.12.04.1)) running KDE.
This only seems to happen when I have a large number of tabs open (about 150 at
the moment, but I think I've seen it happen with less), having been running
Chromium for over a
Public bug reported:
tried to get rhythmbox to access music on NAS via Firefly media server
and crashed. probably too much music to load in one file as i have more
than 100gb of music. Cant access it thru Itunes server either.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libsane
Thank you. I've been playing around with it, and it makes f-spot happy.
But then again, ofcourse it doesn't change the info in the image file
itself, it just mends the database (photos.db) so that f-spot won't
hiccup.
Perhaps f-spot should handle image files with time stamps wrongfully in
the
I suspect the error message and crash being due to some pictures in my
database having date stamps in the future.
Any quick fixes for adjusting dates in the future to, say, todays date
then?
--
F-spot error: Value is greater than Int32.MaxValue or less than Int32.MinValue
Output of f-spot --debug f-spot-debug.txt
** Attachment added: Output of f-spot --debug f-spot-debug.txt
https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/636819/+attachment/1636228/+files/f-spot-debug.txt
--
F-spot error: Value is greater than Int32.MaxValue or less than
The real problem, of course, is that f-spot PERMANENTLY changes date
information in pictures, thereby corrupting them. An example:
1. Picture 0001.JPG is taken on 29th of May 2010 (29-05-10)
2. Picture is imported into f-spot with option Copy to image folder
Expected behaviour would be:
- Place
I am pleased to see that, yes, but I still don't understand what's going
on. Here's the output of 'exiv2 test.jpg': for the first of two example
images:
hakonau@VOSTRO-ubuntu:~/Desktop$ exiv2 test.jpg
Filnavn : test.jpg
Fil størrelse : 662165 Byte
MIME-type : image/jpeg
I would... but my scripting skills aren't up for the task *blush*
On 28. jan. 2011 23:18, Derek wrote:
Well, going through 4,000 images sounds like a perfect task for a
script. :)
Just use exiftool or your thingy above, and if the dates are severely
outside a certain range (like past 10
I get this too, starting two days ago:
En uhåndtert feil oppstod: Value is greater than Int32.MaxValue or less
than Int32.MinValue
at System.Convert.ToInt32 (Int64 value) [0x0]
at System.Int64.System.IConvertible.ToInt32 (IFormatProvider provider)
[0x0]
at System.Convert.ToType
11 matches
Mail list logo
