Marking this bug as fixed since I'm no longer able to reproduce the bug.
If anyone else is still affected by the bug, please reopen it.
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop
Milan: I don't have the issue at the moment. However, I think I had it
for a while after upgrading, IIRC it was fixed by a maintenance upgrade.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
I just tested this in Lucid with Evolution version 2.28.3-0ubuntu10.
It's still reproducible.
** Changed in: evolution (Ubuntu)
Status: Incomplete = New
--
Evolution doesn't honor the HTML mode setting when replying to messages
https://bugs.launchpad.net/bugs/493784
You received this bug
I just tested this in Lucid with Evolution version 2.28.3-0ubuntu10.
It's still reproducible.
** Changed in: evolution (Ubuntu)
Status: Incomplete = New
--
Can't edit original message when replying to HTML mail
https://bugs.launchpad.net/bugs/493789
You received this bug notification
Tried to remove the service file, this resulted in the original problem with
GKD not starting when logging in through GDM with a password. Seahorse produces
the following error message on the terminal:
** Message: secret service operation failed: The name org.freedesktop.secrets
was not
Btw, I checked the patch on
https://bugzilla.gnome.org/show_bug.cgi?id=619209. I It won't work, the
difference is mainly that they always pass the --login option to GKD
independent of whether a password was entered or not. In my case, i.e.
logging in with a password, there shouldn't be any
The problem is that it seems like the daemon doesn't start correctly
early in the login process. The reason I lack the --login option is
because it, in the case where I have the .service file present, is
started when the first client requests the service. I really think, and
this seems to be
Without auto-login I get the following error messages in auth.log:
May 24 21:58:18 minotaur gnome-keyring-daemon[3045]: couldn't connect to dbus
session bus: /bin/dbus-launch terminated abnormally with the following error:
No protocol specified#012Autolaunch error: X11 initialization failed.
May
That was without auto-login and without password-less login.
I get the messages in the original description when auto-login is enabled.
Output from 'ps x | grep keyring' in this case is:
gnome-keyring-daemon --start --components=secrets
But that is likely only due to the fact that I added a
I was using automatic login (but the account is not a member of the
nopasswdlogin group) when I filed the original bug report. I tried
disabling auto login, but that only made things worse, now every
application using the g-k-d just hangs when it tries to communicate with
the daemon.
--
I would argue that this is a separate bug . Bug #525642 deals with the
missing service file, which, had it existed, would only have solved
parts of the problem. For example, ssh-agent functionality does not work
if the daemon is started by dbus since it relies on setting environment
variables.
--
Public bug reported:
Binary package hint: gnome-keyring
There seems to be a race between dbus initialization and starting of
gnome-keyring-daemon (auto-start file in /etc/xdg/autostart). The
following lines are logged in the authentication log:
May 2 01:48:27 minotaur
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47098478/Dependencies.txt
--
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring
It seems like this bug may be a duplicate of bug #525642. However, even
though creating a new service for the org.freedesktop.secrets.service
fixes most of this issue, the start scripts in /etc/xdg/autostart/gnome-
keyring-* are still broken. The ssh-agent functionality will probably
not work
No, there is no crash associated with it, I was trying to debug a freeze
in evolution on when I encountered it, but that is probably related to
something in the evolution-data-server. But, since the assertion
triggered, there is obviously something wrong in the source (could be
something in the
Public bug reported:
Binary package hint: evolution
When selecting an email on both local and IMAP accounts Evolution logs the
following:
(evolution:4040): evolution-shell-CRITICAL **: e_shell_window_peek_shell:
assertion `E_IS_SHELL_WINDOW (window)' failed
** (evolution:4040): DEBUG: Setting
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41052777/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/41052778/XsessionErrors.txt
--
e_shell_window_peek_shell: assertion `E_IS_SHELL_WINDOW (window)' failed
1. Yes, as far as I can tell, this is completely reproducible. I've
tried replying to several different messages with HTML mode set to 'Only
ever show PLAIN' and the new message still quotes the HTML version of
the original message.
2. Set 'HTML mode' == 'Only ever show PLAIN'. Open a message
Public bug reported:
Binary package hint: evolution
If I set HTML mode to 'Only ever show PLAIN' Evolution still uses the
HTML formated message when replying to an HTML formatted e-mail.
ProblemType: Bug
Architecture: amd64
Date: Mon Dec 7 22:45:12 2009
DistroRelease: Ubuntu 9.10
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36549437/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/36549440/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/36549442/ProcStatus.txt
** Attachment
Public bug reported:
Binary package hint: evolution
Sometimes when I reply to an email that contains HTML Evolution doesn't
let me edit the quoted original message. The message is quoted with
badly misaligned '' characters. When trying to insert answers into the
message it is impossible to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36549751/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/36549752/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/36549753/ProcStatus.txt
** Attachment
It did, which isn't so strange since the problem really is that f-spot
can't update the database, creating a new one isn't a problem. IIRC
that's what I did and retagged all the photos.
--
F-Spot fails to update database
https://bugs.launchpad.net/bugs/307960
You received this bug notification
It seems like some of the people commenting on this bug are really
affected by bug #405005 rather than this one. The exceptions that
contain references friends_get_response are related to that bug. The one
mentioning photos_getAlbums_response could also be related to bug
#405005, but is in that
** Attachment added: Change set that fixes the bug
http://launchpadlibrarian.net/29550635/e8986b85c5257a3ef5deb60c5531296de32c5fd0.patch
--
F-Spot crashes during authorization exporting to Facebook if friend IDs are
large
https://bugs.launchpad.net/bugs/405005
You received this bug
Public bug reported:
Binary package hint: f-spot
F-spot version 0.5.0.3-1ubuntu6 running on 64 bit Jaunty crashes when
exporting to Facebook if a friend has a large ID. This was fixed by
change set e8986b85c5257a3ef5deb60c5531296de32c5fd0 in the F-spot GIT
repository.
The following exception is
Note that this is different from #363067 which (originally) dealt with
an unexpected HTTP response code. Some of the comments on that bug are
really related to this bug.
--
F-Spot crashes during authorization exporting to Facebook if friend IDs are
large
https://bugs.launchpad.net/bugs/405005
Just checked with the version 0.5.0.3-1ubuntu6 on jaunty. Seems to be
working fine now.
--
f-spot crashes with unhandled exception when importing photos
https://bugs.launchpad.net/bugs/362592
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Kinda embarrassing not thinking about including that information in the
original report... :(
I was running on Intrepid for AMD64. The F-Spot version was
0.5.0.3-0ubuntu4.
--
f-spot crashes with unhandled exception when importing photos
https://bugs.launchpad.net/bugs/362592
You received this
Public bug reported:
Binary package hint: f-spot
When using the attach tag functionality when importing photos f-spot
may crash with the following exception if one of the tags already
exists.
Unhandled Exception: Mono.Data.SqliteClient.SqliteSyntaxException: table
population already exists
The requested debug output has been attached. Doesn't look like it
contains anything useful except for what's in the description already.
** Attachment added: Output from f-spot --debug
http://launchpadlibrarian.net/20474370/f-spot-debug.txt
--
F-Spot fails to update database
Public bug reported:
Binary package hint: f-spot
F-spot version 0.5.0.3-0ubuntu4 fails to import the database from an
earlier F-spot version. The database is renamed and a new empty database
is created instead of upgrading the old one, i.e. all photo tags are
lost.
The f-spot produces the
Allan:
The problem that we've been facing isn't that the postrm scripts don't run
metacity --replace, this could also be a problem if you are uninstalling compiz
from within the desktop environment, but we wouldn't have noticed that since we
had no running X-terminals at that point. The problem
33 matches
Mail list logo
