I took the suggestion and upgraded to fprint for a couple of months. It
is a downgrade. pam_thinkfinger at least prompts sensibly when doing
the gsudo-type things. pam_fprint just sits there stupidly and you have
to guess when something is waiting for a fingerprint scan or password.
Combine
This doesn't happen in Lucid... or other recent versions...
--
iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds
(e.g. enable/disable using nm-applet)
https://bugs.launchpad.net/bugs/356293
You received this bug notification because you are a member of Ubuntu
Bugs,
Cool. Given that the bug actually existed and that I now know how to
update the status, I changed it to fix released. ;-)
** Changed in: linux (Ubuntu)
Status: Invalid = Fix Released
--
iwlagn intrepid - disabling/enabling wireless freezes system for a few seconds
(e.g. enable/disable
Good to hear that it works for you too, Nate.
Yeah, the documentation has changed its recommendation for modifying
package versions for PPAs, so I followed the new recommendation. Older
packagers from PPAs (such as Jon's will probably look newer). You
should be able to install mine by doing
Packages containing the patch are in my PPA at:
https://launchpad.net/~martin-meltin/+archive/ppa
A quick test seems to show that these packages fix the problem. If
others can install, test and confirm then perhaps someone will build an
official package for lucid
--
Intrepid regression:
The patch linked to in comment #83 works for me.
I'm trying to build a version for my PPA... but I just need to wait for
various build messes to complete... I tried doing something useful with
the package versions...
--
Intrepid regression: carriage-return required after finger scan
We've had a working patch since Hardy. Is there a chance that someone
could pick it up so that we could have a working version in Lucid... or
the next release?
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-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
0.6.27 is in Karmic so this could be closed.
--
gnokii crashes with stack smashing detected error
https://bugs.launchpad.net/bugs/335394
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
That's great news, kbrock... you're welcome!
--
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
kbrock, the patch works with my v1, so I'm not sure what is happening
with you. However, I'm running the version from my PPA rather than
Michael Rooney's PPA. They should be the same though...
Unsolved mystery... :-(
--
usb-storage: waiting for device to settle before scanning
kbrock, it certainly looks like you have mrooney's PPA version of the
package installed, so the bug should be fixed.
Is your Sansa e260 a v1 or v2? There are hints for how to tell the
difference at:
http://www.rockbox.org/twiki/bin/view/Main/SansaE200v2#How_to_identify_an_e200_v2
The current
kbrock, the problem is that the package didn't build. I'm not sure
why... but my guess is that you've actually downloaded the source from
the PPA, you're patching it and then the build process is failing to
patch it again. Hard to be certain though...
Let's focus on whether you have the binary
kbrock, provided you've done the previous 2 steps in comment 12 (apt-get
source libgphoto2-2, wget ...) then the patch line should apply without
any problems - you need to be in the directory containing the
libgphoto2-2.4.2 subdirectory. It shouldn't make any difference but the
only lines you
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
I don't think I've seen this particular bug since upgrading to Jaunty.
That said, I've also switched to the -generic kernel from the -rt one
for most uses... and have seem a big improvement in stability.
--
[i946GZ] X gets stuck in D-wait state at logout
https://bugs.launchpad.net/bugs/356248
paulderol, what solution worked for you? What reverts when you do a
full update?
--
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
OK, here's some better testing from me...
I used a different Ubuntu 9.04 32-bit system where I hadn't tested this
before. It has this sort of USB interface:
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2
EHCI Controller (rev 01)
The system is running up-to-date Jaunty
One interesting thing I haven't mentioned so far: my e260 is a v1. Are
people who are still having problems using a v1 or v2? I've assumed v1
because people mention Rockbox... but I think Rockbox now (partially?)
runs on v2.
--
usb-storage: waiting for device to settle before scanning
It would be interesting if it matters... but my testing was only done on
Ubuntu 9.04 32-bit.
If anyone else tests the version from my PPA can they please post a
comment?
--
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
You received this bug
I applied the patch in comment 10
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/355998/comments/10
the quickest way possible (i.e. applied it to the source rather than
integrating it into debian/patches/) and put the result in my PPA:
Oh, if it matters, my test was with rockbox firmware on a Sansa e260.
--
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I don't think I've seen this problem since Gutsy.
I think it was a race connected to the evms-induced double swap bug.
evms seems to be gone and I don't think feisty is supported anymore, so
I think this should be closed.
--
/dev/.initramfs/progress_state is corrupted at shutdown
I see this too in Jaunty:
pathological:
Installed: 1.1.3-8ubuntu2
Candidate: 1.1.3-8ubuntu2
Version table:
*** 1.1.3-8ubuntu2 0
500 http://proxy jaunty/universe Packages
100 /var/lib/dpkg/status
As mentioned above, turning off music and sound effects stops the crash.
I doubt that most people here have a Windows machine! This bug has been
reported against the Ubuntu Linux distribution.
2 options:
* Pull the relevant parts out of this patch:
http://ppa.launchpad.net/martin-
meltin/ppa/ubuntu/pool/main/m/meanwhile/meanwhile_1.0.2-4~ppa4.jaunty.diff.gz
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
Bugs, which is
I've submitted a PPA build for the patched meanwhile for Jaunty. The
x86_64 version is built but the i386 version is still sitting in the
queue waiting to be built.
I haven't had time to upgrade to Jaunty yet, so when these are built can
someone please test them? I'll remove them if they're
The Hardy and Intrepid packages in my PPA mentioned in comment 9 have
now been tested for nearly 6 months with no adverse effects... sorry, I
guess I should have mentioned that earlier.
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received
Thanks for the suggestion!
Unfortunately the version in linux-backports-modules-2.6.27-11-generic
looks to be the same version as in the main kernel package:
mart...@rover:~$ modinfo /lib/modules/2.6.27-11-generic/updates/iwlagn.ko |
grep '^version:'
version:1.3.27ks
mart...@rover:~$
Public bug reported:
Binary package hint: xorg
On Ubuntu 8.10, attempting to logout from GNOME often leaves the X
server stuck in a D-wait state:
root 5096 1.7 0.9 25484 19660 tty7 Ds+ 14:29 8:25
/usr/X11R6/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten
tcp vt7
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24865787/Dependencies.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/24865788/LsMod.txt
** Attachment added: LsPci.txt
http://launchpadlibrarian.net/24865789/LsPci.txt
** Attachment added:
Public bug reported:
Under Ubuntu 8.10, when I right-click on nm-applet in the notification
area and uncheck Enable Wireless, my mouse and keyboard often stop
working until the Disconnected notification pop-up appears.
Enabling Show seconds on the GNOME clock confirms that the entire X
(or
Load average is the average number of runnable processes over a minute
(or 5 minutes or 15 minutes). A load average of 50 is not a 50% load on
the CPU. It is potentially a 5000% load on the CPU - since dcraw is
likely doing something very CPU intensive it probably is a 5000% load.
I'm running
Yeah, I too don't have thumbnailing enabled and tracker put the load
average on my system up to about 50. For now I've told tracker to
ignore *.CR2 files.
Also, this is a regression - this didn't happen under Hardy.
One question I have is why tracker runs so many dcraw/identify processes
in
Public bug reported:
Binary package hint: gnokii
When trying to write the phonebook of my Nokia 6233, gnokii (version
0.6.26.dfsg-3) fails with a stack smashing detected error, as shown at
the end of this message.
This has been reported upstream:
http://savannah.nongnu.org/bugs/?23941
The
gnokii-0.6.27 is released and seems to fix this bug. This seems logical
since the fix is noted in the upstream bug a couple of months before
0.6.27 was released.
I've tested 0.6.27 by building packages using the debian/ subdirectory
from the buggy version, with appropriate changelog change and a
I have hardy and intrepid packages in my PPA. I've been testing the
hardy one since yesterday with no problems, others are testing the
intrepid package.
Details at:
https://launchpad.net/~martin-meltin/+archive
--
pidgin crashes in libmeanwhile just after connecting
** Attachment added: meanwhile-mwSametimeList_get.patch
http://launchpadlibrarian.net/17105590/meanwhile-mwSametimeList_get.patch
--
pidgin crashes in libmeanwhile just after connecting
https://bugs.launchpad.net/bugs/261695
You received this bug notification because you are a member of
Public bug reported:
Something seems to have changed on a Sametime server I use, causing
pidgin to die in libmeanwhile just after establishing a connection.
I see the problem in libmeanwhile1-1.0.2-3 in Ubunutu 8.04 (Hardy).
Attached is a patch that fixes (or works around) the problem by
Thanks Andreas! That looks good...
I would have submitted a patch but I wasn't sure whether to direct it to
stderr, remove it altogether (as you've done) or something else... :-)
--
anacron prints spurious debug message
https://bugs.launchpad.net/bugs/124518
You received this bug notification
Hi Andreas,
Yes, it still happens:
$ /usr/sbin/anacron -s -d -q -t ${HOME}/etc/anacrontab -S
${HOME}/var/spool/anacron
Checking against 24 with 31
If I redirect the above to /dev/null then I don't see it, so the output
is definitely going to stdout.
peace happiness,
martin
--
anacron
I can confirm that I saw this problem regularly under Gutsy.
--
iwl4965 can't reconnect if AP is lost and then comes back
https://bugs.launchpad.net/bugs/183474
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
Actually, I got it wrong: for me keyboard is fine. The mouse simply
stops working and functions again after switching desktops.
--
[Gutsy] desktop and keyboard freezes while mouse is moveable
https://bugs.launchpad.net/bugs/138094
You received this bug notification because you are a member of
I'm seeing a similar X-related lock-up several times a day under
moderate usage. However, if I change desktops using Ctrl-Alt-Left/Right
then the mouse and keyboard start working again. Is anyone else seeing
this?
This would point to some sort of bizarre window manager bug... or
perhaps an X
Hi Chuck,
Chuck == Chuck Short [EMAIL PROTECTED] writes:
Chuck Added thanks for your patch.
Chuck ** Changed in: tmda (Ubuntu)
ChuckStatus: Confirmed = Fix Committed
Thanks...
At this stage I guess it is worth confirming that python2.5 will still
be the default python
Hi Juho. Just wondering if you've fixed the swap problem and whether
this has caused the corruption on shutdown to go away. Unfortunately
I've had to retired the machine where I was seeing the problem, so I can
no longer test for this problem.
It would be nice to if we were able to add some
I wonder if this is semi-random corruption related to Bug #96715? I've
uninstalled evms and the swap space problem has gone away. Juho, when
you do:
cat /proc/swaps
do you see the same partition used twice (once via /dev/mapper)?
This bug is probably going to be very hard to debug... so
Public bug reported:
Binary package hint: anacron
I assume that when anacron is run from the command line and there are no
problems encountered then it should produce no output. However, if
there's a @monthly entry in the anacrontab, then anacron prints a
message like:
Checking against 0
** Also affects: anacron (Debian)
Importance: Undecided
Status: New
--
anacron prints spurious debug message
https://bugs.launchpad.net/bugs/124518
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I'm hoping to get someone's attention to have this package at least
fixed for gutsy. My previous comment has the patch needed to fix the
problem. :-)
Thanks...
--
No Python TMDA modules for python 2.5
https://bugs.launchpad.net/bugs/109083
You received this bug notification because you are a
This happened again. Here are the contents of
/dev/.initramfs/progress_state:
0(p'-KA
Meaningless nonsense! Actually, the last 2 characters were some sort of
scripted K (kappa?) and a scripted A (?), probably form some distant
part of the console font.
Whatever the case, the file contains
Public bug reported:
Sometimes shutdown fails with the message:
/dev/.initramfs/progress_state: 1: Syntax error: Unterminated quoted
string error: '/etc/init.d/rc' exited outside the expected flow control.
The only thing that writes to this file appears to be the
update_progress() function in
Public bug reported:
Package: wpasupplicant
Version: 0.5.7-0ubuntu2
In Edgy /usr/share/doc/wpasupplicant/README.modes.gz used to say to put:
wpa-conf managed
in an /etc/network/interfaces stanza for an interfaces that were using
WPA managed mode.
However, in Feisty, doing this causes a
I have the same problem.
Attached is the simple patch I used to rebuild a useful version of
python-tmda for feisty.
** Attachment added: Patch to make python-tmda useful under feisty
http://launchpadlibrarian.net/8034086/feisty-python-tmda.patch
--
No Python TMDA modules for python 2.5
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:
84 matches
Mail list logo
