[swar...@esk ~]$ gthumb --version
GNOME gthumb 2.10.11
What's non-standard? All I've done is install Ubuntu, install updates,
and upgrade between Ubuntu releases.
--
gthumb hangs when run to import photos from USB stick
https://bugs.launchpad.net/bugs/557855
You received this bug notification
Aha. This is a bogus bug. When attempting to debug bug 444300, I had
installed gthumb-2.10.11 in /usr/local. I've now deleted everything
under /usr/local, and don't see the hang that this bug refers to; now I
see bug 444300 manifesting instead.
** Changed in: gthumb (Ubuntu)
Status: New =
Fully up-to-date. Issue still present. strace and gdb show same thing
once hung.
** Changed in: gthumb (Ubuntu)
Status: Incomplete = New
--
gthumb hangs when run to import photos from USB stick
https://bugs.launchpad.net/bugs/557855
You received this bug notification because you are a
Help-About shows that it is indeed 2.10.11 (and I also see all the
other version behaviour mentioned above). This kind of packaging
insanity just boggles the mind...
--
gThumb doesn't import images
https://bugs.launchpad.net/bugs/444300
You received this bug notification because you are a member
** Attachment added: gdb-gthumb.txt
http://launchpadlibrarian.net/43627109/gdb-gthumb.txt
--
gthumb hangs when run to import photos from USB stick
https://bugs.launchpad.net/bugs/557855
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Attachment added: strace-gthumb.txt
http://launchpadlibrarian.net/43627125/strace-gthumb.txt
--
gthumb hangs when run to import photos from USB stick
https://bugs.launchpad.net/bugs/557855
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: valgrind-gthumb.txt
http://launchpadlibrarian.net/43627134/valgrind-gthumb.txt
** Changed in: gthumb (Ubuntu)
Status: Incomplete = New
--
gthumb hangs when run to import photos from USB stick
https://bugs.launchpad.net/bugs/557855
You received this bug
Public bug reported:
Binary package hint: gthumb
In lucid, when I insert a USB memory stick, something will automatically
mount the USB stick, and then prompt me for which action I wish to take.
I select Open gThumb Photo Import Tool. The USB stick is then
immediately unmounted, and nothing else
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43410876/Dependencies.txt
--
gthumb hangs when run to import photos from USB stick
https://bugs.launchpad.net/bugs/557855
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Lucid apparently includes gthumb 2.11.2.1, so I guess this is no longer
an issue.
Thanks for the status updates in the bug! :-(
--
gThumb doesn't import images
https://bugs.launchpad.net/bugs/444300
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I'd also like to see this regression fixed in Karmic.
--
Greeter does not show legacy users with uid 1000
https://bugs.launchpad.net/bugs/459199
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
--
desktop-bugs mailing
This particular bug seems to have been made obsolete my Lucid (tested
daily 1/31). The Record from Input option no longer appears in gnome-
sound-recorder. Instead, it uses the system-wide default/current input
stream selected by sound preferences, and does appear to record OK.
I don't recall if
gthumb package maintainers: Is there any chance of getting the latest
(and apparently only supported) gthumb included in Lucid, so Lucid won't
have this issue too?
--
gThumb doesn't import images
https://bugs.launchpad.net/bugs/444300
You received this bug notification because you are a member
FYI, upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=605670 was
closed with the following comment:
Michael Chudobiak [developer] 2010-01-04 13:49:26 UTC
The 2.8.x series is not being maintained, so this bug is being marked as
obsolete.
The first 2.11.x release, which is a
Michael Chudobiak wrote:
Well, 2.10.x isn't being maintained either.
2.11.1 has now been released.
You are kidding right? A version that's included in a 3? month old
distro is already unsupported??? I guess it's time to just dump gthumb
and use something that isn't completely pointless...
--
Lucid will also contain 2.10.x (according to
http://packages.ubuntu.com/lucid/gthumb) unless something changes
between now and when it's released.
--
gThumb doesn't import images
https://bugs.launchpad.net/bugs/444300
You received this bug notification because you are a member of Ubuntu
Desktop
I see this problem too.
It is a regression from Jaunty. I had 2 Jaunty and 1 Fedora (F9/10?)
systems where gthumb import worked correctly. I upgraded the Jaunty
systems and re-installed the Fedora system. All systems now have this
issue.
In my case at least, I found this problem was caused by
Both Jaunty and Karmic contain the same upstream version of gthumb
(2.10.11), so this is probably either a bug in a library that gthumb
uses, rather than gthumb itself, or a bug in Ubuntu's packaging.
--
gThumb doesn't import images
https://bugs.launchpad.net/bugs/444300
You received this bug
More info on my strace findings:
For each JPG file, gthumb's strace starts out like:
[pid 4804] open(/media/64A5-F009//DCIM/103_PANA/P1030183.JPG, O_RDONLY) = 21
[pid 4804] fstat64(21, {st_mode=S_IFREG|0755, st_size=72597, ...}) = 0
[pid 4804] mmap2(NULL, 32768, PROT_READ|PROT_WRITE,
The patch from comment #33 didn't seem to work for me. I don't know if
it was a fluke, but it appeared to prevent my X login from working
correctly; it just hung after removing all the gdm windows and with a
brightness notification on-screen. After removing the patch from a text
console and
Public bug reported:
Binary package hint: gnome-power-manager
This bug is very similar to bug 456057, but there are a couple of critical
differences that I think warrant a new bug:
a) The user in bug 4567057 found that he couldn't change brightness without
gnome-power-manager running. I can on
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34336632/Dependencies.txt
--
brightness autonomously toggles after increasing brightness
https://bugs.launchpad.net/bugs/460062
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/34336633/DevkitPower.txt
--
brightness autonomously toggles after increasing brightness
https://bugs.launchpad.net/bugs/460062
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/34336635/GConfNonDefault.txt
--
brightness autonomously toggles after increasing brightness
https://bugs.launchpad.net/bugs/460062
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/34336636/gnome-power-bugreport.txt
** Tags added: apport-collected
--
brightness autonomously toggles after increasing brightness
https://bugs.launchpad.net/bugs/460062
You received this bug notification because
Architecture: i386
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.1-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686
OK, thanks for bothering to answer my previous question then. I figured
that since nobody answered, it was a mistake.
I'd also debate that it's not serious enough to warrant an update, since
IIRC it blocks bzr-gtk from working, since it crashes. I suppose it's
easy to just re-run the command, but
** Changed in: seahorse (Ubuntu)
Status: Fix Released = Confirmed
--
bzr visualize crashed with DBus error
https://bugs.launchpad.net/bugs/377476
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
Public bug reported:
Binary package hint: seahorse
I've been attempting to get bzr viz to show GPG signatures on
revisions. So, I ran bzr viz against a small local branch (or a branch
from http://bazaar.launchpad.net/~bzr/bzr-stats/trunk/), selected
various revisions, and also selected the
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/32899564/Dependencies.txt
--
seahorse sucks CPU, and RAM, causes swap storm, makes system completely
unresponsive
https://bugs.launchpad.net/bugs/441121
You received this bug notification because you are a member of Ubuntu
How come this is marked Fix Released for Seahorse (Ubuntu)? I'm
still seeing it on Jaunty with the bzr PPA enabled:
bzr 1.13.1-1
bzr-dbus 0.1~bzr36-3
bzr-gtk0.97.0-1~bazaar1~jaunty1
bzrtools 1.13.0-1
seahorse 2.26.1-0ubuntu1
seahorse-plugins 2.26.1-0ubuntu1
Note: The upstream bug report says
I've just read through all the gnome-media bugs on launchpad. There is
no bug besides this one that describes this problem.
--
gnome-sound-recorder: Record from input doesn't show all available inputs
https://bugs.launchpad.net/bugs/378333
You received this bug notification because you are a
I just went to bugzilla.gnome.org, and
a) Read the titles of all open bugs against Gnome-Sound-Recorder
b) Searched bugs in all states (open, closed, ...) for comments that mention
pulse and then again for pulseaudio.
None of those bugs describe this problem.
--
gnome-sound-recorder: Record
That doesn't make sense; if I could have found the bug in the first
place, I wouldn't have filed a new one...
This policy also doesn't help the other people who find all the dups via
google, see they've all just been closed out, and have to file a new one
because they can't find the original.
--
No, my behaviour is not confrontational. In fact, to be honest, I found
your behaviour (just closing the bug without any useful information at
all) quite aggressive.
* If the bug is not a bug, then by all means close it (and state why, so
that everyone else who is affected by this problem and
Reopening. Simply closing the bug claiming that it's a dup without proof
is non-sensical.
** Changed in: gnome-media (Ubuntu)
Status: Invalid = New
--
gnome-sound-recorder: Record from input doesn't show all available inputs
https://bugs.launchpad.net/bugs/378333
You received this bug
Public bug reported:
Binary package hint: gdm
Whenever I boot my laptop from scratch (i.e. not resuming from
standy/hibernate), the X/gdm login screen will play a sound effect when
it's ready for me to log in.
The problem is, this sound effect is always played at the hardware's
maximum volume
Hmm. Further experimentation shows that the gdm pre-login sound is
played back with whatever volume was set when the user last logged out
(or rebooted). I guess the 100% volume issues are in the case of:
a) Live CD default
b) Default on an HDD based install prior to anyone logging in and
Public bug reported:
Binary package hint: gnome-media
When I run gnome-sound-recorder, there's a GUI element labelled Record
from input and a drop-down that displays a single option Capture.
The Gnome volume control indicates that I have two sound input sources;
one Capture: Monitor of Intel
Public bug reported:
Binary package hint: gnome-media
I have a Plantronics USB headset with speakers, microphone, and buttons
for volume up/down and mute.
When I plug this headset into my laptop, and use the volume control
buttons on the headset, it controls the volume on the PC speakers, not
OK, which other bug is it? I could only find closed bugs when I searched
before...
--
gnome-sound-recorder: Record from input doesn't show all available inputs
https://bugs.launchpad.net/bugs/378333
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
41 matches
Mail list logo
