Can someone explain the status change (from unknown to new)? Just
curious. Also curious whether there will be action on this, it continues
to be a usability pain. Thanks!
--
Evolution plain-text email includes formatting "stuff" - should be pure plain
text
https://bugs.launchpad.net/bugs/288185
On Mon, 2010-04-19 at 20:09 +, Pedro Villavicencio wrote:
> this looks similar to bug
> https://bugzilla.gnome.org/show_bug.cgi?id=596204 ; are you still able
> to reproduce the crash?
Evolution-alarm-notify crashes have almost always been unpredictable for
me, but they almost always follow wa
Folks, I'd like to close this as it is likely the problem has been fixed
- please refer to bug# 460710. If you are still experiencing this with
Karmic, please make sure that you have all updates applied, then attempt
to reproduce the bug using the steps above.
If you are no longer experiencing thi
Interesting. That crash occurred before I opened update-manager to apply
the available upgrades. Once update-manager was started, it was allowed
to work to completion (and all upgrades on these machines are manually
initiated).
Difficult to reproduce, at any rate.
--
package gnome-screensaver 2.
** Attachment added: "AptOrdering.txt"
http://launchpadlibrarian.net/37684878/AptOrdering.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/37684879/Dependencies.txt
** Attachment added: "Dmesg.txt"
http://launchpadlibrarian.net/37684880/Dmesg.txt
** Attachment
Public bug reported:
Binary package hint: gnome-screensaver
automatic crash report
ProblemType: Package
Architecture: i386
Date: Sun Jan 3 10:56:21 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new post-removal script killed by signal (Interrupt)
Package: gnome-screensaver 2.28.0-0ub
Brilliant - had the bug again this morning (had to force-quit
evolution), enabled karmic proposed, installed all proposed, tried
sending exact same email, same attachment, worked fine this time: great
work, fix works as promised.
--
Evolution hangs when double-clicking on attachment
https://bugs.
Is this is a dupe of bug# 460710?
--
Evolution freezes when adding attachement
https://bugs.launchpad.net/bugs/476729
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://l
I marked this as invalid for three reasons: 1) it has not happened again
"on its own", 2) I was unable to reproduce it with a specific test case
(create appt 30 minutes in the future; put computer to sleep for 20
minutes; wake computer - reminder is successfully displayed), and 3)
there has been a
Steps to reproduce? Sadly, no. Came back from suspend, it crashed, but
have yet to be able to reproduce. Has not happened otherwise.
--
evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/442986
You received this bug notification because you ar
Marking this as confirmed since it is still a bug, and a well documented
one given the contributions between 05-12 and 06-15.
Update: Plugged in camera today. Error -60 (as above), error -1 (as
above), errors in dmesg. Found this bug report (how could I have
forgotten it! :->), killed gvfs-gphoto2
On Thu, 2009-05-14 at 23:18 +, Sebastien Bacher wrote:
> could you install gphoto2 as indicated by the message before and try
> again to get the log?
I installed the app, tried again, but forgot to get the log. However,
the results were worse:
Install gphoto2
Connect
I performed the sequence described above. For my daughter's account,
error message (-60) then gthumb photo import (her default action) is
started. For my account, same result as above (error, 2 dialogues); for
guest, same (error, 2 dialogues).
In all cases, despite error messages and extra dialogu
OK, this is bizarre. To test default behavior, I restarted the system,
logged in, then issued this command in a terminal:
sudo chmod +x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
I did this in order to restore the system to default behavior, disabling
the workaround quoted previously in the bu
On Wed, 2009-05-13 at 15:23 +, Sebastien Bacher wrote:
> ok interesting, do you run a standard GNOME session?
Yes.
> how many users are logged?
Same result with 1 or 2 users logged in.
> do you get the issue in a guest session?
The camera is with its owner, at school - I will try this thi
On Wed, 2009-05-13 at 14:03 +, Sebastien Bacher wrote:
> What is requested there is extra details, ie "I plug the camera, get a
> dialog asking if I want to import photos, I click ok, f-spot opens and
> displays the error", is that really hard for you to describe?
(Taking a deep breath, counti
On Wed, 2009-05-13 at 12:09 +, Sebastien Bacher wrote:
> now back to the issue:
> - gvfs does mount the device and locks it indeed
Does it? Many/most of us get the -60 error, some of us get the -1 error
as well, and many/most of us can do nothing with the camera without
taking drastic steps (e
On Wed, 2009-05-13 at 12:13 +, Sebastien Bacher wrote:
> you might also describe how you use f-spot to get the issue, f-spot-
> import which is the default GNOME action has this code
>
> "# make sure it's not mounted by gvfs, otherwise we can't access the
> camera
> # (current F-Spot
OK Sebastien, I'll play this game - for a while. When I open the new
bug report, I think I will entitle it "Ubuntu can't mount digital camera
showing a window popup message: -60 could not lock the device message".
That's pretty descriptive of the problem.
Then I'll add the fact that dmesg returns
Whether or not this is a bug depends on expected behavior and nothing
else. Any other behavior is at best a workaround.
On my daughter's machine, plugging in her Kodak C533 worked fine under
Hardy and, if memory serves, under Intrepid. By "worked fine", I mean
that the default photo import applica
On Mon, 2009-04-06 at 12:36 +, Pedro Villavicencio wrote:
> do you have an example that triggers the crash?
Sadly, no. It happened this morning for the first time. I've tried
reproducing it, but have had no success.
--
evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
FWIW, bug# 348159 is related (happened at same time) and has additional
debug information.
--
gnome-screensaver-gl-helper crashed with SIGSEGV
https://bugs.launchpad.net/bugs/348153
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-sc
This report was auto-generated and the problem has not recurred. Since I
cannot reproduce it, I am closing it and will re-open if necessary.
Re The DebuggingProgramCrash page: We need to simplify that process,
perhaps integrate some of these steps into the automatic bug report
utility - the steps
** Changed in: evolution
Importance: Undecided => Unknown
Bugwatch: None => GNOME Bug Tracker #558131
Status: New => Unknown
--
Evolution plain-text email includes formatting "stuff" - should be pure plain
text
https://bugs.launchpad.net/bugs/288185
You received this bug notificat
Re no auto-function: fair point. No sense lowering S/N everywhere!
Re opening upstream: Will do. Guess I needed my frustration levels to
drop low enough to accept what must be done. I'll try to get that report
in within the next few days, then add the link here.
--
Evolution plain-text email inc
This is not a "I wish it were otherwise" feature request: This is an
accessibility and usability bug.
When a user makes a data format input/display choice, a choice supported
by the software, they are making an accessibility choice. If the
software gets it wrong, the software requires correction.
** Also affects: evolution
Importance: Undecided
Status: New
--
Evolution plain-text email includes formatting "stuff" - should be pure plain
text
https://bugs.launchpad.net/bugs/288185
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug a
Public bug reported:
Binary package hint: evolution
If a user sets their preferences to use/prefer plain-text email, then
all new emails and all replies should be pure plain-text - no formatting
boxes, no formatting choices, etc. Plain text is plain text.
Instead, when I reply to certain emails,
** Tags added: need-i386-retrace
--
[apport] gpilot-applet crashed with SIGSEGV
https://bugs.launchpad.net/bugs/103633
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-pilot in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@
On Wed, 2007-03-14 at 07:46 +, jens_acamedia wrote:
> why does
> "lshal -m > file"
> not work
I wondered this myself, and have no explanation. I suppose - and this is
a guess - the lshal dev chose to directly manipulate streams when lshal
is invoked with --monitor (-m) to prevent lshal itself
Ralf, we should be able to detect the behavior you posit in comment#13.
Could you try this test and report back, please?
Open a terminal window
Run lshal -m
Press the keyboard power off key
The command "lshal -m" monitors for important events and device property
changes - the keycod
I'm closing this report as fix released based on Mark's most recent
comment. Thanks all!
** Changed in: linux-source-2.6.15 (Ubuntu)
Status: Needs Info => Fix Released
--
enabling DMA on CD-ROMs causes hal failures
https://launchpad.net/bugs/22599
--
desktop-bugs mailing list
desktop-bu
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6461687/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6461688/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6461689/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: evolution
Start in main window, at email.
Open a second window. Switch that window to Calendar.
Return to first window. Reply to an email; message filters automatically
move the sent item to the current folder. Switch to another email,
reply, boom.
Evo
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6440805/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6440806/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6440807/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: evolution
I had two windows open, mail and contacts. I'd recently saved a contact,
deleted the email from that contact, and evolution was attempting to
display the next email. I clicked on the email above that one, and
evolution died.
ProblemType: Crash
Mark, Tiago, would it be possible for you to test this behavior with
Ubuntu 6.10 (Edgy) and report back?
Thanks!
--
enabling DMA on CD-ROMs causes hal failures
https://launchpad.net/bugs/22599
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/
*** This bug is a duplicate of bug 36290 ***
** This bug has been marked a duplicate of bug 36290
Misplaced bubble after suspend
--
When no icon is shown, notification bubbles show up in lower right corner of
screen
https://launchpad.net/bugs/45659
--
desktop-bugs mailing list
desktop-bugs
Marking as "Rejected" - bug has been in "Needs info" for almost four
months with no additional feedback. Toyed with "Fix released" based on
various comments, decided "Rejected" better matched workflow.
** Changed in: gnome-session (Ubuntu)
Status: Unconfirmed => Rejected
--
taskbar blinks
Are you still experiencing this bug?
If so, does the bug continue to appear if you run the command
sudo tzconfig
???
pww
--
[time-admin] System clock reverts to GMT at boot
https://launchpad.net/bugs/35423
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/m
Is this not a duplicate of
https://launchpad.net/distros/ubuntu/+source/evolution/+bug/9870 ?
I'm reluctant to mark 48872 as a dupe, as others may feel they are
separate problems, but from reading 9870, it seems to me that spam
filtering has been mangled in Evolution for years, this isn't somethin
Is this not a duplicate of
https://launchpad.net/distros/ubuntu/+source/evolution/+bug/9870 ?
I'm reluctant to mark 62192 as a dupe, as others may feel they are
separate problems, but from reading 9870, it seems to me that spam
filtering has been mangled in Evolution for years, this isn't somethin
Is this not a duplicate of
https://launchpad.net/distros/ubuntu/+source/evolution/+bug/9870 ?
I'm reluctant to mark 37878 as a dupe, as others may feel they are
separate problems, but from reading 9870, it seems to me that spam
filtering has been mangled in Evolution for years, this isn't somethin
I can now consistently sync the Palm V over serial, with a couple of
caveats:
1) Only after a boot and before a suspend - there appears to be a kernel
bug related to waking up the serial port. This is obviously out of scope
for this report, just FYI, in case others have the problem of "no sync
aft
Humph, forgot to mention this is under Edgy, er, production Ubuntu 6.10,
all stock, no special patches or bleeding edge bits.
--
Sync with PalmV over serial is inconsistent at best (Dapper)
https://launchpad.net/bugs/31898
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists
Sitsofe, the subject of this comment probably best summarizes the
current state of syncing for me.
The original bug - inconsistent syncing - appears to have been resolved:
I can sync consistently now. However, I still have the following
problems.
1) Progress indicators are meaningless: I get the
https://launchpad.net/malone/bugs/35010
*** Bug 35029 has been marked a duplicate of this bug ***
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/35029
*** This bug has been marked a duplicate of bug 35010 ***
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/31898
Comment:
All latest updates as of 20060305 (not sure what change might have
brought improvements, some gnome applet changes, etc., but no pilot-
specific as far as I can tell).
Two syncs so far today: Copy from Pilot, then a regul
Public bug report changed:
https://launchpad.net/malone/bugs/31898
Comment:
OK, a few steps forward, a few back. All latest updates as of 20060303
applied (2.6.15-17-686 kernel), gnome-pilot is ubuntu16, etc.
gnome-pilot is still crashing intermittently, but sometimes data syncs
and sometimes it
Public bug report changed:
https://launchpad.net/malone/bugs/33126
Comment:
Seeing this with IBM ThinkpadA20m as of yesterday's Dapper updates,
which upgraded:
hal (0.5.6-4ubuntu4) to 0.5.7-1ubuntu1
hal-device-manager (0.5.6-4ubuntu4) to 0.5.7-1ubuntu1
Had not seen this error until these updates
Public bug report changed:
https://launchpad.net/malone/bugs/31898
Comment:
Tested 20060225, still failing, all latest versions (updates made since
20060220):
gnome-pilot 2.0.13-0ubuntu15
libgnome-pilot2 2.0.13-0ubuntu15
gnome-pilot-conduits 2.0.13-0ubuntu3
--
desktop-bugs mailing list
deskto
Public bug report changed:
https://launchpad.net/malone/bugs/31898
Comment:
Occurs in Flight4 with all latest updates as of 20060220.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
https://launchpad.net/malone/bugs/31898
Affects: gnome-pilot (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
ThinkpadA20m. Dapper Flight3+. Pilot applet correctly configured
(AFAICT). Hit sync on cradle, gets as far as id
54 matches
Mail list logo
