[Bug 288185] Re: Evolution plain-text email includes formatting stuff - should be pure plain text
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 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 566544] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
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 waking from suspend. I've never been able to get one to occur reliability, but when they occur they tend to come in consistent bunches (get several over a course of days, then not again for weeks/months). -- evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/566544 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 476729] Re: Evolution freezes when adding attachement
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 this, please let us know so we can close this report. -- 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505637] [NEW] package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt)
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-0ubuntu3.2 ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: gnome-screensaver Title: package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) Uname: Linux 2.6.31-16-generic i686 ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) https://bugs.launchpad.net/bugs/505637 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505637] Re: package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt)
** 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 added: DpkgTerminalLog.txt http://launchpadlibrarian.net/37684881/DpkgTerminalLog.txt -- package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) https://bugs.launchpad.net/bugs/505637 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 505637] Re: package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt)
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.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) https://bugs.launchpad.net/bugs/505637 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 476729] Re: Evolution freezes when adding attachement
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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 460710] Re: Evolution hangs when double-clicking on attachment
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.launchpad.net/bugs/460710 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 442986] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
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 considerable number of updates since the bug occurred, it's likely it was fixed by recent changes. ** Changed in: evolution (Ubuntu) Status: Incomplete = Invalid -- evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/442986 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 442986] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
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 are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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-etc., remounted camera, no errors, able to import photos but had to start f-spot manually. Difference between then and now? Recent system updates must have restored sufficient sanity to unbork the system, though it still does not work as expected. ** Changed in: gvfs (Ubuntu) Status: Invalid = Confirmed -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 camera: Error -60, error -1 No default application, no pop-up to choose application Start f-spot, attempt to connect to camera, long delay, then error: unable to access camera, unknown error uninstall gphoto2, libcdk5, repeat: Same result! So installing gphoto2 borked what used to work. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 bug report. Then I rebooted, logged in, and connected the Kodak C533. First pop-up was the error -60 pop-up. Then, two (2!) you have connected a camera, do you want to open f-spot pop-ups appeared. I chose to open f-spot, f-spot started, the second you have connected a camera pop-up went away on its own, I dismissed the error pop-up, and f-spot was able to talk to the camera just fine. I then turned the camera off, started a guest session, turned the camera on, and got exactly the same behavior. For whatever reason, it has gone from doesn't work at all to works with bizarre extra dialogue and scary dialogue behavior. The only differences between today and last time I tried this are: a) My daughter was also logged in last time (she had logged in first), and b) the chmod -x, chmod +x steps done to make things work last time and to test this time. When my daughter gets home, I will try this again. This is what we will do: Start the machine. She will log in. She will attempt to connect the camera. She will disconnect the camera. I will log in. I will attempt to connect the camera. I will disconnect the camera. I will log in as guest. I will attempt to connect the camera as guest. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 dialogues, photo import works fine. I do not believe I made any other changes to the system, but now I am doubting myself. As for the command output you requested, $ gphoto2 --summary The program 'gphoto2' is currently not installed. You can install it by typing: sudo apt-get install gphoto2 bash: gphoto2: command not found The output of gvfs-mount -li is attached. ** Attachment added: output of gvfs-mount -li http://launchpadlibrarian.net/26736624/gvfs-mount--li -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 something that looks a awful lot like: usb 1-1: new full speed USB device using ohci_hcd and address 3 usb 1-1: configuration #1 chosen from 1 choice scsi10 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning Then I'll mention the fact that if I execute the following two commands, the camera can be used in fspot: sudo killall gvfs-gphoto2-volume-monitor sudo chmod -x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor (Of course, fspot no longer opens automatically, I have to open it manually and manually import the photos, but at least it works. Hey, that's good enough, right?) Then a few more people will add information about the same problem. Then guess what? Deviens, si tu peux! My bug report will get marked as a duplicate of this open, because IT IS THE SAME BUG! Exactement le meme. Oh, by the way, the status you are playing? Tu ne suis pas les regles! The bug status you should be using is Wontfix. At least that's descriptive. Because whatever you say, this is a valid bug report (it contains sufficient information to describe the behavior, properly characterizes the behavior as inappropriate, and properly characterizes it as a regression. So it is by any stretch of the imagination valid. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 version does not yet understand GIO) gvfs-mount -u $udi || true which works fine here and should lead to no error when importing images We get f-spot to work by killing gvfs-gphoto2 (as per the killall in my previous comment) and marking the appropriate gvfs-gphoto2 script as non-executable. Then f-spot can see the camera. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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.g., killall gvfs-gphoto2, chmod -x gvfs-gphoto2) - software wanting to use the camera should know about that and gvfs-mount -u if required, f-spot and gthumb at least does it Really? See previous comment (it don't work). - if somebody has an issue with a software could you open a bug against that software explaining what you do and how it fails so those softwares can be changed to do the right thing? If somebody has an issue with a software With all due respect, Sebastien, these are the words of a cubicle-bound coder and not the words of someone interested in assisting anyone other than another developer. Most users - the vast majority who just want their computers to work reliably and as expected - do not have the technical knowledge to make the distinction you describe. They used to plug in their camera, it worked. Now it doesn't. For most users - the vast majority who just want their computers to work reliably and as expected - the software in question is Ubuntu. That's what they see. Sure, for debugging purposes this can be refined by triagers or developers who know better, but that requires insight and inside knowledge. This is a valid report. If it is not a GVFS bug, then please, since you know more about the inner goings on of the software involved, please direct it elsewhere. If you need to know something specific to assist you with that, then please ask for it. If the bug as originally reported no longer exists, then please mark this fix released, clarify why this report does not apply, and respectfully request that a new report be opened. Continuing to shut this down as invalid is simply a slap in the face to the many people who have tried to contribute to this report. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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, counting to ten.) Plug the camera in. Get error -60 (who knows from where - the dialogue pops up) Get error -1 No application is started. Nothing useful happens. Only error messages appear. What used to happen: Camera was recognized, user was asked if they want to import photos or perform some other action. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 this evening and report back. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
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 application opened. This was EXPECTED BEHAVIOR. Now that her machine has been upgraded to Jaunty, this no longer works. She gets two error messages, the -60 and an unknown -1. This IS NOT expected behavior. The fact that there is a workaround is wonderful. For the technical user. For the rest of the world, this is a bug. In fact, it is a REGRESSION. What worked no longer works. Frankly, this is a matter of fact - what worked no longer works - and not opinion - something works differently/better/worse but still works. ** Changed in: gvfs (Ubuntu) Status: Invalid = Confirmed -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 356162] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
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() https://bugs.launchpad.net/bugs/356162 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 348153] Re: gnome-screensaver-gl-helper crashed with SIGSEGV
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 are many and relatively complex, daunting for many users. ** Changed in: gnome-screensaver (Ubuntu) Status: Incomplete = Invalid -- 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-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 348153] Re: gnome-screensaver-gl-helper crashed with SIGSEGV
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-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288185] Re: Evolution plain-text email includes formatting stuff - should be pure plain text
** 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 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288185] Re: Evolution plain-text email includes formatting stuff - should be pure plain text
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 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288185] [NEW] Evolution plain-text email includes formatting stuff - should be pure plain text
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, there are formatting boxes present in the reply - those boxes with dotted line edges. These contain the quoted reply. They shouldn't be there!!! And they make it extremely difficult edit a reply properly. With plain text selected, there should be the X wrote Y on D header, the quoted reply (... with an intelligent line length limit, e.g., 72), and any auto-inserted signature. And they should all be plain text lines. In other words, I should be able to insert new lines and new text anywhere I want: After the header, in the middle of the quoted test, before the signature, etc. But I cannot, because evolution appears to be trying to be helpful and is missing the mark. This makes it somewhere between aggravatingly inconvenient and impossible to format replies as I want, in other words, to achieve proper emphasis, to rearrange text conveniently for readability, etc. (On a possibly related note, I used to be able to use ctrl-L to go reflow quoted text and it would do the right thing - that has disappeared. Are these related directions?) Every time I encounter this aggravation I seriously consider going to Mutt, despite its configuration complexity problems, or, worse, pine, which was quite a good MUA, despite its licensing challenges. The calendar and contacts integration is keeping me on evolution, but I'm not sure how long that will last. This is not a wishlist item, this is a usability and accessibility issue: If a user chooses and prefers plain text, give them plain text. (I've trolled the help and all preferences to make sure I am not missing anything, to ensure I have plain-text selected everywhere I need to, because this is extremely aggravating and is a serious - I'm not kidding! - productivity issue.) ** Affects: evolution (Ubuntu) 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 subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288185] Re: Evolution plain-text email includes formatting stuff - should be pure plain text
** 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 288185] Re: Evolution plain-text email includes formatting stuff - should be pure plain text
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. If I choose plain-text, I should get text as plain as in this form, as in vi, as on a piece of paper. No bells-and-whistles, no attempts to be helpful, no attempts to second-guess what I *really* meant. Either of the latter is simply paternalistic and contrary to be best principles of usability and accessibility. On a side-note, should there not be a simple click to forward upstream option? Forcing a user make the same effort a second time is far too close to the you got it wrong, n00b response far too common in the floss world. The also affects project option does not appear to have the right result (which is to let the computer do as much of the work as possible). -- 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 103633] Re: [apport] gpilot-applet crashed with SIGSEGV
** 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 81227] Re: Logout screen appears twice [Feisty]
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 from disturbing the devices it is monitoring i cant capture it unless its piped to a file since my computer shuts down when i press powerbutton. help appreciated..thanks Try using script: $ script halout $ lshal -m Then, whatever happens, halout should contain what you are looking for (probably best not to write the script file - halout - to /tmp, it could cleaned away reboot). For best results, you might try script -f -c lshal -m halout That puts the whole thing on one line, and the -f option ensures that output is flushed to disk as it is produced. -- Logout screen appears twice [Feisty] https://launchpad.net/bugs/81227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 22599] Re: enabling DMA on CD-ROMs causes hal failures
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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81227] Re: Logout screen appears twice [Feisty]
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 keycode event generated by pressing the poweroff button should appear there. If there are two events generated, both should be there (To capture the output of lshal, you may need to copy and paste from the terminal, or run it within script piping to a file or another process does not seem to work, at least not for me - contact me directly if you need assistance with script) -- Logout screen appears twice [Feisty] https://launchpad.net/bugs/81227 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85815] [apport] evolution crashed with SIGSEGV in html_object_get_left_margin()
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. Evolution is moving an email from sent to current folder while managing focus between previous and current message in current folder. ProblemType: Crash Date: Sat Feb 17 11:09:59 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evolution InterpreterPath: /usr/bin/evolution-2.10 Package: evolution 2.9.91-0ubuntu1 ProcCmdline: evolution --component=mail ProcCwd: /home/pww ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: evolution StacktraceTop: html_object_get_left_margin () ?? () from /usr/lib/libgtkhtml-3.8.so.15 ?? () ?? () ?? () Uname: Linux EdgeKeep-PC001 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: evolution (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] evolution crashed with SIGSEGV in html_object_get_left_margin() https://launchpad.net/bugs/85815 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85815] Re: [apport] evolution crashed with SIGSEGV in html_object_get_left_margin()
** 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 ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6461690/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6461691/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/6461692/Registers.txt ** Attachment added: Stacktrace.txt http://librarian.launchpad.net/6461693/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://librarian.launchpad.net/6461694/ThreadStacktrace.txt -- [apport] evolution crashed with SIGSEGV in html_object_get_left_margin() https://launchpad.net/bugs/85815 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85348] [apport] evolution crashed with SIGSEGV in html_object_get_left_margin()
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 Date: Thu Feb 15 07:54:41 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/evolution InterpreterPath: /usr/bin/evolution-2.10 Package: evolution 2.9.91-0ubuntu1 ProcCmdline: evolution --component=mail ProcCwd: /home/pww ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: evolution StacktraceTop: html_object_get_left_margin () ?? () from /usr/lib/libgtkhtml-3.8.so.15 ?? () ?? () ?? () Uname: Linux EdgeKeep-PC001 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video ** Affects: evolution (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] evolution crashed with SIGSEGV in html_object_get_left_margin() https://launchpad.net/bugs/85348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 85348] Re: [apport] evolution crashed with SIGSEGV in html_object_get_left_margin()
** 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 ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6440808/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6440809/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/6440810/Registers.txt ** Attachment added: Stacktrace.txt http://librarian.launchpad.net/6440811/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://librarian.launchpad.net/6440812/ThreadStacktrace.txt -- [apport] evolution crashed with SIGSEGV in html_object_get_left_margin() https://launchpad.net/bugs/85348 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 22599] Re: enabling DMA on CD-ROMs causes hal failures
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/desktop-bugs
[Bug 49817] Re: taskbar blinks after restoring session
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 after restoring session https://launchpad.net/bugs/49817 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 45659] Re: When no icon is shown, notification bubbles show up in lower right corner of screen
*** 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35423] Re: [time-admin] System clock reverts to GMT at boot
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/mailman/listinfo/desktop-bugs
[Bug 37878] Re: bogofilters trumps spamassassin on dapper upgrade
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 something new. For example, https://launchpad.net/distros/ubuntu/+source/evolution/+bug/48872 also concerns mangling. To me, these seem to be symptons of the same underlying problem: Evolution's spam filter doesn't work out of the box, cannot be trained without counter-intuitive actions (mark as spam, then ham), and does not cooperate with user addins (which shouldn't be necessary, IMHO). There's also https://launchpad.net/distros/ubuntu/+source/evolution/+bug/62192, which seems to come from this same underlying problem. Would the problem get more or less attention and TLC if these bugs were all marked dupe of a 2+ year old high importance confirmed bug? -- bogofilters trumps spamassassin on dapper upgrade https://launchpad.net/bugs/37878 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 62192] Re: evolution ships with spam filtering completely mangled
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 something new. For example, https://launchpad.net/distros/ubuntu/+source/evolution/+bug/48872 also concerns mangling. To me, these seem to be symptons of the same underlying problem: Evolution's spam filter doesn't work out of the box, cannot be trained without counter-intuitive actions (mark as spam, then ham), and does not cooperate with user addins (which shouldn't be necessary, IMHO). On that last note, https://launchpad.net/distros/ubuntu/+source/evolution/+bug/37878 seems to come from this same underlying problem. Would the problem get more or less attention and TLC if these bugs were all marked dupe of a 2+ year old high importance confirmed bug? -- evolution ships with spam filtering completely mangled https://launchpad.net/bugs/62192 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31898] Re: Works well enough now (Re: Sync with PalmV over serial is inconsistent at best (Dapper))
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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31898] Works well enough now (Re: Sync with PalmV over serial is inconsistent at best (Dapper))
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 after resume. 2) The second progress indicator still behaves oddly, especially during the Econduits - it's fine during the backup ops, for example. I am now getting useful logs, such as: Collecting synchronization info... EAddress: Started EAddress: Ended ECalendar: Started ECalendar: Ended Backup: Making backup of DatebookDB Backup: Making backup of LauncherDB MemoFile: Started MemoFile: Ended EToDo: Started EToDo: Ended Backup: Making backup of ToDoDB Backup: Making backup of Unsaved Preferences Backup: Making backup of Saved Preferences Given all of this, I am going to mark this as Fix released, 'cause it works, and what doesn't work probably isn't related to the originally reported problem. My apologies for the delay in reporting, best efforts and all that ** Changed in: gnome-pilot (Ubuntu) Status: Needs Info = Fix Released -- 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31898] No progress indicators or logs for sync with PalmV over serial
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 whipping back and forth per conduit; 2) No logging: No information at all in the gnome-pilot logs. According to the log information on the Palm itself, all is well. Would you like me to open new reports specifically about those? Sorry for the information overload, I was trying to provide as much information as possible to help developers locate the bug(s), since the original problem was inconsistent -- 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.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35029] In update of package, message of error
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
[Bug 35010] Fails to install: No /etc/alternatives/x-cursor-theme
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
[Bug 31898] Sync with PalmV over serial is inconsistent at best (Dapper)
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 regular update after updating some ToDos from within Gnome (click on date, mark ToDo complete). All is well, so far: applet is still running, no crashes, can sync reliably, seemingly. PalmV is set as fast as possible, gnome-pilot to 34800, will try progressively faster speeds and update report. Problems: A) No logs whatsoever, no text displayed in text portion of progress monitor. Also, no textual explanations of what the two progress bars represent (obvious to me, may not be to others, esp. with problems in 'B'). B) When sync'ing using NON-Evolution conduits, i.e., memos, progress bar behaves pretty much as expected: Upper bar shows over progress, lower bar shows memo progress, and dialog indicates sync'ing memos. The whip effect described above appears when using EVOLUTION CONDUITS and only while actually sync'ing items; once an area, e.g., Calendar, is complete, dialog indicates finished sync'ing X and the lower progress bar advances normally (all the way from left to right, albeit slowly). Conclusion: Sync works, seemingly reliably, applet stays running, UI could stand verification to ensure non-technical users get appropriate data integrity and process reassurance. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31898] Sync with PalmV over serial is inconsistent at best (Dapper)
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 doesn't. I've not yet had a complete sync (always crashes before completion). One positive change: the progress dialog at least now identifies the data being synch'd (e.g., synching address). The progress bar still whips back and forth, but at least there is some feedback. Nothing useful in syslog, daemon.log, etc. Guidance re collecting useful log data would be most welcome, pww -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31898] Sync with PalmV over serial is inconsistent at best (Dapper)
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 desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 31898] Sync with PalmV over serial is inconsistent at best (Dapper)
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
[Bug 31898] Sync with PalmV over serial is inconsistent at best (Dapper)
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 identifying user, sometimes gets farther, sometimes times out. If it gets farther, then sometimes progress dialog appears, sometimes not. If not, pilot applet crashes, is never reloaded. If progress dialogs appear, never have any useful text, progress indicators fly back and forth but never show anything useful. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
