[Bug 530605] Re: gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.
I already posted to Bug #532024 with my symptoms. I'm attaching a backtrace of the running gvfsd-smb process. It seems to hang while trying to contact gnome-keyring-daemon. I tried to make the backtrace as complete as possible symbol-wise, but let me know if I can provide more info. The issue is 100% reproducible here. ** Attachment added: gdb-gvfsd-smb.txt http://launchpadlibrarian.net/42079269/gdb-gvfsd-smb.txt -- gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu. https://bugs.launchpad.net/bugs/530605 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 530605] Re: gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu.
Here is a backtrace of gnome-keyring-daemon taken while the gvfsd-smb process was hanging. I don't see anything strange here, though. ** Attachment added: gdb-gnome-keyring-daemon.txt http://launchpadlibrarian.net/42079373/gdb-gnome-keyring-daemon.txt -- gvfs-mount doesn't always work. gvfsd-smb starts using 100% cpu. https://bugs.launchpad.net/bugs/530605 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 532024] Re: gvfsd-smb-brows uses 100% cpu after selecting Places--Network
Hi! The behavior I'm observing here is different for SSH (ssh: and sftp: URIs) and for SMB. In the SSH case, the gvfs-sftp process hangs when the password is already in Seahorse. If I go to Seahorse and delete the password, however, I get a password prompt again and can login. Indeed, if I ask the system to not store the password, I can keep accessing the directory by typing the password again every time. In the SMB case on the other hand, I can delete the passwords from Seahorse but that doesn't prevent the gvfs-smb process from hanging. I have tried typing the smb: URI directly or using shortcuts but nothing seems to help. -- gvfsd-smb-brows uses 100% cpu after selecting Places--Network https://bugs.launchpad.net/bugs/532024 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 249373] Re: gnome-session storing broken since intrepid
This is still not working for me, unfortunately. I have the latest version of gnome-session available from Jaunty (2.26.0svn20090408-0ubuntu2) and the problem remains: Log Out from the FUSA applet works properly, whereas Shut Down and Restart don't. My test case is to leave Firefox running and terminate the session. After Log Out, Firefox restarts automatically with the same tabs. When any one of the other two options is used, it complains later about having been terminated abnormally. -- gnome-session storing broken since intrepid https://bugs.launchpad.net/bugs/249373 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 249373] Re: gnome-session storing broken since intrepid
Just a short comment to confirm what user Christoph reported above: session shutdown and saving is sort of working when the log out option is chosen in the menu, but not when the restart or shut down options are selected. -- gnome-session storing broken since intrepid https://bugs.launchpad.net/bugs/249373 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 249373] Re: gnome session does not restore the previous session
It appears that Gnome cannot be trusted to release a new version without major regressions, and Ubuntu needs to rigorously test new versions before committing to them. But they don't. Ubuntu is committed to releasing on a rigid schedule regardless of functionality or regressions, too. No need to put the blame on time-based releases. They are definitely preferable to Debian-style releases, which seem to never get ready. The problem is that, in the absence of guaranteed developer commitment (and you never have guaranteed developers in Open Source) and good project planning, it is impossible to make sure that the desired functionality will be ready for the next release deadline. This is an inherent risk of time-based releases: if you're unlucky, you may have very few new features for your next release. This case was particularly difficult for Ubuntu, I guess, because of the complex dependencies inside of GNOME. Running 2.24 with the 2.22 session manager is no trivial matter (as Gentoo's and Debian's efforts show) so this wouldn't have been possible in the Intrepid time frame. Therefore, the decision was between including 2.24 with the regression, and staying with at least a large portion of 2.22. As we all know, 2.24 won. As I already said elsewhere in this thread, I regret this decision. I think that, by doing this, Ubuntu sends to wrong message upstream. I'm really surprised that such a large regression was possible in GNOME without any discussion whatsoever. In GNOME, a developer needs approval from three release team members in order to change a single string after string freeze, but he can cut off half of the functionality of a core component and nobody says a word. Strange, to say the least. But this is getting off-topic. This should be discussed in some higher Ubuntu forum, but I don't know which one is appropriate. If any of you guys have a better idea of how this can be brought to a higher instance in an appropriate way, I'll be glad to know. -- gnome session does not restore the previous session https://bugs.launchpad.net/bugs/249373 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 287062] Re: Screen resolution capplet unnecesarily tries to set virtual resolution
This is working for me, thanks a lot to everyone involved! I would have tested it before, but didn't notice that a package with the fix was available. -- Screen resolution capplet unnecesarily tries to set virtual resolution https://bugs.launchpad.net/bugs/287062 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 249373] Re: gnome session does not restore the previous session
On Tue, 2008-11-04 at 08:54 +, Sebastien Bacher wrote: You can also note that the low priority focus for this bug upstream is due to the fact that the feature has never been working really correctly on many software and they don't consider that something stable and used by the majority of users, Well, as the comments here show, some people were relying on this feature. This should be out of discussion now. that might be wrong but should be discussed on bugzilla.gnome.org rather than here, intrepid ships now the current version which works mostly correctly and the way to go is to get the bug fixed now in the intrepid updates or jaunty With all due respect, I'm really surprised with this answer. Does this imply that every time an upstream project delivers a new version with regressions, Ubuntu will ship it just because it is the new upstream version, no matter what damage it may cause? Does it imply that if Ubuntu, for whatever reason, ships upstream code with a regression, Ubuntu users will be directed to complain upstream as their only resource? I don't think this reflects Ubuntu's objectives (but please correct me if I'm wrong.) As far as I can tell, Ubuntu has generally done a very good job of selecting appropriate versions of upstream software: stable and functional enough for most people, yet current. And most users now rely on upgrades not containing serious regressions. So it can be argued that the Ubuntu Desktop Team made the wrong decision when they let this software in, because in fact, the problem was very well known to them (https://lists.ubuntu.com/archives/ubuntu-devel/2008-September/026588.html look under Release Status). Now, my intention here is not to point fingers, but to ask for reasonable damage control. As a minimum, I would expect this problem to be acknowledged by the desktop team, and clearly reported in the Release Notes, so that users can decide if they want to update. Of course, it would also be good to try to fix gnome-session at least to the point of not putting user data under risk (see my comment above in this bug report) but I don't know if anyone can commit any resources to that. Finally, regarding us complaining upstream, I'm not sure a lot of disgruntled users commenting in GNOME Bugzilla will be of help. As far as I can tell, this is not just a bug. What's going on here is that the desired functionality is simply not implemented, or very immature in the new gnome-session. So, it cannot be said that it works mostly correctly, because, in reality, it is able to start a session properly, but far from being able to stop or restart it properly, which means it currently does 30 to 50% of the intended functionality. This being the actual state of affairs, I think we'll be very lucky if this is ready for Jaunty. Of course, GNOME should have also reported this clearly in their release notes. They should also tell us what their policy regarding regressions is, because they seem to be very picky regarding obscure ABI regressions, but don't seem to mind large, user-visible regressions that potentially put user data under risk of destruction. But this is something we should try to bring to GNOME, and certainly not through bugzilla. Sorry for the long rant, but the way this problem has been systematically understated worries me deeply, and detracts from the high quality level we are already used to expect from Ubuntu. -- gnome session does not restore the previous session https://bugs.launchpad.net/bugs/249373 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 276134] Re: [intrepid] no prompt to save open work on shutdown/restart
On Mon, 2008-10-27 at 11:34 +, Sebastien Bacher wrote: the reason it's not set as a blocker is that questions on session closing has never been something working reliably, only gedit is blocking the session in the GNOME desktop for example so that's not something user have been relying on, that would still something nice to get fixed though That this never worked reliably is simply not true. With the old GNOME session manager (=2.22), programs supporting the old XSMP protocol (Firefox, OpenOffice, Gimp, and most programs using the GNOME libraries) were indeed able to block session shutdown and ask you if you wanted to save work (you can test it on Hardy). Also, for programs not supporting XSMP, the session manager would ask you to terminate them by hand before shutting down. The new GNOME session manager will just kill all running programs without asking. This is very dangerous and will certainly affect people who (maybe unconsciously) still rely on the old behavior. Regarding gedit, it is one of the few programs that can block session shutdown with the new session manager, and it seems to do this incorrectly, by the way. With the old session manager, it used to work well, as far as I remember. -- [intrepid] no prompt to save open work on shutdown/restart https://bugs.launchpad.net/bugs/276134 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 287082] Re: Cannot go back to higher resolution after setting virtual resolution
Yesterday, after reporting, I noticed that the 2305x1024 virtual resolution should be enough for setting 1280x1024. Today I tested again with the same laptop and projector and noticed that xorg.conf looks different: SubSection Display Virtual 2640 768 EndSubSection I must have copied from the wrong xorg.conf backup. So now it's clear why the 1280x1024 resolution wasn't offered anymore. I'm attaching the complete xorg.conf file, just in case that helps. ** Attachment added: xorg.conf with incorrect virtual resolution set http://launchpadlibrarian.net/18795012/xorg.conf -- Cannot go back to higher resolution after setting virtual resolution https://bugs.launchpad.net/bugs/287082 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 276134] Re: [intrepid] no prompt to save open work on shutdown/restart
I reported this in GNOME Bugzilla (http://bugzilla.gnome.org/show_bug.cgi?id=555795) but the report remains unanswered. Also, the watched Bugzilla bug 553166 seems to be related, but is not about the same problem. -- [intrepid] no prompt to save open work on shutdown/restart https://bugs.launchpad.net/bugs/276134 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 287062] [NEW] Screen resolution capplet unnecesarily tries to set virtual resolution
Public bug reported: Binary package hint: gnome-control-center I have observed the problem when using my laptop (Compaq NC6220) with an external monitor or projector. It can be reproduced as follows: 1. Start with both screens in mirrored (clone) mode, and with no virtual resolution line in xorg.conf. 2. Open the screen resolution capplet. 3. Uncheck the mirror screens box. The screens are still displayed as a single one, that is, you still see only one of them even if they aren't in mirror mode anymore. This is confusing. 4. Click on the visible screen. This will move it under the other one, which should have happened in step 3, anyway. 5. Check the mirror screens box again. The screens come together again. Notice that this state should be exactly equivalent to the initial state, before opening the box. 6. Press the apply button. A message box appears stating that the virtual resolution must be changed, which is obviously not true since we didn't change anything. Accepting the dialog actually inserts some bogus Virtual line in xorg.conf. This happened when using the capplet under intrepid beta (gnome-control- center 2.24.0.1). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Screen resolution capplet unnecesarily tries to set virtual resolution https://bugs.launchpad.net/bugs/287062 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 287062] Re: Screen resolution capplet unnecesarily tries to set virtual resolution
** Summary changed: - Screen resolution capplet innecesarily tries to set virtual resolution + Screen resolution capplet unnecesarily tries to set virtual resolution -- Screen resolution capplet unnecesarily tries to set virtual resolution https://bugs.launchpad.net/bugs/287062 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 287082] [NEW] Cannot go back to higher resolution after setting virtual resolution
Public bug reported: Binary package hint: gnome-control-center The following happened to me today while attemping to use my laptop (compaq nc6220, intel 915 graphics) with a video projector. I attached the projector, opened the screen resolution capplet, selected the projector and turned its output on, and checked the mirror screens box. The highest common resolution was 1024x768. I pressed apply. The virtual resolution dialog appeared telling me that the virtual resolution had to be changed. That was surprising, since, up to this point, the laptop had been operating at 1280x1024. Since answering no here wouldn't apply the changes, and I had to do a presentation in a few minutes, I ended up accepting the change. After logging out and in again, everything worked as expected. After the presentation, I disconnected the projector and tried to go back to my usual 1280x1024, but that resolution simply wasn't offered anymore, and a reboot didn't help to bring it back. Further inspection showed that the following lines had been inserted into my xorg.conf: SubSection Display Virtual 2304 1024 EndSubSection First, I wonder how the 2304 was calculated. Second, the capplet obviously won't offer any resolutions that don't fit into the virtual resolution. It should offer them, though, and should also offer to increase the virtual resolution accordingly. My workaround was to delete the lines from xorg.conf, but a less knowledgable user will be completely lost in this case. This bug is probably related to bug #287062, but I decided to report that separately since it can be triggered in a different way. It is also clearly not the same as bug #224229. I was using the capplet under intrepid beta (gnome-control-center 2.24.0.1). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Cannot go back to higher resolution after setting virtual resolution https://bugs.launchpad.net/bugs/287082 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 276134] Re: [intrepid] no prompt to save open work on shutdown/restart
This happens to me as well with Intrepid Beta updated today. I tested with both an old and a new account with equal results. A simple way to test is just opening Firefox, visiting some URL and ending the GNOME session (a log out will do, no need to shut down). If you log in again and start Firefox it will report that the previous session was terminated abruptly. Other applications, such as OpenOffice are similarly affected. I reported this already in Bug #249373, which is not exactly about this same issue, but that is apparently related. In that bug report user Lukas Hejtmanek confirms that he's observing the same behavior. This bug *should not* be triaged as low priority. It is not only a serious regression, but *will cause data loss* when a user forgets saving before ending her session. I would appreciate people to check if they observe the problem and report here, so that the bug can be at least set to CONFIRMED. -- [intrepid] no prompt to save open work on shutdown/restart https://bugs.launchpad.net/bugs/276134 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 249373] Re: gnome session does not start window manager nor restores the previous session
pakraticus: As far as I know, GNOME *didn't* switch to a new session protocol. There are plans to eventually do that, but, for the time being, the session protocol continues to be XSMP. You may be confused by the fact that the GNOME 2.24 release notes mention DBus for session management, but, as far as I understand it, this is just an interface to control the session manager itself (start the shutdown sequence, for example). -- gnome session does not start window manager nor restores the previous session https://bugs.launchpad.net/bugs/249373 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 249373] Re: gnome session does not start window manager nor restores the previous session
First, correction: GNOME is indeed switching to a new D-Bus-based protocol for session management, but the new session manager *should have legacy support for XSMP*. The latest documentation seem to be http://live.gnome.org/SessionManagement/GnomeSession and XSMP is mentioned there prominently. Also on my machine, the session manager is indeed creating the SESSION_MANAGER environment variable needed by XSMP clients, and the variable points to a UNIX domain socket as expected. Some further observation gives me the impression that, in intrepid, the session is not being saved at all, and that applications aren't being shut down cleanly. Try, for example, starting firefox, loading a page, logging out from the GNOME session, logging in again, and starting firefox again (it won't be restarted automatically, anyway.) Firefox will then report that the previous session was ended forcefully, and ask if its state should be restored. I tried with other applications, such as OpenOffice and Lyx (just open a new document, put some text in it, and log out from GNOME) and this leads to data loss. So I don't think this problem should be considered low priority, it isn't just anoying, it is rather dangerous. Also, Sebastien, the linked upstream bug doesn't really seem to be related to this problem. As far as I understand it, it has to do with the new session manager not being able to restore old session data, saved by the older session manager. Can people please check if they can repeat my results with Firefox and OpenOffice? -- gnome session does not start window manager nor restores the previous session https://bugs.launchpad.net/bugs/249373 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 216197] Re: no weather information in gnome panel
Unfortunately, kmon's approach didn't work for me (Hardy beta, last updated yesterday). As shown in the attachment, the applet is actually able to download and display weather information, but not directly on the panel. Show weather and Show temperature are both checked in my preferences. ** Attachment added: Clock applet shows weather info on a tooltip, but not on the panel http://launchpadlibrarian.net/13405952/Screenshot.png -- no weather information in gnome panel https://bugs.launchpad.net/bugs/216197 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 216197] Re: no weather information in gnome panel
Indeed, my time zone wasn't set. and this seems to have fixed it, thanks Timo! I haven't rebooted as yet, so I don't now if the fix will stay. I'll report it if I observe further problems. By the way, the resetting of the time zone that Timo reports may be related to bug #210561. -- no weather information in gnome panel https://bugs.launchpad.net/bugs/216197 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 203513] Re: display doesn't go to sleep after today's gnome-power-manager update
Same situation here running Hardy beta updated earlier today. This is a desktop machine with a flat panel monitor, and an NVidia graphics card (running the proprietary driver.) I'm attaching the output of gnome- power-bugreport.sh, just in case it's useful. ** Attachment added: Output of gnome-power-bugreport.sh http://launchpadlibrarian.net/12827828/gpm.txt -- display doesn't go to sleep after today's gnome-power-manager update https://bugs.launchpad.net/bugs/203513 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 146946] Re: [gutsy] Gnome settings daemon randomly does not work
Sebastian: I just tried to test starting without dbus-x11 but I cannot remove it anymore since some (important) packages in Hardy depend on it: $ sudo apt-get remove dbus-x11 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: dbus-x11 f-spot gnome-mount gnome-volume-manager policykit-gnome ubuntu-desktop 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded. After this operation, 13.5MB disk space will be freed. Do you want to continue [Y/n]? Am I missing something? -- [gutsy] Gnome settings daemon randomly does not work https://bugs.launchpad.net/bugs/146946 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 146946] Re: [gutsy] Gnome settings daemon randomly does not work
Hardy, last updated earlier today. -- [gutsy] Gnome settings daemon randomly does not work https://bugs.launchpad.net/bugs/146946 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 10669] Re: Filters are not applied to new mail on Exchange
On Fri, 2007-11-16 at 09:39 +, Sebastien Bacher wrote: Could people having the issue try the change? I recompiled evolution-exchange two hours ago with the referenced patch, and, so far, it seems to be working. A few spam messages were already filtered properly. -- Filters are not applied to new mail on Exchange https://bugs.launchpad.net/bugs/10669 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 146946] Re: [gutsy] Gnome settings daemon does randomly not work
On Mon, 2007-11-12 at 03:03 +, Craig N wrote: Same issue here. ... message includes: failed to connect to socket /tmp/dbus-CmrPFTAOO I managed to reproduce the problem by reinstating the session file that was causing the it. The complete error message I get is: There was an error starting the GNOME Settings Daemon. Some things, such as themes, sounds, or background settings may not work correctly. The last error message was: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. GNOME will still try to restart the Settings Daemon next time you log in. It seems to me that we are dealing with different problems that have similar symptoms. Martin, Not sure what /.gnome2/session file is. I don't see it in my .gnome2 directory. I have this: I guess you have to save your session to get one. I save my session automatically when I close, i.e., System|Preferences|Sessions|Sesion Options|Automatically remember running applications when logging out is checked. -- [gutsy] Gnome settings daemon does randomly not work https://bugs.launchpad.net/bugs/146946 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 146946] Re: [gutsy] Gnome settings daemon does randomly not work
I was having this problem consistently after rebooting. My first login attempt after a reboot would always fail with the the dreaded There was an error starting the GNOME Settings Daemon message box. Logging out and logging in again always solved the problem, but it was quite annoying anyway. The good news is, I managed to work around the problem by deleting (renaming actually) my ~/.gnome2/session file. This would point to gnome-session as the actual culprit in this case, instead of the real- time kernel. The kernel, however, may still have something to do, because this problem is most probably caused by a race condition during session startup (the fact that it is intermittent, as well as the fact that it didn't affect me on a second login with a warm cache, both suggest it.) A different scheduler will potentially affect process execution order during session startup, and may increase/decrease the chances of this race condition actually triggering. If you are having this problem, could you please try renaming/deleting your session file and report here your results? Some additional info about my setup: I'm running a Gutsy installation (upgraded recently from Feisty.) I use the real-time kernel from Gutsy, but this problem didn't start when I installed it. The problem was apparently caused by me fiddling with my desktop configuration: I was playing with Awn and changed my panel and theme configuration many times in a few days. -- [gutsy] Gnome settings daemon does randomly not work https://bugs.launchpad.net/bugs/146946 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 10669] Re: Filters are not applied to new mail on Exchange
I'm also seeing this here, and is very annoying due to the large amount of spam I receive. In feisty, filters seemed to work most of time, even if every now and then an email or two would remain unfiltered for unknown reasons. Now in gutsy filters aren't applied at all and must be run by hand. By the way, for those suffering with Evolution's baloon notifications, they can be stopped by dissabling the Mail notification plugin under Edit | Plugins. It worked for me, at least. -- Filters are not applied to new mail on Exchange https://bugs.launchpad.net/bugs/10669 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60115] Re: [2.0beta3] Gaim randomly crashes when open during logout
Same problem here. My crash report is attached. ** Attachment added: Crash report http://librarian.launchpad.net/4861011/_usr_bin_gaim.1000.crash -- [2.0beta3] Gaim randomly crashes when open during logout https://launchpad.net/bugs/60115 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63822] Re: Error in evolution while opening a mail folder
I'm observing this problem as well (Edgy, last updated 2006-10-07).
Additionally, if I select the Inbox folder in my IMAP account, then select the
spam folder in that same account, and the go back to the Inbox folder, the
following happens:
- About four of every five times Evolution crashes.
- When Evolution doesn't crash, it shows the error message copied by the
original reporter when I select Inbox. From that point on, every attempt of
selecting Inbox leads to the same error message and an empty summary window.
I tried to collect debug information with symbols. This is the backtrace
as collected by bug buddy:
Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0
Memory status: size: 175222784 vsize: 0 resident: 175222784 share: 0 rss:
25444352 rss_rlim: 0
CPU usage: start_time: 1160255046 rtime: 0 utime: 217 stime: 0 cutime:199
cstime: 0 timeout: 18 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/evolution-2.8'
Using host libthread_db library /usr/lib/debug/libthread_db.so.1.
[Thread debugging using libthread_db enabled]
[New Thread -1233066320 (LWP 12205)]
[New Thread -1367376976 (LWP 12224)]
[New Thread -1358988368 (LWP 12223)]
[New Thread -1308066896 (LWP 12220)]
[New Thread -1299678288 (LWP 12214)]
[New Thread -1290007632 (LWP 12213)]
[New Thread -1281487952 (LWP 12211)]
0xb7145e91 in __waitpid_nocancel () from /usr/lib/debug/libc.so.6
#0 0xb7145e91 in __waitpid_nocancel () from /usr/lib/debug/libc.so.6
#1 0xb7e411b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
#2 0x0805f8e9 in segv_redirect (sig=11) at main.c:426
#3 signal handler called
#4 0xb70289ac in __lll_mutex_unlock_wake ()
from /usr/lib/debug/libpthread.so.0
#5 0xb70259e9 in _L_mutex_unlock_94 () from /usr/lib/debug/libpthread.so.0
#6 0x001d in ?? ()
#7 0xb71d7ff4 in ?? () from /usr/lib/debug/libc.so.6
#8 0x0869c410 in ?? ()
#9 0x0823a828 in ?? ()
#10 0xbfcfd918 in ?? ()
#11 0xb70259e0 in __pthread_mutex_unlock (mutex=0xbfcfd928)
at pthread_mutex_unlock.c:129
#12 0xb70259e0 in __pthread_mutex_unlock (mutex=0x8103fb8)
at pthread_mutex_unlock.c:129
#13 0xb7184176 in pthread_mutex_unlock (mutex=0x8103fb8) at forward.c:183
#14 0xb722a276 in e_thread_put (e=0x8103fa8, msg=0x869c410) at e-msgport.c:1148
#15 0xb3db3e0c in ml_regen_timeout (m=0x869c410) at message-list.c:3923
#16 0xb3db4586 in message_list_thaw (ml=0x823a828) at message-list.c:3305
#17 0xb3d682ff in emfb_set_folder (emfv=0x8239000, folder=0x8573e00,
uri=0x869c0f8 imap://[EMAIL PROTECTED]:5993/INBOX)
at em-folder-browser.c:1899
#18 0xb3d73902 in emfv_got_folder (
uri=0x869c0f8 imap://[EMAIL PROTECTED]:5993/INBOX,
folder=0x8573e00, data=0x8239000) at em-folder-view.c:691
#19 0xb3da6656 in get_folder_got (mm=0x80ef6c8) at mail-ops.c:1230
#20 0xb3da6065 in mail_msgport_replied (source=0x80cd308, cond=G_IO_IN,
d=0x81c1868) at mail-mt.c:461
#21 0xb755bc8d in g_io_channel_unix_get_fd () from /usr/lib/libglib-2.0.so.0
#22 0xb7532802 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb75357df in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#24 0xb7535b89 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#25 0xb7d15a23 in bonobo_main () from /usr/lib/libbonobo-2.so.0
#26 0x0805f718 in main (argc=1, argv=0xbfcfddc4) at main.c:615
Thread 7 (Thread -1281487952 (LWP 12211)):
#0 0xb71721b7 in ___newselect_nocancel () from /usr/lib/debug/libc.so.6
No locals.
#1 0xb7229f1c in e_msgport_wait (mp=0x81add38) at e-msgport.c:643
rfds = {__fds_bits = {0, 16, 0 repeats 30 times}}
#2 0xb722a5e9 in thread_dispatch (din=0x81adcd8) at e-msgport.c:1035
e = value optimized out
m = (EMsg *) 0x0
info = value optimized out
self = 3013479344
#3 0xb70230fb in start_thread (arg=0xb39e0bb0) at pthread_create.c:261
__res = value optimized out
__ignore1 = value optimized out
__ignore2 = value optimized out
pd = (struct pthread *) 0xb39e0bb0
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1224548364, 0, 8195840,
-1281489688, 1284768912, 1208496331}, mask_was_saved = 0}}, priv = {
pad = {0x0, 0x0, 0x0, 0xb7023092}, data = {prev = 0x0, cleanup = 0x0,
canceltype = 0}}}
not_first_call = 0
robust = value optimized out
#4 0xb71788ee in clone () from /usr/lib/debug/libc.so.6
fstab_state = {fs_fp = 0x0, fs_buffer = 0x0, fs_mntres = {
mnt_fsname = 0x0, mnt_dir = 0x0, mnt_type = 0x0, mnt_opts = 0x0,
mnt_freq = 0, mnt_passno = 0}, fs_ret = {fs_spec = 0x0, fs_file = 0x0,
fs_vfstype = 0x0, fs_mntops = 0x0, fs_type = 0x0, fs_freq = 0,
fs_passno = 0}}
__elf_set___libc_subfreeres_element_fstab_free__ = (
const void *) 0xb71b23a0
Thread 6 (Thread -1290007632 (LWP 12213)):
#0 0xb71721b7 in ___newselect_nocancel () from /usr/lib/debug/libc.so.6
No locals.
#1 0xb7229f1c in e_msgport_wait (mp=0x80ef768) at
[Bug 63822] Re: Error in evolution while opening a mail folder
I just noticed bug #62192. Maybe it is unrelated, but I'm also observing the bogofilter and spamassassin error messages when starting Evolution. Both packages are installed in my machine. The error messages seem to appear irregardless of whether I enable or disable the plugins in Evolution's plugin box. -- Error in evolution while opening a mail folder https://launchpad.net/bugs/63822 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
